Hi,
I started to get a weird problem since last week. I've had this phone for about 3 months now and never had any problem like this.
It all started one morning when I wanted to stop phone alarm. The alarm was going off but the screen was black. I pressed the power button to wake up, but it was still black. After couple of times pressing the power button the screen came up. First it was not that often but the situation started to get worse. It came to that I can sometimes cannot turn it on for a long period of time. I need to keep pressing power button, volume buttons and eventually it will come up.
This is what I've found so far:
1) When the power button is pressed, although the screen doesn't start up, I can see the three buttons at the bottom lighting up. So it is not a problem of the power button.
2) When the power button is pressed, although the screen doesn't power up, the screen seems responsive. I can feel the vibrations when I tap (I have a startup password)
3) When the phone is connected to a power supply, screen always starts up without a problem.
4) Screen will start up more frequently when the batter power is high.
It seems as though there is a connection between batters power and the screen not starting up. But then again, once the screen comes up (after not starting up), then it works fine, until I turn the screen off.
Has anybody experienced anything like this before?
I did a factory reset thinking it might be some application I installed but it didnt help.
I had to send this phone once to repair the speaker and cost more than $80 just for courier. I don't want to spend another to get this fixed.
Thanks.
I have this problem or a problem very close to this. I have a HTC One X (international version). I'm running the latest version and updates and the problem has existed for at least the last two updates.
Android Version 4.1.1
HTC Sense version 4+
Software number 3.18.401.1
I have the screen lock pattern turned on.
Sometimes when I hit the power button, the phone does not turn on and so I press it again and only after a third press does the phone turn on. I then unlock the phone and use as normal. So, several times per day I have to press the power button three times before the phone turns on. But other times I press the power button once and it turns on straight away. I've just turned the pattern unlock off to see if this makes any difference. I'll start to record the exact details of when I experience this and see if we can work out a common cause.
Hopefully if enough people report this problem then they can send out an update to fix this problem.
exazonk said:
I have this problem or a problem very close to this. I have a HTC One X (international version). I'm running the latest version and updates and the problem has existed for at least the last two updates.
Android Version 4.1.1
HTC Sense version 4+
Software number 3.18.401.1
I have the screen lock pattern turned on.
Sometimes when I hit the power button, the phone does not turn on and so I press it again and only after a third press does the phone turn on. I then unlock the phone and use as normal. So, several times per day I have to press the power button three times before the phone turns on. But other times I press the power button once and it turns on straight away. I've just turned the pattern unlock off to see if this makes any difference. I'll start to record the exact details of when I experience this and see if we can work out a common cause.
Hopefully if enough people report this problem then they can send out an update to fix this problem.
Click to expand...
Click to collapse
I'm pretty sure this is a hardware issue. I bought mine from Expansys and sent it back to them for repair. It's been more than a month and they say they're still reparing it.
In my case it was impossible for me to start the screen up with power button no matter how much I pressed it. The only thing that worked for me was to press the back of the phone just below the camera. So it seems like a hardware issue. But on the other hand, at times when I can't get the screen turned on no matter what I do, I'd turn the phone off and start again and the thing would start up like nothing happened. So while I'm pretty sure it is a HW issue, I'm not sure how a power restart makes it work.
For me I don't think that this is a hardware problem as it only started happening once I did the big upgrade from 4.0 to 4.1 and then it follows a specific pattern. That is three power button presses will always turn it on. Less frequently I also get a problem where the power button turns on the three lights on the soft buttons but the screen remains black. I then hit the power button to turn it off, and again to turn it on and the phone is back to normal again.
Is yours an international version? I bought mine an international version and had it shipped to Australia.
solved?
Hi - did anyone ever solve this? This is happening to me with my HTC desire X after having had the screen repaired, so I think it is hardware related, but the shop doesn't know how to fix it! My screen also does not turn back on when I want to end a phone call and pull the phone away from my face anymore. These problems seem related as they started at the same time. I would be grateful for help!
As we all know(or should know if you read around the forums) that there is an issue with "sod". Now these sods are not the same as the sod i was familiar with before 4.2. Before 4.2, the device(s) were for all intensive purposes not alive. Sure you could connect to adb, but the device was "dead" until you pulled the battery and rebooted. But with these 4.2 "sods", the device is alive, with the exception of the screen not being able to turn on. Phone calls and messages still come in. notification sounds still play, and you can use the volume buttons to raise/lower the volume. But you still have to pull the battery and reboot for the screen to come back on. Running logcats via adb doesnt seem to show anything related. Well, ive found a way to reproduce these 4.2.X "sods" while the device is awake with the screen on. I can reproduce it at will, and have had other users confirm this. What i do is this.. I go into the main settings, display, then brightness. Turn off automatic brightness if its on. Now adjust the brightness, up, then down, then up(back and forth, but take your finger off the slider when you go up then down). now press ok to set the brightness. Go back into the brightness setting and repeat. Eventually(sometimes seconds, sometimes minutes) the screen goes completely black, like its off, but the device is completely awake. same as these 4.2 sods, phone calls and messages come in, notifications sound, etc. Only difference is the device screen is on when it goes black instead of it being off. The symptoms are the same. This behavior leads me to believe that it most likely isnt a kernel issue like many believe. I believe that its related to some coding that controls the screen. As we know, every rom/kernel has shown this behavior, even stock and unrooted(some more, some less). Personally, i had 3 of these sods last month(trinity kernel/rasbean rom), but i know that some users have them many times a day unfortunately. What could it mean that i can replicate this behavior on an awake device? Any more thoughts about this?
maybe someone using another kernel/rom can try to reproduce this?
I haven't tried your method yet. I'll and post my results here. I was able to replicate it using another program (check the links below)
But reading your post, I'm sure now that SOD has to do with autobrightness or brightness control (knowing that, maybe it is easy to solve?)
Check my posts:
http://forum.xda-developers.com/showthread.php?p=35205418#post35205418
http://forum.xda-developers.com/showthread.php?p=35496824#post35496824
Check my post here:
[URL="http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638"]http://forum.xda-developers.com/showpost.php?p=35899150&postcount=26638[/URL]
whre I answered to that phenomen. I was on RBJ + franco r348 that time
I can't reproduce (force) it now with RBJ + franco r360, I tried about 100 times.
Just wanted to post my results, maybe it's too early to tell as r360 is too young.
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
Maybe because OMAP is abandoned at 3.0.
Ashtrix said:
Why does this not happen on N4, N7 and N10
+ never had an SoD in this wee k (Running anarkia's stable berserk releases, only on 511 & 515 / Jellybro )
Click to expand...
Click to collapse
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app
Jessie-James said:
Sometimes I have my screen say go off but I will click the lock button The screen don't come on but it is still responding. Meaning I can still unlock the device as vibration tells me if I click the ring or not. So this is all down to the SOD? WoW. Learn something new everyday. I am on Xenon-HD 11-12-12 but also had it on stock too. With me though to fix this it just required to to press the power button a few time then the screen returned. Honestly I don't find it annoying at all UNLESS I need to say make a call to my local emergency services. (999 in UK). That is the only time. My nexus S does the same too with the screen but only after I had the NAND chip replaced by Samsung. Hope you guys can find something and my bit of info helps a little.
Regards
Jessie-James
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
if your device wakes, even after a few presses, its not sod.
simms22 said:
it does. just not as often/widespread as with the gnex. ive seen enough reported with the n7 and n4(i havent read any reports with the n10 though).
Click to expand...
Click to collapse
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
pressing and holding the power button for 10-20 seconds will force reboot those devices.
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
MondoMor said:
A battery pull isn't necessary; you can shut down the phone with a little practice (depending on your lockscreen).
1. Press the power button (or wait) to lock the phone
2. Press the power button again and unlock
3. [optional] Press the home button (center of screen near bottom edge)
4. Press and hold the power button until a short vibration is felt.
5. Touch the Power Off button (center of the screen just below a horizontal line from the midpoint of the volume rocker). This puts you in the Power Off confirmation dialog.
6. Touch the screen in the approximate location of the "OK" button. I start at the middle on the right side and work my way down. Soon I get the long vibration telling me the phone has powered off. This is the hardest to master since feedback isn't immediate; the long vibration happens several seconds after I successfully hit the OK button.
7. If nothing happens, press the power button to re-lock and start again.
8. Practice when the phone is functioning normally, and you'll be prepared for your next SOD.
My observations (bone stock GSM phone):
This happened once in a pitch-black room. The screen does not go perfectly dark, but it is extremely dim and uniformly grey. I could not make out any details, so the contrast is completely gone.
SOD happens all the time playing Ingress, or other apps where the screen is active for a long time. It seems to happen most often when the display partly dims before going to sleep. My phone is set to sleep at 30 seconds, and the "pre-dim" happens at about 25 seconds. That's usually where I get my SODs.
SOD happens to me less often with auto-brightness set to OFF. It's extremely rare in normal use (but happened just now as I replied to a text!)
Click to expand...
Click to collapse
wouldnt it be easier to just pull the battery? thank you for your observations btw.
simms22, I actually think it is a kernel issue. I only experience SOD problems when i use a custom kernel. Also yesterday I flashed stock 4.2.1 and tried for 10 min to replicate SOD using your method - I could not. Today I tried again - nothing.
simms22 said:
wouldnt it be easier to just pull the battery? thank you for your observations btw.
Click to expand...
Click to collapse
My phone is in an Incipio case, and it's more of a pain to separate the case, especially if I'm in my car or out hiking or whatever. I've gotten pretty good at doing it blind. Also, years of running Windows have made me anal about doing orderly shutdowns. :laugh:
Forgot to add earlier: I was unable to replicate with the technique described in the OP. But as long as someone can get this to happen on demand, it ought to be solvable.
Edit: although I got the SOD in normal usage a few minutes after trying the technique in the OP. Maybe the display SODs on some specific number of brightness changes? That would explain it happening more often with autobrightness, also.
Ashtrix said:
we cannot pull out the battery and fix the SoD on those devices so how could we fix that on N4 & N7 ?
Click to expand...
Click to collapse
Just hold down the power button for several seconds. Continue to hold down the power button until the screen blinks off and the boot logo appears.
We are flooding here.. lets discusse this other place and leave the devs alone here
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
andQlimax said:
i dont know how replicate this 4.2 SOD, but there is a simple way to avoid it, put all animations inside developers option to 1.0
it doesnt happen anymore to me, stock rom and kernel (i have automatic brightess on if this can matter)
if i put all animations to off or to 0.5, when the screen time out and became black, sometimes it doesnt wake anymore..4.2 sod
Click to expand...
Click to collapse
When I was running the first few nightlies of CM10.1 it still did the "sod" on me. By default the animation settings are at 1.0. Not sure if it's different on stock.
I've had several sod's daily for last few day's and today finally flashed RBJ from the beginning plus dax's modified kernel and now i'm in watching phase. So far so good.
I have time without any sod... Maybe because I'm trying not to use auto brightness or because of the lastest versions of Francos kernel... Stock ROM
Sent from my Galaxy Nexus using xda app-developers app
Hi everyone,
Any help here is appreciated.. I have a moto 360 v2, had it for about 5 months and gave up on it a few months back because it was so laggy and glitchy.
Got it out again a week ago, thinking maybe new updates or whatnot would get it up to speed, and having the same results.
The watch was unresponsive 80% of the time, and spent most of its time flipping in between awake and dimmed, so I turned off AOD as suggested in other posts (although it should have been fixed as I am on the recent firmware?). I also turned off the "lift wrist" wakeup gesture. Now if I touch the screen or press the side button, it usually turns the screen on and then instantly back off. If I can get it to stay on I can open notifications about 50% of the time, the other 50% the screen is unresponsive. Lastly, if the side button opens the apps its a miracle, and I can scroll through the apps briefly before becoming unresponsive.
I've tried factory reset and the above two fixes.
I just tried recovery mode, but the screen doesnt work in recovery mode so I can't swipe between options..
I have emailed Motorola but haven't heard back yet.
I'd love for this device to work well, as it seems like a great device, but its basically unusable atm.
Any help/suggestions would be great!
Thanks
hi All i received my oneplus 5t yesterday and installed oxygen os oreo beta from hydrogen os.
and it works fine but after half a day the phone screen suddenly went black i tried to restart the phone and it walk up but after that the screen went black again i never turn on again fingerprint vibration and led still working anh help please? :crying:
Did you try a hard reset?
same here: black screen (only some rows of pixels on the top slightly light up for a brief moment when i press the power button to toggle on the display), vibration and speakers still working, even the touch functionalities are working (6 AM alarm clock still rings and i have to guess where to slide on the screen to snooze). Tried to hold the power button, rebooted, but nothing else happened and the screen is still black. Seems like an hardware problem... what do you think about it?
Hello. This is my first thread, I have downloaded maybe hundreds of ROM's from this site, have read thousands of threads and of course bricked a few phones lmao. Now I am here with a REALLY confusing problem. Without further ado, let's dive in. sry for my bad english btw.
I bought a second hand S9 today. The guy whom I bought the device told me, when he turns off the screen of the device by pressing the power button, black and green lines appear when he turns on again, and after a few seconds, when he turns the screen back on by pressing the power button, the problem disappears he told. I think he said there is a problem in the part called screen flex. (I ain't sure what that is, I need info about that too.) Sorry if you're confused this far, cuz more is coming thru
I got a very useful APK file named "OLED/AMOLED Saver" and installed it on my device, it worked really well and the lines were almost invisible anymore. After a few hours of use, what I noticed was even more confusing. I activated the AoD (Always on Display) feature, coincidentally, while testing the screen, when I locked the device by pressing the power button and the clock appeared on the AoD screen, when I turned on the screen in that way, I noticed that the screen did not burn in as if it was brand damn new. But if I don't wait for the AoD screen to show up and immediately press the power button again, the screen turns on completely and something really, really terrible appears, a mixture of black and green. Now let's come to my questions, I've blown your mind a lot I think.
1- Can anyone explain what's going on here?
2- Is the problem in the screen flex or is it purely software? (AoD thing)
3-Is there anyone who has experienced this and was able to completely solve the problem?
Thank you for spending your precious time. Hope I get a solution..
Hello, I have same problem with my old S9, it seems that is fully hardware issue, as a workaround you can set full brightness - it causes this issue to appear less frequently and another option is cooling down the phone - when display is black/green just lock the screen and put your phone to the freezer for a while - it will work properly until it heats again
Its something about an update made by Samsung https://eu.community.samsung.com/t5...t-bars-black-screen-issue/td-p/1745470/page/4