Related
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.
I've been running the ICS roms on my kindle fire for 2 months now and wanted to start out by thanking everyone involved in it's development (currently cm9.2.24 and current gapps). I spend a lot of time reading the posts and learning as I go.
I read a lot about black screens and screen lock ups but until recently it only happened occasionally to my device. For the last 3 updates my device has been experiencing each constantly. every time my screen goes to sleep or i turn it off I either open up a frozen screen or a black screen and I need to do a restart to get it to work again. and I haven't seen any comments in the development thread that describe this happening to this extent.
My question is...Is this happening to everyone else or might I be doing something wrong. This isn't my primary device and I can deal with it if happening to everyone and I enjoy the tinkering but I'm thinking its more me and something I'm missing. What is MD5?
When I flash the rom i wipe I do a factory reset, clear delvik cache, cache, and system. and simply restart. Should I be doing more? thanks for your help.
My kindle turns on just fine after sitting for hours or even all night. This may be due to the fact that I have wifi keep alive installed so the wifi never shuts off.
Sent from my GT-I9100 using xda premium
I have also been updating routinely keeping abreast of the latest ICS and have not had any problems so far doing he same cleaning. Could an app be the cause?
MD5 is a way to check to make sure you haven't downloaded and are about to install a corrupted file. You can download a program like MD5 Calculator and check the value of the file on your computer against what the value is supposed to be
I had this issue before with another device. It was wifi going to sleep and not wanting to wakeup... try downloading some sort of powermanagement app and set wifi to.never sleep
Thanks for the help. I thought early on that the problem might arise from an app and have held off installing apps once I flash and it still happen right away. I've read about others with issues related to wifi but never considered that might be my issue. I'll give that a try and let you know if that takes care of it. thanks for the suggestions and with the md5 clarification.
I've set my wifi to always on for 24 hours now and the same issues are still happening constantly. I've also removed the bulk of my downloaded apps to test if they are causing the issue. I only have words w/ friends, g-reader and gmail on the kindle which I assume are fairly popular and others are using too. if I try to re-flash should I wipe more than what I listed in the OP (factory reset, delvik, cache and system) ? issues again are constant black screen and frozen screen. Any other suggestions would be appreciated.
Are you still having the issue? Im suprised that didnt fix it. 99 percent of the time screen of death is wifi sleep problems.
It happened to mine this morning ...
I tried to turn on/ return from sleep mode this morning, and it was the Black screen ... had to hold for 30secs, before it would boot.
I think my issue was related to an alternate Keyboard App I had installed - Touch Pal. It was working perfectly for several days then this morning after the reboot gave me constant FC errors, until I removed the app, with root explorer.
I've had this problem sometime over a month now, can't remember if I did anything to make it like this. I made a post somewhere about it happening the 17th of May, so it started somewhere before that.
My phone will freeze for 2 seconds and then reboot itself.
It started while I was on stock 4.0.2 and now I'm on stock 4.0.4 IMM761. I have a GSM Galaxy Nexus.
It only happens just after the phone has been woken up and something is started. The most common (as it's my go-to-way of forcing it, to see if it's still there) is after waking up the phone, sliding down the notification bar and pressing "settings", which doesn't open but the phone freezes and reboots itself. I first discovered this when I wanted to go in there to change screen brightness. It's also happened when I went into the notification bar and pressed a battery app there. It doesn't matter if I'm doing it in the lock screen or after the lock screen.
It's also happened when I wake up the phone and enter the camera through the lock screen.
It also regularly happen if I set an alarm in the morning. When my alarm is suppose to play it freezes and reboots, and when it's rebooted, the alarm has been cancelled without ever playing.
It doesn't need to wake from deep sleep to do this, I've had it happen mere minutes after trying to see if it's there.
I don't know if it has something to do with this, but the 21st of April I tried to do the "clear google services framework" trick to force 4.0.4 ( I was on yakjuxw), but it did not work and I remember my phone acting janky and I was scared it messed something up, but I seem to remember it getting better. I can't remember what exactly it did though.
I've read that 4.0.4 would fix the reboots that a lot of people were having (don't know if it was the exact same kind of reboots as mine) so I did this to make my phone a yakju (translated from Danish):
http://translate.google.dk/translat...at-modtage-opdateringer-til-din-galaxy-nexus/
I did that the 8th of June, and it worked flawlessly and I was on 4.0.4 IMM761 in no time. Unfortunately it did nothing to stop these reboots.
As part of the process of making my phone a yakju I, of course, did a complete factory reset, although I did make a copy of my entire SD and transferred everything over again after the process.
These past two weeks I've tried the following to fix it:
Clear cache partition in recovery.
Clear google services framework.
Clear media storage.
Tried to uninstall many apps, 2-3 a day, to see if they were causing it, re-installing them when I still had the same problem. If it's an app causing this I've yet to find it, but I find it weird that an app could be causing this.
It happens once a day, but never close to each other. It seems that some time has to pass before it can happen, and it only ever happens just after the phone is woken up, either by my alarm or by me opening the notification bar and pressing something there.
Please help me, this is unbearable.
Another thing, yesterday I tried to let it run without me pulling down the notification bar and pressing "settings", which would set off the freeze-reboot. I found that my phone would not freeze-reboot but very often it would "reload" app icons and widgets when I went around my homescreens. Where I can only see my wallpaper for half a second and then the icons/widgets appear. It would do this very often throughout my 1day 5hour uptime, and a couple of times I would try to force the reboot (by pressing "settings" in the notification bar), after the icons/widgets did the invisible/load thing and it didn't reboot. This must have something to do with it?
hi,
experienced this on my nexus s back then what i did is from recovery>mount and storages>formatted system, boot, and everything else except sd card.then it was all gone.btw you will have to flash your rom and kernel again as this is a full wipe.hope i helped and do this on your own risk
daff
bump
did it cure your reboots?
daff
dark06 said:
did it cure your reboots?
daff
Click to expand...
Click to collapse
I haven't tried that yet. I'm trying a "RAM booster" app to see if that helps, but that doesn't sound too stable even if it does.
I'm going to do a full factory reset and installing nothing, or moving anything to the SD, and just let it run like that to see if it works.
Just writing an update for anyone googling themselves here with the same problem, I had it resolved.
I found out that if I didn't force the reboot (by turning on the phone and quickly pulling down the tray and pressing something there) it could last a long time with just the launcher resetting, but it would lead to complete freezes (anywhere I was on the phone) and would require a battery-pull.
My plan was to wait for jelly-bean before doing another factory reset, I got the JB update and it completely removed the problem. I still don't know why the problem suddenly started or what caused it, all I know is that the JB update fixed it, and the update is fantastic, my phone's never been better.
Hi all!
I'm running CM11 24.06 nightly, along with Devil3 kernel on my n7100.
I've recently updated from 06.06 nightly (I believe), which was a fresh install (full wipe, no updates before), but I have had this issue before already. I think it starts to happen after I perform an update to the newest nightly. Rolling back to previous one doesn't help - another full wipe and fresh install is required to fix this or at least I didn't find a solution.
So, what's the issue? There are four issues that, to me, are connected:
1. Waking up - I'm experiencing serious lag when waking up the device. Sometimes the device doesn't want to wake up for half a minute, sometimes it doesn't wake up at all and it requires me to restart it by holding the power button
2. Lag after unlocking - Most of the time though, when device is actually successfully woken up and I want to fe. go straight to SMS app from lock screen and type something immediately, phone freezes for a second and when I'm able to type (touchscreen reacts, letter-press animation plays) - the letters aren't appearing. Sometimes it takes a while after I can type, sometimes I have to close the app. I've tried different SMS apps, deleting big conversations, different keyboard apps (I'm using SwiftKey, but stock app is the same - this one actually remembers what I type, recommends me something, but when I tap to use the recommendation, nothing is being typed into the text box) and some other things.
3. Application start up time and white status bar - Apps are starting to drop in performance as well. For example, when I run, let's say Play Store, the status bar on top of the screen is flashing white and it takes a bit longer to be able to use them (just like the SMS app).
4. % battery usage of certain (unexpected?) apps - Most battery hunger process is Android System. I've reset battery stats, for the last 1h and 45min used phone to type 2-3 messages, and it's usage is @27%, whereas 2nd process is screen with 18% and 3rd is Android OS with 11%.
Restarting the device seems to temporarily fix first three issues. They start to come back as soon as I start using the device, like opening apps, etc.
As I said before, it all happens after performing an update. Maybe I'm doing something wrong? I usually flash the update, restart device, go to recovery, flash kernel and restart. Since the issue happened again, I've tried to flash the new nightly and kernel together before, it didn't help. Clearing cache/dalvik is not helping (before, after).
I don't have any backups made (I know, I should've made one), so, I guess I'll prolly end up performing a full wipe again. But does anyone have some ideas what may be causing this? So I can prevent this for good next time, hopefully.
Ksenios said:
Hi all!
I'm running CM11 24.06 nightly, along with Devil3 kernel on my n7100.
I've recently updated from 06.06 nightly (I believe), which was a fresh install (full wipe, no updates before), but I have had this issue before already. I think it starts to happen after I perform an update to the newest nightly. Rolling back to previous one doesn't help - another full wipe and fresh install is required to fix this or at least I didn't find a solution.
So, what's the issue? There are four issues that, to me, are connected:
1. Waking up - I'm experiencing serious lag when waking up the device. Sometimes the device doesn't want to wake up for half a minute, sometimes it doesn't wake up at all and it requires me to restart it by holding the power button
2. Lag after unlocking - Most of the time though, when device is actually successfully woken up and I want to fe. go straight to SMS app from lock screen and type something immediately, phone freezes for a second and when I'm able to type (touchscreen reacts, letter-press animation plays) - the letters aren't appearing. Sometimes it takes a while after I can type, sometimes I have to close the app. I've tried different SMS apps, deleting big conversations, different keyboard apps (I'm using SwiftKey, but stock app is the same - this one actually remembers what I type, recommends me something, but when I tap to use the recommendation, nothing is being typed into the text box) and some other things.
3. Application start up time and white status bar - Apps are starting to drop in performance as well. For example, when I run, let's say Play Store, the status bar on top of the screen is flashing white and it takes a bit longer to be able to use them (just like the SMS app).
4. % battery usage of certain (unexpected?) apps - Most battery hunger process is Android System. I've reset battery stats, for the last 1h and 45min used phone to type 2-3 messages, and it's usage is @27%, whereas 2nd process is screen with 18% and 3rd is Android OS with 11%.
Restarting the device seems to temporarily fix first three issues. They start to come back as soon as I start using the device, like opening apps, etc.
As I said before, it all happens after performing an update. Maybe I'm doing something wrong? I usually flash the update, restart device, go to recovery, flash kernel and restart. Since the issue happened again, I've tried to flash the new nightly and kernel together before, it didn't help. Clearing cache/dalvik is not helping (before, after).
I don't have any backups made (I know, I should've made one), so, I guess I'll prolly end up performing a full wipe again. But does anyone have some ideas what may be causing this? So I can prevent this for good next time, hopefully.
Click to expand...
Click to collapse
i think this kernel issue..mybe u should stay with stock cm kernel..
Sent from my GT-N7100 using Tapatalk
Azhery said:
i think this kernel issue..mybe u should stay with stock cm kernel..
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Well, like I said, everything is working fine after a fresh install (with full wipe prior to it), is it possible for kernel to cause that after a nightly update?
Ksenios said:
Well, like I said, everything is working fine after a fresh install (with full wipe prior to it), is it possible for kernel to cause that after a nightly update?
Click to expand...
Click to collapse
mybe problem on nightly..do you hve try other cm based rom?
Sent from my GT-N7100 using Tapatalk
Azhery said:
mybe problem on nightly..do you hve try other cm based rom?
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Some time ago I had OmniRom and after few OTAs I actually started noticing similar issue if I recall correctly (that was the reason for me to switch back to CM).
mybe u try..full wipe..wipe data..wipe cache..wipe system..wipe internal storage..
Sent from my GT-N7100 using Tapatalk
But that's the point, I'll probably end up doing it since restarting my phone every 30-60 minutes is out of the question. But, then what? every few nightly/snapshot I'm gonna perform a full wipe?
Ksenios said:
But that's the point, I'll probably end up doing it since restarting my phone every 30-60 minutes is out of the question. But, then what? every few nightly/snapshot I'm gonna perform a full wipe?
Click to expand...
Click to collapse
mybe u can try other rom like cyanogenmodx..bcause i nver had this issue..
Sent from my GT-N7100 using Tapatalk
I was actually thinking about it, but as I said, when I used OmniRom few months ago, I recall that I had similar issues. Nevertheless thank you for your insight. Anyone have any slightest idea what might be causing such behavior?
I seem to have fixed the issue. Turns out the culprit was Business Calendar - Business Tasks to be more precise. I unistalled both and so far didn't experience those wake up lags.