Anyone know how to get the flashlight to stay on after the screen turns off on ICS based kernels? The light will stay on for a few seconds after the screen goes off but will then turn off until I press the power button to wake the phone back up. I've tried a few different apps with the same results. The only kernel that seems to work is Sebastian's over clocked kernel but I assume that it is based of GB. I'm sorry if this has been answered before, I tried searching but found nothing.
Related
So it seems that no matter what i do regardless of rom, kernel, bootloader version if I press the power button while my gtablet is awake, it will just shut off- maybe twice now it has successfully unlocked for me and came back to life.
The other night i did a test, with 100% battery set the brightness to its lowest setting using the power manger widget (this seems to be 30 out of 255 btw)
Idling while I slept (screen on, sitting at the home screen) it ran 10 hours and still had 16% left.
Obviously the screen still remains as the key battery drainer, so my question is- is there a way to turn the screen off but keep the cpu running? Perhaps even just kill the back light completely- and upon volume button press or maybe a certain swipe gesture on the screen, the back light could be re enabled.
Ive tried a few apps, none of which have functionality quite like this- I was wondering about perhaps a script we could run via terminal (that maybe could be tied to a shortcut on the homescreen..?)
Thanks!
the sleep of death is my #1 gripe with the deivce.
what i am more interested in is why this happens. I would imagine this doesnt happen in stock form, so it must be an issue with rooting it.
Nope
No it happend in its stock form too... even with the 1.0 fw that i started with...
Went for the update to 1.1 bl and 1.2 bl
I really haven't been able to determine the issue and ive tried every rom between 1.1 and 1.2 ... (at least all the obvious ones on the forums here...)
Not sure what to do other than suck it up and just find something that can kill the screen.
I've searched with several different search strings and haven't found an answer to this question, so here goes;
When I place a call and bring the phone to my ear the screen turns off (dims?). At the end of the call after I bring the phone away from my ear, it takes several seconds for the screen to turn back on, sometimes it doesn't turn back on unless I press the power button.
First, is this the normal behavior for the phone app on the I777?
Second, is there a setting somewhere to change the delay for the "screen on after a call" (I know there is a setting in settings-display for screen time-out).
I hate to make the comparison, but on my iPhone (No flaming please, I'm reformed) the screen turned off and on very quickly and I just wonder what I need to do to get that kind of response on the SG2, during the phone call.
BTW, I'm running UnNamed 2.2.1 (Gingerbread 2.3x) with Entropy's kernel.
Thanks for any help.
Clean your screen.
You using a case? Maybe it's partially blocking the proximity sensor.
mbamberg said:
I've searched with several different search strings and haven't found an answer to this question, so here goes;
When I place a call and bring the phone to my ear the screen turns off (dims?). At the end of the call after I bring the phone away from my ear, it takes several seconds for the screen to turn back on, sometimes it doesn't turn back on unless I press the power button.
First, is this the normal behavior for the phone app on the I777?
Second, is there a setting somewhere to change the delay for the "screen on after a call" (I know there is a setting in settings-display for screen time-out).
I hate to make the comparison, but on my iPhone (No flaming please, I'm reformed) the screen turned off and on very quickly and I just wonder what I need to do to get that kind of response on the SG2, during the phone call.
BTW, I'm running UnNamed 2.2.1 (Gingerbread 2.3x) with Entropy's kernel.
Thanks for any help.
Click to expand...
Click to collapse
Ironically I had the same experience in UnNamed to I assumed it was just the nature of GB. It may very well have been as I don't have that issue with ICS based ROMS. And I like the dialer better to boot.
audiophan said:
Ironically I had the same experience in UnNamed too I assumed it was just the nature of GB. It may very well have been as I don't have that issue with ICS based ROMS. And I like the dialer better to boot.
Click to expand...
Click to collapse
OK,
I'm in the throes of upgrading to an ICS ROM, so maybe I'll just go ahead and see if that fixes the problem.
Thanks for the answers
I think its a sensor issue having to due with how long it waits to scan again after light levels are changed. No idea what stock settings are but I can say I don't have a problem with it on AOKP.
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
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.
Hello I have a 9100 international version, and this is not your usual 1-2 seconds lag on wake. My phone (well, my friend's) takes around 10 seconds to wake. Not exactly wake but for the display to show, because when I press the home key or power key, the soft keys light up and the phone vibrates to the touch, the screen is also responsive to touch while the screen is off.
All this started after I flashed paranoid android into it, but after trying multiple roms, the issue is exactly the same. I also flashed a pit file to repartition the phone to have more storage for apps and it worked. I mean the phone works flawlessly except for this particular issue of the screen not turning on fast enough, even though the touchscreen seems to be responsive.
Ill flash stock back to it and give it a try. In the meanwhile, any one else have had this issue?
Try Neatrom 6.4 is a stock based with more feautures and battery friendly. Yeah i faced this issue one time, in neatrom 6.4 i never have this issue.