Had read a few suggestions for fixing this "sleep of death" issue on the G tabs... doesn't seem anyone has posted this
I've tried multiple ROMS, multiple apps like Regpon Wifi stay awake etc. and multiple GTabs...
The only thing that repeatedly seems to completely fix the not waking after sleep issue is an app called "Captivate Keep Alive"
Instead of tying wake to WiFi or CPU, it lets you tie it to battery %.
Try it, let me know if it works on your ROM.
Tested working 100% for Vegan 5.1.1 and CM 7 Harmony.
Tablet used to require boot after leaving it, now it will always wake up, after 1 hour, 20 hours, etc. Plugged in or not.
Completly agree. I tried all ROMs, and Kernals(up to .40). Nothing helps, but Captivate Keep Alive.
I had a similar, but not same issue. My WiFi would turn off completely when teh screen went blank. I could not ping it. Turns out that I had to update my kernel to pershoot's 2.something.39. That fixed it. I do find it every now and then totally unresponsive but pressing the power button patiently 3-4 times wakes it up. I'm running CM7.
App works
So glad I found this thread. I was having this same issue using TNT Lite and installed Captivate Keep Alive. I have been able to turn on from sleep without the reboot.
I have the screen set to always on (no time out) when I have it in the car, it stays on fine while listening to music or if it just sitting there doing nothing, but no matter if I get a call or I make a call -- the screen will always turn off after a couple seconds even though the screen is set to always stay on, also as soon as the call ends -- the phone automatically locks and I have to log in / unlock it every time. I know on the old Froyo ROMs it would stay on if I had it set to always on -- didn't matter a call or not, it stayed on like it is supposed to do and it did not automatically lock either. I am on the Weapon 3.0ROM and I am using the same widgetsoid app as the the switching mechanism for the "always on" screen setting in a widget on one of the home screens. I have checked the widgetsoid settings and there is no definition between call settings and normal data for the screen time out. Under settings in the main menu, there is no toggle to enable/disable the proximity sensor either, but since the phone face has nothing close to it when it is mounted in the car (like it would be if you had it up to your ear), I don't think that this is the proper setting to manipulate. I really believe that this is a timing setting, and I am wondering if it is separate setting that can be changed or linked to the normal screen time out settings.
Is there a way to stop the screen from timing out on the Weapon3.0 Rom during phone calls and then automatically locking the phone when the call ends? its getting a bit annoying and any help would be appreciated.
Am I really the only one experienceing this?
I have tried fully wiping the G2x and started from scratch reloading the ROM, apps, settings, etc. and with the Weapon 3.0ROM when the phone is plugged in charging it still automatically shuts the screen off a few seconds into a call, and then locks the phone even though I have the LCD screen setting set to always be on.
For the most part I really like the Weapon ROM, but this auto screen off and locking when I have the G2x plugged in, in the car is annoying as ****, any help to remedy this problem would be appreciated.
crockashat said:
I have tried fully wiping the G2x and started from scratch reloading the ROM, apps, settings, etc. and with the Weapon 3.0ROM when the phone is plugged in charging it still automatically shuts the screen off a few seconds into a call, and then locks the phone even though I have the LCD screen setting set to always be on.
For the most part I really like the Weapon ROM, but this auto screen off and locking when I have the G2x plugged in, in the car is annoying as ****, any help to remedy this problem would be appreciated.
Click to expand...
Click to collapse
I think that is an unwanted "feature" of the 2.3.3 Gingerbread rom. I am not sure of anyway around it without changing to a rom that is not 2.3.3 based.
I've been digging into the "touchkey backlight issue" and would appreciate some help understanding how it worked (or didn't) on GB-based ROMs. If you are running GB (rather than "I remember..."), understanding how the proprietary Samsung code handled the backlight, both in auto- and manual-brightness mode, under a variety of screen timeouts, USB plugged, AC plugged, etc., would be great. Information like this can also help me guess where Samsung has their proprietary code, rather than wading through 150 MB of ROM.
Reports like,
The backlights go out after a couple seconds
Click to expand...
Click to collapse
aren't terribly helpful.
The backlights turn on when I tap the screen anywhere, then turn off after a second or two (it seems to vary from time to time), when I'm running on batttery, with auto-brightness on, and in normal indoor home lighting. They don't turn on with the same settings if I am outside.
Click to expand...
Click to collapse
or the like is much more helpful.
(I made that stuff up. I don't remember how they worked under GB.)
Oh, let me know which ROM you are running as well.
No promises, but knowing where we came from can help determine where we might go.
Thanks!
P.S. This is a common problem with Samsung phones -- You'd be amazed at the number of inquiries about the touchkey backlight.
I can check these later again a stock S4G I have still on GB, but on my flashed one with FB's AOKP using your brightness for the screen fixes, this is what I just tested.
-Turn Autobrightness off, screen sleep to 5 mins, brightness about 30%, backlights stay on for the whole 5 mins.
-Turn Autobrightness off, screen sleep to 5 mins, brightness about 100%, backlights stay on for the whole 5 mins.
Turn Autobrightness On, screen sleep to 5 mins, filtered/raw 34/34, backlights stay on for the whole 5 mins.
Turn Autobrightness On, screen sleep to 5 mins, filtered/raw 2000/2000, backlights go out as soon as the raw value hits past 150, your default to turn them off.
When I remove it from a bright light and the raw goes back down to below 50 though, the autobrightness does not dim the screen, I have to put it to sleep and wake it up to get it to actually drop the brightness..
Moving the phone between bright light and dim light, the buttons do go on and off corresponding to the 150, but the screen doesn't dim or go brighter.
If the buttons are off from being in bright light, and I press one, they go on and stay on and moving out and back into bright light, they seem to stay on most of the time.
So it seems your code for the autobrightness can turn the buttons on and off, by the 0 value for the correct RAW value. It's spotty though and the autobrightness doesn't adjust itself to the correct level until I sleep/wakeup again. I can have autobrightness on and move my phone from dark to light and the buttons go on and off by the brightness of the light but the screen doesn't.
I will check this same test against a stock GB and see what happens.
This is for gingerbread:
Sometimes the key lights don't turn on at all while using the keyboard, and even when you are pressing keys in the keyboard. It might not even be caused by the keyboard being out, maybe it's the way I hold my phone while I'm typing that causes the auto brightness to go down.
This doesn't occur all the time though. Also, sometimes it doesn't turn on at all even when touching the screen (maybe for a minute) then they turn back on.
It seems that the key lights have some situations where they decide to ignore touches and stay off, I'm still trying to figure out when this is. Again, it mostly happens when the keyboard is out. Maybe it has something to do with auto brightness. When toggling auto brightness on and off, the key lights immediately turn off and stay off for about 30 seconds. This makes me think that the soft key lights even on stock are buggy
Thanks getochkn; great report for ICS!
That pretty much agrees with what I am seeing on ICS and what I would expect from the code.
The buttons "don't play nice" with the Android world as it seems they turn themselves on when you touch them (probably hardware control), and the present TeamAcid ICS driver turns them on when it (re-)initializes. The Android world won't change the brightness of any of the "lights" if it thinks that the level is already set. For example, if it thinks the buttons are off, it won't try to turn them off again. I believe this is why with auto-brightness on the buttons sometimes won't turn off. I'm still wading through PowerManager service to understand how the code is trying to handle them when in "manual" brightness mode.
Definitely looking forward to your results for GB, though pisherthefisher's report that they seem "buggy" on "stock" for him suggests that Samsung might not have gotten it right even there.
Seems to be no way to fully disable them eh? Then we could just use the JB style nav bar like already in FB's AOKP which lets us set color, brightness, custom icon, etc but with the other buttons still working physically, lights on or not, it seems not worth it as you will still hit the sammy buttons, especially if the light is off but the buttons still physically work.
I can "hack" them off, but I'm trying to solve the problem more generally and in a way that keeps the TeamAcid framework able to easily track the CyanogenMod upstream. I might build a "Hefe Kernel Of Darkness" if I can't find something this week.
Posted from my SGS4G, thanks to Team Acid development
Ah. Might be an option, go all softkeys via the ROM instead.
I know OT, but any idea why the autobrightness doesn't seem to fully kick in sometimes either? I can be in the custom screen to view the raw values and see the numbers drop but not the screen brightness until i sleep/wakeup. The backlights will go on/off according to the raw value but not the screen brightness. lol.
Going to go see how my stock one works and I'll report back.
On the auto-brightness not seeming to work, you might want to check the auto-brightness thread in the dev section. I am guessing it might be related to the "Allow light decrease" and "Decrease hysteresis" settings.
jeffsf said:
On the auto-brightness not seeming to work, you might want to check the auto-brightness thread in the dev section. I am guessing it might be related to the "Allow light decrease" and "Decrease hysteresis" settings.
Click to expand...
Click to collapse
Thanks. I forgot the settings after reinstall.
On GB, the lights seem to go out at some value (no custom, can't tell) but do come back on when you press them and then seem to stay on randomly. lol.
FB's AOKP comes with BLN control which does seem to use the lights as an indicator light for lockscreen notifications, so they seem to be able to be controlled from that SW. Not sure if that helps or not?
Hefe kernel of darkness sounds awesome, it would be cool to use the sgs4g like a galaxy nexus
Setting the backlights to 0 on all light settings, the backlights go out, but as soon as you go to sleep, and wake up, the lights come back on and don't go out even though the custom panel shows the state of them at 0. Turning auto-brightness off/on then turns the lights off, so the state is not being restored at wake. Of course touching one of them turns them on and they stay on again unless i toggle off/on again.
Yes, right now driver resume turns on the backlights, but Android thinks they are already off, so it doesn't turn them off based on the auto-brightness settings. Touching the keys is similar, but it seems to be hardware that is turning them on.
Posted from my SGS4G, thanks to Team Acid development
Well I'll test a darkness kernel if you get one going. lol. Use the softkey feature in AOKP. I've already been playing with and have it setup, I just don't want to hit the sammy buttons which I brush sometimes by accident, nor have the lights come back on after wake up, so if can disable them fully in the kernel, that would be cool.
Hefe Kernel Of Darkness in Post #2 of the Hefe Kernel thread
jeffsf said:
Hefe Kernel Of Darkness in Post #2 of the Hefe Kernel thread
Click to expand...
Click to collapse
no wifi. lol. Doesn't even turn on.
Yeah, something is flaky. I'll look at it again tonight.
Posted from my SGS4G, thanks to Team Acid development
jeffsf said:
Yeah, something is flaky. I'll look at it again tonight.
Posted from my SGS4G, thanks to Team Acid development
Click to expand...
Click to collapse
Works good other than that.
Can the lights be disabled with the keys functional?
Sent from my SGH-T959V using xda app-developers app
m4127440 said:
Can the lights be disabled with the keys functional?
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
The best we can do right is only have them turned on while pressed with the hefe kernel of darkness. Check out the hefe kernel thread in the development section, second post
Sent from my SGH-T959V using xda app-developers app
We?
Hey there,
I just got my N5 a few days ago and I have noticed that when the screen is off, it actually is not. It's not off like in I turned the phone off, but off as in it's black but there seems to be some light still coming through. Pretty much like having a all black picture being displayed or when the Google bootlogo comes on, that kinda black. I am running Purity and Franco Kernel but I don't think that would have any cause into it.
I have tried rebooting multiple times, turned off hot word detection but still seems to be present.
I'm sure this isn't normal but if someone could suggest any solution, that would be great.
EDIT: OK, actually I figured it out just mere moments after posting this. It was an option in Lightflow to control the backlight while screen off. It was checked on.... derp. Also, there was an option in trickster for led control and I toggled that and saved and it turned the screen completely off now. Leaving this up for a helpful hint if anyone else experiences this type of issue