Related
So just curious...anyone played around with the settings for "Advanced" on their DX? Wondering if anyone has found any values that work better and give better performance/battery life then leaving it as-is.
Not new to using SetCPU btw...been using it since I rooted/installed a custom ROM sometime last year.
JagoX said:
So just curious...anyone played around with the settings for "Advanced" on their DX? Wondering if anyone has found any values that work better and give better performance/battery life then leaving it as-is.
Not new to using SetCPU btw...been using it since I rooted/installed a custom ROM sometime last year.
Click to expand...
Click to collapse
I usually lower the sampling rate so that it checks itself more often... I also lower the up threshold to somewhere between 20%-35% so when the cpu load hits that percentage setcpu will tell the cpu to go "balls to the wall"...
"4. Advanced Tab
The Advanced menu allows you to tweak the finer aspects of certain CPU governors. It is only activated when you choose the ondemand or conservative governors.
Sampling Rate – An interval (in microseconds) at which the governor will poll for updates. When this happens, the governor will decide whether to scale the CPU up or down.
Up Threshold – Defines a percentage from 1% to 100%. When the CPU load reaches this point, the governor will scale the CPU up.
Down Threshold (conservative only) – Defines a percentage from 1% to 100%. When the CPU load reaches this point, the governor will scale the CPU down.
Ignore Nice Load – If this value is “1,” the system will ignore “Nice” processes when deciding to scale up or down.
Powersave Bias (ondemand only) – Setting this value higher will “bias” the governor toward lower frequencies.
Choose the “Set on Boot” checkbox to apply advanced settings when the phone boots. This option is completely independent of the similar option in the Main tab."
Sources:
http://forum.xda-developers.com/showthread.php?t=505419
http://www.setcpu.com/
If you don't mind me asking what value do you change the sampling rate to? What kind of performance improvement to you see?
What rom you running btw?
Hello all,
since I installed the nightly build on the [ICS][CM9]Defy/Defy+ kangs by FuZZ_ topic, I'm unable to change the frequency on my defy(the max is set to 0, the minimum is set to 300) so it always run in 300 mhz, I've tried using the vsel, but the textfields to change the values doesn't appear, tried changing it on the files over gpu0 folder, but when I try to save it it says "unable to save file" and I've set its permissions to write to all users(other,group,owner) and tried the performance menu over the configuration. Any help?
Push the botton above to restart the device. In the menu that is shown on the screen tap on restart. Then select bootmenu option. accept. wait until restarts. go to cpu settings nd there you can change the vsel and frequency.
:laugh:
how i change CPU frequency
glupsnif said:
Push the botton above to restart the device. In the menu that is shown on the screen tap on restart. Then select bootmenu option. accept. wait until restarts. go to cpu settings nd there you can change the vsel and frequency.
:laugh:
Click to expand...
Click to collapse
hi
how do i change the CPU frequency in the bootmenu? i see the CPU setting but don't know how to change them
thx
IGK80 said:
hi
how do i change the CPU frequency in the bootmenu? i see the CPU setting but don't know how to change them
thx
Click to expand...
Click to collapse
get into CPU Settings, set Clk1 to 300, Clk2 to 600, Clk3 to 1000, Vsel1, 2, 3 to respectivly 30, 46, 58, Status shall be Enable, Load all modules: Enable, Scaling my proposal choose Smartass, slide down and click Save, then Go Back and Reboot
and give a feedback
Hello everybody!
I'm having a strange problem: if i have the phone locked, with screen turned off for a while, in my pocket, when i turn it on again it is very slow. It takes about 30 seconds to come back to usual performance.
For example, if i unlock the phone and i go to SMS or WhatsApp, the keyboard (Swiftkey) it's so slow that i have to wait for every word to complete, before i can type another one.
After 30 seconds from the unlock the phone works ok.
The problem started when i've upgraded from CyanogenMod 7.1 to CyanogenMod 7.2 and i've created an sd-ext partition (in ext3 format, on a class 6 SD) to move there some apps.
I've got an HTC Desire HD.
I noticed the same problem when i was using a MIUI rom with the CPU Tuner app: i supposed that it slowed down too much the CPU when the screen was locked, so that it took a lot to come back to normal performances. But, now, i don't have that app installed and, looking ad Exaile 2 when i unlock my phone, it seems that CPU frequencies it's a 1 Ghz and even RAM usage is ok.
What could it be?
I have to wipe and install CM 7.2 from scratch?
Or could it be the sd-ext partition with apps on?
Thank you in advance!
Try installing set CPU or CPU Tuner again and set the CPU to something high when the phone is asleep. If that then works and it is no longer laggy try reverting it to a lower speed.
Not sure about the sd ext partition,, but yes, try a full wipe and install 7.2.
Sent from a dream.
Just change the governor. Governor is interactive by default i think.
Had the same problem after weeks i just changed governor to ondemand and everything was prefect.
Sent from my Desire HD using Tapatalk 2
Try installing set CPU or CPU Tuner again and set the CPU to something high when the phone is asleep. If that then works and it is no longer laggy try reverting it to a lower speed.
Click to expand...
Click to collapse
When i had it, i never configured because i am too lazy
I'll give a try, thanks!
Not sure about the sd ext partition,, but yes, try a full wipe and install 7.2.
Click to expand...
Click to collapse
I do not really want to, but i think too that could be a good test
Just change the governor. Governor is interactive by default i think.
Had the same problem after weeks i just changed governor to ondemand and everything was prefect.
Click to expand...
Click to collapse
Good tip!
My governor is "interactive" too, infact. I'm changin it to "ondemand".
Does anyone have a table that explain the difference between governors?
I'm on ARHD and the same started all of a dudden a few months ago. I had the same governor and settings for months without change and this still started. I changed governors (ondemand, smoothass, smartass, etc.) but it still happens sometimes. Not ver often but sometimes.
sberla54 said:
Good tip!
My governor is "interactive" too, infact. I'm changin it to "ondemand".
Does anyone have a table that explain the difference between governors?
Click to expand...
Click to collapse
Here you go
7. CPU Scaling Governors
CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies. Most kernels have “ondemand” and “performance.” The availability
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
interactive – Available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
smartass – Included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
Click to expand...
Click to collapse
Here as well
CPUFreq governors in the Android Kernel
=======================================
+ performance
The CPUfreq governor "performance" sets the CPU statically to the highest frequency within the borders of scaling_min_freq and scaling_max_freq.
+ powersave
The CPUfreq governor "powersave" sets the CPU statically to the lowest frequency within the borders of scaling_min_freq and scaling_max_freq.
+ userspace
The CPUfreq governor "userspace" allows the user, or any userspace program running with UID "root", to set the CPU to a specific frequency by making a sysfs file "scaling_setspeed" available in the CPU-device directory.
+ ondemand
The CPUfreq governor "ondemand" sets the CPU depending on the current usage. To do this the CPU must have the capability to switch the frequency very quickly. There are a number of sysfs file accessible parameters: sampling_rate, show_sampling_rate_min, up_threshold, ignore_nice_load, sampling_down_factor.
+ conservative
The CPUfreq governor "conservative", much like the "ondemand" governor, sets the CPU depending on the current usage. It differs in behaviour in that it gracefully increases and decreases the CPU speed rather than jumping to max speed the moment there is any load on the CPU. This behaviour more suitable in a battery powered environment. The governor is tweaked in the same manner as the "ondemand" governor through sysfs with the addition of: freq_step & down_threshold
+ interactive
The CPUfreq governor "interactive" is designed for latency-sensitive, interactive workloads. This governor sets the CPU speed depending on usage, similar to "ondemand" and "conservative" governors. However, the governor is more aggressive about scaling the CPU speed up in response to CPU-intensive activity. The tuneable value for this governor are: min_sample_time & go_maxspeed_load
+ smartass (By [email protected])
The smartass governor is a complete rewrite of the interactive governor. CPU spends much more time at the lower frequencies for improved battery life. It gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
+ savagedzen (By [email protected])
SavagedZen is a governor based on the Smartass governor. With tweaks to paramaters which control how much and how fast cpu ramps up/down. Main difference versus Smartass is that cpu ramps down not in fixed steps, but based on cpu load heuristics, i.e. when cpu load falls below threshold (min_cpu_load), cpu immediately ramps down to a frequency derived from the measured load.
+ interactiveX (By [email protected])
Modified version of interactive with suspend code which locks at lowest clock speed when screen is off. Has a sleep+awake profile, meaning you don't need to set up manual profiles, it will lock at your minimum frequency during screen off
Click to expand...
Click to collapse
andreasy said:
I'm on ARHD and the same started all of a dudden a few months ago. I had the same governor and settings for months without change and this still started. I changed governors (ondemand, smoothass, smartass, etc.) but it still happens sometimes. Not ver often but sometimes.
Click to expand...
Click to collapse
Me too i didn't changed the governor, but in my case, a ROM upgrade and a sd-ext creation are some major changes that can affect performances...
l33ch0r said:
Here you go
Here as well
Click to expand...
Click to collapse
Thank you l33ch0r!
There doesn't seem to be much difference between "ondemand" and "interactive"; regarding to this documentation, "interactive" seems more quick.
Anyway, i've changed my governor to "ondemand" and i must say that all yesterday the phone has been fast and responsive. I'll keep you updated!
Thank you very much!
Hello, after some problem decided to try some newer ROM, chosing cm-7-20130301-NIGHTLY. It works fine except for cpufreq. It seems, that CPU is forced to stay on lowest freq 99.99% of time making the phone sometimes very unresponsive and slow. Do you have any experience with this?
Tried to look in /sys/devices/system/cpu/cpu0/cpufreq/, but any change in governor and/or min/max freqs ends with
sh: write error: Invalid argument
Would be gratefull for any help.
Found a way how to workaround the problem - it is related to ondemand governor, so setting 'interactive' governor in Boot menu will change this and interactive governor behaves as expected, so I'm happy now.
BTW I found this app to be useful not only for settings (defaults are fine for me), but to easily see stats from /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state - No-frills CPU Control by Luca Santarelli.
Overclocking
OnePlus 5T A5010
This is an overclock solution for the clock speed
limiter on the OnePlus 5T's second cluster of CPUs.
Requires root access, and advised to make
a TWRP recovery backup before attempting this.
ElementalX Kernel Manager
Download
X-plore File manager
Download
(Or root browser of your choice)
Build.prop Editor
Download
SSD Boost
Download
1.
First, open up X-plore and navigate to
root/system/etc/vendor/perf/targetconfig.xml
Long press on targetconfig.xml and hit edit text,
then scroll to the very bottom where
you'll find the 2361Mhz limiter.
Replace the config1 brackets with this
Code:
<Config1>
<TargetInfo
Target="msm8998"
NumClusters="2"
TotalNumCores="8"
SocIds="292,319"
SynCore="1"
CoreCtlCpu="-1"
MinCoreOnline="0"
CpufreqGov="1" />
<ClustersInfo Id="0" NumCores="4" Type="little" />
<ClustersInfo Id="1" NumCores="4" Type="big" />
</Config1>
If you've already flashed ElementalX kernel
you can reboot and skip step 2.
2.
Flash the custom kernel
from the ElementalX tab in the app.
Choose custom installation and proceed
to select the overclock frequency caps in recovery.
3.
Set the max frequencies to 2035 and 2592Mhz
and tick the on boot icon blue.
Disable core_control and enable msm_thermal
tick both set on boot.
Enjoy your heightened and less restricted
CPU speeds.
See below for tuning
You should notice a considerable boost
in performance with these apps/tweaks.
Hope this helps anyone that's been having trouble.
Feel free to comment whether or not it worked for you.
Buy me a beer:
PayPal.me/newton3788
ElementalX Tweaks
CPU Min/Max
Cluster 1: 518Mhz / 2.03Ghz
Cluster 2: 806Mhz / 2.59Ghz
CPU Boost
Core 0: 748Mhz / Core 4: 1.26Ghz
Duration: 100ms
GPU
GPU Boost: High
Interactive governor tunables
I've added the downloadable cluster profiles at the bottom.
You may place them in the ElementalX gov_profiles folder.
Cluster 1:
go_hispeed_load - 75
above_hispeed_delay - 20000 2035200:30000
timer_rate - 20000
hispeed_freq - 1670400
timer_slack - 50000
target_loads - 70 1804800:85 1900800:90
min_sample_time - 25000
Cluster 2:
go_hispeed_load - 85
above_hispeed_delay - 20000 2592000:50000
timer_rate - 20000
hispeed_freq - 2035200
timer_slack - 50000
target_loads - 80 2265600:85 2457600:90
min_sample_time - 25000
Build.prop Tweaks
ro.min.fling_velocity=6000
ro.max.fling_velocity=12000
persist.sys.composition.type=dyn
debug.composition.type=dyn
debug.egl.force_msaa=true
persist.sys.use_dithering=1
persist.sys.scrollingcache=1
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.config.nocheckin=1
ro.kernel.android.checkjni=0
logcat.live=disable
wifi.supplicant_scan_interval=400
ro.media.enc.jpeg.quality=100
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
Open Xplore and edit
root/vendor/etc/build.prop
Replace and add these:
dalvik.vm.heapstartsize=32m
dalvik.vm.heapgrowthlimit=384m
dalvik.vm.heapsize=768m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=8m
dalvik.vm.heapmaxfree=16m
Developer Options
Force GPU Rendering off
Disable HW Overlays off
I've yet to find a solution for the random stuttering
But I'll add it if I do
newton378 said:
ElementalX Tweaks
Click to expand...
Click to collapse
Thanks for your tips here mate.
can you tell how s battery life affected
after this changes,i m trying your settings
but i faced deep sleep problems,do you face this too?
broky said:
Thanks for your tips here mate.
can you tell how s battery life affected
after this changes,i m trying your settings
but i faced deep sleep problems,do you face this too?
Click to expand...
Click to collapse
My device sleeps fine, I use the greenify app to hibernate apps on screen off. I can't account for any tweaks you've made to your device apart from what I've detailed here, mine is stock OOS with the EX kernel. Battery life drops depending on usage but you don't overclock to save battery.
edit: I was having battery problems but I've since flashed stock OOS and set everything back up, the battery life is superb with these governor profiles.
OK,I was just anxious about deep sleep,
I know overclockung drains battery.
Will keep on trying this
EDITnewton378
why don t you post this on oneplus 5 thread also, so more people see it and test it?
(just a suggestion)
broky said:
OK,I was just anxious about deep sleep,
I know overclockung drains battery.
Will keep on trying this
EDITnewton378
why don t you post this on oneplus 5 thread also, so more people see it and test it?
(just a suggestion)
Click to expand...
Click to collapse
http://imgur.com/a/Bhqj83w
No problem with deep sleep on my end.
newton378 said:
http://imgur.com/a/Bhqj83w
No problem with deep sleep on my end.
Click to expand...
Click to collapse
were you using the phone for 2 hours constantly?
or you left the phone idle?
broky said:
were you using the phone for 2 hours constantly?
or you left the phone idle?
Click to expand...
Click to collapse
Constant use and then idle for 10 minutes, deep sleep initiated quickly. No idea what problem you're having, sorry.
newton378 said:
Constant use and then idle for 10 minutes, deep sleep initiated quickly. No idea what problem you're having, sorry.
Click to expand...
Click to collapse
Testing as we talking,till now my deep sleep is fine.
Probably something else caused this,thanks for your response and help.
Update
newton378 said:
ElementalX Tweaks
CPU Boost
Core 0: 748Mhz / Core 4: 1.26Ghz
Duration: 100ms
Click to expand...
Click to collapse
you mean
A
0:748Mhz
1:0
2:0
3:0
4:1.26Ghz
5:0
6:0
7:0
or
B
0:748Mhz
1:748Mhz
2:748Mhz
3:748Mhz
4:1.26Ghz
5:1.26Ghz
6:1.26Ghz
7:1.26Ghz
??
i use configuration B and the device is faster than ever but i need to know if this is right:good:
broky said:
you mean
A
0:748Mhz
1:0
2:0
3:0
4:1.26Ghz
5:0
6:0
7:0
or
B
0:748Mhz
1:748Mhz
2:748Mhz
3:748Mhz
4:1.26Ghz
5:1.26Ghz
6:1.26Ghz
7:1.26Ghz
??
i use configuration B and the device is faster than ever but i need to know if this is right:good:
Click to expand...
Click to collapse
I don't think it matters as each cluster's frequencies are locked in sync. Core 1-3 follow 0 and 5-7 follow 4. Setting SynCore to 0 in targetconfig.xml is supposed to allow all cores to fluctuate on their own but it doesn't. Controller must be embedded deeper in the system.
broky said:
OK,I was just anxious about deep sleep,
I know overclockung drains battery.
Will keep on trying this
EDITnewton378
why don t you post this on oneplus 5 thread also, so more people see it and test it?
(just a suggestion)
Click to expand...
Click to collapse
I believe the phone doesn't enter deep sleep when charging due to rapid charging technology. Not sure if turning the phone off to charge helps it stay low power.
I figure this because I left it charging overnight and I had 33 minutes deep sleep and 10 hours of min frequency.
is it required elementalx kernel?cuz i'm using arter kernel right now
filandry said:
is it required elementalx kernel?cuz i'm using arter kernel right now
Click to expand...
Click to collapse
For the tweaks in the second post, no. If you want to have the overclocked CPU speeds, it's made possible by flashing EX kernel with custom settings.
I've tried flashing bluspark kernel over EX kernel and the result was relatively smoother than stock OOS with only EX kernel, however a lot of the settings in EXKM were automatically reverting to bluspark defaults when changed. I don't advise flashing custom kernels over each other unless you want to experiment and have a backup.
You can still remove the limiter on the second cluster's cores with the targetconfig.xml tweak for 2.45Ghz max clock speed.
newton378 said:
For the tweaks in the second post, no. If you want to have the overclocked CPU speeds, it's made possible by flashing EX kernel with custom settings.
I've tried flashing bluspark kernel over EX kernel and the result was relatively smoother than stock OOS with only EX kernel, however a lot of the settings in EXKM were automatically reverting to bluspark defaults when changed. I don't advise flashing custom kernels over each other unless you want to experiment and have a backup.
You can still remove the limiter on the second cluster's cores with the targetconfig.xml tweak for 2.45Ghz max clock speed.
Click to expand...
Click to collapse
so i only need this right?(for remove limiter)
First, open up X-plore and navigate to
root/system/etc/vendor/perf/targetconfig.xml
Long press on targetconfig.xml and hit edit text,
then scroll to the very bottom where
you'll find the 2361Mhz limiter.
Replace the config1 brackets with this
filandry said:
so i only need this right?(for remove limiter)
First, open up X-plore and navigate to
root/system/etc/vendor/perf/targetconfig.xml
Long press on targetconfig.xml and hit edit text,
then scroll to the very bottom where
you'll find the 2361Mhz limiter.
Replace the config1 brackets with this
Click to expand...
Click to collapse
Correct.
newton378 said:
Correct.
Click to expand...
Click to collapse
okay,will give it try :good:
edit :
yes it worked,although it's litte bit different from your guide..
here's my guide to remove second cluster cpu clock limiter (no overclock) using stock cpu clock speed :
First, open up Explorer and navigate to
/system/vendor/etc/perf
Find and Long press on targetconfig.xml and hit edit text,
then scroll to the very bottom where
you'll find the 2361600 limiter number and change it to 2467600
Save And Exit,and then reboot the devices
filandry said:
okay,will give it try :good:
edit :
yes it worked,although it's litte bit different from your guide..
here's my guide to remove second cluster cpu clock limiter (no overclock) using stock cpu clock speed :
First, open up Explorer and navigate to
/system/vendor/etc/perf
Find and Long press on targetconfig.xml and hit edit text,
then scroll to the very bottom where
you'll find the 2361600 limiter number and change it to 2467600
Save And Exit,and then reboot the devices
Click to expand...
Click to collapse
Yes, that would effectively raise the frequency cap but it works the same removing it altogether. Hence, cluster 1 doesn't have the max freq parameter in there and it can hit 1.9Ghz by default.
a10
does it work for android 10