I want to share my setup with you guys for getting good battery life which lasts the day without making you compromise on the features. The primary things I've seen on the forums so far has a lot of involved setup and frankly by the time you get it perfect, you will flash a new ROM and have to re-do a lot of it and so on, overall it's not the worth the hassle.
This is usually what my days look like and I manage to last the entire day:
I keep wifi and GPS on always, regardless of whether I'm using it or not.
Get a fair bit of calls because I live away from family so they all call a lot (I have a massive family, so we are talking about 5-6 hrs of talking everyday).
I like to read news from news republic and I'm subscribed to a lot of stuff there so I go through like 2000+ articles in a given day.
XDA like every few hrs (damn ICS!).
Text messages are also flowing throughout the day with the woman being on the other side of the country and all (100+ a day?).
I have facebook on push (not an addict but active enough to mention)
My gmail, school and exchange are all on push for email so they I see a fair bit there
The setup is VERY easy to setup and replicate. It doesn't require you to lose out on features or use your phone at an anorexic level either. You don't need a task manager or watch your processor non-stop either.
So without further delay, here we go:
Pick a ROM
I'm using Seanster_GBaxe EX v1.5.1 from the T-Mobile section, you can find it here.
Get faux's kernel
The reason for this particular one is because it's given the best results when it comes to undervolting and overclocking without SOD. You can find the kernel here.
Get System Tuner
This is available on market. There are alternatives but for this post, I will be making all the references from this app.
Get the AGPS patch from crypted
This isn't for battery directly but it does get locks VERY fast and you waste less clock cycles getting the signal. Less clock cycles wasted, more battery saved. The patch is available here.
I personally use the v3.0 Google CWM Build (scroll down his post and you will see it)
Get the V6 SUPERCHARGER from zeppelinrox
This is available here. Why the beta one? It works fine.
Okay, at this point you can pretty much store these things together in a neat little folder on your SD card because it makes a perfect library. So let's get started, I'll assume that we are starting from scratch. The order for everything will be as follows:
Get into recovery and install your ROM
This I shouldn't have to explain, the instructions you can find on the ROM thread.
Install the kernel
Same with this, read the kernel thread.
Install the GPS patch
Same with this as well
Boot into ROM
Hmm.... hopefully you can manage this
Restore all your backups and apps, accounts and whatever else
Using titanium here is always good
Install System Tuner
Okay, let's get started. Although faux has done an amazing job with the kernel, there's always the personal bias that goes into making things so his balanced settings might not reflect yours (nor mine but you will be tweak even those soon).
Inside System Tuner, go to CPU:
The first you thing you should choose is whether you want to keep the 1.72 GHz OC or not. I kept it but if you want to get even more you can lower to stock 1.56 GHz or go even lower, your choice. Once you set the max, set the min to 384 MHz. Set it once and you don't need to do it again after. Leave the governer to ONDEMAND.
Now go to the Voltage tab:
Be careful here, this can crash you if you go too far. What we do here is globally undervolt, you can do that by hitting the -12.5 mV button over and over. I use -75 mV (press the button 6 times, for those bad at math). Keep in mind that all chips are NOT THE SAME!!! -75 mV might be too much for you or you might even be able to get to -100 mV, find out by doing it.
Now go back to the CPU tab and hit Boot Settings:
Hit Screen-off behavior:
Governor - No changes
Max frequency - 384 MHz (push doesn't lag at all still so don't worry about notifications)
Max frequency/in call - 384 MHz (yes, calls don't require full blast, they work fine even under 500 MHz)
Now go back
Hit Governors behavior:
Sampling rate - Unchanged (faux has it done perfect)
Up-threshold - 75 (what's this? This means that the CPU will scale to higher frequencies when the load is above 75%)
Power-save Bias - 70 (what's this? This means that the CPU will be "biased" towards lower frequencies when load is below 70%)
Setting the Power-save Bias higher than the Up-threshold is obviously stupid so make sure you did it right.
Now go back
At the bottom, there is a whole bunch of tweaks:
Hit Re-apply CPU settings, choose init.d script (you can choose boot too but init.d works 100% of the time)
Hit Boost app loading, choose init.d
Hit Clear cache, choose init.d
Now go back
Find the Startups section and disable whatever you don't want running at boot (this is purely a personal thing).
Install V6 script
His instructions are very good so I'll assume that you have gotten it installed. Once you have it running, choose option 9, the 1000 HP one. Reboot. Run script again, make sure you've got it at 100% supercharged. Done. Reboot just to be sure again.
All done! Now, I know that was lengthy but here's the awesome part. Make a titanium full backup of System Tuner and you NEVER have to do that again for ANY ROM as long as you use the same kernel!! The script is unfortunately the only thing you have to re-apply, probably that has a quick setup too but I'm new to it so I can't give you shortcuts on it.
Hope you have luck with this and it works for you. I promise nothing and if you break your phone please don't come crying to me because you chose to do this yourself. It works for me so I shared it!! Any suggestions are welcome of course.
Note: NO task manager required!! I will modify this for cm7 if needed.
nice job. thanks a lot!
You're using the rc6.1 correct?
Sent from my SAMSUNG-SGH-I727 using xda premium
Thanks for the detailed write-up.
Are you in an LTE market? A full day on LTE would be pretty awesome.
For the screen-off behavior, do you think one can get away with using the smartass governor instead?
I'm using the RC6, tad older I guess.
Sent from my SGH-T989 using Tapatalk
jedah said:
Thanks for the detailed write-up.
Are you in an LTE market? A full day on LTE would be pretty awesome.
For the screen-off behavior, do you think one can get away with using the smartass governor instead?
Click to expand...
Click to collapse
I'm not in LTE area :-(... Would be nice because that's why I got the phone but then I had to move so can't say anything about LTE.
As for smartass, what kernel are you using? Smartass works very similar to the modified ondemand settings that I set up so it wouldn't make a difference as far as I forsee.
Sent from my SGH-T989 using Tapatalk
I tried this, will post results later. Thanks for the great tutorial
If you could post screen shots of your CPU Spy that would be helpful! How well does your phone do on going into deep sleep? On average from what to what time does yours last you? I'm just skeptical about setting the screen off behavior cause that usually prevents the phone from going to Deep Sleep.
Sent from my SAMSUNG-SGH-I727 using xda premium
DANIEL133337 said:
If you could post screen shots of your CPU Spy that would be helpful! How well does your phone do on going into deep sleep? On average from what to what time does yours last you? I'm just skeptical about setting the screen off behavior cause that usually prevents the phone from going to Deep Sleep.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
You're right about the deep sleep, don't let it go into deep sleep. It lasts me 12 hours normally. I'll get you screenshots when I get a chance.
Sent from my SGH-T989 using Tapatalk
Mine goes into deep sleep with screen off behavior setup.
Sent from my SGH-T989 using XDA App
kr3w1337 said:
You're right about the deep sleep, don't let it go into deep sleep. It lasts me 12 hours normally. I'll get you screenshots when I get a chance.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Dont you think the phone waste alot more battery though when it doesn't go into deep sleep? I've also found that WiFi tends to create a nasty wake lock. My set up is Sky ICS Speed with Faux Clock 1.296 ghz max -384 mhz min. -37.5 u/v LTE on all day, extremely heavy usage. 12 hour battery life on average.
Sent from my SAMSUNG-SGH-I727 using xda premium
InstigatorX said:
Mine goes into deep sleep with screen off behavior setup.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Which kernel are you using?
kr3w1337 said:
Which kernel are you using?
Click to expand...
Click to collapse
Using faux kernel with foxstar rom.
Sent from my SGH-I727 using XDA App
DANIEL133337 said:
Dont you think the phone waste alot more battery though when it doesn't go into deep sleep? I've also found that WiFi tends to create a nasty wake lock. My set up is Sky ICS Speed with Faux Clock 1.296 ghz max -384 mhz min. -37.5 u/v LTE on all day, extremely heavy usage. 12 hour battery life on average.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
From what I've noticed with the faux kernel, it goes into deep sleep after some time on it's own, regardless of the screen-off behavior. I haven't opened up the source to check it out for a better explanation but that's something I doubt is worth exploring since the performance doesn't take any hit.
I haven't chosen to underclock to 1.2 but it should do better than the 12 hrs I get now if I did do that. I have a tendency to start GTA 3 and start playing whenever I get bored so that's why I went OC rather than under. For others looking strictly to use the phone with minimal gaming, this would be a good option. LTE isn't available in my area so I can't test with it but the WiFi radio uses just as much battery as the LTE, if not more I have a feeling.
Trying eugene's kernel from today to see if the lionheart governor does better than the current setup. I will know in a couple of days because every ROM flash needs a couple of charge cycles before it accurately shows battery status.
InstigatorX said:
Using faux kernel with foxstar rom.
Sent from my SGH-I727 using XDA App
Click to expand...
Click to collapse
Do you get any SOD? Everything working okay? Is the setup different than what I've got up there? Would like to know and try it out, can update the OP accordingly.
Just finished with eugene's kernel and the results were pretty disappointing. Looks like the second core is always kept on regardless, faux's kernel turns the second core offline until usage demands need it.
If anyone knows how to tweak eugene's to stop that from happening, do share.
kr3w1337 said:
Just finished with eugene's kernel and the results were pretty disappointing. Looks like the second core is always kept on regardless, faux's kernel turns the second core offline until usage demands need it.
If anyone knows how to tweak eugene's to stop that from happening, do share.
Click to expand...
Click to collapse
Can you clue me location of his latest ROM? Or is it somewhere in the Macnut thread on TMO side of the fence?
InstigatorX said:
Can you clue me location of his latest ROM? Or is it somewhere in the Macnut thread on TMO side of the fence?
Click to expand...
Click to collapse
Using darkside ROM at the moment with the faux kernel, had the Eugene kernel but I noticed that the second core is kept alive regardless of usage and that wasn't helping so I changed back to faux.
Sent from my SGH-T989 using Tapatalk
thanks for the awesome write up!
Did it last night, and lasted the day without a sweat! However, my min frequency wont stick? I have it set to stock frequency 1.5, using faux kernal, and my voltages arent as low as yours (im not a crazy user like you.. maybe an hour of talking a day, lots of texts and emails tho), but i cannot get my min frequency of 3xx to stay. Suggestions?
Thanks!
edit- running stockMod v1.0
im sorry, i have a hard time believing you talk for 6 hours and scroll thry 2000 pages of web and get a day of use. I myself could get about 1.5 days on battery strictly by staying home, connected to wifi all day and barely talking on the phone. i would like to see a screenshot of battery usage at the end of your day
Related
Could anyone help me out with this? I was using SetCPU, but I had heard about its constant processor use and "instability" (jumping down to 19MHz?). So I switched to OC Widget, but I'm having some issues with battery life. I had it set to 767MHz max/min when the screen was on and 245? max/min when the screen was off (I always had SetCPU on "performance"). However, I seem to lose battery like crazy with this for some reason! I switched to 245min/767max with the screen on, and I seem to lose battery much slower, but I will get a bit of lag sometimes (especially when typing something). Any assistance?
TheBiles said:
Could anyone help me out with this? I was using SetCPU, but I had heard about its constant processor use and "instability" (jumping down to 19MHz?). So I switched to OC Widget, but I'm having some issues with battery life. I had it set to 767MHz max/min when the screen was on and 245? max/min when the screen was off (I always had SetCPU on "performance"). However, I seem to lose battery like crazy with this for some reason! I switched to 245min/767max with the screen on, and I seem to lose battery much slower, but I will get a bit of lag sometimes (especially when typing something). Any assistance?
Click to expand...
Click to collapse
Via Flipz's website:
Overclock Widget vs SetCPU: Up until now toast and I have been pushing SetCPU because it allows us to create a custom file that tells it what clock speeds the rom is capable of running at which makes things nice and easy. However a couple of bugs have come up lately. First off is that it is constantly using 10-15% of the processor when it shouldn’t even be doing anything. That doesn’t sound like a lot but that’s pretty extreme. The second issue is that it doesn’t seem to be honoring the settings you pick. I could tell it that I want the minimum to be 245mhz but I would catch it at 19mhz. Or vice-versa I tell it that I want the max to be 650mhz and I catch it at 767mhz. With that said, toast took the time to program settings in to the kernel that will now allow you to pick “automatic” off of the device selection rather than custom. This may resolve the issue, so just keep an eye out for it if you use SetCPU. In OC Widget just go in to settings and click “Detect frequencies” to have it read them. If you have no preference then I’m personally saying to use Overclock Widget. It isn’t quite as user friendly as SetCPU, but it gets the job done right. Additionally as a 3rd reminder: make sure if you are running Fresh Toast that you DO use one of these applications, and if you are running Fresh Rom that DO NOT run one of these. Doing so can cause slowdowns.
Click to expand...
Click to collapse
drummingfool said:
Via Flipz's website:
Click to expand...
Click to collapse
Yes, I read that. That is where I got the information about SetCPU being funky.
I wish I could help, but I'm in a "noob-state-of-mind" right now...how the hell do I find OC Widget? I see it no where!
Thanks,
Tee Jay
I wish I could help, but I'm in a "noob-state-of-mind" right now...how the hell do I find OC Widget? I see it no where!
Thanks,
Tee Jay
Click to expand...
Click to collapse
"Overclock widget" in the Market.
-------------------------------------
Sent via the XDA Tapatalk App
Thank you, I might take a look!
I don't know how much you use your phone, but to say I use mine heavily is like calling Rosie a bit chunky. The settings I use are min:652.8 max:767 while on
min:19.2 max:247 while sleeping. I get roughly 6 hours batter life. But I literally use my internet for around 6 hours every day, plus calling, texting, email etc.
I'd imagine, if you use it less, you'd get much better battery life.
Edit: Oh! And I run MUCH more stably with OC widget than setcpu.
PaulB007 said:
If you haven't been able to get past the HTC screen at boot and keep bootlooping, YOU MUST INSTALL BC'S 1.5 GHZ KERNEL FIRST AND THEN FLASH THESE KERNELS OVER THAT I also just flashed it straight off of a new Mikshift install and I got the bootloop until I did this. So if you guys didn't do this, then install bc's kernel and flash Scary kernel again.
Scaryghoul, I have installed your 1.8 suv successfully on Mikshift. This is great news. I knew it would work, but for some reason I just cant get it running on aosp. I will keep you updated on IRC or through this thread, I haven't seen you on today yet.
Click to expand...
Click to collapse
Link to bcnice20's 1.5ghz kernel: http://forum.xda-developers.com/showthread.php?t=941728
If that doesn't work, try flashing over his 1.8ghz kernel(This is what worked for me, bcnice, if you want me to take down this link just let me know.) - http://thebcblends.com/shift/kernels/Sense-1.8ghz-bfq-test1.zip
Table of contents:
Intro
Features/what this includes
Why it's labeled unstable
Disclaimer
Latest kernels
Instructions for using swap
Governor exlainations
Governor strategies
Recommended apps
Locating cpu% Eaters && other negative items towards battery life
FAQ!
Changelog
Stable/safe voltage kernels
Notes
Source
Credits
Intro: I'm scaryghoul.
What this includes
Swap
BFQ I/o scheduler
Extreme undervolt
Overclocked & underclocked values
HW3D enabled
Sleepers disabled
Smartass governor
New Scary governor!
Tweaked conservative governor
and much more(All of bcnice20's kernel)
Why it's labeled unstable: So I don't get people poking me in the eyes with spoons if/when it freezes up. It actually works quite well, but since I heavily undervolted an undervolted kernel, it is bound to not be 100% stable(It is about 90% stable =P)
Disclaimer: What everyone else puts in kernel threads, about me not being responsible, ect.
Latest kernels
The voltages of the superUV will not work for everyone, if they don't work for you, then try the builds labeled stable
Recommended speeds 245-800mhz or 245-1ghz on scary governor && no setcpu profiles
Scarykernel 1.8 suv - http://dl.dropbox.com/u/15373824/Sense/ScarySense1.8Suv.zip
Scarykernel 1.8 stable undervolt - http://dl.dropbox.com/u/15373824/Sense/ScarySense1.8Stable.zip
Instructions for using swap
For a swapfile do something like this.
dd if=/dev/zero of=$Swapfile bs=1048576 count=$Size
Where $Swapfile is the location of the file you want, and $Size is the amount of mb for swap you want to use.
Then type
mkswap $Path
swapon $Path
Replacing $Path/$Size with your own values of course, so if I wanted 20mb of swap I'd execute the commands
dd if=/dev/zero of=/sdcard/swapfile bs=1048576 count=20
mkswap /sdcard/swapfile
swapon /sdcard/swapfile
Governor exlainations
Toasty makes one transition to the max speed and stays there(benchmarks only usually)
Batterysave! sits at the bottom and when the cpu load increases past the threshhold it scales up to the next speed and takes another load sample and keeps doing that(best on battery life/performance ratio)
Ondemand sits at the bottom and when the cpu load increases past the threshhold, it scales ot the max speed then takes another load sample and scales down accordingly
Powersave makes one transition to the bottom speed and stays there
Smartass(Quoted from another author http://www.ziggy471.com/2010/11/07/smartass-governor-info ) - "is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!"
Scary - A new governor I wrote based on conservative with some smartass features, it scales accordingly to conservatives laws. So it will start from the bottom, take a load sample, if it's above the upthreshold, ramp up only one speed at a time, and ramp down one at a time. It will automatically cap the off screen speeds to 245Mhz, and if your min freq is higher than 245mhz, it will reset the min to 120mhz while screen is off and restore it upon screen awakening, and still scale accordingly to conservatives laws. So it spends most of its time at lower frequencies. The goal of this is to get the best battery life with decent performance. It will give the same performance as conservative right now, it will get tweaked over time.
Governor strategies
Conservative - Upthreshold 85, downthreshold 60
Smartass - Sleep max 245760Hz, Ramp up at 384000Hz at a time, up threshold 90, downthreshold 60
Scary - Upthreshold 80, down threshold 45, sleep max 245760Hz, sleep min, 122880Hz
Recommended apps =)
Zdbox - Great toolbox app, just don't let it run in your notifications bar, it's a cpu eater
Setcpu/Nofrills - Apps that help manage your cpu/profiles/ect.(I don't use them but they're pretty okay)
Perfect system or Elixer widgets - Widgets that monitor battery, current, cpu%, cpu speed, and more(Great for battery guru's)
Adw ex - Smoothest/fasted/lightest ratio in a launcher I've seen so far, and least cpu intensive(for me that's a big thing so the cpu scales less)
Colorize widgets - Great widgets to replace the lpp ones for those converting to other launchers.
AppMonster(pro or free) - Great backup utility, automatically backs up all apps.(I like it better than TB)
GPS Status - Great application for finding satalites near you and helping get a quick lock.
Any go dev team app - Great dev team, all their apps are worth looking at.
Frequently asked questions
Question: My phone is boot looping/not booting on the released suv, what do I do?
Answer: Your phone cannot handle the super undervolted values, you will need to flash the stable undervolted kernel
Question: My phone is running slow on the batterysave or scary governors, what do I do?
Answer: Set your minimum speed higher, those governors spend a lot of time at the lowest values
Question: How do I flash this?
Answer: You probably shouldn't be flashing one of my kernels if you don't know how(Mine are unstable =P)
Question: I'm not getting the amazing battery life/benchmark scores that others are getting
Answer: Well, every device is different, so you may not be able to score as high as some others, but you should get close at least, and the battery completely depends on usage patterns
Question: My phone can't clock to 1.8ghz, or some of the other higher values but does fine on the lower ones
Answer: Every device is different and not all can handle the same speeds/voltages, you are probably better off staying away from the higher speeds, I enabled the speeds but hope that you all are mature enough to handle them
Locating cpu% eating applications.
When in ADB shell type the following
top |grep app
Then look for items with high amounts of cpu% while the phone is idle.
Changelog
v1.8 - Initial kernel release for sense
Safe voltage kernels
v1.8
Scarykernel 1.8 stable - http://dl.dropbox.com/u/15373824/Sense/ScarySense1.8Stable.zip
Notes:
No I can't take the overclock any higher, I think everyone who's had a chance to take a crack at this source has tried, and going any higher seizes up after a few seconds.
Here is the source code for this build. I'll try to maintain it, I have a lot of kernel sources, but this will always be the latest release code, unless I state otherwise.
https://github.com/Scaryghoul
Credits: bcnice20 - For 99.8% of his kernel source.
Dogejcr/Preludedrew - For helping me get my laptop setup for kernel compiling.
Testers - For flashing this even though it says unstable :-X
JoesephMother - For helping me unlock the new lower clock values && other kernel related matters =)
x99percent - I used his middle clock speeds between the 3xx->7xx values as a base(edited voltages) as well as used his smartass source.
I see nobody else has chimed in on this kernel yet.. I will install Mikshift tomorrow and report my findings.
Bummer, my phone is a wuss! I can't boot either one of these. Just sits on white screen. They look cool as hell though.
Sent from my PG06100 using Tapatalk
Yeah both versions don't work on mine.
If you haven't been able to get past the HTC screen at boot and keep bootlooping, YOU MUST INSTALL BC'S 1.5 GHZ KERNEL FIRST AND THEN FLASH THESE KERNELS OVER THAT I also just flashed it straight off of a new Mikshift install and I got the bootloop until I did this. So if you guys didn't do this, then install bc's kernel and flash Scary kernel again.
Scaryghoul, I have installed your 1.8 suv successfully on Mikshift. This is great news. I knew it would work, but for some reason I just cant get it running on aosp. I will keep you updated on IRC or through this thread, I haven't seen you on today yet.
Tried going strait from BC's still no go.
Sent from my PG06100 using Tapatalk
ozzie1p said:
Bummer, my phone is a wuss! I can't boot either one of these. Just sits on white screen. They look cool as hell though.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Did you flash over bcnice20's kernel?
PaulB007 said:
If you haven't been able to get past the HTC screen at boot and keep bootlooping, YOU MUST INSTALL BC'S 1.5 GHZ KERNEL FIRST AND THEN FLASH THESE KERNELS OVER THAT I also just flashed it straight off of a new Mikshift install and I got the bootloop until I did this. So if you guys didn't do this, then install bc's kernel and flash Scary kernel again.
Scaryghoul, I have installed your 1.8 suv successfully on Mikshift. This is great news. I knew it would work, but for some reason I just cant get it running on aosp. I will keep you updated on IRC or through this thread, I haven't seen you on today yet.
Click to expand...
Click to collapse
Thanks for clarifying that, I took down the links until we can get this working on several devices.
ozzie1p said:
Tried going strait from BC's still no go.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Did you try both of them over bcnice20's 1.5ghz? Not everyone can handle the suv one.
edit: Links back up! I need some testers to try the fix at the top.
Ya, I flashed right over the top of bc's. Ill try these new ones.
Sent from my PG06100 using Tapatalk
Scaryghoul are the reposted links any different than the old kernels you had up the first time? If not, the suv build would boot and run, but after using the phone after awhile for cpu intensive tasks it would lock up and require a battery pull. Im wondering if just a tiny bit more voltage would solve this problem.
On the stable build, it would run a minute or so and always lock up and require a battery pull..
PaulB007 said:
Scaryghoul are the reposted links any different than the old kernels you had up the first time? If not, the suv build would boot and run, but after using the phone after awhile for cpu intensive tasks it would lock up and require a battery pull. Im wondering if just a tiny bit more voltage would solve this problem.
On the stable build, it would run a minute or so and always lock up and require a battery pull..
Click to expand...
Click to collapse
Same links....and I see. If the stable build has the same issue as the suv, then it's not the voltage >.<
Oops. Thought they were new. At least I got the flash bug scratched. Flashed over both bc 1.5 and 1.8, no go.
Sent from my PG06100 using Tapatalk
Scaryghoul said:
Same links....and I see. If the stable build has the same issue as the suv, then it's not the voltage >.<
Click to expand...
Click to collapse
Whats the suspected culprit?
ozzie1p said:
Oops. Thought they were new. At least I got the flash bug scratched. Flashed over both bc 1.5 and 1.8, no go.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
PaulB007 said:
Whats the suspected culprit?
Click to expand...
Click to collapse
I don't know so much for the freezes, but I believe that the booting has to do with me using my old voltages, and sense handling things differently than aosp >.<
I'll redo the voltage table later.
Just Wondering?
When Source Code is released will you make a suv kernel for the Gingerbread Update i loved it on froyo and mikshift and gave great battery life.
notsointeresting said:
Just Wondering?
When Source Code is released will you make a suv kernel for the Gingerbread Update i loved it on froyo and mikshift and gave great battery life.
Click to expand...
Click to collapse
The source code isn't actually the issue right now. Lack of motivation mainly, I would consider it more if I hadn't deleted my toolchain from my dev station, can't be bothered to get another one setup right now.
When I get motivated again I will, I honestly don't use my phone much anymore(maybe pick it up once or twice a day).
Scaryghoul said:
The source code isn't actually the issue right now. Lack of motivation mainly, I would consider it more if I hadn't deleted my toolchain from my dev station, can't be bothered to get another one setup right now.
When I get motivated again I will, I honestly don't use my phone much anymore(maybe pick it up once or twice a day).
Click to expand...
Click to collapse
Ah ok that sucks was really hoping for it but I understand thanks for the fast reply
Scaryghoul said:
The source code isn't actually the issue right now. Lack of motivation mainly, I would consider it more if I hadn't deleted my toolchain from my dev station, can't be bothered to get another one setup right now.
When I get motivated again I will, I honestly don't use my phone much anymore(maybe pick it up once or twice a day).
Click to expand...
Click to collapse
The ndk from google's web site has the toolchains needed to build gb kernel in it. The dl isn't terribly huge.
Sent from my PG06100 using XDA Premium App
Does anyone know the ideal settings for undervolting the sensation without causing any problems?
StuartTheFish said:
Does anyone know the ideal settings for undervolting the sensation without causing any problems?
Click to expand...
Click to collapse
Not really. As faux say not all chips are created equal. I've seen up to an amazing -150 but my phone can only handle -50 stable and -75 sometimes with a reboot or two.
Sent from my HTC Sensation 4g using xda premium
Mine handles -100 just fine, but yeah,others can only go -50. Just use system tuner and hit the -12.5 till your phone freezes, then when it restarts go one less and see if it's stable. That's what I did.
Sent from my HTC Sensation 4G using XDA App
I'd also suggest keeping the Max Clock at a consistent value while you play. E.g. UV -100mV might work well at one Mhz then fail at a higher value.
Mine seemed to work consistently at about -100mV, then again I tend to UC unless I'm running CF-Bench or something
Should I only need to concentrate on the lowest and highest clock speeds it's been set to use? Or will I have to undervolt all other frequencies between the two? Not sure if it increments on usage, or simply toggles between the min and max.
If it does increment, how can I test it's stability on the other frequencies if I can't tell what frequency it was using at the time?
Just tapped the -12.5 button a few times, and it reduced all of the sliders. It's -100 now with no apparent issues as of yet.
May I ask the reason for undervolting?
masonic1032 said:
May I ask the reason for undervolting?
Click to expand...
Click to collapse
Mainly to save battery. Altho I have found that it is quite negligible. It may also help with phone heat
masondoctorjt said:
Mine handles -100 just fine, but yeah,others can only go -50. Just use system tuner and hit the -12.5 till your phone freezes, then when it restarts go one less and see if it's stable. That's what I did.
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
I run faux latest version 2.7 beta and I see his scripts to undervolt and the lowest I see it too go is -75 how are you able to go lower to -100.... ???
I think it varies from phone to phone, mine too seems happy enough -100.
StuartTheFish said:
I think it varies from phone to phone, mine too seems happy enough -100.
Click to expand...
Click to collapse
Soooooo how do I undervolt below -75 that's where I am. Now
rawdawgroy said:
Soooooo how do I undervolt below -75 that's where I am. Now
Click to expand...
Click to collapse
If the phone hangs/boots below that level then with the Phone/Kernel/... that's the limit.
I created a GScript script (well a sh script) to U/V after a reboot. I didn't want it to do it automatically as you'd end up in a boot loop. Just hassle to fix. The reason for the GScript was to remove it from the various CPU controllers I'd tried, I ended up just using the CM7 one to control the CPU.
Faux has the command to do it globally (across all frequencies) or individual frequencies. TBH I never bothered with individual ones.
The bottom line is, do what you and your phone are happy with.
EDIT: meant to add you can check the actual value manually. I know the Faux one (same post as the scripts above) but if you are using a different kernel it might be in a different place.
This supposed lag fix has blown up over at r/android. I tried it on my G2x and it for sure booted up the launcher faster on startup. Check it out!
http://forum.xda-developers.com/showthread.php?t=1987032
Sent from my LG-P999 using Tapatalk 2
Thanks for sharing, looks pretty promising. Going to test it out for a bit .
I was wondering if this matters whether CM7 or cm10?
Thanks for sharing this. Installed the apk and it seems a little quicker with things, but that might just be in my head.
I'm not sure if it ****s on your battery life or not, seems like my battery just demolished itself, but now that I think about it I got 6 hours on 52%
Thus why I don't have it
Sent from my LG-P999 using xda app-developers app
I tried it for couple hours and it doesn't seem to work for me.
Sent from my LG-P999 using xda app-developers app
Everything seems pretty good for me. I'll post back in a couple days to say if it's held up.
Sent from my LG-P999 using xda app-developers app
I've installed it last night. My usual morning lag that I experience wasn't there so I believe there is some merit to what this mod is supposed to provide. I'll be tracking the battery life, as that's more important to me than a reboot once a day.
Yes I can also confirm that this app works. Even makes one of my slowest apps (amazon appstore) open much faster. Everything is a bit quicker.
My only concern is battery life, which I am going to be testing over the weekend. Loving the mod so far though.
I can verify this works well use to take close to a minut to load my xda ap lol. Not so any more. Also switching from app drawer to home screen, no lag. I used v6 supercharger for a while and i think that for now im just gonna use this. My phome is much more responsive than it use to be, especially when opening my settings menu. I will be paying attention to battery as well. Thanks for your work.
Edit. My cpu clock speed magically set it self to 1552. Dont ask me how that happened cuz i dont know. Now normally at this speed my phone would freeze. How do i know this? Cus its happened on more than one occasion. I dont overclock anymore because of it. I ran this app all day with no adverse effects. I cant say one way or another if this app works because i dont know when my phone was set to overclock. With the controversy surrounding this.... Im glad i didnt pay 1.50 for it or id feel like a really dumb***
Sent from my LG-P999 using xda app-developers app
RC calls BS
https://plus.google.com/115049428938715274412/posts/GWr72W9zmY2
From his post:
"So to be clear... IMNSHO, the recent entropy pool fad is bull****. The only users of /dev/random are libcrypto (used for cryptographic operations like SSL connections, ssh key generation, and so on), wpa_supplicant/hostapd (to generate WEP/WPA keys while in AP mode), and the libraries that generate random partition IDs when you do an ext2/3/4 format. None of those 3 users are in the path of app execution, so feeding random from urandom does nothing except make random... well... less random
The only conceivable reason some devices may feel faster is because by constantly polling the PRNG, it keeps the device's I/O in constant use (which in turn, depending on device, will make the CPU stick to higher clock frequencies to keep up and/or ramp up the IO scheduler)."
Yes it's bullish**. The whole explanation for this mod doesn't make sense and I just can't figure out how this would help at all. As RC said excellently, it would simply prevent I/O functions to go to sleep and keep your CPU higher. TL;DR : Raise your CPU clocks, change your I/O scheduler and you'll get better performances.
One more thing... I dont know when my phone was set to overclock but here are some interesting screen shots for you.
This is a 1500Mah stock battery. The original batter. I got with the phone over a year ago btw.
Something to cbew on i think. My phone has never run this well. Wtf?
Sent from my LG-P999 using xda app-developers app
Apparently everyone in that thread still thinks it works... I don't think they read Ricardo's post. Someone should keep posting it lol.
jryan388 said:
RC calls BS
https://plus.google.com/115049428938715274412/posts/GWr72W9zmY2
From his post:
"So to be clear... IMNSHO, the recent entropy pool fad is bull****. The only users of /dev/random are libcrypto (used for cryptographic operations like SSL connections, ssh key generation, and so on), wpa_supplicant/hostapd (to generate WEP/WPA keys while in AP mode), and the libraries that generate random partition IDs when you do an ext2/3/4 format. None of those 3 users are in the path of app execution, so feeding random from urandom does nothing except make random... well... less random
The only conceivable reason some devices may feel faster is because by constantly polling the PRNG, it keeps the device's I/O in constant use (which in turn, depending on device, will make the CPU stick to higher clock frequencies to keep up and/or ramp up the IO scheduler)."
Click to expand...
Click to collapse
Isn't faster performance accomplished by keeping the I/O constantly running and the CPU at higher clock speed than it would otherwise be?
Call me crazy but using this made my phone constantly stay in deep sleep! I've never, ever seen my phone stay asleep for so long and so consistently before.
buru898 said:
Call me crazy but using this made my phone constantly stay in deep sleep! I've never, ever seen my phone stay asleep for so long and so consistently before.
Click to expand...
Click to collapse
Does it ever wake up ?
Sent from my LG-P999 using xda app-developers app
New2my8125 said:
My only concern is battery life, which I am going to be testing over the weekend. Loving the mod so far though.
Click to expand...
Click to collapse
I've been using this mod for a little over a week. While RC might be right about what this mod really is doing, my phone hasn't been snappier. As for battery life, I've lost about 10% more battery a day using this. I've got the Anker 2800mWh battery, and at the end of the day I'm usually sitting around 55-60% battery remaining. On hard use days I'd be around 30% battery remaining. Overall I'm still getting a full days use out of the phone.
If someone could suggest what scheduler I should use (instead of this mod) then I'd gladly try RC's suggestion and see if he is right as well.
Hello, my main purpose is to save battery. I want let the CPU act normally (stock) while the screen is ON, and i want to undervolt/underclock the CPU, while the screen is OFF and when i am on a phone call. I do not care about overclocking.
Is there any CPU tuner (or even SetCPU app) guide for nexus 5?
I really want to know the correct frequences to setup in order to avoid problems
I use stock ROM and stock kernel.
Thank you in advance.:good:
There are no correct frequencies. Just play and find what's good. Remember though, the more you underclock, the longer it takes to undertake certain tasks so it can be a false economy.
My advice would be undervolt always and under clock never.
You cannot undervolt stock kernel
Read section 4.3 in my signature
Sent from my Nexus 5 using Tapatalk
rootSU said:
There are no correct frequencies. Just play and find what's good. Remember though, the more you underclock, the longer it takes to undertake certain tasks so it can be a false economy.
My advice would be undervolt always and under clock never.
You cannot undervolt stock kernel
Read section 4.3 in my signature
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you for answering and thank you for the information! I have 1 question in order to clear some things out. What causes battery economy Underclock or undervolt?
Dmoustakas said:
Thank you for answering and thank you for the information! I have 1 question in order to clear some things out. What causes battery economy Underclock or undervolt?
Click to expand...
Click to collapse
Both have potential but really the best thing is deep sleep.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Both have potential but really the best thing is deep sleep.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I already use greenify so i think it is the same thing with deep sleep. One last question, could underclock be false economy in my situations since i want it to work only when screen is off and only on active phone calls?
Dmoustakas said:
I already use greenify so i think it is the same thing with deep sleep. One last question, could underclock be false economy in my situations since i want it to work only when screen is off and only on active phone calls?
Click to expand...
Click to collapse
Screen off does not = deep sleep. In my opinion, it's best to let it do what it wants, however my kernel sets maxscreen off at 1100 MHz
Its all about clock cycles. The Stock kernel allows the CPU to run at approximately 23,000 MHz. Each MHz is a "Clock cycle" per second. So each second, you have 23,000 clock cycles. Now lets say (this is not a real value, but just humour me) that an e-mail Push takes 23,000 clock cycles. You can receive an email in 1 second. With me so far? So what if you underclock to 12,500MHz? It takes twice as long to push that same email to your phone. So now you have to work out, is 12,500MHz using more or less than half the power that 23,000MHz uses? If it is less than half, you *MAY* save some battery, but if it uses more than half, its a false economy because 2 seconds at 12,500 uses more power than 1 second at 23,000.
Does that make sense?
I've kept this basic for illustration purposes, so anyone reading, please don't make technical corrections, this is not meant to be exact or accurate
rootSU said:
Screen off does not = deep sleep. In my opinion, it's best to let it do what it wants, however my kernel sets maxscreen off at 1100 MHz
Its all about clock cycles. The Stock kernel allows the CPU to run at approximately 23,000 MHz. Each MHz is a "Clock cycle" per second. So each second, you have 23,000 clock cycles. Now lets say (this is not a real value, but just humour me) that an e-mail Push takes 23,000 clock cycles. You can receive an email in 1 second. With me so far? So what if you underclock to 12,500MHz? It takes twice as long to push that same email to your phone. So now you have to work out, is 12,500MHz using more or less than half the power that 23,000MHz uses? If it is less than half, you *MAY* save some battery, but if it uses more than half, its a false economy because 2 seconds at 12,500 uses more power than 1 second at 23,000.
Does that make sense?
I've kept this basic for illustration purposes, so anyone reading, please don't make technical corrections, this is not meant to be exact or accurate
Click to expand...
Click to collapse
Great explanation, clearly logical thoughts. You really covered all my questions. Thank you very much! I think i am going to search for a kernel to tinker with undervolting!
Cheers and thanks again!
Dmoustakas said:
Great explanation, clearly logical thoughts. You really covered all my questions. Thank you very much! I think i am going to search for a kernel to tinker with undervolting!
Cheers and thanks again!
Click to expand...
Click to collapse
No probs. Take a nandroid backup before tinkering
Cpu tuner do not turn Data off
Hi all
I re install Cpu Tuner on my Nexus 5 with Cataclysm 5.1
kernel elementalX
but Cpu tuner has the same behavior when a was root but stock Lollipop 5.1
It work but do not turn off or on the Data
profiles works, Wifi, Synchronisation Ok but not for Data
I'll try on 3G or 4G... I re install it same behavior :L
thanks.
PS: I used it with my Galaxy Nexus with no probleme... and I use a new conf for the Nexus5.