I first started using CM at 6.1.2. I'm now on CM7 RC2 and the same problem still occurs. I have no idea why this happens but I'll provide as much info as possible in the hope that someone will be able to figure it out.
My phone will work completely normally for several days after I initially flash CM6.1.2 or CM7. After a few days, a crash will occur where the screen stays on but the phone is completely unresponsive to all input -- touch, softkeys, or hardware keys. The power button stops functioning. After a while, the screen dims and the phone reboots. After the reboot the phone chugs along for a few hours and then the same thing happens. This crash almost always occurs in the Browser, in the middle of loading a page. I don't think it's a memory issue because I consistently have ~100MB free for RAM.
Also, I don't know if this is at all related, but I often notice just before the crash, the haptic feedback from the phone for keyboard presses and the softkeys becomes very erratic and inconsistent.
I can never get a logcat because the phone restarts after the crash. Has anyone else seen this or know what might be the problem? Again, this has been happening all the way since CM6.1.2 (and possibly earlier, I haven't tried anything earlier than 6.1.2 though). This is driving me pretty crazy, and I really love CM and would like to continue using it, but this is kind of a dealbreaker.
Did you wipe between flashing CM6 and CM7?
Yes, I always wipe data/cache/dalvik between flashing.
Related
Hey all, today I just started having a problem with my touch input. Sometimes, it won't register my touches at all, including the hardware capacitive buttons at the bottom. Sometimes, turning the screen off and on will fix it, sometimes it won't.
Other times, I'll get what people call "ghost touches"; the screen is reacting as if I was touching it in certain spots when I'm not. Honestly, I can sit back and watch as my phone uses itself (it's really creepy actually).
The weird thing is that this just happened out of the blue. This morning my phone worked perfectly fine; I had never seen this issue before. Then all of a sudden this started happening. I am using CM6 nightlies and I have tried everything. I wiped everything, flashed the new nightly, flashed a stock 2.2 ROM (with Sense), changed the NovaFreq values, tried a kernel without the FPS unlock, and the problem persists.
Does anyone know how to fix this issue? If it has been over 30 days since I bought the phone, will Sprint still replace it?
Have a VERY weird issue going on. I've been using Burnt Droid 1.4.2 by Netarchy since it came out. I decided to flash his new 4.3.4 CFS-NoHavs,noSBC, with static undervolt (i wanted to try and see if it was stable since I had success using undervolted kernels last year). I used proper procedure and cleared cache/dalvik-cache before flash. I downloaded the new Angry Birds from amazon and started playing it for a few minutes phone started lagging very bad, then had to restart. I said forget this; undervolt is probably causing this, and reverted back to the original 4.3.1-cfs-nohavs-nosbc which I never had a problem with(used proper procedure above to flash back kernel as well).
Now a day later at night, I decide to run my phone down because I'm trying to recalibrate my battery(I'm at less than 10% at this point). So I load up Wifi, turn on Pandora, and browse the internet. Not even 5 minutes into it, here's whats occuring in order:
1) Bad lag.. Pandora starts stuttering, so I hit the home button
2) HTC Sense restarts, It doesn't even force close, or at least it's not telling me
3) a Hot restart occurs a few moments later... (no white boot screen, just starts bootin from ROM screen)
4) At this point, sometimes its still laggy, sometimes it's fine. If it's laggy I must do a battery pull because It will keep looping to this point.
I can rinse and repeat this running pandora + browsing the web, and the same 4 steps above will happen within moments of eachother. I've been using this ROM since January with no major problems like this
A few side notes:
-I have Evo hardware 0002 (launch day evo)
-Rooted with Toast's original root method, eng .76 boot loader
-Newest radio/PRI/NV/Wimax
-My phone does not randomly reboot on me normally. Reboots only occur when following the above steps.
-I do not use Set CPU
Here is where I am very superstitious. I've been closely monitoring the "Boot looping + no Recovery Access" forum, and similar forums to this. Within the past few months I have tried out a few different CM7 nightlies. I have never flashed RC2 but I have flashed some after and before and tried those out for a while. I just hope my phone isn't starting a dying phase in relation to the problems people are having now.
Is there anything else recommended before I end up doing a full wipe and reflash the rom?
bigblueshock said:
Have a VERY weird issue going on. I've been using Burnt Droid 1.4.2 by Netarchy since it came out. I decided to flash his new 4.3.4 CFS-NoHavs,noSBC, with static undervolt (i wanted to try and see if it was stable since I had success using undervolted kernels last year). I used proper procedure and cleared cache/dalvik-cache before flash. I downloaded the new Angry Birds from amazon and started playing it for a few minutes phone started lagging very bad, then had to restart. I said forget this; undervolt is probably causing this, and reverted back to the original 4.3.1-cfs-nohavs-nosbc which I never had a problem with(used proper procedure above to flash back kernel as well).
Now a day later at night, I decide to run my phone down because I'm trying to recalibrate my battery(I'm at less than 10% at this point). So I load up Wifi, turn on Pandora, and browse the internet. Not even 5 minutes into it, here's whats occuring in order:
1) Bad lag.. Pandora starts stuttering, so I hit the home button
2) HTC Sense restarts, It doesn't even force close, or at least it's not telling me
3) a Hot restart occurs a few moments later... (no white boot screen, just starts bootin from ROM screen)
4) At this point, sometimes its still laggy, sometimes it's fine. If it's laggy I must do a battery pull because It will keep looping to this point.
I can rinse and repeat this running pandora + browsing the web, and the same 4 steps above will happen within moments of eachother. I've been using this ROM since January with no major problems like this
A few side notes:
-I have Evo hardware 0002 (launch day evo)
-Rooted with Toast's original root method, eng .76 boot loader
-Newest radio/PRI/NV/Wimax
-My phone does not randomly reboot on me normally. Reboots only occur when following the above steps.
-I do not use Set CPU
Here is where I am very superstitious. I've been closely monitoring the "Boot looping + no Recovery Access" forum, and similar forums to this. Within the past few months I have tried out a few different CM7 nightlies. I have never flashed RC2 but I have flashed some after and before and tried those out for a while. I just hope my phone isn't starting a dying phase in relation to the problems people are having now.
Is there anything else recommended before I end up doing a full wipe and reflash the rom?
Click to expand...
Click to collapse
I'm not really sure what's causing your problem, and If i was in your situation, I'd most likely do a complete wipe, including calkulin's format all, and either restore a good nandroid, or reflash the rom from scratch.
That said, I don't believe CM to be 'dangerous' to run or anything like that. Yes, it is odd that an increasing number of people are reporting somewhat major issues, with boot looping the splash screen, and being permanently stuck there. However, that doesn't mean CM is the cause. It does seem to be a common denominator in the people that this has happened to, but there are soooo many other variables that come into play with something like this. There is no proof that CM caused it, but it does seem odd that everyone it happened to was running CM. Also, I'm sure there are thousands of CM users, and a select 8-10 people have reported these issues on here. That's a very low percentage, overall. With all that said, I myself won't be running CM in the near future, either until it's confirmed or denied that it has anything to do with these issues. I'll just be playing it safe, just in case.
I'm stock everything, no root or mods and it restarts at the 4g screen skips everything else...
Sent from my PC36100 using XDA Premium App
I think I will do the format all and completetly wipe it and reflash the rom from scratch. Thank you!
This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Saturn2K said:
This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Click to expand...
Click to collapse
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
bootny said:
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Click to expand...
Click to collapse
Next time it happens I will, I'm just afraid it will break Facebook/SMS integration like I've had happen before.
It's just so weird since it breaks everything. The lockscreen, the options, Pandora's station list, the browser, and it goes on and on. It's like there's some sort of display mode that gets screwed up.
dom085 said:
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
Click to expand...
Click to collapse
What version are you using. I'm going to try to install nightly 77 today after a fresh wipe.
I was seeing the same thing. Now I'm trying to figure out why my data speeds are so painfully slow on CM7 so I can't offer a fix. Flashing back to Warm to troubleshoot 3G.
I get these issues all the time no matter what kernel or nightly I'm running. It has forced me back to sense roms lol
Same problem here. I updated stable mod from stable mod. Reinstalled. Going on 4 days, no issues so far.
Sent from my PC36100 using XDA App
I have the same exact issue. This never happens on a sense rom. I did some tweaks to my system over the past week and I haven't had to reboot since this past Saturday or Sunday. I thought I had fixed it!
Then...
My phone started doing it this morning after I turned on 4G at work, literally as I was writing this post it started doing it. I then turned off 4G.. and it instantly went away. Turning back on 4G and it isnt doing it right now. Now my phone is doing something weird with go sms pro... when I get a text and I respond via the pop up message.. once my text moves to a second line I dont see what I am typing anymore... and now it has progressed to where the pop up box isnt refreshing after I send a message (this is all happening while I am typing this post). Now the phone has become laggy and somewhat unstable... rebooted! All is well. So I went roughly 4-5 days without a reboot... where as before I had to reboot at least once a day.
Thats about the best I can get with these settings:
CM7 7.0.3.1
Savaged Zen 2.6.38.5 CFS > Using SavagedZen Governor, min 384 max 998
Displaying some animations (read somewhere that is a "fix".. or helping extend the time it takes for the Black screen of death to appear).
This is after several full wipes, several when I was running Amon RA recovery 1.8 then updated to the latest and did it two more times. After upgrading Amon and wiping I did not use any backups and started completely from scratch.
So I am not sure what else to do. Some people are getting this, some are not.
3 days ago I found that pressing the home button didn't take me to my home screen, but just briefly flashed black, but stayed on the home screen. It vibrates so the button is recognised as being pressed.
Rebooting fixes this issue, but it does come back (seemingly randomly).
CM 7-11162011-NIGHTLY-DesireHD, LordMod kernel.
Has been totally stable for months (haven't flashed anything for about about 2 or 3 months, now that I've found I'm totally happy with CM7 and that there are no new nightlies)
http://androidforums.com/droid-x-su...92-home-button-just-flashes-black-screen.html
This thread describes my exact issue, but ADW-Launcher can't be cleared as default, presumably as it's my only launcher. Restarting adwlaucher doesn't fix the issue, but a reboot does.
Please help me fix this!
Have you tried clearing the app data? Maybe wipe cache.
There is actually new nightlies just not from the buildbot. A few people are syncing to the repo and uploading new builds everyday
I don't have a real need to get new nightlies tbh, CM is doing a fab job at the moment, though I can't say I'm aware of what's changed so maybe I'm missing out!
After going crazy, literally trying everything, it seems Tasker is to blame. I've got a rule that says lock the screen if the proximity sensor is set off. If I experience the problem, disabling and re-enabling that rule solves the issue.
I really can't think why that'd be though?! Especially as the proximity sensor is not being set off at the time the issue starts.
Hi all -
I'm on AT&T, 100% stock, non-rooted, etc. I upgraded to JB last night via Kies without issue.
However, ever since the upgrade, my phone won't go more than 5 minutes without freezing and then crashing.
It's a very odd behavior... the screen will still animate. So, if I'm playing a game with a timer, the timer will still count down. But all touch input (including menu/home/back) does nothing. Home/back don't illuminate or do anything, but they do provide haptic feedback. Power button does turn the screen on/off.
Eventually after a few minutes, the lock screen comes up with the "tip" even though I've clicked to never show it again. However, it barely registers a swipe to unlock when it freezes again. At that point, it will usually self-reboot.
I've tried to enable some of the developer options to see if maybe there was a rogue program that was incompatible with JB, and maybe causing the issue, but I couldn't see any correlations.
I really want to avoid doing a factory reset if at all possible, as I have a game that I worked really hard on to beat a few levels, and I'd hate to lose my progress.
Anyone have any ideas on what I can try?
I should note that uninstalling programs is iffy... sometimes it works, other times it just uninstalls indefinitely.
Thanks!
Castaway78 said:
Hi all -
I'm on AT&T, 100% stock, non-rooted, etc. I upgraded to JB last night via Kies without issue.
However, ever since the upgrade, my phone won't go more than 5 minutes without freezing and then crashing.
It's a very odd behavior... the screen will still animate. So, if I'm playing a game with a timer, the timer will still count down. But all touch input (including menu/home/back) does nothing. Home/back don't illuminate or do anything, but they do provide haptic feedback. Power button does turn the screen on/off.
Eventually after a few minutes, the lock screen comes up with the "tip" even though I've clicked to never show it again. However, it barely registers a swipe to unlock when it freezes again. At that point, it will usually self-reboot.
I've tried to enable some of the developer options to see if maybe there was a rogue program that was incompatible with JB, and maybe causing the issue, but I couldn't see any correlations.
I really want to avoid doing a factory reset if at all possible, as I have a game that I worked really hard on to beat a few levels, and I'd hate to lose my progress.
Anyone have any ideas on what I can try?
I should note that uninstalling programs is iffy... sometimes it works, other times it just uninstalls indefinitely.
Thanks!
Click to expand...
Click to collapse
This sounds somewhat familiar to my experiences with JB. I rooted right away with the stock JB and had freezing / crash issues. So I then went pure stock and had issues (un-rooted). I then tried a custom TW-based ROM called BlackJelly and had issues. Now I am on CM10.1 which is AOSP JB4.2.1 based and things are even worse.
There seems to be no JB ROM that is stable for my phone. Getting very tired of this.
See my thread for details:
http://forum.xda-developers.com/showthread.php?t=2044769
- Ed
Strangely enough, my issue ended up going away. I think it was a rogue program that needed it's dalvik cache rebuilt. Once uninstalled, the phone worked great. Not sure what app it was.