Related
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.
Hi,
I have a persistent problem with my camera with the MiniCM7-2.1.8: it simply doesn't work.
When I start the camera, the interface comes in, but where you are supposed to the picture, everything is just black. Then the the camera app force closes. The camera worked a while with MiniCM7-2.1.6, then the problem appeared suddenly and nothing seems to solve it (full wipe with MiniCM7-2.1.6, MiniCM7-2.1.7 and MiniCM7-2.1.8., several times)
The camera doesn't work with third party camera apps either
I don't want to change this rom, for this is by far the most outstanding in my opinion, but it would be great to have a camera.
Any suggestions are welcome, thanks!
smellcheck said:
Hi,
I have a persistent problem with my camera with the MiniCM7-2.1.8: it simply doesn't work.
When I start the camera, the interface comes in, but where you are supposed to the picture, everything is just black. Then the the camera app force closes. The camera worked a while with MiniCM7-2.1.6, then the problem appeared suddenly and nothing seems to solve it (full wipe with MiniCM7-2.1.6, MiniCM7-2.1.7 and MiniCM7-2.1.8., several times)
The camera doesn't work with third party camera apps either
I don't want to change this rom, for this is by far the most outstanding in my opinion, but it would be great to have a camera.
Any suggestions are welcome, thanks!
Click to expand...
Click to collapse
Mine camera working fine! which version of Kernel and MiniCM7 are you using? aNa kernel+ROM?
Problem
Hi, I'm from Venezuela and I have a problem, the rom works perfectly but does not work the camera button to take the picture and must be from the screen ...
also has some problems in the status bar but they are minimal, really good is my first report I want to thank you for making my phone I marvel more and more by large developers like you ...
Hi saintckk,
Now I am using nAa 10, but I had the same problem with 8b an 9 as well. I am kind of out of ideas what might have caused this - as I said, I tried several fresh installs and full wipes.
smellcheck said:
Hi,
I have a persistent problem with my camera with the MiniCM7-2.1.8: it simply doesn't work.
When I start the camera, the interface comes in, but where you are supposed to the picture, everything is just black. Then the the camera app force closes. The camera worked a while with MiniCM7-2.1.6, then the problem appeared suddenly and nothing seems to solve it (full wipe with MiniCM7-2.1.6, MiniCM7-2.1.7 and MiniCM7-2.1.8., several times)
The camera doesn't work with third party camera apps either
I don't want to change this rom, for this is by far the most outstanding in my opinion, but it would be great to have a camera.
Any suggestions are welcome, thanks!
Click to expand...
Click to collapse
TRY THIS
i had some probs with minicm too so i tried this tonight and now itz working ok
backup ur apps and settings and data( i suppose u have as u have changed many roms)
flash stock 2.1
root it
install xrecovery
flash nAa 10 kernel
full wipe
flash minicm7 2.1.8
try if this works and get back to me
Thank you, will try this tomorrow.
Hi hetunandu,
I've tried your method, but my problem seems to be hardware related - camera is not working even with stock 2.1. Anyway, thank you for the suggestion!
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
Hello all,
I recently started installing lots of ROMs and Kernels for my G800f. I quickly noticed I always had common issues with those.. I don't know if I"m the only one, I searched a lot for answers without success so maybe you can help me Here are the problems:
-The phone heats up for no apparent reasons, especially the top right corner of the screen. (being on whatsapp didn't heat my phone that much when I was on stock ROM) (This happens even before installing third party apps). I read on some forums it could have something to do with NFC but the fixes never worked in my case.
-The battery drains so quickly (I guess this has something to do with the previous) (I tried to clean up my battery hardware ports etc...) (This happens even before installing third party apps)
-Big camera issues : on snapchat, when I focus by tapping, everyhting slows down and the app becomes unuseable. On the camera app, I get an "Camera disconnected" error randomly. I saw on the forums that this is a problem with the media servers but please tell me what you think )
I can't just stay on my touchwiz stock rom because it's tooo slooooow to handle stuff like pokemon go (in CM13, pokemon go runs lightning fast). Everything is just better on a aosp custom rom, but It's impossible for me to have my phone heat and drain my battery while not having a reliable camera... I hope you will help me find a solution!!
Thank you in advance,
Netapy
Do you have the same problems with stock ROMs afters a factory reset? It looks like a hardware problem, maybe dying battery, of you still have these issues then probably it's the cause. If not it's software related.