Database Develop

Non ROM Specific Camera Issue

I've been scouring the forums in hopes of a fix for my problem (the G1 Q&A and the Android Development forums). In my searches I have found 10-20 people who have had this similar problem, specifically, a force close whenever I (we) attempt to use the camera.
I'm %90 positive this is a software issue. I have had this phone (my 3rd one) for a few months now, and never have I had any issues with the camera, i actually use the video cam fairly often. Anyways...I decided a while back to root and flash Cyanogen's latest ROM, with the latest radio (posted a few days ago) and the Death SPL. Once i completed this, I was met with an instant force close when attempting to use my camera.
I have actually wiped and installed Cyanogen's ROM 2x, (the 2 latest versions), I have also installed KingKlick latest ROM, neither of these, coupled with countless different configurations has solved the problem. I have attached a small snippet of the last log I pulled. Any help or ideas would be greatly appreciated.

I also forgot to mention (and this might be completely wrong), I did restore the 1.5 image from the SPL, rebooted the phone, and the camera still didn't work, it didn't force close, just hung like it was trying to boot. I have also used the latest Super D ROM and I'm experiencing the same issue.

With my minimal knowledge, only one thing in the log jumped out at me, or, should I say I only saw one thing that I understood.
"X: /dev/msm_camera/control0 open failed: No such file or directory!"
Please help, this is a major deal for a number of people, every time it's posted, people just seem to ignore it.

Download Camera Magik from the market. If the problem is software related, then using a different camera app could be the solution. I like camera magik because is takes better pictures at low lights then the stock and the ability to zoom, but you can try any other app. Another suggestion is trying a sense based rom and using HTC camera. GL

I guess I should have said Kernel based as opposed to software based. I tried Camera Magic as well as one other new type of photo software, Camera Magic FC's, the other one opens, but, the camera never turns on.

Do you have any other apps that use camera(i.e barcode scanner, shopsavy)? You may have to uninstall and re-install. Did you wipe in-between roms? Try clearing your rotation settings from recovery, that may sort it out (I know it's a long shot). Other then that, email whoever's rom you're using directly with that log, they may be able to help you a lot faster then any of us regular folks can
Good luck

try a complete super duper wipe.
start from rc29, nonrooted. see if the camera works. if it does, start the root-rom process and check at certain intervals. if it doesnt work when your not rooted and on the stock original firmware, then its gotta be the phone. did it ever work before? i know you said this is your 3rd phone. has it ever worked on this particular phone?

First off, the camera/video has worked on all 3 of my phones, the 1st one had to be replaced because the keyboard went out, and, the 2nd one just kept randomly rebooting, the 3rd hasn't had any problems what so ever until my first root, which was Stock 2 Cyanogen.
So, I went back to RC29 unrooted and experienced a different problem. The camera didn't FC, but, it hung indefinitely at a black screen (kind of a dark grey). Unfortunately, for some reason the system option to force update to cupcake wasn't available, so, after 5hrs of waiting, I went back to root SuperD.

[Q] Any GPS fixes?

I'm really starting to miss the GPS rapid lock from my Thunderbolt. As soon as I'd start maps up that thing would pinpoint me in my bathroom. Since I've gotten this bionic, it won't even lock on me in my house and it's slow to do it even when I'm outside.

If you haven't tried it, TopNTP is a good app to try. It updates/changes the gps to use only addresses in your area to cut down on the fix time*. It's not instant like you referred to on your thunder bolt, but I've found it to help a lot in my case.
I'll come back and post a link if i run into one again.
Link to thread - http://forum.xda-developers.com/showthread.php?t=2198319
*I retract this statement. You can choose servers based on your location, but he advises this is not always best. Some times other servers are faster or more frequently updated for accuracy. He explains/understands better than I.
typed on a Bionic running Eclipse 1.3 on ICS build 232.

I think that helped a little. It locked on in a couple of minutes. The first time I tried it today.

A couple minutes is really slow, I couldn't say mines ever been that bad, unless of course i was in a position where i wasn't going to get a lock at all.
Just curious, what's your bionic running? Stock ICS, JB? Rooted, ROM'd?

chrisp6825 said:
A couple minutes is really slow, I couldn't say mines ever been that bad, unless of course i was in a position where i wasn't going to get a lock at all.
Just curious, what's your bionic running? Stock ICS, JB? Rooted, ROM'd?
Click to expand...
Click to collapse
IT's running the Carbon rom

There's not much else i could help you out with, unfortunately. I'm running the same setup as you, and usually get locks in about 15 seconds or less.
I've seen some people mention a free app called gps status i think. It can time how long it takes to grab a lock, and clear & grab new settings for the gps.
I haven't had a look at it myself, but it may be worth a shot if you get a chance. If i find anything helpful, or for some reason start needing to fix mine at some point, I'll pop back in
typed on my Bionic

Might have fixed itself. When I was in Rockford with my parents I uninstalled maps and reinstalled, next thing I know it was locking on instantly.

SuperSquirrel0129 said:
Might have fixed itself. When I was in Rockford with my parents I uninstalled maps and reinstalled, next thing I know it was locking on instantly.
Click to expand...
Click to collapse
If you run into this again, I'd recommend a couple troubleshooting tips.
1) Boot to recovery, wipe cache, wipe dalvik cache, fix permissions. Reboot.
If the issue persists
2) Force close Maps and wipe it's cache and data. You'll have to re-configure Maps as you like.
3) Download GPS Status & Toolbox. Download the GPS data in here before opening Maps or Navigation. This should get you quicker GPS fixes. It's free in the market btw.

I'm having trouble getting my gps to work on cm10.1, I restored a previous backup of 10.1.2 and it didn't work. I've dirty flashed, wiped everything and reflashed, cleared the cache & dalvik, gps status clear, rebooted to stock and it worked, and the gps worked before I installed the backup. Running the latest nightly. Any ideas?
Sent from my XT875 using Tapatalk 2

jethead102 said:
I'm having trouble getting my gps to work on cm10.1, I restored a previous backup of 10.1.2 and it didn't work. I've dirty flashed, wiped everything and reflashed, cleared the cache & dalvik, gps status clear, rebooted to stock and it worked, and the gps worked before I installed the backup. Running the latest nightly. Any ideas?
Click to expand...
Click to collapse
I had a similar problem I posted under CM10.1 ROM topic. What I ended up doing is I boot back to stock (Icarus, actually) and ran GPS Test app. Confirm the baby worked. Went Safestrapped booted back to CM10.1 (slot 1) and ran the same app and this time it worked. It's almost as if there's something "stuck" in the hardware despite using a different ROM.
I just say the lockon was quite a bit slower in the Bionic. My old Droid (original) locks on in about 15 seconds. Bionic under stock ROM locks on in 35-39 seconds, and CM10.1 locks in 43 seconds.
I'll try the recommended app and see if that helps.

Problem is intermittent. I tried that recommended top BTM app and did not see any noticeable changes I reverted back to factory and there are no changes noticeable either. The phone just sometimes refuse to see any satellites the GPS test app shows 0 satellites. If I reboot the phone the GPS make sure a few satellites brawl with low signal and it takes about 2 minutes to get a fix. This did not seems to happen under Ice Cream Sandwich.
Sent from my XT875 using Tapatalk 4

[Q] Camera not working on sense but will with CM

So about a week ago my camera out of no where stopped working on my completely stock Sprint HTC One. Every time I opened either the stock HTC camera app or Google camera app it would immediately crash. I did all the usual stuff, cleared cache, data, factory reset, still nothing. Any app that would connect to the camera i.e. Qr scanner would say cant connect to camera. So I thought what better time to root the phone and hopefully fix the problem.
A couple days ago I rooted and S-off'd the phone and long story short ran into some problems and the only rom I could get to run was cyanogenmod (the most current) While I was using cyan to figure what was going on I noticed my camera worked again and took pictures. so I was happy to know it wasn't a hardware problem.
After I figured out my issues I installed Viperone rom and to my surprise when I opened the camera it still didnt work along with anything else that connects to the camera. I thought maybe if I flashed the camera APK from cyan it would work but no beans. Has anyone else had this problem, and possibly found a fix. It seems to be a sense thing but who knows I'm not an expert. Any help would be great THanks

Nothing? I would really love to try to fix this with some help from you guys.

[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.

Question S21 Ultra started to lag and stutter since yesterday out of NOWHERE!! tried everything but still there?

hey so my s21 ultra which was working normal until yesterday started to lag out of nowhere ... the only thing that i did different in these 2days was gaming with my new clip on xbox controller and testing different games ,
I didn't install anything new EXCEPT that octopus key mapper and then Mantis gamepad pro but i didn't really set them up EXCEPT i just tried connecting my s21 ultra to my note 8 via usb c just to test if it worked but then note 8 ran out of battery like crazy...
It just looks like that app did it but i uninstalled all of them but still it is there...
any help? i don't want to reset anything !

Clear system cache.
Try in safe mode.
See which system apps are the most active, delete their data.
A user hidden setting may have been altered by a poorly written app, a possible rootkit etc or a hardware failure.
Factory reset if you can't find it soon.

does it lag in safe mode?
submit an error report on samsung members app > + button > error report if you think it's a software issue

karandevilocs said:
i don't want to reset anything !
Click to expand...
Click to collapse
That last line will make things difficult.
That would be the most foolproof software solution for a non rooted phone IMO. If you reconsider, I'd suggest a full hard reset.

enigmaamit said:
That last line will make things difficult.
That would be the most foolproof software solution for a non rooted phone IMO. If you reconsider, I'd suggest a full hard reset.
Click to expand...
Click to collapse
Hard reboot or factory reset?
A hard reboot is fine. However a hardware issue may be present if this is needed.
Factory reset; it's always preferable to find and correct the root cause rather than doing a factory reset as the issue is likely to reoccur.
Exceptions; unremovable malware, rootkits, major firmware updates, old loads and altered hidden user settings.

I have the same problem, some video on gallery or YouTube, system crash, dji mini 2 app...no display, some apps crashes, android auto heating up the phone....

lambik333 said:
I have the same problem, some video on gallery or YouTube, system crash, dji mini 2 app...no display, some apps crashes, android auto heating up the phone....
Click to expand...
Click to collapse
Backup all critical data now.
Find the cause before it boot loops you.
These are typically the only warnings, if any, before a boot loop. This is not normal behavior.
See which apps are using the most battery, try force stopping them, clear their data, disable them temporarily if possible.
Disable any power management!!!
If using a 3rd party launcher or power management, disable it!!!
Try in safe mode.
Take all factory installed apks especially system apks back to their factory load versions.
Turn off all cloud apps including Google backup Transport for now. Turn off Google Firebase.
Turn off all Google, Samsung, and carrier feedback.
Try temporarily disabling Google play Services, clear it's data.
Reset network settings.
Clear system cache.
Try a hard reboot.

Post Nine said:
does it lag in safe mode?
Click to expand...
Click to collapse
enigmaamit said:
That last line will make things difficult.
Click to expand...
Click to collapse
lambik333 said:
I have the same problem
Click to expand...
Click to collapse
blackhawk said:
Backup all critical data now.
Click to expand...
Click to collapse
so i fixed it after going to safe mode and realizing that it was not the system apps, then i reinstalled that mantis app and uninstall it again to make sure if it was stuck or not also there was this app called : NET SPEED INDICATOR that was updated recently and was flagged as crashed in device monitor so i uninstalled it too and boom, the device was normal again.
so happy that it was a software issue rather than hardware or malware one since i keep close control of what i install and not and monitor everything it was surprising to see such things in my phone, after years of Samsung phone usage it was really shocking to see such behaviors on my s21 ultra with freezing and crashing non stop.
thanks for the help guys!