This widget could not be displayed.
This widget could not be displayed.
cancel
Showing results for 
Search instead for 
Did you mean: 

Instagram Rear-Facing Camera Bug

NikNik
Star II

I'm experiencing an issue where I'm not able to take (or send) photos taken with the Instagram app using the rear-facing camera.

When attempting to take a photo, the app completely freezes, if I repeatedly click the "x" as to cancel the operation it returns to normal.

Taking photos with the selfie camera works without issue.

Taking photos with the rear-facing camera while applying a filter also works! It seems the issue is exclusive to non-filtered images.

The rear-facing camera has no issues in other apps like SnapChat or the regular Camera app.

I have tried updating my phone and reinstalling the Instagram app, clearing the cache etc. to no avail.

I'm on build number WW_33.0220.0220.101, Android 13.

I will attach two screenshots here. The first one is a screenshot of me having pressed the "capture" button and essentially nothing changes, the screen completely freezes until I;
a) Repeatedly press the "x" button.
b) Exit the Instagram App.

NotWorking.jpg

The second screenshot is a successfully captured picture, this only works if I;
a) Apply a filter to be used during capture (does not seem to matter which filter I pick)
b) Use the front-facing (selfie) camera.

WorkingWithFilter.jpg

  

10 REPLIES 10

NikNik
Star II

@Mansi_ASUSYou're the only moderator I have seen comment on other posts, is this issue being looked at? It seems the issue is prevalent for many people judging by the comments in this thread. Should be pretty easy to reproduce in testing too.

nezt94
Star II

same

NikNik
Star II

@Mansi_ASUSIs anyone looking into this? Seems to be a universal issue at this point?

i wanted to add more info, this issue also happens on my rog phone 7

NikNik
Star II

Since I got no answers here I went ahead and contacted ASUS support directly.

They upgraded my ticket to level  2 and I got the final answer that the issue is recognized and that it will be solved in the next firmware update. I have no time estimate on when the next firmware update arrives.