Related
Does NOT work with aosp roms, sorry...
This is what i use in my rom and it works great. I have tried these script with a few other roms and the work with them too.
They make the roms snappy and very fast. Also give a boost in quandrant scores.
Some roms adjust some of the settings in these scripts too but i havent had ant errors with any roms i have tried. Please post if you have any issues with anything.
Devs feel free to add to your roms just leave the #smokin1337 in the scripts if ya dont mind.
Lowered the dalvik heap, will add more later ...
Just flash the zip in recovery to install
EDIT:
v1.1
Since a few people won't use this without basic info here it is:
This script will work with any 2.3.4 rom and afaik aosp or sense but i don't use aosp so i can't say for sure.
The scripts include:
Kernel tweaks
VM tweaks (swappiness, minfree, adj, etc.)
Optimized mounts
Cache Cleanup
SDCard read ahead to 3072
Dalvik Heap to 32 soon to be 48
SQLite Vacuum
tcp tweaks
IO scheduler set to deadline
Chmod User Log Files that go to HTC
Setprop Tweaks are:
VM Props
GUI Tweaks
Video/Pic enhancements
Disable HTC Checkin Service
LCD Density
Disable debug icon
Increase WiFi scan interval to 120 sec.
The Scripts
02sicktweaks
Code:
#!/system/bin/sh
#Sick Tweaks
#smokin1337
rm -f /cache/*.apk
rm -f /cache/*.tmp
rm -f /data/dalvik-cache/*.apk
rm -f /data/dalvik-cache/*.tmp
busybox rm -f /data/system/userbehavior.db
busybox chmod 400 /data/system/usagestats/
busybox chmod 400 /data/system/appusagestats/
busybox mount -o remount,rw,noatime,noauto_da_alloc,nodiratime,barrier=0,nobh /system
busybox mount -o remount,noatime,noauto_da_alloc,nodiratime,nodev,barrier=0,nobh /data
busybox mount -o remount,noatime,noauto_da_alloc,nodiratime,nodev,barrier=0,nobh /cache
export sampling_rate=10000
export up_threshold=65
export READ_AHEAD_KB=3072
if [ -n ${up_threshold} ];
then echo ${up_threshold} > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold
fi
if [ -n ${sampling_rate} ];
then echo ${sampling_rate} > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/sampling_rate
fi
if [ -e /sys/module/lowmemorykiller/parameters/adj ]; then
echo "0,1,2,4,7,15" > /sys/module/lowmemorykiller/parameters/adj
fi
if [ -e /sys/module/lowmemorykiller/parameters/minfree ]; then
echo "2560,4096,6144,12288,14336,18432" > /sys/module/lowmemorykiller/parameters/minfree
fi
if [ -e /sys/devices/virtual/bdi/179:0/read_ahead_kb ]; then
echo "3072" > /sys/devices/virtual/bdi/179:0/read_ahead_kb
fi
# Set io scheduler tweaks for mmc
echo "deadline" > /sys/block/mmcblk0/queue/scheduler
echo "0" > /sys/block/mmcblk0/queue/rotational
echo "2048" > /sys/block/mmcblk0/queue/nr_requests
echo ${READ_AHEAD_KB} > /sys/block/mmcblk0/queue/read_ahead_kb
echo "deadline" > /sys/block/mmcblk1/queue/scheduler
echo "0" > /sys/block/mmcblk1/queue/rotational
echo "2048" > /sys/block/mmcblk1/queue/nr_requests
echo ${READ_AHEAD_KB} > /sys/block/mmcblk1/queue/read_ahead_kb
for i in \ `find /data -iname "*.db"` do \ sqlite3
$i 'VACUUM;'
done
echo "6144 87380 524288" > /proc/sys/net/ipv4/tcp_wmem
echo "6144 87380 524288" > /proc/sys/net/ipv4/tcp_rmem
06sysctl
Code:
#!/system/bin/sh
#sysctl/setprop stuff
#smokin1337
sync
sysctl -w vm.oom_kill_allocating_task=0
sysctl -w fs.nr_open=1053696
sysctl -w fs.inotify.max_queued_events=32000
sysctl -w fs.inotify.max_user_instances=256
sysctl -w fs.inotify.max_user_watches=10240
sysctl -w fs.lease-break-time=10
sysctl -w fs.file-max=165164
sysctl -w vm.swappiness=0
sysctl -w vm.overcommit_memory=1
sysctl -w vm.page-cluster=3
sysctl -w vm.drop_caches=3
sysctl -w vm.min_free_kbytes=4096
sysctl -w vm.dirty_ratio=15
sysctl -w vm.dirty_background_ratio=4
sysctl -w vm.vfs_cache_pressure=10
sysctl -w vm.panic_on_oom=0
sysctl -w vm.dirty_expire_centisecs=200
sysctl -w vm.dirty_writeback_centisecs=500
sysctl -w kernel.sem=500,512000,64,2048
sysctl -w kernel.msgmax=64000
sysctl -w kernel.msgmni=64000
sysctl -w kernel.threads-max=525810
sysctl -w kernel.random.write_wakeup_threshold=256
sysctl -w kernel.random.read_wakeup_threshold=128
sysctl -w kernel.panic=5
sysctl -w kernel.shmall=16777216
sysctl -w kernel.shmmax=268435456
sysctl -w kernel.sched_latency_ns=10000000
sysctl -w kernel.sched_min_granularity_ns=2000000
sysctl -w kernel.sched_wakeup_granularity_ns=0
sysctl -w kernel.sched_compat_yield=1
sysctl -w net.ipv6.conf.default.use_tempaddr=2
sysctl -w net.ipv6.conf.all.use_tempaddr=2
sysctl -w net.ipv6.conf.all.temp_prefered_lft=3600
sysctl -w net.ipv6.conf.default.temp_prefered_lft=3600
setprop cm.filesystem.ready 1
setprop dc.filesystem.ready 1
setprop oxygen.filesystem.ready 1
setprop ro.telephony.call_ring.delay 0
setprop ring.delay 0
setprop windowsmgr.max_events_per_sec 150
setprop windowsmgr.support_rotation_270 true
setprop ro.HOME_APP_ADJ 1
setprop ro.HOME_APP_MEM 2048
setprop dalvik.vm.heapsize 48m
setprop dalvik.vm.stack-trace-file=/data/anr/traces.txt
setprop dalvik.vm.lockprof.threshold=500
setprop dalvik.vm.verify-bytecode=false
setprop dalvik.vm.jniopts=warnonly
setprop ro.ril.hsxpa=3
setprop ro.ril.hsdpa.category =28
setprop ro.ril.gprsclass=12
setprop ro.ril.hep=1
setprop ro.ril.enable.dtm=1
setprop ro.ril.enable.a53=1
setprop ro.ril.htcmaskw1.bitmask=4294967295
setprop ro.ril.htcmaskw1=14449
setprop ro.ril.hsupa.category=9
setprop ro.ril.def.agps.mode=2
setprop ro.ril.def.agps.feature=1
setprop ro.ril.enable.sdr=1
setprop ro.ril.enable.gea3=1
setprop ro.ril.enable.fd.plmn.prefix=23402,23410,23411
setprop ro.ril.disable.power.collapse=0
setprop ro.media.enc.jpeg.quality=100
setprop ro.media.dec.jpeg.memcap=8000000
setprop ro.media.enc.hprof.vid.bps=8000000
setprop pm.sleep_mode=1
setprop persist.adb.notify=0
setprop ro.config.htc.nocheckin=1
setprop ro.config.nocheckin=1
setprop wifi.supplicant_scan_interval=120
setprop ro.sf.lcd_density=240
Hope that helps...
V1.1 has more tweaks, so i'll leave the original in case you dont want the extra ones the ones in code above is from v1.1
Post some results here...
smokin1337 said:
This is what i use in my rom and it works great. I have tried these script with a few other roms and the work with them too.
They make the roms snappy and very fast. Also give a boost in quandrant scores.
Some roms adjust some of the settings in these scripts too but i havent had ant errors with any roms i have tried. Please post if you have any issues with anything.
Devs feel free to add to your roms just leave the #smokin1337 in the scripts if ya dont mind.
Just flash the zip in recovery to install
Post some results here...
Click to expand...
Click to collapse
Thank you sir!
hTc Evo [3D]
What exactly does this script do? this is like giving me a pill and just telling me it will cure cancer with no explanation
Thaxx said:
What exactly does this script do? this is like giving me a pill and just telling me it will cure cancer with no explanation
Click to expand...
Click to collapse
If you open the zip and read the scripts you'd see.
It basically changes a bunch of settings on your phone, dalvik heap to 72mb for example, readahead speed increase on the sdcard, a bunch of other stuff.
This is safe for sense and aosp roms?
Sent from my PG06100 using Tapatalk
It's basically all the speed tweaks out and some i found doing some research. It changes quite a few things as the previous poster said check out the scripts and see what they do, which is good practice to do all the time. I edited the values for speed on my rom but it should work with any existing rom.
stinkdified said:
This is safe for sense and aosp roms?
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Should be its all android system edits.
A dalvik of 72 is a terrible, terrible idea, man. (No offense, I'm sure you put a lot of work into this script)
LiquidSolstice said:
A dalvik of 72 is a terrible, terrible idea, man. (No offense, I'm sure you put a lot of work into this script)
Click to expand...
Click to collapse
Whats a good setting ? Seemed ok to me i read some that said higher is better and some said lower is better. Neither seemed to make much difference so i left it high.
smokin1337 said:
Whats a good setting ? Seemed ok to me i read some that said higher is better and some said lower is better. Neither seemed to make much difference so i left it high.
Click to expand...
Click to collapse
It'll be smooth for a while, but the problem with that is that it will take way too long for the garbage collector to come and clean up after the process. There's a better way of explaining it, unfortunately, I'm not sure how to.
smokin1337 said:
It's basically all the speed tweaks out and some i found doing some research. It changes quite a few things as the previous poster said check out the scripts and see what they do, which is good practice to do all the time..
Click to expand...
Click to collapse
how to "check out the scripts and see what they do"?
directions say to just flash it
theres no written explanation of all the tweaks somewhere?
Going to try this now, Thanks bro
SayWhat10 said:
how to "check out the scripts and see what they do"?
directions say to just flash it
theres no written explanation of all the tweaks somewhere?
Click to expand...
Click to collapse
Nah not really i looked them up on google, i adjusted them back and forth to see what helped and what didn't. I'm gonna lower the dalvik heap with the advice of liquid solstice to 32 just to be safe.
Good stuff man, will report back with results.
Thx..
Sent from my PG86100 using xda premium
question smokin what does this do?
busybox mount -o remount,rw,noatime,noauto_da_alloc,nodiratime,barrier=0,nobh /system
busybox mount -o remount,noatime,noauto_da_alloc,nodiratime,nodev,barrier=0,nobh /data
busybox mount -o remount,noatime,noauto_da_alloc,nodiratime,nodev,barrier=0,nobh /cache
i sort of get it but not really
smokin1337 said:
Nah not really i looked them up on google, i adjusted them back and forth to see what helped and what didn't. I'm gonna lower the dalvik heap with the advice of liquid solstice to 32 just to be safe.
Click to expand...
Click to collapse
I would do 64M, gives everything enough room to breathe and it's sort of the 'standard', I guess. Amything more is no bueno as LS pointed out and anything less is limiting our phones. Just my thoughts.
empiire said:
I would do 64M, gives everything enough room to breathe and it's sort of the 'standard', I guess. Amything more is no bueno as LS pointed out and anything less is limiting our phones. Just my thoughts.
Click to expand...
Click to collapse
i thinks 32 is best HTC Put it there for a reason
SayWhat10 said:
how to "check out the scripts and see what they do"?
directions say to just flash it
theres no written explanation of all the tweaks somewhere?
Click to expand...
Click to collapse
I'm sure you can.extract the zip file and inside you'll find text files with the tweaks or such.
Sent from my PG86100 using Tapatalk
Hmmmm....curious...
#SWAG!!!
@ dalvik tweaks
I see a lot of different settings people either go with 32 or 64. On my ROMS I run 48 and am happy with that. I may give 64 a go and see what it does.
@OP - Good job!
smokin1337 said:
Whats a good setting ? Seemed ok to me i read some that said higher is better and some said lower is better. Neither seemed to make much difference so i left it high.
Click to expand...
Click to collapse
The best setting is about 48MB. If it is too big then it takes a long time for the garbage collector to do its thing and the cache can grow to really large levels after you have been running the phone for a while. 48 is a good balance because it allows more space to be used for apps, but isnt so large that the cache's grow crazy big.
Hello, Im useing this script http://forum.xda-developers.com/showthread.php?t=951274 to install JIT, DualTouch, etc.
I have some update for .sh script.
In JIT installation part:
Code:
echo "Backing up build.prob file"
busybox cp -f /system/build.prop /system/build.prop.stock
echo "Copying build.prop to /system/"
busybox cp -f data/jit/build.prop /system/build.prop
Here script rename system build.prop file to build.prop.stock and copy new build.prop from script folder to system.
And in JIT deinstallation part:
Code:
echo "Copying libraries and build.prop to /system/"
...
busybox cp -f data/jit/disable/build.prop /system/build.prop
And here script copy new build.prop from script folder to system.
BUT!
In deinstallation we need to get back our stock build.prop what was renamed in installation part!
So, i suggest to change
Code:
busybox cp -f data/jit/disable/build.prop /system/build.prop
to
Code:
busybox mv -f system/build.prop.stock system/build.prop
to rename build.prop.stock to build.prop.
And why did we copy/past this build.prop files? Why we cant copy stock build.prop and edit it this way:
Code:
echo "#DEVICE_PROVISIONED=1" >> /system/build.prop
echo "dalvik.vm.heapsize=30m" >> /system/build.prop
echo "#kernel.log=default" >> /system/build.prop
echo "dalvik.vm.execution-mode=int:jit" >> /system/build.prop
What do you think?
And sorry, I cant post this to Development forum because I have < 10 posts.
Iam searching in Google for help and so i find your Post here.
Maybe u can help me a bit.
I have a GalaxyNexus.
I have a Build.prop with and one without Tablet Mode.
I like to use sometimes TabletMode and sometimes not.
I think with a Script like u use here i can change what build.prop to use.
Lets say i have the "build.prop" with TabletMode and a "build.prop.stock" without that Mode.
How can i make it possible to activate the .stock and dissable the TabletMode. And then again the other way arround. ???
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.
BUILD PROP
Hey whats up everyone
I would like to present some of the tweaks i compiled and i called them Xtreme Tweaks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First of all i would like to say that am not a developer and i just make tweaks and roms for personal use so i thought i might i as well share this.
Note:This is still V1 so you will probably get some bugs but as for me i have not noticed any.
Xtreme will give you max perfomance and and its main job is to take out all kind of bugs. Its still in beta but it will get stronger and stronger every update. So enjoy the power of XTREME.
To make these tweaks work
*First you need root
*Get any root file manager
*Copy these lines to system/build.prop
Code:
##----Xtreme Tweaks-----###
debug.composition.type=gpu
debug.egl.hw=1
debug.egl.profiler=1
debug.sf.hw=1
debug.enabletr=1
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
com.qc.hardware=true
ro.HOME_APP_ADJ=1
ENFORCE_PROCESS_LIMIT=falso
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
persist.sys.purgeable_assets=1
windowsmgr.max_events_per_sec=90
dev.pm.dyn_samplingrate=1
debug.overlayui.enable=1
debug.qc.hardware=true
ro.ril.sensor.sleep.control=1
##--- Video, Sound and Media Tweaks----###
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=fasle
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.jpeg.quality=100
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
ro.media.cam.preview.fps=0
ro.media.enc.hprof.vid.fps=60
ro.media.codec_priority_for_thumb=so
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
##----- Perfomance----Tweaks-###
video.accelerate.hw=1
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
persist.sys.NV_FPSLIMIT=60
persist.sys.ui.hw=1
ro.service.swiqi2.supported=true
persist.service.swiqi2.enable=1
##---- Dalvik---Tweaks----###
dalvik.vm.dexopt-data-only=1
dalvik.vm.jmiopts=forcecopy
dalvik.vm.dexopt-flags=m=v, 0=y
dalvik.vm.execution-mode=init:jit
dalvik.gc.type=precise
dalvik.vm.verify-bytecode=false
dalvik.vm.heapstartsize=6m
dalvik.vm.heapgrowthlimit.48m
dalvik.vm.heapsize.64m
## Testing Tweaks### -----NOT ALL OF THEM ARE FOR TESTING SOME WILL WORK----######
ro.void.umsdirtyratio=20
persist.service.pcsync.enable=0
persist.service.lgospd.enable=0
wifi.supplicant_scan_interval=180
ro.sf.compbypass.enable=1
ro.min_pointer_dur=1
debug.gr.swapinterval=0
persist.android.strictmode=0
persist.sampling_profiler=0
ro.fb.mode=1
hw3d.force=1
ro.wifi.hotspotUI=1
persist.sys.composition.type=gpu
ro.PERCEPTIBLE_APP_ADJ=2
ring.delay=0
ro.tether.denied=false
##--- Miscalleneous Tweaks#### -----Not all of them will work----#####
mot.proximity.delay=25
ro.mot.buttonlight.timeout=0
persist.sys.shutdown.mode=hibernate
ro.config.hw_quickpoweron=true
persist.adb.notify=0
persist.service.adb.enable=1
windowsmgr.support_rotation_270=true
ro.telephony.call_ring.delay=0
touch.pressure.scale=0.001
ro.lge.proximity.delay=25
## Internet and Data and Signal Tweaks####
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
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
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.hspda=4096,87380,256960,4096,16 384,256960
net.tcp.buffersize.hspa=4096,87380,256960,4096,163 84,256960
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
ro.config.nocheckin=1
persist.cust.tel.eons=1
ro.ril.gprsclass=10
ro.ril.hsdpa.category=8
ro.ril.hsupa.category=6
ro.ril.hsxpa=1
###---- Battery Saving Tweaks----- ###
pm.sleep_mode=1
usb_wakeup=enable
proximity_incall=enable
power_supply.wakeup=enable
ro.config.hw_power_saving=1
ro.config.hw_fast_dormancy=1
persist.sys.use_dithering=0
ro.mot.eri.losalert.delay=1000
ro.ril.disable.power.collapse=1
###-- Xloud, Sound Enhancements and Drivers--- ###
ro.semc.sound_effects_enabled=true
ro.semc.xloud.supported=true
persist.service.xloud.enable=1
ro.semc.enhance.supported=true
persist.service.enhance.enable=1
ro.semc.clearaudio.supported=true
persist.service.clearaudio.enable=1
ro.sony.walkman.logger=1
ro.somc.clearphase.supported=true
persist.service.clearphase.enable=1
af.resampler.quality=255
persist.af.resampler.quality=255
htc.audio.swalt.enable=1
htc.audio.swalt.mingain=14512
Reboot and enjoy EXTREME!!!!!!
I made sure that there are no double lines and most of the tweaks work very well and give me lots of power too.
Here is my benchmark locked bootloader running the custom rom i made ExPeria NYC;
Please give feedback so i can improve this more and more
SCRIPT
These are some of the scripts i made that work along with the build prop tweaks and give you max perfomance. So enjoy the scripts and build prop tweaks and see your Phone get XTREME.
First of all delete other scripts in init.d in systme/etc/init.d as it may be incompatible
10XpoWer
Script is mainly like for speed and other important stuff.
It includes;
[*]Increasing SdCard reading Speed
[*]Removes logger for locked Bls
[*]Battery Calliberation
[*]Battery Tweaks
[*]And increases Cache size
12Xtreme
This is also for more perfomance and works together with 10XpoWer so if you want more speed and everything use it together with the other.
It includes;
[*]MinFree Handler
[*]Internet Enhancement
[*]Dalvik Management
[*]And Battery stats
[*]And Many more
102XtremeSupport
This script is based on TopDroid's script for project butter but i just changed some stuff and values.
This supports the above scripts and give more perfomance and i do recommend this because it gave me lots of boost and i dont have bugs
Download the file Here ----->http://d-h.st/U7h
As i have already said these scripts were compiled by me so they so if you use them together with the build prop tweaks you will get XTREME POWER perfomance.
Installation [Its not yet a flashable zip]
Download the zip folder
Exract it
Move 10XpoWer to system/etc/init.d
move 12Xtreme to system/etc/init.d
Set permissions to rwxrwxrwx
REBOOT
Downloads
Download here ------>>>>>Click Me
Credits
XtremeSilencer -------> i used some of his posts on scripts
Mv_Style for helping correct last tweaks
TopDroid becaused i based 102XtremeSupport on his script
If you feel like you need to be here PM Me and i will fix it ASAP
CHANGELOG
V1- Beta
** Initial Release**
Updates soon...
V1 beta2
**Fixed old tweaks**
**Removed double lines**
**Added New tweaks whick give better perfomance**
**More stronger than beta1**
**Added 102XtremeSupport**
Banners
if you would like to show support just add these simple banners to your signature thanks.
Re: [09-02-13]Xtreme Tweaks V1-Beta[Build Prop]
have any idea if these tweaks will work on the htc amaze?
sent from the droid you arnt looking for.
SpiritFyre said:
have any idea if these tweaks will work on the htc amaze?
sent from the droid you arnt looking for.
Click to expand...
Click to collapse
yes build.prop is universal
but some are specific to lg, htc, se or qualcomm devices
Re: [09-02-13]Xtreme Tweaks V1-Beta[Build Prop]
SpiritFyre said:
have any idea if these tweaks will work on the htc amaze?
sent from the droid you arnt looking for.
Click to expand...
Click to collapse
These are various tweaks from different devices added up all together so yeah it might work
Sent from my SK17i using xda premium
The installation of the cwm
The backup build.prop
http://www.mediafire.com/?2j6dbbosi70so7d
backup_buildprop
#!/sbin/sh
mkdir /sdcard/MoHaMaD
cp /system/build.prop /sdcard/MoHaMaD/build.backup.prop
Click to expand...
Click to collapse
MoHaMaD_tweaks
echo "## Build.prop tweaks edit MoHaMaD##" >> /system/build.prop
echo "#3G Tweaks" >> /system/build.prop
echo "ro.ril.hsxpa=2" >> /system/build.prop
echo "ro.ril.gprsclass=10" >> /system/build.prop
echo "ro.ril.hep=1" >> /system/build.prop
echo "ro.ril.enable.dtm=1" >> /system/build.prop
echo "ro.ril.hsdpa.category=10" >> /system/build.prop
echo "ro.ril.enable.a53=1" >> /system/build.prop
echo "ro.ril.enable.3g.prefix=1" >> /system/build.prop
echo "ro.ril.htcmaskw1.bitmask=4294967295" >> /system/build.prop
echo "ro.ril.htcmaskw1=14449" >> /system/build.prop
echo "ro.ril.hsupa.category=5" >> /system/build.prop
echo "# Saves some battery without reducing performances" >> /system/build.prop
echo "wifi.supplicant_scan_interval=180" >> /system/build.prop
echo "pm.sleep_mode=1" >> /system/build.prop
echo "ro.ril.disable.power.collapse=0" >> /system/build.prop
echo "# Increase camera's photo and video recording quality" >> /system/build.prop
echo "ro.media.dec.jpeg.memcap=8000000" >> /system/build.prop
echo "ro.media.enc.hprof.vid.bps=8000000" >> /system/build.prop
echo "# Connect and disconnect faster (experimental)" >> /system/build.prop
echo "ro.mot.eri.losalert.delay=1000" >> /system/build.prop
echo "# More free ram and apps load faster" >> /system/build.prop
echo "dalvik.vm.dexopt-flags=m=y" >> /system/build.prop
echo "# Reduce dial-out time" >> /system/build.prop
echo "ro.telephony.call_ring.delay=0" >> /system/build.prop
echo "# Video Acceleration Enabled" >> /system/build.prop
echo "video.accelerate.hw=1" >> /system/build.prop
echo "# Increase jpg quality to 100%" >> /system/build.prop
echo "ro.media.enc.jpeg.quality=100" >> /system/build.prop
echo "# Disable Kernel Error Checking" >> /system/build.prop
echo "ro.kernel.android.checkjni=0" >> /system/build.prop
echo "ro.kernel.checkjni=0" >> /system/build.prop
echo "# Keep launcher in memory to reduce redraws" >> /system/build.prop
echo "ro.HOME_APP_ADJ=1" >> /system/build.prop
echo "# Better internet browsing & download speed" >> /system/build.prop
echo "net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960" >> /system/build.prop
echo "net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960" >> /system/build.prop
echo "net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960" >> /system/build.prop
echo "net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960" >> /system/build.prop
echo "net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960" >> /system/build.prop
echo "# Render UI with GPU" >> /system/build.prop
echo "debug.sf.hw=1" >> /system/build.prop
echo "# Increase general Performance" >> /system/build.prop
echo "debug.performance.tuning=1" >> /system/build.prop
echo "# Reduce the black screen time of the proximity sensor" >> /system/build.prop
echo "ro.lge.proximity.delay=25" >> /system/build.prop
echo "mot.proximity.delay=25" >> /system/build.prop
echo "# Allow purge of assets to free more ram" >> /system/build.prop
echo "persist.sys.purgeable_assets=1" >> /system/build.prop
echo "# Better Scrolling responsiveness and speed" >> /system/build.prop
echo "windowsmgr.max_events_per_sec=150" >> /system/build.prop
echo "ro.max.fling_velocity=12000" >> /system/build.prop
echo "ro.min.fling_velocity=8000" >> /system/build.prop
echo "# Smoother video streaming" >> /system/build.prop
echo "media.stagefright.enable-player=true" >> /system/build.prop
echo "media.stagefright.enable-meta=true" >> /system/build.prop
echo "media.stagefright.enable-scan=false" >> /system/build.prop
echo "media.stagefright.enable-http=true" >> /system/build.prop
echo "ENFORCE_PROCESS_LIMIT=false" >> /system/build.prop
echo "MAX_SERVICE_INACTIVITY=false" >> /system/build.prop
echo "MIN_HIDDEN_APPS=false" >> /system/build.prop
echo "MAX_HIDDEN_APPS=false" >> /system/build.prop
echo "CONTENT_APP_IDLE_OFFSET=false" >> /system/build.prop
echo "EMPTY_APP_IDLE_OFFSET=false" >> /system/build.prop
echo "MAX_ACTIVITIES=false" >> /system/build.prop
echo "ACTIVITY_INACTIVE_RESET_TIME=false" >> /system/build.prop
echo "MAX_RECENT_TASKS=false" >> /system/build.prop
echo "MIN_RECENT_TASKS=false" >> /system/build.prop
echo "APP_SWITCH_DELAY_TIME=false" >> /system/build.prop
echo "MAX_PROCESSES=false" >> /system/build.prop
echo "PROC_START_TIMEOUT=false" >> /system/build.prop
echo "CPU_MIN_CHECK_DURATION=false" >> /system/build.prop
echo "GC_TIMEOUT=false" >> /system/build.prop
echo "SERVICE_TIMEOUT=false" >> /system/build.prop
echo "MIN_CRASH_INTERVAL=false" >> /system/build.prop
Click to expand...
Click to collapse
One question, what hapends when a line is already present in the build.prop?
adrianjos said:
One question, what hapends when a line is already present in the build.prop?
Click to expand...
Click to collapse
Might as well delete mine or the one you have your choice
Yeah but when i forget one? Will everything work?
Re: [09-02-13]Xtreme Tweaks V1-Beta[Build Prop+Scripts][Xtreme Power, SuperFast]
adrianjos said:
Yeah but when i forget one? Will everything work?
Click to expand...
Click to collapse
Yeah everything will work
Sent from my SK17i using xda premium
As per the developers request this thread has been added to
Scripts
.
Re: [09-02-13]Xtreme Tweaks V1-Beta[Build Prop+Scripts][Xtreme Power, SuperFast]
thank you. my sig says it all.
sent from the droid you arnt looking for. because im using Xtreme Tweaks.
Re: [09-02-13]Xtreme Tweaks V1-Beta[Build Prop+Scripts][Xtreme Power, SuperFast]
SpiritFyre said:
thank you. my sig says it all.
sent from the droid you arnt looking for. because im using Xtreme Tweaks.
Click to expand...
Click to collapse
Thanks for trying it out and for feedback
Sent from my SK17i using xda premium
Re: [09-02-13]Xtreme Tweaks V1-Beta[Build Prop+Scripts][Xtreme Power, SuperFast]
you are up pretty late lol. im waiting to run these tweaks on viper rom when its released for the amaze. your tweaks also returned stability to my keyboard
sent from the droid you arnt looking for. because im nrgized with Xtreme Tweaks and faux v26 kernel
they are some double lines
and some of them dont work on ics/jb
and some of them dont work at all
here you can see which dont work
Re: [09-02-13]Xtreme Tweaks V1-Beta[Build Prop+Scripts][Xtreme Power, SuperFast]
mv_style said:
they are some double lines
and some of them dont work on ics/jb
and some of them dont work at all
here you can see which dont work
Click to expand...
Click to collapse
Cheers for the heads up i will fix it ASAP
Sent from my SK17i using xda premium
Good work my friend!
I try it now on CM10. :good:
I have updated the build.prop tweaks and added one more script.
Sent from my SK17i
Everything is fine
Sent from my SK17i using xda premium
Preface:
Worthwhile to know is that WSA is a Hosted OS what runs on Top Of Windows OS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so it shares all hardware resources with Windows OS, really all.
As in every Android OS - so also in WSA emulator - exist files what contain all the important information and command lines to identify the device and to make it run smoothly along side, they basically are named build.prop and/or default.prop and may be located in different partitions. These setting files are read by the Android kernel and also by apps thus they can mend their interface and their functionality to have a smooth interface between user and apps. These files also contain the build number, manufacturer name and other essential information to identify the emulated Android device distinctly.
In WSA w/ Android 11 image these settings are split into several files what are scattered over various locations: root, root/vendor and root/product. In WSA w/ Android 13 image these settings also are split into several files what are scattered over into 2 locations: root, root/vendor.
Prerequisite:
WSA's Android image must got rooted. This in order to can mount the related partitions where the settings files are housed as RW.
Overview:
Android settings in WSA w/ Android 11 image:
For those who are interested in these setting files I've extracted them from WSA w/ Android 11 image and attached:
File: /build.prop -> attached build.prop.zip
Here is printout of this build.prop file
Spoiler
# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.system.build.date=Tue Aug 24 22:34:56 UTC 2021
ro.system.build.date.utc=1629844496
ro.system.build.fingerprint=google/redfin/redfin:12/SPB5.210812.002/7671067:user/release-keys
ro.system.build.id=SPB5.210812.002
ro.system.build.tags=release-keys
ro.system.build.type=user
ro.system.build.version.incremental=7671067
ro.system.build.version.release=11
ro.system.build.version.release_or_codename=11
ro.system.build.version.sdk=30
ro.product.system.brand=google
ro.product.system.device=generic
ro.product.system.manufacturer=Google
ro.product.system.model=mainline
ro.product.system.name=mainline
# end common build properties
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=SPB5.210812.002
ro.build.display.id=SPB5.210812.002
ro.build.version.incremental=7671067
ro.build.version.sdk=30
ro.build.version.preview_sdk=0
ro.build.version.preview_sdk_fingerprint=REL
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=11
ro.build.version.release_or_codename=11
ro.build.version.security_patch=2021-09-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=23
ro.build.date=Tue Aug 24 22:34:56 UTC 2021
ro.build.date.utc=1629844496
ro.build.type=user
ro.build.user=android-build
ro.build.host=abfarm807
ro.build.tags=release-keys
ro.build.flavor=redfin-user
ro.build.system_root_image=false
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86_64
ro.product.cpu.abilist=x86_64,x86,arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=x86_64,arm64-v8a
ro.product.locale=en-US
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=redfin
# Do not try to parse description or thumbprint
ro.build.description=redfin-user 12 SPB5.210812.002 7671067 release-keys
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.treble.enabled=true
net.bt.name=Android
ro.build.fingerprint=google/redfin/redfin:12/SPB5.210812.002/7671067:user/release-keys
ro.product.brand=google
ro.product.device=redfin
ro.product.manufacturer=Google
ro.product.model=Pixel 5
ro.product.name=redfin
File: /default.prop -> attached default.prop.zip
File: /vendor/build.prop -> attached vendor.build.prop..zip
File: /vendor/default.prop -> attached vendor.default.prop.zip
File: /product/build.prop -> attached product.build.prop,zip
In WSA w/ Android 11 image also additionally exists file prop.default what isn't of interest here: it's merely a backup of file root/default.prop.
Android settings in WSA w/ Android 13 image:
In WSA w/ Android 13 image only 2 file /build.prop & /vendor/build.prop exist.
File: /build.prop -> attached 13-build.prop.zip
Here is printout of this build.prop file - extracted from WSA w/ Android 13 image
Spoiler
####################################
# from generate-common-build-props
# These properties identify this partition image.
####################################
ro.product.system.brand=google
ro.product.system.device=redfin
ro.product.system.manufacturer=Google
ro.product.system.model=Pixel 5
ro.product.system.name=redfin
ro.system.product.cpu.abilist=x86_64,x86,arm64-v8a,armeabi-v7a,armeabi
ro.system.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.system.product.cpu.abilist64=x86_64,arm64-v8a
ro.system.build.date=Wed Dec 14 02:14:23 UTC 2022
ro.system.build.date.utc=1670984063
ro.system.build.fingerprint=google/redfin/redfin:13/TP1A.221105.002/2211.40000.10.0:user/release-keys
ro.system.build.id=TP1A.221105.002
ro.system.build.tags=release-keys
ro.system.build.type=user
ro.system.build.version.incremental=2211.40000.10.0
ro.system.build.version.release=13
ro.system.build.version.release_or_codename=13
ro.system.build.version.sdk=33
####################################
# from out/target/product/windows_x86_64/obj/PACKAGING/system_build_prop_intermediates/buildinfo.prop
####################################
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=TP1A.221105.002
ro.build.display.id=TP1A.221105.002
ro.build.version.incremental=2211.40000.10.0
ro.build.version.sdk=33
ro.build.version.preview_sdk=0
ro.build.version.preview_sdk_fingerprint=REL
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.known_codenames=Base,Base11,Cupcake,Donut,Eclair,Eclair01,EclairMr1,Froyo,Gingerbread,GingerbreadMr1,Honeycomb,HoneycombMr1,HoneycombMr2,IceCreamSandwich,IceCreamSandwichMr1,JellyBean,JellyBeanMr1,JellyBeanMr2,Kitkat,KitkatWatch,Lollipop,LollipopMr1,M,N,NMr1,O,OMr1,P,Q,R,S,Sv2,Tiramisu
ro.build.version.release=13
ro.build.version.release_or_codename=13
ro.build.version.release_or_preview_display=13
ro.build.version.security_patch=2022-11-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=23
ro.build.date=Wed Dec 14 02:14:23 UTC 2022
ro.build.date.utc=1670984063
ro.build.type=user
ro.build.user=cloudtest
ro.build.host=8f3cde02c000000
ro.build.tags=release-keys
ro.build.flavor=redfin-user
ro.build.system_root_image=false
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86_64
ro.product.locale=en-US
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=redfin
# Do not try to parse description or thumbprint
ro.build.description=redfin-user 13 TP1A.221105.002 2211.40000.10.0 release-keys
# end build properties
####################################
# from variable ADDITIONAL_SYSTEM_PROPERTIES
####################################
ro.treble.enabled=true
ro.actionable_compatible_property.enabled=true
ro.postinstall.fstab.prefix=/system
ro.secure=1
security.perf_harden=1
ro.adb.secure=1
ro.allow.mock.location=0
ro.debuggable=0
net.bt.name=Android
####################################
# from variable PRODUCT_SYSTEM_PROPERTIES
####################################
debug.atrace.tags.enableflags=0
persist.traced.enable=1
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.usejit=true
dalvik.vm.usejitprofiles=true
dalvik.vm.dexopt.secondary=true
dalvik.vm.dexopt.thermal-cutoff=2
dalvik.vm.appimageformat=lz4
ro.dalvik.vm.native.bridge=0
pm.dexopt.first-boot=verify
pm.dexopt.boot-after-ota=verify
pm.dexopt.post-boot=extract
pm.dexopt.install=speed-profile
pm.dexopt.install-fast=skip
pm.dexopt.install-bulk=speed-profile
pm.dexopt.install-bulk-secondary=verify
pm.dexopt.install-bulk-downgraded=verify
pm.dexopt.install-bulk-secondary-downgraded=extract
pm.dexopt.bg-dexopt=speed-profile
pm.dexopt.ab-ota=speed-profile
pm.dexopt.inactive=verify
pm.dexopt.cmdline=verify
pm.dexopt.shared=speed
dalvik.vm.dex2oat-resolve-startup-strings=true
dalvik.vm.dex2oat-max-image-block-size=524288
dalvik.vm.minidebuginfo=true
dalvik.vm.dex2oat-minidebuginfo=true
dalvik.vm.madvise.vdexfile.size=104857600
dalvik.vm.madvise.odexfile.size=104857600
dalvik.vm.madvise.artfile.size=4294967295
####################################
# from variable PRODUCT_SYSTEM_DEFAULT_PROPERTIES
####################################
# end of file
# extra prop added by MagiskOnWSA
ro.product.brand=google
ro.product.manufacturer=Google
ro.system.build.product=redfin
ro.product.name=redfin
ro.product.device=redfin
ro.product.model=Pixel 5
ro.system.build.flavor=redfin-user
ro.build.fingerprint=google/redfin/redfin:13/TP1A.221105.002/2211.40000.10.0:user/release-keys
ro.system.build.description=redfin-user 13 TP1A.221105.002 2211.40000.10.0 release-keys
ro.bootimage.build.fingerprint=google/redfin/redfin:13/TP1A.221105.002/2211.40000.10.0:user/release-keys
File: /vendor/build.prop -> attached 13-vendor.build.prop.zip
Here is printout of this build.prop file - extracted from WSA w/ Android 13 image
Spoiler
####################################
# from generate-common-build-props
# These properties identify this partition image.
####################################
ro.product.vendor.brand=google
ro.product.vendor.device=redfin
ro.product.vendor.manufacturer=Google
ro.product.vendor.model=Pixel 5
ro.product.vendor.name=redfin
ro.vendor.product.cpu.abilist=x86_64,x86,arm64-v8a,armeabi-v7a,armeabi
ro.vendor.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.vendor.product.cpu.abilist64=x86_64,arm64-v8a
ro.vendor.build.date=Wed Dec 14 02:14:23 UTC 2022
ro.vendor.build.date.utc=1670984063
ro.vendor.build.fingerprint=google/redfin/redfin:13/TP1A.221105.002/2211.40000.10.0:user/release-keys
ro.vendor.build.id=TP1A.221105.002
ro.vendor.build.tags=release-keys
ro.vendor.build.type=user
ro.vendor.build.version.incremental=2211.40000.10.0
ro.vendor.build.version.release=13
ro.vendor.build.version.release_or_codename=13
ro.vendor.build.version.sdk=33
####################################
# from out/target/product/windows_x86_64/obj/ETC/android_info_prop_intermediates/android_info.prop
####################################
####################################
# from variable ADDITIONAL_VENDOR_PROPERTIES
####################################
ro.vndk.version=33
ro.bionic.arch=x86_64
ro.bionic.cpu_variant=
ro.bionic.2nd_arch=x86
ro.bionic.2nd_cpu_variant=
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.x86_64.variant=x86_64
dalvik.vm.isa.x86_64.features=default
dalvik.vm.isa.x86.variant=x86_64
dalvik.vm.isa.x86.features=default
ro.boot.dynamic_partitions=true
ro.product.first_api_level=30
ro.vendor.build.security_patch=
ro.product.board=windows
ro.board.platform=windows
ro.hwui.use_vulkan=
####################################
# from variable PRODUCT_VENDOR_PROPERTIES
####################################
ro.zygote=zygote64_32
# Removed by post_process_props.py because overridden by ro.zygote=zygote64_32
#ro.zygote?=zygote32
ro.logd.size.stats=64K
log.tag.stats_log=I
ro.carrier=unknown
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.apex.updatable=true
init.userspace_reboot.is_supported=true
ro.virtual_ab.enabled=true
external_storage.projid.enabled=1
external_storage.casefold.enabled=1
external_storage.sdcardfs.enabled=0
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
drm.service.enabled=true
wifi.interface=wlan0
####################################
# from variable PRODUCT_DEFAULT_PROPERTY_OVERRIDES
####################################
ro.dalvik.vm.native.bridge=libhoudini.so
####################################
# from variable PRODUCT_PROPERTY_OVERRIDES
####################################
ro.control_privapp_permissions=enforce
debug.sf.nobootanimation=1
ro.opengles.version=196608
debug.stagefright.ccodec=0
debug.latte.hwcodec.avcdec=2
debug.latte.hwcodec.hevcdec=2
debug.latte.hwcodec.vp8dec=2
debug.latte.hwcodec.vp9dec=2
debug.latte.hwcodec.mp4vdec=2
debug.latte.hwcodec.av1dec=2
debug.latte.hwcodec.h263dec=2
debug.latte.hwcodec.mpeg2dec=2
debug.hwui.disable_disk_cache=1
ro.hardware.egl=emulation
ro.surface_flinger.running_without_sync_framework=true
debug.sf.vsync_reactor_ignore_present_fences=true
service.sf.prime_shader_cache=0
ro.hardware.audio.primary=windows
vendor.bt.rootcanal_test_console=off
ro.incremental.enable=true
ro.dalvik.vm.isa.arm=x86
ro.vendor.enable.native.bridge.exec=1
ro.dalvik.vm.isa.arm64=x86_64
ro.vendor.enable.native.bridge.exec64=1
# end of file
# extra prop added by MagiskOnWSA
ro.product.brand=google
ro.product.manufacturer=Google
ro.build.product=redfin
ro.vendor.build.product=redfin
ro.product.name=redfin
ro.product.device=redfin
ro.product.model=Pixel 5
ro.build.flavor=redfin-user
ro.vendor.build.flavor=redfin-user
ro.build.description=redfin-user 13 TP1A.221105.002 2211.40000.10.0 release-keys
ro.build.fingerprint=google/redfin/redfin:13/TP1A.221105.002/2211.40000.10.0:user/release-keys
ro.vendor.build.description=redfin-user 13 TP1A.221105.002 2211.40000.10.0 release-keys
ro.bootimage.build.fingerprint=google/redfin/redfin:13/TP1A.221105.002/2211.40000.10.0:user/release-keys
Take note that settings stored in /vendor/build.prop files take precedence over those stored in default.prop and/or /system/build.prop if they also exist there.
As one can notice contents of build.prop as provided w/ Android 11 image and w/ Android 13 image heavily differ.
Tweaking - Relates to WSA w/ Android 13 image:
We all know Android is the best platform that offers to customize everything. Each operating system has its own config file and All function is stored in the build. prop file, but also in /vendor/build.prop. So changing the /vendor/build. prop file will change the WSA core functioning values. You can tweak your WSA without installing any 3rd party apps or mods, just need root access to edit /vendor/build. prop on WSA emulator.
We know that WSA isn't a smartphone, it's merely an Android emulator that can connect to computer's local Wi-Fi network, hence it's not so much what can get tweaked. But we can try it:
1. Raise RAM Useable by App
Android limits memory per process. Todays apps often require hundreds of MBs of available RAM for exclusive use to flawlessly run. So we give them ( at maximum ) 512 MB - alike Samsung Galaxy S6 SM-G920W8.
dalvik.vm.dex2oat-Xmx=512m
2. Improves Recording Quality.Most of the WSA user wants the best audio and video quality in this emulator. This code in /vendor/build.prop will improve audio and video recording quality. After applying this code the WSA recording may give better clear and louder quality sound.
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.capture.maxres=8m
ro.media.panorama.defres=3264×1840
ro.media.panorama.frameres=1280×720
ro.camcorder.videoModes=true
ro.media.enc.hprof.vid.fps=65
3. Improve Network Speed.If you are facing low network speed? You can overall increase network speed on your emulated Android device by increasing the TCP’s Buffersize. When you are browsing the internet on the android device, Your net has been directly connected with the google DNS. Paste the following code at the bottom of the /vendor/build.prop.
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
net.dns1=8.8.8.8
net.dns2=8.8.4.4
4. Disable built-in error reporting.Every Android user always faces with the Apps crash. After apps crashing, we all noticed a pop-up like Error-Reporting is showing on the screen. It too much annoying for the many users. If you feel this is too much annoying for you and want to disable built-in error reporting features then add the code to the end at the /vendor/build.prop file.
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
5. Change DPI on the emulated Android device.Changing DPI is one of the most useful build.prop for Android users. DPI refers to the Density Independent on the emulated device. You can find many apps in Google Playstore to change this setting but here you can directly tweak DPI on Android. If you set high amount of value in DPI then the output is smaller UI, smaller texts, smaller icons.
If you set low DPI then the output is a larger UI, larger texts, and larger icons. Always set a perfect DPI otherwise you can’t operate WSA. Add the following line to the end of the /vendor/build.prop.
ro.sf.lcd_density=XXX
Here, XXX refers to the DPI Value. The values are a multiple of 160, That is, 160, 320, 480, 640, etc. XXX replace with a value you like.
6. Disable Android logger – logcatEvery Android device records Android log. It basically stores application and portions logs in the system. It displays messages in real time and keeps a history so you can view older messages. So if you want to Disable Android logger then add the the following line to the end of the /vendor/build.prop.
logcat.live=disable
7. Make sure USB-MTP mode is enabled.
Add the following line to the end of the /vendor/build.prop.
persist.sys.usb.config=adb,mtp
8. Ensure ADB is debuggable
Add the following lines to the end of the /vendor/build.prop.
persist.service.adb.enable=1
persist.service.debuggable1
9. Enable Faster boot.
Paste the following code at the bottom of the /vendor/build.prop:
ro.config.hw_quickpoweron=true
persist.sys.shutdown.mode=hibernate
10. Improve the speed of video streaming.
Add the following lines to the bottom of the /vendor/build.prop:
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-rtsp=true
media.stagefright.enable-record=false
11. Set Wireless & TCP Speed.
Paste the following code at the bottom of the /vendor/build.prop:
net.core.wmem_max=1048576
net.core.rmem_max=1048576
net.core.rmem_default=262144
net.core.wmem_default=262144
net.core.optmem_max=20480
net.unix.max_dgram_qlen=50
12. Set number of CPU-cores to be used
It should be well known that WSA emulator shares the Windows computer's hardware resources, so both RAM and CPU. The RAM usage is fixed to 4 GB ( what can't be changed AFAIK ), the number of virtual CPU cores is not. We may have to configure how the virtual CPUs are assigned in terms of real CPU cores and cores per socket,
Note: You may use Windows Command Prompt to get the number of real CPU cores
IMO it's recommnded to determine the half of real CPU cores as virtual CPU cores. Example:
ro.core_ctl_min_cpu=1
ro.core_ctl_max_cpu=4
Conclusion:
I’m sure that several people will try out tweaking WSA settings as mentioned above. For that reason I've created a batch file named wsa_buildprop_tweaker that'll do the job:
Spoiler
Code:
@echo off & setlocal DISABLEDELAYEDEXPANSION
adb disconnect 2>nul
adb connect 127.0.0.1:58526
adb devices
cls
echo Going to tweak Android system settings...
echo Please keep your computer on
echo(
set "CPU_CORES="
for /F "tokens=*" %%a in ('echo %NUMBER_OF_PROCESSORS%) do (
if NOT "%%a"==[] ( set "CPU_CORES=%X%" )
)
::
:: Open Android terminal
::
adb shell
alias SU='find . -executable -type f -iname "su.*"'
if [ -z "$SU" ] then;
echo "SU ( root ) not found. Exiting...";
sleep 10;
exit 1;
fi;
TMP_SCRIPT='/sdcard/Downloads/tweaker.sh';
if [ ! -f "/system/build.prop" ] then;
echo "File /system/build.prop not found. Exiting...";
sleep 10;
exit 1;
fi;
if [ -f "$TMP_SCRIPT" ] then;
rm -f "$TMP_SCRIPT";
fi;
# mount /sytem as RW
$SU 0 -c "mount -o rw,remount -t auto /system"
# create the script we want to get run
alias TWEAKS='cat << EOF'
echo "########################################" >> /vendor/build.prop; \
echo "# Added by $USER" >> /vendor/build.prop; \
echo "########################################" >> /vendor/build.prop; \
echo "dalvik.vm.dex2oat-Xmx=512m" >> /vendor/build.prop; \
echo "ro.media.enc.jpeg.quality=100" >> /vendor/build.prop; \
echo "ro.media.dec.jpeg.memcap=8000000" >> /vendor/build.prop; \
echo "ro.media.enc.hprof.vid.bps=8000000" >> /system/build.prop, \
echo "ro.media.capture.maxres=8m" >> /vendor/build.prop; \
echo "ro.media.panorama.defres=3264×1840" >> /vendor/build.prop; \
echo "ro.media.panorama.frameres=1280×720" >> /system/build.prop, \
echo "ro.camcorder.videoModes=true" >> /vendor/build.prop; \
echo "ro.media.enc.hprof.vid.fps=65" >> /vendor/build.prop; \
echo "net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960" >> /vendor/build.prop; \
echo "net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960" >> /vendor/build.prop; \
echo "net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960" >> /vendor/build.prop; \
echo "net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960" >> /vendor/build.prop; \
echo "net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960" >> /vendor/build.prop; \
echo "ro.sf.lcd_density=480" >> /vendor/build.prop; \
echo "logcat.live=disable" >> /vendor/build.prop; \
echo "profiler.force_disable_err_rpt=1" >> /vendor/build.prop; \
echo "profiler.force_disable_ulog=1" >> /vendor/build.prop; \
echo "ro.config.hw_quickpoweron=true" >> /vendor/build.prop; \
echo "persist.sys.usb.config=adb,mtp" >> /vendor/build.prop; \
echo "#" >> /vendor/build.prop; \
TWEAKS
# run the created script in ROOT mode
$SU 0 -c 'echo "$TWEAKS" > "$TMP_SCRIPT";source "$TMP_SCRIPT";rm -f "$TMP_SCRIPT" 2>/dev/null;'
# unmount /system
umount -af;
::
:: Close Android terminal
::
exit
if defined CPU_CORES (
setlocal ENABLEDELAYEDEXPANSION
set /A CPU_CORES=!CPU_CORES!/=2
adb shell 'echo "ro.core_ctl_min_cpu=1"' >> /vendor/build.prop; \
adb shell 'echo "ro.core_ctl_max_cpu=!CPU_CORES!"' >> /vendor/build.prop; \
endlocal
)
echo Job completed!
timeout /t 10 /nobreak >nul
# reboot WSA
adb disconnect 2>nul
adb usb
adb reboot
exit
It's for your convenience attached.
Thanks for this.. I'm not getting much luck with the batch file. I get the following, and not sure where the error is.
----------
Going to tweak Android system settings..
Please keep your computer on
The system cannot find the file 'echo 8.
----------
May be I'm struck with blindness: Can't detect "echo 8" phrase in file contents.
jwoegerbauer said:
May be I'm struck with blindness: Can't detect "echo 8" phrase in file contents.
Click to expand...
Click to collapse
Yeah, I couldn't find it either. I'm thinking it has something to do with the virtual cores?
Have you tried the script on Android 13?, It could also be related to that.
PS: Do you know of any setting that can make scrolling smoother?
Thanks
You can try to fix it by modifying the maximum and minimum fluid velocity on WSA, which affect the scrolling speed on WSA.
Example:
Code:
windowsmgr.max_events_per_sec=150
ro.min_pointer_dur=8
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000