Related
What have we accomplished so far? List your personal running kernel/ROM combos that you are using for the best (and tested) battery life. Let others benefit from your experiences! Thanks!
Das bamf and drods 1.8 bfs kernel set at 1.45. Usually get around 15ish hours with moderate use.
Sent from my ADR6400L using XDA App
Fyretech rom with imoseyon kernel 1.92 dialed down to 1.792, setcpu, atk. Today is the first day running this combo phone has been on since 7am, moderate use (phone calls, texts, games, internet and youtube,) its 10pm now and i have 39% left on battery. I would have had to charge my phone at least once today when it was new out of the box.
EDIT: using 3g, 4g not available yet in central Jersey.
I'm using the bamf v4.3a kernel with the stock rom. i'm also using setcpu set for the 'ondemand' governor and a profile that underclocks the cpu to 245/245mhz when the screen is off.
BAMF 1.4 sense remix, with adrenaline (spelling? 4.4.2 kernel, dark horse theme, auto rotate Rosie (Saweeeet!) Optimal setcpu settings. Ie: charging profile (245 mhz min- 1.0ghz max/smartass) with this setting I normally get almost 1% battery charge increase a minute. screen off profile (700's mghz-1ghz/on demand. Screen on profile (1.1ghz-1.3ish ghz/smartass. etc... I know some stuff I mentioned doesn't really pertain to battery life, but this set up is just sick! Also, I read somewhere that its a good idea to let ur battery die completely, then turn phone on without charging (you may have to just a bit to get it back on) And let die again. This supposedly tells the phone where the dead zone is on the battery accurately, so it can now get a full clean battery charge. Myth? Idk, but damnit my battery is sick now! Hope this helps.
Sent from my ballerific, sick nasty, purely DopeDiculous, T-Beezy with that LTE-Z!
Personally, I've been testing Imoseyon [ROM] Tesla Coil Version 1.5, with Imoseyon [Kernel] leanKernel: minimal kernel "battsaver" .92 version. I am running it on "On Damand" with charging and screen off profiles, mobile data NOT on auto sync, Tasker for wireless ON at Home and audio OFF at nite.
Really, this seemed to have doubled my battery life. I was having to charge before the end of the work day with moderate use and now have been able to use well into the night.
Hope to see even more Rom/kernel concoctions out there as I love to try any new suggestions.
With adrenalines (I still don't memorize the spelling! Lol) 4.4.2 kernel it deff charges waaay faster as stated. Setcpu charging profile to lowest mghz min to around 1ghz max on smartass. Not demand, n it will bounce around to proper mghz levels as needed to speed up charging process. Its sweet n like you, I'm open for more suggestions
Sent from my ADR6400L using XDA Premium App
Adryn's debloat ROM and his kernel, with extremely light usage I pulled 38 hours (my previous record was 36). I have been using my phone for the bare minimum, so this is why I got so high. No, this is not real world usage and yes, I hated it, but it works. My normal battery life is somewhere closer to ~18 hours, except on Tuesday's and Thursday's, when I have lecture classes, I usually pull 9-10 hours, because I play games and browse the internet for 2 and a half hours.
Using imoseyon kernel 1.4 extreme(InteractiveX governor) with Tesla Coil 1.5. I have an extended battery, and with moderate use my phone can easily make it through one day into the next before needing to be charged.
Screen off and plugged in.. ;-)
I think it would be best to post in your stats whether or not you have 4g enabled as there are large populations of each way and it makes a significant difference.
IISiDeK1CKII said:
__________________
HTC Touch > HTC G1 > Apple iPhone > Apple iPhone 3G > Droid Eris > Droid > Droid Incredible > Samsung Fascinate > HTC Thunderbolt
Click to expand...
Click to collapse
Ha! You change phones a lot! My lineage is >>>Samsung MM-A900 flip phone>>>Samsung Jack (Windows)>>>Droid Eris>>>HTC Thunderbolt
ph0tios said:
Using imoseyon kernel 1.4 extreme(InteractiveX governor) with Tesla Coil 1.5. I have an extended battery, and with moderate use my phone can easily make it through one day into the next before needing to be charged.
Click to expand...
Click to collapse
What's the most noticeable of using with the extended battery? Extra cost, bulk or weight? Thanks.
johnchad14 said:
I think it would be best to post in your stats whether or not you have 4g enabled as there are large populations of each way and it makes a significant difference.
Click to expand...
Click to collapse
True...4g always enabled for me other then when I get no 4g signal and then 3g may go into effect. If no signal at all, then wireless when I am indoors.
I refuse to turn off 4g as that is why I got the phone and my coverage is pretty good for 4g...so, better battery life is a must for me
leankernel v .6 @ 1.41 on demand with das bamf 1.4 remix and i disable data when not using it and right now im at 56% battery at 32 hours with moderate use
I'm using imoseyons extreme kernel on interactivex governer on stock. I'm getting 14hrs %40 battery with moderate usage. I'm mostly on wifi all day with a little of 3g use.
Sent from my ADR6400L using Tapatalk
Huge *NOTE!*
Go to settings, menu, wireless networks, mobile networks and uncheck the third box. No need to have mobile data always on for most peeps . You'll still have 4G n everything, but gain a good 1-2 maybe more hrs (depending on use, kernels, governor settings, and I/O scheduling. I personally am running BAMF 1.6.2 with adryns 4.4.7 kernel, no set CPU, using tool box for that at 245mhz min - 1.02max with ondemand governor and most importantly SIO Scheduler. Try these n you will have amazing performance and better battery life. Let me know you opinions
Sent from my ADR6400L using XDA Premium App
For some reason since this morning after a full night of charging everytime my screen goes to sleep or I pus the power button to put the screen to sleep the device completely powers off. Last night I did flash infusion to oc/uv but had several issues and just kept the the device clocked at 12k and did slight uv. Im using setcpu and have a profile setup for screen off but I disabled in hopes to remedy the total poweroff. Any suggestions? How can infusion be removed?
supadupadoug said:
For some reason since this morning after a full night of charging everytime my screen goes to sleep or I pus the power button to put the screen to sleep the device completely powers off. Last night I did flash infusion to oc/uv but had several issues and just kept the the device clocked at 12k and did slight uv. Im using setcpu and have a profile setup for screen off but I disabled in hopes to remedy the total poweroff. Any suggestions? How can infusion be removed?
Click to expand...
Click to collapse
Flash community kernel your getting sod or try removing your Oc UV settings
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Ok thanks. What is sod by the way???
supadupadoug said:
Ok thanks. What is sod by the way???
Click to expand...
Click to collapse
Sleep of death
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
oh lol im learning slowly but fa showly.
supadupadoug said:
oh lol im learning slowly but fa showly.
Click to expand...
Click to collapse
All good
Infusion kernel is great kernel but your settings are going to be trial an error play around with.UV that's usually the probably with sod
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Question about uv. is less best ie -25? and what does disabling the various clock speeds do?
Try using setcpu to throttle your frequencies. If you're having sod that usually means your phone isn't getting the required voltage for your CPU and you're choking your phone.. See if you can set it at 1200mhz and 800mhz on performance mode and see where that leads you.
Thanks I will give that a try. to oc really isn't my goal just to improve battery life. Right now seems to be working ok @12k with frequency uv @75-50
jdbeitz said:
Try using setcpu to throttle your frequencies. If you're having sod that usually means your phone isn't getting the required voltage for your CPU and you're choking your phone.. See if you can set it at 1200mhz and 800mhz on performance mode and see where that leads you.
Click to expand...
Click to collapse
SoD actually usually happens at lower frequencies - after all the phone tends to stay down there when the screen is off.
Typically SoD results from too much UV from 100-400. I never was able to go more than -50 mV undervolt, others hit -100.
netarchy's Gingerbread OC config is a bit different, instead of setting modifiers from stock you set absolute voltages. (No binaries have been released of his kernel until more testing is done - but the source is out there!)
You guys are great everyday i just read and read and im amazed by the information and knowledge passed on. I learn something new every few pages. As for my oc/uv prob i've stuck to minimal uv with no oc and screen off profile and everything is working aok i did switch to the b version of infusion so so far so good. Ive read 28 pages today on the new infusion v2b2 for gb and that will be my next conquest. To all thanks a bunch and continue to the good work and especially helping out the new guys like me. And believe it or not im an electrical engineer lol. Again thanks and much appreciation
supadupadoug said:
You guys are great everyday i just read and read and im amazed by the information and knowledge passed on. I learn something new every few pages. As for my oc/uv prob i've stuck to minimal uv with no oc and screen off profile and everything is working aok i did switch to the b version of infusion so so far so good. Ive read 28 pages today on the new infusion v2b2 for gb and that will be my next conquest. To all thanks a bunch and continue to the good work and especially helping out the new guys like me. And believe it or not im an electrical engineer lol. Again thanks and much appreciation
Click to expand...
Click to collapse
No prob. Buddy glad to have ya
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Entropy512 said:
SoD actually usually happens at lower frequencies - after all the phone tends to stay down there when the screen is off.
Typically SoD results from too much UV from 100-400. I never was able to go more than -50 mV undervolt, others hit -100.
netarchy's Gingerbread OC config is a bit different, instead of setting modifiers from stock you set absolute voltages. (No binaries have been released of his kernel until more testing is done - but the source is out there!)
Click to expand...
Click to collapse
sounds a bit like unhelpfuls kernel from the eclair captivate days. he had absolute voltage values and other freatures. will the gpu clock be configurable? that would be awesome. under clocking the gpu and agressive uv and ucing the cpu could add hours to the battery life. with 2.3.3 you could set the phone to 800mhz and the gpu to 182 or 166mhz could probably give little negative performance in every day use with exceptional battery life.
to the op:
sod can be a problem especially if you overclock. it seems the cpu doesnt like rapid voltage changes. i can uv -200 acriss the board if i dont overclock. if i do im at -150. the 200mhz clock is almost never used but i find if i disable it im more prone to sod presumably because the voltage and frequency jump to 400mhz is too great. it can help if the 100mhz-200mhz clocks have less uv than 400. if you loose stability on 1200 at -100 then maybe set all clocks to -75 cept 100-200mhz which you may set to -50.
this isnt a rule though. you might be able to uv 400-1000 settings quite a bit more than the 1200 setting just if you have sleep of death you generally dont want agressive settings on the 100-200mhz.
Dani897 said:
sounds a bit like unhelpfuls kernel from the eclair captivate days. he had absolute voltage values and other freatures. will the gpu clock be configurable? that would be awesome. under clocking the gpu and agressive uv and ucing the cpu could add hours to the battery life. with 2.3.3 you could set the phone to 800mhz and the gpu to 182 or 166mhz could probably give little negative performance in every day use with exceptional battery life.
to the op:
sod can be a problem especially if you overclock. it seems the cpu doesnt like rapid voltage changes. i can uv -200 acriss the board if i dont overclock. if i do im at -150. the 200mhz clock is almost never used but i find if i disable it im more prone to sod presumably because the voltage and frequency jump to 400mhz is too great. it can help if the 100mhz-200mhz clocks have less uv than 400. if you loose stability on 1200 at -100 then maybe set all clocks to -75 cept 100-200mhz which you may set to -50.
this isnt a rule though. you might be able to uv 400-1000 settings quite a bit more than the 1200 setting just if you have sleep of death you generally dont want agressive settings on the 100-200mhz.
Click to expand...
Click to collapse
Not a clue - I only know what netarchy has done, not what he plans on doing.
The architecture of voltage/CPU frequency control is significantly different in GB kernels than Froyo. In general it's cleaner, so a lot of the issues with rapid frequency changes might go away in GB. For example, there's some code in the base kernel that's supposed to facilitate rapid voltage changes (not exactly sure how... the only documentation people outside of Samsung have for the MAX8998 is kernel source code.)
Well guys I have some news. I continued use with set cpu no oc just uv on freq above 624 @ -75 and I kept my screen off profile set to 644 max powersave scaling, and my battery life has been outstanding i check emails frequently been texting all morning and playing wwf and im @ 70% after 4 hrs of use. I know I read % doesn't mean much compared to some volts ratio but I think this is worth mentioning. And for my purposes the goal has been achieved in extending battery life and still having exceptional performance.
Oh and I wanted to add that my phone recharges much faster especially with the screen off with these setting. Maybe nothing new to you but def a plus for a(us) neewb's reading.
What's the max performance can I get with PBJT OC kernel?
I set voltage to vr/performance at 1400 max...no voltage reduction. Strange i got quadrant score of about 2200 first time but now only 1500 a few times after....same Rom, kernel and voltage setting
What's best way to improve battery aside disabling wifi and Bluetooth? I know brightness is another. I do have juice defender installed too. Also disabling 4G.
Sent from my SCH-I510 using XDA App
Underclock to 800 mhz, with -100mv across the range (or more if your phone can handle it)
Also, calibrate the battery.
Sent from my Droid Charge running GummyFroyo 1.9.1
I loved the 800mhz setting but I didn't notice a battery increase. All I noticed was a slow down in the browser :[ I might have been doing it wrong, was my first time using setCPU/VC.
I know overclocking is all the rage for more performance. I myself would prefer the gains of overclocking (probably wouldn't be 1.7 ghz atm since that is the performance based kernal, but 1.5 ghz might be doable) with a combination of undervolting for longer battery life.
I know when I was considering a viewsonic gtablet, that most of the kernals that overclocked also undervolted at the same time (how much depended on the kernal and how much of an overclock too).
Advantages to overclocking are pretty obvious, more performance. Undervolting makes the processor (this case SOI) run off of less power, thus more battery life (can be significant if undervolted enough) and less heat, which translates into a tablet that potential has a longer life (heat overtime wears away at life of SOI/processors and sometimes other components), plus much lower risk than overclocking. I undervolt all my laptops, I mostly get my laptop with 3 hour battery life to 3 hr 30min or even 3 hr 45 min on a moderate undervolt. A little undervolting could take this tablet from 8-9 hours to possible 11-12 hours of battery life (plus a little overclock included will add some performance too).
Do any of the present kernals out there try this? If not, I would like to make a request for such a kernal.
Undervolting might cause the TP to be unstable and crash.
Sent from my MB860 using XDA App
neer2005 said:
Undervolting might cause the TP to be unstable and crash.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
it would need to be done in small increments just like overclocking. Same methods are used undervolting as you would overclock. Yes they could both cause instability, if you double the clock speed or cut the voltage in half, it takes time to know the limit of the SOI by using small increments.
You will need to your favorite custom kernel and adjust the volts yourself using Govnah.
But then I also was reading on forums on webosbuzz and you can have screen wake issues to with undervolting
Metalshadowx2 said:
But then I also was reading on forums on webosbuzz and you can have screen wake issues to with undervolting
Click to expand...
Click to collapse
Really? If that is true, I wonder how undervolting would cause that.
The webos-internals-testing kernels include initial experiments with undervolting.
I'm using the Faux Kernel on my Skyrocket. I'm using Set CPU for speed control, under-clocking for more battery life.
I head the terms UC, OC, UV and OC. When I use Set CPU, I assume that when I set maximum CPU speeds, I'm under-clocking. But what is under-volting? Is that different? Is there an advantage to doing both?
Harry
There is an advantage to undervolting you need either fauxs app or systemmtuner to do so.
Undervolting is giving the cpu less power and asking it to do the same amount of work it was doing before
Sent from my GT-P7500 using xda premium
That sounds a bit more dangerous in terms of doing damage to the phone or having reboots etc. when you are giving the circuity less power than it was designed.
For those who chose to undervolt for power savings, it is usually done in conjunction with under-clocking, or is it a one or the other type thing?
Not really, under volting is not as dangerous as over volting (used to also achieve higher overclocks). Over volting can actually damage hardware if you provide too much juice.
Under volting just reduces the voltage, if its not enough the app freezes or worse the phone reboots. If that happens, bump it up one more step (+12500) and you should be fine. Find where you can go low but still be stable (for me it happens to be -87500) you will save more battery.
Dixit
all good correct info. I highly recommend fauxclock, its very user friendly. I have my phone undervolted -100mV and underclocked to 1.2 and I'm getting 13 hours heavy usage with around 5 hours on screen time, with NO juice defender. For this phone, that's pretty good
icenight89 said:
all good correct info. I highly recommend fauxclock, its very user friendly. I have my phone undervolted -100mV and underclocked to 1.2 and I'm getting 13 hours heavy usage with around 5 hours on screen time, with NO juice defender. For this phone, that's pretty good
Click to expand...
Click to collapse
My exact setup. -100mV UV, and 1.188 gHz UC. Went from 100% to 0% in 1 day 7.5 hours with 3 hours of screen on time. No juice defender either. I think its pretty food. Using faux 009u, btw.
Sent from my SAMSUNG-SGH-I727 using XDA
Only issue I got with Fauxclock is that it saves the CPU clocks I set (say 1.298ghz max) but it doesnt actually save the voltage after a reboot. I look at the VDD table and its still stock.
So only way to get it to work is to manually edit the VDD table itself. Not sure if this is by default that fauxclock doesnt actually save the voltages after a reboot.
Dixit
Don't see fauxclock in the application store, sorry, Google Play Station.
Thats cause its not in the Google Play. Its a separate app at this location
http://rootzwiki.com/topic/4550-app09-beta-snapdragon-dual-core-oc-control/
Dixit
Got it, thanks. And the under-volting is so easy with Fauxclock, I've set it down 100.
So I've got SetCPU doing the CPU speed, and Faux for the voltage. Seems a bit redundant, since Faux also does CPU speeds, but SetCPU has some cool configuration settings where you can actually have multiple settings for CPU speed based on various conditions such as battery life remaining, processor temperature, time of day, phases of the moon . So I guess I have to keep them both. Hope they don't interfere with each other.
Fauxclock has very basic CPU clock settings, it was created just for that faux compatible kernels so the original developer didnt spend weeks on it. It was just a simple and fast and effective GUI to set min/max clocks and also voltages (global scale). You can however set one other clock which is the "screen off" clock, but thats about it.
harry_fine said:
Got it, thanks. And the under-volting is so easy with Fauxclock, I've set it down 100.
So I've got SetCPU doing the CPU speed, and Faux for the voltage. Seems a bit redundant, since Faux also does CPU speeds, but SetCPU has some cool configuration settings where you can actually have multiple settings for CPU speed based on various conditions such as battery life remaining, processor temperature, time of day, phases of the moon . So I guess I have to keep them both. Hope they don't interfere with each other.
Click to expand...
Click to collapse
they will, use one or the other. U can manually change global vdd table and use setcpu, or forego advanced profiles in setcpu, but u can't/shouldn't use both
FauxClock force closes on launch for me..
EDIT: Getting a Faux kernal fixed that. Wow I feel dumb.
Shadeslayers said:
FauxClock force closes on launch for me..
Click to expand...
Click to collapse
Are u using faux kernel?
Any tips or thread about how to manually change global vdd table so that I can use SetCPU for the profiles and adjust voltage manually?
Is there a risk to that? If I set it and the phone won't boot, it sticks!
use Gideon UV/OC script and change vdd as u see fit. If it doesn't work u can always flash Gideon stock back
icenight89 said:
use Gideon UV/OC script and change bed as u see fit. If it doesn't work u can always flash Gideon stock back
Click to expand...
Click to collapse
What exactly is the difference between flashing Gideon's script or just using FauxClock? Thanks!
fauxclock gives u dynamic min/Max and voltage control as per user settings. Gideon is pre-set and makes use of init.d script. u can change it, but every change requires a reboot