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
Related
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
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?
Is anyone besides me still using this phone? I'm impatiently waiting for a 2015 Nexus or carrier neutral/Project Fi capable Motorola.
For the most part my phone works fine and does what I need it to do. I've been running v11 M12 since its release without any serious issues EXCEPT...
Lately I've noticed after a few days the phone will slow to a crawl. I'll open Running Apps and see a bunch of apps restarting at one time. Only a reboot will resolve the issue. I'm not running any obscure or obviously misbehaving apps and everything works fine for a few days. It doesn't appear to be 4G/WiMax related (turning it off doesn't resolve the issue).
I flashed the last milestone build, XNG3CAO1L7, without a factory reset and it seemed really buggy right away. I'm trying the latest NIGHTLY right now and it also seems a little buggy. I'd rather not factory reset, but I will if that is what it takes to resolve my issue.
Just curious about the status of anyone else running these builds. Thanks!
Somebody HELP!!!!!!!!
I'm running Resurrection Remix LP v5.5.8 on my T-Mobile Galaxy S4 (SGH-M919). I love this ROM, but I'm having a persistent problem with Bluetooth crashing, within minutes of starting up. This a consistent problem, not even remotely intermittent - happens every single time I try to turn on Bluetooth - it shuts itself off, refuses to turn back on again, and on occasion, gives me the error message "Unfortunately Bluetooth share has stopped."
I have tried clearing the Bluetooth share app cache and data to restart - it will then turn back on, but soon turns back off.
The problem was bad enough that I took RR off my phone and tried some other ROMs, including basic CM12.1. I came back to RR because the other ROMs had more critical issues, but they did help me eliminate causes of my problem, in that I didn't have Bluetooth issues with them like I do with RR, and I was still running all the same apps, same devices I was trying to attach, etc.
I've also played with several of the settings in the Kernel Aduitor, including completely shutting off the task killer. No difference - problem persists.
I also tried some of the apps on Google Play that say they're supposed to cure problems like this. Fixed nothing.
Please help. Is there an alternative something that I can flash - Bluetooth driver, different kernel, something, that can fix this issue once and for all?
Got the same problem. Android V6 RR Remix. Any suggestions?
Seems to be a consistent MM ROM issue, currently. Some seem to work better than others on some phones.
Keeping bluetooth working on the S4 seems to be "dark arts". Cyanogenmod has historically had much problems with this too. Some nightlies are okay, then others cause BT to crash. Some don't work at all.
Anyone have any resolution to this issue? I'm having the exact same symptom, but I'm on a different phone.
Note II / T-889, Conch Republic. Might've been from a radio update I did a while back, trying different ones now.
denverjoe72 said:
Keeping bluetooth working on the S4 seems to be "dark arts". Cyanogenmod has historically had much problems with this too. Some nightlies are okay, then others cause BT to crash. Some don't work at all.
Click to expand...
Click to collapse
You might give this AOKP 6 MM ROM a try:
http://forum.xda-developers.com/showthread.php?t=3391994
Users are reporting that after a week of testing the Bluetooth seems to be working rather well.
Sent from my SGH-M919 using XDA-Developers mobile app