I finally quit over-thinking the sucky battery drain on the new Miui. Originally, I thought using the Bali Kernel would solve this (it did in the older versions) but on the new version 9.23 Miui, the Bali 2.21 would not flash.
Well, went back to my old way of thinking and doing, and just changed the voltage settings on the current kernel
The result was dramatic, went from 10 hours (100% to 5%) on my phone to 15 hrs (100% to 35%) This makes it good enough for me to work all day use my phone ( Phone, camera, text, video, etc) without having to do an interim recharge.
For those who need more on how to, here is a link along with the app you can use:
http://forum.xda-developers.com/showthread.php?t=829731
There is another link inside this posting that explains voltage settings you should read it will help you get the gist of UV settings
I set to 1.2 = -75mv, 1.0 = -50mv 800 = -50mv and 400 =-25mv
This worked well for me but you need to check to make sure it is stable.
Go to the Apps store and D/L "stability test" app. Very useful.
If you want a different app for voltage settings take a look at setVsel app it will also work well.
Either way, an easy fix with a very acceptable outcome.
Hope this helps some of you...
you may want to do some stability testing, because if you're not on Glitch ML or LL, -75uv on 1.2 tends to be unstable, at least in my experience. You have more leeway on the low end than the high. For instance, -50uv at 1ghz and above is typical for most users, but for 800 and below you can easily go to -100uv, or even -150uv or -200uv for 200mhz and 100mhz.
kaintfm said:
you may want to do some stability testing, because if you're not on Glitch ML or LL, -75uv on 1.2 tends to be unstable, at least in my experience. You have more leeway on the low end than the high. For instance, -50uv at 1ghz and above is typical for most users, but for 800 and below you can easily go to -100uv, or even -150uv or -200uv for 200mhz and 100mhz.
Click to expand...
Click to collapse
Not Raining at all Like I said I used what worked for me, phones are all different and in my case my phone is a business tool so my approach has to more conservative and this works perfectly as configured for this phone.
I agree it does not resolve some of the bigger issues that Stockish Kernels possess, but under-volting did resolve the extreme battery drain I was experiencing.
I would prefer using Bali kernel by DrHonk but the new 9.23 Miui build had a few things added to it which will require a change of code and a re-syncing of the revised Bali kernel. DrHonk is aware and is working on this already. Until then, this fix will suffice until there is a update kernel release
BTW, thank you for the lower setting recommendations, I ll play around with that on the weekend.
Just updated the settings in my signature after a bit more testing with the Glitch Medium Leak (ML) Kernel. Was a little surprised that the settings were stable, but after 12hrs, they are rock solid, and battery life is noticeably better.
Did the same thing for my Samsung Fascinate (wifi only, as a poor-man's iPad) and while I couldn't get the settings above 1000mhz stable, the 1000mhz and under settings I used on my Vibrant were stable on the Fascinate as well.
Did you keep the other UV settings for example like 1.3 = -0mv or did you disable them (in SetCPU this is done by unchecking them)?
Related
I know for the droid there are lots of custom kernels that use very low voltages for high speeds. Do we have custom kernels like this?
The processor in our phone is that of the original 2g/3g iPhone, the 528mhz Qualcomm (that should have been updated 3 years ago).
The processor in the Droid is the same as the iPhone 3gs (except 550mhz clocked instead of 600mhz).
The Droid processor has a floating point co-processor (sort of) which is why the Linpack scores are WAY higher than ours (it doesn't actually mean the phone is faster, it just does certain floating point operations faster).
The Droid processor is also SEVERELY underclocked, probably for power reasons. There is more of a demand in the Droid crowd to control power usage while still increasing speed (hence the low-voltage kernels, etc). "Lower voltages" are found by using different ways to multiply the frequency, but in a processor like ours, we are limited in the different speeds we can multiply (not to mention a ceiling of reasonable operation being usually 800mhz or below).
See, some people want their droids to be at 800mhz. They want that great battery life, to keep things cool, and a small performance boost.
Some want to go up to 1300mhz, maybe because they play games, or because the think they're cool, or whatever. That requires different methods for overclocking (depending on which exact speeds) and uses a lot more juice. You could use a 1300mhz kernel and keep it down around 800mhz (or whatever specific speeds the kernel allows), but that kernel might not be built for low voltage - you might just be still multiplying a number that keeps your voltage high, instead of the 800mhz Kernel that only goes so high, but keeps things easier on the battery.
Our Eris processors are more limited. Pretty much, you want your Eris OC'd (usually to the 700+mhz somewhere is all you get), or you don't. If you don't want it OC'd, you just don't install SetCPU. If you do, you install and use it (or whatever other overclocking app/widget you want).
To use your Eris low voltage, you pretty much need to stay 480mhz or lower. I keep my sleep SetCPU Profile at 122mhz-480mhz. VERY good on battery, and it throttles up to 480mhz (so the phone rings faster) when it's time for a call to come in.
Some Kernels have some things enabled (netfilter for wifi tethering and other things, a2sd enabled, overclocking, etc - depending on how it's put together). It's probably best to have a kernel that allows everything, since with our processors, there's not much of a power drain penalty (none that I know of in fact) for having a different kernel, and just running at 528mhz. I notice no battery difference at 806mhz in fact, it's a matter of having SetCPU profiles (or whatever) set up correctly and effectively.
Here are a few Kernels you might find (but most are incorporated in ROMs already, so you'll virtually NEVER have to flash it - except that I use Ivan's Eris_Official 1.0 ROM with zanfur's beautiful v3 kernel - it works perfectly at 806mhz on my Eris).
AOSP kernel with all the goodies:
http://forum.xda-developers.com/showthread.php?t=688275&highlight=kernel
Zanfur's kernel (my favorite):
http://forum.xda-developers.com/showthread.php?t=679102&highlight=kernel
Kaos posted this one for AOSP:
http://forum.xda-developers.com/showthread.php?t=688439&highlight=kernel
Darchstar posted this one:
http://forum.xda-developers.com/showthread.php?t=686797&highlight=kernel
The point is that for us, it's not that useful to flash kernels. Most of the ROMs you'll download (even the most 'basic' ones) have all the goodies enabled on the Kernel.
Different phone, different hardware, different ballgame.
God damn. Best answer I could have hoped for. Seriously thanks a ton man, that was everything I could have wanted to know thoroughly explained.
nvm. answered my own question hah
I'm on Conap's new CFS Kernel. I multitask a lot so that's the kernel for me. Everything feels more responsive. Like 1.5x the responsiveness from the (I think) BFS kernel nonsensikal comes with. I typed all of this without even a hint of lag.
Sent from my nonsensikal froyo using XDA App
Yeah I've learned a lot since I made this topic a few months ago lol
I'm on V4 cfs
5thAgent said:
I'm on Conap's new CFS Kernel. I multitask a lot so that's the kernel for me. Everything feels more responsive. Like 1.5x the responsiveness from the (I think) BFS kernel nonsensikal comes with. I typed all of this without even a hint of lag.
Sent from my nonsensikal froyo using XDA App
Click to expand...
Click to collapse
Which keyboard did you use?
I'm using Kaos's DroidX keyboard - Froyo port.
Sent from my nonsensikal froyo using XDA App
On a Samsung Vibrant (U.S.A.) with stock v2.2 what are the best settings, profiles, ect. for saving battery? Also please label the specifics like max/min, scaling, and your advanced settings. Thank you...
EDIT: I understand you can't overclock without a customized kernal, but if I recall correctly you can underclock without it. Am I correct?
If you underclock your phone, it might get better battery life, but it perfomance will go down too and will start lagging, i don't recommend it at all.
The vibrant doesn't like profiles with less than 800 Max, it tends to freeze on wake-up. The amount of savings from an 800 MHz screen off profile is almost immeasurable as well. Also, the default conservative governor is the only one that is reliable. Therefore unless you're overclocking to start with, setcpu doesn't do anything for battery life on our phones. Best to just use a UV kernel such as BALI.
Sent from my SGH-T959 using Tapatalk
Hey man, what you want is undervolt. Underclock will slow you down, and not make a huge difference. However I undervolt by 75mv through the spectrum and have seen great results.
can't hurt to underclock to 800 though, some kernels are ok at 400 but very laggy.
Vibrant - project v, bali 1.8.6UV
JettyLife said:
Hey man, what you want is undervolt. Underclock will slow you down, and not make a huge difference. However I undervolt by 75mv through the spectrum and have seen great results.
can't hurt to underclock to 800 though, some kernels are ok at 400 but very laggy.
Vibrant - project v, bali 1.8.6UV
Click to expand...
Click to collapse
Yes.
Don't underclock. It will make your phone hell.
UNDERVOLT.
thats good.
Ok, I'm posting here because after doing a search, this is the very latest SetCPU thread. Recently, we finally got a worthwhile Gingerbread JVP and several ROM's (Simply Honey 3.8 & Asgard 3.1 JUST AMAZING ROM's) have finally given us some 2.3's we can keep on our phones, well in my opinion anyway.
So, I'm using cmenard's latest Bullet GB Kernel v6.1 and have decided to finally put to use the profiles section on SetCPU. Below is what I'm thinking and would enjoy a friendly conversation of what/if any benefits can be had on Gingerbread and customs Kernels using SetCPU Profiles. I read somewhere that Android is getting much better in regards to battery/performance efficiency, but I noticed a slight fall in battery life on 2.3.4 over 2.2.1 by a few hours.
My Profiles at this time.
Main SetCPU screen
200 min - 1200 max - Conservative? Smartass? Interactive? Any particular Governor worth using other than stock Conservative? - Set on Boot = YES
I'm not quite sure how the priority works on the main screen, I mean let's say I'm at 21% battery life and its time for my battery profile to kick in, but I'm still using the phone for various reasons, wifi calling or benchmarking etc. Will the phone stay at 200-1200 or will it actually use my battery profiles?
Screen Off (Set at 10 minute timeout)
100 - 800 - Conservative - Priority 100
Battery <11%
100 - 400 - Conservative - Priority 75 (Really thinking I should delete this)
Battery <21%
100 - 800 - Conservative - Priority 50
Charging
100 - 800 - Conservative - Priority 25 (Trying to keep the phone cool)
I have read that the Vibrant does not like profiles of 400 or lower when the screen is off, and this must be true as I tried 100-400, 200-400, but they all gave me wake of death until I set the max to 800 (there was no in between a.k.a 500, 600 or 700), so now 100-800 seems to work great for Screen Off. I hate this since when the screen is off the phone does not need to be doing anything other then checking gmail via wifi and notifying me using BLN blinking. Also, I tried to set a profile for Battery temp, but for what ever reason it will NOT give me the save button, so I assume GB now controls that on its own, or cmenard has removed that option from his kernel (or setcpu is borked, lol).
Any tips or concerns with my settings above? Anyone here a guru with SetCPU profiles and can see I'm a noob with profiles? lol
Thanks
SkOrPn
I stumbled upon these apps by dumb luck and decided to post this for anyone that doesn't know they exist. The dev is Chinese I am guessing based on a lot of his apps being in Chinese. He soes have these 3 apps in full English though and I am glad he does! For anyone that is looking for a SetCPU alternative, look no further. I will be the first to admit that I am not crazy about SetCPU. The app and I don't get along because of stability issues. CPU Master can do everything SetCPU can do but with better stability. I have been using it on both of my Vibrants. I have one Vibrant with the MIUI Rom (1.7.29) with the Bali 1.1.1 kernel and the other Vibrant is running CM7 Trigger Redux #17 with the Bali 1.1.1 kernel. I have had ZERO issues with the phones. Set on boot work flawlessly and overclocking is a breeze. The will give you every scaler that is included with the kernel you are running along with whatever overclock speed is set in the kernel. The Bali kernel supports up to 1.4Ghz and thats what the slider is maxed at. I loaded the Glitch kernel that supports 1.7Ghz overclock to see if the slider adjusts to that speed and as expected, I got 1.7. The only difference between the Free version and the paid version is that you can set and edit profiles in the paid version. For 1.99, its well worth the investment!
The Benchmark app ties directly into CPU Master. It tests everything that Quadrant Advanced (paid version) does PLUS it tests the speed of your SD cards! All of this and it's Free. If you are playing with overclocking speeds on your phone to see where the threshold is on your device, this benchmark will tell you. Through its rigorous testing you will see right away if your phones CPU can handle the speed you are testing. If you lock up during the test, its time to slow it down! On my MIUI Vibrant, I can only go up to 1.3Ghz and beyond that it freaks out. On my CM7 Trigger Vibrant, I can run 1.4Ghz with no problems.
Smart Profiles Free is a great app for people who spend part of their day in places where being quite is important. You can create all kinds of different profiles throughout your day to keep your phone running like the way YOU want it and not worry about turing on and off features. Just make your profiles and you are done! For example, from Monday to Friday I am at work 8 - 4:30 and I want my phone on Vibrate only. During those times I also want my WiFi on to use the company's internet and not my data plan and I also want my GPS off. As you can see you have A LOT of control of the various functions of your phone!
These apps are definitely worth the time to take a look at and try out. For any end user that wants even more control of their phone, they are certainly a fantastic addition!!
Free Apps:
CPU Master (Free): https://market.android.com/details?id=com.antutu.CpuMasterFree
AnTuTu Benchmark: https://market.android.com/details?id=com.antutu.ABenchMark
Smart Profiles (Free): https://market.android.com/details?id=com.antutu.phoneprofilefree
Paid App:
CPU Master for ROOT Users: https://market.android.com/details?id=com.antutu.CpuMaster
Excellent over / underclocking utility!
Yes, sure Antutu CPU Master is really a very good and powerful utility. I bought the pro version and it is worth the money. I am using it in my Samsung Infuse 4G, this allow the device to be underclocked till 100 MHz and overclock up to 1800 MHz, of course with the required Kernel and root access. It can be configured by the readymade profiles that can automatically change the clock settings based on conditions.
The widget which is just two column wide and 1 row height shows CPU Speed, Battery Status and Temperature.It has profiles, default, Charging, Screen off, In Call, Low battery, Temperature over-heat.
For stable clock setting set the minimum to 800 MHz as below this the device goes unresponsive particularly when the screen is off. I am using the range between 800 - 1800 and so far no issues, and it works great!
As mentioned, the benchmark, CPU setting and profile are great features of Antutu collection of software. Thanks to them!
Samsung Fascinate CDMA
Rooted MIUI 1.9.16
Did a brief search here looking to understand how to operate overclocking kernals, but find it/me relatively limited.
I have installed and ran Glitch v11 and v12, played around with HL to LL, and made adjustments to undervoltage utilizing Pimp My CPU and Voltage Control. I have also ran Tweak (though not really a kernal).
My question is this,
am I overclocking when I reduce voltage on Mhz's above 1,000?
If not, could someone point me to, or explain how to achieve overclocking on our phones, and
which kernel and governor do you prefer for overclocking?
As an ammended note, I've installed Tegrak Overclock, but am still looking for a user guide...
Thank you for your time.
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
efan450 said:
If you're the running the glitch kernel...use voltage control, not tegrak overclock...over clocking is when you turn the CPU speed above its normal speed..anything over 1GHz.
under volting is when you turn down the voltage frequency to achieve better battery life...
Any one clock speed may perform more or less stable with different under volting unfortunately all of our phones will vary in performance so one setting that works for one may not be the best for another so experimentation is really the best option...this applies for schedulers and governors as well.
I personally overclock as high as I can until it freezes or crashes..then I go 1 setting down...I then try undervolting different steps observing the stability of my phone...when I find what I like,I run it for a few days, then if its still nice and stable I will apply on boot.
The different leakage values are affected by the hardware quality of the chips in our phones which also vary..I start with high and see how high I can overclock..note the setting, then try medium..see how high I can overclock and so on...just as a reference..high leakage creates the most heat and is the least efficient, but works for most phones, while low leakage is the most efficient and generates the least heat and will work with not as many phones
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
FJRSport said:
Efan450,
Thanks.
How do you over-clock using Glitch and Voltage Control? I see that Voltage Control goes up to 1,300Mhz, but it's at 0 above 1,000Mhz and can be dropped down to -200mV. Is overclocking just the process of decreasing that voltage on Mhz's above 1,000Mhz's
Click to expand...
Click to collapse
come on man.. Clock speed (mhz) and undervolting are 2 completely different things.. Forget the voltage.. No changing the voltage is NOT overclocking.. You overclock by changing your maximum clock above 1000mhz which is stock for this phone.. Try long pressing 1200mhz and selecting set as max.. Now your overclocked to 1200mhz..
Sent from the fascinate that holds the record benchmark on antutu
No decreasing the voltage is simply undervolting whether it's over 1000 or under. The idea behind undervolting is increasing battery life, but you can't necessarily go and set each level to the maximum undervolt (200) you half to see what works. Increasing the processor speed is overclocking, stock speed is 1000 so anything over that is over clocked. As far as how far as how far you can over clock depends mostly on 2 things, 1. the kernel your using, ( for example if it shows 1300 in the list that means thats all that specific kernel supports) 2. It varys greatly between phones. For example with glitch you can overclock to 1700 but very few phones can run that high for longer than a few minutes!
Hope that helps.
Sent from my SCH-I500 using xda premium
Yes.. And the fact you say your running glitch and your max oc is only 1300 my guess is you broke your kernel with tegrak overclocks module.. Delete tegrak and stop downloading overclock apps. or any other root app unless you know fully the consequences first.. If after deleting tegrak, and rebooting, if your voltage control don't show a maximum clock of 1700 mhz, then you will need to reflash your glitch kernel
Sent from the fascinate that holds the record benchmark on antutu
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
FJRSport said:
Neh4pres,
Yeah, I kind of feel like a heel. For some reason, I had a brain fart when looking in the 'General' section of Voltage Control. I see now how to overclock.
Regarding ost #6:
When I flashed MIUI 1.9.16, I did not install any kernel; so it was kind of a half truth in that while running 1.9.9 I did have Glitch installd. Nevertheless, I still have Voltage Control installed.
mkropf,
I see that now, and thought as such earlier, but needed some clarification.
Having so many issues with Glitch and 1.9.9, I'm hesitant to install Glitch, but interested to see if it runs better on the newer MIUI...
Thank you two for answering my newbie questions.
Click to expand...
Click to collapse
There are no issues with glitch.. It is what I run.. Very smooth.. Just have to give your phone time to adjust and build cache
Sent from the fascinate that holds the record benchmark on antutu
Landscape
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
sageDieu said:
Make sure you're on the latest 9/15 version of the kernel. Anything before that will kill all of your phone's sensors.
http://forum.xda-developers.com/showthread.php?t=1252871
Click to expand...
Click to collapse
That was it. I had re-installed the older Glitch v12 that was already on my PC. Deleted them and downloaded the newer Glitch kernels to experiment with.
Thanks!
FJRSport said:
Re-installed Glitch v12 ML last night and have it overclocked @ 1,200 with no under-voltage...yet. Want to see any adverse effects.
I started at 1,300 and it locked up then rebooted within 5 minutes.
A concern I have is that now my phone will not Auto Rotate to Landscape even though I have Auto-Rotate 'on' in Settings.
I've scoured Sixstrings Glitch thread to no avail. Though it's not needed anymore, I also flashed the cleaning script just to see if it would make a difference.
Is there a work around or fix for this?
Click to expand...
Click to collapse
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
OC & UV settings
neh4pres said:
under volting helps stability.. I use -50 for everything above 1ghz.. Your phone may vary
Sent from the fascinate that holds the record benchmark on antutu
Click to expand...
Click to collapse
Yeah, locking and rebooting was while using the older version of Glitch v12. With the 9/15 dated Glitch I'm at 1300 now with the following settings:
Deadline / ondemand
200 - 1300
1300 -25
1200 -25
1000 -50
800 -50
400 -75
200 -75
1.2GHz is the best I say if you want good battery with a higher frequency. 1.4GHz is the best for anyone who uses their phone alot. Samsung did add 1.2GHz overclock in their source.
Sent from my SCH-I500 using XDA App
Back to running MIUI without Glitch.
Things that make you go, Hmmm?
For some reason, every time I accessed the keyboard for Google+, it hung, then froze, and 3 of the four times rebooted. The fourth time I needed to remove the battery to reboot. So I re-flashed MIUI 1.9.16 (effectively removing Glitch) and have 0 problems.
Bummer, I like Glitch too.
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
mkropf said:
I'm in the same boat, however they redone the latest glitch merge and posted it last night so I'm thinking we'll be back in good times
Sent from the most custom, custom rom Miui 1.9.16 and currently the best kernel Jt
Click to expand...
Click to collapse
are you using JT's 9/12 kernel?
if so...did you overclock it?
i'm on jt's 9/12 with miui 1.9.16 and wondering if I can / should overclock and undervolt it. I'm just trying to maximize battery life at this point.
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
sageDieu said:
Try the new glitch posted last night, it is fantastic.
Sent from my MIUI SCH-i500
Click to expand...
Click to collapse
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
worshipNtribute said:
what voltages are you running?
also for anyone..
is there any way to directly compare two kernels? like a test or something?
I can't decide between JT's 9/12 and the new glitch..
Click to expand...
Click to collapse
You wouldn't want to use my voltages, I put everything way lower than anybody else does or recommends and am just lucky that it is stable for me but it causes the sleep of death for anyone else.
For comparison, just run JT's kernel for a bit and then flash glitch and try it... once you play with OC/UV and voodoo color you won't be able to go back. (you'll be able to but you'd have to be insane.)
Just curious is most people who root/use custom ROMs overclock, and if so, what settings do you typically use in SetCPU?
I'm using a S2, rooted with latest Unnamed ROM and find myself contemplating if I should make any changes with SetCPU. Lots of options, and Unnamed has all the different governor options, etc. just really looking for some best practices that people who overclock often.
Would appreciate seeing what you consider to be stable overclock options that give a good boost without causing excessive heat/stability issues.
I'm coming at SetCPU with limited experience so I do appreciate any tips that might see rudimentary, or if there are better resources that teach about this I'd appreciate any links as would like to get a better technical understanding of all this. Thanks in advance.
I use No Frills CPU, and I just set it to 1.6 max/ondemand. Absolutely no heat issues or stability issues, so I just stuck with it. Battery life is good.
most maybe but only by a little bit. a good number of people underclock and undervolt their devices to try and get better battery life. to be honest, the newer phones dont need overclocking to handle the current apps and stuff. the older phones like the nexus one and older need overclocking tho. i leave my gs2 stock. what we really need is dual core support before OC becomes worth it on my phone. ymmv
I have never overclocked mine, phone runs smooth as butter at 1.2 so I don't see the need to go farther. Plus I like my battery lasting more than 24 hours...
I overclock my s2. im running unamed 1.3.0. I like run different speeds at different at different battery percents. 1.6 till 75% 1.4 till 50% 1.2 till 25% 1000 till 15% 800mhz till dead. i had some problems with 1.4 ghz but i tweeked the voltage and that did solved my problem. I'm at 50% battery with normal usage. display 1hr 25mn phone calls for 47min and android os for 56min. my phone doesn't get any hotter then it did before i overclocked. I just did it to say i did. It will prolly help a little unless you like emulators then it will help alot. i have to overclock my iconia a500 to 1.6 if i want to play n64 games.
I'm on UnNamed 1.3.1 with the latest entropy dd kernel and am very happy with the stock CPU speed
Sent from my Samsung GT-I9100