Just moved from MeanBean to a couple of CM based ROM's, first Dirty Unicorns latest, now Deck's CM11 build, and I'm having trouble with the screen. The phone boots up fine and opens the ROM and everything is quick, but when I lock the screen, I can't get it to turn back on. When I press the power button, the buttons light up below the screen, but the screen doesn't do anything. Only way I can fix it is to power off and reboot via power button long press, but it does it again when I boot back up. Any thoughts?!?
I'm running the latest CM 10.2 Rom and mine does kinda the same thing. When it locks and the I try to unlock it the screen won't turn on but the buttons light up. But I don't have to restart the phone. It just takes a couple tries with the power button. But it would be nice if someone knew how to fix the issue.
Sent from my EVO using Tapatalk
There's talk in Deck's CM11 thread that the screen wake issue might be an issue with the Interactive governor. Try switching governors and see if the issue persists.
Sent from my HTC EVO 4G LTE
Search for an issue called screen on lag. Finz is right, interactive might be causing issues. Try ondemand. No current permanent fix is available at this point in time.
Sent from my EVO
Old thread I know, but I'm hoping someone might know a little more about this by now. I'm on the latest Lineage build for my EVO and it actually runs really well. Only problem is the power button screen wake issue. I've tried different governors, but nothing seems to make a difference.
Related
After multiple fails with MTD based ROMs (sdcard issues), I've settled in to TSM resurrection 1.0 (EI20). One thing I can't find mentioned in the ROM thread is a problem I'm having where the screen will randomly turn itself on from sleep. Usually when this happens and I try to push the power button to turn the screen back off, it won't turn off, but instead takes a screenshot. Has anybody else encountered this issue or know what to do with it?
I'm running TSM resurrection with the base kernel from PWGB, no other mods (XIX, heap size, etc). I don't know if this is related, but my battery usage also shows that the email app has been awake for 18m. Could there be a problem with that app that is causing the screen on issues?
I had the exact same issue as you which sadly made me revert back to PWGB with GeeWiz kernel. The screen capture happened all the time for me (it was the worst in the car dock). From my troubleshooting I was not able to fix it (tried different kernels, task killers, etc.). The closest thing I could pin point was it had to do with the soft key back button. The phone thought I was holding down the back button and I would hit the lock button which would cause the screen shot. As far as the screen coming on, I have had that issue with multiple ROMs, but it never really caused problems for me. Hopefully this helps a little.
I'm not sure where off the top of my head, but there is a screenshot.apk you have to delete to stop the phone from taking screenshots. It's been discussed a few times on xda where. Maybe search for it?
"better to be safe than to be odining" -me
Odd. That was happening for awhile, but not since I wiped data, reflashed, and installed the most recent TKSGB kernel.
When it does happen, push the back button. It should stop the screenshots.
I can't remember which rom I'm on (probably the one in my signature, can't remember if I updated it since then lol), but I've been having this issue for a little while now, but sometimes (can't quite figure out what triggers it) I lock my phone and my screen won't turn back on when I hit the lock/power button to turn it back on. Also sometimes I go to lock my phone and the screen will turn off then immediately back on, showing the lock screen. I love everything about the rom except this bug. I don't want to have to pull the battery constantly and it's getting very annoying. I do know I'm on 3.6, but can't remember which rom I'm on. Please help!
Flash different rom? If it sticks on another rom, it's a hardware issue, and you should get it replaced by Verizon
I had this same exact problem I posted about a while back. I linked it to my use of turboprop. Everytime i hit the on button the backlight would turn on but the ui would never come up. Reflash your rom and not turbo after a good wipe. my problem got fixed.
I've had this problem on my GSII (SGH-i777) since playing around with ICS roms, in both AOKP and CMD.
What happens is, after locking it, or a program is supposed to wake it from a blank screen, nothing happens when pressing the power button. The phone is still on and the buttons on the bottom still light up and I can feel vibrations and sounds, but I cannot get the screen to come back on without rebooting.
I'm not sure what causes this and it seems to feel semi random, but I suspect it may be connected to the locking animation in some way introduced in ICS (the emulation of turning off a CRT monitor).
I'm wondering if anyone else has run into this problem and knows a good fix to avoid it (other than going back to stock firmware).
What app are you using that is supposed to wake your phone? Just my opinion but it sounds like an issue with the app.
PS. Crt off animation was introduced well before ics.
ThomasBags said:
I've had this problem on my GSII (SGH-i777) since playing around with ICS roms, in both AOKP and CMD.
What happens is, after locking it, or a program is supposed to wake it from a blank screen, nothing happens when pressing the power button. The phone is still on and the buttons on the bottom still light up and I can feel vibrations and sounds, but I cannot get the screen to come back on without rebooting.
I'm not sure what causes this and it seems to feel semi random, but I suspect it may be connected to the locking animation in some way introduced in ICS (the emulation of turning off a CRT monitor).
I'm wondering if anyone else has run into this problem and knows a good fix to avoid it (other than going back to stock firmware).
Click to expand...
Click to collapse
Try turning off CRT in system setting / ROM Control / General UI / uncheck CRT off animation. I have it off and never have a problem in AOKP
This guy probably didn't wipe everything before posting. Yes this includes your data.
Sent from my MB860 using Tapatalk 2
In two different AOKP roms (AOCP, PACman), I have a problem where if I'm on a call and forcefully turn the screen off by pressing the power button (as opposed to by the prox sensor or by timeout), the phone reboots. Interesting, if there's audio on the call, it will continue to play as the shutdown animation is playing.
I have the accessibility setting to end calls with the power button turned OFF. I can't think of any other settings which would affect this.
I tried searching on this symptom, but didn't find anyone with this issue. I clean installed both ROMs, but AOKP seems to be a common denominator. Anyone have advice for me?
Does it ever reboot at other times after you've pressed the power button, or is it only while in a call? I recently had a problem where the phone would reboot after I turned it on. I was on CM and went to SHOStock and it still did the same! I figured, hell, after two different ROMs and it still acting the same, maybe it was hardware. Ended up taking the phone apart and there was some gunk around the inside part of the power button keeping it held in too far and triggering the reboot after a few seconds. After removing the button and carefully cleaning it (it's very small), I now no longer have a reboot problem on either CM or SHOStock.
sbrown23 said:
Does it ever reboot at other times after you've pressed the power button, or is it only while in a call? I recently had a problem where the phone would reboot after I turned it on. I was on CM and went to SHOStock and it still did the same! I figured, hell, after two different ROMs and it still acting the same, maybe it was hardware. Ended up taking the phone apart and there was some gunk around the inside part of the power button keeping it held in too far and triggering the reboot after a few seconds. After removing the button and carefully cleaning it (it's very small), I now no longer have a reboot problem on either CM or SHOStock.
Click to expand...
Click to collapse
I've only had it happen so far when turning the screen back on during a call. If I don't force the screen off in the first place, the phone will happily turn the screen on and off due to prox sensor. It will also time out and let me turn it back on without the power button with no issue. Because of this, I don't believe it's a mechanical issue. I didn't have this problem until trying AOKP ROMs, the timing is too coincidental.
Based on what I'm seeing with the boot animation, it isn't a full reboot (I don't see the SGS II logo, for example). I didn't even know that rebooting only the OS was possible.
I assume there are logs I can check to help figure out what's going on, but I don't know where to find them.
I found a string of posts in the Carbon thread: http://forum.xda-developers.com/showthread.php?p=46998058&highlight=just+carbon+reboots#post47133798. Same symptom, but different trigger. I tried, I can rotate the camera just fine. I'm currently running the 10/31 nightly of PACman, guess I'll update past 11/2 later today and see what happens.
11/6 was a bust (lots of FCs after a clean install), so now I'm trying 11/10, 11/4, or 11/5.
Initial results with 11/10 show that the problem is fixed; gonna restore my old ROM, go through the TiBu dance, and see what happens when I finish setting up 11/10 completely. Maybe it's something I'm doing.
OK, 11/10 fixed my primary issue. Further, I used to have pretty nasty screen-on lag that I couldn't fix even after messing with the CPU and I/O profiles. Hurray!
Based on my experience this may affect other AOKP based ROMs (like Carbon or AOCP), but it might have been present in pure CM (CyanogenMod) - hard to tell. Hope this helps someone else.
****, it's back. Must be something I'm doing. The quest continues...
Hi all..
I have a problem with my DNA. Sometimes, like maybe once every few weeks or so, the touch screen will not respond correctly.
Here's what happens:
1. I turn on the display while the phone is already running. (meaning, I'm not booting up when it happens)
2. I try to slide the unlock widget up but it doesn't respond.
3. I hold the power button, and it says to continue holding it for 3... 2... 1.. seconds. However, at 1 seconds, it never does anything. I've held it for 2 or 3 minutes at times, and no reboot.
4. I swipe randomly around the screen and notice that some of my quick launch icons or the unlock slider bump up momentarily, but not enough to unlock the phone.
5. I continue swiping randomly, with a random number of fingers, and eventually the stars align and the phone is unlocked.
6. Once the phone is unlocked, tons of random touch presses occur. Random apps will open, messaging, etc. Sometimes, it opens the phone app and randomly presses things. It does this at a very, very rapid rate. I usually panic and turn off the display so it stops.
7. I manage to unlock it and hold the power button until the "Reboot/Shutdown/Airplane Mode" window appears and STAYS on the screen long enough for me to tell it to reboot.
8. After it reboots, the problems are gone and the touch screen returns to its proper functionality.
Has anyone had this problem before or know why it's happening? Or what can contribute to it?
Insertcoin rom or any kernel?
It's kernel issue. I have same problem. Flash another kernel fix it
Sent from my HTC Droid DNA using Tapatalk
Huongnv said:
Insertcoin rom or any kernel?
It's kernel issue. I have same problem. Flash another kernel fix it
Sent from my HTC Droid DNA using Tapatalk
Click to expand...
Click to collapse
Forgot to give some info:
I'm on default Rom, not rooted, nothing special.
To fix this problem, should I go ahead and root and install a new Kernal?
Garmy said:
Forgot to give some info:
I'm on default Rom, not rooted, nothing special.
To fix this problem, should I go ahead and root and install a new Kernal?
Click to expand...
Click to collapse
Flash a clean rom
U can use stock img with latest 4.4.2 sense 5.5 official or viper 4.4.2 sense 6
Sent from my HTC Droid DNA using Tapatalk
My screen started doing this, for me it is hardware failure. When you enable "show touches" from developer options, does it show 3-7 ghost touches? Mine is doing this (shattered screen and that is the only side effect, ha)
Sent from my HTC6435LVW using xda app-developers app