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.
Related
As we know, overclocking MSM is possible now. Just check :
http://forum.xda-developers.com/showthread.php?t=725290
Click to expand...
Click to collapse
But the thread is over 1400 post & most of them are about blackstone, Rhodium, etc.. I think it's about time we make a thread about overclocking our Touch Pro(s)
I use GSM unbranded TP100 & TAEL v.5 ROM.
I'll start with my experience :
What Works
Click to expand...
Click to collapse
1. grab the v.2 file from the thread above. (1st page)
2. Install it to phone Memory.
3. Open the Msm7kCpuSpeed & You can see the current CPU speed in Real Time.
4. Whatever speed you select when on Battery Power, it will revert back to 528Mhz because of the Windows component that make sure the clock speed is 528 Mhz every (xx) second.
5. The only way you can overclock is when u plug your USB to Laptop / Stock Charger. Only then you can move the slider to any speed supported by your device.
6. Every device's speed are varied from the ROM used & quality of the MSM in your device. Try what speed are the best speed in your phone before it locks up. I use TAEL v.5 & I can achieve 768 Mhz in AC (original Charger / USB in Laptop/PC) on 787 i get random lockup
7. If you unplug your Raph from USB / Charger on ANY freq other than 604.8 Mhz, your raph will LOCK UP. So, when unplugging / pressing power button make sure u change the freq to 604 Mhz first. (604 Mhz is special Freq that don't Lockup our device)
8. A couple of seconds after we unplug our Raph in 604 Mhz freq it will revert back to 528 Mhz freq.
What almost works
Click to expand...
Click to collapse
From the explanation above we can use Overclock in Our Raph, but only when plugged into a charger / laptop / PC.
In this
PHP:
http://forum.xda-developers.com/showthread.php?t=725290&page=120
thread Qzytor in post 1191 found a way to overclock our MSM devices when using battery power. But in my experience, it ALWAYS lockup a few seconds after opening the phone dialer, coreplayer (playing video for a few second the lockup), SMS messaging, and Teeter (lockup when level up)
I'll write my experince using above method :
The method is : (Credit goes to Qzytor)
Code:
Install NetRippers Msm7kCpuSpeed V.2 App. in your Device
Install SetCpuSpeed v1.0d on SD card. --get it @ http://forum.xda-developers.com/showpost.php?p=7426966&postcount=1000 --
Take SD card out and soft reset the phone.
Open registry.
Go to HKLM\Software\Msm7kCpuSpeed.
Edit the values as below:
BootTime = 90000 (This is important. This value gives enough time for the
phone to fully boot up. The phone has to fully boot up
before the OC kicks in)
CheckTime = 20 (Stable at 20, otherwise yoyos between base and OCed
cpu speed)
Command = 0
PerfomanceLevel = 35 (This speed is stable for me without SOD)
ScreenOffPerfomanceLevel = 27
SettlingTime = 10
Close Registry editor, insert SD card in the phone and soft reset the phone.
Once the phone has fully boot up, give it a minute before opening NetRippers Msm7kCpuSpeed and you should see your OCed cpu speed.
If your OC cpu speed isnt stable then take your SD card out,soft reset the phone and registry edit PerfomanceLevel to a lower value.
To restore back to phone default speed:
Open File Explorer.
Go to Windows\Startup folder and delete SetCpuSpeed.
Soft reset the phone and phone default speed will be restored.
Before deleting SetCpuSpeed from Windows\Startup folder , save it in Documents folder so if you want to overclock again, copy and paste it from Documents folder to Windows\Startup folder.
1. Performance Level 35 is overclocking @ 672 Mhz
2. Add 1 level means add 19.2 Mhz in clock speed
3. The best speed i reach in AC power (USB / Laptop) is 768 Mhz = performance level 40
4. I change my performance level into 40 & I can see in MSM7kCpuSpeed that i'm running 768 Mhz after 90 seconds from the bootup as written above.
5. a few programs can run ok in 768 Mhz or any speed in that matter, but most causes lockup. This does NOT happen in Blackstone / Rhodium
6. Even on performance level = 35 (672 Mhz) or even in Performance level = 27 i still got a lockup opening phone, SMS, coreplayer, teeter, & FPSECE (only when exiting). they work fine on AC power.
7. I dont know if it's because of my ROM (TAEL v.5) or if all RAPH experience the same Issue.
I hope we can continue to improve overclocking our RAPH to the point it can perfectly works ^^
Another OC program
There is also this Overclock Tool:
http://forum.xda-developers.com/showpost.php?p=7463284&postcount=162
I haven't tried it yet, but it should work with our Raphael, and also on battery power.
I'm using touchpro and newest energy cookie rom.
Tried the method mentioned by b0z0k. Set level 35 for the 1st trial
Apps tried list:
Youtube
Opera
text message
File explorer
excel mobile
google mpas
teeter
window media player (not the music tab in sense)
lockup when playing teeter and music (the sense one). However, for other programs, it was just working brilliantly.
Really hope my experience can help.
After turning it to level 35, the device looks quite stable but i haven't tried any levels upper than that.
zai_hkman said:
I'm using touchpro and newest energy cookie rom.
Tried the method mentioned by b0z0k. Set level 35 for the 1st trial
Apps tried list:
Youtube
Opera
text message
File explorer
excel mobile
google mpas
teeter
window media player (not the music tab in sense)
lockup when playing teeter and music (the sense one). However, for other programs, it was just working brilliantly.
Really hope my experience can help.
After turning it to level 35, the device looks quite stable but i haven't tried any levels upper than that.
Click to expand...
Click to collapse
Yes, i just tried Energy ROM 1-2 days & Overclock works like a charm. Don't hestitate to use higher freq.. i found out that the best stable freq in my device are @ 748.8. 787 will instantly freeze my TP, 768 works but many apps crashing, 748.8 works very well with FpseCE
What i did, is try the newest energy ROM (rel. 23673, GTX, dinik version) & it all work like a charm. Sure, i still got occasional SOD but it's waaaaaaayyyyyy better than having to OC in Laptiop USB only..
So i think the issue i had earlier is definitely with the ROM (I think TAEL rom has some kind of energy saving script that keeps telling the CPU what clock it's running -- even when setCPUspeed already installed)
After i change to Energy Rom rel. 23673, on battery power, MSM7kCPUspeed+setCPUspeed v1.0d runs just as smoothly as AC power. I get occasional SOD only when exiting Fpsece (it makes the CPu drop to 384 Mhz then it froze). Using WMP, TCPMP, & other apps that usually crashes on TAEL v5 did NOT give me the "freeze"
@ 748.8 Mhz FPSEce gives me 5-8 fps boost with no frameskip , with frameskip i can play Final Fantasy Tactics @ 50 fps with no noticable errors (about 29 fps in landscape no frame skip)
And that makes me...
--> very happy TP owner
p.s. a little trick when having a non OC applicable ROM is to use your GPS programs (garmin, sygic, etc), minimize them, & run MSM7kcpuspeed to OC your device. this usually works ok.. Just a very bad battery consumption
& dont forget to change back to 604 Mhz before shutting down your GPS program & then u can power off the screen -- or else u get the SOD.
An update on usage:
I've just flashed to the updated rom for energy(Aug18 Cookie 23678)
After that, I overclock the device by the previous method.
I found that the device freezes everytime when i receive calls. Therefore,I have to remove the setcpu.ink in the window to stop overclocking. Anyone has figured out why the device freezes on some program but behave normal for the most of the time?
zai_hkman said:
An update on usage:
I've just flashed to the updated rom for energy(Aug18 Cookie 23678)
After that, I overclock the device by the previous method.
I found that the device freezes everytime when i receive calls. Therefore,I have to remove the setcpu.ink in the window to stop overclocking. Anyone has figured out why the device freezes on some program but behave normal for the most of the time?
Click to expand...
Click to collapse
This is the biggest problem I have. Theres certain parts of the day while working that I use my phone a lot, and the SOD's with phone can cause me to miss calls or be unable to place a call (SOD while dialing).
Im still waiting for some sort of option to totally disable itself when a named program is run.
hartleyshc said:
This is the biggest problem I have. Theres certain parts of the day while working that I use my phone a lot, and the SOD's with phone can cause me to miss calls or be unable to place a call (SOD while dialing).
Im still waiting for some sort of option to totally disable itself when a named program is run.
Click to expand...
Click to collapse
Just about 2-3 days now i have SOD while dialing too.. I don't know what's causing it, but i can confirm that after a fresh ROM flash (energy build 23673) i CAN dial in my phone while overclocked @ 768 Mhz.. After a lot of install, trial, etc now i have SOD EVERYTIME i dial in phone dialer.
p.s. before SOD's occured i just set up my GPRS/3G connection for my carrier.. i wonder if this is the cause?
b0z0k said:
Just about 2-3 days now i have SOD while dialing too.. I don't know what's causing it, but i can confirm that after a fresh ROM flash (energy build 23673) i CAN dial in my phone while overclocked @ 768 Mhz.. After a lot of install, trial, etc now i have SOD EVERYTIME i dial in phone dialer.
p.s. before SOD's occured i just set up my GPRS/3G connection for my carrier.. i wonder if this is the cause?
Click to expand...
Click to collapse
Maybe.. I do the carrier auto-setup once i boot a new rom. (AT&T USA). It might be some settings in there messing with it.
The test I do to see if it freezes is this: Call my voicemail (google voice) and just keep hitting "7" a bunch of times and see if it freezes.
Ive also tried various phone canvases. Have tried the new one currently being cooked into NRG roms (aug 18th) before it was cooked in, will try again now to see if anything has changed.
edit: I have also been following and trying all versions of iwfratz's overclock tool, and compatibility actually seems to get worse with each new release. the original version would crash after a while at the stock 650, which on my TP its much more stable at 633. But with current versions (1.5) it crashes immediately after setting the overclock, a version or two ago it would run, but would still crash when using the phone app.
i use nrg rom 21914 and overclock with msm7kcpu speed +setup cpu 1.0d.
4 "bugs/[email protected],6Mhz":
-phone works great, untill i receve a call, than the phone hangs.
-also the phone hangs, when i will use nitrogen 1.1 to listen to music.
-and the phone hangs, when my alert goes on and i have the lockscreen activatet.
-when i receve a mms and downloaded it, the phone hangs also
after the hang, i need to put the batterie out of the tp to restart....
@ ~746 the phone starts but sense restarts again and again...but in the 6.august of nrg rom, i thought this speed works also ...
maybe someone know an answere.
I love the speed i wouldn't miss it...i already sold my Acer s200, because it is crap
New Method, No Freeze in Phone dialer, but battery more inefficient
New Method, No Freeze in Phone dialer, but battery more inefficient
I have tried SetCPUspeed v1.0d & it made the Overclock working BUT i dont know why every time I open dialer screen or an SMS came, it always freezes.
I think it has to do with the fact that WinMo in our TP consistantly checking the speed/ frequency of our MSM.
The only way we can bypass this :
1. When we connect to our laptop (activesync) -- when we connect Raph to PC & it starts sync-ing in activesync, the speed/ freq check disabled, this is an exploit that we can use to overclock safely. BUT..
We do need our laptop / PC to do this (we can't overclock when we're traveling & want to play FpseCE in full speed ^^)
2. THE NEW METHOD -- more battery draining though.. We can bypass the freq check using GPS module. When the GPS is ON, the speed check is disabled. This way, even when we're traveling, we can still Overclock our Raph safely (wont freeze when opening dialer / receivinf SMS.
But, it's still opening GPS module, it's a battery drainer. In my experience it's about 20% faster draining the battery. Use HTC GPS tool & choose "open port"
What i do is :
when the phone is not used (deep sleep), i don't use the Overclock. When i want to use something in my phone & i want to boost it's speed i will turn on HTC GPS tool & overclock my phone to 729,6 (the most stable for me). When i'm done & want to put my phone to sleep, i made my MSM7kCPUSpeed to 604 Mhz (safe speed, wont freeze) & i turn off the GPStool.
When i press the power button the freq will change to 528 Mhz again & the battery consumption became normal again. ^^
It's a turn around from the problem we're facing.. but Hey, i got to play Final Fantasy Tactics @ nearly full speed ^^
After a little testing, no freezes anymore.^^
However, if we disable the frequency check, we are not able to stablize the frequency.
What I mean is that sometimes after a call or running some programs, the frequency will drop to about 355 and I have to open MSM7kcpuspeed again to adjust the frequency.
Anyway, this is really a breakthough for overclocking out TP.
still got bugs
I love the increase of speed, when the device is overclocked.
But i got still bugs.
When i want to listen to music, it hangs after about 1-2 secounds. i don't know why.
Maybe you can help me with this problem, because i dont want to have only 527mhz.
my settings:
my BootTime = 90000
CheckTime = 20
Command = 0
PerfomanceLevel = 38
ScreenOffPerfomanceLevel = 27
SettlingTime = 10
best regards
i know it's an old thread, but is any new way public to overclock the touch pro?
atm i need to use it @ normal speed, because it is really buggy @ overclocked=/
As we know, overclocking MSM is possible now. Just check :
http://forum.xda-developers.com/showthread.php?t=725290
Click to expand...
Click to collapse
But the thread is over 1400 post & most of them are about blackstone, Rhodium, etc.. I think it's about time we make a thread about overclocking our Touch Pro(s)
I use GSM unbranded TP100 & TAEL v.5 ROM.
I'll start with my experience :
What Works
Click to expand...
Click to collapse
1. grab the v.2 file from the thread above. (1st page)
2. Install it to phone Memory.
3. Open the Msm7kCpuSpeed & You can see the current CPU speed in Real Time.
4. Whatever speed you select when on Battery Power, it will revert back to 528Mhz because of the Windows component that make sure the clock speed is 528 Mhz every (xx) second.
5. The only way you can overclock is when u plug your USB to Laptop / Stock Charger. Only then you can move the slider to any speed supported by your device.
6. Every device's speed are varied from the ROM used & quality of the MSM in your device. Try what speed are the best speed in your phone before it locks up. I use TAEL v.5 & I can achieve 768 Mhz in AC (original Charger / USB in Laptop/PC) on 787 i get random lockup
7. If you unplug your Raph from USB / Charger on ANY freq other than 604.8 Mhz, your raph will LOCK UP. So, when unplugging / pressing power button make sure u change the freq to 604 Mhz first. (604 Mhz is special Freq that don't Lockup our device)
8. A couple of seconds after we unplug our Raph in 604 Mhz freq it will revert back to 528 Mhz freq.
What almost works
Click to expand...
Click to collapse
From the explanation above we can use Overclock in Our Raph, but only when plugged into a charger / laptop / PC.
In this
PHP:
http://forum.xda-developers.com/showthread.php?t=725290&page=120
thread Qzytor in post 1191 found a way to overclock our MSM devices when using battery power. But in my experience, it ALWAYS lockup a few seconds after opening the phone dialer, coreplayer (playing video for a few second the lockup), SMS messaging, and Teeter (lockup when level up)
I'll write my experince using above method :
The method is : (Credit goes to Qzytor)
Code:
Install NetRippers Msm7kCpuSpeed V.2 App. in your Device
Install SetCpuSpeed v1.0d on SD card. --get it @ http://forum.xda-developers.com/showpost.php?p=7426966&postcount=1000 --
Take SD card out and soft reset the phone.
Open registry.
Go to HKLM\Software\Msm7kCpuSpeed.
Edit the values as below:
BootTime = 90000 (This is important. This value gives enough time for the
phone to fully boot up. The phone has to fully boot up
before the OC kicks in)
CheckTime = 20 (Stable at 20, otherwise yoyos between base and OCed
cpu speed)
Command = 0
PerfomanceLevel = 35 (This speed is stable for me without SOD)
ScreenOffPerfomanceLevel = 27
SettlingTime = 10
Close Registry editor, insert SD card in the phone and soft reset the phone.
Once the phone has fully boot up, give it a minute before opening NetRippers Msm7kCpuSpeed and you should see your OCed cpu speed.
If your OC cpu speed isnt stable then take your SD card out,soft reset the phone and registry edit PerfomanceLevel to a lower value.
To restore back to phone default speed:
Open File Explorer.
Go to Windows\Startup folder and delete SetCpuSpeed.
Soft reset the phone and phone default speed will be restored.
Before deleting SetCpuSpeed from Windows\Startup folder , save it in Documents folder so if you want to overclock again, copy and paste it from Documents folder to Windows\Startup folder.
1. Performance Level 35 is overclocking @ 672 Mhz
2. Add 1 level means add 19.2 Mhz in clock speed
3. The best speed i reach in AC power (USB / Laptop) is 768 Mhz = performance level 40
4. I change my performance level into 40 & I can see in MSM7kCpuSpeed that i'm running 768 Mhz after 90 seconds from the bootup as written above.
5. a few programs can run ok in 768 Mhz or any speed in that matter, but most causes lockup. This does NOT happen in Rhodium (Touch Pro 2)
6. Even on performance level = 35 (672 Mhz) or even in Performance level = 27 i still got a lockup opening phone, SMS, coreplayer, teeter, & FPSECE (only when exiting). they work fine on AC power.
7. I dont know if it's because of my ROM (TAEL v.5) or if all RAPH experience the same Issue.
I hope we can continue to improve overclocking our RAPH to the point it can perfectly works ^^
Im happy that there are people that want to work on oc project for touch pro..I want to help even i dont know much..
I dont get the disconnect ac issues at all, but definitely get the freezing on the phone app, but apparently other phones do as well.
Im waiting for somesort of blacklist option that can actually close the overclock *and not just revert back to 528*.
Have done tests with netrippers app, setcpuspeed 1.0d, iwfratz oc tool, and oc auto 4.1 (this doesn't work with mine, I use the latest Energy rom, and Im part of the "1%" that doesn't have certain registry settings, and it doesn't work by adding them.)
hartleyshc said:
I dont get the disconnect ac issues at all, but definitely get the freezing on the phone app, but apparently other phones do as well.
Im waiting for somesort of blacklist option that can actually close the overclock *and not just revert back to 528*.
Have done tests with netrippers app, setcpuspeed 1.0d, iwfratz oc tool, and oc auto 4.1 (this doesn't work with mine, I use the latest Energy rom, and Im part of the "1%" that doesn't have certain registry settings, and it doesn't work by adding them.)
Click to expand...
Click to collapse
Yes, I agree, Iwfratz's OC tool are NOT WORKING on other device other than RHODIUM. So the best option i have is NetRipper's App + SetCPUspeed 1.0d. Can't work OC auto for some reason (no key binding App to bind mortscript down.mscr to power button).
What i did, is try the newest energy ROM (rel. 23673, GTX, dinik version) & it all work like a charm. Sure, i still got occasional SOD but it's waaaaaaayyyyyy better than having to OC in Laptiop USB only..
So i think the issue i had earlier is definitely with the ROM (I think TAEL rom has some kind of energy saving script that keeps telling the CPU what clock it's running -- even when setCPUspeed already installed)
After i change to Energy Rom rel. 23673, on battery power, MSM7kCPUspeed+setCPUspeed v1.0d runs just as smoothly as AC power. I get occasional SOD only when exiting Fpsece (it makes the CPu drop to 384 Mhz then it froze). Using WMP, TCPMP, & other apps that usually crashes on TAEL v5 did NOT give me the "freeze"
@ 748.8 Mhz FPSEce gives me 5-8 fps boost with no frameskip , with frameskip i can play Final Fantasy Tactics @ 50 fps with no noticable errors (about 29 fps in landscape no frame skip)
And that makes me...
--> very happy TP owner
p.s. a little trick when having a non OC applicable ROM is to use your GPS programs (garmin, sygic, etc), minimize them, & run MSM7kcpuspeed to OC your device. this usually works ok.. Just a very bad battery consumption
& dont forget to change back to 604 Mhz before shutting down your GPS program & then u can power off the screen -- or else u get the SOD.
b0z0k said:
Yes, I agree, Iwfratz's OC tool are NOT WORKING on other device other than RHODIUM. So the best option i have is NetRipper's App + SetCPUspeed 1.0d. Can't work OC auto for some reason (no key binding App to bind mortscript down.mscr to power button).
What i did, is try the newest energy ROM (rel. 23673, GTX, dinik version) & it all work like a charm. Sure, i still got occasional SOD but it's waaaaaaayyyyyy better than having to OC in Laptiop USB only..
talled)
After i change to Energy Rom rel. 23673, on battery power, MSM7kCPUspeed+setCPUspeed v1.0d runs just as smoothly as AC power. I get occasional SOD only when exiting Fpsece (it makes the CPu drop to 384 Mhz then it froze). Using WMP, TCPMP, & other apps that usually crashes on TAEL v5 did NOT give me the "freeze"
@ 748.8 Mhz FPSEce gives me 5-8 fps boost with no frameskip , with frameskip i can play Final Fantasy Tactics @ 50 fps with no noticable errors (about 29 fps in landscape no frame skip)
Click to expand...
Click to collapse
Im getting with the newest nrg rom the same problems..new calls or sms and the phone needs reset..
The best trick of all its just to overclock your phone to max mhz your phone can stand unlagged and move the shortcut from startup to start menu..So you can use it from start menu only for the programms you want to use..When you finish you make a reset..And everything goes to normal again..In my "normal mode" im using nuedynamicclock for max performance of cpu..From "Battery life" side - nuedynamicclock(max performance)+timolols rom it stands <> 2 days..
New Method, No Freeze in Phone dialer, but battery more inefficient
New Method, No Freeze in Phone dialer, but battery more inefficient
I have tried SetCPUspeed v1.0d & it made the Overclock working BUT i dont know why every time I open dialer screen or an SMS came, it always freezes.
I think it has to do with the fact that WinMo in our TP consistantly checking the speed/ frequency of our MSM.
The only way we can bypass this :
1. When we connect to our laptop (activesync) -- when we connect Raph to PC & it starts sync-ing in activesync, the speed/ freq check disabled, this is an exploit that we can use to overclock safely. BUT..
We do need our laptop / PC to do this (we can't overclock when we're traveling & want to play FpseCE in full speed ^^)
2. THE NEW METHOD -- more battery draining though.. We can bypass the freq check using GPS module. When the GPS is ON, the speed check is disabled. This way, even when we're traveling, we can still Overclock our Raph safely (wont freeze when opening dialer / receivinf SMS.
But, it's still opening GPS module, it's a battery drainer. In my experience it's about 20% faster draining the battery. Use HTC GPS tool & choose "open port"
What i do is :
when the phone is not used (deep sleep), i don't use the Overclock. When i want to use something in my phone & i want to boost it's speed i will turn on HTC GPS tool & overclock my phone to 729,6 (the most stable for me). When i'm done & want to put my phone to sleep, i made my MSM7kCPUSpeed to 604 Mhz (safe speed, wont freeze) & i turn off the GPStool.
When i press the power button the freq will change to 528 Mhz again & the battery consumption became normal again. ^^
It's a turn around from the problem we're facing.. but Hey, i got to play Final Fantasy Tactics @ nearly full speed ^^
b0z0k said:
2. THE NEW METHOD -- more battery draining though.. We can bypass the freq check using GPS module. When the GPS is ON, the speed check is disabled. This way, even when we're traveling, we can still Overclock our Raph safely (wont freeze when opening dialer / receivinf SMS.
But, it's still opening GPS module, it's a battery drainer. In my experience it's about 20% faster draining the battery. Use HTC GPS tool & choose "open port"
What i do is :
when the phone is not used (deep sleep), i don't use the Overclock. When i want to use something in my phone & i want to boost it's speed i will turn on HTC GPS tool & overclock my phone to 729,6 (the most stable for me). When i'm done & want to put my phone to sleep, i made my MSM7kCPUSpeed to 604 Mhz (safe speed, wont freeze) & i turn off the GPStool.
When i press the power button the freq will change to 528 Mhz again & the battery consumption became normal again. ^^
It's a turn around from the problem we're facing.. but Hey, i got to play Final Fantasy Tactics @ nearly full speed ^^
Click to expand...
Click to collapse
Ive played around with the gps issue before. Silly me forgot about simply opening the port in gpstool. I was using google maps till the gps would time out on me.
Without the constant cpu checking, I can safely go up to a much higher speed now! (710. 729 makes sense start to crash occasionally)
Now a few questions I will probably answer myself in the next few hours. Will the gps port ever turn itself off? even when going to sleep? Is there a way to open the gps port at start up? will setcpuspeed work better with this? (turn the check time up to 500, or 1000, not 20 like we were working with earlier?
And the big one.. can we use mortscript to enable/disable the gps port? we could just use our own script to overclock our phones. will look more into mortscript later.
edit: this makes me begin to think this might be a rom issue. what is causing the cpu checks? can anything be done to disable it? i know the blackstone users have a similar issue to us with the cpu checking. any chefs/programmers want to shed some light on this?
Battery tweak can be found HERE:http://www.mediafire.com/?xmjdd797f6v2m90
Tweak can only be used with No HAVS kernels (recommended kernels below)
What is the battery tweak exactly? More information in this thread:http://forum.xda-developers.com/showthread.php?t=810940
The intended scope of this thread is for people having trouble with Ksoft consuming too much CPU resources
DO NOT USE WITH SETCPU!
Ksoftirq is something in the kernel that manages requests to the CPU. That means some device in your system is sending the processor a slew of IRQs so that the softirqd for your processor is being consistenly woken up, which ends up using most of your CPU cycles, thus sucking your battery life and performance. As indicated before, anything with a "K" in front of it is referring to the kernel. A kernel is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components).
When the ksoftirq is using such a high percentage of CPU, it is causing your CPU to work harder and doing two things that we dont' want; taking away from performance and draining the battery.
As it stands now, we know that depending on what kernel you're using it is going to determine whether or not you have that problem in the tweak. We know that it is not an app that is sending processes to the CPU that is causing the problem.
Don't fret if you read through this thread (http://forum.xda-developers.com/showthread.php?t=810940) and flash 1 of the 2 kernels known to work and it still shows ~30%, you're probably just not doing it right. You cannot simply just flash a new kernel, because as said before, the kernel is the link between software(battery tweak) and hardware. Therefore you must have the new kernel in place, then go about flashing the battery tweak. That way it is installed properly by the proper kernel.
As of now, there are 2 known kernels compatible with this tweak:
STOCK HTC 11 kernel, modded: http://www.mediafire.com/?i7u103j9xqnaw3s
Netarchy NoHAVS kernel: http://forum.xda-developers.com/showthread.php?t=719763
**Scroll down and you will see NoHAVS kernel by request, I have had better luck and amazing battery life with Netarchy's kernel
Instructions:
1. Open terminal emulator, type su. You will be prompted that you have gained superuser access
2. Type batt-cfg, then press 1 and then enter when dialog comes up about having root access
3. Choose option 4 to Disable battery tweak, then 9 to save changes and exit
4. Type batt-rm.sh, follow directions to remove tweak (It will tell you to choose y/n, choose "y"
5. Reboot your phone into recovery and install new kernel from zip. When that is finished, install battery tweak.
**It is ESSENTIAL that you follow these first 5 steps in order or I promise you that you will have the same ksoft issue over and over again**
6. When you reboot your phone, go into terminal emulator and type su again.
7. After gaining root access, type batt-cfg. Choose option 1 and save changes and exit.
8. Make sure that phone is unplugged from computer/wall! This is very important, having the phone plugged in will not show the ksoft process so you will not know whether it is still a problem or not.
9. Type top "-m 5 -n 1"(without quotes) This will show you your top CPU processes. You should see no abnormally high percentages for system or ksoft particularly. What percentage you see can depend on your current battery life when you run this test. Make sure that your phone is not plugged in when running the test! Also, take note of your battery life.
Tweak Will stick after reboot. You do not need to re-enable it.
If you install system monitor, you will be able to monitor the cpu level. When I am not touching the screen of my phone, it shows 245mhz. When I start moving the screen or etc, it hikes up a little bit. This shows that the tweak is working properly.
I have gotten incredible battery life out of this with very heavy usage(facebook, texting, phone calls, gps, pandora, running command prompts, etc).
Until something new comes around that I am sure will give me equally as good or better performance and battery life, I will not be switching ROMS/kernels EVER!
ROM: Myn's Warm 2.2
Kernel: Netarchy NoHAVS
Sidenote- I have just as good of performance and speed as I did while having CM6 with Snap7.6&turbo enabled, so don't think that you are sacrificing any performance.
Hope this clears up everything for everyone!
UPDATE-
There has been much debate as to whether or not this tweak works or not. I should have been more clear in the original post. Ksoft is still a necessary process, however, when I said that the purpose was to elimate the "ksoft problem" I was meaning that it should not be detectable by the CPU when you run the "top -m 5 -n 1" command. Neotelos_com made a very good point that is necessary to understand this tweak, "ALSO, this tweak lowers the CPU speed as the battery drains, so within the first hour you will notice the most battery drain." This means a few different things:
-Depending of the charge of your battery when you run the top 5 command, you will see different percentages of ksoft. For example, if I run the top 5 command right now, my battery is at 30% and ksoft doesn't even register at all. Assuming that I charge my battery full and run the top 5 command in the morning when my battery is fully charged, it will register as a process. Ksoft in the low ~20% is completely normal with a full charge. IT WILL BECOME LESS LESS AS THE BATTERY DRAINS.
-I have been toying with this in the very little free time that I have had the past couple days and have also discovered a few other things. Programs like Ultimate Juice, Juice Defender, and Tasker used in coherence with the battery tweak will improve a already great mod to give you significantly more battery life than before. the main reason being that 90% of the time your cell stanby is what is draining your battery the most. Those programs will turn off your mobile network when you are not using it saving a TON of battery power.
I will be posting screenshots at the conclusion of my testing either late tomorrow night or wednesday around 12ET. I want to be able to provide everyone with the info that they need to be able to get the best life out of your battery possible.
Contributions:
intheb0x
Neotelos_com
Myn
Developers of battery tweak
So, is seeing ksoftirqd in step 9 bad?
Techrocket9 said:
So, is seeing ksoftirqd in step 9 bad?
Click to expand...
Click to collapse
It depends what percentage of CPU it is using; in my experience it had been 20+ percent every time when I had the problem.
Is this good or bad? I would guess bad if i'm reading it right.
{
"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"
}
Changed Screen Shot. Keyboard was hiding results
nugzo said:
Is this good or bad?
Click to expand...
Click to collapse
Try exiting out and then do it again. Mine showed up but still showed ksoft.
Sent from my PC36100 using XDA App
when you say incredible battery life...how many hours are we talking about
Using this with SetCPU = fail?
freeza said:
Using this with SetCPU = fail?
Click to expand...
Click to collapse
Yes, do not use this with SetCPU. It is unnecessary and will cause conflict as both are going to be scaling your CPU.
jhoffy22 said:
It depends what percentage of CPU it is using; in my experience it had been 20+ percent every time when I had the problem.
Click to expand...
Click to collapse
I just uninstalled, followed directions to the T again with netarchies no havs, this time 37%. Hmmm not working for me.
flam253 said:
when you say incredible battery life...how many hours are we talking about
Click to expand...
Click to collapse
It will be different for everyone based on usage, quality of service in your area(how hard your phone is working to give you good service), and a number of other things. I can't tell you exactly how many hours but I can tell you this...after configuring this battery tweak correctly, battery life has nearly doubled. It's only been one day, but to this point I am extremely satisfied and never looking back. I will report further on this in the future and provide screen shots of my battery usage and Juice Plotter graphs.
nugzo said:
I just uninstalled, followed directions to the T again with netarchies no havs, this time 37%. Hmmm not working for me.
Click to expand...
Click to collapse
What ROM are you using?
OK for clarity are we suppose to have one of those kernels installed before following the instructions or only during step 5?
JaiCameron said:
OK for clarity are we suppose to have one of those kernels installed before following the instructions or only during step 5?
Click to expand...
Click to collapse
It doesn't matter what kernel you have originally, just make sure that before you flash the battery tweak you have it completely disabled and removed and use one of the two suggested kernels when you reflash the tweak.
Im getting "batt-cfg: not found"
JaiCameron said:
Im getting "batt-cfg: not found"
Click to expand...
Click to collapse
You must not have the battery tweak flashed. You need to go to the forum and find the original thread of the collin_ph battery tweak and get the zip file and flash that separately and after flashing the kernel.
Sorry, this was a quick write up and I left out some information for people who weren't familiar with what the battery tweak is exactly.
Mine still shows ksoft.
Sent from my PC36100 using XDA App
heres the post to the updated one FOR THE ERIS, NOT the evo, BUT it has more features, and the creator is in the thread, lots of info about different settings, how things work and so on..
http://forum.xda-developers.com/showthread.php?t=784089
i think i found out all the bugs from this tweak, there may be more, but i think through about a week and a half through my own trial and error, ive found out everything and whats going on. If working correctly (NO KSOFT), you can achieve great battery life.
hopefully the coder from that thread will update the battery tweak we use to include the temperature mod, since my phone overheats and could really benefit from that feature.
if you wanna be more customized, i recommend choosing option 3 and setting it up your way.
heres what i set.
i left it on underclock
i left the governor alone
i also chose deadline instead of noop.
Min cpu- 245000
max cpu 768000
for polling, instead of 60, i used 120 and instead of 15 i used 30,
then when it gets to cpu usage when battery is low, i choose 28 instead of 33.
you can change these numbers to your choosing, but with these above, i noticed no performance issues and everything seemed normal, just with extra battery life.
but with all our heads together, we can work everything out and get this tweak perfect...
Not working. Myn 2.2 netarchy noHAVS kernel. Showing 28% k...irq
Sent from my PC36100 using Tapatalk
What % should cpu be at to determine if the tweak works or not?
JaiCameron said:
What % should cpu be at to determine if the tweak works or not?
Click to expand...
Click to collapse
Go into terminal, run "top -m 5 -n 1" (without the quotes) and if you system says anything more than 20% the tweak is not working correctly.
Hey everyone,
Lately I've been in the works of trying to get better battery life, as I only get about 2 - 2.5 hours of on screen time. I've seen other users get anywhere between 5-7 hours. I do use facebook, and have uninstalled the official facebook app for the friendcaster one, but have yet to still hit anywhere near that amount of time.
Out of curiosity, and hopefully future reference for other users, what are some great ways to boost battery life? Do you use apps? Uninstall software? Please, do share!
justin0025 said:
Hey everyone,
Lately I've been in the works of trying to get better battery life, as I only get about 2 - 2.5 hours of on screen time. I've seen other users get anywhere between 5-7 hours. I do use facebook, and have uninstalled the official facebook app for the friendcaster one, but have yet to still hit anywhere near that amount of time.
Out of curiosity, and hopefully future reference for other users, what are some great ways to boost battery life? Do you use apps? Uninstall software? Please, do share!
Click to expand...
Click to collapse
Manually controlling screen brightness was the biggest increase for me. The other one that helped was 2g data when i turn off the screen.
Freeeeze apps with Titanium Backup. You wont miss anything neither you loose perfomance, no you gain.
Sent from my HTC One S using xda premium
Change notification updates to suit your needs. Stuff that you don't need to know right away, lower frequency or turn to manual. For instance:
- Change weather updates to every 1-2 hours, unless you really need to know that it changed by a couple degrees as it does.
- Decrease facebook notifications (big one. If you use it a lot, then keep it high, but realize that this WILL drain battery.)
- Manually update stocks (again, if you don't need them instantaneously)
- Blog & News apps usually set notifications on by default, disable or lower frequency on them
- Lower screen brightness
- Turn display to auto sleep 30sec-1min tops
Note that while some of the notification controls can be found within the system settings, many apps will require you to go to their individual settings to adjust them.
All depends what you do with it. Navigation, internet, talk time and intense games all suck up more battery. That doesn't mean you shouldn't do that stuff, but it's just the way it is on any device.
Simple, root and install CPU sleeper, that should give u a lot of battery life.. at least that's how I do it and today I unplugged my phone at 10 am and its 9:25 and I have 65% left
Sent from my HTC One S Unlocked
using XDA Premium
justin0025 said:
Hey everyone,
Lately I've been in the works of trying to get better battery life, as I only get about 2 - 2.5 hours of on screen time. I've seen other users get anywhere between 5-7 hours. I do use facebook, and have uninstalled the official facebook app for the friendcaster one, but have yet to still hit anywhere near that amount of time.
Out of curiosity, and hopefully future reference for other users, what are some great ways to boost battery life? Do you use apps? Uninstall software? Please, do share!
Click to expand...
Click to collapse
Almost all of em are running on custom roms I beat and I'm the one you said that with 5 - 7 hours screen time everyday. There are many things to do to maximum the battery performance and first thing is root and unlock your phone and flash a custom rom. If you are on stock rom, it would be almost a no go.
1. Flash ViperOneS 1.2 rom or One maximuS V2.5 rom, they are the best sense based rom with the greatest battery performance I've seen.
2. If you don't need sense, flash cm10 or aokp. They should give you more battery because they aren't as resources hog as sense. However, you couldn't use sense UI and access to the dedicated image chip in camera.
3. Turn the brightness level down to as low as possible, this is the major battery killer.
4. Switch to 2G when you are in standby mode. Disable fast dormancy, it will save you battery in standby mode at the cost of connection speed when you surf web it will be slower but it does save you some battery in standby status. You can disable it in ViperOneS's tweaking but you'll have to do it manually in all other roms but that is very very easy. Personally, I let it on because the 3G speed isn't good in Hong Kong, too many iphone/android everywhere here, over crowed. In every street in HK are messed up by SGS3/Note/Note2/Iphone, think about how horrible it is.
http://forum.xda-developers.com/showthread.php?t=1684604
5. Turn off wifi when you don't use it, disable max performance in wifi setting. Turn the auto-sync off when you don't need it too.
6. Just remove all apps and bloatware you don't want. When you flash ViperOneS/maximuS 's add-on, you will have a list to do it.
7. Some bloatware will still be there after flash the add-on. You have to download systemapp remover to del those apps.
8. Some apps like to run as services mode and they drain battery in background like youtube, google map, playstore. You need to download AutoStarts and force them to disable as an auto-startup services after bootup.
9. Download Systempanel and check any non-system apps running at services mode in background. Force them stop in control panel. I only have four non-system apps let them running as services like whatsapp.
10. Don't run too many widgets, I only have two widgets on. Don't use 3D wallpaper.
11. Use opera mobile to surf web. The stock browser and chrome should faster but sometimes they drain battery real quick.
12. Turn the cpu mhz down when you are just doing some normal/easy works because the stock kernel has very suck governor performance(only ages governor: on-demand, save battery, max performance) and drains battery fast. Turn the cpu mhz back to high level only when you play games, this will save you great battery. Don't worry S4 CPU is still very powerful even you set it to half speed. You can flash custom kernel if you don't like to turn cpu speed up/down, they introduce more efficiency governors to handle it automatically but all 3rd kernels are likely to have some bugs at this time. There aren't many active developers out there.
13. After a heavy or long using like a full battery cycle, reboot the OS to clean up the cache/memory leak.
14. Use nova launcher or apex launcher to replace the sense launcher.
Well, I basically do ALL the stuffs above and got 5 ~ 7hrs screen time. Today, I do surf the web like mad(4hrs), 1hr 720p movie(software decode in MX Player as it's a rmvb movie), 30mins+ music with poweramp. Guess what? I got exactly 5hrs screen time and 1% battery left when I get back to home, very lucky though. I think my usage is a bit high today, normally I have 6hrs screen time average.
A lot of people on stock ROMs can get that sort of battery life too.
This is mine on stock:
http://forum.xda-developers.com/showthread.php?p=27010378#post27010378
Also wrote a quick guide, pretty similar to the above:
Terminator19 said:
Leave "best wifi performance" turned off.
Disable any apps that you don't need in settings>apps>click on app>disable at top right
Don't have weather etc. syncing every 30 minutes etc. set to something like 2 or 3 hours.
Manually control the screen brightness as auto makes the battery life worse, install qbright from the market and set a gesture so when you swipe up or down on the homescreen or dock icons this app is opened like the below:
{
"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"
}
I have it set to currently; night is 0%, indoor 30%, outdoor 50% and sunshine 70%
Keep wifi on as much as possible and set to never sleep
Keep GSM mode selected instead of WCDMA in mobile network settings as one; the voice reception is stronger and better battery life even when connected to wifi I found.
If you aren't going to be using any internet at all for quite while (meaning no need for weather, emails to sync etc.) then turn wifi and mobile network data off.
Only enable WCDMA when you want to browse or stream something (only when wifi is not possible)
Don't use any form of a task killer, if an app isn't responding just use the built in one.
Click to expand...
Click to collapse
WOW! Thanks guys! I'll definitely be trying these tips today.
Lets keep'em coming!
I'm running CM10 and all I did was lower my CPU clock to 1134 and I get great battery life. I also try to keep my wifi off as often as possible. I have auto-brightness and auto-sync on and usually get 6-7 hours and don't have to charge it all day. I prefer being able to use the better governers on top of the decreased frequency, but I haven't been able to get the Fusion AOSP kernel working on CM10 for quite some time.
Jewcifer said:
I'm running CM10 and all I did was lower my CPU clock to 1134 and I get great battery life. I also try to keep my wifi off as often as possible. I have auto-brightness and auto-sync on and usually get 6-7 hours and don't have to charge it all day. I prefer being able to use the better governers on top of the decreased frequency, but I haven't been able to get the Fusion AOSP kernel working on CM10 for quite some time.
Click to expand...
Click to collapse
I've always thought about under-clocking my CPU. I'll give that a try too. I'm sure i don't need the full 1.5ghz. I'll play around with them and see which will fit my needs .
My battery lasts twice as much just by turning the mobile internet off. I turn it on only when I need to surf the web/sync my apps and turn it back off right after.:victory:
Change governor to smartass2 and set your max CPU frequency at 1ghz. Also you can install app called llama for profiles switching and battery saving.
This is driving me crazy. I just noticed that after locking/unlocking the screen the minimum frequency jumps from 300MHz (value at boot) to 787Mhz. I did some little digging and I've found out that the script
Code:
/etc/init.qcom.post_boot.sh
does indeed set the scaling_min_freq at 787Mhz:
Code:
echo 787200 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
So I tried to modify the value 787200 to 300000 but the "issue" is still there. If I reset the min freq. to 300MHz from a specialized app then it switches again automagically.
I doubt this is done by the ondemand governor, since usually the scaling_min_freq parameter is out of governors scope, but I can't be sure about it, I see it has quite a large number of parameters compared to the ondemand governor I've seen in other phones.
My phone is rooted. Any chance anyone can give it a check with rooted or unrooted phones? To check it one must have SetCPU/Voltage Control/ROM Toolbox (pro) or any similar application. Also CPU Spy would help since it would show nearly 0% of usage for the frequencies below 787MHz, but it wouldn't help checking this on real time.
PS: I rebooted the phone and now unlocking the screen is fine. Monitoring via adb the value of scaling_min_freq I notice that it raises up to the max frequency when scrolling a list of files in any application. Wtf.. This is not as any governor should work. Unless installing (and then uninstalling) Xposed messed up something,
There is a build.prop entry which sets min freq of CPU to 787200, you can change it and it will work. However, when I changed it to 300MHz device got many lags and small freezes so I would suggest to leave it as is.
lozohcum said:
There is a build.prop entry which sets min freq of CPU to 787200, you can change it and it will work. However, when I changed it to 300MHz device got many lags and small freezes so I would suggest to leave it as is.
Click to expand...
Click to collapse
Ok, thanks. Do you mean "ro.min_freq"? It's the only property I could find with a 787 value. But I am not allowed to change it:
Code:
bash-4.1# getprop ro.min_freq
787000
bash-4.1# setprop ro.min_freq 300000
bash-4.1# getprop ro.min_freq
787000
Still I think that this is caused by the "mpdecision" process. The one which plugs and unplugs the CPU cores. It seems a bit bugged to me, because after running
Code:
mpdecision -h
which just exists with an error (option not available or the like) it stops messing around with the "scaling_min_freq" value.
But it isn't really an issue after all. Tonight while sleeping the battery drained less than 1% per hour. It means that even keeping at least a middle frequency the power consumption is quite low. I get bad draining switching to 3G/LTE, due to the crap signal of my mobile operator. It's very unclean, though.
Well, when I changed ro.min_freq manually in build.prop it actually worked. I checked it by CPU Spy + and other apps. Obviously root required.
Did you install busybox and run commands as superuser? as far as I know busybox may be needed
which rom are using? 4.3, 4.4.2 or 4.4.4?
Confirmed. Working too
lozohcum said:
Well, when I changed ro.min_freq manually in build.prop it actually worked. I checked it by CPU Spy + and other apps. Obviously root required.
Did you install busybox and run commands as superuser? as far as I know busybox may be needed
which rom are using? 4.3, 4.4.2 or 4.4.4?
Click to expand...
Click to collapse
Yap, it's working fine from the build.prop. I just used ES File Explorer to change the build.prop and it's working good. Here ss:
{
"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"
}
lozohcum said:
Well, when I changed ro.min_freq manually in build.prop it actually worked. I checked it by CPU Spy + and other apps. Obviously root required.
Click to expand...
Click to collapse
Ah, ok, so you actually edited the build.prop file. I dunno, i wanna try to modify as little system files as possible. I hoped to do it on the fly. Anyway, I was just looking for a confirmation that it wasn't just my phone. The thing is that before rooting I thought I could see the minimum frequency stable at 300MHz, with the current frequency varying. But being not rooted I don't know how much reliable could be that reading. At first I was surprised it was reading it at all.
Did you install busybox and run commands as superuser? as far as I know busybox may be needed
which rom are using? 4.3, 4.4.2 or 4.4.4?
Click to expand...
Click to collapse
I am running 4.4.4 with locked bootloader, SuperSu and Busybox (all latest releases) indeed. I also installed bash as you may have noticed. I did the rooting half "manually", messing up with rootkitXperia_20140719 via adb, flashing just the kernels, no OTA needed. I should write a guide after i decide to split and modify the scripts to make them fool proof.
Andrej732 said:
Yap, it's working fine from the build.prop. I just used ES File Explorer to change the build.prop and it's working good. Here ss:
View attachment 3087709
Click to expand...
Click to collapse
Oh, that's a neat tool! I just downloaded it now. It even gets the screen resolution right. they usually mess up (no, actually it reports the wrong screen size, though ).
I recently noticed this after upgrading to 4.4.4; the build.prop fix works.
:good:
Vino Kulafu said:
I recently noticed this after upgrading to 4.4.4; the build.prop fix works.
:good:
Click to expand...
Click to collapse
I actually switched it back to 787 MHz. As @ lozohcum mentioned reducing it to 300Mhz seems to make the screen less reactive. At least swiping pictures in Chrome became a bit of a pain.
Also it is my policy to leave the settings to the factory values as much as possible. If the company making the phones is serious (and Sony is), chances are that touching them we just make things worse. In this case I wanted to switch it back earlier but I simply forgot about it!
Miche1asso said:
I actually switched it back to 787 MHz. As @ lozohcum mentioned reducing it to 300Mhz seems to make the screen less reactive. At least swiping pictures in Chrome became a bit of a pain.
Also it is my policy to leave the settings to the factory values as much as possible. If the company making the phones is serious (and Sony is), chances are that touching them we just make things worse. In this case I wanted to switch it back earlier but I simply forgot about it!
Click to expand...
Click to collapse
Makes sense. Although in my experience, the screen is still responsive. In any case, I just reverted to 787 Mhz as my lowest clock speed.
I was dabbling around using the Performance Control app, which had an option to edit some governor settings. Found out that the optimal_freq in the governor was set to 787200. Since I have no comprehensive knowledge about governors in general, I am lead to believe that 787 Mhz might be Sony's intended lowest clock speed for its KitKat kernel.
Vino Kulafu said:
Makes sense. Although in my experience, the screen is still responsive. In any case, I just reverted to 787 Mhz as my lowest clock speed.
I was dabbling around using the Performance Control app, which had an option to edit some governor settings. Found out that the optimal_freq in the governor was set to 787200. Since I have no comprehensive knowledge about governors in general, I am lead to believe that 787 Mhz might be Sony's intended lowest clock speed for its KitKat kernel.
Click to expand...
Click to collapse
There are two things involved. The CPU Governor and mpdecision the Qualcomm cores hotplug. In a single core CPU the Governor is the one doing all the job changing the CPU clock frequencies depending on the CPU load. In a multicore CPU the core hotplug is the one turning on and on and off the cores depending on the CPU load. From what I have seen monitoring, mpdecision also changes in real time the minimum governor frequency (up to the max frequency of 1190 MHz) not allowing the CPU frequency to go below the minimum frequency defined in "ro.min_freq", basically making the CPU governor useless.
In other words mpdecision either bypasses the CPU Governor (set to ondemand as default in our phones) or it squeezes to the top the range of frequencies available to the latter.
Still all this stuff is made to save energy. I believe that having 1 core active at 787 MHz is faster and consumes less than having 2 cores at 300 Mhz (a case which I have seen monitoring). Also a bad/weak phone signal is much more of a nightmare in terms of energy consumption. My LTE signal is crap for example, switching to HSPA+ (basically turning LTE off) I save 1-2% per hour.