Hey XDA community!
First of all: sorry for my bad english, i am just a regular HD2 owner from Eastern Europe.
Almost everyone who tried a cooked android experienced the Sod (Screen of death) issue. I read a hundred topic, comment and idea to solve this annoying problem, but none of those was really useful.
I guess i found a temporaly fix for that.
I noticed the main issue is the Android lock screen. So i started searching some widget to disable it. And it worked! So download the "Screen off" application from the market and disable the lock screen with it.
Et voilá: the SOD's gone.
I don't now why but it's working. Maybe it was not a g-sensor who caused the SOD.
Could you share the name of the developer, there are at least 5 apps with screen off in their name...
Thank you
Deckoff: I had the same question and the one I tried was by techvision systems.
It doesn't actually seem to put the phone in standby, but rather lowers the back light to 0, which is why there is no wake up delay or in the op's case no SOD. The back light never goes
off and you have no lock screen. Wake up is instant though.
I think perhaps this should be moved to Android Q&A
Related
Hi Folks,
I´m a new user of Excalibur, and i´ve noticed an strange behavior, from time to time the screen turns on, and then off in few secs, even with the keylock enabled.
and it happens with no action like new message, or a call...
I had an mpx220 and sonthing like this used to happen... can it be some kind of signal lost an then come back?
I leave on a shadow area just between 2 antennas!!!
Thanks in advance
Regards
No One?
tks
do you have email that it is checking? I know mine turns on every 5 minutes if i set the email to download that often.
backlight issue
its a well known bug in for the S620...google it....i think alot is written in the howardforums.....hope this helps i either reset the device or change the homescreen theme to the simplest one...still it turns on but not that often anymore...or i dont see it....hehe
Hello all,
My phone is not working properly. I've had some bugs most people seem to be having, but now I have something which is quite annoying. I can't find it on these forums or anywhere on the internet.
I have seen a 1 line reference to my problem here:
/showthread.php?t=666332&highlight=standby
Flaws & annoyances with the HTC Desire (with workarounds!) [updated Apr 23, 2010
Hardware defects. Eg. Dust under screen, device not going into standby properly. Most of us don't experience these. Contact your retailer to exchange the unit or HTC to claim warranty.
So, I seem to have this problem. The phone wakes up with whatever button I press, and I don't have to unlock the phone. I have a unlock pattern set. It also doesn't ask me for this.
I couldn't find a proper topic about this problem, but I assume I'm not the only one. Is there a fix, or is it a hardware problem?
It wouldn't make sense to me if it's a hardware problem since the screen does turn off when I press the 'power' button.
Any info would be appreciated.
Thanks, Bart.
Which Lock?
are you using the built in lock or a third party lock app? I had the same problem when I used LockBot. If it's the standard lock, have you tried Powering the phone off then back on?
I am just using the built in application. I haven't used any other lock app.
I have tried turning the phone off twice, and both times it came back (might have been after charging it, but I don't know at all if that's the reason).
edit: I'm gonna try to recreate the problem with restarting and trying to find out when it stops working properly.
edit2: I restarted now... and it hadn't saved the new background I set... strange... :/
edit3: Ok, it still locks itself... I guess I'll just need to wait and see when it doesn't work anymore... maybe it's just a matter of time for it to stop working...
The problem that you quote in your opening post is probably the problem concerning the Desire (or rather an application running on the Desire) not properly releasing a wake lock which causes severe battery drain, e.g. the calendar app about which another thread exists.
Your problem seems to be quite strange. You do not happen to have an application called 'No lock' installed, right?
No, I don't have 'No lock' installed.
I use 2 calander widgets though... (the little one on my home screen, and an more advanced one on another screen.)
I've got quite some applications installed though... I'll just type them here, maybe someone can see something wrong...
Math Workout Lite
EStrongs File Explorer
Alarmering Droid
Groceo-NL
Q-Park parkeerfaciliteiten
ATM Locator NL
Text-To-Speech Extended
Google Translate
G-MoN for Android 2.x
Buienradar.nl v2
Gesture Search
Scoreboard
Listen
My Tracks
Air Horn!
Bonsai Blast
Star Wars Light Saber
Kaloer Clock - Night Clock
Coloroid
AudioManager Widget
IMDB Top 250
Pobs
Simply Cyanide
Voetbal nieuws
Barcode Scanner
Classic Simon
XDA-Developers
Backgrounds
SchottGunn
Shazam
Funny jokes
Ringtones
Google Maps
Google Goggles
I'm just trying some of the stuff of course... It's quite a long list...
Maybe Kaloer Clock brakes something?
I'll use it tonight again, going to sleep soon... Maybe it'll be broken again tomorow.
Lets hope it wont brake again... but that's probably too optimistic.
First off: sorry for the double post, but I have some new information which will also mean the end of this topic.
This morning it didn't work anymore, and the only application that did it's thing this night was the kaloer clock (night clock).
I looked at the settings, and there are some settings about screen lock.
It's not clear at all, but I changed some settings, and it locks again.
So, I guess it was just me using an app which I didn't fully understand. I'm glad you guys helped me though. And I'm definitely glad that my problem is solved!
I have started this thread to point out a serious problem for a lot of us, the SOD. For me, ActiveSync is causing the SOD's, and for others there may be other problems and fixes for it. This thread is meant to explain the definition of SOD, and be a collection of all available fixes for it. So please contribute to this thread, together we can defeat the SOD!
What is a SOD?
SOD stands for Standby Of Death or Sleep Of Death, which means that when trying to wake up the phone from standby with the power button, it is unresponsive and the screen won't turn on. The only solution is a soft-reset.
What is causing the SOD?
There are many 'possible' reasons why SOD's could occur, and the precise reason isn't clear. With some ROM's you will get alot of them, and some are almost SOD-free.
If you don't know what's causing it, why this thread?
Because in this thread, all possible fixes that have been tested by XDA members will be gathered, and thus can be tested by other XDA members to fix their SOD's
Will Task29 fix my SOD?
No, Task29 doesn't actually fix the SOD's from occuring. It does however decrease the possibility of getting a SOD.
SOD Fixes
Fix #1: ActiveSync Schedule
Method:
If you are using ActiveSync to automatically retrieve your mail and/or calendar, you can try to edit the schedule to see if this reduces/fixes the occuring SOD's. To do this go to Connectivity -> ActiveSync -> Menu -> Schedule and set the "Sync During" to Manually or Every 4 hours.
Reliability:
Worked for: atticus182
Click to expand...
Click to collapse
Fix #2: Recently Installed Applications
Method:
If you have just installed an application and afterwards you're having SOD's, try to uninstall the application and see if the problem persists. If it doesn't, then the application is causing it. Wait for an update or report it to the developer of that application.
Programs that can cause SOD:
Elecont Weather
Reliability:
Worked for: fone_fanatic
Click to expand...
Click to collapse
usually when i get SOD's its from installed apps.
Recently i've noticed elecont weather has been causing SODs for me. Uninstalled it and everythings back to normal. (forgot which version and haven't checked if theres been an update)
Alright thanks for the feedback, I'm adding all useful information to the first post.
on a new rom and decided to give elecont weather another shot. now on version 1.4.2p and no SOD's.
I think all those that have had SOD should let us know how they got it sorted.
I have spent days looking for a solution for my Touch Pro2 but no luck. This thread can solve alot of our problems if people report back what they did to solve theirs,
/Boot
I started expierencing the SOD issue this morning out of no where. I haven't intstalled anything for weeks and I've been running the sprint stock rom for months. I think mine might be a hardware issue. I flashed to NRGs rom and still had the issue. I flashed back to sprints stock rom and it's still happening EVERYTIME the phone goes into standby. I push the power button and the phone won't wake up. I can slide the keyboard out and the button backlights light up but none on the buttons/keys work.
Try installing LUMOS to avoid SOD
i have a couple of TP2 with the SOD problem.
I read several post recommending LUMOS, so i did a quick test and it seems that it's really solving the SOD and also giving a little more battery dimming the screen.
Give it a try and let us know your comments.
I've been reading through the previous threads and I'm still confused if the issue is hardware or software related. I have the AUO panel and have broken swipes, and times where I can't scroll properly. This has been going on a couple months now and it's getting on my last nerve since it's frequently happening when I need my phone to work properly. All this time I assumed it was software but a couple threads mentioned it was hardware. Trouble is, some people with the JDI screen also have issues so I don't understand. My question is, has anyone ruled out software by flashing an AOSP rom? I'd rather not send this to Sony if at all possible since they don't cross ship and I'd be without a phone.
I have rarely an issue with the touch screen, when swipe up or down, it doesn't swipe it acts like I've just touched (clicked) once the display. I think it is a software issue, because in my case, if I turn off the display wait for 2-3 seconds and turn it on, it works with no problems.
Can you point me please to other threads that have this issue in discuss?
Thank you!
Have you removed the asf from the screen and placed an actual screen protector on it? I found that this really helped with the weird screen issues.
I have a screen protector over the ASF. But that has nothing to do with my issue, because, like I said, when I turn the display off, wait 3 seconds, and on again everything is working normally.
vibecatalin said:
I have a screen protector over the ASF. But that has nothing to do with my issue, because, like I said, when I turn the display off, wait 3 seconds, and on again everything is working normally.
Click to expand...
Click to collapse
Yeah, I reboot usually and the issue temporarily goes away. Then it will come back a day or two later. I'm afraid to remove the ASF because I've read some issues with goes touches even with a screen protector. I just want the issue to be fixed... I was thinking of flashing a AOSP rom but wanted to see if anyone with that ROM had any trouble or not. Maybe the L update in January will fix things.
Here are the resources I've read on this issue:
http://talk.sonymobile.com/t5/Xperia-Z1-Compact/Touchscreen-loosing-touch-issue/td-p/580111
http://johnhaller.com/blog/2014-03-06--sony-xperia-z1-z1s-touch-screen-issue
http://forum.xda-developers.com/showthread.php?t=2770293
I have rarely that issue, like I said I just turn off the screen, and after 2-3 seconds turn it on and it's gone. I'm sure this is a software related issue.
If it helps at all, I never had the issue in the two weeks I tried an aosp rom. However the camera and battery life were a bit lacking so I'm back on a stock rom.
I haven't have the issue too in the past weeks, I've wiping cache and dalvik cache pretty often , because I've installed some system apps. Anyway I will really want to know the cause of this
L.E. I'm still on stock firmware.
L.E. 2 : The Glove mode function, in the Settings-Display menu has an application or something? Has a file redirected to it? Is there in the phone's system a file than can be edited or deleted or something for the glove mode function? Maybe we will find answers there.
I'm not sure that I've made myself understood with the question.
Some 5t users noticed a very long wake delay on using 8.1 custom roms. It seems the screen is on as it reacts to touch input but stays rotaly black. Sometimes it even goes back off by itself when the phone is still locked. I lately noticed there is somekind of light below the amoled when the delay occurs. I was only able to see it when my screen was cracked due an accident. So the only logical explanation to me is that there must be somekind of black overlay preventing the user from seeing the content. Also the fact that some users never saw this bug on thair device it is possible that this issue is caused by some kind of google setting which is getting synched and the rom isnt fully compatible yet as it hasnt that implementation yet.
Many people keep saying its caused by pocket mode.
But its still present no matter what setting is used and even occurs after a fully clean installation of the rom without any changes to the default settings.
The only fully working workaround (no body is mentioning) i found out by my self, is to fully disable the lockscreen. xou have to disable swipe lockscreen too. The wake delay will never occure when there is no lockscreen at all.
I made this poll to see how many people had this problem and who didnt.
Who ever saw the wake issue by himself will understand the fact that i think all current 8.1 roms are almost impossible to use when having a lockscreen. Esspecialy at the morning it can take minutes to wake the phone no matter what unlock method/ swipe/ gesture/ password/ fp
i also provided all kind of logs and found the error lines. I showed them to all the devs of the different roms in telegram a month ago. But all we get is: "Disable pocket mode" and it clearly doesnt fix the problem.
one thing i also noticed is, that the problem started when the expanded screen feature got included (im not saying that disabling or enabling expanded desktop causes the issue)
Im not blaming any dev. Im just afraid this bug is beeing ingnored as most people never saw it happen.
I hope the dev will sort this issue as its literally the only bug preventing me from using custom roms.
Did you manage to fix the issue without disabling the lockscreen? I just got the phone yesterday and having this problem
Don't have any bugs you said above, just one issue that no body help me till now, in lastet ob4, the output sound when recording video/sound is really really low compared to the stable 5.04, I have to set the volume to the maximum level to hear clearly. I said this thing many times but may be it's just me, no one else.
do you use expanded desktop enabled on all apps? If so there's a Xposed fix http://repo.xposed.info/module/fr.merams.r.deepscreenoreo