So I have a Tasker profile that fiddles with governor settings to make it fairly responsive when the screen turns on. It then reverts back to more conservative type settings when the screen goes off. I'm not changing governors, just using Tasker to edit the governors settings.
Am I writing to FLASH everytime the screen goes on and off?
I figure turning the screen on 13 times per day will result in almost 10000 writes per year. I assume there's some sort wear leveling going on, but I'm wondering if I created a potential wear out issue here.
Related
Since we need to have the screen turned on to keep wifi/gps etc. running, and there are a few apps that would ideally run in the background with the screen off; to save battery power (and burn in?) it would be nice to have the AMOLED screen display just a black image.
Is there any app out there that just displays a black screen and maybe ignores all but a specific input?
At the moment I just zoom into a black image in the browser, but I can't put the phone in my pocket like that.
(I tried searching for this, but it was beyond my google-fu.)
You dont have to keep the screen on to run either my gps is always on and it neva disconnects also ive spent many nights going to sleep leaving my wifi connected and its neva disconnected either
Yup. If you haven't set WiFi to switch off after 15mins, it should carry on running.
By doing what you proposed, you'll decrease battery life drastically as you'd effectively be disabling the chips sleep mode by keeping it running 100%. With that, only the screen switches off and everything else including Android keeps running. Any application holding a partial awake lock can achieve this.
Lock delay; an app to control the default screen-lock options allows this.
For instance, if you set the initial screen timeout to 2 minutes but standby/lock to 10 minutes in the settings, the screen will switch off after 2mins idling, but the rest of the phone will still be running incl. WiFi/GPS. You can enable a lock/pattern or no lock at all where you press any key including menu/trackpad and it'll come back on in the same place you left it, without any lock. If the phone idles for 10mins, it'll activate the screen lock and place the phone in the standard sleep mode. The max delay you can set the latter to is 24 hours.
I wouldn't advise avoiding the sleep mode unless required in specific circumstances. Battery loss will be drastic; I found out unintentionally when activating this option at the beginning.
-----------------------------------
- Sent via my HTC Desire -
Thanks th3, that should do what I want. I don't intend to leave it unattended, it's just for when don't need the screen on while an app is doing something.
So basically I just rooted my phone and flashed to cyanogen mod 6.1 and I'm loving it. Thanks xda for the rooting and flashing process. I decided to go into overclocking my mytouch slide and everything seems to work perfect except for the fact when I turn off my screen and turn it back on the screen is at the dimmest setting it can get. I reset the brightness back to how I want it and then turn off the screen again and turn it on, and it reverts back to the dimmest setting. I booted up without having setcpu running and the screen settings stay the same after I turn the screen on and off. has anyone found or seen this before?? And if so, is there a solution to this problem??
Thanks
I've never heard of setCPU causing that problem. You may want to trouble shoot a bit more before pinning it on that. We need to knock some things off the list of possible culprits too.
What is the brightness set to, automatic?
Custom oc kernel (dumfuq's) or what's integrated into CM?
What are your clock settings in setCPU?
What governor are you using in setCPU?
Do you have profiles set, if so, what are they?
Have you messed with the light sensor or done any custom brightness tweaks (CM settings)?
You need to answer some of those first so we can narrow it down, you may have something set up wrong. There is also the issue of the phone not coming to full brightness when you try to catch it on the screen time out (screen is off - but not locked). That's fixed by locking it and unlocking.
Is there any kind of mod I can do that dims my screen after say 15s of inactivity?
I don't want the screen to go off (i have it set at 5 min to turn off), but it would be good on the battery if it goes dim (the state that the screen goes 3s before going off).
Basically when I text, I feel like i'm constantly turning the screen on and off and wearing out my physical keys.
You might want to check out RootDim, but it does not have an "after 15s" rule like you were talking about, it's just always what you set it to. The horrible thing about this app is there is no "set on boot" feature and the dev refused to add one, making the app a pain in the ass to use unless you want to manually set the dim level after every reboot, maybe others don't reboot as much as me I dunno.
The battery saver mode page allows for tweaking four settings:
Max brightness
Always-on-display
Disable vibration
Restrict background data
Now, if you disable(!) all of those you still receive minor savings, at least from what the prediction overview (listing all available battery modes) shows. First question: What remains "tweaked" internally to allow for that?
Furthermore, from enabling the items one by one, adjusting max brightness offers a large impact on the predicted runtime. That's no surprise. However, I would have thought that disabling the always-on-display leads to more savings but, looking at the predicted time, it actually doesn't. The impact is close to zero.
Vibration has a minor impact, more than AOD, while a HUGE gain of additional standby hours can be achieved by selecting the "Restrict background data" option. I wonder how that turns out in the everyday use but I think that, if one app would suffer, I would just exclude it and leave the rest in the "saving" position.
Concerning the (assumed) internal changes, I've logged the CPU frequency for a while with the extended battery mode on and off and can't see that throttling is active like I saw with other phones and their battery saver modes, so that's a nice trait. The chipset still clocks to max when needed, same as with the extended mode off.
How are your experiences with that mode? Does it offer more runtime (namely: are the predictions somehow in line with reality?) or is it leading to added lag or other problems? Currently, it seems like taking a lock at that background data option is worth a shot.
BasicallyCP said:
The battery saver mode page allows for tweaking four settings:
Max brightness
Always-on-display
Disable vibration
Restrict background data
Now, if you disable(!) all of those you still receive minor savings, at least from what the prediction overview (listing all available battery modes) shows. First question: What remains "tweaked" internally to allow for that?
Furthermore, from enabling the items one by one, adjusting max brightness offers a large impact on the predicted runtime. That's no surprise. However, I would have thought that disabling the always-on-display leads to more savings but, looking at the predicted time, it actually doesn't. The impact is close to zero.
Vibration has a minor impact, more than AOD, while a HUGE gain of additional standby hours can be achieved by selecting the "Restrict background data" option. I wonder how that turns out in the everyday use but I think that, if one app would suffer, I would just exclude it and leave the rest in the "saving" position.
Concerning the (assumed) internal changes, I've logged the CPU frequency for a while with the extended battery mode on and off and can't see that throttling is active like I saw with other phones and their battery saver modes, so that's a nice trait. The chipset still clocks to max when needed, same as with the extended mode off.
How are your experiences with that mode? Does it offer more runtime (namely: are the predictions somehow in line with reality?) or is it leading to added lag or other problems? Currently, it seems like taking a lock at that background data option is worth a shot.
Click to expand...
Click to collapse
Only thing I've noticed is when I have my phone set to Extended and I've set Max Brightness to 80%. However, I've seen my Brightness go over 80% on Auto especially when I was outdoors (saw it hit 100% and Boosted). Under Manual Brightness, I can have it go to 100% too. So that 80% is misleading?
Good find. I was wondering too since the prediction page instantly applies a gain in standby hours (and a significant one at that) by just enabling the "max brightness" feature. Since it can not know when or for how long the display will be on and what range the "auto" feature will use in a given situation, it seems like a very optimistic value, especially if you just use a limit of 95% for example.
But regarding your question, it's indeed strange to see "auto" exceeding the max brightness limit. I mean, the limit is there for the auto mode only. Might be a bug, unless we struggle to see the logic behind acting like that.
Personally, I would leave max brightness alone since it's more useful to have the display ramp up to max in order to actually see something when needed. If "auto" generally sets up the display as being too bright, one can still adjust the slider (even in auto mode) to tune the point of optimal brightness. I think it acts as an offset to the actual (internal) value the automatic comes up with. At least, that's how I perceived the feature on this and other phones so far.
Before Do Not Disturb even existed I used quite a few apps (llama, Phone Profiles Plus, Sound Profile) to achieve sound management over night. Unfortunately at some points in time some of these failed to work due to more aggressive battery management of my newer phones or after software updates that broke things.
However now I feel that DND provides more options and is a more elegant solution...if it would do what I want.
I would like to turn it *manually* on, go to sleep, and have it turned off at 8:00 AM. Anyone found a way to do that?
You can set a schedule to turn on and off automatically. You can also turn it on manually then set it to turn off automatically. You select how many hours you want it on.