I'm planning on overclocking my device by modifying the init.doh script. I have made the modifications as follows:
Code:
#!/system/bin/sh
sleep 5
# ===================
# Max CPU
# ===================
echo "1504000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
# ===================
# Min CPU
# ===================
echo "200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
# ===================
# Undervolting
# ===================
echo "1425 1300 1200 1100 1000 950 900 900 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
# ===================
# CPU Table
# ===================
echo "1600 1400 1200 1000 800 500 200 100" > /sys/devices/system/cpu/cpu0/cpufreq/freq_table;
# ===================
# Governor
# ===================
echo "lulzactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
^This is the section of the script I've made modifications to.
As you can see I've OC'ed to 1.5GHz and changed governor to Lulzactive, to see if I can get it stable here as 1.6 causes lockups and crashes.
Did I do it right? Do I need to add 1504 to the respective spots in the cpu frequency/undervolt lists?
Any help is appreciated.
Please don't say to use Setcpu or something. I want to learn something here
Is it possible to oc to 1.5G? I thought the steps above 1.2G are 1.4G and 1.6G. The in between frequencies are physically possible? If not, using those number is not going to be useful I guess?
dineshbabumm said:
Is it possible to oc to 1.5G? I thought the steps above 1.2G are 1.4G and 1.6G. The in between frequencies are physically possible? If not, using those number is not going to be useful I guess?
Click to expand...
Click to collapse
Its possible. I found a stable overclock too
You go off of the most stable setting you can find and add increments of 8 until you find a spot where there's a good balance of stability and speed.
For me it was 1496
Mod can close this now.
Hi.
I have troubles with overclocking/undervolting my xperia mini pro (SK17i)
I use KRsH Kernel v3.0 ICS
for overclocking/undervolting i use System Tuner
I have problems with 768mhz frequency - my phone freezes even when I set much more voltage than on higher frequency step.
So I tryed to disable 768mhz from scaling frequencies. But executing the following script ends with error, no permission to execute the command to change available scaling frequencies.
is there any way to disable the 768mhz from available scaling frequencies?
Any help would be greatly appreciated.
Note: all frequencies besides 768mhz are stable.
Code:
#!/system/bin/sh
if [ -e /data/local/cpu_protection ] ; then
echo failed > /data/local/cpu_failed
chmod 777 /data/local/cpu_failed
exit
fi
echo "134400 184320 249600 364800 460800 576000 652800 806400 921600 1017600 1113600 1209600 1305600 1401600 1516800 1612800 1708800 1804800" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
echo applied > /data/local/cpu_protection
chmod 777 /data/local/cpu_protection
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "1708800" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "134400" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
#! 750 750 750 750 750 850 850 850 950 875 925 950 1000 1025 1075 1125 1200 1250 1300 1375 1425 1500
echo "134400 750" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "184320 750" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "192000 750" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "249600 750" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "364800 750" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "460800 850" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "576000 850" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "652800 850" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "768000 950" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "806400 875" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "921600 925" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "1017600 950" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "1113600 1000" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "1209600 1025" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "1305600 1075" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "1401600 1125" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "1516800 1200" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "1612800 1250" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "1708800 1300" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "1804800 1375" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "1900800 1425" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo "2016000 1500" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
Come on guys, is here single soul able to help?
Perhaps problem with kernel. I recommend rage kernel.
Sent from my WT19i using xda app-developers app
Hmm, this is very strange,
I use for testing Stability test 2.5 and if i during scaling testing press home and launch GPS Time 0.6.3 my phone crashes after couple seconds, no matter what voltage or scaling frequencies I select.
Could anyone please test this app combination on his own phone?
Thanks in advance.
This is the instruction originally posted by kevev in the other thread. I am reposting it here for others to find it easier.
--------------------------------------------------------------
1.) Root your device.
2.) Download to your device "overclock.zip" from this thread:
http://forum.xda-developers.com/showthread.php?t=1961989
3.) Install "AndroZip File Manager" from the Play store.
4.) Run AndroZip and browse to overclock.zip. (Probably /mnt/sdcard/Download .)
5.) tap on the file "overclock.zip" and select "Extract file here".
(A new directory named "overclock" is created)
6.) Install "ES File Explorer File Manager" from the Play store.
7.) Run ES File Explorer and press your "menu" button then select "settings".
8.) Change these settings:
Home Directory = /
Root settings --> Check all boxes
9.) Press the "back" button until the app exits.
10.) Run ES File Explorer again.
(Now your root partition "/" should be mounted with read/write permissions.
11.) Browse to the overclock directory. (Probably /mnt/sdcard/Download/overclock/ .)
12.) Long press on the cpu_control.ko file and a menu should open. Select "copy".
13.) Browse to the /system/lib/modules/ directory .
14.) Press "menu" button and select "Operations" then select "Paste" .
15.) Long press on the cpu_control.ko file and a menu should open. Select "Properties".
16.) Press "Change" and check the boxes like this:
User: read write
Group: read
Other: read
17.) Perform steps 12-17 on the symsearch.ko file which is also in the overclock directory.
18.) Install "Rom Toolbox Lite" from the Play store.
19.) Run ROM Toolbox Lite and select "Scripter".
20.) Press the "+" symbol in the top right corner and select "Create" to add the overclock script.
21.) Name it "overclock" or whaterver you wish.
22.) In the "Commands:" field enter this:
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/cpu_control.ko
echo 0 300 980 > /proc/cpu_control/tweak_cpu
echo 1 600 1200 > /proc/cpu_control/tweak_cpu
echo 2 800 1300 > /proc/cpu_control/tweak_cpu
echo 3 1200 1370 > /proc/cpu_control/tweak_cpu
23.) Your phone will overclock to 1.2Ghz.
If you wish to overclock higer you can try changing 1200 in the last line to 1300 for 1.3Ghz.
24.) Press the floppy disk in the top right corner to save the script.
25.) Press the overclock script and a menu will open. Select "Run Script".
If everything worked you should see an "exit valut:0" message.
If you run the script again you will see the same value but with a warning message.
This is normal since the modules are already loaded.
26.) You can load a cpu monitoring app to see if the overclocking works or just create another script that displays cpu clock info.
Here is the command for that script:
cat /proc/cpu_control/opp_table_current
27.) After making sure your device is stable you can have the overclock script run automatically at boot.
Press the "overclock" script and a menu will open.
Press "Set at boot"
Reboot the device and you will see a notification that the script ran in the notification area of the device at top.
All credits go to iodak and the thread created here: http://forum.xda-developers.com/show....php?t=1961989
I have been using slightly different apps to make the phone set to overclock automatically after a boot, I use 'SManager' app to edit and save the script (there is a free version) to run the script after a boot up.
Then I also use "CPU Master"(free version) to control the upper frequency set and the scaling method. I have been using 'interactive'.
With those two apps, the phone will boot up after a reset to the proper frequency and be ready to go automatically.
Try the following script if you want to try to push it to 1300MHz.
Code:
#! /system/bin/sh
insmod /system/lib/modules/symsearch.ko
insmod /system/lib/modules/cpu_control.ko
echo 0 333 830 > /proc/cpu_control/tweak_cpu
echo 1 666 1050 > /proc/cpu_control/tweak_cpu
echo 2 999 1150 > /proc/cpu_control/tweak_cpu
echo 3 1300 1340 > /proc/cpu_control/tweak_cpu
You can try 1220Mhz on 1270mV. For me it is more stable then on 1200Mhz and 1360mV.
luq529 said:
You can try 1220Mhz on 1270mV. For me it is more stable then on 1200Mhz and 1360mV.
Click to expand...
Click to collapse
Were you having problems at 1200MHz and 1360mV? I'm just curious how one determines one set up is more stable than the others.
I have tried running SetCPU stress tests before but that test either runs fine or ends with a lock up.
Thank You csrow for mentioning me.
My P769 would not run stable @ 1200Mhz so I removed the overclock. I may have bad hardware because it has been rebooting randomly at stock clock speeds. This is my 3rd L9. My wife is on her 3rd also.
csrow said:
Were you having problems at 1200MHz and 1360mV? I'm just curious how one determines one set up is more stable than the others.
I have tried running SetCPU stress tests before but that test either runs fine or ends with a lock up.
Click to expand...
Click to collapse
I don't know why. On this settings I have 8200 points in Antutu. Maybe 1220 Mhz is better for our processor.
my current stable voltages
Code:
echo 0 300 830 > /proc/cpu_control/tweak_cpu
echo 1 600 860 > /proc/cpu_control/tweak_cpu
echo 2 800 890 > /proc/cpu_control/tweak_cpu
echo 3 1000 950 > /proc/cpu_control/tweak_cpu
csrow said:
http://forum.xda-developers.com/show....php?t=1961989
Click to expand...
Click to collapse
Link is dead :'[
adixtra said:
my current stable voltages
Code:
echo 0 300 830 > /proc/cpu_control/tweak_cpu
echo 1 600 860 > /proc/cpu_control/tweak_cpu
echo 2 800 890 > /proc/cpu_control/tweak_cpu
echo 3 1000 950 > /proc/cpu_control/tweak_cpu
Click to expand...
Click to collapse
How do you do that ?! That's amazing from 1388 to 950. I will try it soon.
Jrkoffjonson said:
Link is dead :'[
Click to expand...
Click to collapse
Fixed the link. Try again.
Now we have full working CWM 6 for L9, is it by any chance possible to make flashable zip for overclocking and a zip for reverting back to default clock settings?
Which are the best settings to save more battery life??
Any way to overclock also gpu?
Does anyone know the default voltage for L9?
klhk said:
Does anyone know the default voltage for L9?
Click to expand...
Click to collapse
Here the default voltages.
echo 0 300 1025 > /proc/cpu_control/tweak_cpu
echo 1 600 1200 > /proc/cpu_control/tweak_cpu
echo 2 800 1325 > /proc/cpu_control/tweak_cpu
echo 3 1000 1388 > /proc/cpu_control/tweak_cpu
These are my voltages:
Code:
echo 0 300 830 > /proc/cpu_control/tweak_cpu
echo 1 600 830 > /proc/cpu_control/tweak_cpu
echo 2 800 840 > /proc/cpu_control/tweak_cpu
echo 3 1000 860 > /proc/cpu_control/tweak_cpu
They seems crazy low compared to stock but I tested them one by one (set governor to fixed frequency) and they were all stable for 20 minutes of stability test (classic test).
I verified they were successfully applied running "cat /proc/cpu_control/opp_table_current"
I played also fifa 12 for 15 minutes with interactive governor min 300 max 1000 and system was stable.
How can it be?
This is my setting, i will try lower voltage later.
echo 0 300 850 > /proc/cpu_control/tweak_cpu
echo 1 600 880 > /proc/cpu_control/tweak_cpu
echo 2 800 920 > /proc/cpu_control/tweak_cpu
echo 3 1000 1000 > /proc/cpu_control/tweak_cpu
Sent from my LG-P765 using xda app-developers app
I have V10H firmware and now overclock script don't work...It says:
Finished executing script file
exit value: 1
stdout:
null
stderr:
insmod: init_module '/system/lib/modules/symsearch.ko' failed (Exec format error)
insmod: init_module '/system/lib/modules/cpu_control.ko' failed (Exec format error)
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[4]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[5]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[6]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[7]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
what to do ?
wlado93 said:
I have V10H firmware and now overclock script don't work...It says:
Finished executing script file
exit value: 1
stdout:
null
stderr:
insmod: init_module '/system/lib/modules/symsearch.ko' failed (Exec format error)
insmod: init_module '/system/lib/modules/cpu_control.ko' failed (Exec format error)
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[4]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[5]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[6]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
/data/data/com.jrummy.liberty.toolboxpro/files/tmp.sh[7]: cannot create /proc/cpu_control/tweak_cpu: No such file or directory
what to do ?
Click to expand...
Click to collapse
Try running the insmod commands from the terminal and let us know what you see. Also, try replacing the modules. Maybe they are corrupt.
well, I downloaded new modules from link in 1st post modules L9 10h 1398mV 3.0.21-00001-gd335ca33.zip
now it works
Hello, I decided to publish some guide + scripts I already use for a while, which allows you to use all CPU cores and boost GPU performance.
Battery consumption using this configuration surprisingly does not change much or even did not change at all, with default as well with new config my watch stays alive for ~32h with daily usage.
Some theory:
Sparrow is sold with Qualcomm Snapdragon 400 1.2GHz, which is 4 core CPU. ASUS AW2.0 official kernel though supports only 600MHz and 787MHz, as Asus probably thinks this is good balance between battery life and performance.
GPU is Adreno 302/305, which is capable running up to 450MHz, which is also supported by ASUS AW2.0 kernel.
Where is the catch?
During boot there are all four CPU cores enabled, however there is post-init script, disabling two of those and setting frequency as fixed 738MHz with performance governor (no frequency scaling). GPU is set to fix 200MHz:
/system/bin/init.asus.post_boot.sh
Code:
#!/system/bin/sh
PATH=/system/bin
cd /sys
echo 4 > module/lpm_levels/enable_low_power/l2
echo 1 > module/msm_pm/modes/cpu0/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu1/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu2/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu3/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu0/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu1/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu2/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu3/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu0/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu1/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu2/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu3/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu0/power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu1/power_collapse/idle_enabled
#Put all other cores offline
echo 0 > devices/system/cpu/cpu2/online
echo 0 > devices/system/cpu/cpu3/online
governor="performance"
scaling_min_freq="787200"
if [[ `grep "oem_perf_change" /proc/cmdline` ]];then
if [[ `grep "oem_perf_on" /proc/cmdline` ]];then
oem_perf_stats="1"
else
oem_perf_stats="0"
fi
echo -n $oem_perf_stats > /factory/oem_perf_stats
fi
echo $governor > devices/system/cpu/cpu0/cpufreq/scaling_governor
echo $governor > devices/system/cpu/cpu1/cpufreq/scaling_governor
#below ondemand parameters can be tuned
echo 50000 > devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 90 > devices/system/cpu/cpufreq/ondemand/up_threshold
echo 1 > devices/system/cpu/cpufreq/ondemand/io_is_busy
echo 2 > devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 10 > devices/system/cpu/cpufreq/ondemand/down_differential
echo 70 > devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core
echo 10 > devices/system/cpu/cpufreq/ondemand/down_differential_multi_core
echo 787200 > devices/system/cpu/cpufreq/ondemand/optimal_freq
echo 300000 > devices/system/cpu/cpufreq/ondemand/sync_freq
echo 80 > devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load
echo $scaling_min_freq > devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo $scaling_min_freq > devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo 787200 > devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 787200 > devices/system/cpu/cpu1/cpufreq/scaling_max_freq
#Below entries are to set the GPU frequency and DCVS governor
echo 200000000 > class/kgsl/kgsl-3d0/devfreq/max_freq
echo 200000000 > class/kgsl/kgsl-3d0/devfreq/min_freq
echo performance > class/kgsl/kgsl-3d0/devfreq/governor
chown -h system devices/system/cpu/cpu[0-1]/cpufreq/scaling_max_freq
chown -h system devices/system/cpu/cpu[0-1]/cpufreq/scaling_min_freq
chown -h root.system devices/system/cpu/cpu[1-3]/online
chmod 664 devices/system/cpu/cpu[1-3]/online
It is indeed required just to alter this script and you can enable all 4 cores with "ondemand" governor, scaling 600-738MHz and GPU scaling 200-450MHz using "msm-adreno-tz" governor:
(and this requires root of course)
Code:
#!/system/bin/sh
PATH=/system/bin
cd /sys
echo 4 > module/lpm_levels/enable_low_power/l2
echo 1 > module/msm_pm/modes/cpu0/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu1/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu2/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu3/power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu0/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu1/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu2/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu3/standalone_power_collapse/suspend_enabled
echo 1 > module/msm_pm/modes/cpu0/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu1/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu2/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu3/standalone_power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu0/power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu1/power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu2/power_collapse/idle_enabled
echo 1 > module/msm_pm/modes/cpu3/power_collapse/idle_enabled
governor="ondemand"
scaling_min_freq="600000"
if [[ `grep "oem_perf_change" /proc/cmdline` ]];then
if [[ `grep "oem_perf_on" /proc/cmdline` ]];then
oem_perf_stats="1"
else
oem_perf_stats="0"
fi
echo -n $oem_perf_stats > /factory/oem_perf_stats
fi
echo $governor > devices/system/cpu/cpu0/cpufreq/scaling_governor
echo $governor > devices/system/cpu/cpu1/cpufreq/scaling_governor
echo $governor > devices/system/cpu/cpu2/cpufreq/scaling_governor
echo $governor > devices/system/cpu/cpu3/cpufreq/scaling_governor
#below ondemand parameters can be tuned
echo 50000 > devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 90 > devices/system/cpu/cpufreq/ondemand/up_threshold
echo 1 > devices/system/cpu/cpufreq/ondemand/io_is_busy
echo 2 > devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 10 > devices/system/cpu/cpufreq/ondemand/down_differential
echo 70 > devices/system/cpu/cpufreq/ondemand/up_threshold_multi_core
echo 10 > devices/system/cpu/cpufreq/ondemand/down_differential_multi_core
echo 787200 > devices/system/cpu/cpufreq/ondemand/optimal_freq
echo 300000 > devices/system/cpu/cpufreq/ondemand/sync_freq
echo 80 > devices/system/cpu/cpufreq/ondemand/up_threshold_any_cpu_load
echo $scaling_min_freq > devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo $scaling_min_freq > devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo $scaling_min_freq > devices/system/cpu/cpu2/cpufreq/scaling_min_freq
echo $scaling_min_freq > devices/system/cpu/cpu3/cpufreq/scaling_min_freq
echo 787200 > devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 787200 > devices/system/cpu/cpu1/cpufreq/scaling_max_freq
echo 787200 > devices/system/cpu/cpu2/cpufreq/scaling_max_freq
echo 787200 > devices/system/cpu/cpu3/cpufreq/scaling_max_freq
#Below entries are to set the GPU frequency and DCVS governor
echo 450000000 > class/kgsl/kgsl-3d0/devfreq/max_freq
echo 200000000 > class/kgsl/kgsl-3d0/devfreq/min_freq
echo msm-adreno-tz > class/kgsl/kgsl-3d0/devfreq/governor
chown -h system devices/system/cpu/cpu[0-3]/cpufreq/scaling_max_freq
chown -h system devices/system/cpu/cpu[0-3]/cpufreq/scaling_min_freq
chown -h root.system devices/system/cpu/cpu[0-3]/online
chmod 664 devices/system/cpu/cpu[0-3]/online
(both files also attached to this post)
To exchange files in your watch, you can easily use following bash script in linux:
First push desired file into sdcard and go to ADB shell:
Code:
adb push init.asus.post_boot.sh /sdcard/
adb shell
In ADB shell remount system to RW, replace the file and fix privileges, than remount system back to RO:
Code:
su
mount -o rw,remount /system
mv /sdcard/init.asus.post_boot.sh /system/bin/
chown root:shell /system/bin/init.asus.post_boot.sh
chmod 755 /system/bin/init.asus.post_boot.sh
mount -o ro,remount /system
Update 2018/09/05:
In case you want to experiment, I'm also sending "full_power" script, setting all cores to max frequency and performance governor. There should be no issues, except probably less battery life. Just test yourself, how battery life is affected if it is affected at all. Just unpack the zip file, rename the sh script from init.asus.post_boot_full_power.sh to init.asus.post_boot.sh. Rest of the procedure is still the same.
Without kernel sources, this is probably the maximum performance you can get from the watch. Obtaining kernel sources we might get up still twice of current maximum, as the HW is there, but locked on kernel level.
I just swapped the files and I'll give this a try over the next few days. It would be awesome to destroy lag without needing a kernel tweak app to make it happen. You are the man!
Update: I followed your directions, then I wiped cache and dalvik in TWRP. I have only used the watch for a few minutes with this tweak and it is noticeably faster/smoother already. Text messages display lightning fast after being received on the phone. I'm currently on WiFi in my office. The times I notice most lag on my watch is when I'm on 4G, have music playing, and get a call. The phone may ring for 5-10 seconds before the watch displays. I'm excited to see how helpful this tweak is under those conditions. I'll know later today and keep you posted.
I have not experienced any Bluetooth lag since enabling this. This is a must have mod. Thanks for this!
Glad to hear that @CVertigo1. This is just simple SW enablement of things already present in kernel, so even no cache cleans are required. You can play with it on the go even without watch restart.
Amazing will be getting some kernel with much more CPU freq. steps, like 300-768 or even to 1.2GHz (yes, our chip is capable doing so, it is just not enabled in kernel). With proper governor battery will be still ok, resting CPU most of the time in low clocks. It is pity we have great HW, but it is taken out from us with stock kernel.
It would be nice if Asus would upload the kernel source for AW2.0.
CVertigo1 said:
It would be nice if Asus would upload the kernel source for AW2.0.
Click to expand...
Click to collapse
Well we do have latest kernel source
https://www.asus.com/us/ZenWatch/ASUS_ZenWatch_2_WI501Q/HelpDesk_Download/
Or directly here:
http://dlcdnet.asus.com/pub/ASUS/Wearable/ASUS_WI501Q/ASUS_WI501Q-5.2003.1603.10-kernel-src.zip
We just need some handy guy able to compile it and add more governors and frequencies. That is something what overlapping my skills.
That is the latest kernel source for 1.5. They have not released their source for 2.0, nor any firmware for 2.0. I have contacted Asus about it multiple times and none of their reps have any idea what I'm talking about.
CVertigo1 said:
That is the latest kernel source for 1.5. They have not released their source for 2.0, nor any firmware for 2.0. I have contacted Asus about it multiple times and none of their reps have any idea what I'm talking about.
Click to expand...
Click to collapse
Ah, I see I thought 2017/05/12 stated as a release day was after AW20 concluding this had to be the new one. Pity.
Maybe they'll release it eventually...at an Asus speed, like next year.
please help me(rom Sparrow_7.1.1_Debloat ROM ):
adb shell
sparrow:/ $ su
Permission denied
htduy11 said:
please help me(rom Sparrow_7.1.1_Debloat ROM ):
adb shell
sparrow:/ $ su
Permission denied
Click to expand...
Click to collapse
Hi there, you are missing super user in your ROM. Did you installed SuperSU and Busybox thru TWRP after flashing the ROM?
Do this in TWRP, not Android.
'the command can be used in adb in windows or are different? watch must be in recovery or bootloader? wrote a step by step for noob guide please
You must boot in the TWRP recovery. You need the ADB drivers installed on your computer and is easier to use your computer for this.
mastermoon said:
'the command can be used in adb in windows or are different? watch must be in recovery or bootloader? wrote a step by step for noob guide please
Click to expand...
Click to collapse
Actually it is quite simple, what you need:
* in case you use Windows, you need drivers for android (not needed with Linux)
* working ADB
* rooted watch
Then just connect normally booted watch and in command line (Windows) or terminal (Linux), execute:
Code:
adb push init.asus.post_boot.sh /sdcard/
adb shell
Second command above will enter adb shell, when you are in, just copy paste and execute following:
Code:
su
mount -o rw,remount /system
mv /sdcard/init.asus.post_boot.sh /system/bin/
chown root:shell /system/bin/init.asus.post_boot.sh
chmod 755 /system/bin/init.asus.post_boot.sh
mount -o ro,remount /system
LeeonLee said:
Actually it is quite simple, what you need:
* in case you use Windows, you need drivers for android (not needed with Linux)
* working ADB
* rooted watch
Then just connect normally booted watch and in command line (Windows) or terminal (Linux), execute:
Code:
adb push init.asus.post_boot.sh /sdcard/
adb shell
Second command above will enter adb shell, when you are in, just copy paste and execute following:
Code:
su
mount -o rw,remount /system
mv /sdcard/init.asus.post_boot.sh /system/bin/
chown root:shell /system/bin/init.asus.post_boot.sh
chmod 755 /system/bin/init.asus.post_boot.sh
mount -o ro,remount /system
Click to expand...
Click to collapse
yeah worked perfectly... after 9 month the zenwatch is back on my wrist....
---------- Post added at 05:31 PM ---------- Previous post was at 05:29 PM ----------
LeeonLee said:
Actually it is quite simple, what you need:
* in case you use Windows, you need drivers for android (not needed with Linux)
* working ADB
* rooted watch
Then just connect normally booted watch and in command line (Windows) or terminal (Linux), execute:
Code:
adb push init.asus.post_boot.sh /sdcard/
adb shell
Second command above will enter adb shell, when you are in, just copy paste and execute following:
Code:
su
mount -o rw,remount /system
mv /sdcard/init.asus.post_boot.sh /system/bin/
chown root:shell /system/bin/init.asus.post_boot.sh
chmod 755 /system/bin/init.asus.post_boot.sh
mount -o ro,remount /system
Click to expand...
Click to collapse
worked perfectly.... after 9 months zenwatch is back on my wrist
Hey guys,
do i need to do it every time i booted up ?
And can i messure this Overclocking anywhere ?
Greetings
Namelocked said:
Hey guys,
do i need to do it every time i booted up ?
And can i messure this Overclocking anywhere ?
Greetings
Click to expand...
Click to collapse
Hi, this is permanent solution. To revert you need to replace the file with original one.
I am also not aware of any reliable Wear benchmark, but you can see HW info using e.g. AIDA64 for Wear.
LeeonLee said:
Hi, this is permanent solution. To revert you need to replace the file with original one.
I am also not aware of any reliable Wear benchmark, but you can see HW info using e.g. AIDA64 for Wear.
Click to expand...
Click to collapse
I dont even find the AIDA64 for my smartwatch :/ ?
how can i check core, cpu speed etc... aida64 isn't compatible .. tnx..