yashsingh1/xdaforums huggingface dataset:
[Samsung Infuse 4G] xDa.Fun:
Hi All,

Post about Screen of Death/Sleep of Death situations and methods to overcome with the ROM, Kernel, Apps information in this thread.

May be helpful for all.

Thanx

:-)

Sleep/Screen of Death may refer to situation when pressing the power button dont wakes the screen. Sometime phone may go to poweroff state automatically.
[Samsung Infuse 4G] xDa.Fun:
A useful Post from Zen Arcade

"I started noticing SODs when the EDT locks first showed up. I do not get them often, but always notice them when trying to unlock my phone. If I'm near a computer I can connect USB, run adb shell and have full access to the phone. everything is still up and running, just no screen response.

Most recently it happened on Legend, but only after I added the adrenaline zipalign and vacuum scripts. I had previously isolated my SOD situation to adrenaline, so that's what led to my conclusion that a zipalign or vacuum without a dalvik wipe on a rom with the locks mod could trigger a SOD.

Doesn't cover every situation though.. For example, Aeon 1.4 does not implement a zipalign or vacuum script..."

As scott.hart.bti noted there is much unknown here - I attribute that to the existence of a combination of factors that result in a higher probability of getting a SOD. Here's my list in no particular order but grouped with more likely factors toward the top (and suggested remedies in parentheses):

1 - Running a ROM with the locks mod (try running a ROM w/o locks mod)

2 - Running with Overclocking (try setting max to 1200, or running a kernel that does not implement OC)

3 - Running the zipalign or vacuum scripts originally in Adrenaline tweaks (Remove those two files)

4 - Not clearing dalvik/cache after making system changes (boot CWM and wipe both using CWM menu or infuse toolkit)

5 - Running older modems (try UCLB3)

6 - Running an older ROM with mixed/blended lib files (especially after adding one of the newer kernels that is more aligned with UCLB3) - (Upgrade to newer UCLB3-based ROM)

7 - EDIT - Running on the older, slower stock RFS file system (in CWM Voodoo menu, enable lagfix and system conversion, then reboot)

Not saying this is a cure-all..just some things to try. I'm running an OC'ed ROM with locks and haven't seen a SOD except when running zipalign and vacuum. This seems to conflict with Aeonit's findings, but to be sure on that score, a complete comparison between Aeon 1.3.1 and 1.4 would be needed. Since it looks like a new release with full UCLB3 lib files is on it's way from bigfau, I'd say let's wait and see.

I've also been running a phone with nothing but initial deodex, zipalign, debloat, root, busybox, plus lidroid, epm, and crt off added courtesy of jscott30's CWM packages and have not seen one SOD on that phone (which is running an OC'ed kernel btw)... so maybe the critical combo is locks plus OC'ed kernel plus some changes to apk files...I'd like to say for sure but more evidence is needed and this is hard to come by for something that happens only once and a while or not at all.

In the mean time, I'm going to run a few more test scenarios to see if the following reliably produces a SOD: New ROM install (with locks, no scripts)+OC'ed kernel set to 1600-->boot/settle-->boot recovery-->add zipalign/vacuum-->boot-->see what happens :)
[Samsung Infuse 4G] scott.hart.bti:
Then you were one of the lucky ones. Most of the time SoD is extremely hard if not impossible to pinpoint. You will more then likely go nuts before you can narrow down exactly what it is causing the SoD issue.
[Samsung Infuse 4G] mhumfleet:
Hi, my name is michael and i had a SOD

Aeon 1.4 i have had 1 sod so far and tried to eliminate a file that ZEN suggested. So far so good but these things are random for me.:eek:
[Samsung Infuse 4G] :
KL2 was your problem. It is all around horrible. If KL2 would of been the official update i was going to sell my infuse.
[Samsung Infuse 4G] Clark Joseph Kent:
Do you recall the instruction that Zen had suggested?
[Samsung Infuse 4G] BigAtrain:
Aeon 1.4 UCLB3

Experienced a SOD and a random reboot yestetday. SOD seems to happen mostly when I receive a call. The screen will stay black but the phone still rings.

Random reboot was after the screen tried to wake for a text.

Followed some advice from Zen and wiped both caches. No proplem today. *knocks on wood*
[Samsung Infuse 4G] RoryB:
Here it is below
[Samsung Infuse 4G] Clark Joseph Kent:
Thx Rory...fig if others have not seen it, that it could be posted here...:)

I use the force...to stay sod free....and you what they say about the force....:p:D:p
[Samsung Infuse 4G] mhumfleet:
Zen's idea

Here is where i got it:

http://xdaforums.com/showpost.php?p=27411302&postcount=3187
[Samsung Infuse 4G] Clark Joseph Kent:
thanks...:)
[Samsung Infuse 4G] xDa.Fun:
Here seems some different story:

Aeon 1.3.1: (No SoD problem):

There are total 13 (lucky 13 :D) tweaks in \system\etc\init.d folder

Aeon 1.4 (Reported SoD mostly)

There are total 11 (unlucky 11 :D) tweaks in \system\etc\init.d folder

File removed from Aeon 1.4

l. Zipalign 2. Vaccum

If you are frequently facing with SoD problems try to put these files back.
[Samsung Infuse 4G] Clark Joseph Kent:
What?? There are 11 that have reported sod like activity on 1.4? NO SOD here..
[Samsung Infuse 4G] oldbbman:
Yeah hate to be a "follower" but no SODs here either. Now I know for a fact that Joe and I super clean our phone's before we flash a new rom so maybe just maybe that has something to do with it.

:cool:
[Samsung Infuse 4G] Zen Arcade:
Here's a repeat of some additional info (originally posted on Aeon thread since the subject came up- thanks to Aeonit for setting up a thread for all SOD-related complaints!):

"I started noticing SODs when the EDT locks first showed up. I do not get them often, but always notice them when trying to unlock my phone. If I'm near a computer I can connect USB, run adb shell and have full access to the phone. everything is still up and running, just no screen response.

Most recently it happened on Legend, but only after I added the adrenaline zipalign and vacuum scripts. I had previously isolated my SOD situation to adrenaline, so that's what led to my conclusion that a zipalign or vacuum without a dalvik wipe on a rom with the locks mod could trigger a SOD.

Doesn't cover every situation though.. For example, Aeon 1.4 does not implement a zipalign or vacuum script..."

As scott.hart.bti noted there is much unknown here - I attribute that to the existence of a combination of factors that result in a higher probability of getting a SOD. Here's my list in no particular order but grouped with more likely factors toward the top (and suggested remedies in parentheses):

1 - Running a ROM with the locks mod (try running a ROM w/o locks mod)

2 - Running with Overclocking (try setting max to 1200, or running a kernel that does not implement OC)

3 - Running the zipalign or vacuum scripts originally in Adrenaline tweaks (Remove those two files)

4 - Not clearing dalvik/cache after making system changes (boot CWM and wipe both using CWM menu or infuse toolkit)

5 - Running older modems (try UCLB3)

6 - Running an older ROM with mixed/blended lib files (especially after adding one of the newer kernels that is more aligned with UCLB3) - (Upgrade to newer UCLB3-based ROM)

7 - EDIT - Running on the older, slower stock RFS file system (in CWM Voodoo menu, enable lagfix and system conversion, then reboot)

Not saying this is a cure-all..just some things to try. I'm running an OC'ed ROM with locks and haven't seen a SOD except when running zipalign and vacuum. This seems to conflict with Aeonit's findings, but to be sure on that score, a complete comparison between Aeon 1.3.1 and 1.4 would be needed. Since it looks like a new release with full UCLB3 lib files is on it's way from bigfau, I'd say let's wait and see.

I've also been running a phone with nothing but initial deodex, zipalign, debloat, root, busybox, plus lidroid, epm, and crt off added courtesy of jscott30's CWM packages and have not seen one SOD on that phone (which is running an OC'ed kernel btw)... so maybe the critical combo is locks plus OC'ed kernel plus some changes to apk files...I'd like to say for sure but more evidence is needed and this is hard to come by for something that happens only once and a while or not at all.

In the mean time, I'm going to run a few more test scenarios to see if the following reliably produces a SOD: New ROM install (with locks, no scripts)+OC'ed kernel set to 1600-->boot/settle-->boot recovery-->add zipalign/vacuum-->boot-->see what happens :)
[Samsung Infuse 4G] Clark Joseph Kent:
Zen you are....wow, awesome bro!
[Samsung Infuse 4G] Zen Arcade:
I think aeonit was counting the number of scripts in the init.d folder - not counting the number of people reporting SODs :)

He rightly noted that two scripts were removed for 1.4 and deduced a possible contributing factor for SODs... could be, but I'm doubtful given what those two scripts do---

zipalign inspects every installed apk file and if not zipaligned, zipaligns it

vacuum reads every sqlite database (used by most apps to store config info) and compacts and reorders the database (this reduces size and can potentially speed things up somewhat).

Neither do anything that suggests an improvement in how the UI responds when the power button is pressed to unlock the phone. But both do modify essential files significantly and thus might confuse the OS (particularly zipalign) if the contents of the dalvik cache are out of sync with the changed apks. My guess is that a ROM with locks mod and an OCed kernel, plus an OS set to "ondemand" governor and max OC, when woken from sleep ramps immediately up to 1600mhz and some form of chaos ensues. Dunno what that is, or if I'm barking up the wrong tree...hence "guess" :)

Running a minimalist config (i.e. no new tweaks), with no OC, doing your wipes beforehand...probably a good recipe for SOD avoidance :D
[Samsung Infuse 4G] Clark Joseph Kent:
Thx Zen...Aeonit....membr type slow for us that "no i r smarts"

:):p:)
[Samsung Infuse 4G] Zen Arcade:
:D I figure if I keep typing it looks like I'm working and I can avoid the honeydo's that are waiting when I step away from the computer...

(I think we know how that's going to turn out)

":eek::eek::eek:"

:D
[Samsung Infuse 4G] qkster:
I'm running a modded vb.

Nuns locks.

Zen a16 conservative. UV step wise.

lagfix, conversion on.

Ucbl3 modem.

My own init.d tweak I copy and paste from a post.

I have never seen this sod.

I have long suspected adrenaline to be the cause.

:) but as Zen demanded...I have no empirical data to back this up. I don't think nuns lock are an issue though.

As Zen had stated, mixing libs may cause issue, non voodoo may cause issue, improper dalvik wipes when changing or restoring apps may cause issue.

:) none if which i'm guilty of
[Samsung Infuse 4G] RoryB:
You say when trying to unlock the phone. Do you get the screen to light up at all? I press the power button to turn on the phone and it does not respond, just stays blank.

You're only delaying the inevitable.:(

If I get SODs again I'll be glad to test the newer version of 1.4 without the modified lib files.
[Samsung Infuse 4G] RoryB:
Your Vagabond crew miss you. There's not been an update since 3.5
[Samsung Infuse 4G] qkster:
:)

I'll try to push out a build with nun's lock and a few init.d tweaks in a week or so.

Probably with Zen's kernel to spice things up a bit.

I got bogged down with colors scheme :)
[Samsung Infuse 4G] oldbbman:
That's so wrong in so many ways.

:D:p:rolleyes:
[Samsung Infuse 4G] Zen Arcade:
Screen stays blank... Sometimes the volume buttons work.
[Samsung Infuse 4G] Zen Arcade:
Results of first test:

Yesterday afternoon, added zipalign and vacuum back to Aeon 1.4 from CWM recovery... this morning - 1st SOD ever on this ROM, no other changes (did not wipe dalvik or cache before making the change).

As before UI completely unresponsive except for long press of power button to reboot. Accessing phone via "adb shell" works fine, phone OS is still running. Nothing hogging CPU, but com.android.systemui is top process, which is not typical...usually it is system_server... ran "reboot" command to restart phone.

I'm thinking that choice of launcher may have something to do with this too. I'm running GoLauncher EX - this has been a consistent factor across most of my ROM setups... not sure, just putting it out there to see if anyone else sees a correlation.

Next steps.. I'll continue running this config to see if I get a repeat (in the past it seems like I get one SOD right after these two scripts run, then no SODs after). I rebooted into CWM to run a log copy from the toolkit, this will cause the two scripts to run again on restart. After a couple days, if no SODs, I'll try to recreate by flashing a fresh ROM and then adding the two scripts. Time permitting, I'll dig through log files for more info. I'm also going to switch CPU governor from OnDemand to Conservative - this will cause the CPU to ramp up gradually instead of jumping right to 1600mhz from deep sleep..this may also be a factor.
[Samsung Infuse 4G] xDa.Fun:
Are you also testing froZEN margarita :D

Zen is really doing some serious exercise to kill SoD :thumbup:
[Samsung Infuse 4G] Zen Arcade:
Hey... has anyone ever gotten a SOD while their phone is connected to PC or wall charger? This prevents deep sleep so might prevent SODs if the issue occurs when transitioning from deep sleep to awake.

---------- Post added at 12:54 PM ---------- Previous post was at 12:50 PM ----------

:D Margarita and cactus juice in other forms was last night... seeking inspiration... :D
[Samsung Infuse 4G] xDa.Fun:
Not got any SoD while charging yet.

I have started getting SoD while reverting back to Aeon 1.3 Nandroid backup.

1st day No SoD.

2nd day start getting one SoD in every 2-3 hrs. :mad:

So i tried to fix it by : Removing CPU governor Apps, Go launcher etc. (No effect)

Then i removed all the scripts from init.d directory.

Not got any SoD since then. (24 hrs. passed) :rolleyes:
[Samsung Infuse 4G] GoSooners345:
If black hole had a screen of death it would be a literal black hole
[Samsung Infuse 4G] qkster:
Now you are learning, grasshopper...:)

I've been saying this about tweaks for...well..a while.
[Samsung Infuse 4G] BigAtrain:
Glad to see everyone working so hard to figure out this issue. Had 2 SOD yesterday and none today. Crazy how it does that.

Sent from my Infuse running Aeon 1.4
[Samsung Infuse 4G] qkster:
Run zen's toolkit.

Goto tweak menu. Choose remove init.d. Reboot
[Samsung Infuse 4G] BigAtrain:
Downloading as I type. Will report back after a few days.

Sent from my Infuse running Aeon 1.4
[Samsung Infuse 4G] xDa.Fun:
So removing by all tweaks i did mange to pass 2 days without SoD.

2nd Test:

From Zen's toolkit i installed Level 1 int.d tweaks (No SoD in 20 hrs.)

In some days i will test Level 2 int.d tweaks :D
[Samsung Infuse 4G] Zen Arcade:
If you want the option to restore your init.d folder run a config backup first. :)

Level 3 includes the two scripts I suspect will increase the chance of getting a SOD. L2 does not.
[Samsung Infuse 4G] threi_:
Personally every single GB rom I've tried will SOD (more specifically all buttons and the touchscreen stop responding) if you let it boot with the usb cord plugged in. This doesn't happen on ICS roms though.
[Samsung Infuse 4G] jdt352:
I did that, and guess what? Antutu's performance test went UP (Up, I say!) by over 100 points.

Now what were those tweaks supposedly doing for me? :mad:

Thanks mr Q
[Samsung Infuse 4G] Zen Arcade:
Try the level 1 tweaks.. :D
[Samsung Infuse 4G] Erik_T:
They. Mean. Nothing.

Period.
[Samsung Infuse 4G] jdt352:
Not a fan, eh?
[Samsung Infuse 4G] Zen Arcade:
Some tweaks do good things

Some tweaks do bad things

Most tweaks do no thing

Such is the way of the world...:p
[Samsung Infuse 4G] Clark Joseph Kent:
Tweaks are like the force....and....

Sent from my SGH I717, Black Star.
[Samsung Infuse 4G] BigAtrain:
Well after removing the tweeks from int.d file I can report no SOD for 2 days. I think I will try the level 2 tweeks and see what happens from there. Will report back. Also I have found my battery life decreased after removing the int.d.

Sent from my Infuse running Aeon 1.4
[Samsung Infuse 4G] qkster:
:D

Battery life may appear to have declined because the phone is working more normally and you are able to use it more?

Just joking..it may take a few battery cycles to tell. :)
[Samsung Infuse 4G] BigAtrain:
Its not that its bad I normally have about 20 to 30 percent left at night and now its getting to empty. Problem is I work in a cube in the middle of a building and I barely get 1 bar. I think it wears my battery out to constantly look for a signal. When I'm at home I have no issues.

Sent from my Infuse running Aeon 1.4
[Samsung Infuse 4G] Zen Arcade:
Both the level 1 and level 2 tweaks omit the scripts that I believe are contributing to SoDs. It appears your experience corroborates this.

In order to improve battery life, you can run a config backup from the toolkit and then add the build.prop tweaks. These include several power management settings which may or may not have been included in your ROM/firmware/MUF's build.prop. After applying the build.prop tweaks I recommend a second reboot an hour or so after you reboot out of recovery the first time if you notice abnormal battery drain (not a typical situation, but this seems to fix it).
[Samsung Infuse 4G] BigAtrain:
I'm going to leave it alone since everything is working fine. I like not getting frustrated when I try to turn my phone on and nothing happens. Thanks for everything.

Sent from my Infuse running Aeon 1.4
[Samsung Infuse 4G] RoryB:
Had another SOD before I got a chance to jump on that new MUF Qkster brought to the neighborhood. So it will have to wait. downloading latest toolkit now. Will remove everything and put back level 2 unless you want me to start from level 0 or 1.
[Samsung Infuse 4G] Zen Arcade:
Level 1 or 2 should be fine. I recommend level 1 ...
[Samsung Infuse 4G] RoryB:
jumped the gun. I am at level 2.

I'll report in a few days or sooner if I get a SOD
[Samsung Infuse 4G] mikig_mkd:
just to share a weird situation when i received an SoD. I'm familiar with the SoD phenomenon and the occasional weird color screen, but this was different. I was talking on the phone and after i finished i went to hangup and the proximity sensor did not turn on the screen, i could still talk but the screen did not turn on. There was no response from the buttons and softkeys, so i had to reboot.

It happened to me just once, maybe it is a one time time thing, time will tell.
[Samsung Infuse 4G] xxxSuperserieSxxx:
Try remove all tweaks installed on your phone sir, mine didn't installed any and so far didn't experience any sod...
[Samsung Infuse 4G] Zen Arcade:
Possible explanation

Found outside my local ATT store...
[Samsung Infuse 4G] Clark Joseph Kent:
As long as it's out side the store....not in side...:p

Sent from the Black Star`d ICS GNote.
[Samsung Infuse 4G] awl57:
Last night, I put my phone on the charger, and when I pressed the power switch nothing happened. I've been running zeus 5.2 since it came out, no problems at all. I've tried pressing every key combination I can think of to get it to wake up.

Is this the screen of death or a completely dead phone? Any ideas on how to revive it? I really don't want another phone and was just about to jump to Aeon.
[Samsung Infuse 4G] Clark Joseph Kent:
did it reboot for you?
[Samsung Infuse 4G] Zen Arcade:
try a long press of the power button (15 to 20 seconds). if that doesn't work, remove the back cover, pull the battery and replace.

This should get you booted. if you plan to move to a new rom make sure to have the new ROM on your internal sdcard, plus either the infuse toolkit or qkster's complete wipe cwm package. Boot into recovery and do a complete wipe via either of the tools mentioned, then install your new rom.
[Samsung Infuse 4G] awl57:
I've tried the long press - nothing. Pulled the battery - nothing. Replaced with a different charged battery - nothing. Tried to boot into download mode - nothing. I'm thinking of opening the case to make sure there is no moisture in there, but unless it came from a sweaty hand, its never been near water.

This just really sucks. I appreciate everyone's help though!
[Samsung Infuse 4G] RoryB:
This morning, had high battery consumption and it was warm. Email was at fault. Rebooted and recharged to full. Now running about 3.2% per hour.

Still on level 2. Don't notice any side effects. I am not a power user though.
[Samsung Infuse 4G] BigAtrain:
4 days without tweaks and still no SOD. :D

Sent from my Infuse running Aeon 1.4
[Samsung Infuse 4G] RoryB:
What level are you running or do you mean none at all?

Help Zen by testing the next level up, please.
[Samsung Infuse 4G] BigAtrain:
Pretty sure he has been on level 2 for a while. Not sure of the results. Also thought he had it down to the "level 3" tweaks being the culprit for SOD.

Sent from my Infuse running Aeon 1.4
[Samsung Infuse 4G] Zen Arcade:
Sorry that didn't work. Is the phone still under warranty?
[Samsung Infuse 4G] Zen Arcade:
RoryB and BigA..

The level 3 tweaks are straight from adrenaline. The level 2 tweaks are level 3 minus two scripts that appear to be one of the triggers for SoDs. Level 1 is a variation of level 2 that I put together in an attempt to create a more stable option that still yields some performance gains.

I usually run level 1 except when testing.
[Samsung Infuse 4G] qkster:
Possibly a dead phone. Leave the battery out for 12 hrs. If you have an external charger, try charging the battery..don't charge the battery with the phone.

put the battery back on after it's been out and try to power out back up again. If it doesn't work, try holding the phone by a corner and tap it firmly against the speaker corner a few times. There are some connection there that can get loose.

If you get nothing, you may need to warranty it
[Samsung Infuse 4G] RoryB:
I am very happy that I am getting good battery life and no SOD so far.

After a fewmore days of testing, I'm going to jump on that MUF.
[Samsung Infuse 4G] BigAtrain:
After a week and no SOD, I decided to press my luck and go with level 2 tweaks. Wish me luck.

On a side note. If there is ever another update for aeon, will we have to go in and remove the suspect tweaks again?

Sent from my Infuse running Aeon 1.4
[Samsung Infuse 4G] BigAtrain:
I was asking if the int.d tweaks get added when an rom is installed. Thus I would have to run toolkit again to remove the contents of the int.d.

I noticed my phone running super slow after adding level 2 tweaks back via the toolkit. Went back and removed.

Sent from my Infuse running Aeon 1.4
[Samsung Infuse 4G] qkster:
After you remove the init.d, and compare the mufs, most will be similar except for the themes and some options that set them apart. :)

To remove the unit.d before a flash, use 7zip, look in the muf, locate /system/etc/init.d and delete the init.d.

Lol..sounds like you've never looked inside a muf or looked for an etc inside a muf. :)
[Samsung Infuse 4G] BigAtrain:
Most of the time when I'm looking for muff its not on my phone but that's a different topic. :p

Sent from my Infuse running Aeon 1.4
[Samsung Infuse 4G] xxxSuperserieSxxx:
After you installed any tweaks try ff also:

1).../system/etc/init.d and delete the init.d

2)...try also delete or rename this files../system/xbin/sqlite3 to sqlite3.bak and

../system/xbin/zipalign to zipalign.bak then reboot your phone

See if it is works, mine did that and haven't experience any sod till now.
[Samsung Infuse 4G] JustKiddingAmI:
No SODs

I just wanted to chime in. I have AEON 1.4SL had frequent SODs, more often with the Xperia weather widget set. I remove the init.d tweaks and have used Voltage Control to reduce the voltage gradually by decrements of 50, CPU governor is set to Conservative and I/O Scheduler is set to Noop. I also use MinFreeManager, set to Aggressive.

I must say I was never happier with my Infuse. I am not a heavy user so the performance suites me good and the battery life is insanely long and no SODs whatsoever since I made the above changes.