Related
Hi, just wanted to know what is original HTC's ROM CPU scaling range and what is its CPU governor. My guess is 245-528, ondemand - is that correct?
Sorry, I don't know myself, but I'd like to know this too! I've just installed JokerDroid on mine, and I want to set it to stock frequencies so I can improve the battery life.
I'm using 352-691 ondemand, but I think 748 is ok too.
I think the min is 352MHz. But again, I am not so sure. (I arrived at this value when I was on the Stock ROM and used Android System Info which shows the various CPU frequencies and the time periods they operate on that frequency)
zigee said:
I'm using 352-691 ondemand, but I think 748 is ok too.
Click to expand...
Click to collapse
Isn't the max. for this device "528"
xXxeXtreme said:
Isn't the max. for this device "528"
Click to expand...
Click to collapse
Custom ROM's (Or, more appropriately - Custom Kernels) allow you to set a CPU Speed upto 768MHz.
BUT - The performance increase is not as great as the speed increase shows. So, if you do overclock, don't keep huge expectations.
zigee said:
I'm using 352-691 ondemand, but I think 748 is ok too.
Click to expand...
Click to collapse
I am running on 710 max, some people run on 768 max. But apparantly it is phone related because some people can perfectly run on 768 whilst I read a few days ago from a person here whose wildfire started force closing things around 710 or one higher or so.
Try a bit yourself which works for you. There are benchmarks that you can let run to see how often an error will occur approximately I have no link myself but I know a bud of mine did that to try how high he could go
At 691, some apps force closed, so I'm back to 595. It was stable for me.
gues that the 352MHz is the stock minimum then. There should be a noticable battery life increase when 122MHz is my current IDLE clock huh?
Now Iam running 122-710MHz on stock HTC ROM, very stable. If I set the frequency above 710MHz the scaling become unstable uner LOAD sometimes and dropping to 480MHz.
Using jacob kernel v4.
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:
I just want to share my most stable maximum undervolting of my Wonder,
I did not say that I am the first one to post this, I know there are already successfully undervolted their phones.
I've learned this from Pepoluan post, I've forgot that thread already.
We all know that undervolting our device gives advantages, such as extending battery life, increases power supply, extends the life of the device and less heat.
Here's what i've used.
1. Latest CM9 Rom (cm9-20130603-UNOFFICIAL-ancora) by our master Arco68
2. Kernel capable for unvervolting- I'm using HurtSky's kernel ( 3.0.82ICSHurtSky V 3.5)
3. IncrediControl app from playstore
So here are the tabulation below:
HTML:
Frequency Default V UV(My Setting) Difference % Savings
122880 900 750 150 16.7%
245760 900 750 150 16.7%
368640 900 750 150 16.7%
768000 1050 825 225 21.4%
806400 1100 925 175 15.9%
1024000 1200 925 275 22.9%
1113600 1200 975 225 18.8%
1209600 1200 1025 175 14.6%
1305600 1225 1050 175 14.3%
1401600 1250 1100 150 12.0%
1516800 1250 1150 100 8.0%
1612800 1275 1200 75 5.9%
1708800 1300 1275 25 1.9%
1804800 1325 1325 0 0.0%
I have conducted a stress test for every frequency to determine its most stable voltage.
TIPS:
- Use minimum frequency of 368 MHz since they have the same voltage with 122 and 245.
Advantage
- Improves scrolling ( based on my experience)
- Music clarity (also based on my experence)
- Launching Apps is much faster ( again based on my experience)
Disadvantage
- please let me know
Please, if you want to use this set up on your phone, please dont blame me if your phone crashes.
Please conduct a stress test first for every step down on undervolting for every frequency and here is the a Quick Guide below:
Quick Guide - Undervolting
What you need:
1. KERNEL - Capable for UnderVolting.
2. IncerdiControl App
3. Apps for Stress Test or Heavy Games or Benchmarking Apps.
4. Patience.
STEPS
1. Set the minimum frequency and maximum frequency of the CPU - the minimum should be the lowest existing frequency of the cpu and the maximum should be 1 step higher than the minimum (sample: min= 122MHz and max = 245 MHz)
2. Open IncrediControl app and set each frequency by 1 step down ( less 25 each),
3. Then apply, do not apply at boot first, ( so when it crashes it will revert back to the default settings)
4. Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
5. When it passed, repeat steps 2, 3, 4 until your phone crashes.
6. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
7. Record now the stable lowered voltage.
8. Next, increase the maximum frequency by 1 step higher (not the voltage).
9. The minimum frequency should be set to the recorded safe lowered voltage.
10. Open IncrediControl and set the voltage of the maximum frequency only by 1 step down (less 25).
11. Then Apply, do not apply at boot first,
12.Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
13. When it passed, repeat steps 10, 11, 12 until your phone crashes.
14. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
15. Repeat steps 8, 9, 10, 11, 12, 13 and 14 for the remaining frequencies, until you have determined the stable lowered voltages for each frequencies.
16. Now, after you have determined the undervoltage, apply it to your phone, no not apply first at booth,
17. Observe and stress test your phone for at least 1 hour.
18. if it will not crash anymore, you have now the Stable Undevoltage.
19. To be more safe, for daily use, increase the voltages by 1 step for each frequencies, except those which did not changed the value.
20. You can now apply the settings at boot.
21. Enjoy.
Note:
If your phone became unresponsive or vibrates continuously, that's the time that your phone is crashing, just turn off the phone, press the power for at least 10 seconds and it will turn off, or simply pull the battery.
TO THOSE WHO HAD SUCCESSFULLY UNDERVOLTED THEIR GALAXY W, MAY POST HERE AND MAY SHARE THEIR SETTINGS, SO SOME OF THE MEMBERS MAY GET AN IDEA.
Thanks to
Arco68
HurtSky
Pepoluan
honeyx
& Galaxy W Community
stock rom compatible?
Hi, thanks for sharing this:good:
Will i be able to use it with a rooted stock rom?
is stock rom capable of undervolting?
jakelq said:
I just want to share my most stable maximum undervolting of my Wonder,
I did not say that I am the first one to post this, I know there are already successfully undervolted their phones.
I've learned this from Pepoluan post, I've forgot that thread already.
We all know that undervolting our device gives advantages, such as extending battery life, increases power supply, extends the life of the device and less heat.
Here's what i've used.
1. Latest CM9 Rom (cm9-20130603-UNOFFICIAL-ancora) by our master Arco68
2. Kernel capable for unvervolting- I'm using HurtSky's kernel ( 3.0.80ICSHurtSky V 3.4)
3. IncrediControl app from playstore
So here are the tabulation below:
HTML:
Frequency Default V UV(My Setting) Difference % Savings
122880 900 750 150 16.7%
245760 900 750 150 16.7%
368640 900 750 150 16.7%
768000 1050 825 225 21.4%
806400 1100 925 175 15.9%
1024000 1200 925 275 22.9%
1113600 1200 975 225 18.8%
1209600 1200 1025 175 14.6%
1305600 1225 1050 175 14.3%
1401600 1250 1100 150 12.0%
1516800 1250 1150 100 8.0%
1612800 1275 1200 75 5.9%
1708800 1300 1275 25 1.9%
1804800 1325 1325 0 0.0%
I have conducted a stress test for every frequency to determine its most stable voltage.
TIPS:
- Use minimum frequency of 368 MHz since they have the same voltage with 122 and 245.
Advantage
- Improves scrolling ( based on my experience)
- Music clarity (also based on my experence)
- Launching Apps is much faster ( again based on my experience)
Disadvantage
- please let me know
Please, if you want to use this set up on your phone, please dont blame me if your phone crashes.
Please conduct a stress test first for every step down on undervolting for every frequency and here is the a Quick Guide below:
Quick Guide - Undervolting
What you need:
1. KERNEL - Capable for UnderVolting.
2. IncerdiControl App
3. Apps for Stress Test or Heavy Games or Benchmarking Apps.
4. Patience.
STEPS
1. Set the minimum frequency and maximum frequency of the CPU - the minimum should be the lowest existing frequency of the cpu and the maximum should be 1 step higher than the minimum (sample: min= 122MHz and max = 245 MHz)
2. Open IncrediControl app and set each frequency by 1 step down ( less 25 each),
3. Then apply, do not apply at boot first, ( so when it crashes it will revert back to the default settings)
4. Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
5. When it passed, repeat steps 2, 3, 4 until your phone crashes.
6. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
7. Record now the stable lowered voltage.
8. Next, increase the maximum frequency by 1 step higher (not the voltage).
9. The minimum frequency should be set to the recorded safe lowered voltage.
10. Open IncrediControl and set the voltage of the maximum frequency only by 1 step down (less 25).
11. Then Apply, do not apply at boot first,
12.Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
13. When it passed, repeat steps 10, 11, 12 until your phone crashes.
14. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
15. Repeat steps 8, 9, 10, 11, 12, 13 and 14 for the remaining frequencies, until you have determined the stable lowered voltages for each frequencies.
16. Now, after you have determined the undervoltage, apply it to your phone, no not apply first at booth,
17. Observe and stress test your phone for at least 1 hour.
18. if it will not crash anymore, you have now the Most Stable Undevoltage.
19. You can now apply the settings at boot.
20. Enjoy.
Note:
If your phone became unresponsive or vibrates continuously, that's the time that your phone is crashing, just turn off the phone, press the power for at least 10 seconds and it will turn off, or simply pull the battery.
Thanks to
Arco68
HurtSky
Pepoluan
& Galaxy W Community
Click to expand...
Click to collapse
Dude, these voltages are extreme!!! For gaming, these kind of voltages will surely crash the W. Well i tried putting 1.4/1.5GHz to 1175V and it crashed while playing Subway Surfers. Set at 1200V is stable enuff !
Sent from my GT-S6500 using xda app-developers app
lincoln_bw said:
Hi, thanks for sharing this:good:
Will i be able to use it with a rooted stock rom?
is stock rom capable of undervolting?
Click to expand...
Click to collapse
As far as i know, the stock rom is not capable for undervolting.
IncrediControl apps will work only for rooted phone and kernel capable for undervolting.
Thank you...
TiTAN-O-One said:
Dude, these voltages are extreme!!! For gaming, these kind of voltages will surely crash the W. Well i tried putting 1.4/1.5GHz to 1175V and it crashed while playing Subway Surfers. Set at 1200V is stable enuff !
Sent from my GT-S6500 using xda app-developers app
Click to expand...
Click to collapse
Yup, but this was the result after the tests and its really stable enough.
If you really want to check the stable undervoltage for 1.4GHz and 1.5GHz, you may set your minimum frequency to 1.4GHz and 1.5GHZ for the maximum frequency, undervolt it and check if it really crashes your phone.
Sometimes, crashes may caused by the low frequencies, not the maximum frequencies.
Thank you,
To be 100% sure you should check each frequency separately, not just lower all voltages at the same time by 25mV till it causes your phone to crash. For me I could lover the voltages for the lower frequencies more than for the upper frequencies. By saying this even not thinking about the oc frequencies, just the standard clock frequencies.
Also some games and benchmarks will be not enough to test stability. For me many games and benachmarks passed the voltages i set while testing but for example the facebook app freezed the phone after launching it. At some voltages the phone even could last for 3 days stable but crashed then, so the whole procedure took me a while till I found my stable undervolting settings.
honeyx said:
To be 100% sure you should check each frequency separately, not just lower all voltages at the same time by 25mV till it causes your phone to crash. For me I could lover the voltages for the lower frequencies more than for the upper frequencies. By saying this even not thinking about the oc frequencies, just the standard clock frequencies.
Also some games and benchmarks will be not enough to test stability. For me many games and benachmarks passed the voltages i set while testing but for example the facebook app freezed the phone after launching it. At some voltages the phone even could last for 3 days stable but crashed then, so the whole procedure took me a while till I found my stable undervolting settings.
Click to expand...
Click to collapse
+1
Maybe after determining the stable low voltage during stress tests, it would be safe to increase the voltage by 1 step higher for each frequency.
Thanks for sharing,
jakelq said:
+1
Maybe after determining the stable low voltage during stress tests, it would be safe to increase the voltage by 1 step higher for each frequency.
Thanks for sharing,
Click to expand...
Click to collapse
That´s what I also recommend. It doesn´t hurt to incrase all voltages by 25mV after finding the lowest stable values and will incrase stability a lot, as there always might be some small fluctuations while the frequencies are changing.
honeyx said:
That´s what I also recommend. It doesn´t hurt to incrase all voltages by 25mV after finding the lowest stable values and will incrase stability a lot, as there always might be some small fluctuations while the frequencies are changing.
Click to expand...
Click to collapse
Yup, I've already included your recommendation, that would be a great help.
Thanks for the recommendation.
Noob question, what is Undervolting?
Dhada said:
Noob question, what is Undervolting?
Click to expand...
Click to collapse
Are you seroius about this? It´s quite obvious when looking at the first post. It´s lowering the voltage of the CPU to reduce consumption and so also the battery drain.
honeyx said:
Are you seroius about this? It´s quite obvious when looking at the first post. It´s lowering the voltage of the CPU to reduce consumption and so also the battery drain.
Click to expand...
Click to collapse
Sounds to conflict
Dhada said:
Sounds to conflict
Click to expand...
Click to collapse
Baby steps!
I assume you play games and probably set ur phone clock speed stock at 1.4 GHz rite? Sometimes, you notice a huge battery drain after playing games like NFSMW or Modern Combat... Well, undervolt is for you to lower the voltages for EACH clock speed of your device to make battery last abit longer... Setting it too low may result in CRASHING or FREEZING and so u have this guide to show you the most stable undervolting thing... hope it helps CMIIW
Sent from my GT-I8150 using xda app-developers app
TiTAN-O-One said:
Baby steps!
I assume you play games and probably set ur phone clock speed stock at 1.4 GHz rite? Sometimes, you notice a huge battery drain after playing games like NFSMW or Modern Combat... Well, undervolt is for you to lower the voltages for EACH clock speed of your device to make battery last abit longer... Setting it too low may result in CRASHING or FREEZING and so u have this guide to show you the most stable undervolting thing... hope it helps CMIIW
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Nice i already did it
TiTAN-O-One said:
Dude, these voltages are extreme!!! For gaming, these kind of voltages will surely crash the W. Well i tried putting 1.4/1.5GHz to 1175V and it crashed while playing Subway Surfers. Set at 1200V is stable enuff !
Sent from my GT-S6500 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately, not all W's are equal; some are more equal than the others
What I meant was: the components are varying, quite so in fact that a W might survive at those very low voltages, while others give up the ghost and/or go crazy.
One have to test; therefore, great job for @jakelq for posting the complete procedure :thumbup:
-- sent from Samsung GT-I8150 running CM10 by Arco68
pepoluan said:
Unfortunately, not all W's are equal; some are more equal than the others
What I meant was: the components are varying, quite so in fact that a W might survive at those very low voltages, while others give up the ghost and/or go crazy.
One have to test; therefore, great job for @jakelq for posting the complete procedure :thumbup:
-- sent from Samsung GT-I8150 running CM10 by Arco68
Click to expand...
Click to collapse
Hey, where have you been?
Thank you, but you know the credit should go for you.
jakelq said:
Hey, where have you been?
Thank you, but you know the credit should go for you.
Click to expand...
Click to collapse
Had been extremely busy at work... I have to supervise so many things, I lost track of this Wonder-ful forum...
-- sent from Samsung GT-I8150 running CM10 by Arco68
pepoluan said:
Had been extremely busy at work... I have to supervise so many things, I lost track of this Wonder-ful forum...
-- sent from Samsung GT-I8150 running CM10 by Arco68
Click to expand...
Click to collapse
Glad you still find time for our community.
Thank you,
jakelq said:
I just want to share my most stable maximum undervolting of my Wonder,
I did not say that I am the first one to post this, I know there are already successfully undervolted their phones.
I've learned this from Pepoluan post, I've forgot that thread already.
We all know that undervolting our device gives advantages, such as extending battery life, increases power supply, extends the life of the device and less heat.
Here's what i've used.
1. Latest CM9 Rom (cm9-20130603-UNOFFICIAL-ancora) by our master Arco68
2. Kernel capable for unvervolting- I'm using HurtSky's kernel ( 3.0.82ICSHurtSky V 3.5)
3. IncrediControl app from playstore
So here are the tabulation below:
HTML:
Frequency Default V UV(My Setting) Difference % Savings
122880 900 750 150 16.7%
245760 900 750 150 16.7%
368640 900 750 150 16.7%
768000 1050 825 225 21.4%
806400 1100 925 175 15.9%
1024000 1200 925 275 22.9%
1113600 1200 975 225 18.8%
1209600 1200 1025 175 14.6%
1305600 1225 1050 175 14.3%
1401600 1250 1100 150 12.0%
1516800 1250 1150 100 8.0%
1612800 1275 1200 75 5.9%
1708800 1300 1275 25 1.9%
1804800 1325 1325 0 0.0%
I have conducted a stress test for every frequency to determine its most stable voltage.
TIPS:
- Use minimum frequency of 368 MHz since they have the same voltage with 122 and 245.
Advantage
- Improves scrolling ( based on my experience)
- Music clarity (also based on my experence)
- Launching Apps is much faster ( again based on my experience)
Disadvantage
- please let me know
Please, if you want to use this set up on your phone, please dont blame me if your phone crashes.
Please conduct a stress test first for every step down on undervolting for every frequency and here is the a Quick Guide below:
Quick Guide - Undervolting
What you need:
1. KERNEL - Capable for UnderVolting.
2. IncerdiControl App
3. Apps for Stress Test or Heavy Games or Benchmarking Apps.
4. Patience.
STEPS
1. Set the minimum frequency and maximum frequency of the CPU - the minimum should be the lowest existing frequency of the cpu and the maximum should be 1 step higher than the minimum (sample: min= 122MHz and max = 245 MHz)
2. Open IncrediControl app and set each frequency by 1 step down ( less 25 each),
3. Then apply, do not apply at boot first, ( so when it crashes it will revert back to the default settings)
4. Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
5. When it passed, repeat steps 2, 3, 4 until your phone crashes.
6. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
7. Record now the stable lowered voltage.
8. Next, increase the maximum frequency by 1 step higher (not the voltage).
9. The minimum frequency should be set to the recorded safe lowered voltage.
10. Open IncrediControl and set the voltage of the maximum frequency only by 1 step down (less 25).
11. Then Apply, do not apply at boot first,
12.Conduct a stress test or play heavy games or run a benchmarking apps to test the stability.
13. When it passed, repeat steps 10, 11, 12 until your phone crashes.
14. The previous lowered voltage before your phone crashes will now be the most stable undervoltage.
15. Repeat steps 8, 9, 10, 11, 12, 13 and 14 for the remaining frequencies, until you have determined the stable lowered voltages for each frequencies.
16. Now, after you have determined the undervoltage, apply it to your phone, no not apply first at booth,
17. Observe and stress test your phone for at least 1 hour.
18. if it will not crash anymore, you have now the Stable Undevoltage.
19. To be more safe, for daily use, increase the voltages by 1 step for each frequencies, except those which did not changed the value.
20. You can now apply the settings at boot.
21. Enjoy.
Note:
If your phone became unresponsive or vibrates continuously, that's the time that your phone is crashing, just turn off the phone, press the power for at least 10 seconds and it will turn off, or simply pull the battery.
TO THOSE WHO HAD SUCCESSFULLY UNDERVOLTED THEIR GALAXY W, MAY POST HERE AND MAY SHARE THEIR SETTINGS, SO SOME OF THE MEMBERS MAY GET AN IDEA.
Thanks to
Arco68
HurtSky
Pepoluan
honeyx
& Galaxy W Community
Click to expand...
Click to collapse
nice and gonna try it soon, just wanna ask, if i change to another kernel, then i have to reset it again?? .. anyway thankss
jakelq said:
Glad you still find time for our community.
Thank you,
Click to expand...
Click to collapse
Going back here feels like coming back to a family... a slightly dysfunctional family, but still a family nonetheless
Just like some other senior members ; they maybe without a W for some time, but they keep peeking in every now and then, just to enjoy the camaraderie and help people when they can...
hanafi200 said:
nice and gonna try it soon, just wanna ask, if i change to another kernel, then i have to reset it again?? .. anyway thankss
Click to expand...
Click to collapse
Most probably so; a different kernel might stress the system in different ways compared to the previous kernel. What works with one kernel might not be stable with another kernel.
However, if you're using IncrediControl, the app saves the voltage settings so you can start from those numbers instead of starting from scratch. Unless you go Pristine™ of course... in which case I suggest you manually saving the numbers somewhere safe.
-- sent from Samsung GT-I8150 running CM10 by Arco68
Has anyone tried to undervolt his Note 8?
I'll be undervolting my N5110 soon...
So, am I the first one to it or what?
Please share your sets.
Here's my settings. I run CivZ ROM with built-in kernel
I messed with the same rom... yes I undervolted and overclocked and done as much as I could do. Went back to 4.2.2 stock and still get about the same performance, and battery life. One thing that I could not live without, is my 64gb SD card. Too many issues with FAT32 and my music and video files. EXFAT is the only way to go with 64gb SD cards. With my stock ROM, I get 8 to 10 percent every hour, and 15 percent every hour playing HD video through miracast to my TV.
I'm doing it right now, following this guide (not as closely as I should, most likely).
@Alastor_ru : how did you get your values? Mine are generally lower, besides the fact that Voltage Control allows 850 mV as a minimum.
Thanks, but what about the higher freq's voltages
I think that you have up to 1.9 GHZ or 1.8 at least
@bradipovsky, that's the same guide I will follow
bradipovsky said:
@Alastor_ru : how did you get your values? Mine are generally lower, besides the fact that Voltage Control allows 850 mV as a minimum.
Click to expand...
Click to collapse
I use SetCPU, it has 600mV as a minimum.
I perform several steps while set voltage to lower and lower values and stop to play with it, when I get my current settings. As I noticed, the biggest power eater is the screen, so undervaluing doesn't bring the big savings
AhmadLight said:
Thanks, but what about the higher freq's voltages
I think that you have up to 1.9 GHZ or 1.8 at least
Click to expand...
Click to collapse
I don't use the highest freq's, cause it's not needed for me. I limit the highest CPU freq to 1GHz.
Alastor_ru said:
I use SetCPU, it has 600mV as a minimum.
I perform several steps while set voltage to lower and lower values and stop to play with it, when I get my current settings. As I noticed, the biggest power eater is the screen, so undervaluing doesn't bring the big savings
I don't use the highest freq's, cause it's not needed for me. I limit the highest CPU freq to 1GHz.
Click to expand...
Click to collapse
Well, 8" of screen of course don't help the battery I'm doimg it mainly to limit the heating, so high frequencies are the most important. I think it's a better option than underclocking, but that's just my opinion.
I'll share my values later, but I don't think they're ideal yet.
Which kernel is best for performance?(for Whyred)
1. Black box
2.no name
And many out there???
Suggestions please.
Thanks in advance.
Deep.cdy said:
Which kernel is best for performance?(for Whyred)
1. Black box
2.no name
And many out there???
Suggestions please.
Thanks in advance.
Click to expand...
Click to collapse
You should try them and find out the most suitable for you, use them for 1-2 days, you'll see the difference.... personally, I'm using NoName kernel with RR
NoName for Lineage based.
Deep.cdy said:
Which kernel is best for performance?(for Whyred)
1. Black box
2.no name
And many out there???
Suggestions please.
Thanks in advance.
Click to expand...
Click to collapse
i think currently is noname.
we hope a bunch of recognised developers in the near future as franco as many others.
Kirks, for battery...
Dude unlocked the lower cpu freqs...
m666p said:
Kirks, for battery...
Dude unlocked the lower cpu freqs...
Click to expand...
Click to collapse
It operates on lower Volts using this unlocked freqs?
peter-k said:
It operates on lower Volts using this unlocked freqs?
Click to expand...
Click to collapse
God knows, but what I do know is that it should produce less heat at the very least and it performs pretty gud on powersave governor. The gpu on the other hand is garbage at min freq (160mhz), even the launcher lags....
peter-k said:
NoName for Lineage based.
Click to expand...
Click to collapse
But after flashing no name 1.3 the WiFi doesn't work for me on rr 12th June
Deep.cdy said:
But after flashing no name 1.3 the WiFi doesn't work for me on rr 12th June
Click to expand...
Click to collapse
Mine was fine but now I'm on Aosip.
i think for now the best is to use a stock kernel, be careful with the charging limits.
peter-k said:
It operates on lower Volts using this unlocked freqs?
Click to expand...
Click to collapse
m666p said:
God knows, but what I do know is that it should produce less heat at the very least and it performs pretty gud on powersave governor. The gpu on the other hand is garbage at min freq (160mhz), even the launcher lags....
Click to expand...
Click to collapse
Of course it operates at lower voltage as it's a lower frequency and requires less power draw. Lower voltages should mean lower heat, however you don't magically get that lower freqs to operate, you need to tweak the interactive governor to make use of them all efficiently. So far I'm on Kirks kernel and AOSiP and it's a quite good combo.
The lag is not caused by low GPU freqs, it's because of low CPU freqs for that particular load, so governor tweaking is needed.
Cirra92 said:
Of course it operates at lower voltage as it's a lower frequency and requires less power draw. Lower voltages should mean lower heat, however you don't magically get that lower freqs to operate, you need to tweak the interactive governor to make use of them all efficiently. So far I'm on Kirks kernel and AOSiP and it's a quite good combo.
The lag is not caused by low GPU freqs, it's because of low CPU freqs for that particular load, so governor tweaking is needed.
Click to expand...
Click to collapse
Lol, I tested what you said out. Because you said it with such confidence...
I changed the cpu governor to performance and set the gpu to 160mhz max...
That made the experience a bit better but it would still lag a lot in recents and app launcher scrolling...
I've attached a screen shot to prove it too...
Another thing, just because the clock is lower does not mean that the voltage is lower as well, many devices that ive owned over the years have had the same voltage's for lower clocks( moto g2, Sony xperia z1)
And lastly, you should "magically" get those lower frequencies(if they are truly unlocked) since governors will always operate within the min/max frequencies that are set by the user or by default(unless it reverts parameters back to stock, like our device does on interactive)...
Forgot screenshot....
m666p said:
Lol, I tested what you said out. Because you said it with such confidence...
I changed the cpu governor to performance and set the gpu to 160mhz max...
That made the experience a bit better but it would still lag a lot in recents and app launcher scrolling...
I've attached a screen shot to prove it too...
Another thing, just because the clock is lower does not mean that the voltage is lower as well, many devices that ive owned over the years have had the same voltage's for lower clocks( moto g2, Sony xperia z1)
And lastly, you should "magically" get those lower frequencies(if they are truly unlocked) since governors will always operate within the min/max frequencies that are set by the user or by default(unless it reverts parameters back to stock, like our device does on interactive)...
Click to expand...
Click to collapse
First of all, we are talking here about difference in voltage between stock minimum freq for big cluster, which is 1.1ghz and actual possible minimum which is 300mhz, and there is a difference in voltage, that was the point. The devices I owned, S5 and Z3compact had more CPU steps, therefore the difference between some of the steps was really small or there wasn't any, but the CPU scaling made a jump to the freq with bigger difference (higher or lower, that was the stock behavior so some freqs weren't used). Here it might use all of the freq steps as there are less of them and the difference in voltage is significant enough, which might be the case, I said that because of my experience with previous devices. But you've missed the point anyway, I have said that even if unlocked, some freqs won't be used just because they are there if the governor parameters aren't set properly (or will be barely used). That was my point, I said that as a general note, so users won't jump the gun and blame devs for whatever.
And another one, regarding your test and lag with GPU, now I'm confused why would you set your max at 160mhz? I know it was for testing purposes in this case, but you did complain about it in original post and I said it won't lag because the max would still be set to 430mhz in which case the GPU freq scaling would do the job which it does very good so far. It would lag of course if you set max GPU freq to 160, but that's not what would you do for daily usage, right? Sorry if I misunderstood something.
Cirra92 said:
First of all, we are talking here about difference in voltage between stock minimum freq for big cluster, which is 1.1ghz and actual possible minimum which is 300mhz, and there is a difference in voltage, that was the point. The devices I owned, S5 and Z3compact had more CPU steps, therefore the difference between some of the steps was really small or there wasn't any, but the CPU scaling made a jump to the freq with bigger difference (higher or lower, that was the stock behavior so some freqs weren't used). Here it might use all of the freq steps as there are less of them and the difference in voltage is significant enough, which might be the case, I said that because of my experience with previous devices. But you've missed the point anyway, I have said that even if unlocked, some freqs won't be used just because they are there if the governor parameters aren't set properly (or will be barely used). That was my point, I said that as a general note, so users won't jump the gun and blame devs for whatever.
And another one, regarding your test and lag with GPU, now I'm confused why would you set your max at 160mhz? I know it was for testing purposes in this case, but you did complain about it in original post and I said it won't lag because the max would still be set to 430mhz in which case the GPU freq scaling would do the job which it does very good so far. It would lag of course if you set max GPU freq to 160, but that's not what would you do for daily usage, right? Sorry if I misunderstood something.
Click to expand...
Click to collapse
I kinda get what you mean, but the min freqs should kick in by default. They don't though on kirks, you need to change the governor to something like alucard or zzmove once before it actually starts clocking down to 300mhz...
On a side I would just disable the big. Cluster if I could, I don't really need that much cpu performance...
I was trying to find the min gpu freq that would be usable and I was disappointed, cuz my Sony z1 had a smooth ui experience with the gpu clocked at 200mhz max and that thing had a sd800...
Btw, I do all this to get better battery life...
I found out something else, I can't use power save governor any more because it can't handle audio processing(ainur, v4a) when the screen is off...
Just like my old z1, Lol...
Makes me think that the performance is really identical to the snapdragon 800...
I wonder how pissed I would be if a I got the redmi 5 plus, the 625 would have been even worse...
m666p said:
I kinda get what you mean, but the min freqs should kick in by default. They don't though on kirks, you need to change the governor to something like alucard or zzmove once before it actually starts clocking down to 300mhz...
On a side I would just disable the big. Cluster if I could, I don't really need that much cpu performance...
I was trying to find the min gpu freq that would be usable and I was disappointed, cuz my Sony z1 had a smooth ui experience with the gpu clocked at 200mhz max and that thing had a sd800...
Btw, I do all this to get better battery life...
Click to expand...
Click to collapse
m666p said:
I found out something else, I can't use power save governor any more because it can't handle audio processing(ainur, v4a) when the screen is off...
Just like my old z1, Lol...
Makes me think that the performance is really identical to the snapdragon 800...
I wonder how pissed I would be if a I got the redmi 5 plus, the 625 would have been even worse...
Click to expand...
Click to collapse
Yeah I agree, it should, but how much it stays on minimum freq is dependent on couple of governor parameters (talking about interactive). On mine though it does stay on 300mhz when idling, on stock Kirks settings. Big cluster can be disabled through new hotplug solution, like Intelliplug, which I used on my old devices, and it performed great, 1 core was active when screen was off, screen on and light usage required only 2 cores, while all 4 were active under heavy load. Here however there is only Qualcomm's hotplug solution, until that changes, no luck. Regarding GPU freq, I don't think any device would work smoothly under 200mhz, you can set 266mhz here, it will be smooth, I've tested today, on my old SD801 it performed at 233mhz IIRC.
I've seen that, V4A requires higher freq than 300mhz, or even 422mhz which SD801 had, it's more about the freq rather than the chipset, as I've read on multiple threads that even the devices with SD820 were struggling a lot when processing audio at 300mhz when the screen was off. Don't worry, it's a general issue. There is also the optimization of the rom and audio mods as well, background tasks, kernel, it all goes into the mix.
This is actually a very good chipset, it's technically SD660 just with lower clocks on both CPU and GPU.
EDIT: I forgot, this is my usage on AOSiP + Kirks, stock interactive tunables, min freq 300mhz (big/little), GPU initial/min freq 160mhz, max 430mhz. Using microG instead off GApps, I have used FB, Instagram, Messenger app for 1,5h each, Viber was couple of hours, Chrome some 30mins, Panini sticker album 30+ minutes, 30 minutes of 2G calls. Network mode was LTE, though I was on wifi on whole charge.
Started measuring from 92%.
Thanks bro, that explains a lot...