if you don't have it you are crazyFor anyone overclocking. Consider buying Tablet CPU monitor. Fantastic program, amazing dev. Really helps you put together whats happening in your system.
Sent from my Transformer Prime TF201 using Tapatalk
if you don't have it you are crazyFor anyone overclocking. Consider buying Tablet CPU monitor. Fantastic program, amazing dev. Really helps you put together whats happening in your system.
Sent from my Transformer Prime TF201 using Tapatalk
Yeah, hehe, have it since the first day, and the new changes in store are going to be very nice (temp monitoring and stuff)
Enviado desde mi Transformer Prime TF201 usando Tapatalk
For anyone overclocking. Consider buying Tablet CPU monitor. Fantastic program, amazing dev. Really helps you put together whats happening in your system.
Sent from my Transformer Prime TF201 using Tapatalk
well it can't go past 1.8 since the kernel only supports 1.8Doesn't overclock past 1.8 for me on my virtuous rom, gonna try it on the stock stock rom.
HAHA, I requested temp monitoring. I am glad he is putting it in thats awesome.
Sent from my Transformer Prime TF201 using Tapatalk
is it possible to convert this into an apk form like EZOverclock? where there is no need for unlocking and CWM. all needed is rooted device and installing the app. just curious
great work though. plus u mentioning 1.8Ghz might be the final straw needed to push me over the edge to unlock..lol cant wait to see it implemented. I'm holding back so badly with all this new developement coming out for prime. its really starting to blow up in here and temptation to unlock is eating me up
Forgot to mention removed previous changes that prevented overclocking ofcourse
An update coming tonight with more changes
Edit: @tyler i just recieved your mail, thanks for testing, so the kernel @5th april was good? The kernel above is much more improved, plus i think i can spend an hour tonight n make atleast 10+ great changes
echo 520 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
echo 650 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
echo 1 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled
#!/system/bin/sh
echo 4 > /sys/module/cpu_tegra/parameters/system_mode
echo 1350 > /sys/kernel/tegra_cap/core_cap_level
echo 0 > /sys/kernel/tegra_cap/core_cap_state
echo 0 > /sys/devices/platform/tegra_grhost/enable_3d_scaling
echo 10 > /sys/module/cpu_tegra3/parameters/mp_overhead
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_1
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_2
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_3
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_4
setprop power.saving.mode 1
setprop persist.tegra.NV_FPSLIMIT 0
setprop persist.sys.NV_FPSLIMIT 0
setprop persist.sys.NV_POWERMODE 0
echo 1700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo N > /sys/module/cpu_tegra3/parameters/no_lp
#!/system/bin/sh
# auto zram activation init script with busybox search
# by show-p1984
echo "[90ZRAM]: Firing up /system/etc/init.d/90zram";
if [ ! -e /sys/block/zram0/disksize ] ; then
echo "[90ZRAM]: ERROR unable to find /sys/block/zram0/disksize";
echo "[90ZRAM]: Is this a ZRAM kernel?";
echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
else
#find busybox in /system
bblocation=$(find /system/ -name 'busybox')
if [ -n "$bblocation" ] && [ -e "$bblocation" ] ; then
echo "[90ZRAM]: busybox found in:" $bblocation;
echo "[90ZRAM]: Setting ZRAM disksize.";
echo $((100*1024*1024)) > /sys/block/zram0/disksize
echo "[90ZRAM]: Starting ZRAM...";
bblocation=${bblocation%/*}
cd $bblocation
./busybox mkswap /dev/block/zram0
./busybox swapon /dev/block/zram0
echo "[90ZRAM]: ZRAM activated.";
else
echo "[90ZRAM]: ERROR! busybox not found!";
echo "[90ZRAM]: Is busybox installed? Symlinks set?";
echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
fi
fi
#!/system/bin/sh
echo 4 > /sys/module/cpu_tegra/parameters/system_mode
echo 1350 > /sys/kernel/tegra_cap/core_cap_level
echo 0 > /sys/kernel/tegra_cap/core_cap_state
echo 0 > /sys/devices/platform/tegra_grhost/enable_3d_scaling
echo 10 > /sys/module/cpu_tegra3/parameters/mp_overhead
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_1
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_2
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_3
echo 9999999 > /sys/module/cpu_tegra/parameters/pwr_cap_limit_4
setprop power.saving.mode 1
setprop persist.tegra.NV_FPSLIMIT 0
setprop persist.sys.NV_FPSLIMIT 0
setprop persist.sys.NV_POWERMODE 0
echo 1700000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo N > /sys/module/cpu_tegra3/parameters/no_lp
#!/system/bin/sh
# auto zram activation init script with busybox search
# by show-p1984
echo "[90ZRAM]: Firing up /system/etc/init.d/90zram";
if [ ! -e /sys/block/zram0/disksize ] ; then
echo "[90ZRAM]: ERROR unable to find /sys/block/zram0/disksize";
echo "[90ZRAM]: Is this a ZRAM kernel?";
echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
else
#find busybox in /system
bblocation=$(find /system/ -name 'busybox')
if [ -n "$bblocation" ] && [ -e "$bblocation" ] ; then
echo "[90ZRAM]: busybox found in:" $bblocation;
echo "[90ZRAM]: Setting ZRAM disksize.";
echo $((100*1024*1024)) > /sys/block/zram0/disksize
echo "[90ZRAM]: Starting ZRAM...";
bblocation=${bblocation%/*}
cd $bblocation
./busybox mkswap /dev/block/zram0
./busybox swapon /dev/block/zram0
echo "[90ZRAM]: ZRAM activated.";
else
echo "[90ZRAM]: ERROR! busybox not found!";
echo "[90ZRAM]: Is busybox installed? Symlinks set?";
echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
fi
fi
Has Motley forsaken us for the Nexus? Loads of cool stuff going on over there but the Prime kernel scene seems dead as a doornail.
Thanks for making another kernel mr motley!
The kernel is working wonders with Paranoid Android on my 64 GB Prime. Have you implemented any of the optimizations from your old kernel for eMMC? I don't know if the driver for it is updated or not.
Typing is a dream now since there is almost no lag now.
Hi Motley, can i ask would it be possible for you to include SIO IO scheduler in your kernel? we had it on ICS and it was faster than others, well felt like anyway!
thanks
The ROW scheduler is now default. It aids in the slow flash memory, especially ours, by prioritizing Read Over Write, which is what the acronym represents. ROW is nearly identical to SIO except what I said above. This makes it so that fsync writes are scheduled further back and do not interfere with main operation all the time. It still does not solve the problem presented with our slow eMMC, but it helps loads.
Thanks, is there a motley kernel for stock JB base 4.1? I couldnt find one! Thanks
Sent from my Transformer Prime TF201 using XDA Premium HD app