Related
HI,with respect to user's , admins n DEvelopers i would like to say SOD might be due to the sleep time settings (image attached)in brightness.i might be wrong or might not be,if im wrong sorry in advance n would req. the admins to delete this thread,Tnx to all..
EDIT :
Use mattcfroyo 1.4 (with latest cotulla zimage) or DARKSTONE froyo v1 latest(384ram enabled)
[my preference] with windows rom: chuky gtx/chukydroid/miri17.6
and radio 2.10.50/2.12.50 no echo no robovoice no sleep of death evrything is fine
Well have you tried experimenting with it? I don't know if thats the issue or not, but I am desperate to get rid of that SOD issue
Stoferr said:
Well have you tried experimenting with it? I don't know if thats the issue or not, but I am desperate to get rid of that SOD issue
Click to expand...
Click to collapse
thats y i let this info to other users let see what happens to them,n i dont hav n SOD problem but i have robotic voice :"S too bad cant get rid off it,can u sggest me a ROM,m using updated tmous ROM n radio 2.12.50.xxx.. tnx in advance.. and lets see what others say with sleep turned of.. and please do share your results... thank u..
Im testing it right now, so far no problems, but it seems randomly whener SOD appears, so i'll just test it a little longer.
Im using the european HD2.
hmm.. Lets see the results of other users also... and please do share ur findings...
P.S: m using TMOUS HD2 and waitin when i can get rid of robotic voice.
Damnit just got it! Well, seems that this won't help It was a nice try tho
i have never had sleep of death its gta be rom and radio related
i tried to help all... thats all.. but tnx for tryin... but i dont hav SOD either.. now dloadin maatcleo+froyo v1.2 n gonna test if it has SOD..
robotic voice is killing me :'(
I've had sleep of death with basically every android build out there.. i don't think it's a setting in my personal opinion. i think it is because it's still in develoupment and the drivers aren't 100% yet.. and i'm sure in time it will be fixed.
I tried it on zimage 7/25 and still have SOD .Some claim they use the new zimage without SOD ,no matter what I do it won't wake up.
the battery is horrible on 7/23 zimage and carrying the charger in my pocket all the time is a pain.
Off topic: I loved the notes on dna u had there
The "Turn screen off" setting is active in my WM. Using German T-Mobile 1.72 ROM, Radio 2.10.50.19_2, Dan's Froyo V1, zImage 25/7.
Using this combination for two days now and didn't have a single SOD during this time... only two or three times a freeze for few seconds, but afterwards Android resumed working.
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Been using dans13 build with cotullas no speddy zimage. My Rom right now MIRI 17.6 and Radio 2.12.50.26. No SOD report here just couple of freezes now and then. Good battery life. I have to say that I disabled the Auto lock in Windows with HD2 tweak. The first time I tried android on hd 2 i got the SOD, but with this combination and disabling the auto lock been running smoothly. just my 2 cents.
reocej said:
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Click to expand...
Click to collapse
Well what I don't get is when I started trying Android on my tmo hd2 I didn't get the sod but now I do. if its the screen why did it start now?
Daaaaaaaaaaaaaaaaaaaamn waiting for new zImage... Seems that I have a sharp panel... How can I check this?
reocej said:
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Click to expand...
Click to collapse
well now im using miri's v17.6 rom wid radio 2.12 on tmous HD2 no SOD till now although sleep is active in WM...
reocej said:
Sod is related to the Sharp branded lcd panels which are in the Tmo US phones and some of the later batches of the Euro HD2.
Click to expand...
Click to collapse
I've read the same but i think a lot of it is just down to individual ROMs & radio builds, as when android started on hd2 everyone said turn off backlight but mine was never on high nor did i alter any settings as when haret kicks in it turns off all windows functions altogether so you can't have any cross network/OS issues, winmo is supposed to be cut off. although saying that if android is only running off sd how can you remove sd and still run android for 1hr or more? but that's a different topic.
If you have a Tmo US HD2 just use Cotulla's 7/23 zimage and you should not get sod. If you use 7/25 zimage, you WILL experience sod! If you experience sod with 7/23 zimage, then the likely culprit is your sd card. Reformat and try again. If that doesn't work, you need to try a different card.
I am using the 7/23 with chucky's rom, and i was fine all day yesterday but this morning i got 4 sod in 15 minutes, and everytime i rebooted after that. I changed my Radio to 2.12.50.02 and i turned off the sleep thing in WM, and so far haven't had a sod in about 3 hours.
Hi
I know, was discussed so many times...but because of just this, I'm confused as hell. Whenever my batterycharge is quite low, my phone starts to hang pretty frequently...the touchinputs at least. I noticed, that this happens, when I walked a bit with my phone. So my guess would be, that the g-sensor is overloaded and that freezes the touchscreen. I know, there are Kernels that deactivate the g-sensor, but it's a handy tool for screenorientation. So, is there a fixed kernel which leaves the g-sensor activated but removes the touchscreen-freeze bugs?
Hope someone can help me.
Greetings
NessD
wow ... i didnt know the battery charge has play in this ... i guess ill keep it better beefed up ... thanks for da tip
Its still a mystery to me. Because a lot of people seems not having this issue anymore.... Not me, with the last radio, trying wm roms and several builds. Like you, it is very hard to walk typing a sms. Ok I will not be hit by a car but its still frustrating hehe
Yeah, I just noticed that I get those problems when 2 cases are given: Low Battery Charge (full battery is no problem) AND when the HD2 moves around alot. I get touchscreen freezes then. Either one for it's own is no problem, but both keep producing the freezes.
I haven't had ANY touchscreen freezes using hastarin R8. It's actually probably the best one ive used. No touch screen freezes and the auto brightness works on CM6.
No kernels have fixed this yet, some builds claim "no g-sensor freezes" but they do. (or at least they do for me, i'm not doing something wrong am i?)
mmduluth said:
I haven't had ANY touchscreen freezes using hastarin R8. It's actually probably the best one ive used. No touch screen freezes and the auto brightness works on CM6.
Click to expand...
Click to collapse
Hastarin r8 does not work for me...using Hyperdroid v1.7, can't get data to work...
Experimental kernel released that (should) fix this.
http://forum.xda-developers.com/showpost.php?p=9194473&postcount=140
I can confirm it finally works. Today is a great day for the community
My phone will randomly shut down and will not power back on unless I pull the battery, I have 2 batteries and it happens with either one. It does not shut down while on charger/dock. I have wiped the phone multiple times with odin, I've used several different roms/kernals,same results every time. Just curious if anyone else has been experiencing this issue.
I've been experiencing this after I went to eb13 with the custom kernels that are out. But my.phone will either lockup and I have yo pull the battery or it will reboot itself. Never had what happens to u yet.
Sent From My Evo Killer!
This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha
nalewis89 said:
This has been happening multiple times a day to me. Completely at random. its beginning to become unbearable. My phone will lock up like this about 8-20 times in a day. Someone save meee! hahaha
Click to expand...
Click to collapse
I'm averaging 10 times a day myself
Permanent sleep
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.
before updating to 2.2 - I did the DK28 and now the EB13 one - with 2.1 I would have my phone randomly reboot - I would be sitting there and here the music it makes when it starts up but I never turned it off?
other times it would just be turned off, but when I turn it back on the abttery is not low enough to cause it to turn off
all this went away with DK28 2.2 and hasnet happened since I installed EB13 2.2
This happeed to me the other morning. I wasn't able to boot until I reflashed the kernel. Twilight frozen btw.
Sent from my SPH-D700 using XDA Premium App
My first epic would randomly hard power off, even running stock ROMs. If you are running a stock ROM and seeing a hard power off at random, I suggest you go swap the phone. It's just broken.
Ive never had this problem and im on my first and only epic and ive had it since it came out,
Ive been very careful with my epic as it has been great to me, it hates me probaly tho for feeding it stuff while experimenting things that make it spit up FCS,
But my phone has been always working perfect, all the way back to d118.
CLazman said:
I may have experienced a similar problem, running a DK28 based kernel with both Quantum 2.5 & 2.7 ROM's.
When the phone sleeps and you're not able to wake it, do the 4 buttons at the bottom of the screen still light up? If they do then I have had the same issue. I could only narrow it down to restoring apps+data or putting the phone in sleep while an app is running. Once it was the result of putting the phone in sleep after a FC.
I can only posit that it MAY be an ext4-only ROM related issue, considering I did not have the above situation occur with rfs ROM's or rfs/ext4 dual ROM's. In addition this was only limited to DK28 for me. I was off DI18 <16hrs after I bought the phone. The DK28 gps issue was a non-factor as well, occurred whether gps worked or not.
Click to expand...
Click to collapse
the buttons don't stay lit, i'm using twilight kernal right now but was happening with genocide kernal too, going back to eclair just to eliminate 2.2, ext4, etc.. to see if it's a hardware issue
First try
dk18 update.zip flash
Restored apps and data with my backup pro root
Random reboots, FC
Second try
Odin to dk18
Wipe x3
Restored apps and data with mybackup pro root
FC, music player force closing (doubletwist, stock and musicmod, poweramp worked though?), fc when trying to change ringtone or notification.
Started reading about others with the same issues and thought data backups were a reoccuring theme. Did a third try tonight and so far so good. Music players working, no force closings, keyboards working correctly, gps lock indoors. Its still early, problems might still popup, thought id share...
Latest froyotempt
Fresh backup with mybackup pro root
Wipe x3
odin eb13 prerooted (ctsy xda forum) same file from attempt 2. Did this x3 as well, read it in a thread somewhere...
backup apps only with mybackup pro root
All attempts were with genocide kernal.
So far so good, none of the previous bugs are apparent, so far... Those of you that are on the fence regarding doing the same, so far its worth the time.
Sent from my SPH-D700 using XDA App
I was thinking back-ups were part of the problem also, so I used odin and started all over from dl18 without restoring any data, same problem still occured
Still messing with my phone, everything that was broken seems to be fixed. Hopefully it stays this way...
Sent from my SPH-D700 using XDA App
That used to happened to me on eclair when I set my setcpu profiles too low when screen off. You wouldn't happen to be using setcpu would you?
actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800
I'll add to this thread. I seem to be having the same problem and I believe it started when I installed quantum rom... but I'm not sure. The symptoms i had were random reboots, where the screen would shut off and the 4 lights would stay on. Then I would have the sound of lost signal as if my phone rebooted and was starting over. Also, the most recent problem I get is my phone completely shuts off and I need to battery pull to get it to start up, and it loops on the splash screen of my rom. I have tried doing a complete odin wipe and not restoring anything and I believe it is still happening...
joedig52 said:
actually I am, I have my minimum down to 200 MHz, going to raise it and see if that helps
@400 MHz did it again, trying 800
Click to expand...
Click to collapse
Any update?
Also, make sure the governor isn't "powersave". If you have 100-400MHz powersave governor, it still ONLY runs at the lowest speed (100MHz), even if it's 100-400MHz.
Still happening, not on powersave, doesn't matter what settings I have in set cpu. Did a hard reset back to 2.1 and it still happens, bringing it in for repair.
Well it seems as a new member I can't post in the Dev section yet, so I guess I will post it here:
I have been having issues much like others with this rom locking the phone completely up. Most of the time, when I wake the phone the screen is upside down and has graphic artifacts on the screen. This of course causes me to have to pull the battery. Once the phone comes back up, I can literally hit the power button on/off about 10-12 times and it happens again. I have reinstalled the rom and followed the instructions for flashing the ROM 31 times (i keep a journal of it). I am still having the same issue. I have tried Faux's LV and the SV version of his kernal and have even gone back 3 previous version (tried both versions so, 8 kernals in all) and still have the same issue. Now a buddy of mine suggested turning the "screen animations" off, and since I have done that I haven't had the phone lock up on me anymore, however the lockscreen does occasionally flip 180 degrees, but simply hitting the power button off then on and it is ok.
That seems to be my only issue with the rom. I really wanted to post in the dev section, but I guess I have to get my post count up before I can help contribute to the thread.
Thanks again TeamRoyal for another AMAZING release, and I also appreciate you folks assisting us with our minor issues. Keep up the good work, and thanks again for your folks assistance.
gitm said:
Well it seems as a new member I can't post in the Dev section yet, so I guess I will post it here:
I have been having issues much like others with this rom locking the phone completely up. Most of the time, when I wake the phone the screen is upside down and has graphic artifacts on the screen. This of course causes me to have to pull the battery. Once the phone comes back up, I can literally hit the power button on/off about 10-12 times and it happens again. I have reinstalled the rom and followed the instructions for flashing the ROM 31 times (i keep a journal of it). I am still having the same issue. I have tried Faux's LV and the SV version of his kernal and have even gone back 3 previous version (tried both versions so, 8 kernals in all) and still have the same issue. Now a buddy of mine suggested turning the "screen animations" off, and since I have done that I haven't had the phone lock up on me anymore, however the lockscreen does occasionally flip 180 degrees, but simply hitting the power button off then on and it is ok.
That seems to be my only issue with the rom. I really wanted to post in the dev section, but I guess I have to get my post count up before I can help contribute to the thread.
Thanks again TeamRoyal for another AMAZING release, and I also appreciate you folks assisting us with our minor issues. Keep up the good work, and thanks again for your folks assistance.
Click to expand...
Click to collapse
That's strange did you do a full wipe and format sd card along with boot and system and followed there instructions about not touching it on first boot and all. I did that and had no issues. I'm running RC2 because I just like it more and have no issues so thats something else you can look into
I've had the exact same issue when using RC2 with faux's kernel. I've tried the LV and SV versions and still had the same problem.
Finally I gave up and just reinstalled RC2 without faux's kernel and I have not had any issues.
Sent from my HTC Glacier using XDA App
Tazzaras said:
That's strange did you do a full wipe and format sd card along with boot and system and followed there instructions about not touching it on first boot and all. I did that and had no issues. I'm running RC2 because I just like it more and have no issues so thats something else you can look into
Click to expand...
Click to collapse
Yea I have wiped and formated everything. The install I am now on I actually waited a full 30 mins instead of recommended 5 min.Nothing against teamroyal as I have mad respect for what they do, but RoyalGinger has made me a pro at installing it
So far no kernal crashes, which has given me a perma-grin. I'm gonna flash back to the latest LV version of faux kernel (the one that came with it). I'm sure it will be fine as I think the whole problem has to do with the screen off animation. I'll report back with my results.
Update:
It is the screen off animation that is causing my issue. I have flashed the latest kernel and everytime I have the off animation on, it locks. On screen animation works when on by itself, but turn the off animation on, power on and off a couple of times, and it will crash. I'll try to grab the logs and submit them.
Well seems everytime usb debugging is on it simply won't crash, and I can't get emulator to record when the phone crashes. Sorry I can't get a logcat
Same here on my wife's phone. Had to restore a 2.3.2 nandroid because both (CM7 rc2 and RG 1.3) were freezing on wake. Dunno what the cause is because on my mytouch RG 1.3 runs fine since it dropped......
If u read thru the post for Royalginger 1.3 it says that the best kernel for the rom is the kernel that it comes with... it also says u will get best/smoothest response with it set at smartass... I'm not sure if its changed since I've read but give it a try...
Sent from my HTC Glacier using XDA Premium App
So the good news is I was able to get a logcat. I didn't realize that when the phone completely freezes (power on/off does nothing) you can still dump the logcat, hooooray for me. So here is my logcat file, and for the record this ONLY happens when I have the off and on screen animations enabled in the "CyanogenMod settings", with them off I can power on and off without the phone crashing.
[ROM] - RoyalGinger 1.3
[Kernel] - version 2.1.0 Low Voltage
[CPU Frequency] 245~1113
[Governor] Smartass
[Theme] - Honeybread (CM7 honeycomb theme)
[Live Wallpaper] - None
Update:
I did what was instructed in the dev section for flashing the latest Faux Kernel (2.1.2.1). I wiped the cache and delvikcache. I then fixed permissions and installed the kernel. Once the phone got to the lock screen, I waited 15 minutes for the kernel to "settle", immediately rebooted and let it sit for another 15 minutes.
Once that was I done, I enabled both the on and off screen animations, and after power on and off about 20 times, it crashed the phone again. So I am still having the same issue. Also as a heads up, I tried different themes just incase it was the theme, but that made no difference. So I reverted back to screen on/off animations as all off, and still no lockups. I have attached another logcat file, just incase there is some new data in it.
On another note, there simply isn't any last_kmsg file, so I'm sorry I can get you folks the file. It isn't on the phone when it crashes or even when the phone works correctly.
Have you done anything with spare parts?
Nope I haven't touched Spare Parts. I'm really trying to get this issue resolved before I setup anything on the phone. Maybe the 1.3.1 release will resolve the issue, but time will tell.
gitm said:
Nope I haven't touched Spare Parts. I'm really trying to get this issue resolved before I setup anything on the phone. Maybe the 1.3.1 release will resolve the issue, but time will tell.
Click to expand...
Click to collapse
gitm - 1.3.1 should be out by tonight, barring anything weird coming up last minute in testing
and this has the new 2.1.2.1 faux kernel built in but if you want to try in the mean time - go to his thread and flash that kernel (wipe both caches and fix permissions, then flash kernel, then settle for 5 mins on initial boot, reboot, settle another 5 min, then go)
can't remember, are you using stock launcher or a 3rd party?
Using launcher pro.
As for the new kernel, it is still causing the same issue. In my logcats, it says "cpu pegged", and that is pretty odd. Hopefully 1.3.1 will fix it, but I will keep testing and keep you posted
I have had mine for about 9 days now, and it has dose the sleep of death thing twice already... i am running Prime 1.5 it seems that peoples screens dont work after some sleeps of death... just wondering on it.
Optimus-Prime said:
I have had mine for about 9 days now, and it has dose the sleep of death thing twice already... i am running Prime 1.5 it seems that peoples screens dont work after some sleeps of death... just wondering on it.
Click to expand...
Click to collapse
I know that when I installed Prime 1.5, I get "Sleep of Death" every hour... I went back to stock and "Sleep of Death" went away... I'm not sure if this issue was fixed yet. I was told last week that it might be kernel related issue. But in the meantime, you can also try a different kernel and see if that fixes the problem... If not, try a different rom or even use Prime 1.4. Worst case is to go back to stock 3.1.
I'm still using stock rom right now and plan on using it for a while...
ill have to give stock a test drive. i did see that when i changed roms i did get sleep of death.
we can just flash a CWM stock rom right?
I had this problem for the first time today. I'm on Prime 1.5.
I also had no sound when I got it back on. Had to reboot to get the sound back.
Any similar sound/sleep of death issues?
Any new information on a permanent fix for this?
Thanks.
ASUS is working on a fix for this. It has something to do with 'power management.'
Just wait patiently while they release a OTA to fix this and then devs will also incorporate this fix within the ROM.
I had it nearly every time I left the tablet on for more than an hour without touching it. Upgraded to stock 3.1 and it hasn't happened since... (I manually flashed it; didn't wait for the OTA if that matters..)
My first TF suffered a SOD but I think it was a screen of death not sleep of death. I could never get it back so I replaced it at TigerDirect. My current solution? I pushed the TF off to the side of my desk and bought a Xoom...
zephiK said:
ASUS is working on a fix for this. It has something to do with 'power management.'
Just wait patiently while they release a OTA to fix this and then devs will also incorporate this fix within the ROM.
Click to expand...
Click to collapse
I read Asus saying they were fixing hte dock draining issue, nothing about the sleep of death. I have never had this happen, though I'm on stock, and form the looks of it the peeps that are on custom roms have this issue so doubt they'd fix a non-stock problem.
zephiK said:
ASUS is working on a fix for this. It has something to do with 'power management.'
Just wait patiently while they release a OTA to fix this and then devs will also incorporate this fix within the ROM.
Click to expand...
Click to collapse
I also only saw reference to the dock issue being fixed in an OTA. If you have a link to any information about the fix they are working on, it would be most appreciated.
Thanks.
So i replaced everything with stock, and no sleep of death yet to happen. but i have been using it alot lately so ill let it chill for about the next 2 hours and see what happens.
Optimus-Prime said:
So i replaced everything with stock, and no sleep of death yet to happen. but i have been using it alot lately so ill let it chill for about the next 2 hours and see what happens.
Click to expand...
Click to collapse
Thanks... let me know if it works for you.
Bought my TF a week ago, with 3.01, NEVER has seen SOD; today -finally- OTA upgrade to 3.1 in the Netherlands; since upgrade SOD every time TF goes in sleep mode..
Great upgrade, thanks ASUS! Any solution (except downgrading) around, plz?
Last nights OTA update fixed my deep sleep problems. This update apparently included a power management fix.
I've had my transformer for 2 months now. I had it stock, always updated OTA, until the NVflash/APX mode rooting method appeared and then I flashed PRIME! v1.4 and never had any SOD until recently when I upgraded to PRIME! v1.5. However, I did two other things around the time of the v1.5 upgrade that could equally have started the problem, namely; I started using a 16GB SDHC card in the keyboard dock and I also connected HDMI to my TV for the first time using a C-to-A adapter (this also does not work properly - uinstable image - intermittent digital interference flickers along the bottom of the screen).
I have since re-flashed PRIME! v1.5 using the APX/NVflash method and have stopped using the 16GB SDHC card in the dock and now the SOD has stopped happening..... HDMI is still an issue but that could be the cable and/or adapter.
Deep sleep , could it be tegra 2 issue?
the Folio 100, the toshiba thrive and Asus TF has this problem. all of them have Tegra 2. if i set the folio 100 to 30 minutes before sleep i can use it as long as i don't let it go over 30 min before i wake up the screen. if i close the screen (via the button) i don't get deep sleep problem before 30 min has gone. so there is some problem related to the CPU and memory going to deep sleep and can not get interupts from the button anymore
My SOD seems to only happen when it's attached to the keyboard dock. If I leave it undocked, it never get's the SOD. I'm on a replacement dock, and the original dock I had never gave me the SOD either.
I have the latest firmware installed and that didn't make a difference.
No dock. But had my first SOD with Prime 1.6 + Netformer and IO fix OC'd to 1.5
My first post so I'm locked out of development forum with the relevant thread
http://forum.xda-developers.com/showthread.php?t=1070343&highlight=waking+sleepsleep+of+death
Anyway, had my TF for only a couple of days, goes to SOD two-three times a day already. I didn't play around with 3.0 much before doing OTA to 3.1 but 3.1 and now 3.2 still put it to this unnatural sleep.
Actually, it didn't wake up after updating to 3.2 itself.
From reading that thread the best probable cause appears to be the voltage issue when CPU clock speed changes - when waking form sleep clock speed goes up but voltage doesn't or something like that, and if some processes are left running, like logging to a file, the system never really goes to sleep so no problem with waking but a problem with catching the culprit.
Someone also said that in 3.2, by design, there should be even more sudden clock speed increases so SOD problem might become even more frequent.
One more possible argument for the voltage theory - SOD doesn't happen when TF is charging, meaning that CPU management is not that strict. Someone reported that Juice Defender, the app to minimize power consumption/CPU load, actually caused SOD on his TF.
The actual cause of SOD is a failure to get the correct value for blacklight on waking so looking at the display closely with a flashlight one still can see it running, allegedly, and can even unlock it. If that happens and the system is otherwise responsive maybe there's a way to force the backlight on, maybe some widget that toggles autobrightness on something. I'm waiting for my next SOD to test this theory, sometimes the screen doesn't look black, simply not light enough.
Maybe all I've said is nonsense but I'm an unrooted noob, I'm allowed.