I've been fiddling with my Cerberus installation, and I've come to find out it can't do anything with the cameras. When I send a remote request to take a picture or record video with the cameras, the phone either freezes or it sends me an unreadable file. It does everything else fine, like display messages and set alarms and GPS tracking. Seems to be a problem it has with the camera. Is this a known problem?
Just a guess dince im not at all sure, but possibly Cerberus hasnt been made fully compatible with 4.2.2?
Otherwise it may be an isdue with CM. Ive seen several posts about camera issues after flashing CM. (Doesnt seem to affect many people, but a few have mentioned it.)
Sent from my SGH-T999 using xda premium
Im having the same issue. Did you ever solve this? I went on the Cerberus forum to discuss it. Waiting for response.
Related
When I first start the camera app after a reboot I get the message "Cannot connect to camera". If I try to start the app again it works fine every time until the next reboot.
I've tried a factory reset which worked for a few reboots until the message started happening again.
I'm running the latest stock rom and can't figure out what's changing to cause this.
Any ideas?
Had you got that problem on earlier versions of stock ROM?
Sent from my R800i using xda premium
Sorry, I haven't had the phone long enough to have an older version of the stock rom.
Even I had this error once, I had to reboot the device to get that fixed.
This was the 1st time it happened.
One thing is it happened while shooting a 720p Video.
I don't think it's software problem, probably camera is damaged, or its flex cable. I had the same problem for a moment after disassembling my Play but I forgot to completely connect flex to the connector.
I think the only way to fix your problem is to bring Your Play to authorized service or (if your phone has warranty) send it to SE.
Sent from my R800i using xda premium
It could be but it just seems odd that its only the first time using the camera after a reboot. Try the app a second time and every other time its fine.
I would have though if it was the flex cable it would be all the time or happen randomly.
Well.
shadow wave said:
It could be but it just seems odd that its only the first time using the camera after a reboot. Try the app a second time and every other time its fine.
I would have though if it was the flex cable it would be all the time or happen randomly.
Click to expand...
Click to collapse
I'm having an issue like that right now. However, I started getting it after I messed with a ton of system files and the framework-res.apk
Did you do the same? I'm working on figuring out what went wrong, it's definitely a software issue for me.
Possible Problem and Solution
Hey guys,
I noticed something really curious after having an extensive conversation about a few r800's and a Moto Cliq XT about camera issues and I've isolated what might be the problem that people are unknowingly creating.
Status Bar Widgets
Having the LED/Flash/whateveryouwanttocallit light as a widget toggle in Android 2.3.x seems to use the same line of code as the camera. Or something techy like that. IDK. I was about to fix it after a ton of annoying work. But the easiest way (and fastest really) that I came across was just turning the widget off. Removing it completely. In fact, just get rid of that entire feature in 2.3.x and save it for like, IDK, 3.0+
Really hope this helps that random person out there who needs it.
-Fox
Fox Bailey said:
Hey guys,
I noticed something really curious after having an extensive conversation about a few r800's and a Moto Cliq XT about camera issues and I've isolated what might be the problem that people are unknowingly creating.
Status Bar Widgets
Having the LED/Flash/whateveryouwanttocallit light as a widget toggle in Android 2.3.x seems to use the same line of code as the camera. Or something techy like that. IDK. I was about to fix it after a ton of annoying work. But the easiest way (and fastest really) that I came across was just turning the widget off. Removing it completely. In fact, just get rid of that entire feature in 2.3.x and save it for like, IDK, 3.0+
Really hope this helps that random person out there who needs it.
-Fox
Click to expand...
Click to collapse
YES, i agree, should make a fix btw, =)
I've seen a similar post to this way back in the day when I first rooted my phone, but since then have been unable to relocate said post, so I'll just post here as I've noticed this to be a constant problem, perhaps GB related.
Days where I don't make any phone calls I get decent battery life, about 1% every 2 hours and that's listening to music. But god forbid I have to make a phone call because then Dialer remains on consuming my sensor in spare parts. I've disabled just about everything in call settings related to sensors and even tried turning my BT on as I read it might fix it, no dice. The only way to fix atm is to restart or perform a hot reboot.
Anybody else experiencing this or have found a fix? Currently running Decks 1.3d and thinking of going back to a Sense rom cuz I never dealt with this crap before I tried AOSP, even though I love and prefer AOSP over Sense.
Naturesretard said:
I've seen a similar post to this way back in the day when I first rooted my phone, but since then have been unable to relocate said post, so I'll just post here as I've noticed this to be a constant problem, perhaps GB related.
Days where I don't make any phone calls I get decent battery life, about 1% every 2 hours and that's listening to music. But god forbid I have to make a phone call because then Dialer remains on consuming my sensor in spare parts. I've disabled just about everything in call settings related to sensors and even tried turning my BT on as I read it might fix it, no dice. The only way to fix atm is to restart or perform a hot reboot.
Anybody else experiencing this or have found a fix? Currently running Decks 1.3d and thinking of going back to a Sense rom cuz I never dealt with this crap before I tried AOSP, even though I love and prefer AOSP over Sense.
Click to expand...
Click to collapse
I would look for the topic about wake lock, there is a possible fix in there if I remember right. Also could try to reflash decks, I've never had a problem.
Sent from my PC36100 using xda premium
I agree with the guy above me, you should check the thread of whatever ROM your using as well, and for a quick fix you could always just push the Power/Screen Lock button
http://forum.xda-developers.com/showthread.php?p=14814224
Sent from my PC36100 using xda premium
After doing a search, it seems this might be an isolated case, but maybe someone can help regardless.
When I record video (no matter how long the video is) the audio is always out of sync, a little behind the video. I've tried setting it on a lower resolution, turned on "Power Shutter" (which I don't know the function of, to be honest) and doubt it's the ROM since it's done this since stock, and I'm on CND 1.5.0 now.
Any ideas what could be causing this? Has anyone else had this issue besides me?
You might have some hardware issues. Hard to tell, but it does sound like a software issue too.
The only thing tripping me is that you said you had the problem on stock which makes it seem like a hard issue.
Sent from my Galaxy Nexus using XDA
Geez, I hope it's not a hardware issue.
Does anyone have any suggestions for alternative camera apps? I think it might help me figure out if it is indeed a software issue.
Well, it's been about 4 months since I upgraded to this phone, and I've had the same issue, whether it be on ICS (stock, Lifeless, Imperium) or on JB (stock, Lifeless, Imperium)-haven't flashed CM. The issue is, and as far as I can tell, at random, my media sound (YouTube, music, videos-no matter the player) quits on me, up until a reboot, after which it's fine until the next random time it happens. Sometimes I'll go several days with no problems, and other times it'll happen, and then 2 minutes after a reboot, happen again. I've done a little troubleshooting, and haven't had any leads. So, I wanted to put this out and see if there is anyone else having a similar issue, or if maybe something is just up with my specific device.
Sent from my LG-LS970 using xda app-developers app
I am not saying this is the cause but on rare occasions the audio hardware/controller will start to fail. Out of the thousands of phones I've worked on I've seen this only a handful of times. Another cause is a fault in the LG software itself but I would expect to see more reports of this issue if that was that case.
I suggest flashing over to CM and see if you can duplicate it. If so then the audio hardware is suspect. If not, then yet anther LG software bug has shown up.
Lokifish Marz said:
I am not saying this is the cause but on rare occasions the audio hardware/controller will start to fail. Out of the thousands of phones I've worked on I've seen this only a handful of times. Another cause is a fault in the LG software itself but I would expect to see more reports of this issue if that was that case.
I suggest flashing over to CM and see if you can duplicate it. If so then the audio hardware is suspect. If not, then yet anther LG software bug has shown up.
Click to expand...
Click to collapse
I just thought it was strange that it's happened on both OS's and all the ROMs, so I'd leaned toward it being my device. No permanent issues, mostly just an annoyance. Since I rely on my phone for work and such, I've been hesitant on flashing CM. It also hasn't gotten worse or better over time. The most random thing I've experienced on a phone. Oh well, it's not enough of a problems to have to deal with Sprint to try and get it replaced. Mostly just wanted to see if anyone else had experienced it.
Sent from my LG-LS970 using xda app-developers app
Hiya, this is my first post on XDA developers, but I am a relatively experienced user. I'm a licensed computer technician and have been using XDA for years.
Anyways, to the point! Currently, I'm using SlimKat on my note 2 ( i317 ). It works great, but theres only one thing that I am having troubles with, and have not been able to fix. When I'm using the app Snapchat and I'd like to record a video it only records for 3 or so seconds before it automatically cuts it off. I searched up my problem, and found a few solutions that worked for other people.
- Disabling hardware keys
- Going into Snapchat settings and change the video quality to low
Apparently this is a problem with all AOSP based ROMs.
Neither of these worked, and I'm not interested in changing ROM's right now. Anybody have any suggestions that might fix this?
What worked for me was turning it to low. Rebooting and taking a video then turning it back to auto and rebooting again. Hope it helps