Database Info

CPU Freq: How do you keep yours?

This is a question I've never seen asked, but it's an important one. What are you phones CPU Freqs? What Govs do they have, and what Profiles do you use?
Rom: PyroIce
Main: 192 Min, 918 Max. OnDemand.
Screen Off: 192 Min, 384 Max. PowerSave.
InCall: 192 Min, 540 Max. Interactive.
Time 11pm-7am: 192Min/Max Powersave.
Sent from my HTC myTouch_4G_Slide using Tapatalk

that's cool, i might start using profiles again. from fiddling around i've noticed the difference between the ondemand and conservative governors- with ondemand, the processor seems to go from min. to all the way to max. and back down to min, and doesn't use the middle frequencies as much, while on conservative, the processor doesn't shoot up to max. as easily and seems to meander thru the middle frequencies a lot more. it makes sense too, because i've noticed that the phone seems snappier with ondemand.
i noticed you're using some of the others... i'll have to check them out as well.

ondemand
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed. - SetCPU website
conservative
Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery. - SetCPU website
performance
Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
to

so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?

yellowjacket1981 said:
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
Click to expand...
Click to collapse
Yeah Plus there's a huge difference with the Battery. I you use my CPU Settings, you should gain 3 hours Min on your phone. Also dropping the CPU in call is great, helps for longer calls and less overheating. If your S-Off you should use a custom kernel. UV Kernels are great.

AgentCherryColla said:
Yeah Plus there's a huge difference with the Battery. I you use my CPU Settings, you should gain 3 hours Min on your phone. Also dropping the CPU in call is great, helps for longer calls and less overheating. If your S-Off you should use a custom kernel. UV Kernels are great.
Click to expand...
Click to collapse
I actually just got an uv kernel, I am about to flash it, I will use your settings too, thanks.

yellowjacket1981 said:
I actually just got an uv kernel, I am about to flash it, I will use your settings too, thanks.
Click to expand...
Click to collapse
If you run a Sense 3.6 Rom, boost the CPU to 1Ghz. 918Mhz Lags.
Sent from my HTC myTouch_4G_Slide using Tapatalk

yellowjacket1981 said:
so, I bought set cpu about 3 phones ago, but I never really saw a differnence, can it be used with the stock kernel?
Click to expand...
Click to collapse
Yes.
You cannot use anything the kernel doesn't already serve as an option, though.
SetCPU doesn't create options - it allows you user-level access to the ones already existing.
Normally you have no control over your clock speed but with it you can...say... limit the maximum clock speed to only be two-thirds of the stock speed.
Since it doesn't ramp up all the way, it doesn't drain as much power.
If you are playing games and stuff that needs a lot of resources, then the slower clock speeds cost you battery since it takes more effort to get the same work done. But if you don't do much with your phone, and don't need a lot of high-end CPU ability, why let it run flat out?
You can also set it to be like that only sometimes, and maximize battery savings by telling your device to chill out when it doesn't have to be awesome.
Now, if you get into custom kernels where you or a dev has opened up more options, SetCPU will again give you user level control over them.
Especially once you get into overclocking beyond manufacturer(s) recommendations, not having some end-user level control over the processor like this is irresponsible.
If you think I run a 1.7 or 1.9 or 1.5+anything on the device flat-out balls-to-the-wall all the time, I would ask you if you drive your car with the gas pedal smashed to the floor all the time. (it's a fitting analogy)
No, again, that would be irresponsible abuse of the hardware for no good reason.
If not SetCPU, then there would be something else to use, but SetCPU is a great interface that not only works well but is maintaned within the XDA community by a member here.
I will always go for the XDA community member version of any app first - it's usually a problem solved from a perspective very near the way I am perceiving the issue, supports the community, and is always easier to find help on if necessary.
What's even cooler is SetCPU is given away free by the dev to XDA members.
I did go ahead and buy it anyway to support the dev. It is a fantastic tool at my disposal, and I have come to realize just how much time and energy goes into making this kind of stuff.
Beyond all that, though, there are a ton of crap apps and software out there slapped together by people who don't care or didn't put the right level of effort into their work. When I find something that actually works and works well after sifting through a sea of garbage, if there is a paid version of the app i'll usually buy it not only as a thank you but also to encourage that particular person to keep working. They - unlike many, many others (in my opinion) earned it.
I know i'm drifting off topic a bit, sorry for that - I just really appreciate quality work and SetCPU falls in with that crowd nicely.
Even without a custom kernel providing options beyond stock, there is still a lot of value this app can hold for anyone with root level access to their device.

Blue6IX said:
If you are playing games and stuff that needs a lot of resources, then the slower clock speeds cost you battery since it takes more effort to get the same work done.
Click to expand...
Click to collapse
Is this true? in my mind, I feel like it will take longer/not be as smooth, but wouldn't necessarily be worse for battery than a higher clock speed.

On a one-for-one comparison it leans more towards an even playing field, until you add that it's a dual-core processor and it very heavily skews the results towards less battery at higher clock speeds for complex operations.
Faster CPU speeds process the actions more quickly, and when you have to crunch a lot of numbers real quick like you do for most games the higher clock speed (especially on the dual core we are using) will complete the act with less power used. It is able to keep up with and/or outpace the flow of data being thrown at it.
If you are just using a notepad or browsing some forums maybe...sending a few texts? Then the higher clock speeds show a negative return on battery usage - you don't need it and it's wasteful.
But when the data has to stay buffered because the CPU is taking it's time working with it, not only is there more electricity consumed by keeping the processor alive longer but also the juice spent on keeping the data buffered.
The data computed is the same data computed at any speed (unless you lose data along the way...) but the power spent on completing that operation is not equal - not by a long shot.
On single core older processors where you are talking about a couple hundred megahertz one way or another the equation is much different, significantly diminshed returns on electricity invested, but with higher quality and multi-core processors especially they can cut through the data with significant ease when sufficiently powered.
But this is on processor intensive activities, and gaming is the first thing that comes to mind. For most other use of the device it's worth underclocking it and you will see battery gains.

[Q] Overclocking: Minimum/Maximum CPU Clocking Settings?

Running: Asus Transformer TF101 (with Tegra 2 chip)
OS: EOS Custom ROM 78 (Jelly Bean) -- And THANKS to 'em!
Short Question: What the heck are those minimum/maximum MHz settings' optimal numbers?
Long Question: My TF101 w/ EOS Nightly #78 has an overclocking feature in it. Very cool. There are not one, but TWO, separate settings for the chip -- a minimum MHz (starting at 200MHz or something) and a maximum MHz (all the way up to 1600MHz). But after I messed some with it (and like a dunce did not write down the original values) I experienced some random reboots, usually after I closed the lid a while and then reopened it.
So, my question's long version (which is actually a number of questions), follows...
* What are the original values of the Tegra 2 chip in one of these babies? I mean, 1000MHz (1Ghz) is probably the maximum default setting, since that's the chip's official rating. But what's the minimum setting supposed to be at?
* Can I do something as crazy as to tell it to run minimum of 1200MHz and maximum of 1600MHz? In fact, I'm trying that right now and it seems to be working.... but I doubt I'll leave it that way even if it does (makes me nervous about messing up the hardware).
* What optimal settings have others tried with this chip in this (TF101) unit.... or even in other Tegra 2 based tablets?
Thanks for reading. Looking forward to comments.

shonkin said:
Running: Asus Transformer TF101 (with Tegra 2 chip)
OS: EOS Custom ROM 78 (Jelly Bean) -- And THANKS to 'em!
Short Question: What the heck are those minimum/maximum MHz settings' optimal numbers?
Long Question: My TF101 w/ EOS Nightly #78 has an overclocking feature in it. Very cool. There are not one, but TWO, separate settings for the chip -- a maximum MHz (starting at 200MHz or something) and a maximum MHz (all the way up to 1600MHz). But after I messed some with it (and like a dunce did not write down the original values) I experienced some random reboots, usually after I closed the lid a while and then reopened it.
So, my question's long version (which is actually a number of questions), follows...
* What are the original values of the Tegra 2 chip in one of these babies? I mean, 1000MHz (1Ghz) is probably the maximum default setting, since that's the chip's official rating. But what's the minimum setting supposed to be at?
* Can I do something as crazy as to tell it to run minimum of 1200MHz and maximum of 1600MHz? In fact, I'm trying that right now and it seems to be working.... but I doubt I'll leave it that way even if it does (makes me nervous about messing up the hardware).
* What optimal settings have others tried with this chip in this (TF101) unit.... or even in other Tegra 2 based tablets?
Thanks for reading. Looking forward to comments.
Click to expand...
Click to collapse
Generally its all up to your specific chip and how much it can handle as all hardware isn't created equal especially Tegra soc's... the stock speed is 1GHz for the TF but could easily run higher... i would only run your min so high if doing benchmarking not everyday use.. it will kill your battery faster, it would tho benefit benchmarking Because it would run at the highest speed and not have a chance to jump to a lower speed... wont do any damage to the chip since it has built in thermal throttling anyways... my suggestion would be setting your min to the lowest and With the max speed start at 1.2GHz with some stability tests, or heavy use at different OC speeds to find your chips sweet spot with both stability, Battery life and performance.. and have fun

DJLamontagneIII said:
Generally its all up to your specific chip and how much it can handle as all hardware isn't created equal especially Tegra soc's... the stock speed is 1GHz for the TF but could easily run higher... i would only run your min so high if doing benchmarking not everyday use.. it will kill your battery faster, it would tho benefit benchmarking Because it would run at the highest speed and not have a chance to jump to a lower speed... wont do any damage to the chip since it has built in thermal throttling anyways... my suggestion would be setting your min to the lowest and With the max speed start at 1.2GHz with some stability tests, or heavy use at different OC speeds to find your chips sweet spot with both stability, Battery life and performance.. and have fun
Click to expand...
Click to collapse
I'm not sure where the "thanks" button is yet here, but will try to figure it out. Wait.... I just did.
Tonight I backed the minimum down to the 800 vicinity (whatever that number is) and left the top number at 1600. My recent test has been to run Angry Bird, which is not the most stable program. It runs just fine at this setting. The battery is draining fast, though.
So you are suggesting that taking it all the way to the basement minimum-wise will still give me fairly stable top end? I keep wondering if there's any relationship at all between the two numbers, if at some point they don't affect one another adversely if too far apart? This idea is based on no knowledge whatever.
So any furhter thoughts welcome.

shonkin said:
I'm not sure where the "thanks" button is yet here, but will try to figure it out. Wait.... I just did.
Tonight I backed the minimum down to the 800 vicinity (whatever that number is) and left the top number at 1600. My recent test has been to run Angry Bird, which is not the most stable program. It runs just fine at this setting. The battery is draining fast, though.
So you are suggesting that taking it all the way to the basement minimum-wise will still give me fairly stable top end? I keep wondering if there's any relationship at all between the two numbers, if at some point they don't affect one another adversely if too far apart? This idea is based on no knowledge whatever.
So any furhter thoughts welcome.
Click to expand...
Click to collapse
It is best to leave the min freq as per default and push only the max freq. Then, you can set application profiles whereby you will allow an oc if you play a specific app(this feature requires an app that is called setcpu). This is to allow you to gain the best battery life(what you did is okay as well, but you'll have less battery life as the proc is running at 800mhz at min)
Otherwise, you can do it manually by setting the governor. For example, when you want to play games, set the governor to performance and oc your proc. When you don't want to play games anymore, then set it back to interactive or ondemand(or any other suggested governor for your device) to allow battery saving

wcypierre said:
It is best to leave the min freq as per default and push only the max freq. Then, you can set application profiles whereby you will allow an oc if you play a specific app(this feature requires an app that is called setcpu). This is to allow you to gain the best battery life(what you did is okay as well, but you'll have less battery life as the proc is running at 800mhz at min)
Otherwise, you can do it manually by setting the governor. For example, when you want to play games, set the governor to performance and oc your proc. When you don't want to play games anymore, then set it back to interactive or ondemand(or any other suggested governor for your device) to allow battery saving
Click to expand...
Click to collapse
I have setcpu but after mucking about with it managed to end up with an unstable system (spontaneous reboots, esp. after closing then opening lid and "waking up" the TF101). Currently I'm just using the EOS Rom's own system settings and having low end all the way to minimum (200 something) and top end at 1500+. The 1600 mhz setting is apparently a problem for this machine (the spontaneous resets again). But at 1500 whatever it seems just fine
One other issue, very important to all of us (harhar), is that Angry Birds seems unstable since I updated to this custom EOS rom. I noted elsewhere that someone said simply turning off wireless would disable ads and stablize the game. I've not tried that yet. Losing angry birds for me would not be a major blow.

Thermal throttling and hotplug settings

I have been able to fix quite a bit of thermal throttling experienced in multiple benchmark runs by tweaking with the thermal-engine configuration file. With just a few changes and with the copper shim mod I can now run geekbench for as many five times with almost no drop in score. After that I get no thermal throttling in single core but I have it setup to disable two cores after it hits 55C CPU temp in core 4 and 7. I use CPU Z to see actual CPU temp from the sensor readings. Even after 8 Geekbench runs the two cores are still running at full speed and the phone is registering 44C. It's warm but not hot by any means.
If anyone is interested in playing around with it just look for the file in \System\etc\thermal-engine-8994.conf
Most of it is just two adjustments. One for Max temperature at which it will throttle and the one below is the temperature at which throttling stops.

probaina said:
I have been able to fix quite a bit of thermal throttling experienced in multiple benchmark runs by tweaking with the thermal-engine configuration file. With just a few changes and with the copper shim mod I can now run geekbench for as many five times with almost no drop in score. After that I get no thermal throttling in single core but I have it setup to disable two cores after it hits 55C CPU temp in core 4 and 7. I use CPU Z to see actual CPU temp from the sensor readings. Even after 8 Geekbench runs the two cores are still running at full speed and the phone is registering 44C. It's warm but not hot by any means.
If anyone is interested in playing around with it just look for the file in \System\etc\thermal-engine-8994.conf
Most of it is just two adjustments. One for Max temperature at which it will throttle and the one below is the temperature at which throttling stops.
Click to expand...
Click to collapse
Without your copper shim mod have you found any better but safe values we can try?
At least no thermal throttle until 55 celsiius

It should be safe without the copper shim. The thermal pad it comes with works pretty well. It will still thermal throttle to whatever temperature you set it at so it won't cause any harm.
I've set the Big cluster to a max of 65C and a single A57 core to up to 71C and haven't had any problems yet. I used to get horrible performance with PPSSPP emulator. When running Tony Hawk Project 8 in PPSSPP after 30 seconds of gameplay It used to drop to 6fps and now it can sustain over 20fps after reaching 71C on a single A57 core. I only saw a maximum battery temperature of 40C and the device wasn't noticeably warmer than it was with the default thermal settings.

probaina said:
It should be safe without the copper shim. The thermal pad it comes with works pretty well. It will still thermal throttle to whatever temperature you set it at so it won't cause any harm.
I've set the Big cluster to a max of 65C and a single A57 core to up to 71C and haven't had any problems yet. I used to get horrible performance with PPSSPP emulator. When running Tony Hawk Project 8 in PPSSPP after 30 seconds of gameplay It used to drop to 6fps and now it can sustain over 20fps after reaching 71C on a single A57 core. I only saw a maximum battery temperature of 40C and the device wasn't noticeably warmer than it was with the default thermal settings.
Click to expand...
Click to collapse
[SS-LITTLE_CLUSTER_management]
algo_type ss
sampling 10000
sensor xo_therm
device cluster0
set_point 52000
set_point_clr 42000
action_type 10000
I should change for example here set_point to 70000? This is how it works?

kutulu32 said:
[SS-LITTLE_CLUSTER_management]
algo_type ss
sampling 10000
sensor xo_therm
device cluster0
set_point 52000
set_point_clr 42000
action_type 10000
I should change for example here set_point to 70000? This is how it works?
Click to expand...
Click to collapse
Well yes. Except that's the little cluster and they don't get that hot normally. It's the big cluster that needs to be modified. I also tuned my display thermals so the screen wouldn't get so dim when the phone gets warm. Here you can look over my configuration if you want.
https://www.dropbox.com/s/1yve5d0m7uin0ga/thermal-engine-8994.conf?dl=0

probaina said:
Well yes. Except that's the little cluster and they don't get that hot normally. It's the big cluster that needs to be modified. I also tuned my display thermals so the screen wouldn't get so dim when the phone gets warm. Here you can look over my configuration if you want.
https://www.dropbox.com/s/1yve5d0m7uin0ga/thermal-engine-8994.conf?dl=0
Click to expand...
Click to collapse
Thanks i will try them!!

your settings somehow "unlocked" my phones cpu. lol in geekbench I found an increase of performance of 200 points in multicore from 4020 I had before maximum , now nearly 4300 .It is impressive. also if I run 6-7 geekbench in a row there is a decrease everytime ex 4200 4050 3900 3600..... but temperature stays 45 degree.
I will test them more later.
http://browser.primatelabs.com/user/73366

Someone try this?
Wysłane z mojego LG-H955 przy użyciu Tapatalka

Other than the two of us?

kutulu32 said:
your settings somehow "unlocked" my phones cpu. lol in geekbench I found an increase of performance of 200 points in multicore from 4020 I had before maximum , now nearly 4300 .It is impressive. also if I run 6-7 geekbench in a row there is a decrease everytime ex 4200 4050 3900 3600..... but temperature stays 45 degree.
I will test them more later.
http://browser.primatelabs.com/user/73366
Click to expand...
Click to collapse
Thanks for sharing your results. That's the highest multi core score I've seen on our phones. I never gotten that high of a multi core score. Glad to help. My configuration also tweaked the battery thermal settings so now you should see faster charge times as well. The default charge rates had really conservative thermal settings and the high speed charge would drop after a while but now it will 2.2 to 2.4 amp charge through the whole charge.

probaina said:
Thanks for sharing your results. That's the highest multi core score I've seen on our phones. I never gotten that high of a multi core score. Glad to help. My configuration also tweaked the battery thermal settings so now you should see faster charge times as well. The default charge rates had really conservative thermal settings and the high speed charge would drop after a while but now it will 2.2 to 2.4 amp charge through the whole charge.
Click to expand...
Click to collapse
Yes indeed i saw a difference in chargin thanks for your effort in the configuration. I am not very fond of benchmarks but i run some in my devices after magor changes (firmware....). This device should have been speedier because of the full hd snapdragon 810 combination. I wonder if we delete the thermal config is the device gonna be speedier? I am waiting for 5.1.1 hoping for smoother rom. Lets hope soneone unlocks the bootloader!!!! I took my precautions disabling MLT lol

probaina said:
Well yes. Except that's the little cluster and they don't get that hot normally. It's the big cluster that needs to be modified. I also tuned my display thermals so the screen wouldn't get so dim when the phone gets warm. Here you can look over my configuration if you want.
https://www.dropbox.com/s/1yve5d0m7uin0ga/thermal-engine-8994.conf?dl=0
Click to expand...
Click to collapse
My phone gets really hot with those settings
I overwrote the original one ^^ has someone made a backup and can share it with me.?

I guess it depends on what you're doing but I probably wouldn't play any 3d games with those settings. Here's a copy of the original one https://www.dropbox.com/s/yb76q6qwanb9ujr/thermal-engine-8994.conf?dl=0

smouker said:
My phone gets really hot with those settings
I overwrote the original one ^^ has someone made a backup and can share it with me.?
Click to expand...
Click to collapse
When you apply the settings you need to give time to the phone to 'absorve' them.
Run a couple of benchmarks, test a 4k video, reboot the phone 3-4 times, close it also.
I havent noticed higher tdmperature of 45 celsius.

kutulu32 said:
When you apply the settings you need to give time to the phone to 'absorve' them.
Run a couple of benchmarks, test a 4k video, reboot the phone 3-4 times, close it also.
I havent noticed higher tdmperature of 45 celsius.
Click to expand...
Click to collapse
I noticed that haha now its fine

kutulu32 said:
Yes indeed i saw a difference in chargin thanks for your effort in the configuration. I am not very fond of benchmarks but i run some in my devices after magor changes (firmware....). This device should have been speedier because of the full hd snapdragon 810 combination. I wonder if we delete the thermal config is the device gonna be speedier? I am waiting for 5.1.1 hoping for smoother rom. Lets hope soneone unlocks the bootloader!!!! I took my precautions disabling MLT lol
Click to expand...
Click to collapse
I'm not sure what would happen if you just deleted the file. Maybe it'll revert to some default, or perhaps it won't thermal throttle at all which would result in auto shut off when it overheats. Probably not worth risking it without a custom recovery in case it doesn't boot.
I have notice that my phone is way quicker now. It was fast before but now it's a beast when I push it hard. Also things like PPSSPP emulator was useless with the default thermal throttling now it can beat my Tegra note 7 with 4 A15 cores at 2.1ghz at it.

Was there a problem with your settings? I noticed your settings you had shared on dropbox are no longer available.

uh60james said:
Was there a problem with your settings? I noticed your settings you had shared on dropbox are no longer available.
Click to expand...
Click to collapse
The folder was deleted for some odd reason. I was able to restore it so the link should work now. Let me know how it works out for you.

A few questions about these settings.
-At the top where you have SS-Little_Cluster_management and SS-Big_Cluster_management is the set point the shutdown temp for the entire cluster?
-I think this one is self explanatory by the action listed but towards the middle where CPUx_MONITOR for each core is, is the threshold the temperature at which the entire phone shuts down?
-I'm not sure I am noticing the difference between SS-CPUx and CPU_HOTPLUG_MONITOR. Could you explain these?

uh60james said:
A few questions about these settings.
-At the top where you have SS-Little_Cluster_management and SS-Big_Cluster_management is the set point the shutdown temp for the entire cluster?
-I think this one is self explanatory by the action listed but towards the middle where CPUx_MONITOR for each core is, is the threshold the temperature at which the entire phone shuts down?
-I'm not sure I am noticing the difference between SS-CPUx and CPU_HOTPLUG_MONITOR. Could you explain these?
Click to expand...
Click to collapse
I don't want to assume I know everything about this. Everything I know about the thermal configuration file I learned from seeing others modify the LG G3 thermal config file. I also learned some by experimenting with my G Flex 2.
In my understanding SS-Little_Cluster_management and SS-Big_Cluster_management is the temperature at which the Cluster will thermal throttle when all cores in the cluster are being used at once. From what I've seen anything with "action_type 10000" means thermal throttle. The closest thing I can think off that works like that is how Intel I5 and I7 will limit turbo speed when more than one core is being used. Except in our case this is to prevent higher speeds when it reaches a certain temperature. So lets say your phone is running some heavy multithreaded app now it's going to follow the rules set in Cluster_management. The default Big Cluster temperature is set to start slowing things down when temperature reaches 48C and to not go back to full speed until the temperature drops down to 38C. One thing I find interesting is that at about 48C cluster temperatures was about where the Big cores would drop to a max of 1.5 ghz. So I'm just guessing that this setting may play a big part on the big cores max speed.
[CPUx_MONITOR] seems to shutdown the phone when the core reaches a certain temperature threshold of 120 C and I assume will not allow it to turn back on until it drops below 115C.
[SS-CPUx] on a big core seems to slow the specific core down when it reaches a temperature threshold of 85C and to not allow it to go to full speed until it drops below 55C. However this rule can be overwritten by [CPUx_HOTPLUG_MONITOR] which can shut down a core even if it hasn't reached it's maximum temperature threshold.
[CPUx_HOTPLUG_MONITOR] just tells the specific core to turn off once it reaches the temperature threshold specified. On the default configuration core 4 and 7 are set to turn off when their temperature goes above 50C. After that core 5 turns off at 58C and even core 6 turns off at 61C. At which point only the small cores will remain on.
I hope that helps somewhat.

Massive lag/performance improvement for rooted Joying (and other Rockchip) HUs

Must be rooted.
Install kernel adiutor.
Start Kernel Adiutor. You'll be met immediately with four graphs showing the load on all four cores.
Select "CPU"
What you will notice by looking at the CPU frequency graphs, is that the head unit spends most of it's time at a low clock frequency, typically 800MHz or so.
Select "governor". The default setting is probably "interactive". This is not a phone. Any governor setting that favors low energy consumption is not appropriate for an automotive head unit. The kernel governor's job is to throttle the clock speed up or down to meet demand. So when the device isn't doing anything, it can run at a lower speed and conserve battery.
Scroll down to and select "performance". This will lock the CPU at 1.6GHz.
Use the "apply on boot" switch to make kernel adiutor start up and apply the setting at every boot.
You will notice dramatically improved responsiveness (immediately) overall.
This should also work with MTCB units or other (non-Joying) units. You must be rooted.
If someone can provide screenshots of the CPU frequency graphs (before/after) I will add them. I am too lazy to run mine in the old state just for getting a picture of before/after, but in a couple of days I will try to add some pictures.
I don't know if the chip will eventually burn up. If it was designed properly, it won't. The Rockchip is used in millions of tablets and other devices, I suspect it is robust by now. It is also advertised on Joying's website as a 1.6GHz quad core, so why is it running at 800 MHz or lower all the time?
There may be a tradeoff, perhaps using ondemand? Would be worth playing around with the other governors and settings to find a way to get max speed only when it is needed. But then again, there may not be any reason to mess with this at all.
This is *not* overclocking and the kernel governor is not a secret. The performance governor will force the processor to run at its maximum advertised speed. I have been running mine this way for >1 week now with no ill effects.
Following these instructions is at your own risk, like almost everything on XDA.

@da_anton

wskelly said:
Must be rooted.
Install kernel adiutor.
Start Kernel Adiutor. You'll be met immediately with four graphs showing the load on all four cores.
Select "CPU"
What you will notice by looking at the CPU frequency graphs, is that the head unit spends most of it's time at a low clock frequency, typically 800MHz or so.
Select "governor". The default setting is probably "interactive". This is not a phone. Any governor setting that favors low energy consumption is not appropriate for an automotive head unit. The kernel governor's job is to throttle the clock speed up or down to meet demand. So when the device isn't doing anything, it can run at a lower speed and conserve battery.
Scroll down to and select "performance". This will lock the CPU at 1.6GHz.
Use the "apply on boot" switch to make kernel adiutor start up and apply the setting at every boot.
You will notice dramatically improved responsiveness (immediately) overall.
This should also work with MTCB units or other (non-Joying) units. You must be rooted.
If someone can provide screenshots of the CPU frequency graphs (before/after) I will add them. I am too lazy to run mine in the old state just for getting a picture of before/after, but in a couple of days I will try to add some pictures.
I don't know if the chip will eventually burn up. If it was designed properly, it won't. The Rockchip is used in millions of tablets and other devices, I suspect it is robust by now. It is also advertised on Joying's website as a 1.6GHz quad core, so why is it running at 800 MHz or lower all the time?
There may be a tradeoff, perhaps using ondemand? Would be worth playing around with the other governors and settings to find a way to get max speed only when it is needed. But then again, there may not be any reason to mess with this at all.
This is *not* overclocking and the kernel governor is not a secret. The performance governor will force the processor to run at its maximum advertised speed. I have been running mine this way for >1 week now with no ill effects.
Following these instructions is at your own risk, like almost everything on XDA.
Click to expand...
Click to collapse
There is already a thread here on xda discussing this. Actually that thread started at that time discussing if some sort of overclocking is possible. I'm not so sure if setting the soc to performance Governor and therefore always 1,6 GHz is a good idea. I agree with you that it definitely is an improvement and the unit feels more responsive. But as there is no heat spreader on the soc and the cooling is not very good where the unit is usually placed I'm not so sure if this does not reduce the lifetime or even kills it as someone said that the Rk3188 has no temp management.
I would instead recommend to try tuning the interactive Governor settings instead. The default settings almost never scales up to 1,6 ghz as you found out. But if you set the following two tunables with kernel audiutor the soc will scale up to max as soon as 60 percent load occurs on a core. This at least improved my unit while still keeping the advantages of dynamic frequency scaling. Here are the two variables
/sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load 60
/sys/devices/system/cpu/cpufreq/interactive/hispeed_freq 1608000
I already did some programming to set this variables as early as possible in the boot process without the need of kernel audiutor. But so far it is only active on my unit.

da_anton said:
There is already a thread here on xda discussing this. Actually that thread started at that time discussing if some sort of overclocking is possible. I'm not so sure if setting the soc to performance Governor and therefore always 1,6 GHz is a good idea. I agree with you that it definitely is an improvement and the unit feels more responsive. But as there is no heat spreader on the soc and the cooling is not very good where the unit is usually placed I'm not so sure if this does not reduce the lifetime or even kills it as someone said that the Rk3188 has no temp management.
I would instead recommend to try tuning the interactive Governor settings instead. The default settings almost never scales up to 1,6 ghz as you found out. But if you set the following two tunables with kernel audiutor the soc will scale up to max as soon as 60 percent load occurs on a core. This at least improved my unit while still keeping the advantages of dynamic frequency scaling. Here are the two variables
/sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load 60
/sys/devices/system/cpu/cpufreq/interactive/hispeed_freq 1608000
I already did some programming to set this variables as early as possible in the boot process without the need of kernel audiutor. But so far it is only active on my unit.
Click to expand...
Click to collapse
I am willing to try this ROM out if can post it,

SirOrigami said:
I am willing to try this ROM out if can post it,
Click to expand...
Click to collapse
As you already posted in the ROM builder thread: do you know how to build a ROM with that tool by yourself? Because the code is already on github but disabled.
If not I build you a new one this evening.

da_anton said:
As you already posted in the ROM builder thread: do you know how to build a ROM with that tool by yourself? Because the code is already on github but disabled.
If not I build you a new one this evening.
Click to expand...
Click to collapse
Yeah I do. But I am not really friendly with the choices, and what I Must include and what not.

SirOrigami said:
Yeah I do. But I am not really friendly with the choices, and what I Must include and what not.
Click to expand...
Click to collapse
OK, I'll build you one

Someone around here was discussing possible heat problems on these rockchip units, being why the manufacturer chooses to set the CPU governor this way.
I don't know if this tweak is really advisable unless you add hardware mod like passive heatsink or fan to the chip. I couldn't find any temperature data or sensors from the chip.

da_anton said:
There is already a thread here on xda discussing this. Actually that thread started at that time discussing if some sort of overclocking is possible. I'm not so sure if setting the soc to performance Governor and therefore always 1,6 GHz is a good idea. I agree with you that it definitely is an improvement and the unit feels more responsive. But as there is no heat spreader on the soc and the cooling is not very good where the unit is usually placed I'm not so sure if this does not reduce the lifetime or even kills it as someone said that the Rk3188 has no temp management.
I would instead recommend to try tuning the interactive Governor settings instead. The default settings almost never scales up to 1,6 ghz as you found out. But if you set the following two tunables with kernel audiutor the soc will scale up to max as soon as 60 percent load occurs on a core. This at least improved my unit while still keeping the advantages of dynamic frequency scaling. Here are the two variables
/sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load 60
/sys/devices/system/cpu/cpufreq/interactive/hispeed_freq 1608000
I already did some programming to set this variables as early as possible in the boot process without the need of kernel audiutor. But so far it is only active on my unit.
Click to expand...
Click to collapse
Thanks for the info, didn't know about the other thread.
I wonder if... They just forgot? Has anyone actually experienced a thermal. failure? Is there a data sheet for this thing? The Rockchip is by nature a low power device and they made a design decision not to include thermal management (or even temperature measurement?) ... To me it all points to "should be fine" but your solution is definitely more conservative/safer.
I have an infrared temp gun, but I need to pull apart the dash again, disassemble the unit, remove the DVD transport, and then drive around like that taking measurements... Probably not going to happen.
I did see some photos where a guy added some heatsinks...? On the Joying website maybe?
Sent from my Moto G using Tapatalk

wskelly said:
I did see some photos where a guy added some heatsinks...? On the Joying website maybe?
Click to expand...
Click to collapse
I don't know about the Joying website. But ptclabs and I did this and we posted it here: http://forum.xda-developers.com/showpost.php?p=68899885&postcount=22
As I have a heatsink on my SoC I don't mind having it at 1,6Ghz most of the time. But publishing this for everybody as part of a public ROM is maybe not a good idea without being able to measure the CPU temp. That RT3188 is really a cheap piece of electronics.
I don't think you have to drive around to measure this. I guess you could just use a generic 12V power supply and power the unit on your desk. The correct wiring should be written on the unit. Then you can just use any CPU burn app from the Play Store and measure the temp of the SoC with your infrared thermometer. Would definitely be a nice project!

Those of you interested in doing this, I'd recommend you taking a look at this thread regarding overheating:
http://forum.xda-developers.com/and...overclock-mtcd-mtcb-rk3188-quad-core-t3462513
ptclabs said:
being 3188 do not have a temp sensor. none. It will run till it burns or errors out
Click to expand...
Click to collapse

Good to see people steal other members information then try to hide it in another thread....
http://forum.xda-developers.com/and...5-1-1-mtcb-t3394209/post68721156#post68721156
So been working to make this ROM a bit faster. I changed the boot animations to the stock Audi one and shaved 5 seconds off boot. Then I went into developer options and turned off the animations. If you want the transition 0.5x works great too. Next I deleted all the launchers I wasn't using since they have a startup at boot. Now I got a little more in depth. I installed Kernal Adiutor (ROOT) and watched the CPU. I ran a bunch of programs in the background, starting maps, changing menus and noticed the CPU rarely went above 816 Mhz. So I went to adjust the Governor. The performance CPU Governor made everything snappy but running the 1.6 Ghz constantly can't be good for the CPU. I went back to Interactive and adjusted hispeed_freq to the maximum 1.6Ghz and go_hispeed_load to 80% (was originally 96% so 1.6 Ghz would never come on) Finally opening apps would trigger the 1.6 Ghz but it would still go down to the minimum even with Here weGo Maps. I didn't want to mess with the other settings cause I don't quite understand it well. If someone here know how to tweak this CPU more please let me know!!
Everything you need to know about Governors http://forum.xda-developers.com/gene...ors-o-t3048957
---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------
DO NOT LOCK YOUR CPU ON MAX SPEED. YOU WILL BURN YOUR STEREO UP. Read my research above to speed up your system, without burning up the CPU. Been running those setting for a month.

shawndak said:
Good to see people steal other members information then try to hide it in another thread....
http://forum.xda-developers.com/and...5-1-1-mtcb-t3394209/post68721156#post68721156
So been working to make this ROM a bit faster. I changed the boot animations to the stock Audi one and shaved 5 seconds off boot. Then I went into developer options and turned off the animations. If you want the transition 0.5x works great too. Next I deleted all the launchers I wasn't using since they have a startup at boot. Now I got a little more in depth. I installed Kernal Adiutor (ROOT) and watched the CPU. I ran a bunch of programs in the background, starting maps, changing menus and noticed the CPU rarely went above 816 Mhz. So I went to adjust the Governor. The performance CPU Governor made everything snappy but running the 1.6 Ghz constantly can't be good for the CPU. I went back to Interactive and adjusted hispeed_freq to the maximum 1.6Ghz and go_hispeed_load to 80% (was originally 96% so 1.6 Ghz would never come on) Finally opening apps would trigger the 1.6 Ghz but it would still go down to the minimum even with Here weGo Maps. I didn't want to mess with the other settings cause I don't quite understand it well. If someone here know how to tweak this CPU more please let me know!!
Everything you need to know about Governors http://forum.xda-developers.com/gene...ors-o-t3048957
---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------
DO NOT LOCK YOUR CPU ON MAX SPEED. YOU WILL BURN YOUR STEREO UP. Read my research above to speed up your system, without burning up the CPU. Been running those setting for a month.
Click to expand...
Click to collapse
I haven't stolen anything! My MTCD unit is my first unit at all of this kind and I have never seen your post/thread or any other post before regarding the governors on MTCx units. Believe it or not but I've spent hours in my garage playing with the governors. I deeply apologize if it looks like anything has been stolen from you.

da_anton said:
I haven't stolen anything! My MTCD unit is my first unit at all of this kind and I have never seen your post/thread or any other post before regarding the governors. Believe it or not but I've spent ours in my garage playing with the governors. I deeply apologize if it looks like anything has been stolen from you.
Click to expand...
Click to collapse
Keep doing what you are doing!

[/COLOR]
da_anton said:
I haven't stolen anything! My MTCD unit is my first unit at all of this kind and I have never seen your post/thread or any other post before regarding the governors on MTCx units. Believe it or not but I've spent hours in my garage playing with the governors. I deeply apologize if it looks like anything has been stolen from you.
Click to expand...
Click to collapse
Talking about the person who started this thread WSKELLY, unless you two are the same person. I find it hard to believe, out of the 1000's of cpu governor apps, the same one I listed had been chosen.

shawndak said:
Good to see people steal other members information then try to hide it in another thread....
http://forum.xda-developers.com/and...5-1-1-mtcb-t3394209/post68721156#post68721156
So been working to make this ROM a bit faster. I changed the boot animations to the stock Audi one and shaved 5 seconds off boot. Then I went into developer options and turned off the animations. If you want the transition 0.5x works great too. Next I deleted all the launchers I wasn't using since they have a startup at boot. Now I got a little more in depth. I installed Kernal Adiutor (ROOT) and watched the CPU. I ran a bunch of programs in the background, starting maps, changing menus and noticed the CPU rarely went above 816 Mhz. So I went to adjust the Governor. The performance CPU Governor made everything snappy but running the 1.6 Ghz constantly can't be good for the CPU. I went back to Interactive and adjusted hispeed_freq to the maximum 1.6Ghz and go_hispeed_load to 80% (was originally 96% so 1.6 Ghz would never come on) Finally opening apps would trigger the 1.6 Ghz but it would still go down to the minimum even with Here weGo Maps. I didn't want to mess with the other settings cause I don't quite understand it well. If someone here know how to tweak this CPU more please let me know!!
Everything you need to know about Governors http://forum.xda-developers.com/gene...ors-o-t3048957
---------- Post added at 03:47 PM ---------- Previous post was at 03:45 PM ----------
DO NOT LOCK YOUR CPU ON MAX SPEED. YOU WILL BURN YOUR STEREO UP. Read my research above to speed up your system, without burning up the CPU. Been running those setting for a month.
Click to expand...
Click to collapse
Can you be sure? I missed your post too as helpful as it is.

marchnz said:
Can you be sure? I missed your post too as helpful as it is.
Click to expand...
Click to collapse
Only person that can be sure is the thread starter. Of course we both could have stumbled upon the same idea to speed up a laggy system with a background of CPU governor work. We would then set out to pick the exact same program to set the governor. Just seems odd to me.
Anyways hope my governor adjustments suite y'all. Would highly recommend not running the CPU at max capacity especially when cars can easily get to 150 + in the summer. My xtrons unit has a fan and very large heat sink and I'm still nervous about it.

shawndak said:
Only person that can be sure is the thread starter. Of course we both could have stumbled upon the same idea to speed up a laggy system with a background of CPU governor work. We would then set out to pick the exact same program to set the governor. Just seems odd to me.
Anyways hope my governor adjustments suite y'all. Would highly recommend not running the CPU at max capacity especially when cars can easily get to 150 + in the summer. My xtrons unit has a fan and very large heat sink and I'm still nervous about it.
Click to expand...
Click to collapse
Actually I did exactly that about 2 weeks before this thread was created... It's the most logical thing to do for a noob...go into playstore, type kernel and this app is first result. Go in the app, scroll the options and obviously "performance" sounds promising... Very ordinary I think

Reminds me I need to add on a heatsink to the RK3188 in my unit. It couldn't hurt.

Mighty_X said:
Actually I did exactly that about 2 weeks before this thread was created... It's the most logical thing to do for a noob...go into playstore, type kernel and this app is first result. Go in the app, scroll the options and obviously "performance" sounds promising... Very ordinary I think
Click to expand...
Click to collapse
Thats what i did also.

Moto X Pure Battery Performance and Replacement

So my Moto X Pure only gets around 5 hours SOT and around 2-3 hours playing games. I seen a 3200 mAh battery replacement on Amazon and I'm wondering if anyone has tried it? I'm using the Resurrection Remix OS with my CPU set to power save in the battery options. Please post your battery stats and ROM information so I can see if my phone would benefit from a battery change.

Hybrid Theory said:
So my Moto X Pure only gets around 5 hours SOT and around 2-3 hours playing games. I seen a 3200 mAh battery replacement on Amazon and I'm wondering if anyone has tried it? I'm using the Resurrection Remix OS with my CPU set to power save in the battery options. Please post your battery stats and ROM information so I can see if my phone would benefit from a battery change.
Click to expand...
Click to collapse
LoL... With your SOT and game times, your battery is holding up pretty well. I would not expect much of an increase from any battery replacement you may get.
Regarding batteries from Amazon, be wary-especially of those claiming more mAh. Typically higher mAh means a larger battery so be skeptical. Based on what I have read in forums and reviews, it seems many of the batteries for this phone from Amazon, regardless of advertised mAh, have been hit or miss. Some manage to do well for 3 to 6 months then problems start.

aybarrap1 said:
LoL... With your SOT and game times, your battery is holding up pretty well. I would not expect much of an increase from any battery replacement you may get.
Regarding batteries from Amazon, be wary-especially of those claiming more mAh. Typically higher mAh means a larger battery so be skeptical. Based on what I have read in forums and reviews, it seems many of the batteries for this phone from Amazon, regardless of advertised mAh, have been hit or miss. Some manage to do well for 3 to 6 months then problems start.
Click to expand...
Click to collapse
I lowered my GPU frequency to 300 MHz that seemed to help a lot especially when playing games my battery doesn't drain as fast. I even lowered my screen resolution to 720p and set my GPU frequency to 180 MHz. The OS is smooth but when I start playing some 3D games you can definitely notice FPS drop so I put it back at 300 MHz. I couldn't increase my battery by lowering my CPU frequency for some reason my battery life seems worse when I try to mess with the CPU. The only thing I managed to do was disable my big cores in kernel auditor when they aren't needed and setting my low memory killer to aggressive in kernel auditor seemed to help my battery as well. That's just my personal experience hopefully someone will get something out of it.

Hybrid Theory said:
I lowered my GPU frequency to 300 MHz that seemed to help a lot especially when playing games my battery doesn't drain as fast. I even lowered my screen resolution to 720p and set my GPU frequency to 180 MHz. The OS is smooth but when I start playing some 3D games you can definitely notice FPS drop so I put it back at 300 MHz. I couldn't increase my battery by lowering my CPU frequency for some reason my battery life seems worse when I try to mess with the CPU. The only thing I managed to do was disable my big cores in kernel auditor when they aren't needed and setting my low memory killer to aggressive in kernel auditor seemed to help my battery as well. That's just my personal experience hopefully someone will get something out of it.
Click to expand...
Click to collapse
The CPU for the most part does pretty well scaling up and down based off processing needs. You probably just don't have CPU intensive apps so didn't notice much. You notice the GPU while playing games though. I think for the most part setting to a lower resolution might help with games at lower frequencies on the GPU in terms of maintaining higher fps at lower frequencies, but a 5.5 2K screen with simulated 720p probably doesn't net much battery life in other usage areas.

aybarrap1 said:
The CPU for the most part does pretty well scaling up and down based off processing needs. You probably just don't have CPU intensive apps so didn't notice much. You notice the GPU while playing games though. I think for the most part setting to a lower resolution might help with games at lower frequencies on the GPU in terms of maintaining higher fps at lower frequencies, but a 5.5 2K screen with simulated 720p probably doesn't net much battery life in other usage areas.
Click to expand...
Click to collapse
Right I am able to keep my GPU on power save and it'll sit on 180 MHz and the OS is still smooth on 720p if I bump it up to 1080p I'll have to put the frequency at 300 MHz or else it'll lag. I noticed when I move through the OS the GPU will jump to unnecessary frequencies like 300 MHz or even 450 MHz. Keeping it locked to 180 MHz while using Firefox or watching YouTube helped a little bit. The main problem for me is the lack of kernels to choose from. I used this tutorial https://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557 to tune my CPU governor since the Nexus 5X has the same SOC but my rom Remix OS has a feature called CPU boost that I can't turn off unless I flash another kernel. The problem with the Moto X Pure is that it doesn't have many custom kernels. I managed to find one that works with my rom but the camera doesn't work. I could simply go to another rom but they lack the customization Remix has and some of them have SeLinux set to permissive and I don't really feel like dealing with escalation attacks and having my bank information stolen.

Hybrid Theory said:
Right I am able to keep my GPU on power save and it'll sit on 180 MHz and the OS is still smooth on 720p if I bump it up to 1080p I'll have to put the frequency at 300 MHz or else it'll lag. I noticed when I move through the OS the GPU will jump to unnecessary frequencies like 300 MHz or even 450 MHz. Keeping it locked to 180 MHz while using Firefox or watching YouTube helped a little bit. The main problem for me is the lack of kernels to choose from. I used this tutorial https://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557 to tune my CPU governor since the Nexus 5X has the same SOC but my rom Remix OS has a feature called CPU boost that I can't turn off unless I flash another kernel. The problem with the Moto X Pure is that it doesn't have many custom kernels. I managed to find one that works with my rom but the camera doesn't work. I could simply go to another rom but they lack the customization Remix has and some of them have SeLinux set to permissive and I don't really feel like dealing with escalation attacks and having my bank information stolen.
Click to expand...
Click to collapse
Wow. Since I first got the phone 3 years ago, i personally just have had very little time to delve much into doing custom ROMs and kernels for this device due to work scheduling I'm moving to a new job this month and should have more time on my hands. I'm probably going to get back into things.

aybarrap1 said:
Wow. Since I first got the phone 3 years ago, i personally just have had very little time to delve much into doing custom ROMs and kernels for this device due to work scheduling I'm moving to a new job this month and should have more time on my hands. I'm probably going to get back into things.
Click to expand...
Click to collapse
I'd compile a kernel for lineage based roms with the nougat modem but I'm not that smart I don't even have a computer to do it with lol.

So I went ahead and installed the EX Kernel Manager app and I downloaded the Hawktail governor profile. After doing that my battery went from 2-3 hours SOT to 4-6 SOT from 100%. When I play slither.io on the default CPU setup my battery would drop 10% every 10-15 minutes. With the Hawktail profile it drops 10% every 30-40 minutes. I thought this was incredible because NFC and Bluetooth was still on. I also found that the Alucard CPU governor gave me similar results during my observations. I really hope somebody else can benefit from this thread.
Here is the download link https://androidfilehost.com/?fid=24686679545610694
Remove the .txt extension and put it on your micro SD card or in the ElementalX folder. From the Ex Kernel Manager app go to CPU>Governor Options>Load then load the HawkTail file then click apply on boot.