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.
Related
Hey Guys,
Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.
Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.
There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.
I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.
So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.
Thanks in advance.....
Reserved for future use
My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.
Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,
http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/
Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.
Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,
http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en
I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.
Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
wesbalmer said:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
Click to expand...
Click to collapse
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.
I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.
I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.
Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.
After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.
I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).
50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.
The only way to get a cell signal back is rebooting the phone.
Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.
I have the problem, too.
Just a few notes:
didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2
This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.
Seems to be a kernel panic.
I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).
I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.
So, here's my current suspection (I'm not at all sure if that's true!):
The reboot loop only happens when the system runs out of memory.
In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.
I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).
This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic
Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).
So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.
If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. ES Task Manager can show that information, though, for example.)
Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …
Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.
Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)
The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!
Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.
Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?
Maybe we can start by trying to find out what we all have in common?
I have an AT&T/Rogers version of the N1.
I typically have the Facebook, Calendar Widgets on home screen.
Power Widget on 2nd screen
Use gmail but via the standard email client, not the gmail client.
Use the native alarm clock app in the dock at night
16GB ADATA MicroSD card.
I also install:
- ChompSMS (with icon widget on home screen)
- NewsRob (with Widget on home screen)
Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.
While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.
I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.
Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.
The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.
I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.
http://forum.xda-developers.com/showthread.php?t=703508
I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.
I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
cmarti said:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
Click to expand...
Click to collapse
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
DvTonder said:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
Click to expand...
Click to collapse
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
MSigler said:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
Click to expand...
Click to collapse
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
DvTonder said:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.
Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
Click to expand...
Click to collapse
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.
I have this on stock 2.1u1 EPE54B
I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:
1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.
2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
tjsimmons said:
I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
Click to expand...
Click to collapse
Did you flash the Froyo version with SP3?
I've had this major problem for like a year now. Basically most third party camera apps just freeze after taking image. The program itself won't freeze but the part where you see the image. I can still use the cameras UI and if I go to some menu and come back, camera starts working again. I also found out that this doesn't occur in GB roms at all, only ics and newer. I asked from a Finnish tech forum about this issue and many people with same custom rom and phone didn't have this issue at all. I have installed over 30 roms and every time done full wipe so it shouldn't be the problem.
This hasn't been huge problem until now, because I've been satisfied enough with AOSP camera, but now with coming of CM10.2 roms I really would like to use new Focal app, but I can't because of this issue.
Is there any fix for this?
Khallerz said:
I've had this major problem for like a year now. Basically most third party camera apps just freeze after taking image. The program itself won't freeze but the part where you see the image. I can still use the cameras UI and if I go to some menu and come back, camera starts working again. I also found out that this doesn't occur in GB roms at all, only ics and newer. I asked from a Finnish tech forum about this issue and many people with same custom rom and phone didn't have this issue at all. I have installed over 30 roms and every time done full wipe so it shouldn't be the problem.
This hasn't been huge problem until now, because I've been satisfied enough with AOSP camera, but now with coming of CM10.2 roms I really would like to use new Focal app, but I can't because of this issue.
Is there any fix for this?
Click to expand...
Click to collapse
if you want stable camera you need to switch back to stock. :crying:
No solution jet for 4.0 and above.
Focal is acutally in an buggy state, so it will take a little time before we can use it ...
Khallerz said:
I've had this major problem for like a year now. Basically most third party camera apps just freeze after taking image. The program itself won't freeze but the part where you see the image. I can still use the cameras UI and if I go to some menu and come back, camera starts working again. I also found out that this doesn't occur in GB roms at all, only ics and newer. I asked from a Finnish tech forum about this issue and many people with same custom rom and phone didn't have this issue at all. I have installed over 30 roms and every time done full wipe so it shouldn't be the problem.
This hasn't been huge problem until now, because I've been satisfied enough with AOSP camera, but now with coming of CM10.2 roms I really would like to use new Focal app, but I can't because of this issue.
Is there any fix for this?
Click to expand...
Click to collapse
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.
I'm using a Z3 compact with CM12.1, that means unlocked bootloader and no more warranty. All of sudden, the main/back camera has stopped working. It is black, OSD still working, front camera still working, other camera apps don't make a difference.
I don't know if that is a problem of some recent CM nightly or something else. Browsing the web I get the idea that this symptom also appears on stock firmware, and it seems that nobody has yet found a solution (neither factory reset nor hardware replacement of camera help).
My question:
Has somebody else this problem, is it CM related?
Is there a solution other than complete phone replacement?
Is there some logfile I might consult to find out if the camera HW should be replaced? I don't want to disassemble the phone only to find out that the camera still does not work.
Thanks!
Must be a software problem related to the nightlies unstableness.
Try flashing a stock firmware to see if it gets fixed.
I'd rather avoid going back to stock. Reverting to a previous CM nightly (from a time when the camera definitely worked) did not help.
Do you have any reports of CM nightlies problems with the camera? I'd love to hear that, because it would mean that I don't have hardware problems. However, searching the web I only found many reports of the camera suddenly stopping to work, but nothing that this is related with recent CM nightlies.
But if it's a Hardware problem, there should be a logfile somewhere, or?
just did trial and error on the same problem with the black camera for 2h
i did however not install CM to cause this
I have a custom debloated rom, which worked fine.
I had to switch phones so i did a TW recovery backup.
Changed the filename on the new phone so it is found when restoring.
Restored. Everything works well, except the camera app.
When i wipe from the systems menu i lose all my data but the camera app works again.
But of course i need my data exactly the way i had it backed up.
Tried all kinds of things around the camera app, backing and restoring with and without kernel, always the same.
Back camera stays black.
This is similar to other reports I found in the web: The hardware works (which means replacing the sensor is of no use), but somehow it is no longer accessible. I tried different hw info apps, which all report the back camera with all specs and no problems, but no camera app is able to get it to work. I flashed several new CM nigthlies since, it doesn't help
I don't really know how to read logs (with 3CToolbox), however this line caught my attention. Maybe somebody here can interpret it:
07:45:48.427 caladbolg( 301)
9530027 cald_parammgr_generic.c (4299) 301 E [PRM] Fail: camera eeprom status
Since my Kernel debugging skills are also not existent i simply factory reset it and transferred my data with titanium backup.
Everything works fine now.
So my advise is to stop wasting your time with it too, just go back to working software
Unfortunately reverting to stock firmware did not repair my camera. Afraid I have some hardware defect
No resolution to this problem it seems
I have a N6 purchased Dec 2015 new from Amazon. The only mods, if you can call it that is, I have unlocked the boot loader. I am currently running N6F26Y sideloaded via ADB.
The phone was great when I first got it but now after about a day or so of usage it becomes slow and sluggish and unresponsive I have to restart it to use it. I have done a factory reset a couple of times which gets it back to normal for a week or so and then the problem recurs. Occasionally I will delete the cache which also helps. Snapchat is one of the worse apps - crashes the phone regularly and is a very slow app.
Also the camera can get very slow often taking seconds to take one photo.
I love the phone but it's becoming unusable now. The contrast between this and a new phone (I have purchased a Moto Z) is like night and day. The Moto Z runs instantly, has no lag and is a nice phone. But what I like about the N6 is the large screen which makes it great for videos etc.
Short of perhaps flashing some custom ROM is there anything I could be doing?
I'd recommend flashing a rom like pure nexus, super stable that should fix your problem, otherwise you've done all you can and is the easiest fix
Sent from my Nexus 6 using Tapatalk
lchiu7 said:
I have a N6 purchased Dec 2015 new from Amazon. The only mods, if you can call it that is, I have unlocked the boot loader. I am currently running N6F26Y sideloaded via ADB.
The phone was great when I first got it but now after about a day or so of usage it becomes slow and sluggish and unresponsive I have to restart it to use it. I have done a factory reset a couple of times which gets it back to normal for a week or so and then the problem recurs. Occasionally I will delete the cache which also helps. Snapchat is one of the worse apps - crashes the phone regularly and is a very slow app.
Also the camera can get very slow often taking seconds to take one photo.
I love the phone but it's becoming unusable now. The contrast between this and a new phone (I have purchased a Moto Z) is like night and day. The Moto Z runs instantly, has no lag and is a nice phone. But what I like about the N6 is the large screen which makes it great for videos etc.
Short of perhaps flashing some custom ROM is there anything I could be doing?
Click to expand...
Click to collapse
Hello,
It seems like some apps are really slowing down your phone. I use my N6 at home for web browsing mostly as I have a Pixel XL now. Just like you I love the screen size.
The camera has always been slow fore, because of the time it takes to focus...
Did you try using your phone a few days without Snapchat installed? Maybe you also have other misbehaving apps installed.
Uninstall Snapchat and other apps and start from here. Reinstall one per one with a few days interval. See if the issue still occurs.
Installing a custom ROM + kernel will likely speed up things a little bit. I second @Dugaldrob with Pure Nexus and I'd suggest ElementalX kernel on top. Running this combo on N6, N6P and Pixel XL and they work flawlessly.
I don't believe installing a custom ROM alone will fix your issue though. Stock ROM shouldn't cause the phone to slow down to the point you need to reboot to use it.
Finding the culprit will...
Good luck...
5.1 said:
Hello,
It seems like some apps are really slowing down your phone. I use my N6 at home for web browsing mostly as I have a Pixel XL now. Just like you I love the screen size.
The camera has always been slow fore, because of the time it takes to focus...
Did you try using your phone a few days without Snapchat installed? Maybe you also have other misbehaving apps installed.
Uninstall Snapchat and other apps and start from here. Reinstall one per one with a few days interval. See if the issue still occurs.
Installing a custom ROM + kernel will likely speed up things a little bit. I second @Dugaldrob with Pure Nexus and I'd suggest ElementalX kernel on top. Running this combo on N6, N6P and Pixel XL and they work flawlessly.
I don't believe installing a custom ROM alone will fix your issue though. Stock ROM shouldn't cause the phone to slow down to the point you need to reboot to use it.
Finding the culprit will...
Good luck...
Click to expand...
Click to collapse
Thanks
First step is to remove Snapchat. I rarely use the app and only because my daughter sends stuff on it. I am going to tell her to send me stuff via another method
If that doesn't work then it's a new ROM. I have performed ROM installs before but have never flashed a new kernel on a phone before so that will be a new experience. Hopefully I won't brick the phone
lchiu7 said:
Thanks
First step is to remove Snapchat. I rarely use the app and only because my daughter sends stuff on it. I am going to tell her to send me stuff via another method
If that doesn't work then it's a new ROM. I have performed ROM installs before but have never flashed a new kernel on a phone before so that will be a new experience. Hopefully I won't brick the phone
Click to expand...
Click to collapse
Hello,
Don't worry, it's really easy. Also, if you are lost, there must be a ton of tutorials in general section. If you are lost yet, just ask and someone will point you in the right direction...
Good luck...
lchiu7 said:
I have a N6 purchased Dec 2015 new from Amazon. The only mods, if you can call it that is, I have unlocked the boot loader. I am currently running N6F26Y sideloaded via ADB.
The phone was great when I first got it but now after about a day or so of usage it becomes slow and sluggish and unresponsive I have to restart it to use it. I have done a factory reset a couple of times which gets it back to normal for a week or so and then the problem recurs. Occasionally I will delete the cache which also helps. Snapchat is one of the worse apps - crashes the phone regularly and is a very slow app.
Also the camera can get very slow often taking seconds to take one photo.
I love the phone but it's becoming unusable now. The contrast between this and a new phone (I have purchased a Moto Z) is like night and day. The Moto Z runs instantly, has no lag and is a nice phone. But what I like about the N6 is the large screen which makes it great for videos etc.
Short of perhaps flashing some custom ROM is there anything I could be doing?
Click to expand...
Click to collapse
I've been running Pure Nexus and wanted to let peeps know I put Nitrogen on and man it's so smooth, my wifi tether is back and I went to sleep last night with 50% battery still. When I installed it I opted for the nano gapps I think so like 175mb for minimal apps and maybe that's why it's running so efficient. Maybe I could have re-installed Pure Nexus with a clean install and it would have gotten better but it was a good time to try something else. Also when Nitrogen got an update I was notified just like stock and it downloaded. I didn't even know these could do that. Anyways give it a try and you might just switch back. I was looking into new phones but if it keeps working so smooth with battery longer than a day then I'm fine for now.
Snap chat is not that big of an issue. What I have found to cause the device to slow down is normally almost full device storage and a crappy cache release code in apps. Some apps don't release their cache properly. So it causes lag. This is why a reboot seems to fix it.
While a custom rom may fix this issue it is not the solution. The proper solution is to find what is causing it and fix/repair/ditch it.
Worst offenders for crappy code in my thoughts. Other will disagree with one on this list I am sure. So don't bother. I know people swear by it. It runs like crap for me at times and causes my whole device to lag until I close it out.
1 Facebook
2 FB messenger
3 Google Chrome ( don't do it lol)
4 whatsapp
5 Hangouts
Mind you this is just a list on my usage. It may very per user and even device (considering different hardware)
zelendel said:
... It runs like crap for me at times and causes my whole device to lag until I close it out.
1 Facebook
2 FB messenger
3 Google Chrome ( don't do it lol)
4 whatsapp
5 Hangouts
...
Click to expand...
Click to collapse
I can confirm this, because I've removed these apps (-whatsapp) and also decrypted the data partition...
My N6 is fast.
Maybe a lite stock ROM and an other kernel is a good start.
NLBeev said:
I can confirm this, because I've removed these apps (-whatsapp) and also decrypted the data partition...
My N6 is fast.
Maybe a lite stock ROM and an other kernel is a good start.
Click to expand...
Click to collapse
Currently I have FB, FB messenger, and Chrome but when I installed gapps I chose a super lite install so tons of bloat and google apps were not installed and my battery has gone way up and it's so smooth. I'm sure even when we don't use apps they're always doing something in the background. I bet you're right and a stock lite ROM would be good too with the minimal bs apps.
zelendel said:
Snap chat is not that big of an issue. What I have found to cause the device to slow down is normally almost full device storage and a crappy cache release code in apps. Some apps don't release their cache properly. So it causes lag. This is why a reboot seems to fix it.
While a custom rom may fix this issue it is not the solution. The proper solution is to find what is causing it and fix/repair/ditch it.
Worst offenders for crappy code in my thoughts. Other will disagree with one on this list I am sure. So don't bother. I know people swear by it. It runs like crap for me at times and causes my whole device to lag until I close it out.
1 Facebook
2 FB messenger
3 Google Chrome ( don't do it lol)
4 whatsapp
5 Hangouts
Mind you this is just a list on my usage. It may very per user and even device (considering different hardware)
Click to expand...
Click to collapse
Thanks for the advice. Of the list of apps above I have only Chrome and Hangouts. I really can't see replacing either of them.
I also should have pointed out that the phone locks up randomly requiring a hard reset. I wonder if an errant app could cause that or I have some RAM problem. Certainly on a PC bad RAM can use in Windows a blue screen or something but perhaps Android isn't so forgiving?
lchiu7 said:
Thanks for the advice. Of the list of apps above I have only Chrome and Hangouts. I really can't see replacing either of them.
I also should have pointed out that the phone locks up randomly requiring a hard reset. I wonder if an errant app could cause that or I have some RAM problem. Certainly on a PC bad RAM can use in Windows a blue screen or something but perhaps Android isn't so forgiving?
Click to expand...
Click to collapse
I would flash TWRP, flash supersu in TWRP to root, make a complete backup in twrp, then remove whatever Google apps you're not using with a system app removal app. Getting some of that bloat off the device should help. If it's still laggy, then look into a custom ROM. I run Tesla on my Nexus 6 with none of the issues you're having. I don't decrypt it either
Running abdroid 7.1 here. I dont get any slowdowns, at leas until the battery doesnt drop below 50 and 25 percent.
Im running a custom kernel and my phone is rooted. Everything else is stock.
Can you flash a custom kernel and presumably TWRP without wiping the phone? If so then might try that before a custom ROM
lchiu7 said:
Can you flash a custom kernel and presumably TWRP without wiping the phone? If so then might try that before a custom ROM
Click to expand...
Click to collapse
Hello,
Since your bootloader is unlocked, flash TWRP and install the kernel, no problem.
Might give you a slight boost at first sight, but your device will likely slow down over time anyway...
Cheers...
I'm on 7.0 with the April SP. I have dozens of apps installed, including Hangouts. I use Firefox for browsing, I like it better than chrome (and you can install an ad blocker).
My camera slows down when the battery is under 40%, and the whole device slows dramatically, though not unusable, at or below 5%. But otherwise, no issues what so ever.
One solution that I have not seen suggested here is resetting the device and NOT taking the Google account backup of all your apps. I would suggest making a completely clean install of the factory rom you have and installing one or two apps at a time, most important to you first. And do this for a few days/weeks until you find the app that's misbehaving.
Although there are general bad players out there, this bad app could be unique to your device. Just because all devices of the same model have the same specs and components, doesn't mean that there isn't variability in parts quality.
I would do this before trying any new roms or kernels. Find the true problem first.
Good luck!
edit:
I had another idea: Go into your battery stats and network stats and storage stats and see if any app seems to be using too much of any, or all of the 3. This may get you the answer more quickly.