Database Develop

.32 sod possible work around [poll] [cm7]

Hi everyone,
Posting this here because this is my first post. I started to experience s o d or my nook won't wake up around the time the .32 kernals came out. 1 of which when I was playing with the screen on screen, screen off animations. the backlight would turn on but the nook was unresponsive, I did a hard reset and everything was okay. I don't know if it was a coincidence or not but ever since I unchecked " screen on animation" I have not had a sod. Just my 2 cents it seems to be a working for me maybe someone else to confirm this. Please respond using the following format.1. SODS yes or no. 2.screen on animation yes or no. 3. lockscreen yes or no
Sent from my ADR6300 using XDA App

JT75 said:
Hi everyone,
Posting this here because this is my first post. I started to experience s o d or my nook won't wake up around the time the .32 kernals came out. 1 of which when I was playing with the screen on screen, screen off animations. the backlight would turn on but the nook was unresponsive, I did a hard reset and everything was okay. I don't know if it was a coincidence or not but ever since I unchecked " screen on animation" I have not had a sod. Just my 2 cents it seems to be a working for me maybe someone else to confirm this.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
While I've never had a sod, I've found that unchecking screen on animation ensures a smooth, error free wake.

I'm curious to hear from people that have a lot of sods to see if they have screen on animation checked
Sent from my ADR6300 using XDA App

I had SODs when I first upgraded from a .29 kernal build. Wiping personal data has stopped the problem for me.

DeathsArrow said:
I had SODs when I first upgraded from a .29 kernal build. Wiping personal data has stopped the problem for me.
Click to expand...
Click to collapse
What personal data?
Sent from my ADR6300 using XDA App

I see they removed the screen on animation from the next nightly maybe I was on to something after all.

Took my nook from cm7#87 to 3.1 after flashing the stock ROM, wiping and installing all apps manually. overkill but I've been getting SoD, PBD and the SoD+PBD.
maybe on to something or there's something more that had to removed(?) cause I had animation off and had two SoD just this morning.

Check this out guys....
http://forum.xda-developers.com/showthread.php?t=1108964

Running: nightly-87, 1.2Ghz 5/23 OC kernel. Stable as a rock, and running significantly faster than nightly 60-something I came from. my system would not deep sleep at all, didn't have any battery problems.
The method of enabling on/off screen animations, then hard rebooting fixed it right up. No SOD's yet. Even though it will probably end up being fixed in the next couple nightlies, thanks for the tip.
Sent from my Nook color using Tapatalk

I've never had Power On Animation on, and I only recently turned on Power Off Animation. Neither appear to have any affect on SOD.

I was plagued with SoD - would need hard reset even after 3mins of screen turning off.
Unchecking 'screen-on animation' solved it 100%.
I repeat....100%......very happy camper here
Thank you to whoever suggested it - post now buried deep in one of the CM7 dev threads.
kevvyboy

The reason I suggested this is because when I flashed Dal's .32 beta I was thinking how cool the animations were. I sat in my chair for like 2 minutes watching the screen turn on and off, then once when i tried turning it on I got no animation. The back light turned on but no homescreen. I waited nothing happened, so I held down the power button then the back light turned off, then I hit power and it turned back on. So I figured something got hung up with the screen on animation so I unchecked it but still use the screen off animation.

[Q] CM7 shutdown issue

Have anyone other than me experienced that the phone suddenly is turned of? It's not the BSOD or reboot, but just turned off and can be turned on right away..
I've saw it yesterday when it was in my pocket, and this morning when i woke up.
I'm using the CM7 RC1 ROM straight from the box.

Yes. I get this to... (With every build of CM that is)

Same happens to me also with the latest CM7.

Me and my brother also get this, started with cm7 57 I think
Sent from my Optimus 2X using Tapatalk

Does anyone know how to use ADB to log? Then we could maybe capture some logs when this happens and post to aremcee to see if he can help us..

The same thing has happend to me 2 times in the week a have had this replacement device. It's worse than the one I traded this one for
But I'm on stock havn't rooted or anything.

Just had a BSOD aswell.. Gotta hate this phone. It's works on stock so I can't send it to my dealer and get my money back

Install a Froyo Rom
Profit.

My findings on the CM7 sod (sleep of death) issue (I post this here, as I don't have enough posts to post it to dev area):
I've been using CM7 occasionally since the first nightly. About 2 months ago I suddenly had 3 sods in 2 days. This was after I bought JuiceDefender Ultimate. In JD I had sync enabled once per hour, and JD set to first try to connect to wifi and then mobile data. In Android wifi settings I had wifi sleep policy set to "when screen turns off".
After I set JD to use only mobile data on sync events, and turned wifi sleep policy to "never", I haven't had a single sod since. If I remember correctly, I once managed to induce a sod by turning wifi on or off (can't remember which) through the power control widget, and immediately after that I turned the screen off normally by pressing the power button (while wifi was "dimmed" in the power control widget meaning it was changing it's state).
So I strongly believe that my sods were caused by the combination of turning wifi on or off (either through widget or JD doing it) and turning the screen off at the same time. I didn't experiment any more, since I found my solution above.
I wrote this here, because people try hard to hunt down what's causing the sods, and I wanted to share my thoughts. If it is of no help, then sorry.

it happens sometime... don't trust your phone's alarm to wake up. you could have bad surprise (just had the experience 2 days ago) :'(

i am running cm7 no. 165. and vork kernel clocked to 1504 no reboots or black out issues. i also have green power managing my network data only... good luck all... just remember that cm7 is still nightly and is not considered stable.

Hi, I'm about to get one LG, but I've had the same issue with an Orange Boston mobile with a 2.3.5 CM7. I disabled Wi-Fi sleep too and it seems to help.
Before the scren weirdly shut down and the phone rebooted.

Hmm might try this out and see if it works.
I can't seem to get this issues myself. I will try and test this later on my other phone.

That is the reason why I don`t use CM7 anymore ...

Moderator Message
Extensive discussion going on here >
http://forum.xda-developers.com/showthread.php?t=997705
THREAD CLOSED

NC, CM7, Dalingrin OC kernel.. Sleep of Death

CWM 3.2.0.1
CM7 Nightly 131
update-CM7-dalingrin-OC-emmc-063011
Sleep of Death-
Sometimes the screen will remain black when trying to wake the device. I haven't been able to find a pattern to the problem, though I think it has something to do with the kernel. It seems completely random.
This has happened on every nightly I've used, which is why I think it's related to the kernel.
Has anyone found a fix?

omnibyte said:
CWM 3.2.0.1
CM7 Nightly 131
update-CM7-dalingrin-OC-emmc-063011
Sleep of Death-
Sometimes the screen will remain black when trying to wake the device. I haven't been able to find a pattern to the problem, though I think it has something to do with the kernel. It seems completely random.
This has happened on every nightly I've used, which is why I think it's related to the kernel.
Has anyone found a fix?
Click to expand...
Click to collapse
Not sure to what the cause is. However, for me I noticed that every time I left wifi on and put my nook to sleep I would get sod anytime after an hr. So now I manually disconnect wifi every time I put my nook to sleep, and I have not once experienced another sod. There are some people that say the latest nightlies have fixed sod but other report there still there so I guess it varies.
I'm currently on n125 with dal's 6/30 oc kernel.

The problem still occurs with the recent nightlies.
It's weird, last night I left it in sleep mode with wifi turned on, and it powered up fine this morning.
A few hours later, I put it in sleep mode, set it down for a minute, then tried to use it again. It wouldn't wake up. From what I can tell, it doesn't matter what amount of time passes.
I'll keep trying the wifi trick you mentioned. If disabling wifi does the trick, then that will narrow down the problem quite a bit.
Thanks for the tip!

dabiddabird said:
Not sure to what the cause is. However, for me I noticed that every time I left wifi on and put my nook to sleep I would get sod anytime after an hr. So now I manually disconnect wifi every time I put my nook to sleep, and I have not once experienced another sod. There are some people that say the latest nightlies have fixed sod but other report there still there so I guess it varies.
I'm currently on n125 with dal's 6/30 oc kernel.
Click to expand...
Click to collapse
I am on n120 with dals 6/30...I always got SOD when I left wifi set to always on...when I switched wifi to shut off with the screen, the problem has not returned!

Yup, it looks like turning wifi off before it sleeps does the trick. 48 hours later and no SOD.
Thanks for the tip!

cmdauria said:
I am on n120 with dals 6/30...I always got SOD when I left wifi set to always on...when I switched wifi to shut off with the screen, the problem has not returned!
Click to expand...
Click to collapse
How do you set wifi to shut off with the screen? I can't find a setting for it.

omnibyte said:
How do you set wifi to shut off with the screen? I can't find a setting for it.
Click to expand...
Click to collapse
Try an app like juice defender.
Sent from my phone using Tapatalk

omnibyte said:
Yup, it looks like turning wifi off before it sleeps does the trick. 48 hours later and no SOD.
Thanks for the tip!
Click to expand...
Click to collapse
No problem glad it worked for you.

koopakid08 said:
Try an app like juice defender.
Sent from my phone using Tapatalk
Click to expand...
Click to collapse
Great, thanks for the recommendation.

If you are looking for a free solution to do this, the application Setting Profiles Lite allows you to set exactly one rule.
Create a profile with wifi off. Create a rule to set the wifi off profile when the screen is off.
Frank

frankusb said:
If you are looking for a free solution to do this, the application Setting Profiles Lite allows you to set exactly one rule.
Create a profile with wifi off. Create a rule to set the wifi off profile when the screen is off.
Frank
Click to expand...
Click to collapse
http://nookdevs.com/NookColor_Issues#Workaround_One
Details there if anyone wants to try it, works great. I used it on stock ROM, now that I have Tasker on my tablet I use it instead, but all the same.

I'm experiencing the SOD on CM 7.1 RC1... so it's not limited to the nightly's.
Has anyone escalated to the CM devs yet?

I think I have found a temp fix for the SOD, doubled my battery life, and increased my bandwidth when tethered. I am no expert at any of this, but after I installed DroidWall from the market and used the "white list" mode enabling only the apps I wanted to use the network I no longer get SOD. For example I am using wifi tether on my galaxy s in infrastructure mode with droidwall on my NC only allowing XDA app access to the internet.
I also have it installed on my galaxy and only have Linux kernel and applications with root accessesing data. I have gotten more than 8 hours on the galaxy without having to charge. Now I am able to have it tethered to my NC all day and neither device needs charging.
Heck maybe its a placibo effect maybe not.
Running CM7.1 RC1
Now if I can figure out why I lost the ability to mount my NC mass storage on the PC after using the new USB host mode and playing with the wiimote. Go figure
Sent from my NookColor using XDA Premium App

skylar.sutton said:
I'm experiencing the SOD on CM 7.1 RC1... so it's not limited to the nightly's.
Has anyone escalated to the CM devs yet?
Click to expand...
Click to collapse
I've also been seeing SOD almost every time I put the NC to sleep for an extended period of time (longer than an hour). Also running 7.1 RC1. Weird thing is that it's been within the last 2 weeks that it's been happening. I've tried the Setting Profiles workaround listed above but I'm not sure if I set up the rules correctly so we'll see what happens

The setting profiles workaround didn't seem to work. I tried switching out my almost full 8gb sd card for a 16 gb sd card and after putting it to sleep overnight, it came back on immediately. Would sd card memory have anything to do with it?

I have also found AutomateIt (free market app) to work well for setting triggers and actions... i.e.
Power Plugged In -> Set Screen Off Timeout 30 min
Power UnPlugged ->Set Screen Off Timeout 2 min
Screen Off -> Set WiFi State Off (delay 5 min)
Screen On -> Set WiFi State On (no delay)

Just my $0.02... but a profile/setting switcher is not a "fix" for the SOD... it's a work around (and an ineffective one at that). The underlying problem still exists, so nothing has been fixed, we're just maneuvering around it.
I'm going to work on something that logs to a remote file and let it run for a few days. I'm hoping I can catch some data around what is going on immediately prior to the lock up.
Also, sorry for the bump.

blank screen but phone ON!!!!

Has anyone had this issue?
I have tried a few different ROM's and have had this problem on all, the phone will work but sometimes when the phone is locked and asleep you cannot get the screen back.
If you ring the phone it will ring but you can't wake the phone up (the screen is off).
If I then pull the battery and reboot all is well until the next time, which is random.
I will remove all my programs to see if there is one of them causing the issue, I don't believe it is the rom as it has happened on a few of them.

Have you wiped your phone when flashing the different roms? I've had it sometimes, i think it could be a ram management issue...

Talon26 said:
Have you wiped your phone when flashing the different roms? I've had it sometimes, i think it could be a ram management issue...
Click to expand...
Click to collapse
Yeh, I always do a factory/wipe, dalvik cache wipe.
I think it might have been TW4.5, I did some research and installed TW4 Manager I then updated TW4.5 to the latest Version. So far it hasn't happened yet but i'll give it a couple more days.
Thanks.

Yh ive been reading and TW4 generally accelerates the issue (because its a ram hog? not sure i dont use it) Im currently using Golauncher with system tweaks, but was told that nemus launcher and system tweaks was a better combination... Seems to be working, ive had less force closes or issues of that type

it's the proximity sensor. needs replaced.

pch.radu said:
it's the proximity sensor. needs replaced.
Click to expand...
Click to collapse
I don't think so...
The proximity sensor is only used when your in a call. It should not have any effect when he tries to wake it from his pocket after a while...

Well i am on 2.3.5 and using golauncher and never had any problems. Still my best guess is the damn sensor. On samsung apps there is an app called sensors i think and that app tells u what is working inside the phone.
Sent from my GT-I9000 using XDA App

If I recall correctly yeah I had this issue once on JVR and once on JVS and now on JVT I got it a few hours ago
---------- Post added at 06:30 PM ---------- Previous post was at 06:29 PM ----------
pch.radu said:
Well i am on 2.3.5 and using golauncher and never had any problems. Still my best guess is the damn sensor. On samsung apps there is an app called sensors i think and that app tells u what is working inside the phone.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Sounds like a great app but seeing as the screen doesn't turn on that app might as well be useless in this case

No screen turns on, its just when it turns off it wont come back on...

I have the same issue with my SGS. Running stock version of JVT.
Wake up in the morning to phone alarm but screen is black. Pushing home button or any other button does nothing. Had this happen a few times now and only solution is to pull the battery

In order to help you we need to know what you are running currently and what you have tried to resolve the issue so far, can please make as detailed account as possible

It's seems that everybody have this same issue. I have exactly this same - phone is working - buttons are lit, but the screen is blank. I'm on 2.3.5 stock firmware.
Trying to solve this I already did wipe and even formatted the internal storage.
What's more interesting is that this same happens to my wife's Galaxy Mini (S5570) !!.
I can remember though that when my phone was on v2.2 about a year ago it was working ok.
small tip:
What you can do instead of pulling the battery out is to press the power button for about 10 seconds ( phone will turn off) release and the press it again for few seconds to start again.

You don`t need to press power again, just keep it pressed until you see the samsung bootlogo.
Mine has started to blackout too, maybe it`s related to some installed software. It worked ok still few months ago. My galaxy mini is working ok tho, has only few market apps installed.
Sent from my GT-I9000 using Tapatalk

poyda69 said:
Has anyone had this issue?
I have tried a few different ROM's and have had this problem on all, the phone will work but sometimes when the phone is locked and asleep you cannot get the screen back.
If you ring the phone it will ring but you can't wake the phone up (the screen is off).
If I then pull the battery and reboot all is well until the next time, which is random.
I will remove all my programs to see if there is one of them causing the issue, I don't believe it is the rom as it has happened on a few of them.
Click to expand...
Click to collapse
The bug is called SOD (Sleep of Death). Apparently a Gingerbread only bug (I think deep sleep was introduced in Gingerbread).
Your phone is going into deep sleep, and can't be woken agian.
I don't know if there is a fix for it, but you could try search for SOD on these forum pages.

Herman76 said:
The bug is called SOD (Sleep of Death). Apparently a Gingerbread only bug (I think deep sleep was introduced in Gingerbread).
Your phone is going into deep sleep, and can't be woken agian.
I don't know if there is a fix for it, but you could try search for SOD on these forum pages.
Click to expand...
Click to collapse
i had this issue on cm7 with neo kernel, but sometimes it responded after some time
i think its black magic made by apple and will kill our cats

As Herman76 said, this is the SOD, I used to get them quite frequently. I created a thread with a possible workaround. So far haven't got any new SODs.

wifi issues with ics

Hey, my wifi always goes out and needs to be restarted while using ICS. at first it would happen like three times a day. now its a couple itmes an hour. it is very very very annoying. does anyone know a fix for this???

I don't have this problem, but do you have a wifi-sleep timer set up? Maybe an app is doing something?

No i dont. This issue was posted before in the threads but never had a solution. I always wipe EVERYTHING so i dont know why this happens with me.
Sent from my XT862 using Tapatalk

It's not just you. I get MANY wifi drops as well. I don't use it often, but when I do, I get a drop every 15 minutes or so. It happens very randomly: as in not when I'm loading a page, just randomly I'll see the logo go white then disappear.
My solution? A frustrated sigh and a switch of wifi on and off.
Sent from my DROID3 using xda premium

when using fullscreen apps and just even regular browsing its a b*tch. I tried the wifi fixer app but it didnt help. Im clueless

This has been an issue for me since the first ics rom. None since have fixed it or addressed it to my knowledge.
Sent from my DROID3 using XDA

I did no have this problem on the AOKP 4/12 build, but do have it now on the 4/30 build. No idea why.

The audio issue is also ALOT worse for me. most of my phone calls do the silence thing where there is no audio. Today it caused me to run into alot of trouble. i hope these issues get fixed soon. I think it was the bluetooth updates in the changelog that caused the problems to occur more. As they are supposed to be bluetooth related. Unforunately i might have to go back to gingerbread

I am able to use 1x data & WIFI on ICS Rom only. Neither WiFi or Data works with Stock ROM.
Before It used to work in Stock ROM, but now it does not. So I am sticking to CM9

I have this issue too but I use juice defender. I only really use it for 2 functions
1. Enable WiFi when I'm home (constantly on) and disable when I'm away
2. Turn off data at night from 1am to 6am
when i flashed ICS the effectiveness is shady. A lot of times when i turn on the screen wifi is disabled but will reenable after a few seconds during the day. also at night sometimes it won't disable until later than 1am and will randomly enable and disable at like 4 am or something. sucks because i'll randomly get a bunch of notifications for emails twitter etc. and it will wake me up.