mahumi
17/09/12, 20:08:27
Hola, alguien ha probado estos "trucos" de supuesta optimización que he encontrado en XDA?.
Mi ingles no es muy bueno y me vuelvo intentando leer los temas y no se que contestan los otros usuarios.
Estos son las modificaciones a un archivo llamado build.prop en system
3. build.prop tweaks ("/system/build.prop" file)
I have used various suggestions as a reference, incl. demandarin's tweaks for the Prime (just search "build.prop tweaks" on xda and read about what these tweaks do). I am still unsure of some of them, e.g. the proper heap size instead of the default 256m (or maybe we should leave it be?). The tweaks I'm using are the following.
If somebody knows the optimal value for "windowsmgr.max_events_per_sec" (scrolling speed), we would all benefit from setting it to that optimal value Somewhere between 150 and 300 should be OK, I believe. Possibly leaving the default value by ASUS (200) is fine - have a look at what BxMxK has found out about this.
Edit: I'm leaving the default heap size, I think it's better for the games.
Lines to EDIT:
dalvik.vm.dexopt-flags=m=v,o=y
windowsmgr.max_events_per_sec=300
# optional: CHANGE SCREEN RESOLUTION / PIXEL DENSITY (so that your screen can become more capacious)
ro.sf.lcd_density = 160
Lines to ADD:
# BATTERY SAVING
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
# UI & GENERAL PERFORMANCE
debug.performance.tuning=1
video.accelerate.hw=1
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.mot.eri.losalert.delay=1000
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
dalvik.vm.execution-mode=int:jit
com.ti.omap_enhancement=true
# force UI to run at 60 fps, just like on the Jelly Bean! (Tegra only)
# this is overriden by power modes and their cpu1.sh, cpu2.sh and cpu3.sh files btw, so be sure to edit them to suit your needs
persist.sys.NV_FPSLIMIT=60
# MEDIA QUALITY & PERFORMANCE
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
ro.media.enc.jpeg.quality=90
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
persist.sys.use_dithering=1
# NETWORK PERFORMANCE
# there are different types of advice here, you can try what work's best for you out of the latter two (just delete all the spaces which xda keeps adding!):
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
#net.tcp.buffersize.wifi=4096,87380,256960,4096,16 384,256960
net.tcp.buffersize.wifi=262144,524288,1048576,2621 44,524288,1048576
# SWITCHING SOME NOTIFICATIONS OFF
# disable sending usage data
ro.config.nocheckin=1
# disable adb notifications
persist.adb.notify=0
# FAST REBOOT
persist.sys.purgeable_assets=1
# you can also unhash this and disable boot animation for faster boot:
# debug.sf.nobootanimation=1
# This is for current, Wi-Fi only version of Infinity of course:
ro.carrier=wifi-only
# Just for those who need it - unhash the following line to make your device run all ADB shell and terminal emulator commands as ROOT by default (use with caution)
# ro.secure=0
3.1. You can edit the build.prop file manually, you can use one of a few apps out there to manage it, but I have found manually mounting the system r/w (and r/o again after changing the file) and editing it through a PC (you can use Dropbox) or the Infinity with the dock most helpful - you can just cp the new file to (remember to make a backup copy of the old file just in case!).
If you like using the term, you can just 'su' and write these commands:
a) R/W before edit:
mount -o rw,remount /system
b) R/O after edit (remember to run 'chmod 644 /system/build.prop' as root before remounting /system R/O):
mount -o ro,remount /system
3.2. Remember to reboot your device after changing the file. Clearing the dalvik-cache won't hurt either.
Edit: Actually I highly recommend wiping the dalvik cache to avoid bootloops (as root: rm /data/dalvik-cache/*) <- and then.reboot
Este es el post completo:
http://forum.xda-developers.com/showthread.php?p=28427614
Mi ingles no es muy bueno y me vuelvo intentando leer los temas y no se que contestan los otros usuarios.
Estos son las modificaciones a un archivo llamado build.prop en system
3. build.prop tweaks ("/system/build.prop" file)
I have used various suggestions as a reference, incl. demandarin's tweaks for the Prime (just search "build.prop tweaks" on xda and read about what these tweaks do). I am still unsure of some of them, e.g. the proper heap size instead of the default 256m (or maybe we should leave it be?). The tweaks I'm using are the following.
If somebody knows the optimal value for "windowsmgr.max_events_per_sec" (scrolling speed), we would all benefit from setting it to that optimal value Somewhere between 150 and 300 should be OK, I believe. Possibly leaving the default value by ASUS (200) is fine - have a look at what BxMxK has found out about this.
Edit: I'm leaving the default heap size, I think it's better for the games.
Lines to EDIT:
dalvik.vm.dexopt-flags=m=v,o=y
windowsmgr.max_events_per_sec=300
# optional: CHANGE SCREEN RESOLUTION / PIXEL DENSITY (so that your screen can become more capacious)
ro.sf.lcd_density = 160
Lines to ADD:
# BATTERY SAVING
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
# UI & GENERAL PERFORMANCE
debug.performance.tuning=1
video.accelerate.hw=1
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.mot.eri.losalert.delay=1000
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
dalvik.vm.execution-mode=int:jit
com.ti.omap_enhancement=true
# force UI to run at 60 fps, just like on the Jelly Bean! (Tegra only)
# this is overriden by power modes and their cpu1.sh, cpu2.sh and cpu3.sh files btw, so be sure to edit them to suit your needs
persist.sys.NV_FPSLIMIT=60
# MEDIA QUALITY & PERFORMANCE
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
ro.media.enc.jpeg.quality=90
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
persist.sys.use_dithering=1
# NETWORK PERFORMANCE
# there are different types of advice here, you can try what work's best for you out of the latter two (just delete all the spaces which xda keeps adding!):
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
#net.tcp.buffersize.wifi=4096,87380,256960,4096,16 384,256960
net.tcp.buffersize.wifi=262144,524288,1048576,2621 44,524288,1048576
# SWITCHING SOME NOTIFICATIONS OFF
# disable sending usage data
ro.config.nocheckin=1
# disable adb notifications
persist.adb.notify=0
# FAST REBOOT
persist.sys.purgeable_assets=1
# you can also unhash this and disable boot animation for faster boot:
# debug.sf.nobootanimation=1
# This is for current, Wi-Fi only version of Infinity of course:
ro.carrier=wifi-only
# Just for those who need it - unhash the following line to make your device run all ADB shell and terminal emulator commands as ROOT by default (use with caution)
# ro.secure=0
3.1. You can edit the build.prop file manually, you can use one of a few apps out there to manage it, but I have found manually mounting the system r/w (and r/o again after changing the file) and editing it through a PC (you can use Dropbox) or the Infinity with the dock most helpful - you can just cp the new file to (remember to make a backup copy of the old file just in case!).
If you like using the term, you can just 'su' and write these commands:
a) R/W before edit:
mount -o rw,remount /system
b) R/O after edit (remember to run 'chmod 644 /system/build.prop' as root before remounting /system R/O):
mount -o ro,remount /system
3.2. Remember to reboot your device after changing the file. Clearing the dalvik-cache won't hurt either.
Edit: Actually I highly recommend wiping the dalvik cache to avoid bootloops (as root: rm /data/dalvik-cache/*) <- and then.reboot
Este es el post completo:
http://forum.xda-developers.com/showthread.php?p=28427614