Related
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.)
I installed the webtop over hdmi mod on my Atrix and while testing it out, it got very warm in my hand. I opened the setcpu app and noticed that while overclocked to 1.3GHz, the CPU was running at 75C! I lowered it back down to the stock 1GHz and the temp slowly went down and settled at 63C.
It seems that while in webtop mode, the CPU is taxed at 100% all the time so I'm wondering if it's safe to stay overclocked when using webtop.
Everyone has different opinions of what is too hot around here.
IMO the cooler the better. IMI No Atrix should have a temp above 60c and I'm not even comfortable with above 50c either...
Sent from my MB860 using xda premium
I have experienced the same problem and worried that something may fry.... I have had mine overclocked at 1.45 using debian linux and all of a suddent he phone freezes and restarts.... Since it did it to me the second time I have kept my phone at 1Ghz... I am new at this so please don't beat me up too bad for being a noob... Just want to see if maybe undervolting it a little might help or hurt it?
Thanks in advance
Here are some tips I can offer
1.Try re-flashing your custom kernel and see if that fixes the web-top thing and over heating
Whenever the phone is plugged to the web-top it will naturally overheat so it's kinda expected remember now it's gotta work harder since its displaying on lap-dock or TV,but if you can cook an egg on it it might be too hot...lol
2.Set profile for temperature on setcpu so this way once you reach for example 100F your phone will clock down a little and so it might help the heat issue.You can set even more than one temp profile so this way when it reaches 96 it goes down a little then when it reaches 100 it will clock down a little more and such.
3.If that doesn't help,which in my situation it did.Flash a different kernel mayb it's just the one you're using that is causing funny stuff to happen.
Edit: not sure but i think undervolting helps battery but causes more heat,I myself don't undervolt I just created litterally a bunch of setcpu profiles for battery level,screen off,incall,charging,temp,and time and I'm getting 13 hour days at 1.3Ghz and temp profiles have been helping by clocking down when it's too hot therefore saving battery and drastic overheating.I dontlike my phone going anything over 104F it gets me paranoid,but that's just me.
I tried reflashing the kernel but it didn't change anything. I'm using Faux's 1.3GHz overclock kernel for Gingerbread (2.6.32.9). Is there something else I should be using?
sk8trix said:
Edit: not sure but i think undervolting helps battery but causes more heat,I myself don't undervolt I just created litterally a bunch of setcpu profiles for battery level,screen off,incall,charging,temp,and time and I'm getting 13 hour days at 1.3Ghz and temp profiles have been helping by clocking down when it's too hot therefore saving battery and drastic overheating.I dontlike my phone going anything over 104F it gets me paranoid,but that's just me.
Click to expand...
Click to collapse
Do what sktrix said in rest of his post.
I use the stopgap 1.0GHz kernel, and UV does lower temperatures. I would definitely try UV'ing a wee bit. You don't need to go crazy. I am using the following with great results for both temp and battery life:
-50
-50
-75
-75
-75
-100
-100
My setcpu profile clocks it back if I reach 60C, (I idle in the low to mid 30's). Under heavy load I reach around 52C max which is quite acceptable.
Now, granted I am not using Webtop, but the end result for UV should be the same. Lower temps and better battery life. You may also want to try just using 1.0GHz when on Webtop. The phone has more than enough power at this clock speed.
There is a bug with faux's kernel that causes the webtop to clock the phone at max speeds until restart.
Sent from my MB860 using xda premium
I know I'm straying from my correct forums here, however I have an LG Optimus 2X which like the Atrix, is a Tegra 2 CPU.
Our phones get VERY hot, I have had my CPU up to 86C before I decided to back off the stress test. CPUs are very good at handling high temperatures, and IMO you will see no ill effects from doing so, I am unsure of whether or not the Tegra 2 has thermal throttling/shut down, but in my experience they should be fine to around 80C.
The only issue I can forsee is the battery, batteries HATE high temperatures and it is awful for their life span, this is why your laptop batteries turn to crap after 1-2 years, even if low charge cycles, because they are always hot.
I would not be concerned about anything in the 70C realm, at all.
Alcapone263 said:
There is a bug with faux's kernel that causes the webtop to clock the phone at max speeds until restart.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Experienced this countless times. More with the latest 1.45Ghz, but it did happen on the previous release. When I dopped the mhz with setcpu, it wont scale but stay at max cpu. It even did it a few times without using the webtop.
g2tegg said:
Experienced this countless times. More with the latest 1.45Ghz, but it did happen on the previous release. When I dopped the mhz with setcpu, it wont scale but stay at max cpu. It even did it a few times without using the webtop.
Click to expand...
Click to collapse
So which overclocked kernel is best for webtop? I too have noticed where the CPU hangs at 100% at 1.45Ghz for a while when disconnected but it is always there when im in webtop mode.... How is Faux 1.3Ghz kernel with webtop?
ericemir said:
So which overclocked kernel is best for webtop? I too have noticed where the CPU hangs at 100% at 1.45Ghz for a while when disconnected but it is always there when im in webtop mode.... How is Faux 1.3Ghz kernel with webtop?
Click to expand...
Click to collapse
It will still hang at 1.3ghz, though it's a known bug. I just stick with the 1.0 enhanced, there's no noticeable real-world difference from going over 1.0ghz anyway, it's just a benchmark gimmick. Right now, the software that's out there is optimized to run on existing hardware w/o overclocks. I've run Shadowgun at 1.45ghz and didn't see any difference over the 1.0 enhanced.
Now, if we were trying to run games that were coded specifically or faster-paced chipsets then we'd need overclocking to catch up much like you would in the PC arena. That, however, is not happening in the cell phone market just yet.
treehumper said:
I just stick with the 1.0 enhanced, there's no noticeable real-world difference from going over 1.0ghz anyway, it's just a benchmark gimmick.
Click to expand...
Click to collapse
What's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
cjrhoades said:
What's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
Click to expand...
Click to collapse
Bump.
Anyone?
cjrhoades said:
Bump.
Anyone?
Click to expand...
Click to collapse
Read the history at the following:
http://forum.xda-developers.com/showpost.php?p=15387385&postcount=1
You will see a lot more optimization than just upping the clock speed. One of the reasons the 1.0GHz kernel works much better than the stock kernel. Also, the ability to undervolt saving battery life.
IMO there is no need for 1.3GHz or 1.45GHz in everyday use of a phone. The only benefit is for OC'ing bragging rights. Until we can control phone temperatures better, it's pointless to risk the substantial heat increase on ALL internal components for extended periods of time which results from much increased CPU temperatures.
CaelanT said:
Read the history at the following:
http://forum.xda-developers.com/showpost.php?p=15387385&postcount=1
You will see a lot more optimization than just upping the clock speed. One of the reasons the 1.0GHz kernel works much better than the stock kernel. Also, the ability to undervolt saving battery life.
IMO there is no need for 1.3GHz or 1.45GHz in everyday use of a phone. The only benefit is for OC'ing bragging rights. Until we can control phone temperatures better, it's pointless to risk the substantial heat increase on ALL internal components for extended periods of time which results from much increased CPU temperatures.
Click to expand...
Click to collapse
I see... guess that explains why the phone doesn't really feel any faster when it's overclocked. I'll flash the 1GHz kernel then.
Thanks for the info.
Not sure if this is the same with phones but normally a CPU should stay at 40C idle and 50C load. Maximum would be 60C while benching or something.
If it goes above that I would definitely underclock/undervolt.
cjrhoades said:
what's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
Click to expand...
Click to collapse
also has other fixes besides overclocking you can go read them in the kernel threads
alright. ive been playing around and cant find some good governors for what i want.
for hardcore gaming, what governor have you found that works the best
for best batter saving, but still be able to watch videos, surf web, email and just general navigating without it being too slow.
which governors do you guys use for both of those? thanks
Quadrider10 said:
alright. ive been playing around and cant find some good governors for what i want.
for hardcore gaming, what governor have you found that works the best
for best batter saving, but still be able to watch videos, surf web, email and just general navigating without it being too slow.
which governors do you guys use for both of those? thanks
Click to expand...
Click to collapse
anyone?
Use the smartassV2 governor. It regulates the CPU frequency according to load (sorta like ondemand except it works better).
darkghost568 said:
Use the smartassV2 governor. It regulates the CPU frequency according to load (sorta like ondemand except it works better).
Click to expand...
Click to collapse
i tried and i liked it, but it like locked my cpu at 1.24ghz (thats the max i have it set to) and even if i changed it, it would lock to the max frequency????
Quadrider10 said:
i tried and i liked it, but it like locked my cpu at 1.24ghz (thats the max i have it set to) and even if i changed it, it would lock to the max frequency????
Click to expand...
Click to collapse
I'll have v1 of Funky kernel out soon if you want to try out wheatley.
I've been a fan of smartassV2 since the first time I used it on the Thunderbolt. It is as close to an ideal governor as I've ever used. SmartassV2, with a complete sysfs implementation, can be tweaked very nicely. It is a governor that you can really tune so that most of the time it's not running balls out, but it's not loafing along either, which is how a governor SHOULD function. (I like to see a nice bell curve peaking at an ideal frequency, and spiked way out at the bottom frequencies when I look at a bar chart of my time-in-state's.) From what I can tell, few if any devs tune their governors to their kernels. I'm thinking that's how we ended up with a dozen or so governors that are rather similar, yet rarely ideal.
Snuzzo said:
I'll have v1 of Funky kernel out soon if you want to try out wheatley.
Click to expand...
Click to collapse
Wheatley is epic.
Sent from my Rezound using Tapatalk 2
loonatik78 said:
I've been a fan of smartassV2 since the first time I used it on the Thunderbolt. It is as close to an ideal governor as I've ever used. SmartassV2, with a complete sysfs implementation, can be tweaked very nicely. It is a governor that you can really tune so that most of the time it's not running balls out, but it's not loafing along either, which is how a governor SHOULD function. (I like to see a nice bell curve peaking at an ideal frequency, and spiked way out at the bottom frequencies when I look at a bar chart of my time-in-state's.) From what I can tell, few if any devs tune their governors to their kernels. I'm thinking that's how we ended up with a dozen or so governors that are rather similar, yet rarely ideal.
Click to expand...
Click to collapse
Alright now my problem is that I set my CPU to 192mhz lowest and 1.24 max. And that's for normal use. I'm running smart ass2 Nd it's not licking my CPU at max anymore, but it keeps.moving the max to 1.51ghz.
any ideas on how to fix tht?
Quadrider10 said:
any ideas on how to fix tht?
Click to expand...
Click to collapse
No frills CPU in play store
Sent from my ADR6425LVW using Tapatalk 2
Quadrider10 said:
Alright now my problem is that I set my CPU to 192mhz lowest and 1.24 max. And that's for normal use. I'm running smart ass2 Nd it's not licking my CPU at max anymore, but it keeps.moving the max to 1.51ghz.
Click to expand...
Click to collapse
Quadrider10 said:
any ideas on how to fix tht?
Click to expand...
Click to collapse
Yeah. Don't use DSB's kernel. I spent DAYS trying to figure out what his kernel is trying to do as far as governors. I'm not going to talk smack about the guy's work, but I will tell you what I know.
I doesn't appear any of the governors have been tweaked for his kernel. It looks like code was just tossed in there and left however someone else wrote it. For instance, smartassV2 has a sleep_wakup_freq of .998GHz, which is much slower than it should be. It SHOULD be near or equal to scaling_max_freq. Likewise, the max_cpu_load (which determines when the cpu should scale up) is 70, a fairly aggressive number, while the awake_ideal_freq and sleep_ideal_freq are pointlessly high. If I had to guess, these look like parameters for a Snapdragon S1 SoC, not the dual core S3 the Rezound has. No matter what governor you choose, it's only active on "cpu0". "cpu1" runs ondemand no matter what. The reason you have trouble making settings for the governor stick is because the sysfs location disappears and reappears for no obvious reason. It appears when things pop in and out (presumably when cpu1 goes on and off line), things are reset.
Cold hard reality is this: You're NEVER going to optimize any kernel out there to it's fullest potential. Either the options aren't there to tweak, or they behave in inexplicable ways. I can't tell you why DSB's kernel (not to single out a dev or his work, but I'm certain that's the kernel you're talking about) does what it does, but it's so far divorced from optimized on such basic levels you're better off not wasting your time.
As an aside:
After getting a rough feel for what some of these kernels are doing, I'm not at all surprised some kernels have had significant heat and battery drain issues. There are things that simply do not work right or work consistently. The devs shouldn't be blamed for this. These are probably the issues they're trying to work around that they inherited from the sources they're starting from and what makes tweaking them so difficult.
I acutely got everything to work. I'm just trying to overclock the GPU.
The whole time that i have had the rezound i have had problems with the cpu settings sticking, and i read somewhere that using a script to set it works best. would this work? http://forum.xda-developers.com/showthread.php?t=1584508. and also since I have not really had luck with them sticking i would like to know what you guys think is the best governor, i was probably going to use smartassv2, wheatley, or pegesusq, but im not sure if they are the best for performance and all the explanations of them dont really tell if they perform in real life. Im looking for mostly performance, but i dont want something that will destroy my battery
edit: that link doesnt work, the download is missing, so what is a different way?
Why would you want a CPU governer if it wasn't to help with your battery life?
GrayTheWolf said:
Why would you want a CPU governer if it wasn't to help with your battery life?
Click to expand...
Click to collapse
to overclock it to get better performance
xxtsxx said:
to overclock it to get better performance
Click to expand...
Click to collapse
You need an overclocked kernel to do that.
GrayTheWolf said:
You need an overclocked kernel to do that.
Click to expand...
Click to collapse
well yeah i have that, im running cubed ics kernel 2.3.5, and i just want a better way to make my overclock stick and which governor will give the best performance without completely using up the battery, kind of a happy medium but leaning a little more towards performance. I guess I didnt explain that good enough
xxtsxx said:
well yeah i have that, im running cubed ics kernel 2.3.5, and i just want a better way to make my overclock stick and which governor will give the best performance without completely using up the battery, kind of a happy medium but leaning a little more towards performance. I guess I didnt explain that good enough
Click to expand...
Click to collapse
These are a bit dated and from another phone, but can provide a bit of insight into kernel governors and their behavior. Keep in mind a few technical points are different for our phone (different min/max clock speeds) but much is the same in general.
tl;dr Smartassv2 should meet your needs as a top performer while still gaining some battery savings. Try with noop or sio I/O scheduler. A modest undervolt, but avoid pushing it.
Kernel Features and Benchmarks
Battery Saving Governor Benchmarks
Battery Drain Benchmarks
PhantasmRezound said:
These are a bit dated and from another phone, but can provide a bit of insight into kernel governors and their behavior. Keep in mind a few technical points are different for our phone (different min/max clock speeds) but much is the same in general.
tl;dr Smartassv2 should meet your needs as a top performer while still gaining some battery savings. Try with noop or sio I/O scheduler. A modest undervolt, but avoid pushing it.
Kernel Features and Benchmarks
Battery Saving Governor Benchmarks
Battery Drain Benchmarks
Click to expand...
Click to collapse
hey thanks for all that info
I have no problems keeping my Governor (Wheatly) set with System Tuner using the set CPU preference to remember after boot complete.
Hello folks!
This thread is intended for sharing, please be kind. Any suggestions would be appreciated
A few days ago I was tired of having my Mi3 running on stock global dev MIUI 8, it was inefficient system with really bad memory management. On my experience, the MIUI tend to run out of memory. In some case, after a few hours of usage the system cannot reclaim the occupied RAM, thus making the system lags a lot and generate excessive heat!
Yes, MIUI is a feature-rich ROM, and the Mi ecosystem is a pretty mature ecosystem. However, those all greatness needs a lot of power to run on our 3 year old device. After a few research I decided to switch to CM13 ROM.
With efficiency in mind, I do my research and tinkering with my device to get the best setup possible without losing performance. The results are AMAZING! I can use my phone for a whole day without recharge in the mid day. All of this with huge improvement on performance, Real Racing 3 highest graphic setting without any noticeable lag! CPU and battery temperature are now significantly lower (43-47C idle / light tasks, 55-57C heavy gaming). Now that I've found the best setup, I want to share it with you folks! Here we go:
Mi3W 64GB
CM13 ROM snapshot build
CM kernel (automatically flashed while flashing CM13 zip through TWRP)
Screen resolution changed to 720x1280 use this guide
Modded interactive CPU governor (see screenshot below)
Undervolt (see screenshot below, this one really helps reduce CPU working temperature)
Noop I/O scheduler
Reduce aggresiveness of LMK (see screenshot below)
Thats all folks, hope this guide will get our Mi3 having another year of flagship-grade experience! Cheers! :highfive:
How did u undervolt
kingnikpic said:
How did u undervolt
Click to expand...
Click to collapse
It depends on the kernel used. Cm kernel that he used supports undervolt. Careful when undervolting though as too much of it can cause cpu instability and reboots.
kingnikpic said:
How did u undervolt
Click to expand...
Click to collapse
Yes, it depends on the kernel used. Some kernel support undervolting while others don't. You need to flash kernel that support undervolt.
solazz said:
It depends on the kernel used. Cm kernel that he used supports undervolt. Careful when undervolting though as too much of it can cause cpu instability and reboots.
Click to expand...
Click to collapse
While testing CPU voltage value, don't tick "apply on boot" option until you find the most stable voltage without causing system reboot or crashes. Every CPU has different limit on how far you can undervolt, but you can use the values on my screenshot as guidance (Snapdragon 801 / MSM8974-AB only)
Wow!! Thanks a lot bro. I'll fiddle now with my phone.
miui8polska，i cant root it .can you give me a supersu.zip?
Sent from my MI 4LTE using XDA Labs
Random reboot after setting undervolt just likes yours
z1d4n21 said:
Random reboot after setting undervolt just likes yours
Click to expand...
Click to collapse
Undervolting (and clock adjustment, in general) pretty much is a case-per-case basis, so different handsets (even if it's the same type of device) may have different setup. Try lowering it first incrementally and test it, until you have it stable enough.
rxl.noir said:
Undervolting (and clock adjustment, in general) pretty much is a case-per-case basis, so different handsets (even if it's the same type of device) may have different setup. Try lowering it first incrementally and test it, until you have it stable enough.
Click to expand...
Click to collapse
Ok thanks i will test it later