Database Info

Making G1 run at 528 MHz permanently (Haykuro's Builds only)

Run these commands as "su".
Code:
echo 528000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 528000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
You can check the cpu speed by running the command below before and after.
Code:
cat /proc/cpuinfo
I have tested this on 5.0.2H and works flawlessly.
These settings will be lost after reboot.
On JF builds, you can make this run after reboot by including the two lines in "init.rc".
I do not know how to accomplish this in Haykuro's builds.
I am seeing much faster response times, but beware that the battery life will be reduced as the processor keeps running at 528 MHz even when the phone is in sleep mode.
Just wanted to add the reasoning.
If you type
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors
you will see a list of available profiles that can be used by the kernel to control the CPU.
By default, "ondemand" profile is used.
The "scaling_max_freq" and "scaling_min_freq" define the maximum and minimum frequencies the CPU can run at.
What gets used is governed by the profile in use.
"scaling_cur_freq" gives you the current CPU frequency.
The commands given just change these maximum and minimum frequencies.
Hope this clears some questions on how this works.
Update:
I tested by setting minimum to 64000, but the CPU did not clock below 122880 even in standby.
Update:
For now this will only work on Haykuro's builds.
This will NOT work on JF's builds as the system files are different.

good catch! I've been looking into this a lot myself but hadn't found that device. Props.
So, what daring person is gonna try 530000? lol

buttkicker said:
Run these commands as "su".
Code:
echo 528000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 528000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
You can check the cpu speed by running the command below before and after.
Code:
cat /proc/cpuinfo
I have tested this on 5.0.2H and works flawlessly.
These settings will be lost after reboot.
On JF builds, you can make this run after reboot by including the two lines in "init.rc".
I do not know how to accomplish this in Haykuro's builds.
I am seeing much faster response times, but beware that the battery life will be reduced as the processor keeps running at 528 MHz even when the phone is in sleep mode.
Have fun.
Click to expand...
Click to collapse
Im on jf mod apps to sd card, and whenever I try this is says cannot create directory nonexistent

Joeriginal said:
Im on jf mod apps to sd card, and whenever I try this is says cannot create directory nonexistent
Click to expand...
Click to collapse
are you running it as root? I accidentally forgot that it doesn't start you out as superuser and tried to do it and got that exact error. Make sure you su before trying those lines.

There is no point in keeping it at 528Mhz all the time.
Setting the max scaling frequency to 528Mhz would be enough. The device would clock at it only when needed.

[email protected] said:
are you running it as root? I accidentally forgot that it doesn't start you out as superuser and tried to do it and got that exact error. Make sure you su before trying those lines.
Click to expand...
Click to collapse
Yeah, can you show me exactly what you did.

where after you enter
Code:
cat /proc/cpuinfo
does the cpu speed show?

AbsoluteDesignz said:
where after you enter
Code:
cat /proc/cpuinfo
does the cpu speed show?
Click to expand...
Click to collapse
I tried it on 5.01G and I don't see anything showing up in /proc/cpuinfo. Its the same before and after.
If I do a
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
528000
It does show 528000, but I'm not noticing too big if any of a performance improvement, so I don't think it works on the G versions.

hmmm, well i can't really tell if its working, but it doesnt seem to be doing any harm
someone let me know when they go above 528000

it dont work. maybe something to do with app and data on the sd.

MoridinBG said:
There is no point in keeping it at 528Mhz all the time.
Setting the max scaling frequency to 528Mhz would be enough. The device would clock at it only when needed.
Click to expand...
Click to collapse
This. Also, cpuinfo_min_freq lists the cpu as capable of as low as 19.2 mhz, while scaling has the min frequency at 245 mhz. One could presumably prolong battery life on idle by reducing min frequency further, to e.g. 128mhz
Code:
echo 128000 > scaling_min_freq
I'm running at 128mhz-528mhz at the moment, not sure if it makes any significant difference though.

im currently using the 5.0.2h build by haykuro everything runs great the only issue im having is getting it to run on startup i have added it to the /init.rc using adb but even after doing that on reboot it goes back to the default frequency. anyone else having this issue?

AbsoluteDesignz said:
where after you enter
Code:
cat /proc/cpuinfo
does the cpu speed show?
Click to expand...
Click to collapse
I *think* it is the BogoMIPS part. When I just ran it (Haykuro 5.0.2H), I got 247.6 BogoMIPS. Setting JUST the max setting to 528, it remained at 247.6. Setting both the minimum and maximum put it at 527.15.
Performance? I don't have any apps installed to test this. But I will say that it does *seem* faster on the home screen. There is no delay on anything. It's snappy as all hell. Placebo? Maybe.
I'll play around with the init.rc when I get home tonight.
*More*
Just did a test. I dropped my minimum to 128. It showed 127.79 - I then started an MP3 song in the background and checked it (while it was playing) and it said 527.15. I paused the song and it went back to 127.79.
If BogoMIPS is what we're supposed to be looking at, it is working as far as scaling. Need a benchmark program of some sort to really test. I wonder how low we could go to save battery life...
Another way to test (without a benchmark app) is to lower it to 64 min and 64 max. See if the phone locks / is slow.

Ok it does work if I set min and max to 528 in 5.01G.
I guess if max is only set, it will just throttle up when needed.
there's definitely a performance improvement when browsing javascript heavy sites.
KyleK29 said:
I *think* it is the BogoMIPS part. When I just ran it (Haykuro 5.0.2H), I got 247.6 BogoMIPS. Setting JUST the max setting to 528, it remained at 247.6. Setting both the minimum and maximum put it at 527.15.
Performance? I don't have any apps installed to test this. But I will say that it does *seem* faster on the home screen. There is no delay on anything. It's snappy as all hell. Placebo? Maybe.
I'll play around with the init.rc when I get home tonight.
*More*
Just did a test. I dropped my minimum to 128. It showed 127.79 - I then started an MP3 song in the background and checked it (while it was playing) and it said 527.15. I paused the song and it went back to 127.79.
If BogoMIPS is what we're supposed to be looking at, it is working as far as scaling. Need a benchmark program of some sort to really test. I wonder how low we could go to save battery life...
Another way to test (without a benchmark app) is to lower it to 64 min and 64 max. See if the phone locks / is slow.
Click to expand...
Click to collapse

I really hope someone is testing the 128-min/528+max theory to see if it improves battery life. I'm frequently away from any kind of charger for 8+ hours with my phone idle for 90% of that, so if it did, it would be a godsend.

This works for me. If you want an easier way, instally my app that does exactly this. Its called openoverclocker and is on the market. Thanks for the idea buttkicker!

Powermaniac said:
I don't notice any difference. Are you guys sure BogoMips is supposed to really tell any kind of Proc speed?
http://en.wikipedia.org/wiki/BogoMips
Click to expand...
Click to collapse
Yes the BogoMips value is what you want to look out for. Since the haykuro build has dynamic scaling, it will adjust accordingly. =]

I know this method works.
You can download "Neocore" from Market and test it.
Neocore is an OpenGL graphics performance benchmark tool.
I'm posting the before and after screenshots for reference.
The benchmark was run without audio.
The CPU was overclocked to the following setting.
MAX = 528000
MIN = 128000

[email protected] said:
This works for me. If you want an easier way, instally my app that does exactly this. Its called openoverclocker and is on the market. Thanks for the idea buttkicker!
Click to expand...
Click to collapse
You are welcome and thanks for creating an app.

i tested neocore and my fps was 26.4 =]

Overclock Question

I am using the Clemsyn Kernel now, but have never done any overclocking before.
What is the effect on battery life if I went to around 1.4ish?
What is the effect on the lifetime usage of my unit if I overclock?
After I download SetCpu, what settings do I use? Do I have to change anything in voltage?
I read something where people sometimes underclock when the screen is turned off. How can I do this?
Thanks for any help. I am a noob when it comes to overclocking.

deadhead85 said:
I am using the Clemsyn Kernel now, but have never done any overclocking before.
What is the effect on battery life if I went to around 1.4ish?
What is the effect on the lifetime usage of my unit if I overclock?
After I download SetCpu, what settings do I use? Do I have to change anything in voltage?
I read something where people sometimes underclock when the screen is turned off. How can I do this?
Thanks for any help. I am a noob when it comes to overclocking.
Click to expand...
Click to collapse
Start off by setting your main profile to 1.4GHz and tick set on boot. And theres your overclock... I think interactive gov. is the most useful, you can try others if you want.
If you would like to limit the speed when screen off, add a profile under profiles select screen off and set your wanted frequency when screen off.

reidar.ostrem said:
Start off by setting your main profile to 1.4GHz and tick set on boot. And theres your overclock... I think interactive gov. is the most useful, you can try others if you want.
If you would like to limit the speed when screen off, add a profile under profiles select screen off and set your wanted frequency when screen off.
Click to expand...
Click to collapse
+1 This is exactly what I've done

If you set the max speed to 1.4 GHz and set the governor to performance it will drain the battery faster than if you had it set to the others. You'll most likely have already upgraded the TF by the time it dies due to overclocking. It does shorten the life, not dramatically though. You can set up underclocking in profiles.

NSTools and SetCPU Set on Boot

If you have specific profiles in SetCPU and a set CPU frequency NSTools, is there anyway to keep the profiles working without having to disable set on boot for NSTools? NSTools seems to overtake CPU settings on boot.
Sent from my Nexus S 4G using Tapatalk 2

why do you even want use SetCPU ? it seems to be useless with NSTools because what ever it can do is to be done by NSTools , if you say you wanna do something like change frequency while screen off , then the governor will do it automatically if you choose appropriate CPU governor

Jamin13 said:
If you have specific profiles in SetCPU and a set CPU frequency NSTools, is there anyway to keep the profiles working without having to disable set on boot for NSTools? NSTools seems to overtake CPU settings on boot.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
CPU Profiles aren't worth it for day to day use. Constant ondemand is perfectly fine and won't steal any extra battery from you.
However, setting NSTools to set on boot should still allow SetCPU to work fine, as long as CPU settings are set the same on boot time. If not, use init.d scripts but remove CPU parameters from them (find them in /system/etc/init.d/xx-xxxxx), keeping the other settings as you prefer. Might want to remove NSTools after this though as it may undo your changes after opening again.

i guess setcpu makes it easier to change cpu frequencies quickly through the widget, ns tools doeesnt have a widget so its "harder"

qtwrk said:
why do you even want use SetCPU ? it seems to be useless with NSTools because what ever it can do is to be done by NSTools , if you say you wanna do something like change frequency while screen off , then the governor will do it automatically if you choose appropriate CPU governor
Click to expand...
Click to collapse
SetCPU won't control the Backlight Notifications and Dimmer.
Harbb said:
CPU Profiles aren't worth it for day to day use. Constant ondemand is perfectly fine and won't steal any extra battery from you.
However, setting NSTools to set on boot should still allow SetCPU to work fine, as long as CPU settings are set the same on boot time. If not, use init.d scripts but remove CPU parameters from them (find them in /system/etc/init.d/xx-xxxxx), keeping the other settings as you prefer. Might want to remove NSTools after this though as it may undo your changes after opening again.
Click to expand...
Click to collapse
I'm just a bit OCD about battery life some days. I'd rather use the app than making my own scripts. I kinda derped with the profiles earlier today. All is good now.

I wish the two would play better together too - and I don't see how "just don't use them both" or saying SetCPU is no longer needed is acceptable answers. Especially since many of us actually paid for SetCPU...
Now that it looks like we'll only get two governors in MathKids kernel (what a crock)... saying you are picking the wrong one is a bad answer too. Ondemand certainly isn't the best for battery life, and for those of us who have tested and measured battery life we know just picking one isn't a solution either.
So what is the actual answer? Because setting the governor parameters at boot isn't the problem. It's switching between profiles - and the governors that give you the best battery life and giving acceptable performance need to be tweaked from their defaults.
With OnDemand I'm looking at using over 16% battery per hour under 4.1, even with considerable screen off time. Not being able to set it to Wheatley on screen off is killing the battery.
I will say the problem seems to lay directly with SetCPU and I'm going to contact the dev and see what I can find out. I don't see why it should be changing the parameters back to default on profile change.
But people who use neither or just one probably just not comment. Not to flame, or fight, but it's not helpful to add nothing.

CPU tool that lowers the cpu when screen off

Hello, hope this is the right section.
I am looking for good CPU tool that can overclock the processor and control its frequency when the screen is off. So far I am using CPUBoost Lite, but you need to reapply its settings everytime after reboot (CPUBoost Lite, the newest version is a complete bullsheeeee).
I also tried System Tuner, but it has far too many scary tools, and it seems it doesnt always lower the cpu when the screen is off...
So could you suggest me another one?

really guys, am I asking something that complicated?

I'm not sure, but maybe you should consider taking a look a the App "Tasker" and the variable %CPUGOV.
There are quite a few posts here in the forum about Tasker.

sartheris said:
Hello, hope this is the right section.
I am looking for good CPU tool that can overclock the processor and control its frequency when the screen is off. So far I am using CPUBoost Lite, but you need to reapply its settings everytime after reboot (CPUBoost Lite, the newest version is a complete bullsheeeee).
I also tried System Tuner, but it has far too many scary tools, and it seems it doesnt always lower the cpu when the screen is off...
So could you suggest me another one?
Click to expand...
Click to collapse
Please give some details about your device so that people can post more focused replies.
I don't know much about overclocking, but for lowering the cpu when screen off - this should be automatically be done by the kernel in stock / any custom kernel that you install - are you sure your cpu is not lowered when the screen is off?

ivoidwarranty said:
Please give some details about your device so that people can post more focused replies.
I don't know much about overclocking, but for lowering the cpu when screen off - this should be automatically be done by the kernel in stock / any custom kernel that you install - are you sure your cpu is not lowered when the screen is off?
Click to expand...
Click to collapse
And how could I possibly know whats the frequency of my cpu when the screen is off?

sartheris said:
And how could I possibly know whats the frequency of my cpu when the screen is off?
Click to expand...
Click to collapse
Enable USB debugging, install adb drivers, and run the following command through adb shell when the screen is off.
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq

Try SetCPU!It has profiles so you can set one of them to activate when screen is off.

N0nameForNow said:
Try SetCPU!It has profiles so you can set one of them to activate when screen is off.
Click to expand...
Click to collapse
Yes, this works great, thanks!

*ROOT ONLY* Honor 5X Marsmallow battery tweak.

Im not responsible for any behavior like the Note 7, if its explodes while applying the tweak its not my fault!
This tweak will edit a simple file so that the minimum cores get decreased and we wont get unnecessary battery drain
ROOT ONLY!
Manual Guide:
1. Make sure your device has root acces,
2. Install Root Browser from the playstore.
3. Open the app and navigate to > sys/devices/system/cpu/cpu0/core_ctl
4. Search for the file min_cpus make sure the permissions are set to rw-r-r (it showsup under the file name).
5. Open min_cpus and change the number '4' to '0', This will say to the CPU that a minimal of 1 cpu core is needed to be active instead of 4 all the time.
6. Save the file and navigate back to > sys/devices/system/cpu/cpu0/core_ctl and change the permissions back to r-r-r.
7. Your device will still run 'smooth' and safe some battery! You have to apply this every single reboot or need to make a init.d script and make it run every single reboot..
You can also use the provided script in the "Attached Files" section. If you use a script runner you dont have to follow the Manual guide everytime you boot.
Share what you think, any feedback is appreciated!

Thanks, so i did the steps 1 to 6, and the contents of that folder disappear, is that normal? I restart the phone and the files appear and i did the same steps the files disappear again.

danino22000 said:
Thanks, so i did the steps 1 to 6, and the contents of that folder disappear, is that normal? I restart the phone and the files appear and i did the same steps the files disappear again.
Click to expand...
Click to collapse
What content? Im not sure what you mean..

Demian3112 said:
What content? Im not sure what you mean..
Click to expand...
Click to collapse
The files inside core_ctl folder disappear.

danino22000 said:
The files inside core_ctl folder disappear.
Click to expand...
Click to collapse
It shouldnt what device do you have Kiw l21? MM or LP? Open kernel adiutor or something else and see how the cores behave make sure battery settings is on Performance. Not much what i can do other wise..

Kiw l24 MM last update from honor UK support page. For example in kernel adiutor if i want to change the min frequency to 200mhz or any other, the settings won't apply, it return to the original frequency after few secs.

SOT ?? @Demian3112

danino22000 said:
Kiw l24 MM last update from honor UK support page. For example in kernel adiutor if i want to change the min frequency to 200mhz or any other, the settings won't apply, it return to the original frequency after few secs.
Click to expand...
Click to collapse
You cant set big cluster. For small cluster go to sys/devices/system/cpu/cpu4/cpufreq/ and look for min freq set permissions to rw-r-r open it change value 800000 to 200000 save it change permissions back to r-r-r

kartrikpal said:
SOT ?? @Demian3112
Click to expand...
Click to collapse
Havent measured. I safe about 3-8% in an hour doing the same stuff youtube, google, whatsapp and facebook etc. It really depends on what you are doing.
Little cluster runs idle 800mhz with the tweak 200mhz
Big cluster has 8 cores active all the time, with this tweak 0 in idle/simple tasks. It only enables when needed
Just try it out yourself. If you dont like it remove kernal adiutor restart device and tweaks are undone

doesn't seem like little clusters settings are sticking in Kernel aduiter. When changes to 200mhz, it automatically get changed back to 800mhz min

halfacannoli said:
doesn't seem like little clusters settings are sticking in Kernel aduiter. When changes to 200mhz, it automatically get changed back to 800mhz min
Click to expand...
Click to collapse
Make site battery manager is on performance.. i dont Have this issue and i Just upgrades to B330

Demian3112 said:
Make site battery manager is on performance.. i dont Have this issue and i Just upgrades to B330
Click to expand...
Click to collapse
Thanks for the fast response. However, that did not work for me initially. I was able to resolve the issue and it looks like I was able to set the frequency for the big cores as well. As a preface, I have the L24 and updated to MM EMUI 4 through the zip that was found on the hihonor UK website. After the update I did a factory reset. I am just letting you know because some of things you described didn't work while other things did.
What did work was setting the Mincpu to 0, so that when idle only 1 core is running. This worked great, so thanks for that! However, in Kernel Aduiter, I had to set the governor to Interactive for it to use the other Big cores when I am using the phone. If I set it to ondemand, the other 3 big cores does not activate, only core 1 is used along with the 4 little cores.
What did not work per your instructions were setting the min frequencies for the little cores. Yes, I changed the Power option to performance, but every time I exited the kernel auditer, it would revert back to a min frequency of 800mhz.
After tinkering with the phone for a couple of days, I was able to set the min frequency to 200mhz for BOTH big cores and little cores and it seems that both settings are sticking. Throughout the 2 days, I did many changes so I have yet to narrow it down to what changes I did that made both changes stick. When I have some time I will try to reproduce the results and post on how I got it to work. I would also like to give it a few days to make sure that the changes stick.
---------- Post added at 10:22 PM ---------- Previous post was at 10:13 PM ----------
danino22000 said:
The files inside core_ctl folder disappear.
Click to expand...
Click to collapse
it disappears because permission was changed to r-r-r which is read only. change permission to include w (write) and execute, and you'll see it again

halfacannoli said:
doesn't seem like little clusters settings are sticking in Kernel aduiter. When changes to 200mhz, it automatically get changed back to 800mhz min
Click to expand...
Click to collapse
Got to battery manager and set it to performance.

Can someone make an script to keep this installed upon boot? Thanks.

Robertleehadley said:
Can someone make an script to keep this installed upon boot? Thanks.
Click to expand...
Click to collapse
If i have time i will do it!

Nice tweak on changing 4 to 0 at min_cpus but Root Browser (w/Root and Grant) refused to save it so i used X-plore by Michal Baclk Version: 3.86.02 Build Date: 7/16/16 and it took perfectly!
Thanks for the other kernel adjustments too.

anyone ever make that bat file?
And has anyone tried setting CPU4 the same way as suggested for CPU0? By default, it is set to 1.
I'm also a little concerned I may not have understood the directions properly...
From what I read, it looks like you are ignoring the large cores and only modifying the little ones? Am I understanding that correctly?
And why can't we just tick the 'use this on boot' in kernel aduitor? Why does it need to be reset upon every boot? I mean, we are doing these steps with ROOT access, are we not? Shouldn't the file stay modified? I am quite confused... but very eager to get more battery life out of this... was shocked to see that all 8 cores are always on... and my device NEVER hit deep sleep or any of the slower frequencies all day!
No wonder I can drop to 85% within an hour. Sheesh... this blows.
Ok, I played with it some more...
Looks like Root access has nothing to do with modifying that file. Yes, you need root to modify it... but it never stays changed after a reboot. This tells me that this area must be a hardware toggle area. Meaning, there's some place with the default value stored, and is loaded from there to this location during boot.
I did my best to follow all these steps.
upon reboot, every single thing I put in is lost. Kernel Aduitor seems to lose my settings even if I check 'apply on boot'.
furthermore, all 8 cores are still on.
True, I *do* now see that all the big cores aren't *always* on... but it isn't very different from before doing these steps (at least now I can see a core or 2 shutoff for all of about a tenth of a second)
The little cores... they looked like they took the settings the best... until I closed Kernel Aduitor and reopened it... all the settings reverted.

Yep, waiting with anticipation for some guru who is best at putting something together to set all those freq.'s and such that will apply all of them and keep settings.
Very useful battery mod if it can be made to apply and hold up after restarts.

Yes the hotplug drivers and govenors change it back this is something within the kernal thst you cant edit without needing to flash another rom.. Im on CM13 and batttery has improved quite a bit.. Just give it a try its my daily driver now and its smooth as hell..

Demian3112 said:
Yes the hotplug drivers and govenors change it back this is something within the kernal thst you cant edit without needing to flash another rom.. Im on CM13 and batttery has improved quite a bit.. Just give it a try its my daily driver now and its smooth as hell..
Click to expand...
Click to collapse
Without or before flashing a better ROM, did this item ever get worked out whether by another way to make settings stick or a Huawei small update? Thanks for any advice.
Sent from my MT2L03 using Tapatalk