Thanks to Netarchy, Toast, Myn, and Hot_Hands. Big Thanks to NewZJ for helping me test this damn near all day for the past couple of days.
This kernel is based off of Netarchy's 4.2.1 Universal More Aggressive Kernel, so expect the same results when flashing this.
What I've been working on with this kernel is the charging aspect. Desire users have their battery tweak, so I've been working on one for us. With this kernel you'll be able to get the trickle charging experience you've always wanted. I slapped a WIP tag on this thread because although I have gotten this trickle charging to work, I still have some other things I need to iron out and also add.
Things need to fix:
-nothing!
Features:
-All of Netarchy's goodies
-Trickle Charging (AC & USB)
-Full battery charging. Charge your battery to maximum capacity
-Full battery charging for all extended batteries.
-Accurate measurement of voltage while on the charger. Usually on the charger on other kernels, the voltage will still read +4.193V even when the battery is draining on the charger. Now you get to see the draining, so when you pick up the phone in the morning and its not finished with its trickle charging session, you can wait a minute or two until it's done.
-You also no longer need to wipe battery stats.
Lemme clear the air...
- I should clarify. If your phone is at 100% and you're using your phone on the charger, there's a possibility that it will turn off the charger. If your phone is not at 100% then there is absolutely no way the charger will turn off and you can use your phone all you want on AC or USB. And with USB, even if your phone is past 100% you can use it on the charger. So if you're hours upon hours past 100% and you decide to use your phone to do heavy duty work (surf the web for more hours, play some games, listen to some music, stream something), the charger may turn off.
You know when this is working when...
You know this is working when you're 30 minutes past 100% and you don't see any -mA's in the battery widget monitor app (go download from Market, it is free!). If you start seeing -mA's on the charger at any point while charging past 100%, the charger has turned off and this isn't working for you. The only reason the charger will turn off is if you go over the voltage limit. The only way you can possibly go over the voltage limit is if you are using your phone while charging on AC. That is the only way
Will this damage my battery?
Well...this is a running experiment. 8 people have reported battery issues with no real evidence of such thing other than their word. Electrical engineers have spoken of the danger but have yet to conduct an experiment of their own so...use at your own risk! This kernel could possibly blow up your phone, ruin your credit, steal your late night snacks and slap a baby turtle so USE AT YOUR OWN RISK! I AM NOT RESPONSIBLE FOR ANY OF THOSE THINGS (contact PETA about the baby turtle..not me).
my-github
netarchy's-github[/CENTER]
Donation(s)
KERNEL BUILDS
Check 4th post for FAQ's and what not! You only need to flash ONE !!!
SENSE BUILDS
HTC KERNEL #15 v7
12/25/10: v7 Build(s)SBC for Netarchy's 4.2.2 More Aggressive CFS SBC-net-4.2.2-more-havs-cfs-v7.zip (2.9 MB)
SBC for Netarchy's 4.2.2 Less Aggressive CFS SBC-net-4.2.2-less-havs-cfs-v7.zip (2.9 MB)
SBC for Netarchy's 4.2.2 Non-Havs CFS SBC-net-4.2.2-nonhavs-cfs-v7.zip (2.9 MB)
SBC for Netarchy's CFS More Aggressive 4.2.1 (aka 131) 131.zip (2.91 MB)
SBC for Netarchy's CFS Non Havs 4.2.1 (aka 132) 132.zip (2.91 MB)
SBC for Netarchy's CFS More Aggressive 4.1.9.1 SBC-net-4.1.9.1-more-havs-v7.zip (2.9 MB)
SBC for Netarchy's CFS Non-Havs 4.1.9.1 SBC-net-4.1.9.1-non-havs-v7.zip (2.9 MB)
AOSP Builds
v7
12/25/10 - SBC for BC's Kernel SBC-bcnice-stable-v7.zip (2.62 MB)
This is what I'm currently using at the moment. So this gets all the updates as of right now.
v8-BETA
12/25/10 - SBC for BC's Kernel SBC-bcnice-stable-v8.zip (2.62 MB)
This is what I've been testing for a while. This build contains auto bump charging based on the voltage as opposed to the full charge method. I don't know how it works on extended batteries yet...but works pretty good on stock batteries. With this, you should have a better chance of picking up the phone at higher voltages.
Check out Savaged-Zen!
First...... anyways thanks for the updated kernel. I have been waiting for this.
second are you working on the screen on issue or whatever you want to call it.
thanks
tim
Didn't get the 3rd post so this will have to do...
FAQ's
Q: Can I use my phone while on the charger?
A: Yes! I was saying not to because I was mixed up for a bit. You can in fact use it on the charger. There is just the chance that you will raise the voltage and turn off the charger. But that has been fixed in the v3 builds. So its all good now
Q: Do I need to flash build 130-132 before flashing SBC?
A: You only need to flash one kernel. Either 130-132 or SBC
Q: What should I look out for to see if it's working?
A: First, grab "battery monitor widget" from the Market (it's free). Then place the widget anywhere on your homescreen and open it up. Change the update interval to 50 secs. Then just charge as usual. When you've hit 100% just wait a while afterwards (2-5mins). Then open up the widget and go into the history section. You should see nothing but positive mA's. Positive mA's mean that you are still charging even though you are past 100%. That's a good thing. That means its still charging. Now, charge overnight. When you wake up in the morning do the same thing, check your history. If you see any negative mA's, that is not good. That means that the phone still couldve been charging, but something is acting in the background and doing some work. If you still get negative mA's on the v3 builds, shoot me a pm and we'll work it out.
Q: How should I flash this?
A: Flash it like you would normally flash any other kernel.
1.Wipe Cache & Dalvik.
2. Flash Kernel
3. Reboot
-------------------------------Some few tips here and there...
All of the Sense kernels work great with all Sense roms. The AOSP kernels should work well with AOSP. I can't test that because I'm not on AOSP. SBC charging works great in all kernels with AC. SBC USB charging is not in all kernel builds, only the v2 and v3 builds.
information on CFS/BFS/HAVS/No-HAVS etc etc...check this thread out!
NIce Thanks
I have an extended battery and it's kind of irritating to have to do the whole turn off, charge til green, unplug, charge til green, over and over to take full advantage of the extended battery. If you get this to work on extended batteries I will buy you a beer!
on charger with green light for 7hrs, screen on, phone awake, off charger for 5 min still at 100%
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
edit, stayed at 100 for 30 min, has been at 99 for almost an hour
nice thx ! would love to see this on CM6
Can you possibly do this with a non-HAVS based kernel or the "less agressive" undervolting one? Myself along with a lot of others have evo's that do not play well with undervolting and would like to use this tweak...
thank you, this makes an awesome kernal even more so.
CheesyNutz said:
nice thx ! would love to see this on CM6
Click to expand...
Click to collapse
Amen!!!!!!!!
Unknownforce said:
Can you possibly do this with a non-HAVS based kernel or the "less agressive" undervolting one? Myself along with a lot of others have evo's that do not play well with undervolting and would like to use this tweak...
Click to expand...
Click to collapse
mine doesn't play the best with undervolt kernels but works fine with this one, have you tried it?
CheesyNutz said:
nice thx ! would love to see this on CM6
Click to expand...
Click to collapse
+1 on that.
What should the setCPU settings be on this?
This is awesome. Any chance on you or someone else doing this to an aosp kernel.
Sent from my PC36100 using XDA App
ms on the other thread, with this #74 kernel some are getting battery voltages while charging to go slightly over 4200. The highest mine will go is 4187 no matter how long I leave it. Did you set a max on here that may be acting as a cap? Or could my 3500 seidio be the culprit maybe. Ready for your extended battery version.
Would also like to know if set cpu should be involved here?
i run setcpu, try and see if these help
NewZJ said:
mine doesn't play the best with undervolt kernels but works fine with this one, have you tried it?
Click to expand...
Click to collapse
I haven't tried it yet, no, especially since it doesn't sleep or whatever, I'm waiting until it's a little more to a "release" status, but it still would be nice to have some options ya know?
Unknownforce said:
I haven't tried it yet, no, especially since it doesn't sleep or whatever, I'm waiting until it's a little more to a "release" status, but it still would be nice to have some options ya know?
Click to expand...
Click to collapse
word.. i love options too, hopefully most/all/many kernel devs will incorporate ms79723's work into their kernels and the entirety of evo users can benefit, i dont doubt htc/sprint may kang it for stock setups
Related
Test # 1 Video Streaming Over WiFi
ROMS Tested So Far:
Continuum
Serendipity
Precision
Firefly
Cognition
Phoenix
Paragon
Twingerbread
Supernova
Darky's
di11igaf
Dragon
Andromeda
**DISCLAIMER**
Keep in mind that results will vary for each phone and just because I get a certain battery life using the rom's and kernel's listed below does not necessarily mean that you will.
Tired of constantly flashing to find great battery life only to realize the rom didn't meet your expectations; then this thread is for you. Over the next few weeks I will test every rom imaginable and post real world results that will include battery stats, linpack and quadrant results.
**This is not meant to put down any particular ROM. Without our great dev community my captivate would have been returned and thank you all for your hard work.**
[Goal]
To provide the captivate community with real world results from top roms in everyday usage where battery life is the key focal point, but performance is not affected. Hopefully this will help save you time from having to flash multiple ROMS.
[Roms]
*This list will continue to grow*
Stock 2.2 kept fcing so will test it on test 2 this evening 3/28
[Usage]
Each night I will run the exact same VERY LONG documentary using VLC stream and convert and current widget.
[Specs]
*Every rom will run "out of the box" meaning Kernel, Modem, Settings all default to how it was cooked*
° Default clockspeed 1000mhz (as suggested by a smart person listed below)
° 40% Brightness/Screen Timeout Turned Off
° 100% Charge each run (0mV to make ryude get a chubby)
° Auto Sync off
° GPS off
° Zeam launcher
° VLC Steam & Convert used w/ same long documentary used each time
° Phone is placed in exact same spot every test and is unplugged as soon as I hit play
Results So Far
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Test # 2 Web Browsing
Test # 2 Web Browsing on 3g
Roms Tested So Far:
Continuum
Serendipity
Precision
Stock 2.2
Firefly
Phoenix
Paragon
Currently Running:
Twingerbread
Upcoming:
Supernova
Darky's
di11igaf
Dragon
Andromeda
Juiced
Cognition
Goal:
In previous tests I tested on wifi using a vlc stream & convert. With this way of testing I'm hoping to get more realistic real-world results that you can use as a guideline to a roms overall battery performance . Keep in mind your results may vary.
Testing:
Every night I will set tab reload to 15 seconds and it will continuously reload XDA website until the phone dies. It will be placed in the same spot in my house every night and will be ran on phone data, thank god for the unlimited plan.
Applications I will be using:
- Dolphin Browser HD
- Reload tab plug-in
- Current widget
- My Settings
[Specs]
*Every rom will run "out of the box" meaning Kernel, Modem, Settings all default to how it was cooked*
° Default clockspeed 1000mhz
° 40% Brightness/Screen Timeout Turned Off
° 100% Charge each run
° Auto Sync and GPS On (To help give near real world results)
° 3g
° Zeam launcher
° Phone is placed in exact same spot every test and is unplugged as soon as I start Reload Tab Plug-in.
**Will be running all tests on 3g as some ROMs do not have HSPDA**
Results
Reserved for future use
Cool. Any chance you can add stock Froyo to the list as a reference point? It would be interesting to see how much custom rom's are improving over stock...
TheSopranos16 said:
Cool. Any chance you can add stock Froyo to the list as a reference point? It would be interesting to see how much custom rom's are improving over stock...
Click to expand...
Click to collapse
Great suggestion only thing is I won't be able to undervolt so numbers will not be accurate to this testing, but I might run the best two roms after I'm done testing at there defaults against stock froyo.
Since many users are set at the standard 1000, would you consider the testing at standard 1000 speed for a more accurate battery life any user can expect. Just a suggestion
Sounds like Precision should be included, with the black theme it easily gets great battery life.
diablo009 said:
Is this under-clocked? I am on the same ROM with speed at 1000 with no under-volting.
I get 1600+ scores on quadrant, and 14+ scores on linpack (tested out even now).
Click to expand...
Click to collapse
Yes I listed in the specs what they will all be running at. All are uc/uv to 600mhz.
I have been waiting for something like this but I assume that the devs would all be up in arms if someone rated their ROMs higher/lower.
If this thread will be allowed to continue, totally looking forward to the results.
And you should totally throw Precision into the mix as it seems like the de facto battery saving ROM as it skimps on a few services.
Enhanced said:
I have been waiting for something like this but I assume that the devs would all be up in arms if someone rated their ROMs higher/lower.
If this thread will be allowed to continue, totally looking forward to the results.
And you should totally throw Precision into the mix as it seems like the de facto battery saving ROM as it skimps on a few services.
Click to expand...
Click to collapse
Personally, if I was a dev and saw that my rom wasn't too good, I would try to make something better. So who knows how it turns out. A little competition wont hurt anyone, and hopefully have better roms! Btw, good idea with this
Sent from my SGH-I897 using XDA App
Just finished di11i on to paragon. The theme on di11i is very nice too almost a carbon fiber look.
add Torch 1.5
Also try Torch 1.5. So far been outstanding in battery department.
I know this doesn't help as far as battery life, but just for a reference as far as stock 2.2:
1. Linpack - around the 14 mflops (sometime in the 13 range, sometimes in the 14)
2. Quadrant - 1050 or so
3. Nenamark1 - 51 fps (not sure if anyone uses that one much, but thought I would throw it in as I had it available lol)
I would estimate the battery life if I didn't use the phone at all (just left it sitting in standby) would be at 60hours plus, as I get up to around 40 with light usage on 2.2 with battery to spare (haven't run it dead yet to be honest on 2.2) Still a little early though as the phone hasn't been drained and recharged full thus far.
I just checked my phone, and I have had it on for over eight hours, and I am at 92% battery left. I have hardly used the phone today (just a few texts is all), but going on that I should get around 80 hours on a single charge if I just leave it sitting there.
Great idea. I'm a huge continuum fan
Sent from my GT-I9000 using XDA App
good info to know...thanks alot!
This sounds like quite an undertaking. Good luck with the project. I'm looking forward to the comparisons. Thank you for your hard work to benefit Captivate owners out there.
Sent from my SGH-I897 using XDA Premium App
Charge drain charge drain lol gonna get online now and buy a new battery just incase i destroy this one.
LOcation matters
I am using JuicePlotter to monitor my battery usage closely. From what I see, different locations give dramatically different battery life. At home my battery drops 1% per hour. At work 20 miles away it drops 2% on captivate modems but 4-5% on i9000 modems. So the signal strength, cell tower type make big difference.
I have tried multiple Cog ROMs and Paragons ROMs, currently on Twingerbread 3.2. The best ROM in terms of battery life is cog 3.2 for me.
Yea but most people throughout the day are on the move and all I'm trying to achieve are results based on that. The constant will be the kernel in this test that way any thing I log can be directly attributed to the rom/modem. This by no means is the end all, but it will give the community a great idea of where each rom sits.
Interesting kernel choice. I've heard Suckerpunch lauded, but that ignores the fact that most of these roms flash with a different kernel by default. Is it a better test to run them all with the same kernel, or with the one they chose?
I dunno. Might be interesting to test and formally see how much kernel choice affects things.
Hey Guys,
Thought I Would share for any interested...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
*Added a setting for charging that is 100/1400 conservative with a priority above everything except the heat one. so like 91 heat and 89 charging.
Seems stable, zippy and doesn't kill the battery too fast. All good.
Nobleskill
UPDATE: the settings above worked a treat for me on froyo but after updating to gingerbread I found it was back to the old drawing board time. For whatever reason, and being fair to Samsung and gingerbread by saying that the tab is now older and been used and abused its whole life, I wasn't able to apply the same level of undervolting without lockups and rebooted.
Why? Well could be a few reasons, the one mentioned above I really think plays a part in it. I also think though that gb is just different. Obvious I know but I mean its different at a base operating level. It needs new bootloaders and as alot of the experienced developers currently doing the tab gb stuff I think are finding its got a few curveballs its very happy to throw into the mix. The other point is that the control app has been updated dramatically with new ui and a more polished look to the outside which I think also follows into the coding. Xan, the developer must be a very talented individual and is pioneering the CPU control at kernel level IMO and really deserves our support. You can get the fee apk but I think its worth a donation just for the free version.
I notice the newer kernels are also having preset UV settings which is awesome. Gives you a base to build on and as each tab is different, yours may not go as low in volts as little Johnny's tab but it may go further than big Bob's one, it provides a good starting point. Or whatever..
Jump on over here: http://forum.xda-developers.com/showthread.php?t=943669
This guy is my favourite developer evar! Very friendly, very talented and shares <3. Read this thread as much as you can, its brilliant and has a few gems hidden in the posts. Also the kernel's are basically on the cutting edge. Its this guys patches that find their way to other, and all I'm pretty sure, kernels and roms.
thanks a lot buddy ! I was really looking for this !!!!!! you're my hero !!!!
Your most welcome mate. Any issues make sure and let me know through this thread.
Nobleskill
Ps. Watch how big a difference it makes to battery drain with screen off and below 30. I keep thinking it will die before I get a charger and like 4 hours later its only gone down by about 10 percent.
As always, support the Dev's if your able to. They richly deserve it and it doesn't have to be much to make a difference. )
nobleskill said:
Your most welcome mate. Any issues make sure and let me know through this thread.
Nobleskill
Ps. Watch how big a difference it makes to battery drain with screen off and below 30. I keep thinking it will die before I get a charger and like 4 hours later its only gone down by about 10 percent.
As always, support the Dev's if your able to. They richly deserve it and it doesn't have to be much to make a difference. )
Click to expand...
Click to collapse
there is a problem regarding those settings. did you try to restart the Tab after? mine doesn't start at all ! I should try several times to keep pressing the power button and then, after few minutes it starts again. after uninstalling the Set CPU and Voltage Control, everything comes to normal.....any advice?
SetCPU seems to be very crashy on the SGT. You might want to try not decreasing the voltages quite as much, some CPUs can't cope with it. I've got mine set even lower and I'm fine.
The "performance" governor locks the speed at the "max" value, the "powersave" one locks it at the "min" value. It's a pity that the "Ondemand" and "Interactive" governors seem to be so unstable as either would be better for performance than "Conservative".
I've also got another profile for "Charging" which ramps everything up a bit.
One thing I have noticed after spending some time in here is that all SGT's are not created equal!! I have no issues with the settings above, none at all. It boots fine, runs super fast with 2200 being the average score in quad. And I am on my second day without charging... its been lighter usage but still....
I guess I got lucky but all I can say is trial and error, or search for a simillar problem with another user and ask what settings if any worked for them. My thinking is that there would be batches that will run one way and others that won't.
nobleskill said:
One thing I have noticed after spending some time in here is that all SGT's are not created equal!! I have no issues with the settings above, none at all. It boots fine, runs super fast with 2200 being the average score in quad. And I am on my second day without charging... its been lighter usage but still....
I guess I got lucky but all I can say is trial and error, or search for a simillar problem with another user and ask what settings if any worked for them. My thinking is that there would be batches that will run one way and others that won't.
Click to expand...
Click to collapse
Its the CPU. They all have different tolerances on the minimum they can run at. Samsung just uses a voltage that guarantees all of them will work at. I've decreased everything 800mhz and up to -200mv. So far so good.
ovigt71 said:
there is a problem regarding those settings. did you try to restart the Tab after? mine doesn't start at all ! I should try several times to keep pressing the power button and then, after few minutes it starts again. after uninstalling the Set CPU and Voltage Control, everything comes to normal.....any advice?
Click to expand...
Click to collapse
Try install jus UV & set the limit to 1400ghz. Run it for a day or two.
I have problem with SetCPU, give up on it. So now i only have UV installed.
thanks for the settings, no problems since 1 day
Sorry for stupid question, Am I need to flash kernel for 1400ghz? Or just use SetCPU with overcome 1.0 karnel?
Since there are some karnel said they are for 1.4ghz so I am confusing on it, tks!
izamoscar said:
Sorry for stupid question, Am I need to flash kernel for 1400ghz? Or just use SetCPU with overcome 1.0 karnel?
Since there are some karnel said they are for 1.4ghz so I am confusing on it, tks!
Click to expand...
Click to collapse
If the kernel does not support >1ghz, then setcpu cannot set the speed to anything higher.
The overcome kernel supports an overlock of 1.2 and 1.4Ghz.
Overcome Kernel 1.0 is an overclock kernel. Just install setcpu to oc
nobleskill said:
Hey Guys,
Thought I Would share for any interested...
Seems stable, zippy and doesn't kill the battery too fast. All good.
Nobleskill
Click to expand...
Click to collapse
with the settings above do you have it set up as "Save as boot settings"? i had set mine at bfq and limit clock to 1200mhz and not changing anything else saving it as boot but when i went to restart the tab it got stuck on the Galaxy Tab screen, i had to re-store my backup in order for the tab to re-start.
also how did you get the 600mhz:?-100=?mv?
i am using richardtrip's [Kernel] [EURO] [1.4ghz OC/UV] MCR EXT4 compatible/Voodoo Sound V15 22/02 hope that helps with what i am asking.
I gave up on Set Cpu and switched to Cpu Tuner, a choise I don't regret at all.
Sent from my GT-P1000 using Tapatalk
Recently changed to overcome kernel 2.0 and have changed to bfq. All stiull running smoothly.
And yeah i have mine all set to set at boot.
Thanks! Was looking for this.
I copied your settings to the last detail (bfq scheduler) and my Tab is crashing.
Now I am trying with lower UV.
braby said:
I copied your settings to the last detail (bfq scheduler) and my Tab is crashing.
Now I am trying with lower UV.
Click to expand...
Click to collapse
Sorry buddy its been ages I should probably update this. I find that overcome has gottan alot better I still use the same undervolting but no profiles on set CPU. Just set to 100 min and1400 Max ondemand. I can use bfq and have no issues but one thing I know for sure, and I think it was even stated in this thread, no 2 of these are the same... same deal with more strain on the CPU than others so if my settings didn't work for you I'm sorry for that but all I can suggest is what I did to find the right setting... experiment, trial and error...
Best of luck,
Nobleskill
I found out what I did wrong...on Screen Off profile I didn't set "Performance" scaling, instead I did "Conservative"...the Tab was only crashing when screen was off!
Now that I switched it to performance it works just fine...
Using Overcome 1.4.2...
What's has better battery life, now that you have experience with both, with the profiles mentioned above or "On Demand" with no profiles?
That's a tough one as I use my tab a whole heap more and for many more things. I have 3 times as Widgets and so on... put it this way I used to get 2 days with low to moderate use on the setting in this thread, now with extremely heavy usage, I'm talking 8 hours or more almost straight with web browsing, ebooks, video, music, news ect...
I like my new set up cause its alot easier to configure and I find the most important aspect to battery life is the undervolting... overcrowded seems to handle the just fine. The only other thing I really swear by is an app like juice defender or battery boost.. set them up and its turning things off when not used which can be massive...
Hope this has helped and I'm happy to hear you sorted the crash issue.
Nobleskill
Good Morning Thunderbolt Community:
I am looking for the best way to extend my battery life, I have a 2750 Extended battery and still only get a little over a day of battery life. I've read that some folks are using SetCPU again, and would like a thread dedicated to those who want to share their settings to benefit others....
Thanks in advance...ChiefDroid (a.k.a Chiefd23)
Running chingys 3d rom runing set cpu st 1113 max 368 min no profiles and st the end of my 12 hour day I have 70% left. have any more questions lemme know
Liquid gingersense 1.6. Imoseyons 3.5 kernel on extreme mode. Verizon 2750 battery. I get 50 hours easy with a lot of phone usage.
Gingeritis 3D beta VI, ziggys kernel set at 245/1.344 smartass gov, with script fusion (set cpu can be a big no no with some kernels, and id rather use scripts anyway) . I get 20+ hours with average use on a stock battery.
Sent from my TBolt using my f***king thumbs...
Pureasoptheory 1.3x modded imo kernel (stock with rom) setcpu at 1222/245 interactive and a profile for less than 30% @745/245 avg is around 24 hours on stock battery with low to moderate use, maybe a couple youtube videos lots of texting a few calls and lots of web browsing.
Edit: about 50% of the time I'm on wifi vs. 4g to clarify.
M0N0LITHTH3ORY. 245/1024 extreme battsaver. Standard battery. Lucky to get 8 hours. Best battery life of any rom for me so far. Average an hour of calls, 100 texts, TweetDeck and friendcaster pretty much every hour, words with friends, and web browsing.
Sent from my HTC Thunderbolt 4G LTE: M0N0LITHTH3ORY V1.1: MR2 using XDA Premium App
Hack3dao5p by dhacker29. 12 hours and I'm at 80% NO UNDERVOLTING. I will undervolt with vipermod tomorrow and report back. Don't use setCPU. Use vipermod or speedtweak. I recommend vipernod for more control.
Just plug it in every night. I can get 2 days out of my extended battery but what's the point??? Have fun with it instead of worrying about getting more than one day of battery out of it!
Sent from my ADR6400L using Tapatalk
pitchblack86 said:
M0N0LITHTH3ORY. 245/1024 extreme battsaver. Standard battery. Lucky to get 8 hours. Best battery life of any rom for me so far. Average an hour of calls, 100 texts, TweetDeck and friendcaster pretty much every hour, words with friends, and web browsing.
Sent from my HTC Thunderbolt 4G LTE: M0N0LITHTH3ORY V1.1: MR2 using XDA Premium App
Click to expand...
Click to collapse
Same here on all accounts
xTFGx said:
Hack3dao5p by dhacker29. 12 hours and I'm at 80% NO UNDERVOLTING. I will undervolt with vipermod tomorrow and report back. Don't use setCPU. Use vipermod or speedtweak. I recommend vipernod for more control.
Click to expand...
Click to collapse
I think I might make the switch! How much use? light, mod, heavy?
M0N0LITHTH3ORY straight out of the box, I'm getting close to 20 hours with 20% left for the first time ever. 4g when I'm out and WIFI at home. Like I said in the MONO thread this ROM is the best out there. oh yeah stock battery too. Thanks DT!
This is by no stretch of the imagination an Android development thread.
Fits better in General. I've moved it there.
Continue.
I haven't used SetCPU on my Tbolt in a while. My config is in my sig and my settings are implemented through ScriptFusion. The following is the settings I'm using in ScriptFusion. The first image is the clock/voltage settings, the second image is time-in-state. As you see, it spends most of it's time sipping .8 volts or less. As long as I'm not tapping glass like a mad man, eeking out a full day on the stock battery isn't terribly difficult.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
justavillain said:
Same here on all accounts
I think I might make the switch! How much use? light, mod, heavy?
Click to expand...
Click to collapse
Mod-heavy mostly internet jtexting and Facebook with a few phonecalls here and there. GPS off
i use gingeritis 3d, wifi when im home, and when im out, i only activate mobile data if i wanna check my fb or look something up. cpu is usually max 1113600 min 8064000 scaling powersaver, i also use chainfire's nightmode setting when im not actively using my thunderbolt (tested today and seamed to help alot), auto brightness on. at the end of the day on a stock battery i am usually at 20-10%
I flashed the newest radio turned off 4g and am running CL3ANTH3ROY and i got 20 hrs on the charge off of 1.0. Im on 1.1 now at about 14.5 hrs on mod/heavy use with a little 4g use in there.
I know if you do not have 4g in your area all the time turning that off is a MANOR battery saver. If you didnt know go *#*#4636#*#*phone identity, scroll down and choose cdma auto (prl)
sent from my thunderbolt running CL3ANTH3ROY, using the XDA premium app
z06mike said:
Just plug it in every night. I can get 2 days out of my extended battery but what's the point??? Have fun with it instead of worrying about getting more than one day of battery out of it!
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
This.
I charge mine every night and it makes through the whole day no matter what I throw at it. I keep email on push notifications and gps/sync on all the time. 4G is on all the time. None of those are ever turned off.
Why? Because that's how smartphones are supposed to be used! It's not a marathon race.
Sent from my Synergized Thunderbolt via XDA Premium App
Can I just make a quick comment about freq_min, freq_max, and governors? I like to equate them to a car's engine. At idle (freq_min), it's should be just loafing along, doing the least needed to keep things going. At red line (freq_max), it's chugging down the fuel and kicking out all the horsepower possible to haul that ride down the road. And your governor is kinda like your cruise control. You're cruising across Nebraska, not a hill in sight (you're phone is doing nothing) and it's just BARELY tipping that throttle in to maintain. But, you hit Colorado with those big ol' hills, and now it's flooring it, letting off, then flooring it again to get over those hills. Think of those hills like you making your phone do stuff.
Here's my point:
When you set your freq_min to 800MHz with, it's like running your engine at 5000RPM, all the time, regardless of load. Setting your freq_max at 800MHz is kinda like jamming a stop under your throttle so it will never make enough power to pull you over those big hills. The idea of a governor is to throttle the speed up and down relative to the load... kinda like your cruise control. Some could do it better, some have very limited real-world application (performance and powersave), and some are pretty much ideal. It really depends on how the dev has set them up or how you've tweaked them.
I post this because I'm looking at some of the setting some of you are using and I KNOW they could be more efficient. I would encourage you to look at your time-in-state and experiment with your freq_min, freq_max, and gov. As you can tell from mine, though I have my max set at 1.49GHz, it spends VERY little time up there. It's more like the nitrous shot if things get real hairy and the system needs the extra power.
i currently use BURNTH3ORYX V1.5 w/ the MR3.5 (802) radio, also have the 2750mAh battery, and i just use the built in "performance" option. I set it to 'OnDemand' and overclock to 1.5 Jigga Hertz.
for example, last night the battery was at 100% and decided to watch the movie "Return Of The Living Dead" all the way through. when it was done, the battery was at 95%.
Please tell me if my Deep Idle is working. I imagine that there are others with the same question. Here is a picture.
No. You need to flash the Bluetooth framework fix. I take it you are on stock/a stock based rom?
nodstuff said:
No. You need to flash the Bluetooth framework fix. I take it you are on stock/a stock based rom?
Click to expand...
Click to collapse
Nope im running CM7 with Matrix kernel 11.5
also i dont use BT
Turn on Screen Off Max Freq. Also, you mean CM9 right? And i believe the latest (a20p1) has the bluetooth fix incorporated.
Harbb said:
Turn on Screen Off Max Freq. Also, you mean CM9 right? And i believe the latest (a20p1) has the bluetooth fix incorporated.
Click to expand...
Click to collapse
CM7 with a ICS Theme and even though i dont use BT i still need to flash this? Where do i find such a God given thing? lol
Sorry, for some reason i thought you said matr1x 14.5. The bluetooth bugfix is, as far as i know, only for ICS ROMs (bluetooth is always "ready" to turn on, which forces only top=on time). Turning on Screen Off Max Freq will hopefully give you some deepidle time.
Harbb said:
Sorry, for some reason i thought you said matr1x 14.5. The bluetooth bugfix is, as far as i know, only for ICS ROMs (bluetooth is always "ready" to turn on, which forces only top=on time). Turning on Screen Off Max Freq will hopefully give you some deepidle time.
Click to expand...
Click to collapse
Thanks bud. Not to be a nooob and all but how long does it take to initiate?
I'll get some top=off time after about 20 seconds with nothing at all in the background and using matr1x 14.5, stock ics, 100/1200, lazy and screen off max freq. I would say if you don't have anything after a 2 or 3 minutes it's not activating for some reason.
Harbb said:
I'll get some top=off time after about 20 seconds with nothing at all in the background and using matr1x 14.5, stock ics, 100/1200, lazy and screen off max freq. I would say if you don't have anything after a 2 or 3 minutes it's not activating for some reason.
Click to expand...
Click to collapse
Cool ill check that out. What ROM/KERNEL combo do u have? what the battery life on that 100/1200 set up?
Cool ill check that out
I said the ROM and kernel in the post and it's in my sig too. With 4 hours of gaming and 2 hours of general internet browsing i got around 12 hours with weak 3G signal. Battery drops very little with no use, somewhere around 5%/10 hours. I havn't noticed any major battery drain OCing to 1200, just a little bit of heat on demanding games. Drain is proportional to increase in perfermance most of the time.
I'd definitely be confident going 2 days with a single charge as long as screen time is kept under a couple hours. ATM i'm playing around with different governors to get better battery life, deep idle won't be any use to me for another month or so.
Harbb said:
I said the ROM and kernel in the post and it's in my sig too. With 4 hours of gaming and 2 hours of general internet browsing i got around 12 hours with weak 3G signal. Battery drops very little with no use, somewhere around 5%/10 hours. I havn't noticed any major battery drain OCing to 1200, just a little bit of heat on demanding games. Drain is proportional to increase in perfermance most of the time.
I'd definitely be confident going 2 days with a single charge as long as screen time is kept under a couple hours. ATM i'm playing around with different governors to get better battery life, deep idle won't be any use to me for another month or so.
Click to expand...
Click to collapse
I know your running stock but there are sooooo many stock ics roms for the NS4g.
After booting up, open and close the camera. That works for me.
I'm on CyberGR CM7
turkobr said:
After booting up, open and close the camera. That works for me.
I'm on CyberGR CM7
Click to expand...
Click to collapse
Ain't that some shiznik! It worked! Thanks broski!
Sent from my Nexus S 4G using XDA App
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what it looks like now.
Sent from my Nexus S 4G using XDA App
treyweez11 said:
This is what it looks like now.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
This is know as the CAM bug which was fixed in ics kernels. Every time you reboot the phone your camera is active and prevents the deep idle from working. Opening and closing a camera app closes it and deep idle can start working.
Isn't the cam bug only fixable by disabling/removing google talk (or installing the non-video one)? Otherwise you are forced to open and close a camera app each time you reboot to get any top=off values.
Also, i mean true stock, google OTA. The NS4G doesn't have this yet.
Harbb said:
I'll get some top=off time after about 20 seconds with nothing at all in the background and using matr1x 14.5, stock ics, 100/1200, lazy and screen off max freq. I would say if you don't have anything after a 2 or 3 minutes it's not activating for some reason.
Click to expand...
Click to collapse
Could you please explain what does screen off max freq do ? I have tried to get into those things May be now is a nice time
While screen is off, allow the processor to use max frequency (stock is 1000mhz). This allows "race-to-idle" which the hardware is capable of, effectively reducing the amount of time the CPU is processing (and therefore powered), reducing power consumption and further allowing deep-idle to work.
Hey guys, I'm new to this forum but not Android Central. Anyways, I just recently switched to jelly beans build 14 w/lean kernel. For some reason my battery life is just terrible. I'm just barely making it through an 8 hour workday, and that's not even using it that much. I was wondering if you guys had any tips for good battery life on this ROM/Kernel combo. I do have set cpu installed and running but I'm only Overclocked to 1.6 and undervolting by 50 mv. I also have a save battery life profile that drops it down to 1026 when the screen is off, it's charging, or battery is below 40%. Can you guys give me advice on settings to use to save battery life? I really like this ROM and kernel but I'm getting such terrible battery life. I think it's probably more user error than anything but maybe you guys could provide some tips.
Thanks in advance.
Nick
sent from my Galaxy S3 on beans 14 via tapatalk 2
How recently did you switch to Beans and LK combo? I wouldn't base battery life off of the first day after a flash. I use the same combo, however I use the LK exp version. I would suggest changing your voltages to match begin at a lower mv. I have mine starting at 900 mv according to Imoseyon voltage chart.
http://rootzwiki.com/topic/31329-ke...nimalistic-kernel/page__st__1410#entry1042976
That said, I have my screen off max cpu speed at 486 so you could probably go lower. How's your signal at work as well?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
How recently did you switch to Beans and LK combo? I wouldn't base battery life off of the first day after a flash. I use the same combo, however I use the LK exp version. I would suggest changing your voltages to match begin at a lower mv. I have mine starting at 900 mv according to Imoseyon voltage chart.
That said, I have my screen off max cpu speed at 486 so you could probably go lower. How's your signal at work as well?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Hey thanks alot for the response!! It's the third day of this ROM/Kernel combo. So I can really go as low as 486 when the screen is off? I figured it probably wouldn't be very stable if I dropped it that low. I've looked at the Rootzwiki thread you posted and have set all my voltage settings as follows for the last two days:
1900mhz-1250mv
1809mhz-1200mv
1720mhz-1200mv
1620mhz-1150mv
1512mhz-1100mv
1458mhz-100mv
1350mhz-1125mv
1242mhz-1125mv
1134mhz-1125mv
1026mhz-1125mv
and its 1125 mv the rest of the way down.
So basically I'm undervolted by about 50mv at the highest clock speeds, then gradually come down to about 25mv at the lower speeds.
I'm really scared to go much more than that for fear of causing instability. I would love to be able to undervolt by more if I knew for sure it wasn't going to make it unstable. What are your voltages at the highest clock speeds and the lowest? Can I undervolt it by more when I get down below 1026 mhz? I figured they were all set to 1150mv stock for a reason. Got any advice on that? I want to squeeze as much battery as possible..
Oh and my signal is perfect! I think it's even better than it was before. This Rom didn't come with a different radio too did it?
Thanks for the reply!!
nicholi2789 said:
Hey thanks alot for the response!! It's the third day of this ROM/Kernel combo. So I can really go as low as 486 when the screen is off? I figured it probably wouldn't be very stable if I dropped it that low. I've looked at the Rootzwiki thread you posted and have set all my voltage settings as follows for the last two days:
1900mhz-1250mv
1809mhz-1200mv
1720mhz-1200mv
1620mhz-1150mv
1512mhz-1100mv
1458mhz-100mv
1350mhz-1125mv
1242mhz-1125mv
1134mhz-1125mv
1026mhz-1125mv
and its 1125 mv the rest of the way down.
So basically I'm undervolted by about 50mv at the highest clock speeds, then gradually come down to about 25mv at the lower speeds.
I'm really scared to go much more than that for fear of causing instability. I would love to be able to undervolt by more if I knew for sure it wasn't going to make it unstable. What are your voltages at the highest clock speeds and the lowest? Can I undervolt it by more when I get down below 1026 mhz? I figured they were all set to 1150mv stock for a reason. Got any advice on that? I want to squeeze as much battery as possible..
Oh and my signal is perfect! I think it's even better than it was before. This Rom didn't come with a different radio too did it?
Thanks for the reply!!
Click to expand...
Click to collapse
I actually have my voltages set to exactly what Imoseyon has listed for the nominal cpu. As far as my screen off, I honestly just picked a low number and since I don't see lag I keep it there haha in addition, I use interactive governor which scales up the cpu once the screen comes on so it balances out either way.
To check which cpu type you have, do this. Details on what the cpu differences are included in the link as well. Matching your cpu type and adjusting your voltages may help extend your battery life but some say it is marginal.
No, your radio actually stays the same unless you manually flash a different one. I should also ask, what else do you have enabled? For example, in Maps/Settings, do you have everything disabled except "Enable Location History"?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yeah i already did that to sort out what Cpu I have as well.
And I have limit background processes enabled in developer options, limit processes 4 at most. Also where exactly are the maps settings? I have GPS off and Google maps frozen by Titanium backup (except when I use it occasionally). I also have every other unnecessary app frozen. Like the Samsung keyboard (use swiftkey) the stock email app, etc.
sent from my Galaxy S3 on beans 14 via tapatalk 2
nicholi2789 said:
Yeah i already did that to sort out what Cpu I have as well.
And I have limit background processes enabled in developer options, limit processes 4 at most. Also where exactly are the maps settings? I have GPS off and Google maps frozen by Titanium backup (except when I use it occasionally). I also have every other unnecessary app frozen. Like the Samsung keyboard (use swiftkey) the stock email app, etc.
sent from my Galaxy S3 on beans 14 via tapatalk 2
Click to expand...
Click to collapse
Well it's under Location Settings but if you have Maps frozen until needed then it's an unnecessary step. You have done even more than I do or suggest haha I haven't frozen anything.
What would you say you're seeing as your average screen on time?
Sent from my SCH-I535 using xda app-developers app
Oh average screen on time is probably around 2.5 to 3 hours or so. Nothing crazy. I just wanna get my battery life back to before, where basically I could leave home fully charged and work a 10-12 hour day and come home with around 30% or so battery life. That's good enough for me.
So about these recommended voltages. I have the "fast" processor, should I just st the voltages for what he recommends? Are those recommended for bet battery life or best performance? I want to undervolt as much as possible without creating an unstable system or causing damage.
And can you help me understand the governor settings, my understanding is that "ondemand" activate both cores when needed, and interactivex is all the time? Is that roughly correct?
sent from my Galaxy S3 on beans 14 via tapatalk 2
Okay nevermind about the governers. I read quite a bit more about them over the last hour and feel that I understand them at least a little bit better. hehe. So much to learn!! It seems InteractiveX is the obvious choice for performance AND battery. I'm still kinda unsure about how much undervolting I can really get away with though. I love how smooth everything runs when I'm overclocked, but i'm not sure it's worth it in terms of battery life (unless I'm playing a game, or flying my AR Drone). It seems there is still an advantage to be had by setting it to the normal clock speed (1512mhz) and then undervolting by just a bit. Might be able to squeeze just a tad more battery life out. It's still nice to have these things within my realm of control though. I understand why people find this so addicting now!
nicholi2789 said:
Okay nevermind about the governers. I read quite a bit more about them over the last hour and feel that I understand them at least a little bit better. hehe. So much to learn!! It seems InteractiveX is the obvious choice for performance AND battery. I'm still kinda unsure about how much undervolting I can really get away with though. I love how smooth everything runs when I'm overclocked, but i'm not sure it's worth it in terms of battery life (unless I'm playing a game, or flying my AR Drone). It seems there is still an advantage to be had by setting it to the normal clock speed (1512mhz) and then undervolting by just a bit. Might be able to squeeze just a tad more battery life out. It's still nice to have these things within my realm of control though. I understand why people find this so addicting now!
Click to expand...
Click to collapse
Yea flashing kernels and roms is very addicting. Since you have a fast cpu, you can actually UV much lower than I can with my nominal cpu. You can set your voltages to match Imoseyon's table and you'll be fine or maybe try lower. I know from experience that I can't UV lower than 900 mv without my phone immediately locking up lol You can even hold off on setting voltages at boot if you want to get a feel for performance while UV'ed.
I can't really speak on OC vs. regular clock battery life, I keep mine OC'ed at 1.62 ghz so I'd notice minor drops in battery life compared to say 1.8 ghz. I don't even have much need for that since its fast enough to me as is. I haven't noticed too much of a hit on battery, I still range between 2.5-4 hours screen on pending if I'm on LTE or wifi during that charge.
Also, if you want to try your hand at really digging into kernel settings then you should also check out the the Team Kernelizer's thread for KT747 kernel. Personally, I use LeanKernel cuz it works really good for me so I applied some settings from there but not everything was applicable. This thread has some really knowledgeable people in it. Definitely give KT747 a look, or any other kernel for that matter, and see which ones you like the best.
Yeah i think i may have had a bad battery. I checked and I know my phone is deep sleeping, but since adjusting my voltages and settings last night it'd definetely improving. I have my voltages set to 25mv under what is recommended on that chart down to 1.4 the in the lower clock settings o have it exactly at the recommended settings. Seems to work okay. I have set on boot enabled but i also have the stock voltage settings on my SD Just in case of a boot loop.
sent from my Galaxy S3 on beans 14 via tapatalk 2
Does anyone have any suggestions? I really like this ROM and would prefer to keep it if possible but this battery life is terrible. Ant ideas on some measures I could take to try and improve it a bit?
I wiped cache partitions, davlik cache, and did factory reset before installing. I even do them twice just to be sure.
Would maybe wiping and re flashing the Rom help? I'm totally stumped here.
sent from my Galaxy S3 on beans 14 via tapatalk 2
I don't understand. I used cpu spy and i know phone is deep sleeping. I have set CPU to drop the clock speed when screens off.
Why the heck is it using so much battery? I'm dropping about 6-7% battery at idle. Somebody shed some insight.
sent from my Galaxy S3 on beans 14 via tapatalk 2