Related
Hello, in other forum, " dervari " resolved the tethering A101 with BlackBerry:
in /system/etc/ppp/peers/tether, change novj for #novj
in /system/bin/tether_start_dun.sh., change if [$# -eq 4 ] for if [ $# -eq 4 ]
but that was with firmware 2.3.26... now, the new firmware 2.3.81 changed these scripts..
my questions:
.- This changes makes tethering A101 with BlackBerry ?
.- Not necesary makes more changes in scripts ?
new /system/etc/ppp/peers/tether in 2.3.81:
#debug
# connection
crtscts
hide-password
nodetach
# peer parameters
noauth
# most gprs phones don't reply to lcp echo
lcp-echo-interval 0
lcp-echo-failure 0
# dns, routing
ipcp-accept-remote
ipcp-accept-local
defaultroute
#replacedefaultroute # not currently supported by our pppd
noipdefault
usepeerdns
# avoid compression
# novj is now an option
novjccomp
noccp
nobsdcomp
nopcomp
noaccomp
# connect scripts
connect '/system/xbin/chat -v -t3 -f /data/tether_start'
disconnect '/system/xbin/chat -v -t3 -f /etc/chatscripts/tether_stop'
new /system/bin/tether_start_dun.sh in 2.3.81:
#!/bin/sh
# $1 is the mac address of the phone
# $2 is the channel
# $3 is the user (not a mandatory argument)
# $4 is the password (not a mandatory argument)
# $5 is the novj option
MAC=$1
CHANNEL=$2
USER=$3
PWD=$4
NOVJ=$5
if [ "$USER" = "" ]
then
/system/xbin/dund --connect $MAC --channel $CHANNEL --pppd /system/bin/pppd /dev/rfcomm0 115200 mru 1280 mtu 1280 $NOVJ call tether
else
/system/xbin/dund --connect $MAC --channel $CHANNEL --pppd /system/bin/pppd /dev/rfcomm0 115200 mru 1280 mtu 1280 $NOVJ name $USER password $PWD call tether
fi
Starting this thread to share experiences with any good sysctl settings for the flyer.
What is sysctl?
Sysctl is an interface for examining and dynamically changing parameters in the Linux operating systems.
What is sysctl.conf?
sysctl.conf is a simple file containing sysctl values to be read in and set by sysctl command. The syntax is simply as follows:
# comment
; comment
token = value
Note that blank lines are ignored, and whitespace before and after a token or value is ignored, although a value can contain whitespace within. Lines which begin with a # or ; are considered comments and ignored.
Where is sysctl.conf located?
sysctl.conf is located in /system/etc/ directory on your tablet.
Changing sysctl values
You could pull the file /system/etc/sysctl.conf from your phone, edit the data, push the modified file back to your phone.
However, it is easier (provided that you have init.d) to use a script in /system/etc/init.d/ which is ran at boot time to change the values:
Example via init.d script
You could have a file, e.g. /system/etc/init.d/84sysctl
#!/system/bin/sh
sysctl -w net.ipv4.tcp_fin_timeout=30
(this would change socket FIN timing)
Advantage of doing like this is that you don't have to modify your original /system/etc/sysctl.conf file.
So far I have been using:
sysctl -w vm.dirty_ratio=90
sysctl -w vm.dirty_background_ratio=55
sysctl -w vm.vfs_cache_pressure=10
sysctl -w vm.swappiness=0
sysctl -w vm.panic_on_oom=1
sysctl -w net.core.wmem_max=1048576
sysctl -w net.core.rmem_max=1048576
There are two import settings which control the kernel behaviour with regard to dirty pages in memory. They are:
vm.dirty_background_ratio
vm.dirty_ratio
The first of the two (vm.dirty_background_ratio) defines the percentage of memory that can become dirty before a background flushing of the pages to disk starts. Until this percentage is reached no pages are flushed to disk. However when the flushing starts, then it's done in the background without disrupting any of the running processes in the foreground.
Now the second of the two parameters (vm.dirty_ratio) defines the percentage of memory which can be occupied by dirty pages before a forced flush starts. If the percentage of dirty pages reaches this number, then all processes become synchronous, they are not allowed to continue until the io operation they have requested is actually performed and the data is on disk. In case of high performance I/O machines, this causes a problem as the data caching is cut away and all of the processes doing I/O (the important ones in dCache pool) become blocked to wait for io. This will cause a big number of hanging processes, which leads to high load, which leads to unstable system and crappy performance.
vm.swappiness=0
We don't swap ... so no need.
sysctl -w net.core.wmem_max=1048576
sysctl -w net.core.rmem_max=1048576
Increase the max size of TCP/IP send/receive buffers.
sysctl -w vm.panic_on_oom=1
This enables or disables panic on out-of-memory feature. If this is set to 1, the kernel panics when out-of-memory happens. If this is set to 0, the kernel will kill some rogue process, by calling oom_kill(). Usually, oom_killer can kill rogue processes and system will survive. If you want to panic the system rather than killing rogue processes, set this to 1.
vm.vfs_cache_pressure=10
This is more interesting. File system cache (dentry/inode) is really more important than the block cache above, so we really want the kernel to use up much of the RAM for them. The default value is 100, and what you want to do is lower that value to tell the kernel to favor the file system cache and not drop them aggressively.
i like!!! but how would you change a build.prop property? cause at first i thought sysctl was for changing build prop stuff =X
Hello,
While i am not new to this forum, due to some reasons I had to create a new user for myself. I am currently using Samsung Galaxy Tab Plus P6200.
From the very beginning, I am frustrated at how android decides to kill my apps on my own. I majorly use web browser with 6-7 tabs open and as soon as I switch applications, the browser gets killed and all tabs are lost.
Thus i wanted to take the matter in my own hands as there is no stable CM for this tablet.
While going through init.rc, I found a block of property setter, which i think are used to kill apps. This is:
Code:
# Define the oom_adj values for the classes of processes that can be
# killed by the kernel. These are used in ActivityManagerService.
setprop ro.FOREGROUND_APP_ADJ 0
setprop ro.VISIBLE_APP_ADJ 1
setprop ro.PERCEPTIBLE_APP_ADJ 2
setprop ro.HEAVY_WEIGHT_APP_ADJ 3
setprop ro.SECONDARY_SERVER_ADJ 4
setprop ro.BACKUP_APP_ADJ 5
setprop ro.HOME_APP_ADJ 6
setprop ro.HIDDEN_APP_MIN_ADJ 7
setprop ro.EMPTY_APP_ADJ 15
# Define the memory thresholds at which the above process classes will
# be killed. These numbers are in pages (4k).
# These are currently tuned for tablets with approx 1GB RAM.
setprop ro.FOREGROUND_APP_MEM 8192
setprop ro.VISIBLE_APP_MEM 10240
setprop ro.PERCEPTIBLE_APP_MEM 12288
setprop ro.HEAVY_WEIGHT_APP_MEM 12288
setprop ro.SECONDARY_SERVER_MEM 14336
setprop ro.BACKUP_APP_MEM 14336
setprop ro.HOME_APP_MEM 14336
setprop ro.HIDDEN_APP_MEM 16384
setprop ro.EMPTY_APP_MEM 20480
# Old values for phones. Should probably be adjusted up for the next
# phone version.
#setprop ro.FOREGROUND_APP_MEM 2048
#setprop ro.VISIBLE_APP_MEM 3072
#setprop ro.PERCEPTIBLE_APP_MEM 4096
#setprop ro.HEAVY_WEIGHT_APP_MEM 4096
#setprop ro.SECONDARY_SERVER_MEM 6144
#setprop ro.BACKUP_APP_MEM 6144
#setprop ro.HOME_APP_MEM 6144
#setprop ro.HIDDEN_APP_MEM 7168
#setprop ro.EMPTY_APP_MEM 8192
# Write value must be consistent with the above properties.
# Note that the driver only supports 6 slots, so we have combined some of
# the classes into the same memory level; the associated processes of higher
# classes will still be killed first.
write /sys/module/lowmemorykiller/parameters/adj 0,1,2,4,7,15
write /proc/sys/vm/overcommit_memory 1
write /proc/sys/vm/min_free_order_shift 4
write /sys/module/lowmemorykiller/parameters/minfree 8192,10240,12288,14336,16384,20480
So i went forward and changed these to suit myself, for once rebooted, my changes were lost! Searching more, I found that the flash in device is partitioned with hidden partitions as boot and recovery where the master files are placed ( init.rc), which on reboot are copied to device. So now I want to change the content of boot partition.
The device does not have /proc/mtd but mmcdevice is split in many parts. I am unable to recognize which one is boot partition.
So my question is can I use the official image of Samsung (gz file), unzip it, extract the boot partition, edit its content , repack it and flash it via odin?
Also if any simple workaround to stop android killing my apps is known, please do let me know.
init.rc
You need to do a couple things before editing init.rc
1) Unpack your boot.img
2)Find init.rc in ramdisk folder
3) Aha now edit init.rc
4) repack boot.img
5) make a lil flashable zip to load up new boot.img
My guess is you are trying to edit init.rc in /system; problem is ramdisk will overwrite that 'copy' and so your changes are not persistent. Try editing on ramdisk and watch the magic unfold
As for a memory management, after you tweak init.rc, you can get your init.d scripts looked at first [which is as it should be] and include the script(s) there. This way your boot.img doesn't swell up like a balloon
Rob
I'm no expert, but..
Probably safer than editing your ramdisk is using init.d, sysinit or install_recovery.sh
/system/bin/sysinit & /system/etc/install_recovery.sh are normal shell scripts that run at boot
experiment to see which you prefer & if either get overwritten or removed
In the one that you choose, if you have busybox, insert
Code:
run_parts /system/etc/init.d
otherwise you're going to have to do something much more elaborate like (correct my syntax)
Code:
for F in (/system/etc/init.d/*)
do
if test -x $F
then
source $F > /dev/null 2>&1 &
fi
done
In /system/etc/init.d/ place something like 99my_memory_hack.sh containing your fixes
'setprop' works as you've listed above, but the 'write' command is specific to init.rc
for the single parameter commands use
Code:
echo [parameter] > /proc/[wherever]
for the multi parameter commands I'm not sure, it might work as above or you might need a 'for' loop & post them sequentially (correct my syntax)
Code:
for I in (parameters)
do
echo $I >> /proc/[wherever]
done
---------- Post added at 11:32 AM ---------- Previous post was at 11:14 AM ----------
For every 'setprop' you intend to use, use 'getprop' to find the current value - it might not be what's set in init.rc!
Also look in /system/build.prop & look on the market for 'build.prop editor'
Xposed appsettings and resident ur app. It's the easiest and fastest way.
Gesendet von meinem Xperia SP
After tweaking init.rc
As for a memory management, after you tweak init.rc, you can get your init.d scripts looked at first [which is as it should be] and include the script(s) there. This way your boot.img doesn't swell up like a balloon
Rob[/QUOTE]
Hi Rob, I found this very helpfull and edited the init.rc file in the boot.img. It worked magically - but just for a few days.
Looking into process statistic I found that there was barely free RAM - even after rebooting. Is it that what you ment with: "you can get your init.d scripts looked at first [which is as it should be] and include the script(s) there. This way your boot.img doesn't swell up like a balloon "
I have to admit, I don´t no what I would have to do with the init.d scripts, beside of the fact, that I did not found a file with that name in the firmware. Any help or advice would be very much appreciated.
Thanks
Michael
micbin said:
I have to admit, I don´t no what I would have to do with the init.d scripts, beside of the fact, that I did not found a file with that name in the firmware. Any help or advice would be very much appreciated.
Thanks
Michael
Click to expand...
Click to collapse
Init.d is a set of scripts that is executed during the initialisation phase of the phone. So, instead of increasing the size of the tiny boot image by adding a few more lines into init.rc, you can create a script and add it to the init.d folder.
As far as I know, init.d runs after init.rc has completed execution, but still much before Android boots, so you can use it to apply your memory management mods.
From your message above, I feel you haven't understood some things properly. Init.d is not a file but a folder which can contain many number of scripts which are executed one by one in alphabetical order at boot time. It is usually located at /system/etc/init.d or /etc/init.d.
In most of the phones this folder is absent by default because the stock kernel doesn't support init.d.
Refer to this to get init.d support on your phone without having to switch to a new kernel.
I've been collecting some tweaks and scripts and seems to me it's now time to share it. While some values in terms of optimization might be different from device to device, I've found these pretty consistent throughout many.
I didn't tested all of them, and i don't assume any risk!!! Use them at you own risk!!!
Some useful tips on how to use them at the end of the post
This thread will be updated when new/better things come out
Superuser, Busybox install/update
1. Easily install Busybox (YOU NEED ROOT FIRST)
Code:
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5qcnVtbXkuYnVzeWJveC5pbnN0YWxsZXIiXQ..
2. UPDATE SuperUser (root app)
Code:
http://goo.im/superuser/
Build.prop
(edit your /system/build.prop with a file manager with root access)
Careful for already existing settings. In this case, just change the values.
1. Force launcher into memory
Code:
ro.HOME_APP_ADJ=1
2. Raise JPG quality to 100%
Code:
ro.media.enc.jpeg.quality=100
3. VM Heapsize; higher the RAM, higher the hp can be
Code:
dalvik.vm.heapsize=96m
4. Render UI with GPU
Code:
debug.sf.hw=1
5. Decrease dialing out delay
Code:
ro.telephony.call_ring.delay=0
6. Helps scrolling responsiveness
Code:
windowsmgr.max_events_per_sec=150
7. Save battery
Code:
wifi.supplicant_scan_interval=180
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
8. Disable debugging notify icon on statusbar
Code:
persist.adb.notify=0
9. Increase overall touch responsiveness
Code:
debug.performance.tuning=1
video.accelerate.hw=1
10. Raise photo and video recording quality
Code:
ro.media.dec.jpeg.memcap=12000000
ro.media.enc.hprof.vid.bps=12000000
11. Signal (3G) tweaks
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
12. Net speed tweaks
Code:
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
13. Disable blackscreen issue after a call
Code:
ro.lge.proximity.delay=25
mot.proximity.delay=25
14. Fix some application issues
Code:
ro.kernel.android.checkjni=0
15. Phone will not wake up from hitting the volume rocker
Code:
ro.config.hwfeature_wakeupkey=0
16. Force button lights on when screen is on
Code:
ro.mot.buttonlight.timeout=0
17. Disable boot animation for faster boot
Code:
debug.sf.nobootanimation=1
18. Miscellaneous flags
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
19. Specifics to some LG devices
Code:
persist.service.pcsync.enable=0
persist.service.lgospd.enable=0
user.feature.flex=true
user.feature.lgdrm=false
user.feature.lgresource=false
user.feature.lgpoweroff=false
user.feature.ls_event=false
user.feature.ls_normal=false
user.feature.sui=false
Init.d
(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 77tweaks)
1. strict minfree handler tweak
Code:
echo "2048,3072,6144,15360,17920,20480" > /sys/module/lowmemorykiller/parameters/minfree
2. internet speed 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. 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
4. misc 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;
5. battery tweaks
Code:
echo "500" > /proc/sys/vm/dirty_expire_centisecs
echo "1000" > /proc/sys/vm/dirty_writeback_centisecs
6. EXT4 tweaks (greatly increase I/O)
(needs /system, /cache, /data partitions formatted to EXT4)
a) 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
b) perfect mount options
Code:
busybox mount -o remount,noatime,noauto_da_alloc,nodiratime,barrier=0,nobh /system
busybox mount -o remount,noatime,noauto_da_alloc,nosuid,nodev,nodiratime,barrier=0,nobh /data
busybox mount -o remount,noatime,noauto_da_alloc,nosuid,nodev,nodiratime,barrier=0,nobh /cache
7. Flags blocks as non-rotational and increases cache size
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. microSD 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
9. Remove logger
Code:
rm /dev/log/main
10. Ondemand governor tweaks
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. Auto change governor and I/O Scheduler
a) I/O Scheduler (Best: MTD devices - VR; EMMC devices - SIO) - needs kernel with these
Code:
echo "vr" > /sys/block/mmcblk0/queue/scheduler
or
echo "sio" > /sys/block/mmcblk0/queue/scheduler
b) Governor (Best: Minmax > SavagedZen > Smoothass > Smartass > Interactive) - needs kernel with these
Code:
echo "governor-name-here" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
12. Auto-zipalign on boot
(needs zipalign bin)
Code:
[url]http://forum.xda-developers.com/showthread.php?t=860586[/url]
13. Loopy Smoothness tweak
Code:
[url]http://forum.xda-developers.com/showthread.php?t=1137554[/url]
[url]http://forum.xda-developers.com/showthread.php?t=1205744[/url]
14. Move dalvik-cache to cache partition (if it's big enough) to free up data partition space
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
15. Disable normalize sleeper
Code:
mount -t debugfs none /sys/kernel/debug
echo NO_NORMALIZED_SLEEPER > /sys/kernel/debug/sched_features
16. OOM groupings and priorities tweaks - SuperCharger
Code:
[url]http://forum.xda-developers.com/showthread.php?t=991276[/url]
GPS.conf
(create or edit your /system/etc/gps.conf with a file manager with root access)
For improving GPS lock time and signal.
a) European NTP server (replace for america or asia in your case)
Code:
NTP_SERVER=europe.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
b) SE supl for A-GPS (better than Nokia's or Google's)
Code:
SUPL_HOST=supl.sonyericsson.com
SUPL_PORT=7275
Other tweaks or guidelines
1. Patch your hosts file for blocking Ads
(please think before doing this; many developers are supported through this way)
Code:
You can use AdFree application for this or changing manually your hosts file.
Here are some databases:
http://www.mvps.org/winhelp2002/hosts.txt
http://pgl.yoyo.org/adservers/serverlist.php?showintro=0;hostformat=hosts
2. Use CyanogenMOD's APN list file - it's one of the most complete.
Code:
It's located in /system/etc/apns-conf.xml
3. Use UOT kitchen for basic theming on your device.
Code:
http://uot.dakra.lt/
4. Use Google's dns servers
Code:
Create an empty file, name it resolv.conf and put there these 2 lines:
nameserver 8.8.8.8
nameserver 8.8.4.4
Save to /system/etc/.
5. Update Superuser and su binary to latest version (3.0 beta)
Code:
http://goo-inside.me/superuser/
6. Disable sync feature in sqlite
(author: ownhere - needs a source for your device so you can compile the /system/lib/libsqlite.so)
Code:
Patch file here: http://forum.xda-developers.com/showthread.php?t=903507
7. Do not use task killers.
sysctl_tweaks and sysctl.conf tweaks
added by krabappel2548 Thank him
To make them work:
1. make a new file in /system/etc/init.d, name it sysctl_tweaks
2. make a new file in /system/etc, name it sysctl.conf
3. Paste the right code in the right file
1. sysctl_tweaks
Code:
#!/system/bin/sh
# grep sysctl /etc/init.d/*
/etc/init.d/02vm:# Load /sys/etc/sysctl.conf
/etc/init.d/02vm:sysctl -p
2. sysctl.conf
Code:
#sysctl.conf file
############################
# Battery life tweaks #
############################
sysctl -w vm.dirty_writeback_centisecs=3000;
sysctl -w vm.dirty_expire_centisecs=500;
############################
# kernel tweaks #
############################
sysctl -w kernel.sched_features=15834233;
sysctl -w kernel.msgmni=1024;
sysctl -w kernel.msgmax=64000;
sysctl -w kernel.shmmax=268435456;
sysctl -w kernel.shmall=2097152;
sysctl -w kernel.sem="500 512000 100 2048";
sysctl -w kernel.hung_task_timeout_secs=0;
sysctl -w kernel.sched_latency_ns=18000000;
sysctl -w kernel.sched_compat_yield=1;
sysctl -w kernel.sched_shares_ratelimit=256000;
sysctl -w kernel.sched_child_runs_first=0;
sysctl -w kernel.threads-max=10000;
sysctl -w kernel.panic=30;
sysctl -w kernel.panic_on_oops=1;
sysctl -w kernel.sched_features=24189;
sysctl -w kernel.sched_min_granularity_ns=1500000;
sysctl -w kernel.sched_wakeup_granularity_ns=3000000;
############################
# CPU tweaks #
############################
# Queue size modifications
sysctl -w net.core.optmem_max=20480;
sysctl -w net.unix.max_dgram_qlen=50;
# Net Core Settings
# Location: /proc/sys/net/core
sysctl -w net.core.wmem_max=524288;
sysctl -w net.core.rmem_max=524288;
sysctl -w net.core.rmem_default=256960;
sysctl -w net.core.wmem_default=256960;
############################
# VM & Filesystem tweaks #
############################
sysctl -w fs.lease-break-time=10;
sysctl -w fs.file-max=65536;
sysctl -w vm.overcommit_memory=1;
sysctl -w vm.min_free_order_shift=4;
sysctl -w vm.block_dump=0;
sysctl -w vm.oom_dump_tasks=1;
sysctl -w vm.page-cluster=3;
############################
# Net Speed tweaks #
############################
# UnderUtilized Networking Tweaks below as recommended by avgjoemomma (from XDA)
sysctl -w net.ipv4.tcp_congestion_control=cubic;
# Hardening the TCP/IP stack to SYN attacks
sysctl -w net.ipv4.tcp_syncookies=1;
sysctl -w net.ipv4.conf.all.rp_filter=1;
sysctl -w net.ipv4.conf.default.rp_filter=1;
sysctl -w net.ipv4.tcp_synack_retries=2;
sysctl -w net.ipv4.tcp_syn_retries=2;
sysctl -w net.ipv4.tcp_max_syn_backlog=1024;
sysctl -w net.ipv4.tcp_max_tw_buckets=16384;
sysctl -w net.ipv4.icmp_echo_ignore_all=1;
sysctl -w net.ipv4.icmp_ignore_bogus_error_responses=1;
sysctl -w net.ipv4.tcp_no_metrics_save=1;
sysctl -w net.ipv4.tcp_fin_timeout=15;
sysctl -w net.ipv4.tcp_keepalive_time=1800;
sysctl -w net.ipv4.ip_forward=0;
sysctl -w net.ipv4.tcp_moderate_rcvbuf=1;
sysctl -w net.ipv4.route.flush=1;
sysctl -w net.ipv4.udp_rmem_min=6144;
sysctl -w net.ipv4.udp_wmem_min=6144;
sysctl -w net.ipv4.tcp_rfc1337=1;
sysctl -w net.ipv4.ip_no_pmtu_disc=0;
sysctl -w net.ipv4.tcp_ecn=0;
sysctl -w net.ipv4.tcp_sack=1;
sysctl -w net.ipv4.tcp_fack=1;
# Don't accept source routing
sysctl -w net.ipv4.conf.default.accept_source_route=0 ;
sysctl -w net.ipv4.conf.all.accept_source_route=0;
# Don't accept redirects
sysctl -w net.ipv4.conf.all.accept_redirects=0;
sysctl -w net.ipv4.conf.default.accept_redirects=0;
sysctl -w net.ipv4.conf.all.secure_redirects=0;
sysctl -w net.ipv4.conf.default.secure_redirects=0;
This is another init.d tweak It's a battery calibration script
3. This is my battery calibration tweak
Code:
#!/system/bin/sh
# ========================================
# init.d script for KA Xperia SSpeed
# made by krabappel2548
# ========================================
SLEEP=120
if [ -e /data/.battery-calibrated ] ; then
exit 0
fi
(
while : ; do
LEVEL=$(cat /sys/class/power_supply/battery/capacity)
CUR=$(cat /sys/class/power_supply/battery/batt_current)
if [ "$LEVEL" == "100" ] && [ "$CUR" == "0" ] ; then
log -p i -t battery-calibration "*** LEVEL: $LEVEL CUR: $CUR***: calibrating..."
rm -f /data/system/batterystats.bin
touch /data/.battery-calibrated
exit 0
fi
# log -p i -t battery-calibration "*** LEVEL: $LEVEL CUR: $CUR ***: sleeping for $SLEEP s..."
sleep $SLEEP
done
) &
#Disable normalize sleeper
mount -t debugfs none /sys/kernel/debug
echo NO_NORMALIZED_SLEEPER > /sys/kernel/debug/sched_features
#battery tweaks (sleepers)
mount -t debugfs none /sys/kernel/debug
echo NO_NEW_FAIR_SLEEPERS > /sys/kernel/debug/sched_features;
echo NO_NORMALIZED_SLEEPERS > /sys/kernel/debug/sched_features;
umount /sys/kernel/debug
Tips Combined twaks and apps
Still testing better values to add!
1. incredibile fast browsing in zoomed pages with no shutters!
♦ VM Heapsize; higher the RAM, higher the hp can be
Code:
dalvik.vm.heapsize=96m
♦ Helps scrolling responsiveness
Code:
windowsmgr.max_events_per_sec=250
♦ Opera Mobile Browser
2. Faster internet speed
♦ Signal (3G) tweaks
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
♦ Net speed tweaks
Code:
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
Alright, I think this is it for now.
If you have any other tweaks or better values, you can PM me and I'll include them
thanks to
kenzo
krabappel2548
thanks ve been waiting for this
Nice work been looking for some of these
Sent from my LT26i using xda premium
can i use it for xperia u?
10/40 said:
can i use it for xperia u?
Click to expand...
Click to collapse
Yes you can.
Sent from my LT26i using Tapatalk 2
gm007 said:
Yes you can.
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
thx ...have to try it, soon
added Tweaks Combination to make it easier to understand for new people
nice job u done here very useful,
The Mods should make this thread sticky
May I put those scripts everywhere I can in build.prop ?
mpttrung said:
May I put those scripts everywhere I can in build.prop ?
Click to expand...
Click to collapse
nope add them at the end of the page and leave a free row between them to avoid problems
WebMuth said:
nope add them at the end of the page and leave a free row between them to avoid problems
Click to expand...
Click to collapse
ok, thanks ! lets me check it out
optik19918 said:
4. Render UI with GPU
Code:
debug.sf.hw=1
Click to expand...
Click to collapse
This one was already added by Sony in build.prop
optik19918 said:
7. Save battery
Code:
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
Click to expand...
Click to collapse
I tested these a while ago and found them not effective. I even experienced less battery drain without these 2 lines
optik19918 said:
10. Raise photo and video recording quality
Code:
ro.media.dec.jpeg.memcap=8000000
Click to expand...
Click to collapse
I'm not sure if these help because we have 12mp camera and not 8.
optik19918 said:
b) SE supl for A-GPS (better than Nokia's or Google's)
Code:
SUPL_HOST=supl.sonyericsson.com
SUPL_PORT=7275
Click to expand...
Click to collapse
These are also already added by Sony
btw I'll post some more tweaks here later so you can add them to first post
krabappel2548 said:
This one was already added by Sony in build.prop
I tested these a while ago and found them not effective. I even experienced less battery drain without these 2 lines
I'm not sure if these help because we have 12mp camera and not 8.
These are also already added by Sony
btw I'll post some more tweaks here later so you can add them to first post
Click to expand...
Click to collapse
thanks for all i'l update when i go home now i'm at work!
some values are wrong becose i have those tweaks since the time of the x10
and i left the one already added by Sony in build.prop to make them easier to understand
Sent from my LT26i using xda premium
Here are some more tweaks Feel free to add them to the first post
To make them work:
1. make a new file in /system/etc/init.d, name it sysctl_tweaks
2. make a new file in /system/etc, name it sysctl.conf
3. Paste the right code in the right file
1. sysctl_tweaks
Code:
#!/system/bin/sh
# grep sysctl /etc/init.d/*
/etc/init.d/02vm:# Load /sys/etc/sysctl.conf
/etc/init.d/02vm:sysctl -p
2. sysctl.conf
Code:
#sysctl.conf file
############################
# Battery life tweaks #
############################
sysctl -w vm.dirty_writeback_centisecs=3000;
sysctl -w vm.dirty_expire_centisecs=500;
############################
# kernel tweaks #
############################
sysctl -w kernel.sched_features=15834233;
sysctl -w kernel.msgmni=1024;
sysctl -w kernel.msgmax=64000;
sysctl -w kernel.shmmax=268435456;
sysctl -w kernel.shmall=2097152;
sysctl -w kernel.sem="500 512000 100 2048";
sysctl -w kernel.hung_task_timeout_secs=0;
sysctl -w kernel.sched_latency_ns=18000000;
sysctl -w kernel.sched_compat_yield=1;
sysctl -w kernel.sched_shares_ratelimit=256000;
sysctl -w kernel.sched_child_runs_first=0;
sysctl -w kernel.threads-max=10000;
sysctl -w kernel.panic=30;
sysctl -w kernel.panic_on_oops=1;
sysctl -w kernel.sched_features=24189;
sysctl -w kernel.sched_min_granularity_ns=1500000;
sysctl -w kernel.sched_wakeup_granularity_ns=3000000;
############################
# CPU tweaks #
############################
# Queue size modifications
sysctl -w net.core.optmem_max=20480;
sysctl -w net.unix.max_dgram_qlen=50;
# Net Core Settings
# Location: /proc/sys/net/core
sysctl -w net.core.wmem_max=524288;
sysctl -w net.core.rmem_max=524288;
sysctl -w net.core.rmem_default=256960;
sysctl -w net.core.wmem_default=256960;
############################
# VM & Filesystem tweaks #
############################
sysctl -w fs.lease-break-time=10;
sysctl -w fs.file-max=65536;
sysctl -w vm.overcommit_memory=1;
sysctl -w vm.min_free_order_shift=4;
sysctl -w vm.block_dump=0;
sysctl -w vm.oom_dump_tasks=1;
sysctl -w vm.page-cluster=3;
############################
# Net Speed tweaks #
############################
# UnderUtilized Networking Tweaks below as recommended by avgjoemomma (from XDA)
sysctl -w net.ipv4.tcp_congestion_control=cubic;
# Hardening the TCP/IP stack to SYN attacks
sysctl -w net.ipv4.tcp_syncookies=1;
sysctl -w net.ipv4.conf.all.rp_filter=1;
sysctl -w net.ipv4.conf.default.rp_filter=1;
sysctl -w net.ipv4.tcp_synack_retries=2;
sysctl -w net.ipv4.tcp_syn_retries=2;
sysctl -w net.ipv4.tcp_max_syn_backlog=1024;
sysctl -w net.ipv4.tcp_max_tw_buckets=16384;
sysctl -w net.ipv4.icmp_echo_ignore_all=1;
sysctl -w net.ipv4.icmp_ignore_bogus_error_responses=1;
sysctl -w net.ipv4.tcp_no_metrics_save=1;
sysctl -w net.ipv4.tcp_fin_timeout=15;
sysctl -w net.ipv4.tcp_keepalive_time=1800;
sysctl -w net.ipv4.ip_forward=0;
sysctl -w net.ipv4.tcp_moderate_rcvbuf=1;
sysctl -w net.ipv4.route.flush=1;
sysctl -w net.ipv4.udp_rmem_min=6144;
sysctl -w net.ipv4.udp_wmem_min=6144;
sysctl -w net.ipv4.tcp_rfc1337=1;
sysctl -w net.ipv4.ip_no_pmtu_disc=0;
sysctl -w net.ipv4.tcp_ecn=0;
sysctl -w net.ipv4.tcp_sack=1;
sysctl -w net.ipv4.tcp_fack=1;
# Don't accept source routing
sysctl -w net.ipv4.conf.default.accept_source_route=0 ;
sysctl -w net.ipv4.conf.all.accept_source_route=0;
# Don't accept redirects
sysctl -w net.ipv4.conf.all.accept_redirects=0;
sysctl -w net.ipv4.conf.default.accept_redirects=0;
sysctl -w net.ipv4.conf.all.secure_redirects=0;
sysctl -w net.ipv4.conf.default.secure_redirects=0;
This is another init.d tweak It's a battery calibration script
3. This is my battery calibration tweak
Code:
#!/system/bin/sh
# ========================================
# init.d script for KA Xperia SSpeed
# made by krabappel2548
# ========================================
SLEEP=120
if [ -e /data/.battery-calibrated ] ; then
exit 0
fi
(
while : ; do
LEVEL=$(cat /sys/class/power_supply/battery/capacity)
CUR=$(cat /sys/class/power_supply/battery/batt_current)
if [ "$LEVEL" == "100" ] && [ "$CUR" == "0" ] ; then
log -p i -t battery-calibration "*** LEVEL: $LEVEL CUR: $CUR***: calibrating..."
rm -f /data/system/batterystats.bin
touch /data/.battery-calibrated
exit 0
fi
# log -p i -t battery-calibration "*** LEVEL: $LEVEL CUR: $CUR ***: sleeping for $SLEEP s..."
sleep $SLEEP
done
) &
#Disable normalize sleeper
mount -t debugfs none /sys/kernel/debug
echo NO_NORMALIZED_SLEEPER > /sys/kernel/debug/sched_features
#battery tweaks (sleepers)
mount -t debugfs none /sys/kernel/debug
echo NO_NEW_FAIR_SLEEPERS > /sys/kernel/debug/sched_features;
echo NO_NORMALIZED_SLEEPERS > /sys/kernel/debug/sched_features;
umount /sys/kernel/debug
Big thanks for krabappel and optik!!
Sent from my Sony Xperia™ S
@krabappel2548: are the tweaks you posted already in your ka08 rom?
Apology11 said:
@krabappel2548: are the tweaks you posted already in your ka08 rom?
Click to expand...
Click to collapse
Yes
Sent from my LT26i using XDA
@Optik @Krabappel
i've just added all tweaks right now...bt i recognized my benchmark decreased it's now 6693 and it was 6900..im using doomkernel..maybe some tweaks or not compatible with it??
I added ro.mot.buttonlight.timeout=0 in the end of build.prop but it doesn't seem to have effect. Reboot didn't help either.
amfirbek92 said:
@Optik @Krabappel
i've just added all tweaks right now...bt i recognized my benchmark decreased it's now 6693 and it was 6900..im using doomkernel..maybe some tweaks or not compatible with it??
Click to expand...
Click to collapse
Stop looking at synthetic benchmark scores if your phone otherwise feels snappy.
mikbe said:
I added ro.mot.buttonlight.timeout=0 in the end of build.prop but it doesn't seem to have effect. Reboot didn't help either.
Stop looking at synthetic benchmark scores if your phone otherwise feels snappy.
Click to expand...
Click to collapse
Just removed ondemand governor tweak..everything seems very good now..and the benchmark is around 7400
Sent from my Sony Xperia™ S
Hi guys hope someone can help, i found a guide on dual booting my tablet its a linx 7
32 gb win 8.1 , I've spent the past two days reading and flashing having all sorts of problems lol but at least now ive managed to get it into a workable state.
At the minute its only booting android 4.4.4 as i deleted the windows.old folder and will probably have to do a full reinstall.
The problem with rooting android it seems is due to the usb otg part of the tablet and the ported version of the android version comes from the cube i7. The usb debugging is disabled due to the tablet only being designed for usbotg but there seems to be other versions of the android with root available from the manufacturer but due to using google translate and dead links im having no joy.
I found this using translate and google cache
You try to disguise iWork7 to Nexus7
Famous place in Arigasu such Pazudora is is, the domestic application There are many apps that limit such as carrier restrictions and ROOT limit is provided. Do not be able to start these apps from iWork7 it is currently being adjusted.
1. Look at the source
[GitHub]
2. Check item
the following values of the defualt.prop is NG
ro.secure = 0
ro.allow.mock.location = 1
ro.debuggable = 1
persist.sys.usb.config = adb
↓
Replaced iodide
ro.secure = 1
ro.allow.mock.location = 0
ro.debuggable = 0
persist.sys.usb.config = mtp
When the following exists NG (compatible with root switching of SuperSu)
· /system/app/Superuser.apk
· / System / bin / su
· / System / xbin / su
· / Sbin / su
You want to Nexus7 beetle the build.prop
Tablet classic [Nexus Factory Image
· Au of IntelAtom machine [ASUS MemoPad 8]
ro.build.id = KTU84P
# Ro.build.display.id = U67GT_v1.0__20150117
ro.build.display.id = KTU84P
# Ro.build.version.incremental = user.jim.20150117.113528
ro.build.version.incremental = 1227136
ro.build.version.sdk = 19
ro.build.version.codename = REL
ro.build.version.release = 4.4.4
# Ro.build.date = Sat Jan 17 11:37:11 CST 2015
ro.build.date = Fri Jun 13 07:23:23 UTC 2014
# Ro.build.date.utc = 1421465831
ro.build.date.utc = 1402644203
ro.build.type = user
# Ro.build.user = jim
ro.build.user = android-build
# Ro.build.host = build-168
ro.build.host = vpbs2.mtv.corp.google.com
# Ro.build.tags = dev-keys
ro.build.tags = release-keys
# Ro.product.model = U67GT
ro.product.model = Nexus 7
# Ro.product.brand = intel
ro.product.brand = google
# Ro.product.name = CUBE
ro.product.name = razor
# Ro.product.device = U67GT
ro.product.device = flo
# Ro.product.board = baylake
ro.product.board = flo
ro.product.cpu.abi = x86
ro.product.cpu.abi2 = armeabi-v7a
# Ro.product.manufacturer = intel
ro.product.manufacturer = asus
ro.product.locale.language = ja
persist.sys.language = ja
persist.sys.country = JP
ro.product.locale.region = JP
persist.sys.timezone = Asia / Tokyo
ro.wifi.channels =
ro.board.platform = baytrail
# Ro.build.product is obsolete; use ro.product.device
# Ro.build.product = CUBE
ro.build.product = flo
# Do not try to parse ro.build.description or .fingerprint
# Ro.build.description = em_i8270_64-user 4.4.4 KTU84P user.jim.20150117.113528 dev-keys
ro.build.description = razor-user 4.4.4 KTU84P 1227136 release-keys
# Ro.build.fingerprint = intel / em_i8270_64 / em_i8270: 4.4.4 / KTU84P / user.jim.20150117.113528: user / dev-keys
ro.build.fingerprint = google / razor / flo: 4.4.4 / KTU84P / 1227136: user / release-keys
ro.build.characteristics = nosdcard, tablet
*
| 2015-04-28 |
Mobile
*| Comments: 0
*|
Dynamically edit the Defualt.prop on Android
It seems possible to edit the defualt.prop under Android-root environment when you use the setpropex, quite amazing tool ,,,. (On reboot)
----------------------------------------
su -c "setpropex ro.secure 1"
---------------------------------------
(Ro.allow.mock.location = also the same format 1 and ro.debuggable = 1)
*
| 2015-04-28 |
Mobile
*| Comments: 0
*|
iWork7 without deleting the Windows area, to rewrite the image of Android !!
The standard recovery procedures, it is the initialization of the inescapable Windows, but it became a rewritable only favorite area of Android by step on this procedure. (Mr. SpecialThanks dia-sea)
Download the required files
· XDA bootimg_tools_7.8.13.zip [HP] [Download]
As basic knowledge, organize the recovery boot order
1. BIOS -> Lanch EFI Shell file filesystem device
2. Shell.efi (Shellx64.efi can not move because it does not correspond to 64bitEFI)
3. startup.nsh -> efilinux.efi -f droidboot.img
4. installer.cmd
※ seemed to make re-partition is performed when you run the droidboot.img, require modification of droidboot.img.
modification of droidboot.img
Information display
# ./boot_info Droidboot.img
PAGE SIZE: 2048
BASE ADDRESS: 0x80000000
RAMDISK ADDRESS: 0x81000000
CMDLINE: 'loglevel = 0 androidboot.bootmedia = sdcard androidboot.hardware = em_i8270 watchdog.watchdog_thresh = 60 androidboot.spid = xxxx: xxxx: xxxx: xxxx: xxxx: xxxx androidboot.serialno = 01234567890123456789 oops = panic panic = 40 vmalloc = 172M slub_max_order = 2 vga = current i915.modeset = 1 drm.vblankoffdelay = 1 acpi_backlight = vendor g_android.fastboot = 1 droidboot.minbatt = 0 droidboot.use_installer = 1 droidboot.installer_usb = / dev / block / sda1 droidboot.installer_file = installer. cmd '
dismantling of droidboot.img
# Split_boot droidboot.img
Editing of partition table
# Cp /droidboot/ramdisk/system/etc/partition.tbl /droidboot/ramdisk/system/etc/partition.tbl.bk
# Vi /droidboot/ramdisk/system/etc/partition.tbl
We want to only two lines
partition_table = gpt
reload / dev / block / mmcblk0
repack of ramdisk
# .././repack_ramdisk Ramdisk /
Creating droidboot.img
# .././mkbootimg --kernel Droidboot.img-kernel --ramdisk new-ramdisk.cpio.gz --cmdline "loglevel = 0 androidboot.bootmedia = sdcard androidboot.hardware = em_i8270 watchdog.watchdog_thresh = 60 androidboot.spid = xxxx: xxxx: xxxx: xxxx: xxxx: xxxx androidboot.serialno = 01234567890123456789 oops = panic panic = 40 vmalloc = 172M slub_max_order = 2 vga = current i915.modeset = 1 drm.vblankoffdelay = 1 acpi_backlight = vendor g_android.fastboot = 0 droidboot.minbatt = 0 droidboot.use_installer = 1 droidboot.installer_usb = / dev / block / sda1 droidboot.installer_file = installer.cmd "--base 0x80000000 --pagesize 2048 --ramdiskaddr 0x81000000 --output droidboot_not_clear.img
Creating a Boot USB
Prepare a USB memory that was formatted with FAT32, to copy the contents of AnTaku folder of the USB memory to the root.
You have created so far, system_rootja.img the system.img, boot_adbon.img the boot.img, and rename and droidboot_not_clear.img the droidboot.img,, with the same copy of the USB memory to the root.
and it rewrites the partition.tbl the same content as the droidboot.img you just created.
partition_table = gpt
reload / dev / block / mmcblk0
editing of startup.nsh, change to start the droidboot_not_clear.img.
efilinux.efi -f droidboot_not_clear.img
modification of installer.cmd
And comment out the partition fix part
factory, cache, system, config, logs, the data is initialized,
Fixed boot.img, recovery.img, droidboot.img, the writing of system.img appropriate.
Below, mount the / system in rw, boot_adbon.img the adb effectiveness of boot.img
root of, example of Japanese, as system_rootja.img unwanted apps deleted system.img, it has saved to a USB memory.
oem start_partitioning
REM oem partition /installer/partition.tbl
erase: factory
erase: cache
erase: system
erase: config
erase: logs
erase: data
oem stop_partitioning
REM oem wipe ESP
REM flash: ESP # / installer / esp.img
REM flash: boot # / installer / boot.img
flash: boot # / installer / boot_adbon.img
flash: recovery # / installer / recovery.img
flash: fastboot # / installer / droidboot.img
REM flash: system # / installer / system.img
flash: system # / installer / system_rootja.img
continue
Now, without initialization of Android image the Widnows became the all-you-can-****. Hail and Hail.
Incidentally is the recovery manual wrote by making full use of the translation site. [DL]
*
| 2015-04-28 |
Mobile
*| Comments: 0
*|
iWork7 Rooted !! full version!
We were successful in perfect Root acquired in iWork7. Correct the previous steps and re-published as a full version. (Mr. SpecialThanks dia-sea)
1. Download the necessary environment and file
Windows7 and (even 8.1) in a virtual environment we will proceed in the Linux (VMPalyer & Ubuntu14.10).
· Ubuntu14.10 Japanese 64bit [HP] [Download]
· VMWare Player [HP] [Download]
· IWork7 factory image [HP] [Download]
· Ext4_utils_cygwin_fixed [HP] [Download]
· SuperSu 2.46 [HP] [Download]
· Busybox [HP] [Download]
· Sgs2toext4 [HP] [Download] for people who system.ext4.img does not make well. (JAVA)
· USB memory space is available formatted with NTFS of about 8GB
· USB memory space is available formatted with FAT32 of more than 2GB
· USB keyboard, OTGHUB
2. Building a home directory
Once you start the ubuntu, to make a [iwork7] directory to the home directory,
and rename ext4_utils_cygwin_fixed.zip, system.img, copy the busybox, the directory name to unzip the UPDATE-SuperSU-v2.46.zip [updatesu].
After this it will be operation in the linux console.
In order to comfortable operation with the administrative authority, operation and after you to live do not put sudo passwords many times is easy.
$ Sudo $ {SHELL}
[Sudo] password for username:
Or, it will switch to the root user with su.
$ Sudo su -
3. Mount of system.img
System.img of factory image because it is a file that was cut wasteful part (0?) At the simg format, you will need to convert it to the format of the raw image ext4.
It wants to install the zlib1g-dev necessary to ext4_utils of make.
# Apt-get install zlib1g-dev
ext4_utils of thawing
# Unzip ext4_utils_cygwin_fixed.zip
make of ext4_utils
# Cd ext4_utils
# Make
to copy to make to the finished file to iwork7 directory.
The ones where you unzipped the SuperSu to updatesu directory, to just below iwork7 your own build.prop.
Examples of Japanese correspondence build.prop
ro.product.locale.language = ja
ro.product.locale.region = JP
persist.sys.language = ja
persist.sys.country = JP
persist.sys.timezone = Asia / Tokyo
Creating system.ext4.img
# Simg2img system.img system.ext4.img
System.img remove because it is unnecessary at this point
iWorkt-Root02.png
copy of busybox
# Cp busybox-x86_64 sys / xbin / busybox
# Chown root: root sys / xbin / busybox
# Chmod 0755 sys / xbin / busybox
4. Mount of system.img
# Umount msys
# Rm -f system.img
# Rm -rf msys
# Rm -rf sys
# Mkdir msys
# Mkdir sys
# Mount -o loop system.ext4.img msys
# Cp -a msys /. Sys
# Umount msys
5. root setting
Clear root
# Rm -rf sys / bin / .ext
# Rm -rf sys / etc / init.d
# Rm -f sys / bin / su
# Rm -f sys / xbin / su
# Rm -f sys / xbin / daemonsu
# Rm -f sys / bin / .ext / .su
# Rm -f sys / etc / install-recovery.sh
# Rm -f sys / etc / init.d / 99SuperSUDaemon
# Rm -f sys / etc / .installed_su_daemon
# Rm -f sys / app / Superuser.apk
# Rm -f sys / app / Superuser.odex
# Rm -f sys / app / SuperUser.apk
# Rm -f sys / app / SuperUser.odex
# Rm -f sys / app / superuser.apk
# Rm -f sys / app / superuser.odex
# Rm -f sys / app / Supersu.apk
# Rm -f sys / app / Supersu.odex
# Rm -f sys / app / SuperSU.apk
# Rm -f sys / app / SuperSU.odex
# Rm -f sys / app / supersu.apk
# Rm -f sys / app / supersu.odex
root acquisition start
# Mkdir sys / bin / .ext
# Cp updatesu / x86 / su sys / xbin / daemonsu
# Cp updatesu / x86 / su sys / xbin / su
# Cp updatesu / x86 / su sys / bin / .ext / .su
# Cp updatesu / common / Superuser.apk sys / app / Superuser.apk
# Cp updatesu / common / install-recovery.sh sys / etc / install-recovery.sh
# Mkdir sys / etc / init.d /
# Cp updatesu / common / 99SuperSUDaemon sys / etc / init.d / 99SuperSUDaemon
# Echo 1> sys / etc / .installed_su_daemon
# Chown root: root sys / bin / .ext
# Chown root: root sys / bin / .ext / .su
# Chown root: root sys / xbin / su
# Chown root: root sys / xbin / daemonsu
# Chown root: root sys / etc / install-recovery.sh
# Chown root: root sys / etc / init.d / 99SuperSUDaemon
# Chown root: root sys / etc / .installed_su_daemon
# Chown root: root sys / app / Superuser.apk
# Chmod 0777 sys / bin / .ext
# Chmod 06755 sys / bin / .ext / .su
# Chmod 06755 sys / xbin / su
# Chmod 0755 sys / xbin / daemonsu
# Chmod 0755 sys / etc / install-recovery.sh
# Chmod 0755 sys / etc / init.d / 99SuperSUDaemon
# Chmod 0644 sys / etc / .installed_su_daemon
# Chmod 0644 sys / app / Superuser.apk
Unnecessary apps (Chinese market, etc.) Delete
# Rm -f sys / preinstall / 91hiapk_AndroidPhone_1008443.apk
# Rm -f sys / preinstall / AnZhi_KuBiMoFangFuFei_V5.4_20141002.apk
# Rm -f sys / preinstall / BaiduNaviHD_d4033_20140523.apk
# Rm -f sys / preinstall / baidusearch_Android_1_3_0_7_1009249a.apk
# Rm -f sys / preinstall / cn.keyshare.course_ku_bi.apk
# Rm -f sys / preinstall / CUBE_UgameStore_V210_20141128.apk
# Rm -f sys / preinstall / Mediaplayer.apk
# Rm -f sys / preinstall / ninegameclienthd_v2.2.0_android_release.apk
# Rm -f sys / preinstall / Tudou_Android_phone_4.2_yingyue1.apk
# Rm -f sys / preinstall / wandoujia_kubimofang_oem_fa.apk
One line below if unnecessary copy your own bulid.prop may not run
# Cp build.prop sys / build.prop
Root, installation of busybox
# Mv sys / system
# Rm / system / bin / cp
# Rm / system / bin / mv
# / System / xbin / su --install
# / System / xbin / busybox --install -s / system / bin
# Mv / system sys
6. writing of system.img
When you root reduction, to create the following command implantation system.img. (Note the space)
# ./mkuserimg.sh -s Sys system.img ext4 system 896M
Copy the file to Windows, it will overwrite the system.img to where you copied the Android system to a USB memory that was formatted with FAT32.
6. Rooted !!
To complete the installation of the Android system open the BIOS menu from the ESC key to turn on the power. All after the completion of Android has become the Root state.
iWork7-BootBIOS.png
Finally, Do not you forget the installation of Windows.
Windows will cause is initialized in the above procedure.
In the next section we will learn the steps to rewrite only Android, leaving the Windows.
*
| 2015-04-28 |
Mobile
*| Comments: 0
*|
iWork7 adb daemon configuration of (tcp)
It is iWork7 ~ is the first place impossible to connect with adb in USB debugging on, but can be connected by TCP.
If editing the /ramdsik/default.prop I may, but does not use the ramdisk.img, it uses the ramdisk in the boot.img. (Mr. SpecialThanks dia-sea)
1. File downloading
· XDA bootimg_tools_7.8.13.zip [HP] [Download]
2. It will copy the necessary files
Unzip the bootimg_tools_7.8.13.zip, is located in the following
Home directory / iwork7 / bootimg_tools
Copy the boot.img to bootimg_tools.
3. information display of boot.img
# Cd boot
# Boot_info boot.img
PAGE SIZE: 2048
BASE ADDRESS: 0x80000000
RAMDISK ADDRESS: 0x81000000
CMDLINE: 'loglevel = 0 androidboot.bootmedia = sdcard androidboot.hardware = em_i8270 watchdog.watchdog_thresh = 60 androidboot.spid = xxxx: xxxx: xxxx: xxxx: xxxx: xxxx androidboot.serialno = 01234567890123456789 oops = panic panic = 40 vmalloc = 172M slub_max_order = 2 vga = current i915.modeset = 1 drm.vblankoffdelay = 1 acpi_backlight = vendor '
4. dismantling of boot.img
# Split_boot boot.img
5. adb setting
# Cd boot / ramdisk
# Vi default.prop
persist.nomodem_ui = 1
ro.arch = x86
ro.com.google.clientidbase = android-google
ro.secure = 0
ro.adb.secure = 0
ro.allow.mock.location = 1
ro.debuggable = 1
persist.sys.usb.config = adb
Creating 6.boot.img
# Cd boot
# .././repack_ramdisk Ramdisk /
# .././mkbootimg --kernel Boot.img-kernel --ramdisk new-ramdisk.cpio.gz --cmdline "loglevel = 0 androidboot.bootmedia = sdcard androidboot.hardware = em_i8270 watchdog.watchdog_thresh = 60 androidboot.spid = xxxx: xxxx: xxxx: xxxx: xxxx: xxxx androidboot.serialno = 01234567890123456789 oops = panic panic = 40 vmalloc = 172M slub_max_order = 2 vga = current i915.modeset = 1 drm.vblankoffdelay = 1 acpi_backlight = vendor "--base 0x80000000 --pagesize 2048 --ramdiskaddr 0x81000000 --output boot.img
# Mv boot.img ../.
iwork7 to the connected with tcp / ip after adb Enable
on the command prompt of windows
# Adb connect "iwork7 of ip address"
# Adb shell
# Su - (Since root permission prompt SuperSU exits click allowed on the tablet!)
# Ps
# Root @ U67GT: / # ps
*
| 2015-04-28 |
Mobile
*| Comments: 0
And im not sure if this helps or not.
Am i able to add root to the rom myself ?
Just to add the usb-debugging is not enabled from the way the rom is designed, when you click the build/ model number to enable it then dev options it only offers the option to revoke the rights .
Bump!
Anyone? is there a way to add superuser to the system.img by decompiling / recompling?
crickyo said:
Bump!
Anyone? is there a way to add superuser to the system.img by decompiling / recompling?
Click to expand...
Click to collapse
Check these:
http://forum.xda-developers.com/showthread.php?t=2294909
http://forum.xda-developers.com/showthread.php?t=2665283
sdeepb said:
Check these:
http://forum.xda-developers.com/showthread.php?t=2294909
http://forum.xda-developers.com/showthread.php?t=2665283
Click to expand...
Click to collapse
Hi thanks for the reply i tried those the other night , but from what i remember it was asking for ext 4 and the files i have are system.img, I read through that thread and i think it said to try open the .img in the second program when i tried this it hung and crashed.
Is it really as simple as unpacking it and repacking it?
Im a long time android tinkerer but never knew what ive been doing just following guides
crickyo said:
Hi thanks for the reply i tried those the other night , but from what i remember it was asking for ext 4 and the files i have are system.img, I read through that thread and i think it said to try open the .img in the second program when i tried this it hung and crashed.
Is it really as simple as unpacking it and repacking it?
Im a long time android tinkerer but never knew what ive been doing just following guides
Click to expand...
Click to collapse
Sorry I don't have experience with this, asking in the thread would be your best bet
Hi , I managed to find a link on a chinese site to a modified system.img the two programs dont work and the thread says as much.
Mods can close this thread if they want.
OK guys if you are still after root I can help I have a linx 7 with the dual boot I used some files I found around the internet also my android partition is 8g instead of 4g it works like a charm if you guys still want I can upload and post a link
[email protected] said:
OK guys if you are still after root I can help I have a linx 7 with the dual boot I used some files I found around the internet also my android partition is 8g instead of 4g it works like a charm if you guys still want I can upload and post a link
Click to expand...
Click to collapse
can you post tutorial or links? is there chance to root device without touching windows partition?
marcindh said:
can you post tutorial or links? is there chance to root device without touching windows partition?
Click to expand...
Click to collapse
http://linxtablet.co.uk/viewtopic.php?f=4&t=2096
Unfortunately it does wipe your windows installation and you will be flashing the bios with a Chinese dual boot but it does 100% work
[email protected] thank you for very fast reply I have dualboot but android is not rooted (tutorial from reddit). Android from your link is already rooted?
marcindh said:
[email protected] thank you for very fast reply I have dualboot but android is not rooted (tutorial from reddit). Android from your link is already rooted?
Click to expand...
Click to collapse
No i don't think it is but if you download supersu.zip file search it on xda and download it to your memory card in your tablet then turn your tablet off.... holding the volume down button in while turning on and keeping the volume down pressed it will boot to a screen where you can select recovery and install from .zip in recovery when installed reboot all done ...:good:
[email protected] said:
No i don't think it is but if you download supersu.zip file search it on xda and download it to your memory card in your tablet then turn your tablet off.... holding the volume down button in while turning on and keeping the volume down pressed it will boot to a screen where you can select recovery and install from .zip in recovery when installed reboot all done ...:good:
Click to expand...
Click to collapse
I almost forgot my copy of the dual boot has a different recovery so you might have to reinstall