Whenever I load up any app that involves the camera about 3-8 seconds in the application my phone freezes, cannot go to homescreen, menu and back button vibrations stop.
I am currently on 10/21 AOKP and it's been happening ever since I can remember like 9/14 or 8/14 of CM10 Preview.
tehsprayer said:
Whenever I load up any app that involves the camera about 3-8 seconds in the application my phone freezes, cannot go to homescreen, menu and back button vibrations stop.
I am currently on 10/21 AOKP and it's been happening ever since I can remember like 9/14 or 8/14 of CM10 Preview.
Click to expand...
Click to collapse
Have you returned to stock to verify it isn't hardware related?
I have had a few small glitches on AOKP, but they have all been resolved by doing a FULL wipe. I use CWM and have found that multiple wipes tend to be more effective along with formatting /system and /data.
Bump .
tehsprayer said:
Whenever I load up any app that involves the camera about 3-8 seconds in the application my phone freezes, cannot go to homescreen, menu and back button vibrations stop.
I am currently on 10/21 AOKP and it's been happening ever since I can remember like 9/14 or 8/14 of CM10 Preview.
Click to expand...
Click to collapse
Flashed 10/28 task ROM today. Camera didn't work. Searched. Saw that some had suggested simply rebooting. Worked for me.
I too have this issue with my camera app.
Tried a different one from the play store as well.
Tried not restoring apps from TB.
After I do a fresh rom flash, the camera seems to work flawlessly for around a day with some reboots in between.
Then after said time, I go to try it and it locks the phone up which I then have to do a hard reboot.
I've noticed this since the October AOKP releases, Paranoid and just tried the latest SLIM BEAN rom which are all built off of AOKP and CM so I wonder if its an AOKP issue for select (unlucky) users.
I've been trying to narrow it down as to when it happens or what changes, but so far its hard to pinpoint.
I suppose my next try would be to see if CM does it then perhaps that would indicate that its a AOKP issue
Related
I have been running the Petes nightly rom for a couple months now and have been loving it. However last night something really strange happened. I was watching tv and turned my screen on to unlock the phone and when I did I noticed about 3 force close messages and I never get fc. I tried to open other apps and almost all of them force closed. I rebooted the phone and same thing. I rebooted into recovery and chose the fix permissions option and when I rebooted it seemed better at first besides a few apps still fc. Then I noticed that all my homescreens were deleted except my default one which still had my app folders on it. I am running francos kernel with the updater. I have been on milestone 2 for about a week now and hadnt had any issues. It's almost like I did a wipe data on the phone because I had to sign back in to certain apps as well. Any idea for what could have happened? The only changes I made to the phone yesterday was updating 3 apps and I used the settings in francos updater to drop all the voltages down 25mv but I don't see how either could have done anything.
How do I thaw it without damaging the device?
Wild guess here, go to apps management and clear data?
Did you try any free camera app from market n check if that too is freezing?
I too have this issue with my camera app.
Tried a different one from the play store as well.
Tried not restoring apps from TB.
After I do a fresh rom flash, the camera seems to work flawlessly for around a day with some reboots in between.
Then after said time, I go to try it and it locks the phone up which I then have to do a hard reboot.
I've noticed this since the October AOKP releases, Paranoid and just tried the latest SLIM BEAN rom which are all built off of AOKP and CM so I wonder if its an AOKP issue for select (unlucky) users.
I've been trying to narrow it down as to when it happens or what changes, but so far its hard to pinpoint.
I suppose my next try would be to see if CM does it then perhaps that would indicate that its a AOKP issue
Updated to JB 4.1.1 and video camera not working, Gallery Stopped.
Updated to JB 4.1.2 same problem.
My camera and panorama are working fine.
Please help.
Thank you.
I'm having a similar problem.. last night, I attempted to use the TeslaLED widget to aid myself while walking my dog at night. To my chagrin, the light never came on. I wondered if it was the light itself, so I attempted to open the camera to take a picture... it immediately closed and showed "gallery stopped" for an error message. I rebooted the phone hopping that would fix the problem. The problem was still there after booting back up.
I was running a CM10 nightly that I've had for over a month. My Verizon Galaxy Nexus is rooted and unlocked. I attempted to flash a stable CM10, but am still having the same problem. I will attempt to flash stock tonight to see if that fixes it.
Gallery not working
Ever since JB 4.2.1 update...my gallery and camera no longer works! Tried clearing cached, hard reset but no luck. Next step might be to toss it out the window....
Ok, somehow its fixed! I had backed up my gnex via recovery mode before I installed the stable cm10. When that didn't fix my problem, I restored the backup do I didn't have to reconfigure everything again when I flashed stock later yesterday evening. But, to my surprise, restoring the backup fixed the problem!
I too am having an issue w/ my Gnex's camera. The app will open from the gallery, & the camera buttons are at the bottom of the screen, but the screen is black. You can push the button to capture a pic, but nothing happens, you can switch to record video & it locks up & FC's. Every now & then you can open the app directly from the camera widget, but it typically just goes to a black screen w/ the software keys at the bottom faded out & the phone just locks up. I replaced the camera w/ a known working camera from a parts Gnex I have. Same issue. I was running 4.1.2, but I've since upgraded to 4.2.2 hoping there was some sort of software fix. No dice... still doing the same thing. The isn't rooted... but I'm going to root it & throw on another ROM to see if I can get it working somehow... but outside of that, I don't know what else to do. Any new ideas?
wslytoy said:
I too am having an issue w/ my Gnex's camera. The app will open from the gallery, & the camera buttons are at the bottom of the screen, but the screen is black. You can push the button to capture a pic, but nothing happens, you can switch to record video & it locks up & FC's. Every now & then you can open the app directly from the camera widget, but it typically just goes to a black screen w/ the software keys at the bottom faded out & the phone just locks up. I replaced the camera w/ a known working camera from a parts Gnex I have. Same issue. I was running 4.1.2, but I've since upgraded to 4.2.2 hoping there was some sort of software fix. No dice... still doing the same thing. The isn't rooted... but I'm going to root it & throw on another ROM to see if I can get it working somehow... but outside of that, I don't know what else to do. Any new ideas?
Click to expand...
Click to collapse
I have the same problem... camera non working
No idea why??
I've been using nothing but CyanogenMod ROMs on my phones since my Epic, and have always liked the CM roms.
I was running CM10.1.3 until CM10.2 was released. Never had any problems with 10.1.3. In the past, even the RC's have been pretty much daily driver material, but with 10.2, when i flashed the RC, I had nothing but trouble. FC's all over the place. I figured it was probably because I 'dirty flashed' 10.2RC over 10.1.3, but since at the time, i didn't feel like wiping and reloading everything, i reverted to my backup of 10.1.3 until 10.2 Stable was released. When Stable came out, I wiped the phone, cache and davlik 5 times each before flashing 10.2, then re-installed all apps from play. I only restored my sms/mms and call logs.
Since going to 10.2, I have had nothing but FC's and reboots. It has spontaneously forgotten all of my email accounts, lost all my text messages and sometimes takes several tries to get it to boot (hangs on boot). There isn't an app that hasn't FC'd - dialer, messaging, gosms pro, e-mail, to highlight a few, have all had problems crashing, and when they start crashing, I have to reboot the phone for anything to work. If i use the built in torch function, i generally have to pull the battery to get the phone to work again.
BLE also doesn't seem to work, and with the overall problems, I don't know if its because it's just not working in CM in general or if it's related to the rest of the problems I'm having.
Is anyone else having similar problems, and/or does anyone have any thoughts as to why I'm having so many problems? How close to 'Daily Driver' material are the CM11 nightlies?
SubnetMask said:
I've been using nothing but CyanogenMod ROMs on my phones since my Epic, and have always liked the CM roms.
I was running CM10.1.3 until CM10.2 was released. Never had any problems with 10.1.3. In the past, even the RC's have been pretty much daily driver material, but with 10.2, when i flashed the RC, I had nothing but trouble. FC's all over the place. I figured it was probably because I 'dirty flashed' 10.2RC over 10.1.3, but since at the time, i didn't feel like wiping and reloading everything, i reverted to my backup of 10.1.3 until 10.2 Stable was released. When Stable came out, I wiped the phone, cache and davlik 5 times each before flashing 10.2, then re-installed all apps from play. I only restored my sms/mms and call logs.
Since going to 10.2, I have had nothing but FC's and reboots. It has spontaneously forgotten all of my email accounts, lost all my text messages and sometimes takes several tries to get it to boot (hangs on boot). There isn't an app that hasn't FC'd - dialer, messaging, gosms pro, e-mail, to highlight a few, have all had problems crashing, and when they start crashing, I have to reboot the phone for anything to work.
BLE also doesn't seem to work, and with the overall problems, I don't know if its because it's just not working in CM in general or if it's related to the rest of the problems I'm having.
Is anyone else having similar problems, and/or does anyone have any thoughts as to why I'm having so many problems? How close to 'Daily Driver' material are the CM11 nightlies?
Click to expand...
Click to collapse
Just curious, you are flashing the correct gapps right? That gave me issues before.
Sent from my SPH-L710 using Tapatalk
The one I used is 'GApps_Core_4.3.zip'
Sent from my SPH-L710 using Tapatalk
I am currently running the latest build of the PacMan rom for my Sprint S3, but my problem didnt start there. As over the course of a few weeks my phone has been randomly crashing while running build 7 of Slimkat. It started crashing when i wanted to take a picture with the AOSP camera (when i hit the camera button and then it would shut off). Then it progressed to just crashing trying to use accuweather, or even when the screen was auto-rotating in my SMS app. So finally i just backed up my important bits and made a clean wipe into Wicked X 8.0 TW rom (because i'm on Ting and TW roms initially work on their network and wanted to export, or to just copy down the settings of, the APN xml to use in AOSP roms). After playing around with that for 20 minutes, i didn't experience any fc's or reboots. Though i did not use the camera in that time (i forgot to check). To which i then wiped it into PacMan rom that im at now. Which at the moment seems fine to do everything, except it will shut off if i want to OPEN the camera (doesn't let me use it at all). Plus i did have it crash once rotating with the play store up...
So im kinda lost, i wonder if this is just an issue with the camera in the rom, or if it might be a bigger issue with the phone itself. As ive been having the same random error's with two roms and i dont see anyone having FC's with pacman rom with the camera.
more testing done
So i have also attempted to odin completely back to stock and i have a stock rooted rom with nothing touched. The sudden shut-offs still happen and occur randomly. I installed logcat and what seems to be throwing error's is the accelerometer. Plus at first when i flash a new rom it seems to work ok with no problems for the first day, then suddenly start showing symptoms the next. Plus ive had it shut off during bootup too while going through the sprint 4g animation screen. Though i have not had it die on me in recovery, so thats a thing.... Plus it will rotate no problem half the time, and then ive seen it die rotating to use my keyboard.
So at this point i feel like its actually a hardware option. If it is the accelerometer, is it easy to fix (i guess re solder the connections if they're broke?)? or should i just try and replace the main board?