Related
Sent from my PC36100 using XDA App
http://forum.xda-developers.com/forumdisplay.php?f=652
I've had my phone overclocked 15% for months now...I pre-ordered and picked it up on June 4th (the day they were released to the public) and it's never been replaced. I rooted it right away using the engineering hboot method, and I immediately went to a rooted stock rom with a kernel that'd allow overclocking the very first time I saw one posted on this forum. I've never been able to run it at anything higher than 1152 mhz, but I've also never had any stability issues at 1152 mhz. I also allow it to go as low as 128 mhz all the time.
Since then I've played with various roms, and various kernels, but the first thing I've done when changing any rom or kernel, is always set the min and max CPU speeds again, and decide which governor to use. I've also always played with the undervolting strategies, from static to HAVS, and I've always been able to get away with the most agressive stuff posted without any stability issues.
Your mileage may vary, but thats been my experience with an overclocked Evo. I will admit I can barely notice the performance difference from 998 mhz to 1152 mhz, but I actually notice a battery life improvement...get it done faster so the CPU can go back to idling at a low frequency as soon as possible mentality I guess.
please watch what you say here. its not going to get you any help to curse and swear at other members. last warning
@MikeOD, which governor and what governor parameters have you found to work best for you?
I think the whole overclock boils down to what you do with your phone. If nothing overly cpu intensive, then there's likely to be little gain in the amount of saved time.
I actually have mine under clocked at 921 Mhz (came that way in the rom initially). UI was fluid enough and everything still seemed to work well/responsive. I get slightly better battery life too. Noticeable in the rate the batt % declines during active tasks (web browsing).
II'm very new to xda but i successfully flashed SyndicateROM frozen 1.10 and wanted to know what setting i should be placing in setCPU to achieve the advertised overclocked 1.3gHz and undervolted at 1.0gHz, i've read min:200, idle:800, and max:1000-1300. Anyway I appreciate the help and thanks to all of you hard at work in the Android dev community!
You'll get the undervolted 1ghz by default. If you want 1.3ghz, use it as the max.
so if i understand correctly, if i overclock it to 1.3ghz i will be undervolted at 1ghz, so as far as battery life goes, will overclocking it to 1.3ghz give me battery life of the stock 1.0ghz? Sorry for the possibly erroneous questions lol
trdmatrix88 said:
so if i understand correctly, if i overclock it to 1.3ghz i will be undervolted at 1ghz, so as far as battery life goes, will overclocking it to 1.3ghz give me battery life of the stock 1.0ghz? Sorry for the possibly erroneous questions lol
Click to expand...
Click to collapse
No. You will see less battery life at 1.3ghz. If you want battery life, don't even bother with SetCPU.
Set min 100, max 1.3ghz ondemand governor. 1ghz is uv automatically when it runs at that, but with 1.3 as your max it may not spend much time in 1.0. If your concerned with battery (UV) then min 100, max 1000 might be what you want. I've been running that and I seriously cannot come up with a single speed complaint. K0 and team have done an amazing job with this thing.
Sent from my ACS frozen Epic 1.1 and counting.
is setCPU safe to use on the epic with syndicaterom? i searched the forums, and it looks like some people are having problems with it...
niiiick said:
is setCPU safe to use on the epic with syndicaterom? i searched the forums, and it looks like some people are having problems with it...
Click to expand...
Click to collapse
I've been using syndicate rom for a coons age now and set cpu running the entire time working flawlessly.
Sent from my SPH-D700 using XDA Premium App
Total noob question, is it safe to overclock? If I use setCPU to slow the processor down once it gets over a certain temperature will I be okay? I am just worried about melting the phone.
I use setcpu I keep my Max frequency at 1157 and my min frequency and around 422 that way my phone doesn't have to use much power if it doesn't need to. I usually run the smartass governor or conservative. Its very safe as the kernels wont let you clock past speeds that would overheat your phone.
~ d3rk
overclocking its so last year, try underclocking! the battery life is awesome
NewZJ said:
overclocking its so last year, try underclocking! the battery life is awesome
Click to expand...
Click to collapse
Derp.
Just make sure the "set on boot" box is unticked in SetCPU and you shouldn't have any problems.
Thanks everyone!
Hi guys, i've been looking into many threads and reading a lot of posts and asking a lot of questions. however i know that their is not for sure answer to this but i would like to see what you guys believe to be your best kernel for battery and performance. i have seen people say it is Godmode (v9), Tiamat v4.1.0, Tiamat v3.3.7, and Savaged-zen v2.2.1. (ALL of these ARE with SBC-OFF). i just want to know what is you best kernel at the moment for your evo with decks or cm7.
Side Question: what is the difference between the governors: (Interactive, InteractiveX, Smartass, SmartassV2, Savaged-zen, and Lag Free)?
- Thank You
I like Tiamat 4.1.0, but I can't help you for your side question. I'm still new to development and rooting
kendallc123 said:
I like Tiamat 4.1.0, but I can't help you for your side question. I'm still new to development and rooting
Click to expand...
Click to collapse
i know you said your new but im just wondering have you tried any other kernels?
and what is your battery life with Tiamat 4.1.0
I've used damn near every kernel available for CM7. And by far the BEST kernel for battery life is Savaged Zen. I'm on a stock battery and it just seems to last forever. Add to that the fact that the battery lasts all day without sacrificing performance at all. Every phone is different and you may or may not see the same results. This is just what has worked for my phone. Honestly, your best bet is to get flash happy with various kernels until you find one that gives you the performance and battery life that you're looking for. By the way, I use SVZ Manager with my kernel so that I can toggle SBC on and off as I please. It's a nice apk that gives you some flexibility.
**CLICK HERE**
Green_Arrow said:
i know you said your new but im just wondering have you tried any other kernels?
and what is your battery life with Tiamat 4.1.0
Click to expand...
Click to collapse
I've tried Tiamat 4.0.8 and a Savaged Zen kernel (can't remember which version). They both gave me about 12 hours of battery life on an average day(for me). But an average day for me is going to school, so I'm not on my phone as much. I haven't gotten to really test the battery life because I haven't looked at it on the weekend when I'm not at school. But like Concordium said, every phone is different! Try them all!
Tiamat 3.3.7 sbc
Sent from my PC36100 using XDA App
Concordium said:
I've used damn near every kernel available for CM7. And by far the BEST kernel for battery life is Savaged Zen. I'm on a stock battery and it just seems to last forever. Add to that the fact that the battery lasts all day without sacrificing performance at all. Every phone is different and you may or may not see the same results. This is just what has worked for my phone. Honestly, your best bet is to get flash happy with various kernels until you find one that gives you the performance and battery life that you're looking for. By the way, I use SVZ Manager with my kernel so that I can toggle SBC on and off as I please. It's a nice apk that gives you some flexibility.
**CLICK HERE**
Click to expand...
Click to collapse
at the moment i am using the latest svz kernel with the svz manager as well. i have been flashing many kernels and for a while i was happy when i used the godmode kernel my phone lasted me 1 day and 6 hours, however he is no longer updating his kernels =( i'm hoping to find another kernel such as that one that will give me around the same results ^_^
Green_Arrow said:
at the moment i am using the latest svz kernel with the svz manager as well. i have been flashing many kernels and for a while i was happy when i used the godmode kernel my phone lasted me 1 day and 6 hours, however he is no longer updating his kernels =( i'm hoping to find another kernel such as that one that will give me around the same results ^_^
Click to expand...
Click to collapse
I liked Godmode. But it didn't seem to give me as good battery life as savaged zen has given me. Each phone is different though.
Concordium said:
I liked Godmode. But it didn't seem to give me as good battery life as savaged zen has given me. Each phone is different though.
Click to expand...
Click to collapse
well im testing this one out at the moment and it has given me so far 17 hours and 20 mins, still at 31% battery, im just not sure if it'll do better than godmode did, at the moment im running it on the smartass kernel and i ran godmode on interactive so maybe that is the prob... however another issue is i've heard that svz is no longer updating as well... do u know if this is true? and one random thing that only a few people have told me is that they run on performance and overclock their phone and get the best battery from it, is that possible or a lie?
Edit: it lasted 20 hours and 53 mins, so since it didn't do as good as GodMode did then im gonna try the tiamat 4.1.0 now cause it has first place in the poll atm.
Green_Arrow said:
well im testing this one out at the moment and it has given me so far 17 hours and 20 mins, still at 31% battery, im just not sure if it'll do better than godmode did, at the moment im running it on the smartass kernel and i ran godmode on interactive so maybe that is the prob... however another issue is i've heard that svz is no longer updating as well... do u know if this is true? and one random thing that only a few people have told me is that they run on performance and overclock their phone and get the best battery from it, is that possible or a lie?
Edit: it lasted 20 hours and 53 mins, so since it didn't do as good as GodMode did then im gonna try the tiamat 4.1.0 now cause it has first place in the poll atm.
Click to expand...
Click to collapse
Its true that its not being updated anymore. It sucks but I plan to ride it out as long as the kernel functions properly with CM. Once it starts screwing up then I'll switch.
Those who say they get the best battery life by overclocking and putting their phone on performance are full of crap. Performance governor is basically the polar opposite of Powersave. Performance keeps your cpu constantly running at a high frequency. Logic states that overclocking to 1.13 ghz and perpetually running at that frequency requires more power than running at 245 mhz. The more power required the less time your battery will stay alive. Powersave gives you best battery life but gives you crap performance. Interactive, Smartass, and Ondemand give you a balance of performance and battery life. Performance gives you the best performance but crap battery life.
By the way, do you really need a phone that can stay off the charger for more than 21 hours? :-x
Concordium said:
Its true that its not being updated anymore. It sucks but I plan to ride it out as long as the kernel functions properly with CM. Once it starts screwing up then I'll switch.
Those who say they get the best battery life by overclocking and putting their phone on performance are full of crap. Performance governor is basically the polar opposite of Powersave. Performance keeps your cpu constantly running at a high frequency. Logic states that overclocking to 1.13 ghz and perpetually running at that frequency requires more power than running at 245 mhz. The more power required the less time your battery will stay alive. Powersave gives you best battery life but gives you crap performance. Interactive, Smartass, and Ondemand give you a balance of performance and battery life. Performance gives you the best performance but crap battery life.
By the way, do you really need a phone that can stay off the charger for more than 21 hours? :-x
Click to expand...
Click to collapse
no i do not but! 3 days of the week im at school doing nothing for 8-10 hours so... i think if my phone can run longer than a day w/o charging then it mean i can play games on my phone while waiting and by the end of the day i'll still have battery. and does it make sense for someone to get better battery life on interactive than on smartass?
Green_Arrow said:
no i do not but! 3 days of the week im at school doing nothing for 8-10 hours so... i think if my phone can run longer than a day w/o charging then it mean i can play games on my phone while waiting and by the end of the day i'll still have battery. and does it make sense for someone to get better battery life on interactive than on smartass?
Click to expand...
Click to collapse
Well Smartass, as I've heard it described, is sort of like Interactive 2.0. It's basically the interactive governor but better. Unfortunately, I do not know enough of the exact specifics of the governors to tell you which SHOULD be getting better battery. I would just run each of those governors and see which one works better for you.
And I thought your phone already lasted 21 hours with a decent amount of usage. You need to test the governors/kernels in the exact situation you are going to be using the phone. Interactive, Ondemand, and Smartass would all manage the phone pretty much the same if you just leave it alone and let it sit till the battery drains. but they each manage the power allocation supplied to the cpu very differently during actual use. One ramps up the voltage quickly while one scales it up more gradually. So take your charger with you to school, in case you run into trouble, and use the phone as you believe you will be using it in the future. Then you'll have a more accurate idea of which setup works best for you.
Concordium said:
Well Smartass, as I've heard it described, is sort of like Interactive 2.0. It's basically the interactive governor but better. Unfortunately, I do not know enough of the exact specifics of the governors to tell you which SHOULD be getting better battery. I would just run each of those governors and see which one works better for you.
And I thought your phone already lasted 21 hours with a decent amount of usage. You need to test the governors/kernels in the exact situation you are going to be using the phone. Interactive, Ondemand, and Smartass would all manage the phone pretty much the same if you just leave it alone and let it sit till the battery drains. but they each manage the power allocation supplied to the cpu very differently during actual use. One ramps up the voltage quickly while one scales it up more gradually. So take your charger with you to school, in case you run into trouble, and use the phone as you believe you will be using it in the future. Then you'll have a more accurate idea of which setup works best for you.
Click to expand...
Click to collapse
just wondering what do you keep your cpu settings at: the governor, cpu min & max?
When I am plugged into my wall charger I keep it at 1113/245. I use Performance for benchmarking and testing since I don't need to worry about battery life and Smartass when doing everything else. For normal every day use I have it at 1036/245/Smartass, Interactive, or Ondemand. I don't really have a preference between the three governors since they all make my battery last more than long enough. So it usually comes down to whichever my clumsy finger happens to accidentally select first. If I happen to not go home and need more life then I'll drop to 729/245/Conservative or Powersave. I use conservative if I still need to be able to use the phone a bit and powersave if I want my phone to just sit there and look pretty till I get back home.
Concordium said:
When I am plugged into my wall charger I keep it at 1113/245. I use Performance for benchmarking and testing since I don't need to worry about battery life and Smartass when doing everything else. For normal every day use I have it at 1036/245/Smartass, Interactive, or Ondemand. I don't really have a preference between the three governors since they all make my battery last more than long enough. So it usually comes down to whichever my clumsy finger happens to accidentally select first. If I happen to not go home and need more life then I'll drop to 729/245/Conservative or Powersave. I use conservative if I still need to be able to use the phone a bit and powersave if I want my phone to just sit there and look pretty till I get back home.
Click to expand...
Click to collapse
why is ur lowest 245 and not 128? sorry if im bugging you
Green_Arrow said:
why is ur lowest 245 and not 128? sorry if im bugging you
Click to expand...
Click to collapse
You're not bugging me man. This place exists so people can ask questions and get help.
I keep my min at 245 because I've read, in multiple places, that allowing it to go any lower is not something your cpu really appreciates. Just like there is such thing as too high with your clock speed there is also a too low. And everywhere I have seen 245 is the preferred low end. I am not 100% sure as to why but I would assume that it is because your cpu needs at least a certain amount of power to run the basic processes required to keep your phone functional. Similar to a computer. Lower the cpu too much and it just can't do what it needs to.
Concordium said:
You're not bugging me man. This place exists so people can ask questions and get help.
I keep my min at 245 because I've read, in multiple places, that allowing it to go any lower is not something your cpu really appreciates. Just like there is such thing as too high with your clock speed there is also a too low. And everywhere I have seen 245 is the preferred low end. I am not 100% sure as to why but I would assume that it is because your cpu needs at least a certain amount of power to run the basic processes required to keep your phone functional. Similar to a computer. Lower the cpu too much and it just can't do what it needs to.
Click to expand...
Click to collapse
i see do u happen to know of a good thread that talks about this? cause i keep mine at the lowest because i read that its better for battery life, but they never said anything about it being bad
Green_Arrow said:
i see do u happen to know of a good thread that talks about this? cause i keep mine at the lowest because i read that its better for battery life, but they never said anything about it being bad
Click to expand...
Click to collapse
I don't remember there being a thread dedicated to this. I just remember it from posts I saw within different OC/UV threads. Do a Google search for it and see if that returns any results. Like I said, I doubt you'll find a full dedicated thread. But you may be able to find the individual posts where it's mentioned.
Concordium said:
I don't remember there being a thread dedicated to this. I just remember it from posts I saw within different OC/UV threads. Do a Google search for it and see if that returns any results. Like I said, I doubt you'll find a full dedicated thread. But you may be able to find the individual posts where it's mentioned.
Click to expand...
Click to collapse
thank you, you have been really helpful ^_^
With Tiamat 4.1 and juicedefender I get the best battery performance and v6 supercharger I have a smooth screen with no problems or lag at all.
Re: Post by user splus in Franco.kernel thread
Sorry to post in this forum, but I don't have the minimum post count yet to post in the development forums
I read a post today by splus which I found very interesting,
In r220 hispeed_freq parameter in governor control has been changed from 1200000 (was an old value from first version of Franco JB kernel) to 1228000. As a result CPU now spends most of its time at either at 384 or 1228 MHz, and much less time at higher frequencies.
For some reason if speed_freq value is set to a step lower than 1228000 then it will make CPU to use all higher frequencies in a more balanced way.
What I noticed is that for 1036 it needs to have slightly higher value of 1037000, because 1036000 will put the CPU only to 729 MHz. This is probably because the real 1036 MHz frequency is something like 1036.xx MHz, so it's best to set speed_freq value to a 1000 more than the desired frequency.
Hispeed_freq parameter is just an initial higher speed frequency that CPU will jump to when there's some CPU load. And if the CPU load is still high after the CPU goes into this frequency (in other words if this frequency is not enough to finish the job) then interactive governor will put the CPU in even higher frequencies.
On stock JB kernel max frequency is 1200 MHz, and hispeed_freq is 700000.
When speed_freq is set to 1228000 it will use mostly 384 and 1228 MHz frequencies.
Set speed_freq to 1037000 (or previous 1200000) and more higher frequencies will be used.
There's certainly many possibilities to play with min and max CPU values, together with speed_freq to come to the best values. And probably for each max CPU frequency different speed_freq value would work best...
Click to expand...
Click to collapse
but I wanted to learn more so I did a lot of Googling about the parameters of the interactive governor. Unfortunately, I kept finding the same few beginners' guides to the different governors available, explaining and comparing their capabilities. There was no advanced explanation of the parameters or their possible valid values.
I found this post by RootzWiki user abqnm, which shed a little more light on the hispeed_freq parameter, and input_boost also. From what I've read on various sites, the input_boost seems to be a binary parameter, so setting it to 1 should jump the CPU up to the frequency specified in hispeed_freq immediately upon detecting a screen touch event. This would make your GNex feel a bit more responsive, without having to wait for the CPU to hit load, but it could negatively affect battery life. In my case, running 729/1612 with hispeed_freq set down at 1036MHz (1037000 in governor control), it's not that big a jump and opening a couple of apps would likely push my speed up beyond it soon anyway, so the battery hit would probably not be much.
As splus said:
After lot of fiddling I found it works best when hispeed_freq is set to 1037000 (not 1036000, it looks like that frequency is actually closer to 1037 MHz so 1036000 doesn't "reach" it).
Click to expand...
Click to collapse
so using 1036000 in governor control would correspond to the next step down, 729MHz. I know it's easy enough to stick on an extra 1000 for safety, to ensure we hit the right steps, but I'd be curious to know the exact kHz values we could be using.
I'm off to start experimenting with undervolting these new CPU freqs, and my 512GPU Core to reduce my temps a bit.
In case anyone asks, I'm on stock JRO03C w/Franco r220 512GPU.
Very good post! Welcome to XDA! :good:
I'll link to your post on the franco thread just so it gets a couple views from people there.
Edit: I see that you've actually been here awhile! Go help a few more people so you can contribute in the Dev forum.
Yup, that's me... total lurker! I usually defer to the wisdom of the devs and seasoned members, and 99% of the time if I've had a problem/question re my Nexus it's already been posted and there are whole conversations for me to read and digest. I hate the idea of clogging up a thread with a "me too" or "thanks" post, so generally if I don't have something useful to contribute I keep quiet and hang in the shadows. I only come out to feed.
So basically, I'm a knowledge vampire.
That's enough OT... Franco stuff!
I've previously read droidphile's governors thread to which splus linked in their reply to your repost in Franco.kernel. In post #2, containing the governor tweaks (which I found very useful) even droidphile seems to have the wrong idea about the "hispeed_freq" parameter, stating:
(Default value is scaling max freq)
Click to expand...
Click to collapse
The same section also omits any mention of the "input_boost" parameter.
My undervolting is going well. Inspired by the voltages on rogersnm's signature, I'm currently running these:
Code:
1612 - 800 mV
1536 - 750 mV
1420 - 750 mV
1305 - 750 mV
1228 - 725 mV
1036 - 725 mV
729 - 700 mV
384 - 700mV
CORE -
512/384 - 900 mV
307 - 900 mV
153 - 825 mV
IVA -
266 - 600 mV
133 - 600 mV
I added an extra 100mV to the seemingly rock bottom CPU voltages for safety, but I'll try to reduce them gradually. I've been stable for over 40 hours so far on this setup. With r220, Franco really seems to have nailed it!
BTW, thanks for reposting in the Franco.kernel thread :highfive:
Fantastic. Keep us updated on your progress with voltages, seems like you're doing a great job!
Also, happy to help!
nemotheblue said:
Code:
1612 - 800 mV
1536 - 750 mV
1420 - 750 mV
1305 - 750 mV
1228 - 725 mV
1036 - 725 mV
729 - 700 mV
384 - 700mV
CORE -
512/384 - 900 mV
307 - 900 mV
153 - 825 mV
IVA -
266 - 600 mV
133 - 600 mV
I added an extra 100mV to the seemingly rock bottom CPU voltages for safety, but I'll try to reduce them gradually. I've been stable for over 40 hours so far on this setup. With r220, Franco really seems to have nailed it!
BTW, thanks for reposting in the Franco.kernel thread :highfive:
Click to expand...
Click to collapse
I'm trying these too. So far so good!
Hi nemotheblue. Good post and findings!
I'm just looking at those voltage values you wrote - are you sure you turned off the SR?
If you haven't don't turn it off with those voltages because you'll get an instant reboot, they seem super low.
Rogersnm wrote and fiddled a lot with voltages, some very good posts.
Better go back to stock voltages, turn off the SR, and then go little by little down with frequencies. When adjusting each frequency best is to set that particular frequency as min (or max if it is higher) frequency so the CPU actually uses it.
And when you get a reboot then just use 25mV higher than the one with reboot.
I'd suggest to have fsync turned on when you fiddle with voltages because that will lessen the possibility of loss of data when phone reboots.
Another thing to have in mind is that even some combinations of frequencies do not work together. Some frequency might work OK with certain voltage with certain max/min frequencies but might not with other min/max frequencies. It looks like the actual change from one frequency to another (and depends from which to which) can determine a lot if a voltage is stable or not.
Also, it apparently very much depends on a ROM you use - different ROMs will probably need readjustment of voltage table.
Undervolting actually won't help much with battery life, smart reflex does a very good job already. It would help most if you game a lot or use your phone heavily, so then when higher frequencies are used the phone would get less hot and use slightly less power.
Otherwise, and especially if you change ROMs, I'd say it isn't worth the trouble.
nemotheblue said:
..................................
I've previously read droidphile's governors thread to which splus linked in their reply to your repost in Franco.kernel. In post #2, containing the governor tweaks (which I found very useful) even droidphile seems to have the wrong idea about the "hispeed_freq" parameter, stating:
..............................
Click to expand...
Click to collapse
Since there's lot of info to cover, mistakes can happen. I'll correct it if something is wrong.
Anyhow, if you check the interactive governor code,
if (!hispeed_freq)
hispeed_freq = policy->max;
This means if kernel default for the value of hispeed_freq=0, then it's assigned to policy_max aka scaling_max.
hispeed_freq is kinda like max_load_freq for ondemand.
Btw, input_boost is not available for interactive governor 'designed' for i9100 GS2 with Exynos chip. I don't know about Gnexus' Omap. Since i take one of the GS2 kernel as reference, governors params are kinda specific to i9100 and exynos architecture.
splus said:
Hi nemotheblue. Good post and findings!
I'm just looking at those voltage values you wrote - are you sure you turned off the SR?
...
I'd suggest to have fsync turned on when you fiddle with voltages because that will lessen the possibility of loss of data when phone reboots.
...
Undervolting actually won't help much with battery life, smart reflex does a very good job already. It would help most if you game a lot or use your phone heavily, so then when higher frequencies are used the phone would get less hot and use slightly less power.
...
Click to expand...
Click to collapse
@splus Wow, thanks for joining in on my little thread! Rest assured, before I started my tinkering I turned SR off and fsync on. I've read all 2306 pages of the Franco.kernel thread and avidly followed several conversations within it. I don't mind being a bit adventurous and trying out tweaks and mods; I just prefer to let other, more educated people try it first! I'm a measure twice, cut once kinda guy.
I followed rogersnm's undervolting saga in the Franco thread up to a couple of weeks ago, and recently caught up with his linaro thread, but I was as amazed as you seem to be at the tiny numbers he's currently reporting.
That being said, the voltages I reported were totally stable for me the last 3 days, until tonight. Tonight, I went to a double bill of Batman Begins and The Dark Knight - 5 hours in a huge, sold out cinema with easily 1,000 people. By the second movie, the room temperature was in the high 30s, if not 40C. I got an email, had a read, tapped back to inbox and BAM! The screen froze for about 3 seconds, then rebooted. The crazy thing is, I tried an hour later to reapply the undervolt and it froze straight away. I'm back on SR for a while, but I might try again tomorrow.
My original intention with the undervolting was just to drop the CORE, because I'm getting great performance from the 512GPU, but I notice the area under the camera on the back of the phone can get pretty hot if I'm playing games or watching a video for >30mins. Granted, I don't do that too often, but I figured it'd be nice to eliminate the extra heat. Once I saw the power saving calculations in rogersnm's chart, I was convinced to go the whole hog. The jury's out...
droidphile said:
Since there's lot of info to cover, mistakes can happen. I'll correct it if something is wrong.
Anyhow, if you check the interactive governor code,
if (!hispeed_freq)
hispeed_freq = policy->max;
This means if kernel default for the value of hispeed_freq=0, then it's assigned to policy_max aka scaling_max.
hispeed_freq is kinda like max_load_freq for ondemand.
Btw, input_boost is not available for interactive governor 'designed' for i9100 GS2 with Exynos chip. I don't know about Gnexus' Omap. Since i take one of the GS2 kernel as reference, governors params are kinda specific to i9100 and exynos architecture.
Click to expand...
Click to collapse
@droidphile Thanks for taking the time to reply. I didn't mean to sound like I was attacking your guide; I'd just read conflicting information from multiple other sources and played the numbers. I was labouring under the false assumption that all interactive governors are created equal. Is there some kind of official/original reference/guide/man page for the governors and their parameters, or are you devs left to interpret the code for yourselves?
I must admit, I'm more confused than ever now. I just can't reconcile your explanation with splus' claim that hispeed_freq=1037000 is the sweet spot for getting interactive to use the intermediate freqs up to a max well above 1036MHz???
nemotheblue said:
@splus Wow, thanks for joining in on my little thread! Rest assured, before I started my tinkering I turned SR off and fsync on. I've read all 2306 pages of the Franco.kernel thread and avidly followed several conversations within it. I don't mind being a bit adventurous and trying out tweaks and mods; I just prefer to let other, more educated people try it first! I'm a measure twice, cut once kinda guy.
I followed rogersnm's undervolting saga in the Franco thread up to a couple of weeks ago, and recently caught up with his linaro thread, but I was as amazed as you seem to be at the tiny numbers he's currently reporting.
That being said, the voltages I reported were totally stable for me the last 3 days, until tonight. Tonight, I went to a double bill of Batman Begins and The Dark Knight - 5 hours in a huge, sold out cinema with easily 1,000 people. By the second movie, the room temperature was in the high 30s, if not 40C. I got an email, had a read, tapped back to inbox and BAM! The screen froze for about 3 seconds, then rebooted. The crazy thing is, I tried an hour later to reapply the undervolt and it froze straight away. I'm back on SR for a while, but I might try again tomorrow.
My original intention with the undervolting was just to drop the CORE, because I'm getting great performance from the 512GPU, but I notice the area under the camera on the back of the phone can get pretty hot if I'm playing games or watching a video for >30mins. Granted, I don't do that too often, but I figured it'd be nice to eliminate the extra heat. Once I saw the power saving calculations in rogersnm's chart, I was convinced to go the whole hog. The jury's out...
@droidphile Thanks for taking the time to reply. I didn't mean to sound like I was attacking your guide; I'd just read conflicting information from multiple other sources and played the numbers. I was labouring under the false assumption that all interactive governors are created equal. Is there some kind of official/original reference/guide/man page for the governors and their parameters, or are you devs left to interpret the code for yourselves?
I must admit, I'm more confused than ever now. I just can't reconcile your explanation with splus' claim that hispeed_freq=1037000 is the sweet spot for getting interactive to use the intermediate freqs up to a max well above 1036MHz???
Click to expand...
Click to collapse
Yeah, if you do some gaming and more intensive stuff then it might be worth to find some good voltage values.
Still, those voltages seem pretty far from what hardware would be capable of running so that makes me think the SR check box wasn't really displaying its actual state somehow.
If you were using Franco's app did you check the last tab to see if mV values at certain frequencies were the same as in your table? If yes then I'm just amazed you were able to run it that way...
Anyway, good luck with further undervolting, please post your stable voltages when you find them...
If you have higher OC CPU frequency as max value in interactive (I'm talking about GNex, every chipset behaves differently) then it looks to me that if you set hispeed_freq to 1228000 the CPU would often just stay at that frequency, as if the system decides that it's enough to finish the job. But if you set it to 1037000 then it often determines it is not enough and scales the CPU to higher frequencies, and then you get the CPU to actually use higher frequencies as well.
Other direction would be to set hispeed_freq to even higher frequencies and that'll definitely make it more responsive but at a battery life cost.
The most responsive system would be that CPU goes to max whenever there's something happening. Google actually said at their IO that they tuned JB to go to max frequency at any touch but if you use the stock kernel and check CPU Spy charts you'll see that CPU goes initially only to 700 MHz.
There are other parameters, but it's all about finding a sweet spot for performance and battery life...
Needless to say, tuning all those governor parameters is greatly dependent on available frequencies, programmatically implemented governors and its parameters (which can be changed, a kernel developer can design and implement his own governor and its parameters) and especially chipsets and the way they behave. Every device is very different...
I think we would have better performance if there would be less frequencies in a kernel than currently in Franco's, but if the CPU is really efficient at scaling frequencies up and down through many steps all the time then maybe not.
Either case life goes on and I'm looking forward to see that new Batman myself in couple of days!
Fine folk of XDA,
Apologies for my long absence! I wasn't abandoning the thread; I got a call to work on a short film and had an insane 10 days of 13-16 hour working days and my brain was just too tired in the evenings to keep up with testing and tweaking. Plus, I needed my phone 24/7 stable to handle the continuous flow of calls, texts and emails from the production office.
So, I reverted to SR and dropped my max freq to 1228 and had no problems.
Catching up on the Franco thread tonight, I read a post by daggerxXxsin saying
I am running 600mv on 384-729 and 675mv on 1036-1228. Only works when I'm on 512gpu though. No random reboots or nothin'. Plays games like a champ and never heats up (temp never goes higher than 45°)
Click to expand...
Click to collapse
I'm currently trying these out on 729-1228 with SR off and fsync on, along with the following:
Code:
CORE -
512/384 - 900 mV
307 - 900 mV
153 - 825 mV
I'm gonna leave IVA alone on SR. I never really noticed any difference undervolting it before, and I figure if I'm pushing my MPU voltages so low, I'm just begging for crashes so it's best not to mess with anything that would affect I/O.
I'm currently running r225 512GPU, and I had some wifi issues where the indicator would frequently switch from blue to grey and lose the connection. However, having read some frequent posts in the Franco thread, I've switched from CWM to TWRP, wiped caches and reflashed Franco so I'll wait and see if the problem resurfaces.
BAH! Screw it, I just refreshed the Franco thread and r230 is out. Gonna flash and see how I get on...
Hi again nemo, just stumbled on this thread again
Wondering what posts indicate that CWM vs. TWRP recoveries would make a difference for the booted OS's Wifi/Google Services connectivity?
As I understand it JB in general just has a bit of a Wifi problem vs. ICS and even with ICS the Galaxy Nexus does vs. any other phone. I'm currently having acceptable Wifi using franco 241 (which has a new IO scheduler which makes things feel extremely snappy).
I'm pretty sure all I based that decision on was this discussion in the Franco.kernel thread. In retrospect, kinda half-baked but I must say I'm impressed with this recovery anyway!
I'm still following the thread religiously, rocking M5 at the moment though I'll likely jump on the first 512GPU nightly that comes out. I spent hours yesterday reading the MiNCO and MiNCO+ threads, very carefully backed up, then flashed v4 and immediately ran into this major roadblock and ended up reverting. Further study is required...
A few things come to mind with that storage problem:
1) Maybe that the sdcard bin (as is also in franco's cwm zips) is installed and messing things up weirdly. You'll need to push the stock one back (first post of franco.Kernel thread iirc).
2) A recent ROM Manager bug where .nomedia files were getting placed in the /sdcard/ top level folder, so you might want to investigate that with adb shell (though this would be weird considering you say you're using TWRP and ROM Manager is CWM).
3) Go to Apps > All > MediaStorage, Force Stop and clear data+cache. Reboot to have MediaScanner rebuild the MediaStore.
Edit: Just saw your post in the linked thread... looks like you tried 2+3... so try 1?
osm0sis said:
...1) Maybe that the sdcard bin (as is also in franco's cwm zips) is installed and messing things up weirdly. You'll need to push the stock one back (first post of franco.Kernel thread iirc)...
Click to expand...
Click to collapse
Very clever! Way to think outside the box, ossie :highfive:
I should have time to try again tonight, so I'll let you know how it plays out. While I'm at it, I'm excited to try out DarkJelly's inverted gapps, but I'll make sure to tackle the storage problem before flashing any apps/mods
So I couldn't wait!
I was unable to shake the feeling I might have just had a bad download of MiNCO, so I grabbed a fresh copy before I began. Flashed the ROM, Gallery worked fine. Flashed a navbar/battery icon mod, Gallery still ok. Gapps, no problem. Inverted apps, smooth sailing!
I now have a fully functional, customised ROM and no storage problem whatsoever. I must've just borked the first MiNCO download...
All's well that ends well
And I successfully tricked you into making your 10th post, so my work here is done! :laugh:
Now come join us in the main thread :good:
osm0sis said:
And I successfully tricked you into making your 10th post, so my work here is done! :laugh:
Now come join us in the main thread :good:
Click to expand...
Click to collapse
Nice one! :highfive: