Related
Any recommended apps that increase battery life?
So far I only have setCPU.
Locale Beta saves much 12hrs of the day.
pickles said:
Locale Beta saves much 12hrs of the day.
Click to expand...
Click to collapse
What??
what does setcpu do? lower cpu clock?
Screebl, Advanced Task Manager, and SecCPU are an awesome battery-saving combination.
zok-star said:
what does setcpu do? lower cpu clock?
Click to expand...
Click to collapse
Yes, but the best part is, you can set it to only lower the cpu clock when the phone is asleep (i.e., when the screen is off). Theoretically you could also overclock it when the screen is on, but not yet on the N1. On the G1/Dream, it was awesome--I overclocked when the screen was on, and underclocked when it was off. It saved battery AND made the phone faster at the same time. Here, it does nothing but save battery--a LOT of battery.
I don't have any problems with the battery.... it lasts me an entire day with pretty liberal use.
I just started using juice defender.. but it seems to slow the phone down at times... does anyone know of a similar app that is maybe more efficient
http://www.appbrain.com/app/juicedefender-battery-saver/com.latedroid.juicedefender
Here's a good software:
It's called Turn Off your Phone. Saves as much as up to 1 month worth of battery!!
chowlala said:
Here's a good software:
It's called Turn Off your Phone. Saves as much as up to 1 month worth of battery!!
Click to expand...
Click to collapse
is it a free app?! OMG!
<3
Power manager and set cpu work for me. Power manager hasn't been updated in a while, but its still works and its pretty easy to use. Alternately, you can use Tasker, it has a high learning curve but once you get it, you'll get an entirely different level of performance from your phone.
carnegie0107 said:
Yes, but the best part is, you can set it to only lower the cpu clock when the phone is asleep (i.e., when the screen is off). Theoretically you could also overclock it when the screen is on, but not yet on the N1. On the G1/Dream, it was awesome--I overclocked when the screen was on, and underclocked when it was off. It saved battery AND made the phone faster at the same time. Here, it does nothing but save battery--a LOT of battery.
Click to expand...
Click to collapse
Actually you can overclock n1 when screen is on, it is set at 998 stock, but it can go higher 1113 is stable. But it depends on your kernel. I use 245/652 when screen is off, 384/1036 when on.
N1
chowlala said:
Here's a good software:
It's called Turn Off your Phone. Saves as much as up to 1 month worth of battery!!
Click to expand...
Click to collapse
ROFL hilarious,
Due to juice defender slowing down my phone, i am going to try green power for a week then juice defender beta for a week and see how they work
juice defender beta seems to work the best
chowlala said:
Here's a good software:
It's called Turn Off your Phone. Saves as much as up to 1 month worth of battery!!
Click to expand...
Click to collapse
Nice, it's more like a function to do than a app to utilize, fail.
Hey everyone,
Just wondering if deep sleep is working on any of the ICS roms/kernel combo so I can use it.
Also I have searched to no avail, but can someone possibly explain how deep sleep works? Like I know it clocks the processor to very low levels, but is the phone able to 'wake up' when it receives a call/text/email, or do you only use this feature in situations when you do not need your phone (like in class or at work etc) as to keep the battery from draining?
thanks for your time
samsizzle said:
Hey everyone,
Just wondering if deep sleep is working on any of the ICS roms/kernel combo so I can use it.
Also I have searched to no avail, but can someone possibly explain how deep sleep works? Like I know it clocks the processor to very low levels, but is the phone able to 'wake up' when it receives a call/text/email, or do you only use this feature in situations when you do not need your phone (like in class or at work etc)
thanks for your time
Click to expand...
Click to collapse
Harsh kernel goes into deep sleep.. its an idle state it wakes up when you get calls and such its automatic after a certain amount of time with the screen off
DJLamontagneIII said:
Harsh kernel goes into deep sleep.. its an idle state it wakes up when you get calls and such its automatic after a certain amount of time with the screen off
Click to expand...
Click to collapse
so is using setcpu and creating a profile that lowers the clock speed for 'screen off' counterintuitive?
samsizzle said:
so is using setcpu and creating a profile that lowers the clock speed for 'screen off' counterintuitive?
Click to expand...
Click to collapse
no it will lower the speed before it goes into deep sleep.. theres a certain amount of time with the screen off that its not in sleep and thats when the profile will save battery
samsizzle said:
Hey everyone,
Just wondering if deep sleep is working on any of the ICS roms/kernel combo so I can use it.
Also I have searched to no avail, but can someone possibly explain how deep sleep works? Like I know it clocks the processor to very low levels, but is the phone able to 'wake up' when it receives a call/text/email, or do you only use this feature in situations when you do not need your phone (like in class or at work etc) as to keep the battery from draining?
thanks for your time
Click to expand...
Click to collapse
Tegra does not have deep sleep. It instead has low power states called lp1 and lp2. Basically your phone goes into lp1 hundreds or thousands of times a second. actually the "cpu percentage" you see in almost all apps is the amount of time spent in lp1 vs awake.
Lp2 can be considered deep sleep. All kernels support it in this phone. What it does is "park" the cpu. most of the time it only parks one core on this phone, but in times of very low activity it parks both. In lp2 the processor is using so little power it's almost not even on.
While a core (or both) is (are) in lp2. There is something built into it so that if for example you get a call, the radio will wake the cpu up and it well resume working.
about screen off profiles, in my opinion they are useless.
Processors use a technique called "Race to Idle" basically it takes way less power for the cpu to go up to 1ghz, do its work very quick, then go back to sleep, then it does for it to do the work slowly at 216mhz. Because of this you should never limit your cpu to a lower speed. Nvidia spent a lot of time and money researching how to do these things power efficiently, and limiting the cpu lower only makes the cpu fight itself.
Sent from my LG-P999 using Tapatalk 2
^ give this man his thanks!
This is why I love this community, so informative and helpful.
Klathmon said:
Tegra does not have deep sleep. It instead has low power states called lp1 and lp2. Basically your phone goes into lp1 hundreds or thousands of times a second. actually the "cpu percentage" you see in almost all apps is the amount of time spent in lp1 vs awake.
Lp2 can be considered deep sleep. All kernels support it in this phone. What it does is "park" the cpu. most of the time it only parks one core on this phone, but in times of very low activity it parks both. In lp2 the processor is using so little power it's almost not even on.
While a core (or both) is (are) in lp2. There is something built into it so that if for example you get a call, the radio will wake the cpu up and it well resume working.
about screen off profiles, in my opinion they are useless.
Processors use a technique called "Race to Idle" basically it takes way less power for the cpu to go up to 1ghz, do its work very quick, then go back to sleep, then it does for it to do the work slowly at 216mhz. Because of this you should never limit your cpu to a lower speed. Nvidia spent a lot of time and money researching how to do these things power efficiently, and limiting the cpu lower only makes the cpu fight itself.
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
will overclocking effect the ip1 and lp2 states?
jwalker3181 said:
will overclocking effect the ip1 and lp2 states?
Click to expand...
Click to collapse
the short answer is no, not really in any way that will matter...
the long answer is yes, let me explain:
it may actually increase the amount of time that the CPU spends in these states. on the other hand, if the kernel developer messes with these threshold values that determine some of these states, it may actually increase the amount of time one core spends in lp2, but reduce the amount of time the other core spends fully awake.
either way, its a balancing act that the kernel devs do, and they seem to have a pretty good hold on it.
Klathmon said:
the short answer is no, not really in any way that will matter...
the long answer is yes, let me explain:
it may actually increase the amount of time that the CPU spends in these states. on the other hand, if the kernel developer messes with these threshold values that determine some of these states, it may actually increase the amount of time one core spends in lp2, but reduce the amount of time the other core spends fully awake.
either way, its a balancing act that the kernel devs do, and they seem to have a pretty good hold on it.
Click to expand...
Click to collapse
I feel like you've got all the answers, man. I learn a bunch reading your posts.
Caliyork said:
I feel like you've got all the answers, man. I learn a bunch reading your posts.
Click to expand...
Click to collapse
Android is my hobby, i spend an insane amount of time pouring over data sheets, source code, and manuals. Honestly I'm still fairly new to Android, but I've been programming for years so that helps
And for some reason even i don't know, i kinda like answering questions on this forum
Sent from my LG-P999 using Tapatalk 2
Caliyork said:
I feel like you've got all the answers, man. I learn a bunch reading your posts.
Click to expand...
Click to collapse
+1 im glad klathmon is in our forums
Sent from my LG-P999 using xda premium
I have this issue—the screen stays black when I wake up the phone—, so I have to do “adb reboot” manually. I global undervolted 50mV and my phone is on franco. Do you think undervolting may have caused this problem? I do not have enough data in order to judge if undervolting is the main cause. Thanks in advance.
ericjslee said:
I have this issue—the screen stays black when I wake up the phone—, so I have to do “adb reboot” manually. I global undervolted 50mV and my phone is on franco. Do you think undervolting may have caused this problem? I do not have enough data in order to judge if undervolting is the main cause. Thanks in advance.
Click to expand...
Click to collapse
no, its not undervolting. it sounds like sod, sleep of death. it could be kernel or rom related, among other things. anyways, next time so you dont have to connect to adb, press your power button in for 15-30 seconds, itll reboot.
Thank you!
Sent from my Nexus 5 using Tapatalk
Try global 25 to prove the point?
Sent from my Nexus 5 using Tapatalk
Undervolting can certainly cause a phone to be really slow to wake up. Turn off undervolting and see if it continues
Sent from my Nexus 5 using Tapatalk
rootSU said:
Undervolting can certainly cause a phone to be really slow to wake up. Turn off undervolting and see if it continues
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Undervolting is the most likely culprit for your SoDs. No reason to do it anyhow. Although, franco kernel has had that issue with some releases, but are usually fixed very quickly.
Undervolting will add minutes only to SoT and next to nothing for overall time. It's not worth the trouble it can cause.
Just my opinion....and experience.
guys, while undervolting can affect turning on the screen with a slight delay, most likely its not in this case. and undervolting does not cause sod.
simms22 said:
guys, while undervolting can affect turning on the screen with a slight delay, most likely its not in this case. and undervolting does not cause sod.
Click to expand...
Click to collapse
Given that we're using sod as a generic term, I respectfully disagree. It definitely can cause trouble coming from the sleep frequency to the minimum frequency if the voltage is too low, it cannot make the transition. He definitely should roll it back and rule it out before doing anything else. This goes for any instability issue.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Given that we're using sod as a generic term, I respectfully disagree. It definitely can cause trouble coming from the sleep frequency to the minimum frequency if the voltage is too low, it cannot make the transition. He definitely should roll it back and rule it out before doing anything else. This goes for any instability issue.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
of course it can cause trouble coming from sleep frequencies, but it wont cause sod. yes, undervolting can and will cause stability issues, but it wont cause the screen not to come on. it would cause a delay in the screen coming on, but the screen would turn on still.
if it cannot get to 300MHz from sleep, the screen won't come on.
Sent from my Nexus 5 using Tapatalk
kj2112 said:
Undervolting will add minutes only to SoT and next to nothing for overall time. It's not worth the trouble it can cause.
Just my opinion....and experience.
Click to expand...
Click to collapse
It can help with heat tho if you're having issues in that department
Sent from my Nexus 5 using Tapatalk
Ben36 said:
It can help with heat tho if you're having issues in that department
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yup. Maybe good for gamers....or frequent navigators.
kj2112 said:
Yup. Maybe good for gamers....or frequent navigators.
Click to expand...
Click to collapse
I'm neither and always UV by a bit. I also revert to troubleshoot if I run into any problems. In this case I'm betting a revert to stock voltages cures the OPs issues.
theesotericone said:
I'm neither and always UV by a bit. I also revert to troubleshoot if I run into any problems. In this case I'm betting a revert to stock voltages cures the OPs issues.
Click to expand...
Click to collapse
I'm all for anyone doing anything to their device.... That's what android is all about.
But undervolting and under clocking is just something I personally never got. I suppose aside from trying to curb heat issues. But not to prolong battery life. It just makes such a minor difference. I've never seen proof showing otherwise.
But, to each their own.
kj2112 said:
I'm all for anyone doing anything to their device.... That's what android is all about.
But undervolting and under clocking is just something I personally never got. I suppose aside from trying to curb heat issues. But not to prolong battery life. It just makes such a minor difference. I've never seen proof showing otherwise.
But, to each their own.
Click to expand...
Click to collapse
True that.
I look it it this way. Less heat equals less stress. Less stress equals longer life. Use any analogy you want but the theory is there. If I ever run into an issue with my device the very first thing I do is revert my UV settings. If it persists, at least I've ruled out UV.
I believe the idea of UVing devices comes from an era not that long ago. IE, inefficient processors. Modern(the last two years) processors don't seem to have that much inefficiency. Could be snake oil on my side. It's habit though.
theesotericone said:
True that.
I look it it this way. Less heat equals less stress. Less stress equals longer life. Use any analogy you want but the theory is there. If I ever run into an issue with my device the very first thing I do is revert my UV settings. If it persists, at least I've ruled out UV.
I believe the idea of UVing devices comes from an era not that long ago. IE, inefficient processors. Modern(the last two years) processors don't seem to have that much inefficiency. Could be snake oil on my side. It's habit though.
Click to expand...
Click to collapse
I hear ya! Just see sooooooo many thinking they'll see big battery life gains.... And it seems they usually do this for battery more so than heat.
But yeah, I get the heat and stress part of it. Again, especially for games and GPS and what not.
Many of us have long weekends away in the Summer with no source of power. Can anyone point me to some tips for getting the most out of a single charge. I'm going to keep as many things turned off (wifi, BT, GPS), screen as dim as possible, switch to 2G and no data unless I need them, is there anything else. I have a boeffla kernel so I guess maybe some underclocking and so on, but I don't feel knowledgeable about that!
patp said:
Many of us have long weekends away in the Summer with no source of power. Can anyone point me to some tips for getting the most out of a single charge. I'm going to keep as many things turned off (wifi, BT, GPS), screen as dim as possible, switch to 2G and no data unless I need them, is there anything else. I have a boeffla kernel so I guess maybe some underclocking and so on, but I don't feel knowledgeable about that!
Click to expand...
Click to collapse
Diable every radio is not needed + underclocking will help. Reduce GPU to 200 Mhz, CPU to about 1.4 GHz and disable autosync of data, swtitch to 2G.
Also why don't you bring a powerbank with you in case of emergency
patp said:
Many of us have long weekends away in the Summer with no source of power. Can anyone point me to some tips for getting the most out of a single charge. I'm going to keep as many things turned off (wifi, BT, GPS), screen as dim as possible, switch to 2G and no data unless I need them, is there anything else. I have a boeffla kernel so I guess maybe some underclocking and so on, but I don't feel knowledgeable about that!
Click to expand...
Click to collapse
How about turning the damn thing off? You're at a festival, so enjoy the music and the atmosphere, turn the phone back on once in the morning and once in the evening just in case someone needs to get hold of you. Otherwise it doesn't really matter how much you try to minimise battery use, you're not going to get through a weekend.
patp said:
Many of us have long weekends away in the Summer with no source of power. Can anyone point me to some tips for getting the most out of a single charge. I'm going to keep as many things turned off (wifi, BT, GPS), screen as dim as possible, switch to 2G and no data unless I need them, is there anything else. I have a boeffla kernel so I guess maybe some underclocking and so on, but I don't feel knowledgeable about that!
Click to expand...
Click to collapse
Young kids of today have no idea.
Seriously if you are at a festival and you are worried about your phone lasting you are doing it all wrong. One thing experience has taught me is that you organise your....ahem, supplies beforehand.
A much greater risk is your phone getting lost smashed or stolen. I am sure the land mass of Glastonbury is by now made of 50% trampled phones.
So turn your phone of, put it away, purchase a battery pack relax and have a good time.
I'm 48 you know!
It went well, phone lasted four days with minimal use for texting, photos and the odd call. We had four smartphones with the odd top up from a 10000MAh power bank and all finished with charge. The best performer was a little Huawai, then a Moto G, then my OPO, then a Samsung Atrix.
I totally agree that it's best to minimize phone use at a festival, but pre-mobile I remember many a Glaso constantly failing to meet up with mates. It's a lot easier these days.
patp said:
Many of us have long weekends away in the Summer with no source of power. Can anyone point me to some tips for getting the most out of a single charge. I'm going to keep as many things turned off (wifi, BT, GPS), screen as dim as possible, switch to 2G and no data unless I need them, is there anything else. I have a boeffla kernel so I guess maybe some underclocking and so on, but I don't feel knowledgeable about that!
Click to expand...
Click to collapse
You can disable hotplugging and only have one core running which will help save battery. The best thing to do when going for long days is to keep your brightness low. Good luck!
patp said:
Many of us have long weekends away in the Summer with no source of power. Can anyone point me to some tips for getting the most out of a single charge. I'm going to keep as many things turned off (wifi, BT, GPS), screen as dim as possible, switch to 2G and no data unless I need them, is there anything else. I have a boeffla kernel so I guess maybe some underclocking and so on, but I don't feel knowledgeable about that!
Click to expand...
Click to collapse
Since you are already using Boeffla kernel, I am sure you will underclock the CPU and GPU to power save modes. You need to switch off google location services. Install a software that can take log of your device's wakelocks and you might want to disable those applications. Xposed is still in Alpha but AMPLIFY on Xposed was a great wakelock fix. You can install GREENIFY from PlayStore to make sure apps are hibernated when not been used.
Qrze said:
You can disable hotplugging and only have one core running which will help save battery. The best thing to do when going for long days is to keep your brightness low. Good luck!
Click to expand...
Click to collapse
10k35h said:
Since you are already using Boeffla kernel, I am sure you will underclock the CPU and GPU to power save modes. You need to switch off google location services. Install a software that can take log of your device's wakelocks and you might want to disable those applications. Xposed is still in Alpha but AMPLIFY on Xposed was a great wakelock fix. You can install GREENIFY from PlayStore to make sure apps are hibernated when not been used.
Click to expand...
Click to collapse
You guys didn't actually read the thread, did you...
Kernel auditor says either 1.4GHz or deep sleep. 200MHz-1.2GHz is unused
I've searched the threads far and wide. I've tried 4 different ROMs or kernels. I've used different Gapps. I'm not seeing any excessive wake locks . It does do deep sleep about 40% of the time (when the screen is off)
My phone drains really fast and runs hot. 6 years of Android. Never seen anything like it.
Resolved: it was KLWP for some reason.
lamortcroix said:
Kernel auditor says either 1.4GHz or deep sleep. 200MHz-1.2GHz is unused
I've searched the threads far and wide. I've tried 4 different ROMs or kernels. I've used different Gapps. I'm not seeing any excessive wake locks . It does do deep sleep about 40% of the time (when the screen is off)
My phone drains really fast and runs hot. 6 years of Android. Never seen anything like it.
Click to expand...
Click to collapse
this is the result of no hotplugging
WaxysDargle said:
this is the result of no hotplugging
Click to expand...
Click to collapse
i run my phone cool without hotplug
its just preference and what works best
HelpMeruth said:
i run my phone cool without hotplug
its just preference and what works best
Click to expand...
Click to collapse
yea, i get much better performance without hotplug
obviously less hours on battery but well worth it