SOD and random screen freezes has been bothering me almost always. I was reading all over the xda, different complains and strange solutions for them. I almost tried all of them and NONE is REALLY working (at least for me).
Recently I notice that when I wake up my phone (with yes button) after turning on, LCD immediately turns off. I mean after waking up the lcd, even if it is awake and responses to screen touch (even I can unlock it) but the LCD is off!!!! in this situation if I continue touching the screen it comes to life after couple of seconds and if not it goes back to sleep mode.
I wanted to see if anybody else has experienced same thing and If there is any solutions for it or not.
my android is HyperDroid http://forum.xda-developers.com/showthread.php?t=769026
and my kernel is hastarin http://forum.xda-developers.com/showthread.php?t=787588
I assume you are using the auto backlight...
If so search the problem is discussed in the hyperdroid thread.
Hold up to a bright light when that happens.
hold up to a lightbulb and then turn of autobrightness.
joseph230 said:
SOD and random screen freezes has been bothering me almost always. I was reading all over the xda, different complains and strange solutions for them. I almost tried all of them and NONE is REALLY working (at least for me).
Recently I notice that when I wake up my phone (with yes button) after turning on, LCD immediately turns off. I mean after waking up the lcd, even if it is awake and responses to screen touch (even I can unlock it) but the LCD is off!!!! in this situation if I continue touching the screen it comes to life after couple of seconds and if not it goes back to sleep mode.
I wanted to see if anybody else has experienced same thing and If there is any solutions for it or not.
my android is HyperDroid http://forum.xda-developers.com/showthread.php?t=769026
and my kernel is hastarin http://forum.xda-developers.com/showthread.php?t=787588
Click to expand...
Click to collapse
Not only hold it up to a bright light, but once the screen comes back on go insto display settings and turn off the auto brightness. If our using hyperdroid you should try phiremod CM6
I had this problem. I also search xda to find solutions. The only thing that worked for me was to update to the latest radio. 2.15.50 if you havent tried that already
good luck
cs378 said:
I had this problem. I also search xda to find solutions. The only thing that worked for me was to update to the latest radio. 2.15.50 if you havent tried that already
good luck
Click to expand...
Click to collapse
My Radio is 2.15 already.
I will try the bright bulb and turning off the auto balcklight to see wat happens. I hope it fix the problem. I will report back with the result.
Thank you everybody for the replies. I really appreciate it.
For EVO kernels, screen backlight turns off when brightness value is set lower than 30. Meanwhile the default lowest autobacklight level is 20. If you use a Cyanogenmod build, the levels can be adjusted, but the "screen dim level" cannot be set to values greater than 26.
The best solution would be lowering turn-off threshold in backlight driver to 20 or less.
RobertsDF said:
hold up to a lightbulb and then turn of autobrightness.
Click to expand...
Click to collapse
Thank you.
I used the trick and when I turned the auto balcklight off, it seems that my problems are gone.
AMCJUNGLE said:
Not only hold it up to a bright light, but once the screen comes back on go insto display settings and turn off the auto brightness. If our using hyperdroid you should try phiremod CM6
Click to expand...
Click to collapse
Thank you , the tricked worked
About PhireMod, I switched to it and till now LATE WAKE UP time is gone. It is waking up very fast and normal. Of course it had the same auto backlight problem which got fixed by disabling it.
Also for me HyperDroid was not giving me bluetooth and it was causing the phone process to FC. But PhireMod successfully passed the bluetooth test and I am using it now.
Thank you again for hints and suggesting the PhireMod.
Related
I use Froyo 2.1 build, after I press power key to turn off screen, if I press the power key again in short time, the device wakeup will take a long time (about 5 seconds), sometimes even not wakeup (due to timeout in the lockscreen and screen turns off again I guess), then I have to press the power key again and wait, normally it will take about 4 seconds to turn on the screen.
I tried to turn off setCPU and ATK completely, but not works, still long time to wake up.
is there a solution to this? everything works fine except this
thanks in advance!
I also have this issue. I tried many builds but there is always lag. No build will wake up so fast as WinMo but I think its the limitation of running OS from SD Card. Maybe I`m wrong but I think internal memory has lower latency so windows wakes up immediately and android always takes some time..
I want to know is there anyone do not have this long delay before wakeup? if there is, please tell me, thanks!
these are known issues and there is no fix , most of time things like this come
from human error
Yeah these are known issues with the Froyo builds. Will probablyget fix somewhere down the line.
The best thing to do now is to be patient with it. I find the more frustrated I get with it, the worse it gets. What I mean is if I keep hitting the hangup/unlock button to try to get it to wake, it takes longer to awake.
Also someone has posted that a possible problem is with Advanced Task Killer settings. If you have that program set to kill apps during sleep, it could cause a hang on wake. Also I believe auto screen rotate could have an effect.
I am sure that in time the situation will be resolved, as will every other minor bug and glitch.
The only solution I have foudn to this problem is to use shub 1.4c or d. It usualy turns on the first press, if it doesn't I press the button again(b/c usually the backlight goes on on the first press just nothing shows up on the lcd) then wiat a couple seconds and it goes on. I also have minimal TS freezes w. that build while with other builds they are common
disable autorotate. i had this even in shubcrafts builds, sometimes it woiult be within have a second, sometimes id see the screen power up but and go greyish, then a few seconds later id get the lock screen. from time to time, though i wouldnt get the lock screen and it just power down again.
since disabled auto rotate, its been pretty consistant at showing the lockscreen quickly.
The devs know about these problems, they are bveing worked on.
this is the major problem for me, but I still can not find it in any build's known bug/issue list, does the developer guys really know this? or it's only the problems shown in our devices?
If any of you have installed Battery Indicator, try to uninstall it and see if it help.
I used to have Battery Indicator to disable screen lock, after I uninstalled it, the problem is gone.
I have had the same issue with all the roms i tried ... but recently on shubcraft 1.5, i ve found out that when pressing the end key and that nothing shows on the LCD but the keyboard backlight is on, you can unlock as usual by doing the slide pattern on the black screen (you can feel it vibrate when you hit the spot before sliding).
Sent from my HTC HD2 using XDA App
I'm using FroyoStone 2.1 with kernel r9 and have the same issue.
I can confirm your finding that it's indeed the backlight that doesn't light up and unlock can be done anyway...
Dev's please fix this backlight issue...
BIG THANKS!
I had this annoying issue and tried almost all the builds and finally the build in the following link worked well. Note : This is a nexus ROM without sense and FM radio. Very snappy and no wakeup delay for me.
forum.xda-developers.com/showthread.php?t=773790
Yes, same here. Using mattc 1.1 clean
hate it.
I have this problem either , Shubcraft 1.5 , also during calls , sometimes it take more than 5 seconds to wake the screen after you take it off from your ear .
cecaa1030 said:
I use Froyo 2.1 build, after I press power key to turn off screen, if I press the power key again in short time, the device wakeup will take a long time (about 5 seconds), sometimes even not wakeup (due to timeout in the lockscreen and screen turns off again I guess), then I have to press the power key again and wait, normally it will take about 4 seconds to turn on the screen.
I tried to turn off setCPU and ATK completely, but not works, still long time to wake up.
is there a solution to this? everything works fine except this
thanks in advance!
Click to expand...
Click to collapse
Can you try waking up your phone with the YES/SEND key? (instead of power key)
Please provide feedback if this makes a difference.
memin1857 said:
Can you try waking up your phone with the YES/SEND key? (instead of power key)
Please provide feedback if this makes a difference.
Click to expand...
Click to collapse
Thx a lot.. The Call button wakes up the phone much faster than the default Power button.
Is is possible that a low memory situation can cause this? My HD2 was running perfectly then out of nowhere the long wake and wake screen freeze started to appear. I have been troubleshooting it for 2 days now. I just noticed that my available memory show in Taskiller was 109mb. I had seen that low memory situation before during a freeze period and not paid any attention to it. But I do know that after I reboot the phone its perfect again w/ 200+mb.
Anyone else notice this?
Has any progress been made on this matter in recent builds? Running shubcraft 1.5, and still having major troubles with it about 2 out 3 unlocks..
Try disabling any & all task killers, what I think is happening is that something gets killed when it shouldn't. I had the same issue to the point of going back to Winmo and as a last resort just disabled all those and then went with a static wallpaper (no live). The problem disappeared and now the battery last much longer.
I'm having issues where after going to sleep, it wakes up with the lcd very dark. It doesn't matter which level of brightness I put it on, the lcd is still hard to see. Rebooting solve the problem. Just wondering if anyone experienced this too. I hope it isn't my lcd dying...
This happen on both froyostone and bangster. I'm on the latest radio using tmousa.
I had this on bangsters 1.2, but haven't seen it on 1.3b, but only been running that build for a few days.
azzzz said:
I'm having issues where after going to sleep, it wakes up with the lcd very dark. It doesn't matter which level of brightness I put it on, the lcd is still hard to see. Rebooting solve the problem. Just wondering if anyone experienced this too. I hope it isn't my lcd dying...
This happen on both froyostone and bangster. I'm on the latest radio using tmousa.
Click to expand...
Click to collapse
i had this a few times before on a shubi build. I came to the conslusion that it is the screen not fully coming out of sleep. Seeing as it only happened when I put the phone to sleep and then tried to wake it immeadiately or got frustrated and impatient with it and tried tapping buttons repeatedly until the screen came on.
palosjr said:
i had this a few times before on a shubi build. I came to the conslusion that it is the screen not fully coming out of sleep. Seeing as it only happened when I put the phone to sleep and then tried to wake it immeadiately or got frustrated and impatient with it and tried tapping buttons repeatedly until the screen came on.
Click to expand...
Click to collapse
I had this same experience. Patience is a virtue with these phones. As long as I wait if its taking a bit to come out of sleep, I get zero problems.
Sent from my HTC HD2 using XDA App
thanks for the advice. I hope its just a software glitch. I will just have to be more patient when coming out of sleep.
My solution
azzzz said:
I'm having issues where after going to sleep, it wakes up with the lcd very dark. It doesn't matter which level of brightness I put it on, the lcd is still hard to see. Rebooting solve the problem. Just wondering if anyone experienced this too. I hope it isn't my lcd dying...
This happen on both froyostone and bangster. I'm on the latest radio using tmousa.
Click to expand...
Click to collapse
Here is my solution, i posted it in a similar thread, I think the key element here is the bsb tweaks part, hope it helps, thanks:
I solved this problem in my phone.
even turn on/off/on/off/on/off etc the screen, the devices wakes up correctly every time.
I don't really what exactly fixed but.
i installed Miris romm 20.0, then i turned off the auto screen off *start/system/power, so the screen nevers dims or turn off. I turned off the charge the device when it is connected to the computer, turned off quiet pickup, turned off 3g.
and now i think this is the key, installed bsb tweaks and turned off everything(even power savings), disable data connections and screen rotation, I only left use high glymp cache. reboot and run android, in winmo i dont have anything installed besides bsb1.6
in android i have the task killer on and set cpu at 768mhz ondemand. no profiles. battery last well over 24 hrs moderate use. by the way im using shubcraft, and the gsensor disabled kernel. thanks,
edit: also my auto sync is off in android and my wifi is always on.
I dealt with the problem by putting a widget to control screen brightness on my home page, if it goes dim I can find it ' blind'
Sent from my HD2 on mattc froyo sense.
Yeah it does happen to me if I'm being impatient and banging on the screen before it fully wakes up. Haven't found a real solution yet, but so far I would just try my luck by turning on/off/on/off several times, hoping that it get stucks momentarily again to let if "fully" wake up. Worst case scenario, reboot.
Hello,
I recently noticed an issue with my wifi (stock 2.3.3), where an app that needs to update regularly didn't seem to be doing it when the screen was off. As the phone always sits on its dock when I'm at home, I "solved" the issue by making the screen never turn off.
However, today I decided to give SIPdroid another go, as I tested it when I first got my phone and it wasn't working properly. I found out why, the second I put the phone to my ear, the screen turns off and the sound cuts. If I take the phone away, I suddenly get all the audio high speed as it catches back up.
A bit of googling showed this to be a known issue, the wifi goes into power saving mode when the screen turns off - on SIPdroid there's an option to keep the screen off and it seems to work well, it just dims the screen instead. But that's still an unnecessary battery drain.
I had trouble finding any recent info on the issue (within the past 6 months), maybe I was just using the wrong keywords. So I thought I'd ask here. Does anyone know anything about this issue? Is it likely to be fixed in the next version of android if it ever comes to the desire HD? Maybe there's a fix out there already (preferably without rooting and/or installing custom rom, my phone is just right as it is now...).
Settings>Wireless & Networks>Wifi settings>Hit 'Menu'>Advanced>Wifi sleep policy>Never
That'll prevent the wifi turning off when the screen turns off.
Sent from my Desire HD using xda premium
I tried that before posting, it makes no difference whatsoever (besides, the sleep policy is either never or 15 minutes, this problem occurs the second the screen goes off).
If u re root: change radio... try anyone.
stock: mmm default reset to try. (i think)
No:
http://code.google.com/p/sipdroid/issues/detail?id=268
http://code.google.com/p/sipdroid/i...Status Priority Milestone Owner Summary Stars
Reading through the comments, it seems a more general android problem. A reset wouldn't fix it.
Also:
http://code.google.com/p/android/issues/detail?id=9781
I'm now on my third nexus 7 and in general absolutely love the device but I'm getting fed up with the issues.
My first device suffered from sever flickering, the second had the backlight bleed and now the third refuses to wake after the screen is turned off about fifty percent of the time.
This is not the same issue as people are reporting in other posts as the charger is never connected when I have a problem. It doesn't matter if the screen times out or if I press the power button to after I finish using the device.
I'm using the stock ROM (with the 4.1.1 update), no root and have only installed the kindel app so its about as vanilla as can be.
The second nexus I had did this once but I had already organised the return and didn't think much of it.
Anyone else having similar issues or able to recommended a fix as this nexus is perfect in every other way?
Factory reset, leave it that way for a while, does it happen? If no, then you probably have an app doing something wonky.
Turn off automatic backlight, manually set it to around 40% and see if the flicker and the "SOD" goes away.
As the poster above said, turn off automatic brightness and see if that fixes it.
Nospin said:
As the poster above said, turn off automatic brightness and see if that fixes it.
Click to expand...
Click to collapse
Automatic brightness is on my N7 (and other devices) 100% of the time... No SOD problems here.
lol, so far there's not an issue for you. But some have noticed that depending on the brightness settings it reads when you power on the screen, it can "think" it's either too bright or too dark and leave you with a screen you can't see.
This gets mistaken for "SOD" because you never see the screen-Why? Because it looks like the ratio for the lowest automatic brightness setting is a bit, um, TOO low. LOL
Most other devices won't exhibit this using stock settings, but the N7 will.
THANKS!
Just got my first nexus 7 yesterday and after pretty much falling in love, was dismayed about the unexplained black outs for no apparent reason. Could not wake up the device afterward without holding down the power key for 10 sec then leaving it alone for a while.
After reading your post, I realized that the incidents occurred after switching from manual to automatic brightness in a dimly lit room, followed by mysterious recoveries when moving to brighter room. I will monitor, but hope for the best. (Will probably just use manual settings as I found the automatic mode to be too dim in all settings anyway - old eyes!)
I am already pretty raw on this point as I just spent the last 10 years or so with a laptop that would not wake up from sleep, and just learned to live with it after wasting SO much time trying to get to the bottom of it. If you have saved me from that, or from having to exchange the n7, I owe you big time. Thanks again!
Compusmurf said:
lol, so far there's not an issue for you. But some have noticed that depending on the brightness settings it reads when you power on the screen, it can "think" it's either too bright or too dark and leave you with a screen you can't see.
This gets mistaken for "SOD" because you never see the screen-Why? Because it looks like the ratio for the lowest automatic brightness setting is a bit, um, TOO low. LOL
Most other devices won't exhibit this using stock settings, but the N7 will.
Click to expand...
Click to collapse
did you solve it or what?
I have the exact same issue and I'm about two second from returning this crap
so annoying
seven2099 said:
did you solve it or what?
I have the exact same issue and I'm about two second from returning this crap
so annoying
Click to expand...
Click to collapse
well that didnt fix anything.
Its a hardware issue, so i'm going back to stock and see what I can do, because if not, this baby is going back
seven2099 said:
well that didnt fix anything.
Its a hardware issue, so i'm going back to stock and see what I can do, because if not, this baby is going back
Click to expand...
Click to collapse
i have similar issue with forced sleep, it cannot waken sometimes. TnT
anyone can help?
Further investigation shows this has nothing to do with brightness and that all tablets with this issue should be returned/exchanged immediately.
Quick google search will allow you to find that comes directly from Asus support.
Total fail, asus ftl
new tab rendered more quality issues. opened it at the shop, returned it immediately and went samsung.
Asus will always be asus.. too bad cuz my tf300 was pretty decent in terms of quality, just had wierd screen lift and squeecky issues.
Galaxy Tab 2.0 7inch is a much better choice now.
I have exactly the same problem with my current device. About 30% of the time, the power button would just stop working so I couldn't turn the unit on or off, unless I plugged it in to the charger. It didn't turn on for a full day once so I did a full factory reset which included re-flashing the stock rom and the problem persisted, the button would still not work! So I packaged it up for return and left it sitting for a couple of days. Just before I went to post it, I checked that the issue remained and to my surprise it turned itself back on again! I kept it and since then, it has only happened once.
I do intend to return it though, but only when I hear Asus are shipping units which are built properly. Clearly a hardware issue but pretty weird since it seems random and is not reproducible by any means I know of.
I am experiencing a similar issue. Does setting a manual brightness fix the issue?
It is my 3rd Nexus now with exactly the same problem.
I found out that the Nexus is in APX-mode (NVFlash) when it's in this state (SoD). Windows tries to install a APX driver when it is connected via USB.
The problem occured always with 16GB Nexus. A friends 8GB works fine.
Nexus 7 (C9) - Stock Rom 4.1.2. - locked - not rooted
Turning off the auto-brightness fixed the issue for me. Minor workaround to a major problem.
I tried searching if this happens to anybody else, but couldn't find it. Since I updated to lollipop (I put original polish rom first via odin) whenever my auto brightness is turned on, when I wake the phone using home key or power button, my screen turns on with full brightness for a half second or something like that, and than goes back to normal.... I thought it was a bug on polish ROM, so I flashed austrian rom, but no improvement. Now I have custom TW rom, and it is still the same. When I turn auto brightness off, it doesn't happen. So I suspect it to be that screen turns before the light sensor on unlock, and it is set to full brightness always. is there some file I can edit, so screen starts at lowest brightness or delay screen start for half a second so the sensor can start first.
It is killing me when I get a message while sleeping in a dark room, and I want to check it, it blinds me so I wake up, and can't go back to sleep later!!!
LOL I have the same problem, which is extremely irritating to say the least, but I had no idea that it had to do with auto brightness! I am on latest AryaMod, which is stock TW based ROM, so I guess its a problem of all the TW releases?
Don't know! I will ask this in AryaMod topic and see whether dev will be more than kind to provide us a solution. Thanks for creating the topic, I had thought about it a lot of times, but was never intrigued enough.
neky92 said:
I tried searching if this happens to anybody else, but couldn't find it. Since I updated to lollipop (I put original polish rom first via odin) whenever my auto brightness is turned on, when I wake the phone using home key or power button, my screen turns on with full brightness for a half second or something like that, and than goes back to normal.... I thought it was a bug on polish ROM, so I flashed austrian rom, but no improvement. Now I have custom TW rom, and it is still the same. When I turn auto brightness off, it doesn't happen. So I suspect it to be that screen turns before the light sensor on unlock, and it is set to full brightness always. is there some file I can edit, so screen starts at lowest brightness or delay screen start for half a second so the sensor can start first.
It is killing me when I get a message while sleeping in a dark room, and I want to check it, it blinds me so I wake up, and can't go back to sleep later!!!
Click to expand...
Click to collapse
Same thing here mate. I noticed that this happens to all 5.0 rom and currently I am using ported 5.0.1 rom and it went well.
shchiam1978 said:
Same thing here mate. I noticed that this happens to all 5.0 rom and currently I am using ported 5.0.1 rom and it went well.
Click to expand...
Click to collapse
I tried flashing 5.0.1, but it didn't fix it, I also have a problem with screen not turning off during calls now, which rom are you using?
neky92 said:
I tried flashing 5.0.1, but it didn't fix it, I also have a problem with screen not turning off during calls now, which rom are you using?
Click to expand...
Click to collapse
I am using death note.
Now I am back to Arya to test the battery life.