As some folks had already discovered by finding some test versions, I've been making an app to control the speed of the CPU. Started out as a test to determine if the "1ghz hack" was genuine or not, and ended up to be able to control cpu speed and to overclock to some degree.
First of all. This app is NO LONGER BEING DEVELOPED. You can use it as-is and at your own risk. And no, I won't make a WP7 version.
Features
- Updates CPU speed every half second (calculated from the processor registered directly! not from some driver)
- Can stress the CPU to show you that it goes up to 998mhz under load (when idle speed is less than 998mhz)
- Disable autoscaling so that you can control the speed yourself
- Select the speed you want by moving the slider or pressing 768/998 presets
- Automatically disable autoscaling and set speed at boot (via menu)
- Overclocking
Notes on auto-apply speed at startup
1) Disable autoscaling
2) Select the cpu speed you want
3) Menu > Apply speed at boot
Notes on overclocking
1) Obviously overclocking is completely at your own risk, as you could harm your device. Luckily, in most cases, your device will just lock up and you'll need to restart your device (remove battery, re-insert and turn on again).
2) The green buttons were the overclock settings that have been succesful 9 out of 10 times. The orange speeds have been succesful like 5 out of 10 times. The red speeds have never worked for me yet.
3) The higher the speed, the more unstable. This is mainly because I don't have a way to increase voltage of the core.
4) Overclocking only works on AC power! When on battery power, the overclock will work but will be undone within 500 milliseconds by the OS. Something within the OS, or a driver, or the radio rom, enforces the proper CPU speed every 500ms.
Notes on battery
I have seen only very very miniscule differences on battery usage when using 998MHz all the time. You really wouldn't notice the difference if it were at 998MHz all the time, or at 768MHz (default). The only thing you _do_ notice, is that it feels snappier.
Try playing a decent movie in TCPMP or coreplayer with autoscaling on, and try again with autoscaling off and at 998mhz. Huge difference. (Note that some ROMs already have autoscaling disabled and will run at 998MHz all the time, like CleanEX. You won't notice a difference there obviously.)
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Versions
v4
- For advanced users only: call LeoAutoCpuSpeed.exe with a custom performance level to set that speed (and disable autoscaling if enabled). So, calling "LeoAutoCpuSpeed 12" will set it to 768MHz. And FYI, 18 = 998MHz.
v3
- Add overclock
- Add auto-apply at startup
v2
- Add speed control by slider
- Enable/disable autoscaling
v1
- Initial version (only read cpu speed & stress cpu)
Known issues
Q: Current CPU speed reads 4294967 MHz, that's amazing!
A: Read here why that happens. It's at 128MHz or 256MHz when it shows this.
Q: CPU speed is at 921MHz and pressing 998MHz doesn't change it to 998MHz.
A: Click the 768 button, then the 998 button. It'll be at 998MHz now (has to do with the internals of the driver).
Download
HERE
Thank you! Absolutely must have, works brilliantly.
NICE!!!! Thxs for the update....will test...
THX! I'm already using the v2 and it works well. The only thing I would want to know is how the autoscaling is handled. Sometimes it just stays at 998 MHz and there is no autoscaling(of course autoscaling enabled) and sometime it works. Sometimes it even dropped to .294967 MHz(I think this is the funny thing you mentioned in the other thread as it only happened on AC).
thx, thats a great app
Cab does not work. Just downloaded and installled the cab file. it says that the file "Could not find LeoClockLib.dll" And it exits me.
Fixed: I copied the .dll file from V2 into the startmenu folder under windows and then re-installed V3's cab. it works now. werid.
great app... thank you very much!!!!
do you think there will be a way to leave the overclock on in battery mode and not ac only ?
thank you
for all your work
thank you netripper, was waiting for this
Hey Netripper
first of all thx for this great tool.
I have been playing a bit with the new v3,and I found an extrange behaviour,overclock doesnt seem to work even when the HD2 is in AC/ charging,it displays the overclocked speed and quickly reverts back to 998,but if i start the stress test ,wait a couple of secs and overclock it then it works,even when the phone is not on AC charge!
i can change on the fly the overclocked speed as long as the stress cpu is going on, so its prettty pointless at this stage, but im wondering, either LeoCpuspeed gives the wrong speed and does the stress at 998 displaying wrong overclocked speeds or it does indeed work and keeps the overclocked speed at all time as long as the cpu is doing something.
Im using Chucky rom
Thank you for this great program! It would also be great if you could find a way to maintain overclocking on battery power.
Great app.
miko3d said:
Hey Netripper
if i start the stress test ,wait a couple of secs and overclock it then it works,even when the phone is not on AC charge!
Click to expand...
Click to collapse
I can confirm it. As long as the cpu Stress is activated you can overclock on battery. But stopping it reverts it back to 998MHz. Another thing I noticed, is that as soon as you press the screen, it goes from .4294967 to 768MHz. But if you click with mymobiler, it doesn't change(only when clicking on a button etc.).
miko3d said:
Hey Netripper
first of all thx for this great tool.
I have been playing a bit with the new v3,and I found an extrange behaviour,overclock doesnt seem to work even when the HD2 is in AC/ charging,it displays the overclocked speed and quickly reverts back to 998,but if i start the stress test ,wait a couple of secs and overclock it then it works,even when the phone is not on AC charge!
i can change on the fly the overclocked speed as long as the stress cpu is going on, so its prettty pointless at this stage, but im wondering, either LeoCpuspeed gives the wrong speed and does the stress at 998 displaying wrong overclocked speeds or it does indeed work and keeps the overclocked speed at all time as long as the cpu is doing something.
Im using Chucky rom
Click to expand...
Click to collapse
I am using artemis rom and i also noticed this behavior.
Something I noticed:
Freshly hard reset phone, 1.72 base, WM 6.5.
When running at 998 MHZ the taskbar is updating noticably slower. Just tested a few times to make sure. When pressing the startbutton, showing the start menu, and closing it with the X-button in the corner, the taskbar icons update. With 998mhz, this takes a few moments longer, resulting in a small stutter (pretty much the same as with the weather update). With scaling off and running at 768mhz, the update is definitely faster and stuttering is pretty much gone (as used to).
anyone can check with their device?
Working great, auto-apply at startup was the only thing I was missing in V2. Thanks for a great app.
very nice release! works very well, and loving the new features. thank you!
lemonspeakers said:
Fixed: I copied the .dll file from V2 into the startmenu folder under windows and then re-installed V3's cab. it works now. werid.
Click to expand...
Click to collapse
Glad it works now, but it sounds really weird. You shouldn't need a dll in \windows\startup, only a shortcut (if auto-apply is enabled) to the leoautocpuspeed.exe. The app creates this shortcut when you enable auto-apply. Maybe it conflicted with someleft-overs you had from v2? Dunno otherwise.
radiohead7778580 said:
do you think there will be a way to leave the overclock on in battery mode and not ac only ?
Click to expand...
Click to collapse
I've been trying to figure it out for a while. Also tried patching coredll but I can't find the correct function to patch.
miko3d said:
I have been playing a bit with the new v3,and I found an extrange behaviour,overclock doesnt seem to work even when the HD2 is in AC/ charging,it displays the overclocked speed and quickly reverts back to 998,but if i start the stress test ,wait a couple of secs and overclock it then it works,even when the phone is not on AC charge!
i can change on the fly the overclocked speed as long as the stress cpu is going on, so its prettty pointless at this stage, but im wondering, either LeoCpuspeed gives the wrong speed and does the stress at 998 displaying wrong overclocked speeds or it does indeed work and keeps the overclocked speed at all time as long as the cpu is doing something.
Click to expand...
Click to collapse
Thanks for that observation. That's a nice find. First of all it's weird you cannot overclock on AC the normal way, but it sounds related to the same problem on battery. It's weird that the device stays overclocked when under load. But it might help me localize where to look to fix this.
chalid said:
When running at 998 MHZ the taskbar is updating noticably slower. Just tested a few times to make sure. When pressing the startbutton, showing the start menu, and closing it with the X-button in the corner, the taskbar icons update. With 998mhz, this takes a few moments longer, resulting in a small stutter (pretty much the same as with the weather update). With scaling off and running at 768mhz, the update is definitely faster and stuttering is pretty much gone (as used to).
anyone can check with their device?
Click to expand...
Click to collapse
Are you sure you just disabled autoscaling, and did not press "start test"? To be absolutely sure, start the app, disable autoscaling, set it to 998mz, and press "exit" (the app does not need to keep running). If you still notice the performance hog, it's really weird.
thanks for the fast reply netripper!
continue your great work
I like this tool but now I love.
thanks a lot.
Is there any way to configure SetCPU so it normally runs with the 'conservative' governor (the only one the Epic 4G apparently supports right now), but instantly kicks the CPU up to max and keeps it there whenever a soft keyboard (specifically, Graffiti) is active?
For anybody who's never tried it, Graffiti's accuracy is nearly perfect when the phone is in 'Performance' mode... and, er, a bit more... um... "variable and inconsistent" when it's not. The thing is, my battery life is getting totally nuked by keeping the phone in performance mode all the time.
For me, at least, kicking it to 100% whenever any soft input area is active (without worrying whether it's Graffiti or some other one) is more than good enough.
Failing that, is there a setting that translates to "Performance profile when the screen is on, Conservative profile when the screen is off" so it's at least not running full-bore when the phone is just sitting in my pocket or idle and dark on my desk?
Hi all,
I found out that when I use kyrillos ROM 4.1 OC edition on my samsung galaxy apollo i-5800 then the phone sometimes freezes with only a reboot possible.
It occured to me this happened only in idle (no cpu intensive actions) mode.
With setcpu I raised the lower frequency limit from 83 to 166 Mhz (also in screen-off profile), because I thought the freezing could be related with lower 83 Mhz.
Since then I "never" ran into freezes anymore with my phone...no issues when cpu is between 166 and 1300 mhz (yes no issues even at high clock speed, against all laws ).
I just wanted to share this information for other people having the freezing issue, maybe also on other customized ROMS, just try this min cpu setting if it works for you
BTW I didnt really notice worse battery life with this 'remedy'
Enjoy your phone, it's made for you !!!
Br.
Michel
i5800 freeze
I'm new on this forum, but I'm used to flash my phone.
I got the next problem, I'm running Kyrillos'rom 9.7.1 (update) for 2 weeks.
On my first install of kyrillos my phone freezes when I was 2 minutes working, so I installed setcpu to lower the cpu-speed and It worked.
Now, I had to flash my phone again, because I did something wrong in the system file.
I re-installed the kyrillos 9.7.1 update with Odin, but then, when my phone boots, it almost immediately freezes when I do something.
I don't get the time to install setcpu to lower the freqency
I tried it almost 20 times...
Can anyone help me lowering the frequency?
Thanks!
UPDATE:
It worked, I finaly got into my files to install set cpu! After 30 times rebooting...
But My question is still there, because It's almost impossible for me to flash my phone again now!
Hi,
I have tried different rom + kernel:
cleanrom
ultra fast rom: http://forum.xda-developers.com/showthread.php?t=1901784
untermensch kernel: http://forum.xda-developers.com/showthread.php?t=1892326
and still can't oc the cpu to something higher than 1.3ghz
I used the No-frills CPU as well as the antutu cpu master (free version)
for the No-frills cpu, whenever I set the CPU speed to something high (ie. 1.6ghz max and 102mhz min), checked apply on root then apply, it worked fine for a while, but later on when I open no-frills cpu, th e current max and min will reset back to 1.3ghz and 102mhz.
Governor and I/O scheduler is fine though.
Sounds to me like u need to check start on boot..i havent oveclocked mine yet but option should be there where u select governors and such...
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Of course i have checked that it just didnt work
Give Voltage Control a try. It gives you the options to apply on boot or init.d. I use the init.d setting because the phone boots quicker. I had that problem with CPU Master in the past while running it on my phone.
Sent from my LG-LG855 using Xparent Green Tapatalk 2
Will do, however i dont think it's the reboot problem. The problem was, when i set the cpu speed to 1.5 or 1.6 its works fine for an hour or so ( i closed the cpu app, reopen it and the curent seed got set) but then an hour or so, it got resetted back to 1.3 without rebooting the device
redjersey said:
Will do, however i dont think it's the reboot problem. The problem was, when i set the cpu speed to 1.5 or 1.6 its works fine for an hour or so ( i closed the cpu app, reopen it and the curent seed got set) but then an hour or so, it got resetted back to 1.3 without rebooting the device
Click to expand...
Click to collapse
Hi !
Overclock automatically deactivates when the device enters in standby !
surdu_petru said:
Hi !
Overclock automatically deactivates when the device enters in standby !
Click to expand...
Click to collapse
Ahh, that's what I thought was going on, this is happening to me as well.
treo4life said:
Ahh, that's what I thought was going on, this is happening to me as well.
Click to expand...
Click to collapse
Hi!
No, this happens to everyone
However, it seems a pretty good thing - why we need OC - if the device sleep ? :laugh:
- it is also good for battery - !
So i will have to reoverclock it everytime ??
Mine doesn't do this at all. I use CleanROM 3.1, unters kernel and setcpu. No issues.
I guess I know why it's because setcpu has the profile settings allows u to set the CPU speed when screen is on / when screen is unlocked
Othe CPU apps I have tried have no such feature which means oc works when u set it, but when u turn off the screen then turn it on , it will reset back to 1.3ghz
Using setcpu, what I did was set a "screen off" profile to max out at 1700ghz when the screen is off or in sleep mode and it worked for me!!! That way will not default back to stock 1300ghz everytime I hit screen off or sleep mode.
Hi all, while I was playing a game, I noticed some lag on balanced mode, so I decided to put on performance mode, but lag was still there.
Because of this, I downloaded cpu-z and it seems that on balanced mode just CPU 0 is working, while the other three are stopped (which is fine, I think), but on performance mode, CPU 1 and CPU 2 are stopped, while CPU 0 and CPU 3 are at full speed, heating up the device a lot (up to 70°C).
I'm currently running MIUI 8 v7.6.8 global, full stock.
Is there a way to make all CPUs working at the same time, without keeping all of them at full speed?
Added screenshots of cpu-z both on balanced and performance mode.
https://forum.xda-developers.com/xi...-2-cores-miui-recover-4-cores-miui-7-t3623241
Try this.