Database Users

Arch linux chroot

I started using Arch some months ago and I really enjoying it. Coming from a released based distro, it feels really nice been able to choose exactly what you want to run in your system and always have the packages up to date. For a while I have been planning on running ubuntu in my transformer but I just don't feel too comfortable with ubuntu , so decided to run arch in my transformer. I couldn't find a tutorial so I scavenged the net and found bits and peace that I put together to make this tutorial. What I like about arch is that I am in control of my system and I can run exactly what I want, thanks awesomely documented Arch!
This is a tutorial that will show you how to run Arch Linux in a chrooted environment within your Asus Tarsnformer. I will not provide a simple script that if you run it will do everything for you, instead I will teach you how to make your own installation by grabbing all necessary elements.
You will need:
Arch Live image: Go to http://archlinuxarm.org/developers/downloads and grab the omap 3/4 package.
Install environment: It can be your internal storage or a sd/micro card. Here I will show how to use the micro sd card.
Script for starting the chroot: I grabbed mine from http://forum.xda-developers.com/showthread.php?t=1517993&highlight=chroot and did some modifications. Thanks-miska-
Rooted Asus Transformer(Prime?) with Terminal: You need root to mount the file system and loop devices. In theory this should work in the Prime too.
Linux Machine
Step 1:
For installing arch in a (micro)sd card (I prefer micro as I don't need the dock for using it), first you need to format the card and make two partitions. (I used gparted) Make one partition fat and assign a small amount of space(I have a 4gb micro and assigned 128mb to the fat partition), then make the rest ext4. Make sure the fat partition is first and the ext one is second.
Step 2:
Now as root you need to extract the package in the ext partition of your card. REMEMBER to be root, I got stuck thinking there was something wrong with the package I downloaded but it was that I was unpacking as normal user.
Code:
# tar -c /path/to/extpartition -xzf ArchLinuxARM-omap-smp-latest.tar.gz
Now you have a arch environment in your (micro)sd card.
Step 3:
In your asus transformer create a folder called 'arch' in the root of your internal storage.
Code:
#mkdir /sdcard/arch
Or use a file manager.
Now place this script somewhere in your transformer, I usually keep it in /sdcard/Downloads
Code:
#!/bin/sh
# Modify this according to your needs
DEVICE="/dev/block/mmcblk1p2"
LOOP="no"
# Maybe this as well
MNT_PATH="/mnt/sdcard/arch"
# Modify only if you know, what are you doing
BINDS="dev dev/pts proc sys mnt/sdcard"
ANDROID_BINDS=" /system /data "
TMPS="tmp var/tmp var/log var/run"
MY_MOUNTS=""
unset PS1
# Helper functions
die() {
echo " $1"
exit 1
}
safe_mount() {
mkdir -p "$MNT_PATH""$2"
if [ "$3" ]; then
OPTION=" $3 "
else
OPTION=""
fi
if [ -z "`mount | grep " $MNT_PATH$2 "`" ]; then
mount $OPTION "$1" "$MNT_PATH$2" || die "Can't mount $2!!!"
fi
MY_MOUNTS="$MNT_PATH$2 $MY_MOUNTS"
}
# Real work
[ "`whoami || echo root`" = "root" ] || die "You must be root first!"
LOOP_ARG=""
[ "$LOOP" = "no" ] || LOOP_ARG=" -o loop "
safe_mount $DEVICE "" "$LOOP_ARG -t ext4 "
for i in $BINDS; do
safe_mount "/$i" "/$i" " -o bind "
done
if [ -d /Removable ]; then
for i in /Removable/*; do
[ -d "$i" ] && safe_mount $i /mnt$i " -o bind "
done
fi
for i in $ANDROID_BINDS; do
safe_mount $i /mnt/android$i " -o bind "
done
for i in $TMPS; do
safe_mount none /$i " -t tmpfs "
done
mount -o remount,ro "$MNT_PATH"
chroot "$MNT_PATH" /sbin/fsck.ext2 -y "$DEVICE"
mount -o remount,rw "$MNT_PATH"
# Tweak configuration of the chroot during first start
#if [ \! -f "$MNT_PATH"/etc/profile.d/tweak.sh ]; then
#mkdir -p "$MNT_PATH"/home/opensuse
echo 'nameserver 8.8.8.8' > "$MNT_PATH"/etc/resolv.conf
#echo 'net:x:3003:root,opensuse' >> "$MNT_PATH"/etc/group
#echo 'opensuse:x:1000:100::/home/opensuse:/bin/bash' >> "$MNT_PATH"/etc/passwd
#echo 'opensuse:$1$joWqOQdr$YsapocP32UtdiR3PKBXVM1:15395:0:::::' \
# >> "$MNT_PATH"/etc/shadow
#sed -i 's|^root:.*|root:$1$joWqOQdr$YsapocP32UtdiR3PKBXVM1:15395:0:::::|' \
# "$MNT_PATH"/etc/shadow
#echo '#!/bin/sh
#export TERM=linux
#export LANG="en_US.utf-8"
#export EDITOR="busybox vi"
#alias vi="busybox vi"
#precmd() { :; }
#if [ "`whoami`" = root ]; then
# export HOME=/root
# export USER=root
# hostname -F /etc/HOSTNAME
#fi
#if [ -z "$CHROOTED" ]; then
# export CHROOTED=yes
# export HOME="/home/opensuse"
# export USER="opensuse"
# su opensuse
#fi
#' > "$MNT_PATH"/etc/profile.d/tweak.sh
#fi
export PATH="/bin:/sbin:/usr/bin:/usr/sbin:/system/xbin:/system/bin"
# Chroot
chroot "$MNT_PATH" /bin/bash
#chroot "$MNT_PATH" /root/init.sh
# Cleanup
echo "Umount everything"
for i in $MY_MOUNTS; do
umount -l $i
done
Step 4:
Chmod +x the script and run it as root.
Code:
su
#chmod +x scriptname.sh
sh scriptname.sh
The script will mount the ext partition of your (micro)sd card in /sdcard/arch and will chroot into it. It also does other really nice things, such as mounting your android partitions to /mnt so you can access them from within your arch environment. I have disabled some lines that are used to set up a some environment variables, but you should still be able to get a fully functional command-line environment and you can enable them and modify them as you want.
Step 5:
The rest is completely up to you, now you have arch running in your transformer. But what!? You need X?! really???? Ok, so lets create a vnc server so we can remote into it.
Your network connection should work, so the first thing to do is an update
Code:
#pacman -Syu
Now install xorg
Code:
#pacman -S xorg-server xorg-xinit xorg-twm xorg-xclock xterm
Now install a vncserver
Code:
#pacman -S tightvnc
And now this is the tricky part(And I spent a lot of time in this).
I grabbed this script from the UbuntuInstaller post. This is the script they use for setting a resolution at each boot. What I did was to remove the resolution prompt and fix the resolution to 1280x752(fullscreen) and remove some ubuntu stuff. I also added an export for HOME and USER that will allow you to run 'vncserver' as root.
Code:
#!/bin/bash
#############################################
# Asks User to screen size and saves as REZ #
#############################################
#echo "Now enter the screen size you want in pixels (e.g. 800x480), followed by [ENTER]:"
#read REZ
###########################################
# Tidy up previous LXDE and DBUS sessions #
###########################################
#rm /tmp/.X* > /dev/null 2>&1
#rm /tmp/.X11-unix/X* > /dev/null 2>&1
#rm /root/.vnc/localhost* > /dev/null 2>&1
#rm /var/run/dbus/pid > /dev/null 2>&1
############################################################
# enable workaround for upstart dependent installs #
# in chroot'd environment. this allows certain packages #
# that use upstart start/stop to not fail on install. #
# this means they will have to be launched manually though #
############################################################
#dpkg-divert --local --rename --add /sbin/initctl > /dev/null 2>&1
#ln -s /bin/true /sbin/initctl > /dev/null 2>&1
###############################################
# start vnc server with given resolution and #
# DBUS server, (and optionally an SSH server) #
###############################################
export HOME="/root/"
export USER="root"
vncserver :0 -geometry 1280x752
dbus-daemon --system --fork > /dev/null 2>&1
/etc/rc.d/sshd start
#echo
#echo "If you see the message 'New 'X' Desktop is localhost:0' then you are ready to VNC into your ubuntu OS.."
#echo
#echo "If VNC'ing from a different machine on the same network as the android device use the 1st address below:"
##########################################
# Output IP address of android device #
##########################################
ifconfig | grep "inet addr"
#echo
#echo "If using androidVNC, change the 'Color Format' setting to 24-bit colour, and once you've VNC'd in, change the 'input mode' to touchpad (in settings)"
#echo
#echo "To shut down the VNC server and exit the ubuntu environment, just enter 'exit' at this terminal - and WAIT for all shutdown routines to finish!"
#echo
###############################################################
# Spawn and interactive shell - this effectively halts script #
# execution until the spawning shell is exited (i.e. you want #
# to shut down vncserver and exit the ubuntu environment) #
###############################################################
/bin/bash -i
#########################################
# Disable upstart workaround and #
# kill VNC server (and optionally SSH) #
# Rename used xstartup to its first file#
#########################################
vncserver -kill :0
/etc/rc.d/sshd stop
Place this script in /root/, give it the name 'init.sh' and make sure it is executable(chmod +x). Now in the previous script comment the line:
Code:
chroot "$MNT_PATH" /bin/bash
and uncomment the line
Code:
chroot "$MNT_PATH" /root/init.sh
Step 6:
Now you should be able to start a vncserver with twm as your window manager and a xterm.
You can now go to
https://wiki.archlinux.org/index.php/Desktop_Environment
or
https://wiki.archlinux.org/index.php/Window_Manager
and set up the desktop environment that you like the most.
Remember that you need to set up the graphical environment to start manually and not at boot. In a normal environment you would usually use 'startx' which will read the .xinitrc file and run the programs from there. In our case put everything that needs to go into .xinitrc into ~/.vnc/xstartup. An example of my ~/.vnc/xstartup
Code:
#!/bin/bash
xrdb $HOME/.Xresources
exec startfluxblox
This will start an empty fluxbox window manager.

[MOD][GUIDE]tweak collections for build.prop/init.d

1 i DIDNT made this all tweaks ... Credit goes to their Developers...
I am not responsible for your bricked phone/sd if u pointed on me i will laugh at u
Forever king Tweaks....​
Build.prop tweaks​
1 VM Heapsize; higher the RAM
Code:
dalvik.vm.heapsize=48m
2 Good JPG quality
Code:
ro.media.enc.jpeg.quality=100
3 Render UI with GPU
Code:
debug.sf.hw=1
4 Best Scrolling
Code:
windowsmgr.max_events_per_sec=150
5 Decrease dialing out delay
Code:
ro.telephony.call_ring.delay=0
6 battery Saving
Code:
wifi.supplicant_scan_interval=180
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
7 Disable debugging notify icon on statusbar
Code:
persist.adb.notify=0
8 Increase touch responsiveness
Code:
debug.performance.tuning=1
video.accelerate.hw=1
9 Awesome photo and video recording quality
Code:
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
10 Network tweaks
Code:
Code:
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
11 Internet fast tweaks
Code:
net.tcp.buffersize.default=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.wifi=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.umts=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.gprs=6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.edge=6144,87380,524288,6144,16384,262144
net.tcp.buffersize.hspa=6144,87380,524288,6144,16384,262144
net.tcp.buffersize.lte=524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.hsdpa=6144,87380,1048576,6144,87380,1048576
net.tcp.buffersize.evdo_b=6144,87380,1048576,6144,87380,1048576
12 Fix some application issues (FC)
ro.kernel.android.checkjni=0
13 Phone will not wake up from hitting the volume rocker
Code:
ro.config.hwfeature_wakeupkey=0
14 Disable boot animation for faster boot
Code:
debug.sf.nobootanimation=1
15 faster streaming
Code:
media.stagefright.enable-meta=true
media.stagefright.enable-record=false
16 Miscellaneous Tweaks for performance
Code:
ro.config.hw_menu_unlockscreen=false
persist.sys.use_dithering=0
persist.sys.purgeable_assets=1
dalvik.vm.dexopt-flags=m=y
ro.mot.eri.losalert.delay=1000
17 Use Google DNS
Code:
net.ppp0.dns1=8.8.8.8
net.ppp0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
Init.d tweaks​
(needs ROM with init.d access and busybox, open empty file, insert header "#!/system/bin/sh" and put these there, save in /system/etc/init.d and name it something like tweak1)
1 strict minfree handler tweak
Code:
echo "2048,3072,6144,15360,17920,20480" > /sys/module/lowmemorykiller/parameters/minfree
2 internet speed hack tweaks
Code:
echo "0" > /proc/sys/net/ipv4/tcp_timestamps;
echo "1" > /proc/sys/net/ipv4/tcp_tw_reuse;
echo "1" > /proc/sys/net/ipv4/tcp_sack;
echo "1" > /proc/sys/net/ipv4/tcp_tw_recycle;
echo "1" > /proc/sys/net/ipv4/tcp_window_scaling;
echo "5" > /proc/sys/net/ipv4/tcp_keepalive_probes;
echo "30" > /proc/sys/net/ipv4/tcp_keepalive_intvl;
echo "30" > /proc/sys/net/ipv4/tcp_fin_timeout;
echo "404480" > /proc/sys/net/core/wmem_max;
echo "404480" > /proc/sys/net/core/rmem_max;
echo "256960" > /proc/sys/net/core/rmem_default;
echo "256960" > /proc/sys/net/core/wmem_default;
echo "4096,16384,404480" > /proc/sys/net/ipv4/tcp_wmem;
echo "4096,87380,404480" > /proc/sys/net/ipv4/tcp_rmem;
3 kernel tweaks
Code:
echo "8" > /proc/sys/vm/page-cluster;
echo "64000" > /proc/sys/kernel/msgmni;
echo "64000" > /proc/sys/kernel/msgmax;
echo "10" > /proc/sys/fs/lease-break-time;
echo "500,512000,64,2048" > /proc/sys/kernel/sem;
4 vm management tweaks
Code:
echo "4096" > /proc/sys/vm/min_free_kbytes
echo "0" > /proc/sys/vm/oom_kill_allocating_task;
echo "0" > /proc/sys/vm/panic_on_oom;
echo "0" > /proc/sys/vm/laptop_mode;
echo "0" > /proc/sys/vm/swappiness
echo "50" > /proc/sys/vm/vfs_cache_pressure
echo "90" > /proc/sys/vm/dirty_ratio
echo "70" > /proc/sys/vm/dirty_background_ratio
5 battery tweaks
Code:
echo "500" > /proc/sys/vm/dirty_expire_centisecs
echo "1000" > /proc/sys/vm/dirty_writeback_centisecs
6 removes journalism
Code:
tune2fs -o journal_data_writeback /block/path/to/system
tune2fs -O ^has_journal /block/path/to/system
tune2fs -o journal_data_writeback /block/path/to/cache
tune2fs -O ^has_journal /block/path/to/cache
tune2fs -o journal_data_writeback /block/path/to/data
tune2fs -O ^has_journal /block/path/to/data
7 increases cache size and increases speed
Code:
LOOP=`ls -d /sys/block/loop*`;
RAM=`ls -d /sys/block/ram*`;
MMC=`ls -d /sys/block/mmc*`;
for j in $LOOP $RAM
do
echo "0" > $j/queue/rotational;
echo "2048" > $j/queue/read_ahead_kb;
done
8 SD card speed tweak
Code:
echo "2048" > /sys/devices/virtual/bdi/179:0/read_ahead_kb;
9 Defrags database files
Code:
for i in \
`find /data -iname "*.db"`
do \
sqlite3 $i 'VACUUM;';
done
10 Ondemand governor
Code:
SAMPLING_RATE=$(busybox expr `cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_transition_latency` \* 750 / 1000)
echo 95 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo $SAMPLING_RATE > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
11 Governor Best: Minmax , SavagedZen , Smoothass , Smartass, Interactive
Code:
echo "governor-name-here" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
12 Move dalvik-cache to cache partition
Code:
CACHESIZE=$(df -k /cache | tail -n1 | tr -s ' ' | cut -d ' ' -f2)
if [ $CACHESIZE -gt 80000 ]
then
echo "Large cache detected, moving dalvik-cache to /cache"
if [ ! -d /cache/dalvik-cache ]
then
busybox rm -rf /cache/dalvik-cache /data/dalvik-cache
mkdir /cache/dalvik-cache /data/dalvik-cache
fi
busybox chown 1000:1000 /cache/dalvik-cache
busybox chmod 0771 /cache/dalvik-cache
# bind mount dalvik-cache so we can still boot without the sdcard
busybox mount -o bind /cache/dalvik-cache /data/dalvik-cache
busybox chown 1000:1000 /data/dalvik-cache
busybox chmod 0771 /data/dalvik-cache
else
echo "Small cache detected, dalvik-cache will remain on /data"
fi
13 Disable normalize sleeper
Code:
mount -t debugfs none /sys/kernel/debug
echo NO_NORMALIZED_SLEEPER > /sys/kernel/debug/sched_features
Other tweaks (not build.prop,init.d)​
1 v6 supercharger
Code:
http://forum.xda-developers.com/attachment.php?attachmentid=591730&d=1305000576
Credit- zeppelinrox
2 Use CyanogenMOD's APN list file (fully , for every operator)
Its in system>etc
3 Use uot kitchen for Theming your rom
Code:
http://uot.dakra.lt/
4 Never use Task killer............
please hit thanks and comment if you like this guide....if using in Rom proper credits to this guide!

Tizen

As tizen source is available now I wondered if anyone has taken a look at it yet.
I prepared my machine to start building it and test it.
Will publish updates in this thread.
Sent from my GT-I9300 using xda premium

Another mobile OS. Like there isnt enough already.

Subscribe
Tapatalk 2-vel küldve az én GT-I9300-ről

As far as I have read the new phone with Tizen which Samsung will release (i9500) uses the i9300 modem.
Looking at the structure, used kernel etc now.
For building a kickstart file is used, it is looking like this:
Code:
# -*-mic2-options-*- -f loop [email protected]@-rs.tar.gz -*-mic2-options-*-
#
# Do not Edit! Generated by:
# kickstarter.py
#
lang en_US.UTF-8
keyboard us
timezone --utc America/Los_Angeles
# ROOT fs partition
#part / --size=800 --ondisk mmcblk0p --fstype=ext4 --label=platform
# Use larger partition for creation, and will be shrinked at last, workaround of libzypp bug
#part / --size=2000 --ondisk mmcblk0p --fstype=ext4 --label=platform
# DATA partition
#part /opt/ --size=1800 --ondisk mmcblk0p --fstype=ext4 --label=data
# ROOT fs partition
part / --size=1700 --ondisk mmcblk0p --fstype=ext4 --label=platform
# DATA partition
part /opt/ --size=3000 --ondisk mmcblk0p --fstype=ext4 --label=data
# UMS partition
part /opt/media/ --size=300 --ondisk mmcblk0p --fstype=vfat --label=ums
rootpw tizen
bootloader --timeout=0 --append="rootdelay=5"
desktop --autologinuser=root
user --name root --groups audio,video --password ''
repo --name=Tizen-main --baseurl=https://download.tizen.org/snapshots/trunk/common/@[email protected]/repos/main/armv7l/packages/ --save --ssl_verify=no
repo --name=Tizen-base --baseurl=https://download.tizen.org/snapshots/trunk/common/@[email protected]/repos/base/armv7l/packages/ --save --ssl_verify=no
%packages
@tizen-c210
@tizen-bootstrap
-glib2-static
-gettext-tools
-eglibc-utils
-imake
-giflib-utils
-brcm-gps-daemon
-insserv
%end
%prepackages
libgcc
eglibc
sqlite
zlib
libpython
libdlog
libcap
libattr
default-files-slp
busybox
python-base
libacl
glib2
tzdata-slp
vconf
libxml2
heynoti
openssl
shared-mime-info
libudev
security-server
dbus-libs
cert-svc
libsecurity-server-client
%end
%post
echo 'kickstart post script start'
if [ -d /etc/init.d ]; then
cp /etc/init.d/* /etc/rc.d/init.d/ -rdf
fi
rm -rf /etc/init.d*
ln -sf /etc/rc.d/init.d /etc/init.d
# Without this line the rpm don't get the architecture right.
echo -n 'armv7l-meego-linux' > /etc/rpm/platform
ssh-keygen -t rsa1 -f /etc/ssh/ssh_host_key -N ""
ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key -N ""
ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key -N ""
ail_initdb
/opt/apps/com.samsung.menu-screen/bin/menuscreen_initdb
cat > /usr/bin/press << EOF
#!/bin/sh
JUNK="SLP"
[ "\$1" ] && TIMEOUT="\$1" || TIMEOUT="1"
echo "Press return key to stop scripts"
read -t \$TIMEOUT JUNK
exit \$?
EOF
chmod +x /usr/bin/press
ln -s /opt/etc/X11/xkb /usr/share/X11
echo "UDEV_PERSISTENT_STORAGE=no" >> /etc/sysconfig/udev
rm -rf /usr/include
rm -rf /usr/share/man
rm -rf /usr/share/doc
MAJOR="2"
MINOR="0"
cat >/etc/info.ini <<EOF
[Version]
Major=$MAJOR;
Minor=$MINOR;
Build=TIZEN_`date +%Y%m%d`_1;
Order=;
[Build]
Date=`date +%Y.%m.%d`;
Time=`date +%H:%M:%S`;
EOF
ln -sf /etc/info.ini /opt/etc/info.ini
ln -sf /etc/info.ini /usr/etc/info.ini
mkdir -p /home/app
cp -a /etc/skel/.e /home/app/
chown -R 5000:5000 /home/app
chmod 0755 /home/app
chown -R 5000:5000 /opt/home/app
chmod 0755 /opt/home/app
cat > /usr/lib/systemd/system/usb-debug.service << EOF
[Unit]
Description=Start usb networking for debugging
ConditionPathExists=/sys/devices/platform/usb_mode/UsbMenuSel
[Service]
Type=oneshot
RemainAfterExit=yes
Environment=PATH=/bin:/sbin
ExecStart=/bin/bash -c 'echo 4 > /sys/devices/platform/usb_mode/UsbMenuSel'
ExecStart=/sbin/ifconfig usb0 192.168.129.3 netmask 255.255.255.0
ExecStop=/bin/bash -c 'echo 0 > /sys/devices/platform/usb_mode/UsbMenuSel'
#
# We now don't launch this USB mode hack by default. If you need that, run this:
# systemctl enable usb-debug.service
# or create a link manually like below:
# ln -s ../usb-debug.service /usr/lib/systemd/system/basic.target.wants/usb-debug.service
#
[Install]
WantedBy=basic.target
EOF
# required for the connman systemd service
cat > /etc/sysconfig/connman << EOF
OPTIONS="-W wext"
EOF
# required for the wpa_supplicant systemd service
cat > /etc/sysconfig/wpa_supplicant << EOF
OPTIONS="-Dwext"
EOF
ldconfig
rpm --rebuilddb
echo 'kickstart post script end'
%end
%post --nochroot
%end

News ?

It is nice Android to have competition but from what I saw on youtube Tizen is just android stuck at version 2.3. Is there anything new except that there will be no native apps?

gud to here that
now wating for ur good work

SM-T230NU - Generate .config used by a running a kernel

Is it possible to create a new kernel config file used by the running kernel for the SM-T230NU? If so, what are the steps to create one? The reason I am asking is I want to use the .config file to create a Kernel module. The module is LiME.ko and it is used to acquire the tablet's memory image which I use for forensic analysis. The challenge is that default Samsung Kernels/ROM's do not appear to come with a kernel .config file.
Your help is appreciated.
Thanks,

http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-T230
-> arch/arm/config
https://github.com/GalaxyTab4/andro...h/arm/configs/pxa1088_degaswifi_eur_defconfig
-> my GitHub
checking for ikconfig
->
Code:
#!/bin/sh
# ----------------------------------------------------------------------
# extract-ikconfig - Extract the .config file from a kernel image
#
# This will only work when the kernel was compiled with CONFIG_IKCONFIG.
#
# The obscure use of the "tr" filter is to work around older versions of
# "grep" that report the byte offset of the line instead of the pattern.
#
# (c) 2009,2010 **** Streefland <****@streefland.net>
# Licensed under the terms of the GNU General Public License.
# ----------------------------------------------------------------------
cf1='IKCFG_ST\037\213\010'
cf2='0123456789'
dump_config()
{
if pos=`tr "$cf1\n$cf2" "\n$cf2=" < "$1" | grep -abo "^$cf2"`
then
pos=${pos%%:*}
tail -c+$(($pos+8)) "$1" | zcat > $tmp1 2> /dev/null
if [ $? != 1 ]
then # exit status must be 0 or 2 (trailing garbage warning)
cat $tmp1
exit 0
fi
fi
}
try_decompress()
{
for pos in `tr "$1\n$2" "\n$2=" < "$img" | grep -abo "^$2"`
do
pos=${pos%%:*}
tail -c+$pos "$img" | $3 > $tmp2 2> /dev/null
dump_config $tmp2
done
}
# Check invocation:
me=${0##*/}
img=$1
if [ $# -ne 1 -o ! -s "$img" ]
then
echo "Usage: $me <kernel-image>" >&2
exit 2
fi
# Prepare temp files:
tmp1=/tmp/ikconfig$$.1
tmp2=/tmp/ikconfig$$.2
trap "rm -f $tmp1 $tmp2" 0
# Initial attempt for uncompressed images or objects:
dump_config "$img"
# That didn't work, so retry after decompression.
try_decompress '\037\213\010' xy gunzip
try_decompress '\3757zXZ\000' abcde unxz
try_decompress 'BZh' xy bunzip2
try_decompress '\135\0\0\0' xxx unlzma
try_decompress '\211\114\132' xy 'lzop -d'
try_decompress '\002\041\114\030' xyy 'lz4 -d -l'
# Bail out:
echo "$me: Cannot find kernel config." >&2
exit 1

Thank you for getting back to me. You have been very helpful. I have a related question. How do I install the kernel I downloaded from the opensource.samsung site to my SM-T230NU?
I have created a kernel .config file from the downloaded kernel from the link you provided and subsequently generated a zImage file but I do not know how to create the ramdisk and boot.img. I tried installing the kernel using AnyKernel and Heimdall but it fails. Can you provide guidance or a tutorial on how to do this? I would rather not install a ROM. Only the kernel.
I really appreciate the help.
sub77 said:
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-T230
-> arch/arm/config
https://github.com/GalaxyTab4/andro...h/arm/configs/pxa1088_degaswifi_eur_defconfig
-> my GitHub
checking for ikconfig
->
Code:
#!/bin/sh
# ----------------------------------------------------------------------
# extract-ikconfig - Extract the .config file from a kernel image
#
# This will only work when the kernel was compiled with CONFIG_IKCONFIG.
#
# The obscure use of the "tr" filter is to work around older versions of
# "grep" that report the byte offset of the line instead of the pattern.
#
# (c) 2009,2010 **** Streefland <****@streefland.net>
# Licensed under the terms of the GNU General Public License.
# ----------------------------------------------------------------------
cf1='IKCFG_ST\037\213\010'
cf2='0123456789'
dump_config()
{
if pos=`tr "$cf1\n$cf2" "\n$cf2=" < "$1" | grep -abo "^$cf2"`
then
pos=${pos%%:*}
tail -c+$(($pos+8)) "$1" | zcat > $tmp1 2> /dev/null
if [ $? != 1 ]
then # exit status must be 0 or 2 (trailing garbage warning)
cat $tmp1
exit 0
fi
fi
}
try_decompress()
{
for pos in `tr "$1\n$2" "\n$2=" < "$img" | grep -abo "^$2"`
do
pos=${pos%%:*}
tail -c+$pos "$img" | $3 > $tmp2 2> /dev/null
dump_config $tmp2
done
}
# Check invocation:
me=${0##*/}
img=$1
if [ $# -ne 1 -o ! -s "$img" ]
then
echo "Usage: $me <kernel-image>" >&2
exit 2
fi
# Prepare temp files:
tmp1=/tmp/ikconfig$$.1
tmp2=/tmp/ikconfig$$.2
trap "rm -f $tmp1 $tmp2" 0
# Initial attempt for uncompressed images or objects:
dump_config "$img"
# That didn't work, so retry after decompression.
try_decompress '\037\213\010' xy gunzip
try_decompress '\3757zXZ\000' abcde unxz
try_decompress 'BZh' xy bunzip2
try_decompress '\135\0\0\0' xxx unlzma
try_decompress '\211\114\132' xy 'lzop -d'
try_decompress '\002\041\114\030' xyy 'lz4 -d -l'
# Bail out:
echo "$me: Cannot find kernel config." >&2
exit 1
Click to expand...
Click to collapse

Dangerous Performance

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 @BitOBSessiOn OC Kernel @laufersteppenwolf 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 @BitOBSessiOn 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.

m0nt3s said:
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 @BitOBSessiOn OC Kernel, he 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
I know it's alot to copy and paste but this is the truest way to get the maximum performance.
To get your touch screen to respond as fast as you set your tablet navigate to
/system/usr/idc
and edit touch.idc which is 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 @BitOBSessiOn for inspiring me to learn.
Click to expand...
Click to collapse
The touchscreen improvement is that adb shell or what not good with scripts sorry

skooter32 said:
The touchscreen improvement is that adb shell or what not good with scripts sorry
Click to expand...
Click to collapse
Learn to quote.

edisso10018 said:
Learn to quote.
Click to expand...
Click to collapse
Eh? I ask a simple question and get stupidityin return cheers oh u do realise that this is xda ?

@skooter32 For the toucscreen I use fx file explorer, it has a built in text editor and it has easy root navigation

I attached some files to the original post, the boot img is userdebug with true SU, although I would reflash supersu-sr-1 after installing the new boot.img

m0nt3s said:
@skooter32 For the toucscreen I use fx file explorer, it has a built in text editor and it has easy root navigation
Click to expand...
Click to collapse
So am adding this to build.prop? Because a cant find it on build.prop
---------- Post added at 11:22 PM ---------- Previous post was at 11:20 PM ----------
skooter32 said:
So am adding this to build.prop? Because a cant find it on build.prop
Click to expand...
Click to collapse
Edit found it

skooter32 said:
So am adding this to build.prop? Because a cant find it on build.prop
---------- Post added at 11:22 PM ---------- Previous post was at 11:20 PM ----------
Edit found it
Click to expand...
Click to collapse
Sadly editing the build prop doesn't change touchscreen sensitivity. Install the apk I've attached, grant it root permission, then from in the apk, go to system(root) system, then usr, then idc, once your in the idc folder you'll see touch.idc which you need to open with fx text editor and delete the # infront of
touch.pressure.calibration = amplitude
touch.pressure.source = default
touch.pressure.scale = 0.01
save your changes and then back out to the same idc folder and editsensor00fn11.idc the same by deleting the the #
you only have to do this once, since I've already changed it i might be mistaken but the stock sensitivty is #0.0125, change it to 0.001 and save in both

proof of concept
@boswelja, @BitOBSessiOn, @Steel01,[/MENTION], @Bogdacutu,
So I need some help and you guys are the best of the best. The problem I'm having is that I've gutted the OTA 4.3 rom so much that when I try to build the replicate of my rom it errors out after booting with "setup wizard has failed" and just loops after booting. If I were to give you a TWRP backup of my current rom with settings do you think you could get it to work? I'm currently full f2fs, with a probably more than i should of gutted OTA 4.3. This is my lowest benchmark that I'm confident with your help we could make it universal. any input is apprciated.

m0nt3s said:
Sadly editing the build prop doesn't change touchscreen sensitivity. Install the apk I've attached, grant it root permission, then from in the apk, go to system(root) system, then usr, then idc, once your in the idc folder you'll see touch.idc which you need to open with fx text editor and delete the # infront of
touch.pressure.calibration = amplitude
touch.pressure.source = default
touch.pressure.scale = 0.01
save your changes and then back out to the same idc folder and editsensor00fn11.idc the same by deleting the the #
you only have to do this once, since I've already changed it i might be mistaken but the stock sensitivty is #0.0125, change it to 0.001 and save in both
Click to expand...
Click to collapse
Sorted????

m0nt3s said:
@boswelja, @BitOBSessiOn, @Steel01,[/MENTION], @Bogdacutu,
So I need some help and you guys are the best of the best. The problem I'm having is that I've gutted the OTA 4.3 rom so much that when I try to build the replicate of my rom it errors out after booting with "setup wizard has failed" and just loops after booting. If I were to give you a TWRP backup of my current rom with settings do you think you could get it to work? I'm currently full f2fs, with a probably more than i should of gutted OTA 4.3. This is my lowest benchmark that I'm confident with your help we could make it universal. any input is apprciated.
Click to expand...
Click to collapse
Err.. the best I could do is get a logcat and tell u what's causing the problem

m0nt3s said:
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 @BitOBSessiOn OC Kernel, he 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 @BitOBSessiOn 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.
Click to expand...
Click to collapse
Although I was working at the beginning in a OC kernel, all latest OC work must be thanked to @laufersteppenwolf . Basically I've only merged his work in latest BitO-KX series.
Correct merits should be put in OP, please.
Thx!

Touch tweaks; latency or sensitivity?
Thanks for these details. I understand the objective of these tweaks are for hardware performance, but I'd like to ask if these modifications to the touch IDC improve touch latency on the Shield? I recently purchased one when stock became available and find that it's touch response is significantly slower than my Nexus 9 (same K1, but dual core 64-bit) when not plugged into any power source (so far my power sources introduce MORE latency...). I'd like to identify any measures I can take to reduce touch latency if possible.
This is apparent in any scrolling app, using debug 'show touches', or testing apps such as Yet Another Multi Touch Tester, where any visual indication lags behind the finger significantly when dragging and swiping. It also results in diminished response in rhythm games which already have enough trouble with the state of Android audio latency.
This tweak looks like it adjusts touch sensitivity (finger distance from screen before registering a touch), which I don't have any problem with. Can anyone using these tweaks confirm or deny if they improve latency as well?

@Crayphish
Try using my modified sysctl, it sounds like you're using the stock one which limits so many different factors that I wouldn't really know where to start troubleshooting, I would start in ADB SHELL change these parameters start by replacing your sysctl,the easiest way to change all the new parameters would be with 3C toolbox .
eglSwapInterval — specifies the minimum number of video frame periods per buffer swap for the window associated with the current context.
The interval takes effect when eglSwapBuffers is first called subsequent to the eglSwapInterval call.
The interval specified by the function applies to the draw surface bound to the context that is current on the calling thread.
If interval is set to a value of 0, buffer swaps are not synchronized to a video frame, and the swap happens as soon as the render is complete. interval is silently clamped to minimum and maximum implementation dependent valuesbefore being stored; these values are defined by EGLConfig attributes EGL_MIN_SWAP_INTERVAL and EGL_MAX_SWAP_INTERVAL respectively.
fs.inotify.max_queued_events = 32768
fs.inotify.max_user_instances = 256
EGL_MIN_SWAP_INTERVAL = 0
EGL_MAX_SWAP_INTERVAL = 10
add these lines to your build prop
ENFORCE_PROCESS_LIMIT=false
MAX_SERVICE_INACTIVITY=false
MIN_HIDDEN_APPS=false
MAX_HIDDEN_APPS=false
CONTENT_APP_IDLE_OFFSET=false
EMPTY_APP_IDLE_OFFSET=false
MAX_ACTIVITIES=false
ACTIVITY_INACTIVITY_RESET_TIME=false
MAX_RECENT_TASKS=false
MIN_RECENT_TASKS=false
APP_SWITCH_DELAY_TIME=false
MAX_PROCESSES=false
PROC_START_TIMEOUT=false
CPU_MIN_CHECK_DURATION=false
GC_TIMEOUT=false
SERVICE_TIMEOUT=false
MIN_CRASH_INTERVAL=false
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
ro.zygote.disable_gl_preload=false
windowsmgr.max_events_per_sec=180
debug.sf.hw=1
debug.composition.type=gpu
persist.sys.ui.hw=1
persist.sys.composition.type=gpu
debug.performance.tuning=1
touch.pressure.scale=0.001
view.touch_slop=4
ro.min_pointer_dur=0.001
touch.size.calibration=geometric
touch.size.scale=100
touch.size.bias=70
touch.pressure.calibration=amplitude
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
ro.ril.disable.power.collapse=0
dalvik.vm.heaptargetutilization=0.75
sys.usb.config=mtp,adb
dalvik.vm.dexopt-flags=m=y,v=n
ro.debuggable=1
ro.kernel.android.checkjni=0
ro.secure=0
profiler.force_disable_ulog=1
profiler.force_disable_err_rpt=1
debug.egl.hw=1
ro.config.disable.hw_accel=false
video.accelerate.hw=1
ADB SHELL This and see is you notice a difference.
I noticed a huge difference after maxing out the emc memory and the 3d.emc
cat /sys/kernel/debug/clock/emc/possible_rates
cat /sys/kernel/debug/clock/3d.emc/possible_rates
cat /sys/kernel/debug/clock/emc/max > /sys/kernel/debug/clock/override.emc/rate
echo 1 > /sys/kernel/debug/clock/override.emc/state
echo "EMC: `cat /sys/kernel/debug/clock/emc/rate`"
cat /sys/kernel/debug/clock/3d.emc/max > /sys/kernel/debug/clock/3d.emc/rate
echo 1 > /sys/kernel/debug/clock/override.3d.emc/state
echo "3d.EMC: `cat /sys/kernel/debug/clock/3d.emc/rate`"
it's going to be a bit of a troubleshooting process but try these tweaks and let me know if anything changes for better or worse. Also I would make a Full TWRP Backup before.

@m0nt3s
Thanks for the help. I've just put TWRP on the device and setup @BitOBSessiOn 's experimental F2FS kernel with good success so far. I will try your sysctl and build.prop changes as well and see if I can get any improvements. :good:

Kernel auditor is also a very useful app that I think is a must have

Crayphish said:
@m0nt3s
Thanks for the help. I've just put TWRP on the device and setup @BitOBSessiOn 's experimental F2FS kernel with good success so far. I will try your sysctl and build.prop changes as well and see if I can get any improvements. :good:
Click to expand...
Click to collapse
Can you or anyone else point me in a direction for everything to make the sensitivity consistent?
I literally bought the Shield K1 tablet to play a rhythm game (Love Live, specifically) and whenever I'm playing a very difficult song, I easily drop my combo due to touches not being input. I'm certain there's some way of fixing this...
What rom should I use, should I change the kernel, what else should I try? I don't have any external cooling sources and I'm pretty new/bad at this stuff overall.
Not even sure what to do with a sysctl.
I've tried a bunch of things, and so far my tablet feels worse than when I started from the stock rom with just root.

@KariArisu
Go to settings, about tablet, and tap on Model number six times to open the built in touch calibrator.
The biggest performance impactor would be Google. Go to settings accounts, google, and uncheck Sync and every other google feature. if you do need to use a feature you can always do it manually or turn the feature back on when you need it, googles background sync eats %23 - %29 memory when activated. if you're not using cloudprint turn that off under settings printing, you can also go to about tablet, tap on build number 7 times, enabled developer options go down to the drawing section, change Window, Transition, and Animatorr scale to .5 or .25 if you have gravity box installed. also in about tablet uncheck help nvidia improve shield, ot's another background sync app but Nvidia is sneaky in that in the build prop they still have this enabled stock
ro.nvidia.collect_data_enabled=true, use FX editor, navigate to system(root) system, click the little lock to unlock or remount as r/w and then edit your build prop lines
ro.nvidia.collect_data_enabled=false
ro.input.noresample=0
you can also go back to settings, developer options, hardware accelerated rendering, check force use of GPU for 2d drawing, disable HW overlays, and then go maximize system memory scroll down to the bottom of developer options, apps, background process limit and change it to either 1 or none.

Did all of this now, and it's better but still not great. Whenever I have to rapidly tap for long periods of time, it will eventually cause taps to lag behind or just not happen at all. It's really weird.

KariArisu said:
Did all of this now, and it's better but still not great. Whenever I have to rapidly tap for long periods of time, it will eventually cause taps to lag behind or just not happen at all. It's really weird.
Click to expand...
Click to collapse
Sounds like it's time to flash Bit's OC kernel, after you flash go on the playstore and get Kernel Adiutor (ROOT)
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en
once you do, let me know and we can start tweaking some things