For the past few weeks, my screen has been turning on Randomly, and then staying on until I shut it off. This happens sometimes when I'm unplugged, but more often when I'm plugged in. When the screen is on, I also find that the screen will dim after a few seconds (my timeout period) and then brighten back up again.
The up time is 13 hours on it right now, and the awake time is around 8 and a half hours, so I'm unsure if this could be considered a wakelock issue, although it has a lot of similarity's.
I know it must be one of my apps's doing it, but I'm not sure where to start to find out which one is doing it. I'm using Synergy Rom R318. I would consider just uninstalling each app until I found the culprit, but the screen on issue happens randomly, and it could go 15 or 20 without actually turning on.
DeMiNe0 said:
For the past few weeks, my screen has been turning on Randomly, and then staying on until I shut it off. This happens sometimes when I'm unplugged, but more often when I'm plugged in. When the screen is on, I also find that the screen will dim after a few seconds (my timeout period) and then brighten back up again.
The up time is 13 hours on it right now, and the awake time is around 8 and a half hours, so I'm unsure if this could be considered a wakelock issue, although it has a lot of similarity's.
I know it must be one of my apps's doing it, but I'm not sure where to start to find out which one is doing it. I'm using Synergy Rom R318. I would consider just uninstalling each app until I found the culprit, but the screen on issue happens randomly, and it could go 15 or 20 without actually turning on.
Click to expand...
Click to collapse
Are you using an Evo 4G or an Evo 3D? I know this is the Evo 3D section, but I ask because I noticed that on my 4G right after I got even before installing any apps. It would only happen when it was charging but I ignored it assuming it did that when the battery went to 50%/75%/100%. After getting my Evo 3D, I saw that I no longer had this issue. If it is because of the battery charge levels, I'm sure you can flash a mod to disable it.
Shouldn’t you be able to use an app like Watchdog Task Manager by Zomut to track the app down?
https://market.android.com/details?id=com.zomut.watchdoglite&feature=related_apps
I'm gonna run logcat and see what pops up.
This happened to me on my Evo 3D as well. It was happening using SteelROM ROM. It was odd because it was on the desk, disconnected, and it'd light up and, if I didn't touch it, dim down and then brighten up again, and would not shut off until I clicked the power button to "lock" it.
After I flashed ShooterRewind RLS3, I haven't had this issue again. I don't know if it is ROM related, or something else that was replaced with ShooterRewind.
Just something to consider, though I'm no expert. Also, each ROM comes with its own set of apps, and with some other apps removed. So it could have been one of the apps that was on SteelROM but not on ShooterRewind. I am using RCMIX 3.0 beta kernel, if that makes any difference.
Related
I've noticed a handful of times that if I don't turn my screen of manually, it does not shut off. battery will be nearly dead, phone hot, and the screen still on an hour later. I have it set to turn off after one minute, but it does not always work. Anyone else run into this?
Sent from my PG86100 using Tapatalk
Yes, mine is doing that as well. Did you find out anything about why this is happening?
Rob the plumber said:
I've noticed a handful of times that if I don't turn my screen of manually, it does not shut off. battery will be nearly dead, phone hot, and the screen still on an hour later. I have it set to turn off after one minute, but it does not always work. Anyone else run into this?
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
nelanka said:
Yes, mine is doing that as well. Did you find out anything about why this is happening?
Click to expand...
Click to collapse
I'm on a stock ROM and I haven't noticed the screen stay on longer than the timeout i have set, currently 1 min. Although, I might be in the habit of turning the screen off when I'm done, I do think I've left the screen many times and it always turns off as I've never noticed the screen being on for long periods of time.
One thing which does come to mind, is there is an app which I use that has a setting to keep the screen on while the app is open. Perhaps if you have one of these apps open, it would lock the screen on. Do you run any apps like that?
Are you guys rooted? HTC or Revolutionary unlock? What ROMs/kernels are both of you using?
I was installing some apps on my phone and suddenly the screen turned off. When I tried to turn it on, nothing happened. I then let the phone sit for a minute and still nothing would happen until I noticed the buttons turning on and off. I tried swiping where the unlock would be when the buttons come on and it worked. I could tell from the tactile feel. I then rebooted the phone by pressing and holding the power button and guessing where restart would be. The screen works again.
Has anyone else experienced this problem? First time for me.
hpcolombia said:
I was installing some apps on my phone and suddenly the screen turned off. When I tried to turn it on, nothing happened. I then let the phone sit for a minute and still nothing would happen until I noticed the buttons turning on and off. I tried swiping where the unlock would be when the buttons come on and it worked. I could tell from the tactile feel. I then rebooted the phone by pressing and holding the power button and guessing where restart would be. The screen works again.
Has anyone else experienced this problem? First time for me.
Click to expand...
Click to collapse
I had it happen to me once, when I first got the phone. Exactly as you described, except I had to battery pull. I was using an app called Screen Filter, so I could dim the capacitive lights. I figured it had to do with that app, so i removed it. I haven't had it happen since. I'm not sure if it was Screen Filter that caused it or not, but I haven't had it happen again since I removed it. Either that, or just a coincidence.
Happened to me once when I was messing with a root script that had a bug. Ended up clearing some of my app data too. Seems like a common "brain death" state that the phone can get into. I'm pretty sure it's software related and nothing to worry about.
Mike
it happens to me often, and I too have screen filter... but that isn't the cause of the problem (i got it to dim the buttons but it doesn't work on those yet).
I'm not sure what the problem is, but you can eventually turn the screen back on and reboot it - just keep at it. Do you have anything plugged into the headphones jacks BTW? If you do, and you try to reboot, it'll hang. It's done that to me a few times so I unplugged the headphones everytime
Started happening to me after i installed either switkey x or the amazon app, i am not sure but i think that's what caused it
SwiftKey works fine for me... try reinstalling it. Same far any other apps that cause issues, make sure the download was good and reinstall.
If the phone freezes, remember that the only ways to get a try restart is a dead battery or battery pull. Wifes phone froze and shut off, would not restart until a battery pull.
Good luck!
Sent from my phone
Happens to me too and it is really irritating.
GhettoBSD said:
it happens to me often, and I too have screen filter... but that isn't the cause of the problem (i got it to dim the buttons but it doesn't work on those yet).
I'm not sure what the problem is, but you can eventually turn the screen back on and reboot it - just keep at it. Do you have anything plugged into the headphones jacks BTW? If you do, and you try to reboot, it'll hang. It's done that to me a few times so I unplugged the headphones everytime
Click to expand...
Click to collapse
It works perfect for dimming (well turning off) the buttons, check your settings!
so i keep having the same problem even without the swiftke y installed tried to reboot and even factory reset no luck. did you find any solutions.
used to happen a lot when i had aosp roms on my old hero
Are you guys overclocked?
I am not overlooked and I exchanged to another phone.
Sent from my PG86100 using XDA App
iliapiano said:
I am not overlooked and I exchanged to another phone.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Damn....I may have to do that. Sprint allowed you to exchange with no hassle? It seems to happen so randomly that I don't think my Sprint Store will exchange it if they can't reproduce it.
freeza said:
Are you guys overclocked?
Click to expand...
Click to collapse
My wife was oc when hers froze
Sent from my phone
I'm overclocked but the issue @ hand is software related. When I had the OG Evo, certain kernels would cause the screen to act in the same matter stated in the op. A lot of bugs that people report would be resolved once we get perm. Root.
My ''xDU4L C0R3 SH00T3Rx'' shot you down in 3D!
SO this has happened to me and I am freaking out thinking its the aosp rom. how long did it take for the screen to light up again. it been like two hours for mine.
been trying out this rom the past few days even though using sense roms is against my religion (i'll confess later and everything will be fine).
anyway, whenever i take it off of automatic brightness... like say, at night, i turn the brightness all the way down... once the screen goes off and i turn it back on, it's bright as hell again.
oddly, the brightness setting will still show that it's all the way down(even though it's bright as hell), so then i have to slide it up & then back down again.
and then it does the same thing all over again!
am i the only one experiencing this issue? is there a fix for it?
have you given up your booty to jesus?
voxigenboy said:
been trying out this rom the past few days even though using sense roms is against my religion (i'll confess later and everything will be fine).
anyway, whenever i take it off of automatic brightness... like say, at night, i turn the brightness all the way down... once the screen goes off and i turn it back on, it's bright as hell again.
oddly, the brightness setting will still show that it's all the way down(even though it's bright as hell), so then i have to slide it up & then back down again.
and then it does the same thing all over again!
am i the only one experiencing this issue? is there a fix for it?
have you given up your booty to jesus?
Click to expand...
Click to collapse
...nope. Ain't given up my booty to Jesus yet.
Never had that problem, but I haven't messed with screen brightness manually on beta8. Last time was Beta7 and it worked just fine. It does seem REAL slow on the brightness level uptake though. Like when you use the camera and it ramps up brightness all the way... it takes it about 30 seconds or so to readjust it.
Running the newest UnNamed and I'm trying to find a way to keep the screen on while charging from USB. The point is to keep the screen on while driving. At night I charge with AC power so that's not an issue.
I found posts saying there was a burn in problem with SMOLED screens being on with a static image for more than a couple minutes at a time. I haven't seen it personally but if anyone has first hand experience with this phone or the international model, please speak up before I damage my phone.
Otherwise, once again, it looks like I need Tasker for the job. Have it detect bluetooth connection for the car and upon usb power trigger car mode and keep the screen on at ~50% brightness. something like that.
With unnamed go to Settings>Applications>Development and click Stay Awake.
Try this first,
Menu->settings->Applications ->Development -> Stay awak
If not working , try this
Menu->settings->Display->Screen Timeout ->Never
Now I've never seen permanent burn in on my SGSII or Nexus One (even while on constantly during a 10h drive to Vegas). I was using a stop watch app on my Nexus One, and while only on for 5 minutes or so, I did see it burn in, but it went away after a few minutes of being off (boy was I scared when I first saw it though).
Now, I have personally seen permanent burn-in on a Vibrant (not mine).
Funny thing is the screen timeout is set to like 5 seconds on it, so it's barely on. Yet I can clearly see the clock is burned into the screen.
Have you tried running a car app to hold a screen lock? I know Google Maps can do that. Plus it doesn't require going into settings (at least more than once).
EDIT: As a simple observation, the burn-in seems worse when it's white on a black background.
I have run into these issues several times. They seem to be related, but I can't say for sure.
Every now and then while I'm actively using the phone, 1/2 the screen will go away and the phone will be unresponsive. If I shut off the screen, then turn it back on, it usually clears up. Sometimes the screen won't come back on. It stays off no matter what buttons I press. So I put it on the charger, that triggers the screen turning on and everything is back to normal (the battery is always over 50% or more at this point). Yesterday this got to a point of happening several times in 1/2 hour, so I ended up rebooting to see if it would clear it up. This issue did not come back since then.
On a similar note, I was playing a game this morning in a dark room with the brightness turned all the way down. I was being very active in interacting with the screen. Every now and then the screen would go black, except for the notification bar. I could still see that (time and statuses of things running). The screen would not respond to any touches, so I would shut the screen off and turn it back on and all would be good. This happened 2-3 times over a 45 min period. I play this game quite often, but not usually in the dark and often not as actively as I was doing. My resolution is set in the middle (FHQ+ I think it's called).
Has anyone else run into anything like this?
This S9+ snapdragon through Verizon just seems to be plagued with so many minor issues. I've never had a new phone with this many problems.
Brokk said:
I have run into these issues several times. They seem to be related, but I can't say for sure.
Every now and then while I'm actively using the phone, 1/2 the screen will go away and the phone will be unresponsive. If I shut off the screen, then turn it back on, it usually clears up. Sometimes the screen won't come back on. It stays off no matter what buttons I press. So I put it on the charger, that triggers the screen turning on and everything is back to normal (the battery is always over 50% or more at this point). Yesterday this got to a point of happening several times in 1/2 hour, so I ended up rebooting to see if it would clear it up. This issue did not come back since then.
On a similar note, I was playing a game this morning in a dark room with the brightness turned all the way down. I was being very active in interacting with the screen. Every now and then the screen would go black, except for the notification bar. I could still see that (time and statuses of things running). The screen would not respond to any touches, so I would shut the screen off and turn it back on and all would be good. This happened 2-3 times over a 45 min period. I play this game quite often, but not usually in the dark and often not as actively as I was doing. My resolution is set in the middle (FHQ+ I think it's called).
Has anyone else run into anything like this?
This S9+ snapdragon through Verizon just seems to be plagued with so many minor issues. I've never had a new phone with this many problems.
Click to expand...
Click to collapse
As a followup, I think I have found the problem. It seems to be with a product called Game Tuner. It can black out the screen while leaving the app running in the background. I think it is buggy. Doesn't seem to be a way to shut it off though.
Brokk said:
As a followup, I think I have found the problem. It seems to be with a product called Game Tuner. It can black out the screen while leaving the app running in the background. I think it is buggy. Doesn't seem to be a way to shut it off though.
Click to expand...
Click to collapse
I was able to uninstall, then install an older version of Game Tuner and the problem that was easiest to reproduce was fixed. Hopefully this will prevent the weird 1/2 screen thing as well.