Alright, I've been having this "glitch" on 2 GSIII's. When I hit he power button to lock my phone and what not and then click the physical button to turn it on I always have to hit it multiple times to get the screen up. I've had it on both Liquid Smooth & Codename ROMS and the kernel is the newest version of KT746. Any help or way I can fix this? Its rather annoying..help is greatly appreciated.
Also, my phone is getting really hot quickly, even when all I do is text..
STVERDI said:
Alright, I've been having this "glitch" on 2 GSIII's. When I hit he power button to lock my phone and what not and then click the physical button to turn it on I always have to hit it multiple times to get the screen up. I've had it on both Liquid Smooth & Codename ROMS and the kernel is the newest version of KT746. Any help or way I can fix this? Its rather annoying..help is greatly appreciated.
Also, my phone is getting really hot quickly, even when all I do is text..
Click to expand...
Click to collapse
Have you overclocked at all??? I use my phone very very heavily and have NEVER felt any heat or anything...... As far as the screen issue that could also be the kernel or very possible even the ROM itself.... I know for a while mine wouldn't respond to touching it after I woke it up I would have to hit the power button to darken the screen and wake the screen again... but after a few times it solved itself....
dr12volt1338 said:
Have you overclocked at all??? I use my phone very very heavily and have NEVER felt any heat or anything...... As far as the screen issue that could also be the kernel or very possible even the ROM itself.... I know for a while mine wouldn't respond to touching it after I woke it up I would have to hit the power button to darken the screen and wake the screen again... but after a few times it solved itself....
Click to expand...
Click to collapse
Yes, I'm OC'd to 1809. I'm beginning to believe its the kernel (KT747), this problem has followed me from CM10 Night lies, CNA, Paranoid, and so on and so forth.
I just disabled over clocking and it still took me twice to hit the physical button in order for my screen to come on.
I had this problem on mine when i used the CleanKernel. It would take like 5 or 6 times of me pressing the power button to get it to respond. I changed the kernel back to the stock original kernel via a naindroid backup and i have not had the problem since. Im nervous to flash other roms cause of that issue. Im waiting for more stable builds even though i really wanna try Synergy.... lol
Set from my Verizon Stock Rooted (Modded) Galaxy S3 using xda-developers app
It seams to be kernel related, was running kt with slimbean and could not get power button to wake up the device. Changed to lean and it works when it wants to. I also had the same thing happen on cm9 on another device, so it may just be an aosp thing. Be sure that the option is selected in the main menu too, but as of now I think it is what it is.
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
---------- Post added at 06:31 PM ---------- Previous post was at 06:31 PM ----------
Edit: home button
Sent from my VZW GS3 running Synergy/Trinity/Dark Horse Rises
Related
usually you will get the black screen of death when:
-after a phone call
-during/after charging
-when hitting the power button to turn off or turn on your screen.
do you think that the gingerbread launcher is causing this problem?
Ive read on other forums on different phones that the launchers were causing the same problems on their phone as well and when they switched launchers, it all stopped.
is this a reasonable explanation?
Nope. It happens to my wife on GO Launcher as well.
Sent from my LG-P999 using xda premium
??
what is the black screen of death? or am i better off not knowing. lol
i have go launcher on my phone and wad curious if i have experienced the black screen of death. sounds scary lol
Aestetics said:
usually you will get the black screen of death when:
-after a phone call
-during/after charging
-when hitting the power button to turn off or turn on your screen.
do you think that the gingerbread launcher is causing this problem?
Ive read on other forums on different phones that the launchers were causing the same problems on their phone as well and when they switched launchers, it all stopped.
is this a reasonable explanation?
Click to expand...
Click to collapse
Only SOD I ever come across is the call SOD. That happens when running Trinity kernel on CM7 or CM7 based roms. Morfics updated Trinity kernel I assume has fixed the SOD as I haven't come across it while running CM7's nightly 199.
Sent from my LG-P999 using XDA App
suicidalintentions said:
what is the black screen of death? or am i better off not knowing. lol
i have go launcher on my phone and wad curious if i have experienced the black screen of death. sounds scary lol
Click to expand...
Click to collapse
This is when your phone goes on permanent "sleep" as in your screen wont turn on. Only way to turn it on is to do a batt pull and reboot.
Sent from my LG-P999 using XDA App
i use 2.3.7 eaglesblood running the trinity kernal and knocn on wood no problems at all. Hope i dont get that phone disease.
The kernel is the problem. I've said it a million times. Its why CM7 based roms don't do this and those with custom kernels. My Asus transformer did this (tegra 2) until a custom kernel came out.
Change the kernel and fix the SoD.
LG G2x - 2.3.7 CM7
Asus Transformer - 3.7 Revolver OC/UV
Black Screen of death
I recently flashed EB 2.3.7 / 2.5 (runs amazing by the way) but have one small issue. When charging my phone at night it goes into perm. sleep mode for the last 3 nights. My wake up call never goes off . I read somewhere it may be kernel related, so I flashed faux .46 hoping that would resolved sleep issue. It has not, anyone else have any insight?
Thanks.
That happens sometimes or stock ROM.
Sent from my LG-P999 using xda premium
gman87 said:
This is when your phone goes on permanent "sleep" as in your screen wont turn on. Only way to turn it on is to do a batt pull and reboot.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Hold the power button down for a long time. After about 30-45 seconds, something will usually happen. Sometimes the home screen will flash on for a second and then go black again, sometimes the home screen will come on but will be in a frozen state and won't accept input, and sometimes the screen will come back on normal. This will allow you to avoid a battery pull maybe a quarter to a third of the time you get an SOD.
When I wake the phone after installing this ROM, It takes 2-3 seconds before taps on icons are functional. Almost like the device is still half 'asleep'.
Anyone seen this? Any suggestions?
I really like this ROM and would like to keep it, as it is pretty Vanilla and I prefer the pure Android experience.
Thank you for your time.
Chris
cditty said:
When I wake the phone after installing this ROM, It takes 2-3 seconds before taps on icons are functional. Almost like the device is still half 'asleep'.
Anyone seen this? Any suggestions?
I really like this ROM and would like to keep it, as it is pretty Vanilla and I prefer the pure Android experience.
Thank you for your time.
Chris
Click to expand...
Click to collapse
Have you checked voltages? Perhaps your min cpu speed is very low keeping your phone from fully waking. I cant say for sure thats the problem but its a start. Some kernels can be undervolted to as little as 194mhz which can cause it not to wake. AOSP roms on the S3 have come a long way but still have issues. Hope this helps.
Like the previous post said, first thing is to check voltages. Next I would check min and max CPU clock speeds. If those don't work, consider flashing Lean Kernel. I love the Liquid and Lean combo.
I guess you could also check and see how many programs you have running. Hold home button til they pop up. If you have a ton of running apps then that could also lag you down.
jmarch said:
Like the previous post said, first thing is to check voltages. Next I would check min and max CPU clock speeds. If those don't work, consider flashing Lean Kernel. I love the Liquid and Lean combo.
I guess you could also check and see how many programs you have running. Hold home button til they pop up. If you have a ton of running apps then that could also lag you down.
Click to expand...
Click to collapse
Thank you very much. I will make the adjustments and see what happens.
Hi. I have been running pacman v22.0.1 for quite some time now and I could quite easily make and receive calls with no problems, the rom was fast and battery life was great. But quite recently, I received a call and answered it spoke but when it came to ending it, I couldn't get the screen to turn on and all that happened was the button backlights were flashing like mad! So I left it for a while and came back to the phone which had dropped from 84% battery to 41% and it was running very slow. Later when I tried making a call, I couldn't hear anything and I couldn't end the call which led to a charge of £5 which isn't too much money I'm not too fussed with that. But I switched to another rom then wiped everything and flashed pacman again but still had the same problem. Is there anybody who is facing the same problem or has a solution? I have tried on 4 different 4.2 roms now and have experienced the same problem with all.
Just uploaded a very, very long log cat if you are a dev or have knowledge of logs, please read!
Problem solved, it was my screen protector which was covering my proximity sensor and jelly beans behaviour with the proximity sensor caused it to stay off. When buying a screen protector always make sure it has a hole or gap of some sort for the proximity sensor. The bug in the log cat was something else which was fixed by a build.prop tweak.
My radio is 3831.19.00.110
ifti786 said:
I couldn't get the screen to turn on and all that happened was the button backlights were flashing like mad! So I left it for a while and came back to the phone which had dropped from 84% battery to 41% and it was running very slow. Later when I tried making a call, I couldn't hear anything and I couldn't end the call which led to a charge of £5 which isn't too much money I'm not too fussed with that.
Click to expand...
Click to collapse
Were you rapidly pressing the power button? Occasionally, I find my phone lags when turning the screen on, I press the power button once and the buttons light up, then I don't press it again and wait for the screen to turn on. If it is pressed a second time, it means "turn the screen off again", so you never see it turn on.
paulie-uk said:
Were you rapidly pressing the power button? Occasionally, I find my phone lags when turning the screen on, I press the power button once and the buttons light up, then I don't press it again and wait for the screen to turn on. If it is pressed a second time, it means "turn the screen off again", so you never see it turn on.
Click to expand...
Click to collapse
That could just be it: the reason for my problem is my impatience! Still need to check though...
No, that didn't fix it. I think it might have something to do with my proximity sensor because on vipersaga, it used to turn the screen on when I moved my phone from my ear but now it doesn't so I have to press the power button.
Also have the same problem on jelly bean fire
Sent from my HTC Desire S
Please help because I really want Jelly Bean 4.2 but at the current moment, it looks like my desire s is incapable of running it!
I flashed the ROM this morning and everything is well except of GPS (or is it just invisible?) and no weather on the cLock widget (btw any ideas here anybody?). I had issues of the screen keeping black with backlightes hardware buttons (and some others) with v21. But I never tried to use the phone for calling somebody with that, cause it was merely a stage facing the best ROM for me.
Did you do full wipe and Dalvik cache wipe? I found it is very useful to do so, cause it eliminates uncertainties the kind of "where does this come from?".
sanilii said:
I flashed the ROM this morning and everything is well except of GPS (or is it just invisible?) and no weather on the cLock widget (btw any ideas here anybody?). I had issues of the screen keeping black with backlightes hardware buttons (and some others) with v21. But I never tried to use the phone for calling somebody with that, cause it was merely a stage facing the best ROM for me.
Did you do full wipe and Dalvik cache wipe? I found it is very useful to do so, cause it eliminates uncertainties the kind of "where does this come from?".
Click to expand...
Click to collapse
Wipe all partitions except sd card AMD done this on pacman v22.0.1, JellyFireBean, JellyTime, flinny cm10.1 and AOKP redefined. I have just flashed a new radio and will check if that fixed it
Flashing a new radio did not fix the problem please somebody help!
ifti786 said:
Flashing a new radio did not fix the problem please somebody help!
Click to expand...
Click to collapse
I've got the same problem. My screen won't turn on after I move the phone away from my head after a call, altho I can turn it on with the powerbutton somehow. Happens on all JB ROMs for me aswell.
I tried Proximity Sensor Finder app from play store and it says 9cm when theres nothing infront of the sensor, then goes to 0cm when there is something, but doesn't go back to 9cm when the sensor is free again. It only goes back to 0cm when I restart the app.
I don't know whats the problem, but I think its software related.
Is the s2w turned on? If so, it could be the problem. BTW, the problem with black screen but capacitive button lights turned on, also have I. I see it, when I turn off the screen and try to turn it on after 5-10 seconds. But waiting a little helps.
Running Pacman 22.0.1
NVardan said:
Is the s2w turned on? If so, it could be the problem. BTW, the problem with black screen but capacitive button lights turned on, also have I. I see it, when I turn off the screen and try to turn it on after 5-10 seconds. But waiting a little helps.
Running Pacman 22.0.1
Click to expand...
Click to collapse
S2w is off, tried waiting too and that didn't help. I took a log cat of what happened and can upload it if wanted. My friend is taking a look at it for me to see whether there's a bug. It could have something to do with the build.prop.
ifti786 said:
S2w is off, tried waiting too and that didn't help. I took a log cat of what happened and can upload it if wanted. My friend is taking a look at it for me to see whether there's a bug. It could have something to do with the build.prop.
Click to expand...
Click to collapse
Maybe you should upload the logcat in the PACman thread.
Ok will do that now
Sent from my HTC Desire S
NVardan said:
Maybe you should upload the logcat in the PACman thread.
Click to expand...
Click to collapse
The log cat is waaaaaaay too long, I've sent you a message, anybody else who wants the log cat, ill pm you.
ifti786 said:
The log cat is waaaaaaay too long, I've sent you a message, anybody else who wants the log cat, ill pm you.
Click to expand...
Click to collapse
Unfortunately I am NOT a developer so I can't help you.
You must copy-paste your logcat in a .txt file and upload it in the PACman thread.
Sent from my Desire S using Tapatalk 2
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
sarcome said:
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
Click to expand...
Click to collapse
Right, I've just had a look through the logcat and i've found a bug. I'm going to try some build.prop tweaks and see what the results are. I will let you know but please bear in mind that it might take some time as I am having some very important exams coming up so I'm going to be revising in most of my free time.
sarcome said:
I'm having the same problem with JellyFireBean v2. I ended up leaving a few voicemails without knowing, and it cost me 10$ from abroad...
I installed an app that gives information about all the sensors (sensor kinetics). When I start the test it shows a distance of 9cm, then I put my hand over the phone and it shows 0 cm, but then I remove my hand and it stays at 0, exactly like when I make a call.
Click to expand...
Click to collapse
Do you have a screen protector on your phone by any chance?
My infuse is randomly turning off (not bootlooping). No particular time of the day. It is not critical but very annoying. Almost evertime I need the phone quickly, it appears off.
Currently running [ROM] 4.2.2 - Jellybean - AoCP 5.6 - The Collective - Final and it appears fine. I am also using an extended battery and though the case back was loose, so I checked that and put in a small wad of piece of paper as a filler to pack the battery in a little more and also cleaned all the terminal connections between battery and phone.
Just wondering if anyone else is having this issue and what to do to correct it?
yes i think its a pretty normal issue for a Infuse. Mine was doing that when i was running Froyo. Now it just reboots.
GutterGuppy said:
yes i think its a pretty normal issue for a Infuse. Mine was doing that when i was running Froyo. Now it just reboots.
Click to expand...
Click to collapse
Reboot is the power button issue (most of the time). This one likes to turn off. Since I padded the case with a little wad of paper, no turn offs but I suspect, now that I said it, it will start turning off again...LOL.
I've had issues with the phone mysteriously turning off ever since running JB. Maybe ICS too. I don't recall ever having an issue with 2.2.
We have five infuses in my family....3 on Froyo and two on GB. I am the designated troubleshooter. (geek)
We have occasional reboot, often during heavy use. I'm not sure I've ever seem them turn off...if it has happened, it's not often.
Sent from my SAMSUNG-SGH-I997 using Tapatalk 2
Its the power button. Lots of people have the issue. What I recommend is upgrading to a rom (Beanstalk for example) and in the settings have the volume buttons also turn on the screen and then download a remapper that you can change the power button
Sent from my SGH-I997 using xda premium
toxicpaulution said:
Its the power button. Lots of people have the issue. What I recommend is upgrading to a rom (Beanstalk for example) and in the settings have the volume buttons also turn on the screen and then download a remapper that you can change the power button
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
You sure about that? wouldn't power button issues making the phone restart rather than simply turn off?
I guess if the power button did not work at all and simply was non-responsive the phone could be on and you'd never know it for sure, but at least in my case I know I've missed phone calls when it's off so i dont think that is the case.
I don't think it is the power button issue. It randomly turned off, it did not just reboot. Since I added a piece if paper between back and battery, it has only turned off once. Prior to that it was turning off a couple of times a day.
Sent from my SGH-I997 using xda premium
Anyone having issues with the screen not turning on? The home button still has the haptic feedback but nothing happens after that. The power button doesn't do anything either. Not sure if this is a defective phone or a s8+ overall issue...
Yes.. mine locks up frequently. Hold volume down and power until it responds
Haven't had this problem as of yet, and I have over 130 apps installed onto my phone. Transferred from Google first and Smart Switch after that. Haven't had a single problem.
seem the people in this link are having the same issues: https://forum.xda-developers.com/galaxy-s8+/help/phone-freezing-rebooting-unlocking-t3593075
hopefully its just a minor software glitch that can be fixed
topaz330 said:
seem the people in this link are having the same issues: https://forum.xda-developers.com/galaxy-s8+/help/phone-freezing-rebooting-unlocking-t3593075
hopefully its just a minor software glitch that can be fixed
Click to expand...
Click to collapse
For whats its worth i had the same issues the first day and a half. After everything got set up and running it hasnt done it yesterday or today. Its so smooth and fast now.
topaz330 said:
Anyone having issues with the screen not turning on? The home button still has the haptic feedback but nothing happens after that. The power button doesn't do anything either. Not sure if this is a defective phone or a s8+ overall issue...
Click to expand...
Click to collapse
Press it twice in a row
Sent from my SM-G955U using Tapatalk
---------- Post added at 04:59 PM ---------- Previous post was at 04:58 PM ----------
Twice in a row takes you to the swipe screen lol I thought WTF too at first
Sent from my SM-G955U using Tapatalk
topaz330 said:
Anyone having issues with the screen not turning on? The home button still has the haptic feedback but nothing happens after that. The power button doesn't do anything either. Not sure if this is a defective phone or a s8+ overall issue...
Click to expand...
Click to collapse
I'm also getting this issue on my S8. Wondering if it's related to the always on lockscreen
Is this a serious issue?
---------- Post added at 08:02 AM ---------- Previous post was at 07:58 AM ----------
Take it back for warranty
Just had this happen for the first time in the two weeks I've owned the S8+. Restart resolved it for now.
Had my phone since a day or 2 before launch and have not had this problem.
try to reboot a few times and also clear out the cache.
I remember the s7e had this problem and about 1 out of 20ish time the phone wouldnt wake up on first try. But they sent out an update to fix it.
strongsteve said:
Yes.. mine locks up frequently. Hold volume down and power until it responds
Click to expand...
Click to collapse
I came here looking for answers, since I was experiencing the same problem (although no haptic feedback). This solution solved the problem. Got me into recovery mode, where I was able to turn off the phone and reboot.
Some of the answers suggested restarting. I don't think they understood the problem. The OP stated the power button was not working, as was my case. So 'just restarting' was not a solution.
I'm having the same issue but it started a couple weeks ago after I installed a firmware updated. It has happened 3 times since then, and never happened before that since I got the phone (on launch date a few months ago).