I want to make sure I'm not trippin', I've searched all thru the dev forum, and I don't see a non overclocked kernel. everyone complains about battery life but they are using a kernel that wasn't geared for battery life. oc kernels are for performance and bragging rights. we need a stock kernel with uv and ram optimization along with battery optimization mods
Sent from my Desire HD using XDA App
boimarc89 said:
I want to make sure I'm not trippin', I've searched all thru the dev forum, and I don't see a non overclocked kernel. everyone complains about battery life but they are using a kernel that wasn't geared for battery life. oc kernels are for performance and bragging rights. we need a stock kernel with uv and ram optimization along with battery optimization mods
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Why not just not overclock? Also, the kernel that comes in Inspired Ace isn't overclockable.
There are many battery saving options! If you have the Leedroid kernel, in setcpu you have the option of running your proccesor at Powersave, performance,smartass and so on...this is also in a few other kernels but I am not sure which ones at the moment.
And if you are really hyped up on saving battery, shutoff haptic feedback, turn of data when you are not using it, lower screen brightness, Use a task killer to kill stray apps(if you were playing angry birds kill it afterwards).
These are a few things you can do that will increase your battery life significantly...
With an overclock capable kernel, you can underclock. I run mine at 921 MHz and don't notice any performance hit. I've tweaked the undervolt to as low as I can get away with. I get pretty awesome battery life that way.
Before you ask, I'm using a kernel I compiled myself from HTC's latest linux source for the Inspire. It's essentially stock with only the addition of the frequency table and hooks for OC/UV.
Gene Poole said:
With an overclock capable kernel, you can underclock. I run mine at 921 MHz and don't notice any performance hit. I've tweaked the undervolt to as low as I can get away with. I get pretty awesome battery life that way.
Before you ask, I'm using a kernel I compiled myself from HTC's latest linux source for the Inspire. It's essentially stock with only the addition of the frequency table and hooks for OC/UV.
Click to expand...
Click to collapse
This.
Simply underclocking will solve your problems. I prefer to run @1.4 Ghz. I have everything optimized for speed & efficiency and still don't lose in battery performance.
Running CM7 with LordMod UE 2.6 kernel and smartass CPU governor, I can set the max speed to 768mhz with very little performance hit noticed. I might just keep it that way, haven't decided yet. Scrolling is still smooth, Angry Birds is still smooth. The cool thing about running max 768mhz with the pinky undervolt script is the CPU voltage never goes above 900mv.
I'm running CM7 with nightly 91 and on my Vibrant, they made a kernel that was stock uv no oc and u could use it all day, literally....
Sent from my Desire HD using XDA App
Related
Can you experienced doods, help out a noob? I have recently rooted my phone (after MUCH research and reading) and just installed Set CPU app. I have been reading about the different settings for Set CPU, and it appears to be device specific, so I wanted to know if any can suggest some stable and useful settings and profiles I can use.
My goal would be to extend battery life and increase erformance while the phone is being used. I kinda guess this is most peoples reason for using this app. Slow the CPU down while the screen is off, and increase it a bit when the screen is on. I am not totally sure why you adjust it while it is charging. And wold this fi into the screen is off profile.
Ok enough rambling, and thanks for any assistance!
Forget SETCPU. Voltage Control is the way to go. For battery life, I would underclock to 100-800mhz and have -100mv all through the range. For performance, 100-1400 mhz (1.5 & 1.6 ghz are heavily overvolted) and have -100mv from 100-1000 mhz and -75 for 1100-1400. Leave the governers and io schedulers where they are.
Sent from my Droid Charge running GummyFroyo 1.9.1
kvswim said:
Forget SETCPU. Voltage Control is the way to go. For battery life, I would underclock to 100-800mhz and have -100mv all through the range. For performance, 100-1400 mhz (1.5 & 1.6 ghz are heavily overvolted) and have -100mv from 100-1000 mhz and -75 for 1100-1400. Leave the governers and io schedulers where they are.
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
Using the voltage control within SetCPU or a voltage control app?
Thanks
Edit: after installing set CPU my phone seems to be running slower than usual. So, I ran a quadrant benchmark and it is coming up with much lower scores than it did before. Is there any way to set it back to the original cpu speeds with out deleting the app?
Delete setcpu and get voltage control from the market.
Sent from my SCH-I510 using Tapatalk
sneakysolidbake said:
Delete setcpu and get voltage control from the market.
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
+1 for this
running Imoseyon's OC/UV test kernel:
100-1000mhz uv -75
1200-1400 uv -50
IO: deadline and Governor: conservative
smooth as butter and fast when it needs to be, getting a little over 2200 in quadrant
anoninja118 said:
+1 for this
running Imoseyon's OC/UV test kernel:
100-1000mhz uv -75
1200-1400 uv -50
IO: deadline and Governor: conservative
smooth as butter and fast when it needs to be, getting a little over 2200 in quadrant
Click to expand...
Click to collapse
Thanks, can I use this with imnuts OTB kernal?
gdubya34 said:
Thanks, can I use this with imnuts OTB kernal?
Click to expand...
Click to collapse
you should be able to yeah.. try a different set of settings every day to find whats the most fast and stable on your phone, what works on mine may not necessarily work on yours or someone elses
blazing through on my VZ Droid Charge 4G
anoninja118 said:
+1 for this
running Imoseyon's OC/UV test kernel:
100-1000mhz uv -75
1200-1400 uv -50
IO: deadline and Governor: conservative
smooth as butter and fast when it needs to be, getting a little over 2200 in quadrant
Click to expand...
Click to collapse
Tried those settings and my phone froze a few times so I upped the voltage to get it to work for me. This is my first time overclocking a phone. Do any of these settings look strange using voltage control?
100-400mhz uv-75
800-1000mhz uv-50
1200-1300mhz uv-25
I haven't froze yet, although I noticed my battery drains a little faster then normal (that was expected).
hmmm.... The GummyCharged GBE 1.9RC1 8/13/11 kernel is not incompatible with the Voltage control free app.
Error message "Unsupported kernel detected. The kernel your device is running is incompatible with Voltage control."
praveen1789 said:
hmmm.... The GummyCharged GBE 1.9RC1 8/13/11 kernel is not incompatible with the Voltage control free app.
Error message "Unsupported kernel detected. The kernel your device is running is incompatible with Voltage control."
Click to expand...
Click to collapse
GummyCharge GBE is gingerbread which means stock kernel, no voodoo and therefore no changing of voltage settings
blazing through on my VZ Droid Charge 4G
Gotcha! Thanks to that.
Now I have a crazy question below. (trust me there are even more questions all over my mind now)
When they say "ROM", I'm assuming that its collective of Kernel, all the apps and the radio.... Can't we just downgrade the kernel of "GummyCharge GBE" Rom?
anoninja118 said:
+1 for this
running Imoseyon's OC/UV test kernel:
100-1000mhz uv -75
1200-1400 uv -50
IO: deadline and Governor: conservative
smooth as butter and fast when it needs to be, getting a little over 2200 in quadrant
Click to expand...
Click to collapse
These gave me a reboot watching netflix on wifi. Will try -25 @ 1300 and see what happens. Thanks for the post though. Its a great starting place for me.
running humble 1.51
Khanusma said:
These gave me a reboot watching netflix on wifi. Will try -25 @ 1300 and see what happens. Thanks for the post though. Its a great starting place for me.
running humble 1.51
Click to expand...
Click to collapse
Yeah those are kinda high 'performance' settings, not all phones like being overclocked or undervolted much less both lol.. Start with it just overclocked for a day or two and see how it runs, however there's gonna be some serious battery drain obviously. Then move on to undervolting slowly like maybe -25 across the board and leave 1400 alone for another day or two... just experiment like this until you have the right balance of speed, stability and battery life. As a matter of fact I toned mine down a bit afterwards and it worked nice:
Overclocked to 1.2ghz (1200mhz),
took out 600mhz frequency and set 100 to -75, then 200-800 at -50, 1000 and 1200 at -25
or if you want battery life and don't mind sacrificing a little performance you can underclock to 800mhz and set all to maybe -75... its a lot of testing to find what works for your phone, if it reboots freezes or lags too much its either overclocked too much or undervolted too much
edit: I also use the free voltage control app from the market, it lets you set min. and max. clock speeds as well as voltage so thats all I need lol
blazing through on my VZ Droid Charge 4G
praveen1789 said:
Gotcha! Thanks to that.
Now I have a crazy question below. (trust me there are even more questions all over my mind now)
When they say "ROM", I'm assuming that its collective of Kernel, all the apps and the radio.... Can't we just downgrade the kernel of "GummyCharge GBE" Rom?
Click to expand...
Click to collapse
Roms are not always all inclusive with a kernel and whatnot.. Most are custom apps, themes, and build/framework remakes to operate on top of the stock roms and will use stock radio and kernel to operate unless a custom radio/kernel is flashed. While most radios and apps will work well with different roms, kernels (being basically the 'engine' for the android OS i believe) are dependant on baseband and will not work by switching them around or flashing one over the other. This is the way I understand it to be anyway, I just know kernels are not compatible between 2.2 and 2.3
blazing through on my VZ Droid Charge 4G
anoninja118 said:
Roms are not always all inclusive with a kernel and whatnot.. Most are custom apps, themes, and build/framework remakes to operate on top of the stock roms and will use stock radio and kernel to operate unless a custom radio/kernel is flashed. While most radios and apps will work well with different roms, kernels (being basically the 'engine' for the android OS i believe) are dependant on baseband and will not work by switching them around or flashing one over the other. This is the way I understand it to be anyway, I just know kernels are not compatible between 2.2 and 2.3
blazing through on my VZ Droid Charge 4G
Click to expand...
Click to collapse
Makes sense. I'm sure the apps and radio are dependent on the kernel as it is the core. (like an Operating system that provides the platform for applications to work.)
I'm sure the developers thoroughly test these combinations before releasing any ROM, .
However I want to have some fun updating the kernel on the GC GBE 1.9 that I currently have on my charge with couple other kernels out there....
Will see if I create some magic
praveen1789 said:
Makes sense. I'm sure the apps and radio are dependent on the kernel as it is the core. (like an Operating system that provides the platform for applications to work.)
I'm sure the developers thoroughly test these combinations before releasing any ROM, .
However I want to have some fun updating the kernel on the GC GBE 1.9 that I currently have on my charge with couple other kernels out there....
Will see if I create some magic
Click to expand...
Click to collapse
don't use froyo kernels with GB (as of right now there's only one custom GB kernel, navenedrobs nameless ext4 one), it will just lead to a soft bricked phone... i could be wrong but i think imnuts and imoseyon from team gummy are working on some GB kernel awesomeness
blazing through on my VZ Droid Charge 4G
What about the noop, fifo, bfq, vr options? What do these mean?
Sent from my gummycharged SCH-I510 using XDA Premium App
gdubya34 said:
What about the noop, fifo, bfq, vr options? What do these mean?
Sent from my gummycharged SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
Don't touch them. They will either make your phone crawl or have FCs. It hasn't been implemented in the kernel yet.
Sent from my Droid Charge running GummyFroyo 1.9.1
kvswim said:
Don't touch them. They will either make your phone crawl or have FCs. It hasn't been implemented in the kernel yet.
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
Oh crap, I am not sure what one it was on when I installed it. I think I changed it by accident. right now it is on the vr setting.
Are there any setting s to avoid when messing with the voltage control, and if I delete the app does go back to the default settings?
gdubya34 said:
Oh crap, I am not sure what one it was on when I installed it. I think I changed it by accident. right now it is on the vr setting.
Are there any setting s to avoid when messing with the voltage control, and if I delete the app does go back to the default settings?
Click to expand...
Click to collapse
To avoid: IO schedulers, overvolting (only done in Extreme), and going above 1400 mhz, as 1500 & 1600 are HEAVILY overvolted. Toasted processors=bad magic.
However, you can switch the governers from conservative to performance, but its kind of useless.
If you delete the app it will NOT go back to default...I think. The default io scheduler for imoseyon's kernel is deadline, I forgot what PBJ's is. If you switched it and its still working, don't worry about it.
Sent from my Droid Charge running GummyFroyo 1.9.1
I just purchased SETCPU from the market. I know its free here but from what I've read it is well worth 2 bucks (or a lot more).
I'm running bamf 1.0,9 cubed and I verified in setcpu it is set to low of 368 and high of 1 ghz.
I am using stock kernel but thinking of trying adynaline's new kernel.
Anyway should I set a custom profile? Any suggestions on settings? I'm more interested in avoiding screen freeze than speeding up anything.
Profiles are not needed.
They're just usefull if you want to underclock at a certain battery level or temperature to save battery or cool down the device in my opinion.
Sent from my LT15i using XDA Premium App
I just overclocked to 1.28 we'll see how it goes....
recDNA said:
I just overclocked to 1.28 we'll see how it goes....
Click to expand...
Click to collapse
should be fine.
i had some profiles of:
screen on - min was as low as it could go, max = 1.4ghz -ondemand
screen off - min was as low as it could go, maz = 5xx mhz - batt saver or conservative
battery at 50%, put max at 1ghz- on demand
battery at 15% max was at 7xx mhz -batt saver/conservative
temp>115 max was 7xx mhz-batt saver
this yeilded pretty good battery life. i am a heavy data user in a 4g area and on a sense ROM i could easily get 12 hours. pushed it over a day with me trying to get the best battery life possible.
Sounds good. I'm also a heavy user.
Profiles aren't needed with a lot of kernels. Some have built in profiles and in others some governors include profiles such as smartass and interactivex.
The only thing I really use it for is if I overclock, which I rarely ever do, and to change the governor.
Sent from my ADR6400L using XDA App
I use SetCPU with imo's latest kernel and I never let it go above the 1.59GHz mark, but that is where I usually put it when charging via AC.
bamf forever already has the ability to set cpu speeds, its in the bamf settings
It says in the op of bamf kernel thread that bamf setting is unable to retain kernel settings so use setcpu.
As some of you might know, the HTC Desire S overclocks very well.
I've done alot of research, and I've found no difference between the MSM8255 chipset our Desire S runs on, and the higher clocked MSM8255T (which runs at 1.4-1.5GHz).
I've created this topic to gather some information on what method you use to over/underclock (built-in, custom, app etc), how high you've clocked your device, what governor you're using, and what temperature you're at.
Right now my Desire S runs at 1.4GHz, incredibly stable, ive stress tested for hours (so far) without any errors, maxing at bout 36,5c temp.
My current method is SetCPU, using 245-1401 interactive scaling.
Please post your findings / preferences / device settings.
I never overclocked my Desire S. Ok sometimes he can be slow, but I don't like overclocking a CPU of a smartphone... Maybe it's because I'm scared to blow him up or something, dunno. I just leave it like it was, in my eyes, the best thing you can do
I'm using OC/UV Beater2 which came in Endymion ROM. My DS is overclocked to 1,2 Ghz and it is very stable, never freezes
But I have a question, what is default undervolt settings? Because I think when I set for example -25 undervolt settings, that will come default setting after a while..
So I dont know what is default voltage... So if someone could tell what is though 122Mhz voltage, I would be happy!
1ghz ondemand. Sometimes 245/768mhz and in games 1.2ghz
Raaert said:
As some of you might know, the HTC Desire S overclocks very well.
I've done alot of research, and I've found no difference between the MSM8255 chipset our Desire S runs on, and the higher clocked MSM8255T (which runs at 1.4-1.5GHz).
I've created this topic to gather some information on what method you use to over/underclock (built-in, custom, app etc), how high you've clocked your device, what governor you're using, and what temperature you're at.
Right now my Desire S runs at 1.4GHz, incredibly stable, ive stress tested for hours (so far) without any errors, maxing at bout 36,5c temp.
My current method is SetCPU, using 245-1401 interactive scaling.
Please post your findings / preferences / device settings.
Click to expand...
Click to collapse
Yeah, I've done some research too, and cannot find any differences about the 8255T vs 8255.
Ours are highly capable of going to 1.8Ghz stable.
What are the key differences?
-------------------------------
Sent from my HTC Desire S
How severely does overclocking affect battery life
Sent from my Desire S using xda premium
245-1200MHz, interactive governor, using CM7 built in performance control. Phone is very stable, never had any problems because of OC. The highest temp i saw was +34C.
Sent from my HTC Desire S using xda premium
Same CPU 'issue' with the Arc and Arc S ->
http://forum.xda-developers.com/showthread.php?t=1396071
That pretty much sums it up, why the Desire S (some - mine?) overclocks so well..
Same thing they do with desktop CPUs.
Like my old C2D E6600 2.4GHz OCs to 3.4GHz without adding volts and running only on air cooling, 48c after 10-12hrs of stress testing with SLI nvidia cards in the case.
All in all, the MSM8255 and MSM8255T could easily be the exact same chipset/CPU, just at different speeds, some tested more extensively than others.
Has anyone tried running speeds above 1.5GHz+ successfully? 1.5GHz should also be doable, as the HTC Flyer has the MSM8255T and runs at 1.5GHz.
Raaert said:
Same CPU 'issue' with the Arc and Arc S ->
http://forum.xda-developers.com/showthread.php?t=1396071
That pretty much sums it up, why the Desire S (some - mine?) overclocks so well..
Same thing they do with desktop CPUs.
Like my old C2D E6600 2.4GHz OCs to 3.4GHz without adding volts and running only on air cooling, 48c after 10-12hrs of stress testing with SLI nvidia cards in the case.
All in all, the MSM8255 and MSM8255T could easily be the exact same chipset/CPU, just at different speeds, some tested more extensively than others.
Has anyone tried running speeds above 1.5GHz+ successfully? 1.5GHz should also be doable, as the HTC Flyer has the MSM8255T and runs at 1.5GHz.
Click to expand...
Click to collapse
Ah!
Many thanks for that mate!
Been looking and couldn't find much info too!
Yeah, i guess the T stands for being tested more.
My Desire OC's very well. I can go to 1.8Ghz stable for very long.
(I don't usually OC though.)
I tried 2.0ghz too for about 10 minutes with no issues. but I quickly went back to 1ghz incase I had any issues.
-------------------------------
Sent from my HTC Desire S
My CPU clock is as in my siggy. I don't undervolt though.
I have overclocked my phone to 1.5GHz almost all time and I do not see any problem, it's very fast and snappy. I use Sense roms, CM7 and ICS without freezes or something like that. Battery life is nice for me, 1 or 2 days of use.
I've got mine oc at 1.2ghz and uv .75 on everything using ocuv and has been stable for weeks now with good battery life.
CM7.1 Stable
TIAMAT Kernel
SmartAssv2: 184mhz - 1017mhz
Screen Off: SmartAssv2 184mhz - 384mhz
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
Sent from my HTC Desire S
Do you use setcpu? Can i use it also on latest stock cm7. 1 for desire s? Or is tiamat necessary? I'm mainly interested in undervolting -> better battery life.
peters. said:
Do you use setcpu? Can i use it also on latest stock cm7. 1 for desire s? Or is tiamat necessary? I'm mainly interested in undervolting -> better battery life.
Click to expand...
Click to collapse
Hi there,
Yes I use setcpu. Tiamat kernel is Undervolted by default which is good.
I'm my experience, I'm getting much better battery life with Tiamat kernel.
Are you on the nightly build or the stable version? I heard a few issues with tiamat on nightly builds, but not too sure!
Also a small note; undervolting doesn't help massively with battery life... the battery gain is minimal. On sense based ROMs, I UV by about 125V and it doesn't make a HUGE difference.
I think tiamat has really good battery llife as it has been exclusively optimised for our 8255 CPU by the brialliant Devs
Hope this has been some help to you!
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
Sent from my HTC Desire S
I never overclock higher than 1.5 GHz, I dont want to melt my phone.
Sent from my HTC Desire S using XDA App
I'm on latest nighly, which doesn't work with tiamat 1.1.5 (no sound). Nightly fixed some bugs which were crucial for me, so no way going back to stable.
Reason i'm asking: on lowveld's hyperions i got 8-9mA consumption while idle, on CM i'm always at 10-15. The min freq on both is 245mHz, which was suggested as lowest stable so the next difference i thought could be the undervolting... From battery stats i see that phone was not awake...
peters. said:
I'm on latest nighly, which doesn't work with tiamat 1.1.5 (no sound). Nightly fixed some bugs which were crucial for me, so no way going back to stable.
Reason i'm asking: on lowveld's hyperions i got 8-9mA consumption while idle, on CM i'm always at 10-15. The min freq on both is 245mHz, which was suggested as lowest stable so the next difference i thought could be the undervolting... From battery stats i see that phone was not awake...
Click to expand...
Click to collapse
What bug fixes did the nightlies bring? Please share!
Hmmm... I guess you could just wait for CM 7.2, I think its coming very soon with the bug fixes, so I guess you could go back to stable from there, and use Tiamat.
My lowest CPU clockspeed is 184Mhz on CM (122Mhz on Endymion)
Its very stable for me. No freezes, etc
I use smartass2, so it will throttle up the speed in sleep if 184mhz is too low. When it has many tasks to load etc.
Not to sure how to Manually UV with CM, (as OC beater doesn't work - FC on me)
But on Endymion, OC beater app does the job.
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
Sent from my HTC Desire S
Mainly bugs with voip calls. After htc released kernel sources, Nexx included them into the cm and the voip audio hack was not needed any more... Hopefully cm9 will be out sooner than 7.2
peters. said:
Mainly bugs with voip calls. After htc released kernel sources, Nexx included them into the cm and the voip audio hack was not needed any more... Hopefully cm9 will be out sooner than 7.2
Click to expand...
Click to collapse
Yeah, hopefully!
Side note: on sense, i could OC easily to 1.5ghz, possbily more! And it was very stable.
But now with CM7, i OCed to 1.5ghz and it froze... I tried several times too ..
So does software depend on how much the CPU can clock?
Sent from my iPod touch using Tapatalk
I bought a nexus S yesterday (the 9023 version), so I unlocked the BL, applied the CWR and flashed the 4.0.4 stock.
However, I feel the phone has more to give (more speed). Also, I suspect that the wifi signal is weak. Which kernel should I apply? I was wondering if I apply the air kernel, but the overclocking to 1.4 ghz kind of "scares me". But I see that OC is applied in other kernels. So, is it provely safe or something?
Also, if in the future I want to go back to stock kernel, all I need to to is flash an official OTA update again (too lose the root and the custom kernel)?
thanks in advance to all!
The custom kernels really can extract more juice from the NS. Try the ones that fits best for you, IMHO the best ones are Steve Garon's, Air Kernel and Franco's.
You can manage the clocks and voltages with NStools, and you don't need to use a daily 40% overclock. These things you can test, each device responds differently to overclock. I'm have a i9023 and actually using 1.32 GHz, it's pretty good.
Also, the feel of responsiveness comes not only by the clock, but also for SD speed and RAM utilization. Franco kernel comes with stock clocks, but the speed when oppening an app or scrolling the photo gallery is very good.
homerograco said:
The custom kernels really can extract more juice from the NS. Try the ones that fits best for you, IMHO the best ones are Steve Garon's, Air Kernel and Franco's.
You can manage the clocks and voltages with NStools, and you don't need to use a daily 40% overclock. These things you can test, each device responds differently to overclock. I'm have a i9023 and actually using 1.32 GHz, it's pretty good.
Also, the feel of responsiveness comes not only by the clock, but also for SD speed and RAM utilization. Franco kernel comes with stock clocks, but the speed when oppening an app or scrolling the photo gallery is very good.
Click to expand...
Click to collapse
Many thanks for your reply.
Maybe you can point the key advantages of those kernels in your opinion?
The main advantages for me are:
- More controls for clock scaling, you can define how your device will scale up or down the clocks in response to use
- Franco, Steve Garon and Air kernel have tweaks for SD card performance, the responsiveness when opening apps is better
- Steve Garon applies a 10% overclock in the bus, some applications that are GPU bound become more smooth, like browser (facebook and google reader too!)
- Steve Garon's and Air kernel implements methods for lower battery consumption when idle, even with overclock you can achieve the same battery consumption
Personally, my device is now much better than with stock kernel.
Sent from my Nexus S
Thanks.
My current favorites are Trinity and Matr1x cfs. Steve Garon's kernels were phenomenal, but he's recently retired from nexus development.
Sent from my Nexus S 4G using Tapatalk 2 Beta-5
What is the most stable? Franco?
I have a couple of question/advices I want to receive an answer for about CPU.
So I am struggling to get better battery life without hurting performance.
1) Can CPU apps hurt battery life by themselfs. I mean could only using an app not regarding the settings damage the battery life. Is it better to let the cpu work by itself and not any apps managing it?
2) Which is the best CPU control app?
3) Will Underclocking improve my battery life a lot and will it make performance worse. What are the best settings to keep battery life and performance optimized at the same time. If I want to play heavy games I will overclock for the time I play the game. But I don't want my cpu to be working at 1600ghz for instance when I am not doing gaming or similar heavy processes. What are the best settings to improve battery life but not hurt performance?
If you use an app like SetCPU, you can have profiles. I used to have it so that the phone would underclock when the battery reached a certain % or was too hot.
If you're S-Off and rooted, you can get way better battery life if you flash a new kernel. I'm using Faux v004, I've set SetCPU off and just let the kernel do its thing, and my battery life is at 1 day and almost 15 hours.
(I also play a lot of games and the Faux kernel is very resposnive. My games load much faster that they did on stock kernel)
Thanks! I am using this Kernel http://forum.xda-developers.com/showthread.php?t=1216197 and I find it good. I am rooted and used SetCPU in the past so I know all about profiles and etc. But my questions were. Do programs like SetCPU drain battery? And which best CPU program? And what about undervolting?
SsBloodY said:
Thanks! I am using this Kernel http://forum.xda-developers.com/showthread.php?t=1216197 and I find it good. I am rooted and used SetCPU in the past so I know all about profiles and etc. But my questions were. Do programs like SetCPU drain battery? And which best CPU program? And what about undervolting?
Click to expand...
Click to collapse
Apps like that don't really have any more of a drain than checking your email or receiving a text. If using Faux Kernel, there's an app out there designed for it that helps with clocking and undervolting it, made by the man himself. If not, AnTuTu has one on the market, I think.
sshede said:
Apps like that don't really have any more of a drain than checking your email or receiving a text. If using Faux Kernel, there's an app out there designed for it that helps with clocking and undervolting it, made by the man himself. If not, AnTuTu has one on the market, I think.
Click to expand...
Click to collapse
Fauxclock hasn't been updated in ages and it's by Romanbb, not faux, afaik.
As for the OP's questions:
1. Not really. I haven't noticed any extra battery drain with CPU apps so it's probably not significant.
2. I don't think there's a 'best' CPU app. I used to use SystemTuner, which worked fine for me, but I switched to SetCPU because I wanted to underclock the intellidemand governor on faux's latest beta.
3. Underclocking will lead to some improvement in battery life. As for undervolting, some people say it helps, others say it's a placebo; personally I've never bothered with it. You could try using faux's kernel with the intellidemand governor, which sets the clock speed (and whether the second core is online/offline) depending on the CPU load. As for best settings, it depends on each individual kernel and your own personal needs, so you might want to try flashing a few custom kernels to decide which one is for you.
hunter890 said:
Fauxclock hasn't been updated in ages and it's by Romanbb, not faux, afaik.
Click to expand...
Click to collapse
Ah, learn something everyday. Whenever I sideloaded the apk on CM7, the author was listed as "faux123".
sshede said:
Ah, learn something everyday. Whenever I sideloaded the apk on CM7, the author was listed as "faux123".
Click to expand...
Click to collapse
I know. I used to get confused too, especially since the app is called fauxclock! But faux mentions it's made by Romanbb on his kernel thread so... yea.
Sent from my HTC Sensation using XDA