Hello.
Undervolting your CPU has always been a daunting task - there's so many CPU steps, if you pick say -100mV to all frequency steps and you get a reboot, how do you work out which step (or steps!) is causing the problem? If you undervolt -25mV on one frequency, then wait a couple of days to make sure it's stable, then reduce the same frequency by another 25mV.. you'll still be undervolting a year later.
This thread is my tutorial on how to do a best effort at quickly and safely undervolting your phone CPU.
First of all - is undervolting your CPU worth it?
Initially it was thought not to make much difference, but after some serious testing (thanks AndreiLux), "we" decided that it was a good idea. I also did my own basic testing, and it looks like it's worth it.
What are the advantages of undervolting?
Better battery life
Cooler phone, especially useful if you overclock your CPU
What are the disadvantages of undervolting?
That's the great thing! Really the worst that can happen is your phone freezes or reboots. The steps below should eliminate all of that. Once you have undervolted your CPU to just above its freeze/crash levels, there are no disadvantages!
Note: I have had some minor data loss (eg an app forgets a setting) after an undervolting related crash, but it was rare and I believe has to do with the Perseus kernel "Enable dynamic FSync" setting. I note below how to mitigate against this.
What do you need?
A rooted phone, and a kernel that supports undervolting. Perseus and Siyah will work, but any kernel should be fine that supports SetCPU's undervolting schema
SetCPU or you can use a combination of STweaks and Stability Test (use STweaks for setting the frequency and voltage, and use Stability Test's Classic Test for the stress test)
A paper and a pen - I used Sticky Notes as I was at a computer for most of the process
Some patience
Let’s begin.
Open SetCPU. You’ll be greeted by the Main screen which has the min/max CPU frequencies, the governor options, and the IO scheduler options. Reduce the max CPU frequency to the lowest step. On the SGS3 this will be reducing 1400MHz down to 200MHz, so you now have both the min and the max set at 200MHz. The phone will get pretty slow at this point. Ensure the Set on Boot option is unticked
Set the governor to Performance (note: you have to make sure all cores of your CPU are being used. In a complex kernel such as Perseus, you'll have to go into STweaks and set the CPU hotplug lock to 4 so all 4 cores are used. Also note there appears to be a bug in Perseus at the time of writing: you have to set the hotplug lock BEFORE you change the governor to performance)
Move to the Voltages screen
Ensure the Set on Boot option is unticked, and scroll down to the lowest setting, and change it to something low, like 700mV, and then apply it (click the third icon from the right at the top of the screen, a rectangle with a tick on it) . This first setting is always a bit of guess and check, and to be honest you’re hoping for the phone to freeze or crash on this first one. Has it frozen? If so move on to the next step. If not, reduce it by a further 25mV and apply again, repeat until your phone freezes or reboots.
So, you have undervolted too far. Reboot the phone, and perform steps 1-3 again. At step 4, use the voltage that crashed your phone +25mV (eg if it crashed at 675mV, this time set it to 700mV). Now, you have a very slow phone running a low voltage that doesn’t immediately crash it. Move on to the next step
An easy crash test I found was simply allowing the phone to go into deep sleep, and waking it up again. To do this, unplug your phone if it’s charging, and turn the screen off. At this point I usually wrote the time down on my piece of paper, as well as what frequency and voltage I was testing as I’m prone to forget these things. Wait 5 minutes with the screen off (and make sure no notifications have come in while the screen is off – this wakes the phone up and you’ll have to wait another 5 mins), then turn the phone on. You’ll know it’s gone into deep sleep as there’ll be a slight delay before the screen turns on as compared to no delay when turning it off and immediately back on again. If the phone doesn’t turn on, go to step 5. If your phone comes out of deep sleep OK, move on to the next step.
Now, we stress test. In SetCPU scroll over to the Info screen, and scroll down to the Stress Test option. Start it, and note down the time on your paper/Sticky Notes. Your CPU will now run as hard as it can at the current frequency. Let it run for 15-20 minutes. At the lowest frequency it will be pretty laggy and slow, if you think it has frozen always give it 30 seconds to see if it picks up again. If it gets stuck for over a minute, you probably have a crash. Go to step 5. If after 15-20 minutes it’s still running, you have found your first stable(ish) voltage for that frequency! At this point I saved the voltages in SetCPU by pressing the diskette icon. To ensure the changes are written to disk turn the phone screen off for 5 seconds then turn it back on again.
We are now ready for the next frequency. There’s pretty much no way a frequency will run stably on a lower voltage than a frequency below it, so our first voltage for the next frequency up should be the same stable voltage we found for the previous frequency. For example if we found a stable voltage of 725mV on the 200MHz frequency, our first test voltage for 300MHz should be 725mV. Write this down with the frequency on your paper. In the Main screen of SetCPU, change the max frequency to the next step up. Then, in the Voltages screen, adjust the voltage to be the same as the lower frequency, as discussed above. If your phone immediately freezes or reboots, move to the next step. If not, go to step 10.
So, you have undervolted too far, again! Reboot your phone, open up SetCPU, and in the main screen ensure the max frequency is set to the frequency we’re testing. Give the sliding bar things a jiggle to apply it. Ensure the governor is set to Performance by pressing it on the lower left part of the screen. Move to the Voltages screen, and you’ll either see your previous “saved” voltage values ready to be applied in dark grey under the “current” voltage settings, or you’ll have lost your “saved” voltage settings. If you have lost them, never fear; just restore the latest settings by clicking the first from the right icon at the top (a square with an arrow pointing outwards). Adjust the frequency we’re testing’s value to 25mV more than the value you last used when it crashed, and apply it. If it crashes immediately, repeat this step. If not, move on
We now start the two tests in steps 6 and 7 again, but this time if your phone crashes or freezes, go to step 9. If it completes the deep sleep and stress test tests, go to step 8 for the next frequency test.
Sorry for the complexity here, but it was the easiest way I could write it without repeating myself too much. The TL;DR version goes like this:
Pick the lowest untested frequency, set the max frequency to this and the governor to Performance, and find the lowest voltage that doesn’t immediately crash the phone
Put the phone into deep sleep, and see if it crashes. If it does, increase the voltage for the current frequency we’re testing by 25mV and test again. If not, move on
Run a stress test on the phone for 15-20 minutes. If it crashes, raise the voltage by 25mV and go to step B. If it doesn’t crash the current frequency is now tested. Go to step A
You now have a set of frequencies that shouldn’t immediately crash the phone. Set the min and the max frequencies back to normal, and set the governor back to your usual governor. At this point for me I was able to use the phone for about 2 hours before I had my first crash. How running a stress test on each frequency for 20 minutes didn’t pick up this crash situation I’m not sure, but it didn't.
After screwing around for a while I found the easiest solution was to just raise each frequency step by 25mV and then continue every day usage. That was enough to stabilise my phone. If it still crashes for you, keep raising all the values by 25mV until it settles down. After a day or two of no crashes you can start slowly one by one reducing each step by 25mV again to find out which step caused the crash.
After that, you should be done!
Ps I know there is another thread around here discussing undervolting, but I found it too vague on the details and sometimes wrong, so I thought I’d share my experiences in the hope it might help.
Good work!
Would you pls post your testing results for our reference?
Thanks.
Mod edit: please do not quote the OP.
A table with the running undervolting settings would be a great orientation help. Given that, people don't need to trail and error from scratch.
Sent from my Nexus 4 using xda app-developers app
me_max said:
A table with the running undervolting settings would be a great orientation help. Given that, people don't need to trail and error from scratch.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Under/over volting doesn't work that way. Each chip is unique, and chips are tested only on default voltage and frequencies, so each one's behavior on non-default settings is unpredictable. Some are able to work on 100 mV lower voltage, some can't handle even -25mV... Trial and error is the core of overclocking.
yep, that's one of the reasons i disagreed with the other UV thread - they list absolute voltage levels which are only applicable to the specific grade of chip in their phone (and yes, I posted some corrections in the other thread but they were ignored).
Have a look HERE if you'de like to see all the different possible default voltage settings for the i9300/i9305.
As a rough rough guide of a voltage level for the 200MHz step that will (hopefully) crash your phone, I'd start at 650mV.
i have tested my cpu
for stable values and i finished with these settings:
200Mhz - 0.775V
300Mhz - 0.800V
400Mhz - 0.825V
500Mhz - 0.850V
600Mhz - 0.875V
700Mhz - 0.900V
800Mhz - 0.925V
900Mhz - 0.950V
1000Mhz - 0.975V
1100Mhz - 1.000V
1200Mhz - 1.050V
1300Mhz - 1.100V
1400Mhz - 1.150V
1500Mhz - 1.200V
My exynos is stable for 2 months now, i play a lot of new games like most wanted etc.
In UV more important is leaving phone in idle, deep sleep on and off, or non demanding tasks, if i UV too much games were stable but i had random restarts when phone was in the pocket sleeping. But, as You mentioned, every cpu is different so everyone has to test it...
Thank you OP for this very, very useful guide. I am new to undervolting and even though I have a T999V north-american model with the Qualcomm SoC, this will prove very useful in my experimentation.
Only difference with the Qualcomm is that clock speed can go as low as 96Mhz, but you can't undervolt under 700mV - SetCPU just refuses to apply anything under that.
No probs
That's a kernel limitation, not SetCPU. Check with your kernel dev to see if they can allow further undervolting.
I tried to make the instructions as generic as possible so any stepping config could use them. good luck!
I'm doing my 96Mhz test and running a stress test.
The loading circle is still moving just fine (although a bit sluggishly) but none of my buttons are responding at all so I cant leave the test until I pull the battery. Would this count as a freeze/crash, or do you think this voltage is okay to stick at (or even go lower?!)
That's just the CPU bogging down, it's not a voltage issue.
hi guys. this might sound like a dumb question but i honestly looked everywhere but i cant seem to find the UV in setcpu. i'm i missing something?
Probably the kernel you're using doesn't support UV.
Hey
I find that 200 is stable on 687500
And then when I move to edit 300 it reboots
Then increased the number on both and still reboot.
I don't restart in between. Any idea??????
Sent from my GT-I9300 using xda app-developers app
tony1234567890tony said:
Hey
I find that 200 is stable on 687500
And then when I move to edit 300 it reboots
Then increased the number on both and still reboot.
I don't restart in between. Any idea??????
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
That means that 200 is NOT stable. Try using a higher voltage. 0.6875v is ridiculously low
TP.
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
tony1234567890tony said:
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Default voltage for 200mhz step is 0.9v (for me on asv2). So 0.7v (which is still higher than what you have set) it a whopping 200mv less than stock which is like I said before, ridiculously low. It may run at this voltage for you for now(depending on your as level), but I can pretty much guarantee you that it will never be 100% stable
I'll take your THC ; ) lol
TP.
Thanks I'll give you feed back
Sent from my GT-I9300 using xda app-developers app
omniwolf said:
Probably the kernel you're using doesn't support UV.
Click to expand...
Click to collapse
i thought the matr1x kernel supports it. UV works fine in trickster mod. i don't even have a heading for 'voltages' in the the app like it's shown in the play store.
tony1234567890tony said:
What do you mean low he says in the op to reduse to 700
THC for fast answear
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
yep, as STAticKY says, if you get a reboot on a step, then it's not stable. raise the voltage on that step and try again.
STAticKY said:
Default voltage for 200mhz step is 0.9v. So 0.7v (which is still higher than what you have set) it a whopping 200mv less than stock which is like I said before, ridiculously low. It may run at this voltage for you for now, but I can pretty much guarantee you that it will never be 100% stable
I'll take your THC ; ) lol
TP.
Click to expand...
Click to collapse
This is only correct for your ASV value. Please edit this post, it contains incorrect information. Your default voltage for 200MHz might be 0.9v, but for other people it's likely different, as they have different quality chips. Read post 3, 4, and 5 in this thread for more info.
genericuser2013 said:
i thought the matr1x kernel supports it. UV works fine in trickster mod. i don't even have a heading for 'voltages' in the the app like it's shown in the play store.
Click to expand...
Click to collapse
possibly the matirx kernel does support UV, but it might not be exposed in the way that SetCPU is expecting. Does the Matrix kernel developer recommend a specific app to adjust the voltages? If so use that, you can still follow my guide.
Can anybody tell me how to determine ASV-level of my chip?
I open this topic for a discussion of the performance and acceptance, famous hotplug ...
What is CPU Hot-plug?
Hot-plug by definition is adding or removing things without switching off the system. Say Add a hard disk to the system and increase it's storage capacity without switching off the system. CPU hot-plug means adding or removing CPU's from the system without switching off the system.
Why CPU Hot-plug?
This feature came in for servers which have so many CPU's and one or more CPU's may become faulty. And switching off the server and physically removing it may be costly for any business. CPU hot-plug helps here by hot-plugging out the CPU from the software so that nothing gets scheduled on the CPU once that is done the power rails of the CPU can be turned off from the software and later if need be, the CPU can be safely removed from the system.
Similarly, Adding CPUs.
Hot-plugging for Saving Power.
But, this feature is increasingly being used for saving power. We have so many mobile phone or tablets with 4-Core, 8-Core CPU's etc... But when the mobile is just idling in your pocket waiting for any call or when the tablet is in standby or playing a song, one really does not need the power of so many cores. So, Mobile/Processor makers nicely use the hot-plug mechanisms to turn off the CPU. When very lightly loaded or in standby the not-need cores are hot-plugged off. And added whenever needed. This way there is a lot of power saving achieved.
A bit of Internals.
Once it is decided that a CPU is going to be hot-plugged basic thing needs to be done. In a multi-processor system there are several processes running, or sleeping in every CPU. Which essentially means there could/will be some processes that are running or sleeping in the CPU that we would like to hot-plug. So, first thing to be done is to "migrate". The migration scheduler thread has to run and transfer all the running or sleeping processes into the other available cores. The isr's. We need to mention the interrupt controller that this core is no longer available for servicing interrupts if the core is capable of handling interrupts. This step is very architecture specific.
After this is done the architecture specific hot-plug code is invoked in arch/xxx/mach-xxx/cpuxxx.c. This will do what is needed in the specific chip to switch off the cpu rails and turn off or reduce to voltages according to the need.
When adding the core the same step is reversed. Once the hardware specific things are done the new CPU is added to schedulers domain and scheduler starts freely migrating threads into the new cpu.
Pitfalls of CPU Hot-plug:
When CPU Hot-plug is used for power saving, the major pitfall is the cpu not being available on time during sudden load conditions. It always take a while to predict the load, and latency in brining a CPU online and latency in moving a process to a new CPU. So, there can be instances in which we have a load and the CPU's are not yet added to the system to digest it. This might lead to some uneasy user experience. Even after paying money for a 4/8 CPU product the user may not have them when needed. But, this is not as bad as I have worded it. It is just a balance.
If there is a running task on a CPU which is going to be hot-plugged it has to be moved to another CPU. There is always a cache penalty associate with every migration as there will be no cache for this process in the per-cpu cache of the new processor where it has moved. Cache penalty is separate subject and it is very very architecture specific.
How and when to Hot-plug?
There is no simple answer or this. It is purely dependent on the SoC. Every SoC vendor have their own implementation of the logic. There are some open source implementations also available. Also, there are some multi-core SoC's which don't use CPU hot-plug for power savings.
I modify my kernel, each with a different version of hotplug, each will have to try it, and based on the experience rate, the hotplug with the most votes, will be the default hotplug my kernel.
FIRST VERSION
FenomenalMOD with MSM_ZEN DECISION
msm: add msm_zen_decision
This adds a simple driver intended to allow the MPDecision service to be disabled.
The driver is easily extendable, but currently it:
- Can be enabled/disabled in /sys/kernel/zen_decision/enabled
- On screen power OFF it removes all cpu cores after suspend_wait_time
- On screen power ON it enables all cpu cores.
- /sys/kernel/zen_decision/suspend_wait_time (ms) refers to how long we wait after screen is off to remove the cores (default 5s). This just to avoid removing cores in excess.
DOWNLOAD: ZEN-Hotplug
SECOND VERSION
FenokenalMOD with msm_hotplug
It will switch on more cores very quickly. In Dorimanx kernel, this hotplug can be heavily tweaked to be battery friendly to pure performance. With the right tweaks it is a very good choice for balanced performance.
DOWNLOAD: MSM Hotplug
THIRD VERSION
FenomenalMOD with Mako Hotplug
Basic Hotplug by francisco franco
DOWNLOAD: Mako Hotplug
FIVE VERSION
FenomenalMOD with AUTOSMP Hotplug (very good!!)
AutoSMP is a simple but effective hot plug governor by mrg666
You can modify this in sys/kernel/autosmp/conf
DOWNLOAD: AUTOSMP
SIX VERSION
FenomenalMOD with Bricked Hotplug(very good!!!)
Conservative hotplug driver by @showp1984
DOWNLOAD: BRICKED HOTPLUG
Please, try each before voting, Czech performance, battery, etc .... ALL DOWNLOAD IS FOR AOSP ROMS (CM, AOSP, PARANOIS, ETC=
Tested bricked Hotplug bestBatery backup with best performance, i accidentally voted mako
not working for stock?
DAVI FELICIANO said:
not working for stock?
Click to expand...
Click to collapse
No, its only for test
Msm & Mako!
Here's a tie, I'll add the 3 most voted hotplugs ...
DELETED
Hello
I am on a quest to find the best governor or kernel for me.
Firstly heres my ''specs'':
I am using I9505, on GE JFLTE-GPE 5.0.1 rom. Right now i have Hulk Kernel, but i have also tried Alucard/Goggy_Max.
I do not care if i have to flash kernels, etc. but i do not wish to change rom
I use my phone for Facebook, Snapchat, Messenger, Chrome, Gmail and loads of music. My music is on my MicroSD (64GB 95MB/s reads). i do NOT game on my phone.
My wish is for the most smooth performance of the above-mentioned, but it is also VERY important for me to have good battery life. Therefore i use Greenify and Amplify. I have limited many alarms/wakelocks, and greenified alot (not Messenger/Snapchat, because it stops notifications)
I do NOT own SetCPU, but i am using STweaks on Hulk Kernel right now.
I have usually used Ondemand governor, but found out yesterday that governors can do alot of difference, so i have shortly tried Badass, and trying SmartassH3 right now. I have been very satisfied with Ondemand governor, but i would be happy if i could get better battery life, with the same performance. For my GPU im trying 'Simple'' governor.
Furthermore ive considered the following governors; DanceDance, Badass, Ondemand, Yankactive, Smartmax, Impulse, SmartassH3 but i am not limiting myself to these, if you have other suggestions.
Thanks in advance
Links to my used Rom/Kernels
Goggy_max : http://forum.xda-developers.com/showthread.php?t=2741181
Hulk_Kernel : http://forum.xda-developers.com/galaxy-s4/i9505-develop/kernel-hulk-kernel-v1-stweaks-based-t3050469
GE Rom : http://forum.xda-developers.com/showthread.php?t=2557353
Alucard Kernel : Included as default in rom.
Here's a thread with explanation on pretty much all CPU governors and I/O schedulers.
Based on what you're saying, Intellidemand should be ok for you. It scales CPU based on the GPU load. So that means if your GPU is not working hard (gaming) your CPU should sit in lower frequencies.
SmartassH3 is more of a conservative governor.
You can even try the conservative governor. It was designed with battery in mind. Meaning that this governor prefers the lower CPU frequency. This also means less smoothness.
Another option is to activate one of the Intelli-Plug profiles from Hulk.
Eco performance is what I would suggest. It will turn your phone into a dual core phone but with some performance tweaks.
You could also try the other profiles and see what works best. But you get more battery savings by turning cores off or disabling them.
GDReaper said:
Here's a thread with explanation on pretty much all CPU governors and I/O schedulers.
Based on what you're saying, Intellidemand should be ok for you. It scales CPU based on the GPU load. So that means if your GPU is not working hard (gaming) your CPU should sit in lower frequencies.
SmartassH3 is more of a conservative governor.
You can even try the conservative governor. It was designed with battery in mind. Meaning that this governor prefers the lower CPU frequency. This also means less smoothness.
Another option is to activate one of the Intelli-Plug profiles from Hulk.
Eco performance is what I would suggest. It will turn your phone into a dual core phone but with some performance tweaks.
You could also try the other profiles and see what works best. But you get more battery savings by turning cores off or disabling them.
Click to expand...
Click to collapse
Hi
I tried the SmartassH3, but it seems it keeps rather high freqs? atleast it made my phone warmer than usual, so i am back to Ondemand until further. I activated the intelliplug and limited the cores to 2, and ive felt no performance loss yet. Which is great, so thanks for that tip
BTW, after ive begun with the governor tweaks, ive noticed my Poweramp decides to turn off when my screen is off? :/ It is not hibernated by Greenify, and Amplify has not limited either, so i do not understand why it stops. If i choose ''use wakelocks'' in Poweramp, it stays active. But this ofc. drains battery very quickly . Do you have any idea, what could be the problem here?
Check with an app to see how many cores you have active. Some said those settings don't work. For me they seem to work. But just to make sure.
When using poweramp the device will be awake anyway.
Governors should not have any effect on apps and how they run, except performance-wise. Governors can't put apps to sleep.
Poweramp requires the media service to run. Make sure you did not block that.
GDReaper said:
Check with an app to see how many cores you have active. Some said those settings don't work. For me they seem to work. But just to make sure
When using poweramp the device will be awake anyway.
Governors should not have any effect on apps and how they run, except performance-wise. Governors can't put apps to sleep.
Poweramp requires the media service to run. Make sure you did not block that.
Click to expand...
Click to collapse
I've already checked with Trickster MOD kernel settings, and verified it works
Ill check up on the media service. Do you know its exact name in Amplify?
amd62 said:
I've already checked with Trickster MOD kernel settings, and verified it works
Ill check up on the media service. Do you know its exact name in Amplify?
Click to expand...
Click to collapse
No, as I don't use Amplify.
after ALOT of tests, i think ive found out what happend. I limited the screen off max freq to 384MHz, and i think this was the problem. I will report back if it is NOT the problem. Else consider it solved
EDIT: Seems it was not. The search continues :I
Setting up Custom Kernels
*this information is helpful for anyone, everything written here, I have thoroughly tested, this guide is not laid out beautifully,I will rewrite it on my desktop pc soon.
There seems to be allot of confusion about how to set up
"Custom" Kernels for the Moto G 2015 (Osprey) for testing
This is mostly due to the following reasons :
Guides/info are Outdated
info usually Vague/Confusing for Novice
Guides are often for different hardware/software
Information is wrong or unfounded or based on speculation/theory
tunables for "performance" often do the opposite
But the biggest issue that Novices have seems to be
A lack of understanding that almost every tunable has
An equal opposite reaction (side effects)
Therefore balancing each tunable with each other is essential*
Getting Ready to bench
1 ) My First step is, head over to the Android Modders Guide (look in KA to see which Gov's & Scheduler's) and get familiar with the Govs & Sched's featured in the kernel your using
2 ) now that you're familiar with that open up KA and go to
To the hotplugging section, disable any hotplugging
For the reason that you want to be able to accurately test the performance/characteristics of The CPU and Governor in use (in order to properly tune the system.)
(If you want, turn it back on when your *COMPLETELY DONE TUNING*)
3 ) make sure that while testing your phone CPU freq and Gov
That you're IO ReadAhead cache is set to 128, that way it doesn't interfere or confuse you while trying to set the CPU.
4 ) Go to the misc tab, do you see "Dynamic Fsync" ?
If so turn that off, This will switch it back to Standard Fsync
So in the rare case of a system crash your less likely to damage your data.
5 )*(optional) in the IO tab, Disable add random, and then go to entropy tab and set to 64-192 or 128-256 depending on preference.
Now onto the benching itself
1 ) alright, open the CPU tab and check the Max CPU Frequency, if there is OC available make sure you Never Start your testing/tuning using the Highest OC Frequency
(We don't have a baseline yet and most chips will not be able to perform properly or stable at these higher OC freq's eg. Above 1.593 GHz) start testing with your Max CPU set to
1.363 GHz and work your way up testing each one for performance and stability(Geekbench 3 is a good start).
2 ) Do the same thing for Selecting a Governor for benching . (Your phone might get warm while benchmarking, if you feel Like your phone is getting too hot, this could effect performance turn the phone off for a while until it cools down. Also make sure you restart occasionally in between tests to refresh everything.)
3) in GPU Tab, this is going to be just like setting up the CPU with one exception, you'll want to stick with one of
these two GPU govs (simple_ondemand) & (Msm-adreno)
the other ones are experimental.
and another thing, if your overclocking gpu to max550-650
i recommend setting the min freq to 200 for 550 and 310 for 650mhz, to avoid heat due to ramping up and down.
4 ) alright now into the IO tab, this is where you pick the scheduler that you're going to test with, I suggest fiops or tripndroid. *.
5 ) start benchmarking, I suggest you do multiple tests of whatever your using to benchmark.
6 ) Have fun!
*understand that benching will eat battery, therefore make sure when you get settings you like, you do separate battery test on a full charge.
*once you get the tunables that you're comfortable with.
You can enable hotplugging if you want.
I will post my recommended tunables for the 1GB Osprey
Below...
__________________________________________________________
*if you're going to be doing GPU heavy tasks i recommend
disabling Adreno idler.
recommended tunable for Adreno Idler
(battery savings and cool GPU)
24
17
6
Hi everybody, I'm using an XT1642 with RR 7.1.1 but had the same problem with stock nougat too (I thought RR would help but it didn't): Serious lagging in Angry Birds Pop. GameBench shows fps usually around 20, while on my old Xperia Z1 Compact it's almost always 60...
Does anybody have an idea what might be the problem?
It's possibly an issue with the kernel not online-ing cores. Even so, it shouldn't lag that far behind the Z1 (even though the Z1 does have a faster CPU).
I recommend installing an app called "Kernel Adiutor", and manually change the minimum/maximum cores of the "big" cluster of the CPU, or even offline the big cluster and see if Angry Birds scales better on 4 cores.
Thank you! Setting "minimum cpus big" to 3 did solve the problem. I assume that shouldn't be kept this way because of the battery. Is there a way to have the setting changed to 3 when I open the app and back to 2 when I'm not playing? Like in getools?
berliner77 said:
Thank you! Setting "minimum cpus big" to 3 did solve the problem. I assume that shouldn't be kept this way because of the battery. Is there a way to have the setting changed to 3 when I open the app and back to 2 when I'm not playing? Like in getools?
Click to expand...
Click to collapse
There are a couple routes to this. There should be 2 variables within the Kernel Adiutor (I use EX kernel manager which is definitely worth a buy, the dev also develops the ElementalX kernels) that are called "Up Threshold" and "Down Threshold" for the big cluster. Essentially, "Up threshold" marks the CPU load at which the CPU begins to online the big cluster cores, while "Down Threshold" is the CPU load at which the CPU begins to offline big cluster cores.
I set the minimum to 0, and my up/down load levels are 60 and 45, respectively (I'm a super light user, just some reddit and clash royale), and my maximum is 4. However, lowering up and down load levels may help as the load at which the CPU onlines is much lower.
However, this may not work regardless. Some apps scale weird on octa-core CPUs; I know that Chrome was very, very janky on early big.LITTLE designs.
With EX Kernel manager flar built in a "performance" and "battery saving mode" which can be toggled via a desktop widget. I find it super useful if I'm using my G4 for VR. Essentially, you can set the max frequency and CPU governor per each mode. It is a paid app however, but the dev is great (he has a kernel out for the G4 as well) and well worth the price.
Thanks again, I will loot into it!