[Shield Tablet General] m0nt3s:
So I've never really been happy with the stock shield tablets performance. It's a gaming tablet, so why do I get pwned in Vainglory due to my touches not being registered or stuttering. I understand why Nvidia had to put a cap on performance and I'll tell you how to get the performance that you expected but it's on you if you do decide to utilize my advice. Number 1 is HAVE AN EXTERNAL COOLING SOURCE! A common house fan placed behind the tablet at the very minimum.

Step one, Be rooted. Step two, flash [MENTION=6411851]BitOBSessiOn[/MENTION] OC Kernel [MENTION=4716493]laufersteppenwolf[/MENTION] really put in some time in effort in making sure its awesome and that the voltages wouldn't **** your device over. I've tested it through and through and he put nvidia to shame with it.

That being said, you won't get anywhere unless your boot.img default prop looks like this.

#

# ADDITIONAL_DEFAULT_PROPERTIES

#

ro.secure=0

security.perf_harden=0

ro.allow.mock.location=0

ro.debuggable=1

ro.zygote=zygote32

dalvik.vm.image-dex2oat-Xms=64m

dalvik.vm.image-dex2oat-Xmx=64m

dalvik.vm.dex2oat-Xms=64m

dalvik.vm.dex2oat-Xmx=512m

ro.dalvik.vm.native.bridge=0

debug.atrace.tags.enableflags=0

persist.sys.usb.config=mtp,adb

ro.adb.secure=0

#

This is important because ADB SHELL is going to be your best friend, Terminal does work equally as well but with SHELL you can copy and paste so much faster. I've enabled init.d every which way possible in the boot.img init.rc i.e

on property:sys.boot_completed=1

start sysinit

service sysinit /sbin/sysinit.sh

oneshot

class late_start

user root

group root

disabled

mount -o remount,rw -t auto /system

mount -o remount,rw -t auto /data

mount -t rootfs -o remount,rw rootfs

if [ ! -e /system/etc/init.d ]; then

mkdir /system/etc/init.d

chown -R root.root /system/etc/init.d

chmod -R 755 /system/etc/init.d

fi

for FILE in /system/etc/init.d/*; do

sh $FILE >/dev/null

done;

mount -t rootfs -o remount,ro rootfs

mount -o remount,rw -t auto /data

mount -o remount,ro -t auto /system

it works for running #!/bin/sh and #!/system/bin/sh scripts all day but to get true performance scripts wont work. The only true way to maximize is through SU adb shell.

I've probably rambled enough already and if you understand what i've been going on about, this is how to Max your shield to the upmost dangerous overclock. you've been warned.

I know I said scripts don't work but if any one does benefit benchmarking it,s disabling journaling. This is done through TWRP. This is for ext4 partitions. Unmount /system /data /cache though TWRP and then you can ADB shell or TWRP terminal and type "SH, whatever you name this following text.sh

#!/sbin/sh

sync;

/sbin/busybox umount -l /system

/sbin/busybox umount -l /cache

/sbin/busybox umount -l /data

/sbin/busybox umount -l /dev/block/mmcblk0p13

/sbin/busybox umount -l /dev/block/mmcblk0p14

/sbin/busybox umount -l /dev/block/mmcblk0p23

/sbin/tune2fs -m 0 /dev/block/mmcblk0p13

/sbin/tune2fs -m 0 /dev/block/mmcblk0p14

/sbin/tune2fs -m 0 /dev/block/mmcblk0p23

/sbin/tune2fs -m 0 /dev/block/platform/sdhci-tegra.3/by-name/APP

/sbin/tune2fs -m 0 /dev/block/platform/sdhci-tegra.3/by-name/CAC

/sbin/tune2fs -m 0 /dev/block/platform/sdhci-tegra.3/by-name/UDA

/sbin/e2fsck -yf /dev/block/platform/sdhci-tegra.3/by-name/APP

/sbin/e2fsck -yf /dev/block/platform/sdhci-tegra.3/by-name/CAC

/sbin/e2fsck -yf /dev/block/platform/sdhci-tegra.3/by-name/UDA

/sbin/e2fsck -p /dev/block/platform/sdhci-tegra.3/by-name/APP

/sbin/e2fsck -p /dev/block/platform/sdhci-tegra.3/by-name/CAC

/sbin/e2fsck -p /dev/block/platform/sdhci-tegra.3/by-name/UDA

/sbin/e2fsck -p /dev/block/mmcblk0p13

/sbin/e2fsck -p /dev/block/mmcblk0p14

/sbin/e2fsck -p /dev/block/mmcblk0p23

/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/platform/sdhci-tegra.3/by-name/APP

/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/platform/sdhci-tegra.3/by-name/CAC

/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/platform/sdhci-tegra.3/by-name/UDA

/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/mmcblk0p13

/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/mmcblk0p14

/sbin/tune2fs -o journal_data_writeback -c 1 -i 1d -m 0 /dev/block/mmcblk0p23

/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/platform/sdhci-tegra.3/by-name/APP

/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/platform/sdhci-tegra.3/by-name/CAC

/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/platform/sdhci-tegra.3/by-name/UDA

/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p13

/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p14

/sbin/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p23

/sbin/e2fsck -Dfy /dev/block/platform/sdhci-tegra.3/by-name/APP

/sbin/e2fsck -Dfy /dev/block/platform/sdhci-tegra.3/by-name/CAC

/sbin/e2fsck -Dfy /dev/block/platform/sdhci-tegra.3/by-name/UDA

/sbin/e2fsck -Dfy /dev/block/mmcblk0p13

/sbin/e2fsck -Dfy /dev/block/mmcblk0p14

/sbin/e2fsck -Dfy /dev/block/mmcblk0p23

sync;

This is my 50th some odd test combination that outputs the best results. remember, unmount before running.

So now down to the brass tax. This is no way good for your device, you must have cooling and it rapes the battery so plug in.

we can put the device in true performance mode, which means maxing out both gpus, putting all cores online, disabling the 5th cpu core, keeping the high power cluster always activated

ADB SHELL#

echo 0 > /sys/devices/system/cpu/cpuquiet/tegra_cpuquiet/enable

echo 1 > /sys/devices/system/cpu/cpu0/online

echo 1 > /sys/devices/system/cpu/cpu1/online

echo 1 > /sys/devices/system/cpu/cpu2/online

echo 1 > /sys/devices/system/cpu/cpu3/online

echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo 480000000 > /sys/kernel/debug/clock/override.c2bus/rate

echo 1 > /sys/kernel/debug/clock/override.c2bus/state

echo 756000000 > /sys/kernel/debug/clock/override.c3bus/rate

echo 1 > /sys/kernel/debug/clock/override.c3bus/state

echo G > /sys/kernel/cluster/active

cat /sys/kernel/debug/clock/override.emc/max > /sys/kernel/debug/clock/override.emc/rate

echo 1 > /sys/kernel/debug/clock/override.emc/state

for i in `ls /sys/devices/system/cpu/cpu*/cpuidle/state*/disable`; do echo 1

> $i; done

cat /sys/kernel/debug/clock/gbus/max > /sys/kernel/debug/clock/override.gbus/rate

echo 1 > /sys/kernel/debug/clock/override.gbus/state

echo userspace > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo userspace > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

echo userspace > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor

echo userspace > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

cat /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq

cat /sys/devices/system/cpu/cpu2/cpufreq/scaling_max_freq > /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq

cat /sys/devices/system/cpu/cpu3/cpufreq/scaling_max_freq > /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq

echo 0 > /sys/devices/system/cpu/cpuquiet/tegra_cpuquiet/enable

for file in /sys/devices/system/cpu/cpu*/online; do

if [ `cat $file` -eq 0 ]; then

echo 1 > $file

fi

done

just copy and paste all of it once you're SU in ADB SHell for maximum performance.

To get your touch screen to respond as fast as you use file explorer to navigate to /system/usr/idc

and edit touch.idc by deleting the # from infront of

touch.pressure.calibration = amplitude

touch.pressure.source = default

touch.pressure.scale = 0.01

This is how I benchmark so high everytime, but remember, with great voltage comes great heat.

Shoutout to [MENTION=6411851]BitOBSessiOn[/MENTION] for inspiring me to learn.

I've attached my edited boot.img with init.d support and bit's f2fs kernel already installed.

unzip the image and flash it with

fastboot flash boot boot.img

if you try to flash it through recovery it wont work. I've also attached the journaling script and a virtual memory tweak script that helps with performance.