Related
I read a lot of comments about the processor used by qualcomm being asymmetrical thus one core is doing the heavy lifting most of the time while the other is at a lower clock speed and it affects overall performance but enhances battery life. Now that this is a big factor on why the performance and benchmarks are lower than tegra and exynos because its running on one core most of the time.
NOW.... When we get s-off and are able to mess with the kernel, cpu speeds and such. Can there be the possibility where we can use a tool like setcpu to force both cores to run at the same clock speed always? This might level the playing field and show some drastic performance enhancements imo.
Theoretically... Is there a slightest chance something like this can be done? I suppose so since we can manipulate the cpu so easily with kernel access
Please input
nothing? lol
this might be harder than i thought...
mike21pr said:
nothing? lol
this might be harder than i thought...
Click to expand...
Click to collapse
I don't think gingerbread has the capability even if the kernel was modified.
We can only wait and see
IMHO, with proper kernel, system will manage cores better and there will not be any lag. Asymmetrical core scaling will yield much better battery life then symmetrical one, just need better implementation.
What is overclocking?
Overclocking is the process of making a computer or component operate faster than the clock frequency specified by the manufacturer by modifying system parameters. One of the most important techniques is running at a higher clock rate (more clock cycles per second; hence the name "overclocking"), but other parameters, such as CPU multiplier and memory timings, can also be changed and would be considered to be overclocking. Operating voltages may also be changed (increased), which can increase the speed at which operation remains stable. Most overclocking techniques increase power consumption, generating more heat, which must be dispersed if the chip is to remain operational.
Advantage:
Higher performance in games, encoding, video editing applications, and system tasks at no additional expense, but with increased electrical power consumption. Overclocking can extend the useful life of older equipment. Adding noticible response time for multitasking and powerhungry applications and games.
Disadvantages:
Overclocking if it's not done with moderate rate can be very risky and potentialy might permanantly damage your device's hardware, plus it can cause a slight battery drain. If it's done correctly then you're good to proceed.
Undervolting :
Undervolting is reducing the voltage of a component, usually the processor, reducing the voltages of each step less than the original stock voltages.
Advantages:
Increase of Battery life.
The heat that come from the processor reduces.
Disadvantages:
Undervolting if it's applied correctly then it's good, Hard undervolting might make the device unstable and potentily will lead to bootloops and freezes.
CPU
Maximum clock that could be applied on The Galaxy S4 is XXXXmhz and the minimum is XXX mhz . I will add the stock clock values as soon as possible.
More to come asap !
SERIOUSLY?
A guide about overclocking when you don't even know what CPU the specific models will be getting?
AndreiLux said:
SERIOUSLY?
A guide about overclocking when you don't even know what CPU the specific models will be getting?
Click to expand...
Click to collapse
I as well, think that this is a bit strange...
AndreiLux said:
SERIOUSLY?
A guide about overclocking when you don't even know what CPU the specific models will be getting?
Click to expand...
Click to collapse
and probably the S600 version will not be OCable its already has throttling problem due overheating ( + its an OCed version of S4 pro )
Weird thread
sent from an Galaxy s3 GT I9300
Running perseus kernel 33.1 , XELLA 4.1.2 leaked build
forum.xda-developers.com/showthread.php?t=1784401
Dont click,you might regret , I won't be responsible if you brick ur head
jus sawed this guide tosee whats safe minimum voltage and other stuff! better to change title or a how to (i already know btw )
lol this is horrible! where's guide to udenervolt? i also underclaockd m cpu to 1GHZ that feels a lot lot colder and still freaking fast! even think more stable! also i wannt to underclaock the GPU too and also udnervolt it anyone knows how? i got i9500 octa
Hi
When flashing XtreStoLite Aroma Installer I can choose 4 different kernels.
Right now i'm on "stock" XtreStoLite Unikernel, but is it a possibility that the other kernels will increase my battery life?
Which kernel available right now would you guys say is the best when looking from a battery perspective?
Thanks in advance
Faspaiso said:
Hi
When flashing XtreStoLite Aroma Installer I can choose 4 different kernels.
Right now i'm on "stock" XtreStoLite Unikernel, but is it a possibility that the other kernels will increase my battery life?
Which kernel available right now would you guys say is the best when looking from a battery perspective?
Thanks in advance
Click to expand...
Click to collapse
If they can undervolt but your device can get unstable undervolting, mine always have but maybe I have been unlucky with my socs
I am using simpl kernel and have undervolted with additional 12.5 mV (to the default -12.5 mV) combining to total -25 mV for all frequenceies. Haven't experienced any issues so far, but don't want to experiment and push it too far.
godutch said:
If they can undervolt but your device can get unstable undervolting, mine always have but maybe I have been unlucky with my socs
Click to expand...
Click to collapse
vordhosbnbg said:
I am using simpl kernel and have undervolted with additional 12.5 mV (to the default -12.5 mV) combining to total -25 mV for all frequenceies. Haven't experienced any issues so far, but don't want to experiment and push it too far.
Click to expand...
Click to collapse
What can "happen" if you undervolt too far? What do you define my unstable? Will it restart, freezing or what? If that happens, can't I just remove the undervolt?
Thanks in advance
Faspaiso said:
What can "happen" if you undervolt too far? What do you define my unstable? Will it restart, freezing or what? If that happens, can't I just remove the undervolt?
Thanks in advance
Click to expand...
Click to collapse
usually reboots or failure to boot, easy to fix by flashing another kernel or resetting to default values though but if you rely on your phone for important things then you could miss those....
Faspaiso said:
What can "happen" if you undervolt too far? What do you define my unstable? Will it restart, freezing or what? If that happens, can't I just remove the undervolt?
Thanks in advance
Click to expand...
Click to collapse
godutch said:
usually reboots or failure to boot, easy to fix by flashing another kernel or resetting to default values though but if you rely on your phone for important things then you could miss those....
Click to expand...
Click to collapse
In the specific case Simpl kernel is bundled with the Synapse kernel tuner app, which has a failsafe mechanism related to undervolting. After every restart the voltage settings are applied and after X minutes, if there is no reboot, they are marked "safe". If you get too low and have problems before you reach those X minutes, Synapse will not apply the voltage settings, allowing you to make the needed changes.
vordhosbnbg said:
I am using simpl kernel and have undervolted with additional 12.5 mV (to the default -12.5 mV) combining to total -25 mV for all frequenceies. Haven't experienced any issues so far, but don't want to experiment and push it too far.
Click to expand...
Click to collapse
godutch said:
usually reboots or failure to boot, easy to fix by flashing another kernel or resetting to default values though but if you rely on your phone for important things then you could miss those....
Click to expand...
Click to collapse
Can you define when the unstable thing occurs? Just for testing I have undervolted all simpelkernel is capable of and still going as smooth as always.
Faspaiso said:
Can you define when the unstable thing occurs? Just for testing I have undervolted all simpelkernel is capable of and still going as smooth as always.
Click to expand...
Click to collapse
If you see frequent reboots you know you have undervolted too much
Faspaiso said:
Can you define when the unstable thing occurs? Just for testing I have undervolted all simpelkernel is capable of and still going as smooth as always.
Click to expand...
Click to collapse
When unstable also can cause your phone to freeze and lock up. You could run stress tests for each frequency if you really wanted to go the extra mile. Usually I lower by 5mv for all steps and then when i start noticing weird behaviors I increase by 5mv and call it a day.
Lower frequencies can only go so low, so eventually you'll just be decreasing the high freq steps. Just like a computer, youll need a high enough voltage to keep the phone stable.
godutch said:
If you see frequent reboots you know you have undervolted too much
Click to expand...
Click to collapse
tlxxxsracer said:
When unstable also can cause your phone to freeze and lock up. You could run stress tests for each frequency if you really wanted to go the extra mile. Usually I lower by 5mv for all steps and then when i start noticing weird behaviors I increase by 5mv and call it a day.
Lower frequencies can only go so low, so eventually you'll just be decreasing the high freq steps. Just like a computer, youll need a high enough voltage to keep the phone stable.
Click to expand...
Click to collapse
Well it might not work for me then. I undervolted all that Simpelkernel is capable off and have just ran a two hour stress test. Nothing. Phone works like charm.
Faspaiso said:
Well it might not work for me then. I undervolted all that Simpelkernel is capable off and have just ran a two hour stress test. Nothing. Phone works like charm.
Click to expand...
Click to collapse
I believe some kernels allow for lower undervolting.. Im still on 5.0.2
vordhosbnbg said:
I am using simpl kernel and have undervolted with additional 12.5 mV (to the default -12.5 mV) combining to total -25 mV for all frequenceies. Haven't experienced any issues so far, but don't want to experiment and push it too far.
Click to expand...
Click to collapse
Oh, I undervolted busses. Can you explain me which I should undervolt and what is the difference between busses, A57 Cluster, GPU, A53 Cluster and so on and which is the right to undervolt?
Thanks in advance
Faspaiso said:
Oh, I undervolted busses. Can you explain me which I should undervolt and what is the difference between busses, A57 Cluster, GPU, A53 Cluster and so on and which is the right to undervolt?
Thanks in advance
Click to expand...
Click to collapse
Well I am not an expert in these matters, but from what I have read, roughly Power = Voltage^2 * Frequency. This exponential relation between voltage and power consumption is the reason undervolting is so effective in incresing battery life. As @tlxxxsracer said, lower frequencies already use lower voltages and pushing those too low will cause problems, but you can experiment boldly on higher ones.
Regarding your question about different voltage groups:
Our ARM CPU is following the big.LITTLE architecture. This means it has 2 groups of 4 cores - one is the "big" one (A57 Cluster) which is very powerfull, but also not very efficient and is put online when a heavier task load is put on the system. The other is the "LITTLE" group (A53 Cluster) which is what you usually use outside of gaming and short CPU usage spikes. The GPU is the graphics chip and the bus is the memory bus controller, which is basically what connects the RAM, the CPU and the GPU and handles data transfer between them.
What should you undervolt? I would say - whatever you can [get away with]. Push voltages as far as you can without compromsing stability. Lowering the voltage on the A53 and the GPU should be most beneficial. I am perfectly fine with my battery life and did not want to concern myself over stability, so I just undervolted with 25 mV. You however can be the brave man who spent a week in undervoltage experiments and share your results with us.
Now another thing to consider is what quality is your Exynos chip. If you are not familiar with the semiconductor production process, you can read on it over wikipedia, but in short - there are many processors produced on one "waffle" and about half of them are completely unusable. The other half are of varying quality (almost none of them perfect) and based on that imperfections they are sorted in different "bins" (this is known as CPU binning). This means that an almost perfect chip, from a higher bin can sustain much lower voltages, without issues, in comparison with a lower grade chip.
You can take a look in this thread to see what avs group (bin) people have and also how to see yours. I was not able to look it trough the method described in the OP, though, but you can see it in the kernel dmesg.
vordhosbnbg said:
Well I am not an expert in these matters, but from what I have read, roughly Power = Voltage^2 * Frequency. This exponential relation between voltage and power consumption is the reason undervolting is so effective in incresing battery life. As @tlxxxsracer said, lower frequencies already use lower voltages and pushing those too low will cause problems, but you can experiment boldly on higher ones.
Regarding your question about different voltage groups:
Our ARM CPU is following the big.LITTLE architecture. This means it has 2 groups of 4 cores - one is the "big" one (A57 Cluster) which is very powerfull, but also not very efficient and is put online when a heavier task load is put on the system. The other is the "LITTLE" group (A53 Cluster) which is what you usually use outside of gaming and short CPU usage spikes. The GPU is the graphics chip and the bus is the memory bus controller, which is basically what connects the RAM, the CPU and the GPU and handles data transfer between them.
What should you undervolt? I would say - whatever you can [get away with]. Push voltages as far as you can without compromsing stability. Lowering the voltage on the A53 and the GPU should be most beneficial. I am perfectly fine with my battery life and did not want to concern myself over stability, so I just undervolted with 25 mV. You however can be the brave man who spent a week in undervoltage experiments and share your results with us.
Now another thing to consider is what quality is your Exynos chip. If you are not familiar with the semiconductor production process, you can read on it over wikipedia, but in short - there are many processors produced on one "waffle" and about half of them are completely unusable. The other half are of varying quality (almost none of them perfect) and based on that imperfections they are sorted in different "bins" (this is known as CPU binning). This means that an almost perfect chip, from a higher bin can sustain much lower voltages, without issues, in comparison with a lower grade chip.
You can take a look in this thread to see what avs group (bin) people have and also how to see yours. I was not able to look it trough the method described in the OP, though, but you can see it in the kernel dmesg.
Click to expand...
Click to collapse
This is the most in depth answer I have ever gotten. Thanks for that!
Mind if I ask one more question? What is HPM voltage control and when undervolting is that the thing I should undervolt (it's in all of the 4 sections you explained)? Or should I undervolt each core individually?
Thanks in advance!
If I would have to guess, I would say, based on the description that increasing this increases the range, which you can change the volatage on each individual frequency, but I may be wrong, you should ask in the simpl kernel thread.
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.
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.