I've had this issue for a long time. After taking a HDR pic I have to wait at least 15 secs to take another one. İt's frustrating. But when I install the camera version 3.2 it works fine but it keeps updating even auto update is off.
I'm running latest nitrogen build. Does anyone else have similar problem.
Sorry I just realised. This is the wrong forum. Can you please move it to QA section and delete this post
Cheers
Related
Hi everybody,
I updated cym to 7.1 a few days ago and since then the camera no longer works. When I click the camera button the first image the camera sees freezes and that's it. I can't focus on anything else and nothing happens until I push the exposure button again and then all I get is a fuzzy, blurry picture of whatever the camera first saw.
Anyone have a solution for this problem or know what's causing it?
Thanks for your help
Richard
Can't post yet on android development forum so I'm posting this here.
I noticed some people who have recently flashed cm 10.1 have issue with the camera getting stucked for ~10 seconds before flashing and taking pictures when flash is enabled. Some people don't suffer from this issue however.
This is my observation while using the camera as I have also recently flashed cm: When flash is enabled, using the autofocus feature(touching the screen to focus before hitting the capture button) triggers the ~10second hang. Hitting the capture button immediately however without using autofocus doesn't suffer from the same issue.
Hope this helps someone
akosierwin said:
Can't post yet on android development forum so I'm posting this here.
I noticed some people who have recently flashed cm 10.1 have issue with the camera getting stucked for ~10 seconds before flashing and taking pictures when flash is enabled. Some people don't suffer from this issue however.
This is my observation while using the camera as I have also recently flashed cm: When flash is enabled, using the autofocus feature(touching the screen to focus before hitting the capture button) triggers the ~10second hang. Hitting the capture button immediately however without using autofocus doesn't suffer from the same issue.
Hope this helps someone
Click to expand...
Click to collapse
this also is an issue on 20a when using any camera app other than stock, with flash on, just for the information
Got a strange issue here. My camera was working fine on JB (stock rom & also on KnoxRaid 2.6). After the kitkat v2 release of Knoxraid I decided to give it a try. Everything is perfect except whenever I open the camera I get "Warning - Camera Failed". I restored back to mj5 thinking it was maybe a hardware thing but no, the camera works perfectly on stock mj5. So I decided to test Knoxraid 2.6 (non kitkat version) and again, camera work fine. I have asked Drakeymcmb what he thinks about the issue, but I think it has even him stumped. He suggested I try the other kitkat rom leaked by designgears. So again I restored back to mj5 and then tried the designgears leak. No luck, camera failed. I have wiped my internal memory and tried everything I can think of. I am hoping maybe someone has run into this issue and knows a fix?? Please help!! Thanks!
Not having any camera failing, but I'm experiencing a pretty substantial lag after taking a photo.
When i hit the shutter button, my screen will say "Processing". If the camera moves AT ALL before the "processing" is done, the picture will be blurry -it almost looks like I've moved the camera during exposure.
Anyone else having this problem?
AT&T Note 3
I notice that as well. I just turn the smart stabilization off and problem solved. Turn it back on when you wanna take pic in the dim light situation and be prepare to hold the phone still.
mutantblack said:
I notice that as well. I just turn the smart stabilization off and problem solved. Turn it back on when you wanna take pic in the dim light situation and be prepare to hold the phone still.
Click to expand...
Click to collapse
That's a great tip. I'm going to try that.
Thanks!
AT&T Note 3
Were really talking about 2 completely different issues here. I wish my problem was that the camera was too slow, but mine will not load at all...
My camera hasn't been working properly since updating for 5.0.1. Everything's blurry and doesn't seem to focus. I managed to take one photo once after clicking around the focus for 5 minutes, but it was the only time it happened.
I already tried a factory reset and it didn't work. Has anyone else experienced this? Is there a fix or should I try going back to 5.0.0?
Downgrade to 5.0 or even 4.5.1 and check if camera works there. If it does, then it might be that your phone doesn't like this update
Is anyone else running into this issue? The problem started last night, and it happened first on the September update, so I don't think much about it, kinda pissed, sat outside in the cold taking 4 minute pictures that looked awesome just to have them not save to the device. But the problem still persists after updating to the November update.
When I take the picture, I can click the thumb nail immediately after taking the shot, and once the thumb nail pulls up the phone says that it is processing, than just vanishes the photo as if was never taken and pops the previous photo in my camera roll into the thumb nail. This happens with night shots, Astrophotography shots, and selfi night shots. Basically anything using the night shot software is not saving to the phone. I randomly have gotten two photos to save, and I am assuming that is purely luck, as I tried taking at least 100 now while trouble shooting.
Some basic info. I'm on the pixel 4 xl, unlocked (not a carrier device) I'm currently rooted, but had no issues with this last week while being rooted. I have tried clearing the data and force stopping the camera app and also the photos app, and no change. To try everything possible, I even hid root from all Google apps with magisk, and still nothing. My current build is QD1A.190821.014 (TMobile service)
Anyone else having this issue I would be fascinated to hear about it. And of course if you have an idea about how to fix this nonsense that would be awesome. Thanks in advance.
Well figured it out, the November 5th update appears to be the problem.
Down graded to the October 25th release: Google Camera 7.2.011.276470382, andy night shots are now saving to my device.
The November 5th update is one that was giving me issues, it's version: Google Camera 7.2.014.278150624
jasonstackhouse said:
Well figured it out, the November 5th update appears to be the problem.
Down graded to the October 25th release: Google Camera 7.2.011.276470382, andy night shots are now saving to my device.
The November 5th update is one that was giving me issues, it's version: Google Camera 7.2.014.278150624
Click to expand...
Click to collapse
Interesting, my camera version didn't change when I upgraded to the nov security patch. It was and still is 7.2.011.276470382
Just found the new version on APK mirror, gonna install and test it out and see if I have those same issues.
*Just tested every mode, with and without DNG. Everything saves fine for me. I'm not rooted if that matters. Maybe something with magisk is screwing it up.
Well I thought I fixed my issue, but it started back up. I thought maybe it was the kernel I was running so I went back to stock, and for some reason I am having the same issues. So weird, not sure how this could be only happening to me, it's hard to believe that I have a hardware issue.
I had a similar issue once with motion photos. Do this, take a photo that you expect to disappear and view it immediately after you take it, then verify the date is correct in the file name and EXIF data.