Backlight setting itself to "powersave" after disabling other power-saving features - 8125, K-JAM, P4300, MDA Vario ROM Development

Backlight setting itself to "powersave" after disabling other power-saving features
Hi,
I'm using Faria's WM6 ROM.
I tried to disable the backlight from turning off for both battery and external power. I also disabled "turning off when not it use" for both external and battery power.
The problem is the backlight keeps going to "powersave" (completely off). The only way I found to stop this is to just re-enable those powersaving features, which annoy me because they happen while I'm on a phone call. This didn't happen to me with WM5.
Thanks for any help.

Related

[Q] Wifi Sleep Policy of Off Screen on SUperAOSP ROM

I have trouble downloading large files using this ROM since when my screen turns off, WIFI is also disabled. How can I change it. I've been looking in the settings but to no avail.
Edit: Found it...you have to click menu when in the WIFI Settings, then choose advanced.
Edit2: Wifi is disabled when screen is turn off even if the Wifi sleep policy is changed to Never.
Any ideas?
then that is some kind of bug. because setting wifi sleep policy to never should behave as such.
related note, setting wifi sleep to never greatly increases batteyr life, as said thru the forums, because back on 3g the data kills your battery much faster. so allowing wifi to stay on makes a huge improvement on battery.
for example if you leave wifi on overnight, you might lose 5% total. but if it switches back to 3g overnight, you might lose 20%.
is this bug confirmed?
me too have same problem with SuperAosp (i will test with other rom....)

[Q] Trying to get utility to auto-disable Wifi without wakelock on CM7

Okay, I've been trying to diagnose a somewhat annoying issue. I've been using a fairly simple set of conditions in the Llama utility to automatically disable Wifi when the screen turns off in CM7 to prevent a wakelock condition and reduce battery drain.
So I activate wifi, I reset the log in CPU Spy, and I lock the phone disabling the screen. When I reactivate the phone and check CPU Spy, wifi was definately off but the phone was never in Deep Sleep, so something was holding the wakelock I guess. I repeat the experiment with no changes and Llama still running, but this time I manually disable wifi before locking the screen. This time the phone immediately goes into Deep Sleep according to CPU Spy-- it works perfectly.
So what is the difference between Llama autodisabling and manually disabling wifi that leaves a wakelock active? I've repeated this experiment like ten times last night, and it isn't making much sense to me.
Thanks,
Gnat
I would love an answer to this as well. I can add that with juice defender ultimate the same thing happens. It will disable the wifi but the wakelock stays active. I have tried several settings and reboots and tests and the only thing that would get my phone to deep sleep was disabling JD.
mikel81 said:
I would love an answer to this as well. I can add that with juice defender ultimate the same thing happens. It will disable the wifi but the wakelock stays active. I have tried several settings and reboots and tests and the only thing that would get my phone to deep sleep was disabling JD.
Click to expand...
Click to collapse
I can't tell whether this is the exact same, because you make it sound like JD has the wakelock. In my case, Llama is running in both tests, the only difference is whether Llama turns off Wifi or I manually toggle it-- manual toggling puts it into deep sleep even with Llama running.
On the general battery issues on Triumph, one of the more helpful discussions I've seen is this one here-- http://androidforums.com/triumph-all-things-root/456795-cm7-triumph-battery-life-improvement.html. In it a quote from Tickerguy blesses the JuiceDefender approach to throttling data use for battery savings, but I don't think he had done any analysis regarding wakelocks. BTW, I reverted to stock today, and I am finding the exact same problems as CM7-- wifi imposes a wakelock, and Llama can't shut down wifi automatically without the wakelock persisting. I have to manually toggle wifi off before screen off before the wakelock is gone.
Regards,
Gnat
gnatd said:
I can't tell whether this is the exact same, because you make it sound like JD has the wakelock. In my case, Llama is running in both tests, the only difference is whether Llama turns off Wifi or I manually toggle it-- manual toggling puts it into deep sleep even with Llama running.
Click to expand...
Click to collapse
Sorry; the wakelock is WLAN. It is almost always active if JD is toggling wifi. I hadn't tried disabling wifi manually but leaving JD active yet. I just tested that and got deep sleep immediately. So it must have something to do with how it disables wifi isn't releasing the wakelock.
You know, after switching back to stock from CM7 I'm really not sure I'm not happier. With CM7 I was getting worse battery performance, which led me to start obsessing about wakelocks and deep sleep. Now that I am back on stock, I do the same analysis and see that I have the same problems with wakelocks and deep sleep-- but the battery performance is better so it's not that big a deal. I'm sure that there are things I could do to make CM7 have better battery performance-- but I wasn't enjoying the process and wasn't finding answers, so why bother?
It's like power management programs. I ran Green Power for a long time, and had some glitchy problems with being unable to get wifi to turn on even though it wasn't supposed to be managed while the screen was on. Then I disabled it, and you know what... my battery life was good enough to get me through the day. Froyo is good enough to get me through the day.
The wakelock was put in there on purpose to prevent the phone from hanging when WiFi was on and the phone went to sleep. I use my power widget to turn off WiFi before I turned off the screen unless I'm actually using it.
You could try and build it to see if removing the wakelock is still necessary. If you need help on that side, just post and I'll help. It's not hard, really.

[Q] Power saving through Tasker

I consider our Tablet to be different than a phone, in the sense that when we turn off the screen, we dont need all the background functions still running. Currently I see TF101 deep sleep battery drain caused by many different functions running in the backend...for example the location services api.
I was thinking of creating a Tasker script that turns off as many different things as possible a few minutes after the screen is turned off.....And turns them back on when the device is unlocked.
I didn't want to spend time reinventing the wheel if this has already been done....
Anyone already try this? Results?
thanks.
I decided I was over-thinking it...and went with tasker scripts to
a) Auto Turn on Airplane mode when the screen goes off
b) Auto Turn off Airplane mode when the device is unlocked.
(This involved using the "Secure Settings" plugin app to allow Airplane mode via tasker on 4.2 JB)
So far the results have been good. i don't see those map api's being called during deep sleep.

Wifi shuts down during sleep (it is set not to)

The wifi icon disappears after few minutes of screen being off after locking. I did set wifi to be on during sleep. Does anyone else have that issue ? I have a SIP client installed on my phone and need wifi all the time so that is a pain.
Mine does the same thing. I think it might be because I have the *intelligent power saving* checked in "power management" in settings. I think the phone disables data every so often to preserve the battery. Haven't tested my theory by un-checking, but I remember this happening on my Blu studio energy.
I have intelligent power disabled.
I think I am getting this on my phone. Sometimes on wakeup it forgets it is connected to Wifi and apps and chrome won't update. I usually just turn airplane mode on/off to fix it. Still, it is annoying. Doesn't seem to happen with LTE, at least.

Ambient Display won't turn off

It just continually pulses so I'm afraid it's draining the battery and causing screen burnin. I even disabled the "moves" in settings. Any ideas?
I have the same problem.

Categories

Resources