Database Develop

[Q] camera issues

I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!

Um...I don't think you even explain you problem. Might want to elaborate a bit.
Sent from my Nexus 6 using XDA Free mobile app

No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.

Andddddddd it stopped working again. Super legit.

Might be similar to my issue.
My camera started only showing front facing..even the option for back facing wasn't there. Did wipes in recovery and app settings. Would work, it seemed, but would revert right back to not working. At one point the camera app wasn't appearing in the app drawer at all even though it was shown in "all apps".
This occurred on stock and custom ROMs. I was advised to try flashing factory IMG but I'm well within the warranty period ( phone less than 2weeks) so I'm locking it back up and have a replacement on the way from ATT...
* I also noticed the issue starting while I was on bliss ROM 1.7
Sent from my Nexus 6 using XDA Free mobile app

My camera is really shaky and won't focus correctly in landscape mode. I returned the first phone I had for basically the same thing because it wasn't focusing in portrait mode but looked fine in landscape. I haven't seen anyone else have this issue. At first I thought the camera was inconsistent but if you zoom in you can see that it doesn't focus properly.

I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.

you better do it before its too late. id rma it.

cellularticulate said:
No matter what ROM I use, no matter what camera I try to install, I cannot get it to consistently work. More often than not, cannot connect to camera. I feel like its a setting or file sticking on the "SD card" that is interfering. I also cannot use the flashlight toggle, and parts of Google+ and gallery crash at times. This has been intermittently occurring since my first flash. Blissful ROM v1.7 twrp 2.8.4.0
Tried every wipe except for the one that makes me type yes. I've already flashed boot.IMG to disable decryption, and I'm starting to think that may have something to do with it.
I was under the impression I had twrp 2.8.4.0, but after double checking, it looks like it was stuck on 2.8.2.1. I flashed the newer version from twrp manager, and now my camera is working. I didn't do anything other than install the new recovery. And yes I've tried rebooting my phone in the past. This may be a temporary fix, but I'll report back tomorrow on whether it is still working. This is very odd.
Click to expand...
Click to collapse
There is no sdcard.
Try going back to factory sysimage, and data wipe.
Are you using any "added in" camera software? If so, what?

cellularticulate said:
I'm starting to wonder why there are so many people experiencing the same or similar camera issues. The only reason I'm starting to think that it is software based and not entirely hardware based is because I was having this same issue (cannot connect to camera) on my sgs5 with cm based Roms.
I'm not saying any of this makes sense, its just strange. I wish we could help troubleshoot what the root of this problem is instead of just RMAing the device. I'm afraid to RMA with T-Mobile.
Click to expand...
Click to collapse
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.

I have only had issues with the stock camera app. Ive been running Pure Shamu for 2.5 weeks now and only using the Google Camera app from the play store (the one with HDR+ and the icon has the lens filled with rainbow colors) with absolutely no issues and only getting excellent quality pictures.

Had the issue where the camera wouldn't focus and everything on the screen gets jiggly and wavy like there's some sort of interference. I had motion sickness looking at the screen. Called Moto for an advance replacement and after a week of delay due to stock issue...somehow they were kind enough to upgrade me to a CW 64gb model. I hope it's new and no more camera issues.

Has everyone who got the 'no-focuse OIS' issue gotten new phone on RMA?
I took mine to repair few days ago and they said that they won't give me a new phone instantly, rather they try to fix the OIS. Not sure how that is going to work..?
They also suggested that this issue might be "self inflicted" or just an "feature" of the camera itself. fml.

Giants2010 said:
Similar issue. Get errors "Unfortunately, camera has stopped" or "cannot connect to camera." I picked up the phone right before a 2 week vacation so unfortunately I can't bring back to AT&T. Hopefully Moto plays nice. Problems originally occurred on stock 5.0 before the 5.0.1 update. Since AT&T was lagging on OTA, I flashed to the official BlissPop rom but I have the same problems. Sometimes it'll work like it's supposed to for a couple days but always reverts back to the errors. Nothing like being at the top of a mountain in Hawaii and "cannot connect to camera" right????Since I've read about this happening on so many different firmware variations, I have to believe it's a hardware issue.
Click to expand...
Click to collapse
I returned mine to stock, unroot/locked boot loader, factory reset, before shipping it off and the camera issue was still there. Maybe hardware related I'm thinking.
Sent from my Nexus 6 using XDA Free mobile app

Something rather peculiar Ive noticed...
I didn't really pinpoint this until today, but the camera very consistently starts working when you go into fastboot, load the recovery, and then boot into system. I'm really, sincerely not quite sure why this would be happening, but I still feel like it has something to do with boot.IMG
If any devs can point me in the right direction to try and track down the possibility of this being an issue, I'd love to potentially fix a bunch of people's camera issues (albeit there is probably also a hardware defect direct from moto).
Is logcat going to pick up on issues that originate from boot?

cellularticulate said:
I've tried browsing the forums, and even locating the post talking about the fix for the camera, and I simply can't find it. I really don't want to go without a phone seeing as my job requires my phone, but it really sucks not having a camera or a flashlight toggle.
I've seen some people that have indicated its a physical issue, however, it sporadically starts working again. Note: I would like to avoid doing the super data wipe as I'm also having computer issues at the same time. If someone needs me to post a catalog, I will need help Learning what to filter out in order to upload only the necessary info.
I've tried wiping the data through twrp advanced wipe, and of course the dalvik cache has been wiped many-a-time. Any help would be appreciated!
Click to expand...
Click to collapse
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298

rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.

cellularticulate said:
Not the issue I'm explaining though. This is a bit more deeply seeded of an issue. When I boot directly into the ROM, my twrp installer says I'm back on 2.8.2.1, but when I boot into fastboot and then twrp, and then ROM, it says 2.8.4.0 and my camera works. This is legitimately weird as ****.
Click to expand...
Click to collapse
Ohhh man that is weird.

rdizzle707 said:
This is a hardware issue. Check http://forum.xda-developers.com/nexus-6/help/camera-lens-movement-t2984298
Click to expand...
Click to collapse
rdizzle707 said:
Ohhh man that is weird.
Click to expand...
Click to collapse
It appears a bit more stable now. I tried flashing twrp from my computer and it seems to be a bit more nice. That and normal reboot to twrp doesn't say 2.8.2.1 - let me check twrp manager now.
And my camera and flashlight have worked for almost three days now. Dafuq.

Same issue. "Unfortunately, Camera has stopped."
No flash light available, only front camera working, clicking on HDR exits the app with the aforementioned error message.
Has anyone solved this issue?
I was on 5.1 stock (with root) and now I've updated to 5.1.1, but with no change to the Camera behaviour.

Rotation bug with EVERY available rom!

Hi guys,
Whatever rom I install on my xiaomi mi5, after a certain time, the screen rotation does not work anymore.
To prevent software errors I run always by a clean flash.
In many forums write user that this bug after the update to a specific version Miui disappears.
This is not a' solution for me.
Has anyone else this problem?
Perhaps it is also a hardware defect...

dont think its a software problem, maybe you should get your phone checked out

njuz said:
Hi guys,
Whatever rom I install on my xiaomi mi5, after a certain time, the screen rotation does not work anymore.
To prevent software errors I run always by a clean flash.
In many forums write user that this bug after the update to a specific version Miui disappears.
This is not a' solution for me.
Has anyone else this problem?
Perhaps it is also a hardware defect...
Click to expand...
Click to collapse
Its of course a well know bug for all mi5 roms. I read yesterday that last thursday rom update fix this:
"Fix - Accelerometer and gyroscope didn't work after and OTA update (08-12)
Fix - Accelerometer and gyroscope didn't work normally (08-12)"

The problem occured with miui as well as with unofficial CM build, what i am using now. This indicates to me that it has nothing to do with the installed rom directly.
After rebooting, everything works fine again.
I suspect apps like Pokémon go to stay in relation to the bug. Since i am not playing that game anymore it occures much rarer...

I am too having this problem with no solution, i guess its not an hardware issue, otherwise dozens of people like us have an defective hardware on their mi 5. I tried MIUI 7.5.2.0 and 8.0.2.0, both global stable, occurs when i play pokemon go for a while, then i go back to any app and the screen does not rotate anymore.
I wonder if it is related to the kernel, since we dont have the kernel sources, all the roms available are based on the kernel miui have, so... Any help would be apreciated.

I was having the same problem. I dont play pokemon. Im still on vendor rom. But now the bug gone i tried to simulate the bug but it rotate normally

I have this issue. I'm on the latest CM 13 build and I get issues where the camera won't take in landscape and full screen videos won't switch to landscape when you rotate the phone. It's so nearly perfect apart from that.

shucrut said:
I am too having this problem with no solution, i guess its not an hardware issue, otherwise dozens of people like us have an defective hardware on their mi 5. I tried MIUI 7.5.2.0 and 8.0.2.0, both global stable, occurs when i play pokemon go for a while, then i go back to any app and the screen does not rotate anymore.
I wonder if it is related to the kernel, since we dont have the kernel sources, all the roms available are based on the kernel miui have, so... Any help would be apreciated.
Click to expand...
Click to collapse
Did you ever fix this bug as a matter of interest? I've just done a full-wipe reset and reinstall of the latest CM13 build and I still have auto-rotate issues. It's really annoying me now because it's a great build in all other respects.

I installed a couple of Sensor Test apps and neither one can see my accelerometer sensor to even test it. So it's like the sensor isn't even there. I know it works because one of Shade.sh's beta CM 13 builds was able to detect the sensor OK! Any ideas?

Here's the sensors detected in the Check My Android app. There seems to be only two axis detectors working. How does this compare to a healthy Mi 5?

sharkyblunt said:
Did you ever fix this bug as a matter of interest? I've just done a full-wipe reset and reinstall of the latest CM13 build and I still have auto-rotate issues. It's really annoying me now because it's a great build in all other respects.
Click to expand...
Click to collapse
Yes, i actualy did. After installing developer version 6.9.18 the problem never appeared again. Now im on 6.9.22 and the rotation bug is gone

Hmm, I've just tried SlimRom and the same bug is present, presumably because it's derived from the same tree as CM 13.
I'm actually tempted to give MIUI 6.9.22 a go then if it's the only way to get this fixed.

I have just flashed the MIUI developer ROM 6.9.2.2 and my sensors are working perfectly now. So it must be something for flaky in the CM stack or Kernel version. See screenshot.

RP2-specific fixes/updates with 9.0 update?

To those who have updated to Android 9.0, have you seen any improvements/fixes specific to the RP2? I know many of us have noted issues with the speakers (notably at lower volumes) and the camera software (mostly fixed by using Gcam), although there's been other more isolated/random issues for some too (Bluetooth, cellular signal, etc).

I haven't done extensive testing, but I do nelieve the small issues I've had with the speakers at low volumes are fixed. The only issue that I've seen in the last couple days I've had pie is that my wifi will randomly stop being able to access the internet, but turning wifi off and on fixes it and mostly a minor inconvienence. It's probably worth noting that I have Magisk with many modules installed.

Hangouts doesn't give a notification sound when the app isn't open. I've made another thread about that earlier
------------------------------------------------------------------------------
Never mind. Had to go deep into Hangouts settings to fix it. Still annoying

I would willingly trade fully functional wifi for speakers that don't crackle and cut out at lower volumes, since I have unlimited data and solid LTE signal everywhere I go. Though I've had that wifi issue on rare occasion on Oreo too.

They moved the clock :'(

Anyone notice potential decrease in touch sensitivity after the upgrade? I had a screen protector on and it seemed like I need to push down a little more to get the touches to register. Took off the protector to test and it was fine with just the screen. Put another one on and occasionally touches aren't registering or registering but releasing early on swipes.
Sent from my Phone 2 using Tapatalk

CalebQ42 said:
I haven't done extensive testing, but I do nelieve the small issues I've had with the speakers at low volumes are fixed. The only issue that I've seen in the last couple days I've had pie is that my wifi will randomly stop being able to access the internet, but turning wifi off and on fixes it and mostly a minor inconvienence. It's probably worth noting that I have Magisk with many modules installed.
Click to expand...
Click to collapse
How do you unlock your bootloader, bro? How did you root your phone?

acegrace said:
How do you unlock your bootloader, bro? How did you root your phone?
Click to expand...
Click to collapse
Follow the guide here, it's what I used to get everything under way. As long as you didn't install the latest OTA that dropped last week.
https://forum.xda-developers.com/razer-phone-2/how-to/root-pie-guide-t3910407

Gamesoul Master said:
Follow the guide here, it's what I used to get everything under way. As long as you didn't install the latest OTA that dropped last week.
https://forum.xda-developers.com/razer-phone-2/how-to/root-pie-guide-t3910407
Click to expand...
Click to collapse
crap, i just updated last night - can i factory reset and do the same thing?

alawiggle said:
crap, i just updated last night - can i factory reset and do the same thing?
Click to expand...
Click to collapse
Nah, you're good now. Warrior's thread (which the post I gave you directly references) has the updated boot image for MR1 (which is what you're on now), so just use that and you should be fine.
Oh! And turn off any unlock security (PIN, fingerprint, etc) you may have on before doing it. Just to be safe. You can turn it all back on when you're done rooting.

Gamesoul Master said:
Nah, you're good now. Warrior's thread (which the post I gave you directly references) has the updated boot image for MR1 (which is what you're on now), so just use that and you should be fine.
Oh! And turn off any unlock security (PIN, fingerprint, etc) you may have on before doing it. Just to be safe. You can turn it all back on when you're done rooting.
Click to expand...
Click to collapse
nice, thanks!

Randomly Unresponsive Screen After The Pie Update

I have an Motorola G6 Play XT1922-3 and after the Pie update the screen becomes randomly unresponsive, every 3-5 minutes or so. Locking and unlocking the phone fixes the issue but it's really annoying, especially if you have some kind of security on the lock screen; also I don't think is a hardware issue since only this method works, nothing 'physical' works (like slaps, bumps, etc. :laugh: ).
Do you know some kind of fixes for this?

When my Moto G6 got the first Pie update it was laggy. All over the place random laggy. The fix that was suggested (and it worked) was to reflash the phone with the RSD lite tool and the same OTA rom from https://mirrors.lolinet.com/firmware/moto/ali/official/RETUS/. Note make sure you grab the correct rom from https://mirrors.lolinet.com/firmware/moto/ and the correct channel for you specific device.
-Chris

I've been struggling with the same issues as the first poster - random screen freeze until the phone is locked and unlocked which I also think is some sort of software issue since updating to Pie. Has anyone managed to find a fix for this at all?

richtee74 said:
I've been struggling with the same issues as the first poster - random screen freeze until the phone is locked and unlocked which I also think is some sort of software issue since updating to Pie. Has anyone managed to find a fix for this at all?
Click to expand...
Click to collapse
A friend of mine had his G6 lagging a lot, factory reset did the trick for him.
I and currently using Descendant 3, but in my experience it has other issues, so, I would suggest the factory reset, or rooting stock Pie, if you are into that sort of thing.

Notification Bar, Home, Recent buttons disappear occasionally since Android 12

Since upgrading my Samsung S10e OTA, the Home and Recent App buttons disappear, and also I can't swipe the Notification pane down. The only fix seems to be a restart. The problem happens reliably after charging for a while, and occasionally during normal use as well.
I have tried wiping the cache and pretty much every other setting I can think of. Any idea how to fix this so that I at least don't have to reboot!?

any ideas anyone?

I am wondering if your launcher/home app is crashing? I think that even if you use a third-party launcher (eg, I use Nova) these buttons are still handled by Samsung's launcher/home app? If that is sleeping or crashing, it may be why these are disappearing? That would be my only guess at the moment.
On older phones, when this kind of thing happened, I would put a launcher icon on the screen, so I could relaunch it. But I don't see an icon available for the OneUIHome app on my phone... but if you can find some way to get that it may allow you to restart it, and test this theory?

schwinn8 said:
I am wondering if your launcher/home app is crashing? I think that even if you use a third-party launcher (eg, I use Nova) these buttons are still handled by Samsung's launcher/home app? If that is sleeping or crashing, it may be why these are disappearing? That would be my only guess at the moment.
On older phones, when this kind of thing happened, I would put a launcher icon on the screen, so I could relaunch it. But I don't see an icon available for the OneUIHome app on my phone... but if you can find some way to get that it may allow you to restart it, and test this theory?
Click to expand...
Click to collapse
I am not using a 3rd party launcher. However I have tried using Nova (free) and it seems to have the same problem.
I have also installed Assistive Touch that puts a little floating button on the top that acts as home/last used/notification panel. Only the Home function works however so I still can't access the notification panel.
I really don't want to do a factory reset! Maybe the next update will fix it but this phone is quite old now so I don't know how many updates are yet to come....

Sorry, I don't have any other ideas. I have heard of people having issues with A12 in general, but not this one particularly. That said, if you do a FDR then you may consider going back to A11 and seeing if that resolves it. The FDR might do it as well, but you can't go back to A11 from A12, so you could do that and see how it fares... then do the A12 update (without FDR) and see if it comes back - in which case you'd know it's something to do with A12 on your phone...?
Sorry I don't have better ideas!

Thanks - do you know if there are any large updates in the pipeline after the update to A12? I ask since I had this problem when I first bought the phone and I think it went with the next large update. Back then (2 years ago or more) I could fix the problem without restarting by clearing the cache in Android settings which somehow got the buttons & notification pane back. Unfort there isn't an option to clear the cache in A12 (I have tried doing it in recovery which made no difference).

That's weird... I don't believe we can expect A13... so the only thing I'd expect is continued security updates...
I have avoided A12 because of the many issues I read about on the forums and elsewhere. I have no issues with the phone today, so I figure why bother, you know?

I've actually never encountered this behaviour, strange. Mine have a bright line on the bottom part of the screen and sometimes it shines more then other. But that's purely hw issue not software.
Regarding updates, Samsung is updating now with May 22 security patches, I heard they moved us to 3months cycle of updates, but seems they still comes out monthly. That's cool!

kayuz said:
I've actually never encountered this behaviour, strange. Mine have a bright line on the bottom part of the screen and sometimes it shines more then other. But that's purely hw issue not software.
Regarding updates, Samsung is updating now with May 22 security patches, I heard they moved us to 3months cycle of updates, but seems they still comes out monthly. That's cool!
Click to expand...
Click to collapse
There are one or quite old posts about the same problem, and the suggested fix is to enter the following in ADB
adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity
But on my S10e there is no SetupWizardTestActivity option available when I go into ADB.
Any idea?

drb01 said:
There are one or quite old posts about the same problem, and the suggested fix is to enter the following in ADB
adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity
But on my S10e there is no SetupWizardTestActivity option available when I go into ADB.
Any idea?
Click to expand...
Click to collapse
Any ideas anyone? The problem seems if anything worse since the last OTA update from Samsung !

Have you tried a different launcher app? Is the OneUI app being killed by something? I would think it should be eliminated from battery optimization in the stock ROM by default, but make sure it is. Beyond that, if you're using any battery-saving apps that could be killing it?

schwinn8 said:
Have you tried a different launcher app? Is the OneUI app being killed by something? I would think it should be eliminated from battery optimization in the stock ROM by default, but make sure it is. Beyond that, if you're using any battery-saving apps that could be killing it?
Click to expand...
Click to collapse
The OneUI Home app was "Optmised". I changed it to Unrestricted which made no difference.
In a previous version of Android when I had this same problem I could just clear the app cache in Settings and the buttons would reappear. There doesn't seem to be a way to do this in Android 12. I have tried wiping cache in recovery which made no difference.

Do you have other battery optimization apps installed? Greenify, etc? These may be killing it as well.
You can still wipe cache in Android 12: https://mobileinternist.com/clear-cache-android
If you had a workaround in A11, I might suggest going back to that - you should be able to (for a while, at least... once the BL changes you won't be able to).

schwinn8 said:
Do you have other battery optimization apps installed? Greenify, etc? These may be killing it as well.
You can still wipe cache in Android 12: https://mobileinternist.com/clear-cache-android
If you had a workaround in A11, I might suggest going back to that - you should be able to (for a while, at least... once the BL changes you won't be able to).
Click to expand...
Click to collapse
V happy to go back to a11, but Is there a way to go back to a11 without doing a factory reset?
And excuse my ignorance but what is BL?

No, you can't go backwards without resetting.
BL = Bootloader. Samsung has been updating this and if you're on a later version, you cannot backtrack it (at least not on a Snapdragon phone). I realize now that I'm not sure which phone you have, so if you're on Exynos then the situation could be different.
As long as the A11 you're flashing has the same BL version as the one you have now, you can flash backwards that way. 5th digit from the end of the version number (eg G970U1UEU6IVD2) tells you the BL version. You'll need to get an A11 with the same version there, and it should be doable.
What's your full version number?

schwinn8 said:
No, you can't go backwards without resetting.
BL = Bootloader. Samsung has been updating this and if you're on a later version, you cannot backtrack it (at least not on a Snapdragon phone). I realize now that I'm not sure which phone you have, so if you're on Exynos then the situation could be different.
As long as the A11 you're flashing has the same BL version as the one you have now, you can flash backwards that way. 5th digit from the end of the version number (eg G970U1UEU6IVD2) tells you the BL version. You'll need to get an A11 with the same version there, and it should be doable.
What's your full version number?
Click to expand...
Click to collapse
The full build version is SP1A.210812.016.G970FXXUFHVE1.
If there is a way to go back to a11 without doing a reset I'd love to know! Or of course just any way to fix this problem ..

Sorry, I should have chased this down first - you have an Exynos phone, so you may have other options. You'll need to re-post and say you have an Exynos phone, and ask people about this again... maybe others who are more familiar with Exynos can chime in. Sorry for wasting your time with my Snapdragon-related info.
In the future, it's important to mention you have an Exynos phone... or say you have a G970F... the "F" means the same thing.