Hi all,
I've got a problem with System Tuner. On every ICS ROM I try the CPU clock and voltage settings won't stick. After I reboot the phone they go back to their defaults. Hence, I've got 3 questions:
1. Does everyone have these problems? Did I not check a setting or something?
2. What alternatives to System Tuner don't turn the second CPU core permanetly on?
And 3. Is there an init.d script which lets you set the clock speeds/voltage settings? Because I would rather not use an app at all to do that.
Set your CPU clock and voltages, then press Boot settings on the cpu tab( small button ), press Re-apply CPU Settings -> On boot completed.
ccs16rocks said:
Set your CPU clock and voltages, then press Boot settings on the cpu tab( small button ), press Re-apply CPU Settings -> On boot completed.
Click to expand...
Click to collapse
Yes I did that, but the minimum frequency doesn't stick.
Nobody?
I'm using No-frills atm, but does that turn CPU1 permanently on?
-editedpost-
V1k70r said:
Yes I did that, but the minimum frequency doesn't stick.
Click to expand...
Click to collapse
My setup is similar to yours except I'm on ARHD 6.5.3.
I can confirm it is changing back to 192Mhz min. Could be kernel related as I'm on bricked 3.0 v5 too. Maybe we should ask showp-1984 or it cold be related to System Tuner.
Did you have tried another software like setCPU?
yasobaso said:
My setup is similar to yours except I'm on ARHD 6.5.3.
I can confirm it is changing back to 192Mhz min. Could be kernel related as I'm on bricked 3.0 v5 too. Maybe we should ask showp-1984 or it cold be related to System Tuner.
Did you have tried another software like setCPU?
Click to expand...
Click to collapse
Hi there I'm on same Rom but with serbas ken and I use system tuner pro and mine sticks even after reboot, on a off chance do you have oc demon disabled in boot settings
Sent from my ARHD ICS powered senny
boroboy69r said:
Hi there I'm on same Rom but with serbas ken and I use system tuner pro and mine sticks even after reboot, on a off chance do you have oc demon disabled in boot settings
Sent from my ARHD ICS powered senny
Click to expand...
Click to collapse
Could you be more detailed Do you mean " Re-Apply CPU settings" if so yes I had it enabled. I will reflash stock o any other kernel and check if it's going to solve this.
I also have this problem with system tuner pro, now i'm using setcpu and the settings stick.
using vipers 1.1.0, tried anthrax/bricked/faux123 all didn't stick.
You know you.could ask the dev of super tuner. He's always very responsive anytime I've had issues. Also having different versions backed up in Ti helps as well cause a new update fixes one thing from a slew of phones but might just break yours. Having a backup versions means you can go back restore and test.
Casperi.
Sent from my SGH-T989 using xda premium
In relation to your second question, what kernel are you using? Faux's kernel has the second core on by default. System tuner doesn't have the ability to turn it off. If you want it offline until it's needed, try seb's or bricked kernels instead.
System Tuner 3.0
Just to let you know System Tuner 3.0 was released some time ago and provides improved CPU handling, new GPU, Gamma, MP, thermal controls on many custom kernels and a lot of other new or improved features (entropy, fstrim to name a few).
This is now a spawn of Android Tuner, and benefits from a larger user-base, improved stability and performance.
It now has the ability to turn on/off CPU cores, with a dedicated screen-off option. Only if custom kernel allows it though.
If you have specific profiles in SetCPU and a set CPU frequency NSTools, is there anyway to keep the profiles working without having to disable set on boot for NSTools? NSTools seems to overtake CPU settings on boot.
Sent from my Nexus S 4G using Tapatalk 2
why do you even want use SetCPU ? it seems to be useless with NSTools because what ever it can do is to be done by NSTools , if you say you wanna do something like change frequency while screen off , then the governor will do it automatically if you choose appropriate CPU governor
Jamin13 said:
If you have specific profiles in SetCPU and a set CPU frequency NSTools, is there anyway to keep the profiles working without having to disable set on boot for NSTools? NSTools seems to overtake CPU settings on boot.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
CPU Profiles aren't worth it for day to day use. Constant ondemand is perfectly fine and won't steal any extra battery from you.
However, setting NSTools to set on boot should still allow SetCPU to work fine, as long as CPU settings are set the same on boot time. If not, use init.d scripts but remove CPU parameters from them (find them in /system/etc/init.d/xx-xxxxx), keeping the other settings as you prefer. Might want to remove NSTools after this though as it may undo your changes after opening again.
i guess setcpu makes it easier to change cpu frequencies quickly through the widget, ns tools doeesnt have a widget so its "harder"
qtwrk said:
why do you even want use SetCPU ? it seems to be useless with NSTools because what ever it can do is to be done by NSTools , if you say you wanna do something like change frequency while screen off , then the governor will do it automatically if you choose appropriate CPU governor
Click to expand...
Click to collapse
SetCPU won't control the Backlight Notifications and Dimmer.
Harbb said:
CPU Profiles aren't worth it for day to day use. Constant ondemand is perfectly fine and won't steal any extra battery from you.
However, setting NSTools to set on boot should still allow SetCPU to work fine, as long as CPU settings are set the same on boot time. If not, use init.d scripts but remove CPU parameters from them (find them in /system/etc/init.d/xx-xxxxx), keeping the other settings as you prefer. Might want to remove NSTools after this though as it may undo your changes after opening again.
Click to expand...
Click to collapse
I'm just a bit OCD about battery life some days. I'd rather use the app than making my own scripts. I kinda derped with the profiles earlier today. All is good now.
I wish the two would play better together too - and I don't see how "just don't use them both" or saying SetCPU is no longer needed is acceptable answers. Especially since many of us actually paid for SetCPU...
Now that it looks like we'll only get two governors in MathKids kernel (what a crock)... saying you are picking the wrong one is a bad answer too. Ondemand certainly isn't the best for battery life, and for those of us who have tested and measured battery life we know just picking one isn't a solution either.
So what is the actual answer? Because setting the governor parameters at boot isn't the problem. It's switching between profiles - and the governors that give you the best battery life and giving acceptable performance need to be tweaked from their defaults.
With OnDemand I'm looking at using over 16% battery per hour under 4.1, even with considerable screen off time. Not being able to set it to Wheatley on screen off is killing the battery.
I will say the problem seems to lay directly with SetCPU and I'm going to contact the dev and see what I can find out. I don't see why it should be changing the parameters back to default on profile change.
But people who use neither or just one probably just not comment. Not to flame, or fight, but it's not helpful to add nothing.
Hello. I have been a "lurker" on these boards for roughly 2 years. I have rooted, flashed and installed custom ROMs, bootloaders, recoveries and radios on the following devices:
Samsung Vibrant (original samsung galaxy S)
HTC Amaze (a.k.a Ruby.... wire trick and all)
ASUS Transformer 1 WiFi Only model ( a.k.a TF101)
Anyway, I am posting for the first time. Because of this, I cannot post directly to the development thread involved with my issue. Never the less, here it is:
I am running RaymanFX's JellyBean Cyanogen 10 V6 (STABLE) with Rayman's custom kernel on my TF101. I was running a Revolver ICS ROM prior to installing this JB ROM.... or Revolution HD, I can't remember... anyway
I am having an issue with the TF101 either 1) involuntary reboot or 2) freeze/lockup/crashing after wakeup from sleep mode and complete loss of WiFi radio.
Yes, I have extensively searched the development threads and I found posts related to this one, but none of them solve the issue and I also noticed a few people have this same problem but have no known solution.
I have wiped and done clean install of this ROM several times always with the same result. I also flashed LiquidSmooth (Rayman worked on this ROM and his kernel is cross compatible) to see if it was ROM-related and discovered it is not.... this is a kernel issue. My wipe procedure is:
Factory Reset (cache/data wipe)
Run Superwipe script for TF101 from Android Revolution HD thread (format cache, data, etc...)
Wipe Dalvik Cache
Flash ROM
Reboot
Flash GAPPS (latest version linked on Cyanogen thread from goo.im)
Reboot
Everything runs buttery smooth and flawlessly, HOWEVER.... "Wake on WiFi fix" solution on RaymanFX's post does not work for me.
The "fix" is to designate WiFi Always On during Sleep. Changing this setting doesn't stick... WiFi still sleeps even with this setting corrected. With one caveat... Changing the setting to "Never" and then modifying WiFi Idle Timeout to "3 hours" and then changing the Keep WiFi on During Sleep to "Always" will delay the WiFi from idling out temporarily unless the tablet is in Sleep longer than 3 hours.... at which it idles anyway and causes a crash or reboot.
Secondly, I have discovered that the CPU Frequency setting under Performance could be part of the reason it crashes. I have "Set on Boot" enabled. Setting a CPU Frequency, regardless of governor, above 1408 Mhz WILL cause tablet to lockup/crash upon wakeup from Sleep as the processor jumps to maximum set frequency. If maximum frequency is set to 1408, it will stutter and lag out the system forcing it to become unresponsive to touch commands but "stable" and useable.... albeit very laggy. If the Max Frequency is set to 1200, it will NOT reduce the maximum frequency set for the CPU unless tablet is put into Sleep mode and then woken again.... it will constantly cycle between the "old" maximum frequency setting and the "new" maximum frequency setting (observed by monitoring the frequency in the Performance setting screen after changing from a higher max frequency to a lower max frequency and staying on the menu screen and allowing the CPU to "settle" without any user input).
I really like this ROM and I hate to give up on it, so I'm hoping someone out there will have an idea about what I can do to make this work... or at least recommend a different kernel that will work with this ROM and also has a way to change CPU frequencies and governers.
Any ideas?
i have the 1689mhz bug!!! at random time the MIN freq of the cpu is stuck at 1689mhz andthe max still at 2ghz. ( you can activate on developer options the "show cpu info" toggle)
i cannot change the min value from kernel adiutor, i click on 652mhz but nothing changes, only a REBOOT actually fix the min freq used.
i thought it was a problem of my custom rom resurrection 5.8.3 or the fact i am using kernel adiutor, in fact this app does randomly give CPU LOAD BUG on several devices i mod! sometimes kernel adiutor load my cpu cores at 100% also on light load, but just forceclosing the app the cores return to lower freq.
but the 1689mhz bug is a KERNEL BUG, i read about this bug also on people with stock rom, and the p2a42 phone.... and i have p2c72 hardware phone!!! so this kernel BUG is found in EVERY VERSION of this phone.
please developers, we need a modded kernel that fixes this bug, and why not.......... new i/o schedulers and governors.... and maybe a little undervolt for every cpu freq
realista87 said:
i have the 1689mhz bug!!! at random time the MIN freq of the cpu is stuck at 1689mhz andthe max still at 2ghz. ( you can activate on developer options the "show cpu info" toggle)
i cannot change the min value from kernel adiutor, i click on 652mhz but nothing changes, only a REBOOT actually fix the min freq used.
i thought it was a problem of my custom rom resurrection 5.8.3 or the fact i am using kernel adiutor, in fact this app does randomly give CPU LOAD BUG on several devices i mod! sometimes kernel adiutor load my cpu cores at 100% also on light load, but just forceclosing the app the cores return to lower freq.
but the 1689mhz bug is a KERNEL BUG, i read about this bug also on people with stock rom, and the p2a42 phone.... and i have p2c72 hardware phone!!! so this kernel BUG is found in EVERY VERSION of this phone.
please developers, we need a modded kernel that fixes this bug, and why not.......... new i/o schedulers and governors.... and maybe a little undervolt for every cpu freq
Click to expand...
Click to collapse
Haha! Have very less hopes,bcoz some feel that custom kernels are not at all needed! They think that a device wid 2ghz processor doesn't need custom kernel
And btw the post topic is 100% right,bt the place where it's posted is wrong! This should be under discussion section
realista87 said:
i have the 1689mhz bug!!! at random time the MIN freq of the cpu is stuck at 1689mhz andthe max still at 2ghz. ( you can activate on developer options the "show cpu info" toggle)
i cannot change the min value from kernel adiutor, i click on 652mhz but nothing changes, only a REBOOT actually fix the min freq used.
Click to expand...
Click to collapse
Yes, thats true. The bug is i think VDD related. Sometimes the VDD switches automatically on, the min CPU freq goes up to 1689 MHz, and can not be lowered until you don't switch off the VDD. You can switch off in Kernel Adiutor/Thermal section, or use the following command :
echo '0' > /sys/module/msm_thermal/vdd_restriction/enabled
I use the KSLABS Schedule! app to run the command every 5 minutes.
I hope this will help you, until we get one bugfree kernel.
u are right
now the bug is MORE AGGRESSIVE THAN EVER............ i rebooted, i attachedthe phone to a charger, arrived 100%, then rest for 1h30min on idle(deep sleep) but when i started using the phone... i checked the frequencies and BOOM....... another time the bug of 1689mhz!!! the battery was 100%......
maybe there is an app that causes this... but which one?
realista87 said:
maybe there is an app that causes this... but which one?
Click to expand...
Click to collapse
Which ROM do you use?
I have stock 244, but the method worked for me in 233 too. In the past, I used the Magisk Crossbreeder Lite module to eliminate this problem, but the latest (1.6+) versions made the phone very slow, especially booting.
Vis77 said:
Yes, thats true. The bug is i think VDD related. Sometimes the VDD switches automatically on, the min CPU freq goes up to 1689 MHz, and can not be lowered until you don't switch off the VDD. You can switch off in Kernel Adiutor/Thermal section, or use the following command :
echo '0' > /sys/module/msm_thermal/vdd_restriction/enabled
I use the KSLABS Schedule! app to run the command every 5 minutes.
I hope this will help you, until we get one bugfree kernel.
Click to expand...
Click to collapse
can you help me with the console command... but with macrodroid? i don't use that app
edit_ i setted your app, ibut i prefer every 1h to toggle VDD off
realista87 said:
u are right
now the bug is MORE AGGRESSIVE THAN EVER............ i rebooted, i attachedthe phone to a charger, arrived 100%, then rest for 1h30min on idle(deep sleep) but when i started using the phone... i checked the frequencies and BOOM....... another time the bug of 1689mhz!!! the battery was 100%......
maybe there is an app that causes this... but which one?
Click to expand...
Click to collapse
Maybe the Kernel adiutor itself cause the high load, as background task make 28-30% cpu load, see the attachment.
But, the 1689 MHz bug still exist. :-\
Vis77 said:
Maybe the Kernel adiutor itself cause the high load, as background task make 28-30% cpu load, see the attachment.
But, the 1689 MHz bug still exist. :-\
Click to expand...
Click to collapse
what app do you use to see the % of cpu for each thread?
i don't think that the cause is kernel adiutor... i repeat, a lot of people with 100% stock rom have this bug.....
hey vis could you help me with the string of the scheduler app? i don't understand how to set every 1 hour my previous screenshot i think is wrong because it does not work every 1 h
sorry but the "cron expression" is too much difficult to me to understand.....
EDIT i found how to do every 1h!! 0 0 0/1 1/1 * ? *
thanks to this site!!! http://www.cronmaker.com/
realista87 said:
what app do you use to see the % of cpu for each thread?
i don't think that the cause is kernel adiutor... i repeat, a lot of people with 100% stock rom have this bug.....
[/B]
Click to expand...
Click to collapse
The app name is 3C Toolbox Pro.
Yes the bug is still here, Kernel Adiutor is only different problem.
After reading all your discussion.. I understood that one of you knew solution to stop the bug ,and the other guy learnt how to do it ..
But I don't get a single thing ,what and how you solved that bug
Note : I don't even know that 1698 bug is present , all I know is cpu idle is consuming more power ..
Is this the same thing you guys were discussing?
If yes ..how can a I solve it ? Any walkthrough?for dumb minds like me ...?
nandakis4 said:
After reading all your discussion.. I understood that one of you knew solution to stop the bug ,and the other guy learnt how to do it ..
But I don't get a single thing ,what and how you solved that bug
Note : I don't even know that 1698 bug is present , all I know is cpu idle is consuming more power ..
Is this the same thing you guys were discussing?
If yes ..how can a I solve it ? Any walkthrough?for dumb minds like me ...
Click to expand...
Click to collapse
I've made the following observations:
On a fresh install(stock or custom rom(i have not tried Firelord versions)), rooted phone(with Magisk or SuperSU), if you install the Kernel Adiutor, and go to Thermal section the VDD restriction by default is OFF. You can change freely the CPU minimum frequency.
After some hours/days(total random) something switch ON the VDD restriction, the CPU minimun frequency going up to 1698 MHz, and unable to set back the default 652 MHz. If you switch off the screen the cores going to deep sleep, but if you switch on the screen the min. freq. is still 1698 MHZ.
If you manually switch OFF the VDD restriction, the CPU working normal, until switched ON automatically again.
If your phone is not rooted, the only thing what you can notice that the battery is dropping faster than usual, or the phone a bit warmer.
The problem still occurs even if you do not have a program that you can turn on/off the VDD.
The above solution does not repair the problem, it only remedies the symptoms...
I sometimes notice that even though I don't use it, "Google Play Services" consume an unusual amount of battery and will continue to do so unless I reboot the phone. I have never investigated the cause. Might this be related to the 1698MHz bug ?
medwatt said:
I sometimes notice that even though I don't use it, "Google Play Services" consume an unusual amount of battery and will continue to do so unless I reboot the phone. I have never investigated the cause. Might this be related to the 1698MHz bug ?
Click to expand...
Click to collapse
I do not think so, but check the status of VDD when you have rooted phone. Sometimes I have too huge battery usage caused by the Google Play Services, but i would suspect first of the Location services. If I use some sport tracker, or navigation app then growing for me the Google Play Services consumption.
Vis77 said:
I do not think so, but check the status of VDD when you have rooted phone. Sometimes I have too huge battery usage caused by the Google Play Services, but i would suspect first of the Location services. If I use some sport tracker, or navigation app then growing for me the Google Play Services consumption.
Click to expand...
Click to collapse
My phone is rooted. I will start monitoring VDD. FYI, I don't use any google app (Gmail, Play Store, Maps, etc ...). Location services is also turned off. Sometimes, out of nowhere, I'd see Google Play Services at the top of the battery consumption details. Yesterday, it had a very high CPU consumption time of around 1h (prevented the phone from going to sleep; had 3000+ wakelocks). I had to reboot the phone to get it to stop eating my battery. Usually, Google Play Services use the CPU for a total of 10min on a full charge.
medwatt said:
My phone is rooted. I will start monitoring VDD. FYI, I don't use any google app (Gmail, Play Store, Maps, etc ...). Location services is also turned off. Sometimes, out of nowhere, I'd see Google Play Services at the top of the battery consumption details. Yesterday, it had a very high CPU consumption time of around 1h (prevented the phone from going to sleep; had 3000+ wakelocks). I had to reboot the phone to get it to stop eating my battery. Usually, Google Play Services use the CPU for a total of 10min on a full charge.
Click to expand...
Click to collapse
If you don't use it, you can remove what is mentioned on the MicroG Prerequisites page[0].
Some apps nag about it but the only noticable problem I have is messenger lite notifications don't go automaticaly away after replying. Even my banking app keeps working.
[0]https://github.com/microg/android_packages_apps_GmsCore/wiki/Prerequisites