I am currently using this rom http://forum.xda-developers.com/showthread.php?t=2306650 , but i doubt its the rom fault.
Using the MIUI settings, Antutu CPU master, or ROM ToolBox, applying a lower CPU max freq will not stick.
Ex: The max is 1890mhz, but i want it at 1566mhz for the max. After turning the phone off and on, the max CPU freq. goes back to the original 1890mhz. With a reboot, it sticks, half the time.
What do i do? Please reply ASAP, my S4 gets hot while playing games so i like to underclock it.
With many years of experience, the best thing I can tell you is to not place a MHz cap that is too high. Your phone can potentially be a potato if you're not careful.
Sent from my GT-I9505G using Tapatalk
HenryTheUnicorn said:
I am currently using this rom http://forum.xda-developers.com/showthread.php?t=2306650 , but i doubt its the rom fault.
Using the MIUI settings, Antutu CPU master, or ROM ToolBox, applying a lower CPU max freq will not stick.
Ex: The max is 1890mhz, but i want it at 1566mhz for the max. After turning the phone off and on, the max CPU freq. goes back to the original 1890mhz. With a reboot, it sticks, half the time.
What do i do? Please reply ASAP, my S4 gets hot while playing games so i like to underclock it.
Click to expand...
Click to collapse
Download CPU controller app from the market. It will reset your CPU upon screen on.
Sent from my SGH-M919 using Tapatalk
elesbb said:
Download CPU controller app from the market. It will reset your CPU upon screen on.
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Everything I've ussed applies settings on boot, but it wont frickin work sometimes.
HenryTheUnicorn said:
Everything I've ussed applies settings on boot, but it wont frickin work sometimes.
Click to expand...
Click to collapse
SetCPU has different profiles to configure. And which ROM are you on? There might be an init.d script adjusting the frequencies. SetCPU will apply them AFTER any init.d scripts are ran so that should fix it. I loved SetCPU till ktoonsez made his own app.
elesbb said:
SetCPU has different profiles to configure. And which ROM are you on? There might be an init.d script adjusting the frequencies. SetCPU will apply them AFTER any init.d scripts are ran so that should fix it. I loved SetCPU till ktoonsez made his own app.
Click to expand...
Click to collapse
the rom i am on is in the first post.
How do i check the script if it is?
Meh, till i figure that out, time to use SetCPU. I MUCH prefer Antutu Cpu Master Pro, a profile for overheating? Hell yes, i set mine to 1.2ghz at 105 degrees F. and 1.5/1.6ghz when its normal. Helped ALOT
HenryTheUnicorn said:
the rom i am on is in the first post.
How do i check the script if it is?
Meh, till i figure that out, time to use SetCPU. I MUCH prefer Antutu Cpu Master Pro, a profile for overheating? Hell yes, i set mine to 1.2ghz at 105 degrees F. and 1.5/1.6ghz when its normal. Helped ALOT
Click to expand...
Click to collapse
I believe setCPU has that profile as well
Sent from my SGH-M919 using Tapatalk
elesbb said:
I believe setCPU has that profile as well
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Oh darn. It worked for a bit. Now instead of going back to normal max frequency after a reboot or boot up, it does it when I'm using the phone.
Does PAC ROM have this issue? If not, I'll use pac rom instead. Or it may be a kernel problem? Idk much about android stuff
HenryTheUnicorn said:
Oh darn. It worked for a bit. Now instead of going back to normal max frequency after a reboot or boot up, it does it when I'm using the phone.
Does PAC ROM have this issue? If not, I'll use pac rom instead. Or it may be a kernel problem? Idk much about android stuff
Click to expand...
Click to collapse
Sounds like the kernel is overriding certain things in different scenarios. I'd try a different kernel.
Related
can anyone suggest a good overclock tool with voltage parameters? setcpu doesn't seem to have one for the play... and antutu seems bugged when setting voltages... (keeps changing the value for 1300mhz to 1300mv)
seagheart89 said:
can anyone suggest a good overclock tool with voltage parameters? setcpu doesn't seem to have one for the play... and antutu seems bugged when setting voltages... (keeps changing the value for 1300mhz to 1300mv)
Click to expand...
Click to collapse
I'm using Antutu CPU Master Pro and I don't find it buggy. This is better to use imo than setcpu which consumes more battery. Longpress the frequency you are in and using then set to -25mv. Tick on "set on boot" then click "apply". Reboot your phone and check again your settings if it was changed or not. Also, try to reinstall your overclocking app and clear some cache on your phone.
anbu187 said:
I'm using Antutu CPU Master Pro and I don't find it buggy. This is better to use imo than setcpu which consumes more battery. Longpress the frequency you are in and using then set to -25mv. Tick on "set on boot" then click "apply". Reboot your phone and check again your settings if it was changed or not. Also, try to reinstall your overclocking app and clear some cache on your phone.
Click to expand...
Click to collapse
i do agree that antutu is very good... but the problems started when i updated to 2.5... i was using 2.3 before
is -25 the lowest it can go??? isnt -50 safe?
EDIT: also in 2.5 it keeps saying that it has been granted superuser permissions... in 2.3 it only does that whenever i change any setting...
I use OC/UV Beater2v1.7, and it's awesome! Unlike setcpu, it won't run in the background, but rather sets up scripts in init.d (don't set as permanent unless you're 100% sure of your OC/UV settings, otherwise bootloops can occur)
seagheart89 said:
i do agree that antutu is very good... but the problems started when i updated to 2.5... i was using 2.3 before
is -25 the lowest it can go??? isnt -50 safe?
EDIT: also in 2.5 it keeps saying that it has been granted superuser permissions... in 2.3 it only does that whenever i change any setting...
Click to expand...
Click to collapse
I use 2.3.1 version. I tried -50 on setcpu and it crashed my phone. Haven't tried -50 yet on Antutu. I rolled back my speed from 1.5ghz to around 900+mhz as the speed is still fast (btw im using T.E.A.M. rom).
jacklebott said:
I use OC/UV Beater2v1.7, and it's awesome! Unlike setcpu, it won't run in the background, but rather sets up scripts in init.d (don't set as permanent unless you're 100% sure of your OC/UV settings, otherwise bootloops can occur)
Click to expand...
Click to collapse
so i only have to run this once? seems good... will try it later...
anbu187 said:
I use 2.3.1 version. I tried -50 on setcpu and it crashed my phone. Haven't tried -50 yet on Antutu. I rolled back my speed from 1.5ghz to around 900+mhz as the speed is still fast (btw im using T.E.A.M. rom).
Click to expand...
Click to collapse
i set my cpu to -50 and it runs fine... did some stress tests and it is stable... running at 1.4ghz (just right for psx games)
jacklebott said:
I use OC/UV Beater2v1.7, and it's awesome! Unlike setcpu, it won't run in the background, but rather sets up scripts in init.d (don't set as permanent unless you're 100% sure of your OC/UV settings, otherwise bootloops can occur)
Click to expand...
Click to collapse
What are bootloops btw? ty
anbu187 said:
What are bootloops btw? ty
Click to expand...
Click to collapse
Bootloop means your phone endlessly reboots without ever getting past the bootlogo
jacklebott said:
Bootloop means your phone endlessly reboots without ever getting past the bootlogo
Click to expand...
Click to collapse
ah ok thanks, that never happened to me so far. Anyway, any idea why my battery is drained that much even when im not using it. No wifi, no other background apps enabled, or is it with the kernel? ty
So I know a lot of us don't use stock here, but my gf likes her phone stock so I had recently debloated her phone. I started to notice that her phone didn't spend anytime in the 192 Mhz clock speed. I tried using setCPU to change the min/max but to no avail. So my question is, is this stock kernel behavior or did I screw up somewhere?
milkdudxp said:
So I know a lot of us don't use stock here, but my gf likes her phone stock so I had recently debloated her phone. I started to notice that her phone didn't spend anytime in the 192 Mhz clock speed. I tried using setCPU to change the min/max but to no avail. So my question is, is this stock kernel behavior or did I screw up somewhere?
Click to expand...
Click to collapse
Thats just how it is.
xcrazydx said:
Thats just how it is.
Click to expand...
Click to collapse
Thanks, glad I didn't mess it up. I'll try out another kernel on her phone later.
milkdudxp said:
Thanks, glad I didn't mess it up. I'll try out another kernel on her phone later.
Click to expand...
Click to collapse
You don't need that, man. 384 is fine, 192 usually gets sleep of death
xcrazydx said:
You don't need that, man. 384 is fine, 192 usually gets sleep of death
Click to expand...
Click to collapse
+1
384 is the lowest
Sent from my SGH-T989 using XDA
Hi Guys! I'm on CM10 Nightly's kernel, and as you know it is set to max frequencies on all 4 cores, which causes crazy battery drain. I change CPU frequency manually but as soon as the phone gets rebooted it gets back to max. I tried to change performance settings and using some apps - didn't work. Any ideas how can I make CPU frequency stick to the one I pick? Maybe I should try another kernel?Thanx
Sent from my HTC One X using Tapatalk 2
I would recommend that you download SetCPU application from Play Store and play with it a little bit. But be careful, you could mess things using it.
I would start using a non nightly kernel. Nightly kernels could have bugs that could damage your device. My guess is that CPU frequency reset was put into the kernel for safety reasons.
Sent from my HTC One X using xda app-developers app
I am on nightly (seadersn edition) and checking apply settings on boot works fine with min and max frequencies. Also nobody has complained in the official cm10 thread. Try re flashing your kernel. And fastboot erase cache afterwards.
"No Frils" or "System tuner" apps will keep the frequencies for you
ekabon said:
Hi Guys! I'm on CM10 Nightly's kernel, and as you know it is set to max frequencies on all 4 cores, which causes crazy battery drain. I change CPU frequency manually but as soon as the phone gets rebooted it gets back to max. I tried to change performance settings and using some apps - didn't work. Any ideas how can I make CPU frequency stick to the one I pick? Maybe I should try another kernel?Thanx
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
OP, I'm having the same problem as you - CM10, latest nightly. I'm really worried that it running at max CPU frequency will damage my phone. Have you managed to find a solution? I'm a complete noob at all this, and can't quite figure out how to install a new kernal. Thanks dude
I touched some no frills cpu control settings and now my benchmark results are about 19000-22000 and it used to be like 24000 i tried changing the rom and all that stuff if someone can give me the stock governator and all frequencys and that stuff it would be helpful.. Thanks i need help i dont know what to do
Now i cant do any better than 23000
rbcios said:
Now i cant do any better than 23000
Click to expand...
Click to collapse
Firstly, I assume by the size score that you are using Antutututu. If so then you always get variance in the scores, and yes it can be 4k difference.
Next, I'm gonna bet that you are seeing thermal throttling, where the device is turning off 2 of the cores due to heat.
I've only noticed this behaviour recently myself. It's a real pain in the arse. I've downloaded trinity kernel app to get around the problem. In his app you can turn off thermal throttling and force the two other Cores to stay on.
This isn't a permanent fix though as the settings don't want to stick for some reason that is beyond me.
Next, is there no reset to default in no frills cpu app ?
Or you can uninstall no frills and make sure you delete any folders off your sd card, then either reflash your rom or you could even flash AICP kernel.
This should get you back to default.
Finally if you still think it's your settings, you could tell us all the settings you have changed and between the guys on the forum we could tell you what to change back to.
All the best rich
**just had a quick look at no frills on play Store. Looks like there's not loads to alter.
I like interactive governer and row scheduler (as we can't get row I use deadline.)
Min frequency wants to be at 384 and max at 1728.
That's the basics.
Sent from my LG-V500 using XDA Premium HD app
Every time I try to underclock the CPU as soon as I leave the app the sliders go back to where they were originally. Even after applying on boot. Am I doing something wrong?
BakedOnSomeSour said:
Every time I try to underclock the CPU as soon as I leave the app the sliders go back to where they were originally. Even after applying on boot. Am I doing something wrong?
Click to expand...
Click to collapse
Since you've given virtually no information, I will assume that your phone is unrooted and/or running with the stock kernel. You will need to address both to be able to underclock.
Because underclocking is silly.
Wakamatsu said:
Since you've given virtually no information, I will assume that your phone is unrooted and/or running with the stock kernel. You will need to address both to be able to underclock.
Click to expand...
Click to collapse
I am rooted and running elementalX kernel
BakedOnSomeSour said:
I am rooted and running elementalX kernel
Click to expand...
Click to collapse
I'm not running EX. Does it use init.d or config script? Those may overwrite whatever method you're using to underclock at boot.
Underclocking-saving battery
Is a BIG LYE
CPU will not use full power (max freq) when not need.
Dont forget what is Mhz (how MUCH things CPU can do in what TIME) the only deffrent bettwen underclocked and overclocked is TIME.312Mhz will do something in 5 mins,but 2 Ghz will do it in 1 second. It just do faster,but battery use is same,count yourself
1. You warmed up a dusty thread.
2. Battery-work isn't simply product of time and frequency: longer low tasks eats fewer capacity than shorter peak ones.