Related
I updated to CM 7.1 RC1 last week and I've noticed a few times where the device has locked up after "going to sleep". Essentially, if I leave it on the coffee table with WiFi on and let the screen turn itself off, it won't respond when I return to it 20-30 minutes later. I have to force reboot via the power button + nook button.
Just curious if anyone else has noticed it or if it's just me. If it's a common issue I'll escalate to the CM folks, if it looks like just me I'll start the long and tedious process of uninstalling apps one by one. =)
I have at least one every day. I figure its just a price I pay. Over all its the best rom I have used.
Sent from my NookColor using XDA Premium App
Only once have I had the issue you described. I leave WiFi on some of the times, but majority of the time I have it off when I am done using it. I know some people have mentioned using Tasker or something similar to turn WiFi off when screen goes off so that it can perhaps be prevented.
EDIT: I don't believe I can link yet on my account, but search General for the post "NC, CM7, Dalingrin OC kernel.. Sleep of Death" and start about post #6.
Thanks bio, that looks like the exact issue I'm experiencing.
For the next guy with this issue: Link to the thread biohazard mentioned
Installing Droid wall has fixed the problem for me and has doubled my battery life
Sent from my NookColor using XDA Premium App
mrkavanagh said:
Installing Droid wall has fixed the problem for me and has doubled my battery life
Click to expand...
Click to collapse
That's a pretty generic statement... what did you blacklist within Droid wall to increase battery life / fix the issue?
I'm facing random freezes when I open an application like tweetdeck or mercury and leave it updating from the internet. After some time, I'm not using it, it just stucks. To get it back to life I have to press for a few seconds the power button to shutdown it and then again to power it on. I have used different nightlies, voltages or governors but it is still here.
Now, I don't have freezes since yesterday that I really reduced the voltages but I'm not sure if my problem is solved.
configuration: 144 nightly 300-1100mhz xlv profile
not sure if anyone has told you that what you describes is called:
Sleep of death.
Felt to be possibly related to wifi being on all the time. In wifi settings, go to advanced change it wifi to off when screen off.
skylar.sutton said:
That's a pretty generic statement... what did you blacklist within Droid wall to increase battery life / fix the issue?
Click to expand...
Click to collapse
I'm sorry. I use the white list feature and only check mark the current application that I want to use and allow to access the internet. It keeps everything else from using background data.
For example right now I selected xda and updated rules.
Sent from my NookColor using XDA Premium App
Phatdawg said:
not sure if anyone has told you that what you describes is called:
Sleep of death.
Felt to be possibly related to wifi being on all the time. In wifi settings, go to advanced change it wifi to off when screen off.
Click to expand...
Click to collapse
It seems that I solved it reducing the voltages. When sod occurs a black screen appears right? I never had sod, only random freezes.
Sent from my Nook Color
Not sure how to search on the XDA app, so please forgive me if this is already a topic... does anyone have any tips/tricks for avoiding the Sleep Of Death?
-XDA Premium on CM7 Nook Color
What version CM7 are you on?
Latest SOD fixes were put into a kernel which is available as separate zip but have not made it into a nightly build as the build has not been working since mid November.
You may be able to use the kernel update if you are on a fairly recent version or you could switch to the KANG MiRaGe ROM which does include the kernel fix together with other improvements which have not made it into a nightly. Look for the main MiRaGe thread in the development forum.
Other than that before applying this kernel fix people were using various techniques for switching wifi off rapidly when suspending which seemed to be a work-around.
I haven't had a SOD since using the new kernel when it first appeared and as now as embodied in MiRaGe.
I'm on cm7.1.0, I don't get SOD all the time just on occasion without pattern
-XDA Premium on CM7 Nook Color
Widgets...
Don't use Beautiful Widgets. That causes SoD's. Other widgets may cause the same problem.
I have found that every widget that has weather causes SOD for me. All others are okay.
Sent from my NexusHD2 using xda premium
I had to switch ROM's from MIUI to Phiremod to get this to stop. Works fine now even with Beautiful Weather Widget active.
The KANG ROM you describe is the one I have been on since it was introduced. I had the SOD fix but it still occured albeit infrequently. My "fix" is to just shut my Nook down every night. I haven't had one since.
Setting wifi to shut off when screen goes off also works for me (the issue seems to be wifi related). You can also use tasker to shut wifi off when the screen turns off.
Both beautiful widgets and the go weather widgets have caused the sleep of death for me. Without any widgets, my Nook would be up for weeks at a time.
stephen_liu said:
Setting wifi to shut off when screen goes off also works for me (the issue seems to be wifi related). You can also use tasker to shut wifi off when the screen turns off.
Both beautiful widgets and the go weather widgets have caused the sleep of death for me. Without any widgets, my Nook would be up for weeks at a time.
Click to expand...
Click to collapse
Indeed the tasker wifi fix worked for me
-XDA Premium on CM7 Nook Color
vessamj, could you explain what you did with Tasker to prevent SOD?
Quick Tasker fix for SOD
Thomas Droid said:
vessamj, could you explain what you did with Tasker to prevent SOD?
Click to expand...
Click to collapse
Certainly...
I'm assuming you have a basic understanding of how to use Tasker, if this is not so please let me know and I'll be more in-depth. I created a profile named WIFISLEEP with the condition being "Display Off". The first step of the internal task is to wait 5 minutes, with the "IF" box checked and the "IF" condition reading "%SCREEN ~ off". The second step is to set Wifi to off, with the same "IF" condition as the first step. The third step is to play a notification sound (not required, but nice to be assured that your profile actually executes), with the same "IF" condition as the first two steps. I already had a "Display On" profile (for setting the CPU governor and speed), so I just added the next part to the pre-existing profile. If you don't already have such profiles you can just create another profile (named something like "Display On"). The condition, of course, being "Display On", and the first task being "WiFi set On" with the "IF" condition being "%SCREEN ~ on". The second task being "WiFi Net Action Reconnect", with the same "IF" condition as the first task. Not only does this fix my SOD problems, but it will also save you quite a bit of battery when not in use for long periods of time. There will be a slight (10-20 sec.) delay waiting for the WiFi to reconnect after you turn the screen on (as long as it's been more than 5 min of course), but it's definitely worth it. The reason I have a 5 minute wait is so that downloads can finish before they are cut off, you can set the wait time longer if your downloading times take longer. Overall, this did the trick for me on SOD.
*EDIT* I did also get ahold of a much better WiFi management application called Green Power. Instead of having Tasker turn off the WiFi after 5 minutes of the screen being off no matter what, Green Power throws in a few more conditions to look for. Through Green Power I have it set to turn off the WiFi after 20sec of the screen being off IF WiFi traffic is at 1Kb or less. If it is not at 1Kb or less, the app will re-check the traffic every 10sec until it is at or below that level, then shut it off. Also, while the display is off, Green Power will re-enable the Wifi for 2min every 30min to allow data sync to occur. When the screen is turned on, WiFi will be re-enabled automatically. However, if the device can't successfully connect (after 30sec) OR if the strength at connection is less than 20% signal, the WiFi will be temporarily disabled so that there is no battery wasted continually trying to connect/stay connected. This setup is perfect for finishing a download after the screen goes off and then putting the WiFi to sleep, and quickly giving up on the reconnect if there is low/no signal and trying again later. This also fixes the SOD for me, with better overall management than what Tasker can provide as far as WiFi is concerned.
Hey guys, just wanted to post what I used to fix my problems related to SoD.
I was getting SoD all the time with any ROM that I used, no matter 7.1.0 or 7.2. So recently i started fresh on a 7.1.0 stable rom and moved the ROM from SD to EMMC, but the problems still persisted.
After seeing this thread, it gave me some insight regarding the root problem... For me, it seemed that wifi being on when the screen was off was the culprit. So I downloaded the free app called "Easy Battery Saver+ Task Killer" found here:
https://market.android.com/details?...SwxLG51bGwsImNvbS5lYXN5LmJhdHRlcnkuc2F2ZXIiXQ..
I set it to the "General Power Saving Mode" profile, which basically turns off the wifi whenever the screen is off.
That seems to have fixed the problem, now I never get a SoD! So I recommend giving it a try!
If you are interested in my opinion...
switch81 said:
Hey guys, just wanted to post what I used to fix my problems related to SoD.
I was getting SoD all the time with any ROM that I used, no matter 7.1.0 or 7.2. So recently i started fresh on a 7.1.0 stable rom and moved the ROM from SD to EMMC, but the problems still persisted.
After seeing this thread, it gave me some insight regarding the root problem... For me, it seemed that wifi being on when the screen was off was the culprit. So I downloaded the free app called "Easy Battery Saver+ Task Killer" found here:
https://market.android.com/details?...SwxLG51bGwsImNvbS5lYXN5LmJhdHRlcnkuc2F2ZXIiXQ..
I set it to the "General Power Saving Mode" profile, which basically turns off the wifi whenever the screen is off.
That seems to have fixed the problem, now I never get a SoD! So I recommend giving it a try!
Click to expand...
Click to collapse
The problems I see here are that there is no WiFi traffic check (at least from what you've explained) before it kills the WiFi, and the Task Killer part. Task Killers actually cause more battery usage because the Android System will have to use more battery to re-start many of the killed processes. This is because the OS is programmed to keep some/most of those background processes running and will continually re-start them no matter how many times a task-killer stops them. It is better to have apps such as Ram Manager Pro (http://forum.xda-developers.com/showthread.php?t=1111145) or V6 SuperCharger script (http://forum.xda-developers.com/showthread.php?t=991276) to optimize your RAM for much better smoothness and crisp response, with much better battery savings. Combine one (or both depending on what parts you use for different activities) with Green Power app, which will give a hand-full of extra conditions to look for before turning off the WiFi at screen off and thus fixing your SOD and providing better performance with extra battery savings. I hope this helps!
I may have asked this before, but I'm not sure.
My A500 has a custom ROM on it, but its had this problem on multiple roms. I haven't tried on stock yet, but that's probably my next step. Anyways, here are my questions:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
When I first got it, I remember leaving my A500 in standby mode (it should automatically go into standby when you idle, right?) and being able to wake it by hitting the power button almost a day later. Now I can only do it for a few hours and then it won't come out of sleep. I'll have to turn it off by holding the power button down (even though there is no indication that it is turning off), then I can turn it on again. Sometimes my battery will be depleted, apparently indicating that it did not properly go into sleep mode?
chairhome said:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
Click to expand...
Click to collapse
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.
All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..
Moscow Desire said:
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.
Click to expand...
Click to collapse
erica_renee said:
All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..
Click to expand...
Click to collapse
Thanks to both of you. I needed reassurance that my tablet wasn't just messed up. I have a warranty on it and was thinking about getting it replaced and seeing how the new one behaved, but I'll try the suggestions. I'll probably try to reload my ROM after formatting and start with just the base apps and add one at a time as you suggested. If that doesn't work, I'll try a different kernel or ROM with a different kernel. I've already tried not using SetCPU to under/overclock, but that didn't work. Thanks again!
Another (relatively rare) issue is that the kernel you're using actually is flawed and fails to wake the GPU after it went to sleep (this may be a lot later than the device itself, depending on background services!). In this case using a different kernel will solve the issue (stock kernel is works).
EDIT: Posted at the same time... By all means try another kernel, this is a known evil with custom ones.
Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.
OK, before you take your tab back, personally, I wouldn't worry about it.
I have noticed, on some occassions, (yes, I do run stock rooted on occasion), that sometimes, the tab will get what we call the sleep of death. And usually, this may occur over a long period of time. Also, sometimes, I have to hit the pwr button several times, before it wakes.
+1 with the PP on overclocked kernels. This happens with the most recent ones.
Fortunately, System Tuner Pro, will increase MB voltages, so you don't get this.
If it does it again, and you are on stock, try to press the pwr button several times.
cool, thanks. I'll try this today.
chairhome said:
Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.
Click to expand...
Click to collapse
Mine has never worked on any rom with any configuration. Turning off wifi helps sometimes.
I have found the fix for SOD's on ICS builds (based on i9220 leak kernel)!!
THIS YOU DO BY YOUR SELF! I TAKE NO PART IF YOU HAVENT READ THIS THRU AT LEAST 2 TIMES BEFORE DOING THESE STEPS!
First of I had a theory of the i9220 kernel and its CWM that in one way it does not represent our hardware right. It has its differences and they are more on a file level then anything. This can be shown easy by trying to format /system. By doing so you will get in to a world of trouble (so don't try it, just trust me)
So my first thing as I have never had a SOD was try to RECREATE a SOD. So my theory is/was that the kernel provided for the i9220 is the real culprit in this scenario and that by flashing RADIOS with its built in CWM is a MISTAKE!
And boy was I right! I installed a random N7000 radio .zip thru CWM (Now when I say CWM I do NOT mean some crappy .apk or app that does it FOR you. I mean the CWM you enter by starting the phone with Power + volume up + home button) and rebooted the phone.
I played around with it and let it rest for 30min. When I was going to wake it up again... SOD!!
Mission Accomplished!! Recreated Error!
So now ... how to fix it...
First off wee need to learn how Mobile Odin works and why this method works to fix it. When Mobile Odin is instructed to flash a ROM or anything else (like a radio) it boots to ITS OWN KERNEL! That is the file that Mobile Odin downloads on first run!
Now IF you are going to use Mobile Odin while on any ICS build (except the original i9220leak! Important! Mobile Odin will NOT work on stock i9220 leak!) you have to be 100% sure that you are PROPERLY ROOTED!
So Steps...
Step1: Get ZCLP1.zip Radio from the Radio Thread and extract the modem.bin file.
Step2: Get Mobile Odin and just flash modem, nothing else. The modem.bin you just extracted.
Step3: It should reboot and enter the Blue Odin Droid Kernel and flash radio.
When its done it will reboot again. And you will probably be SOD Free!
Hit the thanks button if this worked for you guys. Thanks for reading.
Oh btw I don't think that it is locked to use only that modem. I had la3 radio before and I didn't suffer any sods so don't get to blind on just the Chinese radio...
| GalaxyNote ICS | Tapatalk |
im on midnight 2.0 ics.i done what u said in the post.i just had a sod.
here is how it happened.i pressed wifi in pull down notification.it was stuck ..wifi would not turn on after the screen turned off and try to awake by using power button.it was dead.it would not do anything.had to hold power button for couple of min to restart.
Im currently on gb, used ics for a couple of weeks since chinese leak. Im not a 100% sure, but i really think it has something to do with wifi. I never really tested but I always had the most sod at home while connected. Rarely had sod at work, which was cellular data H+.
There is another method and that is to increase min CPU speed from 200 to 500mhz. Has worked for some...
| GalaxyNote ICS | Tapatalk |
Thanks mate, i'm gonna try some of that.
These SOD are making me crazy :/ Some day i can have 0 SOD and the day after 1 per hour...
You can use Wakelock and no more Sod...
Sent from my GT-I9220 using XDA
super_sonic said:
You can use Wakelock and no more Sod...
Sent from my GT-I9220 using XDA
Click to expand...
Click to collapse
But wouldn't that drain the battery faster?
Sent from my GT-N7000
I only get sods when wifi doesn't activate too. If it doesn't switch on immediately then the phone won't come out of sleep. I just restart manually when this happens instead of letting it sleep.
Sent from my GT-N7000 using XDA
I get SOD with or without wifi completely randomly. I'm going to try increase CPU see if that works.
excuse me wt is SOD issue meaning ?
i know its a very stupid Que
but i hoppe to till me wt is it
thnx
It's not specific to the radio. I've done Mobile Odin Pro to try many different radios. Each time, I'd get an SOD.
Folks have also reported getting an SOD WHILE in Airplane mode. This completely puts the baseband issue out of the picture together.
If it's in airplane mode, it can't be a WIFI issue too.
The kernel itself is just bad and it has its quirks.
Due to the inability to get a logcat when it is in a SOD state, it makes it very hard to pinpoint what is causing the SOD.
MaZaGnGy said:
excuse me wt is SOD issue meaning ?
i know its a very stupid Que
but i hoppe to till me wt is it
thnx
Click to expand...
Click to collapse
SOD is Screen Of Death or Screen Of Darkness; meaning that the screen will not wake up up after you turn the phone on and you have to restart/reboot the device. Various things cause it... Have a search and you will learn more about it!
robmeik said:
SOD is Screen Of Death or Screen Of Darkness; meaning that the screen will not wake up up after you turn the phone on and you have to restart/reboot the device. Various things cause it... Have a search and you will learn more about it!
Click to expand...
Click to collapse
Nope, it's Sleep Of Death. The rest is correct
Sent from my GT-N7000 using XDA
We need a SOD-off app
Look for wake lock power manager in play store. It creates a wake lock, preventing deep sleep, and consequently a SOD. For the price of a low battery autonomy.
I was having lots of sod's on aosp v7 and the reason was not related to ROM. it was something to do with the cpu frequency and voltage in the chainfire ics kernel.
Steps I performed to reproduce.
1. Use setcpu or system tuner to set the cpu frequency to 500 mhz when screen off.
2. As soon as the screen is off you can see that note is not responding to keys. Sod reproduced !!!!
In my opinion it has some thing to do with the voltage at frequency 500 mhz, may be the voltage is a little bit less for that frequency and it refused to wake.
Hope it helps some one with the similar sods.
masiullah said:
I was having lots of sod's on aosp v7 and the reason was not related to ROM. it was something to do with the cpu frequency and voltage in the chainfire ics kernel.
Steps I performed to reproduce.
1. Use setcpu or system tuner to set the cpu frequency to 500 mhz when screen off.
2. As soon as the screen is off you can see that note is not responding to keys. Sod reproduced !!!!
In my opinion it has some thing to do with the voltage at frequency 500 mhz, may be the voltage is a little bit less for that frequency and it refused to wake.
Hope it helps some one with the similar sods.
Click to expand...
Click to collapse
We know that ICS leak comes from i9220 and that it's set to work at maximum 1200Mhz.
Now the question is - do i9220 and n7000 use exactly the same CPU ? If so, then we can rule out voltage problems - unless engineers at Samsung f....up.
For all it's worth, that's an early build leak...when official update will be here, i think our problems will be over as we'll just use the proper kernel with our ICS roms.
Akiainavas said:
We know that ICS leak comes from i9220 and that it's set to work at maximum 1200Mhz.
Now the question is - do i9220 and n7000 use exactly the same CPU ? If so, then we can rule out voltage problems - unless engineers at Samsung f....up.
For all it's worth, that's an early build leak...when official update will be here, i think our problems will be over as we'll just use the proper kernel with our ICS roms.
Click to expand...
Click to collapse
Is there any way or app which stops using certain frequencies.
Hello All,
I'm really not sure if this a bug or setting adjustment. When the phone goes in the sleep mode, it will not wake at all and I have to pull the battery. This happens intermittently and there is not one app that it does it the most. I have Zip's 4.03 on my phone, but it has been doing it with all the Zip ROMs. I've searched dev forum and I can't seem to find anything, so it's probably something with my phone. I tried to make adjustments the performance settings with both the built in set cpu and the setcpu from the market and it still happens.
On this last update, I formatted data and dalvik cache and flashed the ROM in CWM and the aroma installer came up with no problems.
Again... love the ROM and don't kill the posting Newb. Just trying to help out.
Thanks
Eric
cybereric518 said:
Hello All,
I'm really not sure if this a bug or setting adjustment. When the phone goes in the sleep mode, it will not wake at all and I have to pull the battery. This happens intermittently and there is not one app that it does it the most. I have Zip's 4.03 on my phone, but it has been doing it with all the Zip ROMs. I've searched dev forum and I can't seem to find anything, so it's probably something with my phone. I tried to make adjustments the performance settings with both the built in set cpu and the setcpu from the market and it still happens.
On this last update, I formatted data and dalvik cache and flashed the ROM in CWM and the aroma installer came up with no problems.
Again... love the ROM and don't kill the posting Newb. Just trying to help out.
Thanks
Eric
Click to expand...
Click to collapse
Im running the same as you and i haven't had a single reboot or it not waking up at all. Try this kernel and see if it makes a difference for you. http://forum.xda-developers.com/showpost.php?p=24214386&postcount=3
Shot of awesomeness v2-zip edition
ok...I followed all of the instructions and flashed the zip. I set the cpu at 1228/230. What is the best CPU settings with this kernel?
cybereric518 said:
ok...I followed all of the instructions and flashed the zip. I set the cpu at 1228/230. What is the best CPU settings with this kernel?
Click to expand...
Click to collapse
i use 1305 max 384 min on interactive ...i get great battery life. And make sure you use rom toolbox from the market. Its a great app to have.
yeah..I got the ROM toolbox. thanks for the settings..I will give them a try.
Another lock up
Hey em2drvr03,
I had another sleep lock up today. This time I noted what was going on with the phone when it happen for feedback. I was playing a radio station in the iheart radio app. My phone was in sleep for about 20 minutes when I tried to wake it. Even though I could not wake it, it was still playing the radio station with brief skips. My wifi was off and I was streaming on my 4G. My phone is responding better...it would sleep lock up more often on the old kernel.
Eric
cybereric518 said:
Hey em2drvr03,
I had another sleep lock up today. This time I noted what was going on with the phone when it happen for feedback. I was playing a radio station in the iheart radio app. My phone was in sleep for about 20 minutes when I tried to wake it. Even though I could not wake it, it was still playing the radio station with brief skips. My wifi was off and I was streaming on my 4G. My phone is responding better...it would sleep lock up more often on the old kernel.
Eric
Click to expand...
Click to collapse
To be honest i have never had any of those problems...i've been running zips 4.03 since it was released and no problems. I wish i knew what to tell you.
It's all good
It's fine. It's happening far less with the kernel update. Someone else mentioned it in Zip's Dev forum. They called it the "Sleep of death", so at least I'm not crazy...lol.