• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Build.prop Tweaks

M

mrjello

Member
I see that some of the custom roms have changes to build.prop. What changes are you making and do they really make a difference? I see many tweaks listed online but I question the effectiveness of some of them.
 
mrjello said:
I see that some of the custom roms have changes to build.prop. What changes are you making and do they really make a difference? I see many tweaks listed online but I question the effectiveness of some of them.
Click to expand...

If they're the right ones, they make plenty of difference. One example is the dalvik.vm.heapsize tweak. Normally, that line is dalvik.vm.heapsize=32m. Many of us have tweaked the build.prop so that line is, instead, dalvik.vm.heapsize=64m. I'm too tired to provide a quality wordy description of the difference, but try playing fruit ninja when the value is 32, versus when it's 64. The result is much smoother, higher FPS gameplay.
 
Artine said:
If they're the right ones, they make plenty of difference. One example is the dalvik.vm.heapsize tweak. Normally, that line is dalvik.vm.heapsize=32m. Many of us have tweaked the build.prop so that line is, instead, dalvik.vm.heapsize=64m. I'm too tired to provide a quality wordy description of the difference, but try playing fruit ninja when the value is 32, versus when it's 64. The result is much smoother, higher FPS gameplay.
Click to expand...

From what I understand changing the heap size can potentially make larger apps run more efficiently but could make smaller apps less efficient.

Anything besides heap size worth playing with?
 
You can find a lot of them here - http://forum.xda-developers.com/showthread.php?t=1874269

Harsh7689 said:
General Performance
debug.sf.hw=1
Edit existing line,
dalvik.vm.heapsize=48m
persist.sys.ui.hw=1

Faster Scrolling
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000

Saves power
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
windowsmgr.max_events_per_sec=60 (can be increased to higher values)
wifi.supplicant_scan_interval=180

Raises quality of images
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000


Increased Media & Streaming Performance
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
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.evdo_b=4096,87380,256960,4096,1 6384,256960

Disable sending usage data
ro.config.nocheckin=1


To make the phone ring faster when dialing out
ro.telephony.call_ring.delay=0

Disable black screen issue after call

ro.lge.proximity.delay=25
mot.proximity.delay=25

Disable USB Debugging icon from Status Bar. (Just the Icon, debugging remains enabled.)
persist.adb.notify=0

Makes apps load faster and frees more ram. (Edit exsisting line)

dalvik.vm.dexopt-flags=m=v,o=y

Improve 3g data speeds

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

Update :

Increase the volume steps in-call :

ro.config.vc_call_steps=20

By Default, android offers seven audio levels for calls. This can be altered through this command , if you want to fine adjust the volume of your voice calls. This won
Click to expand...
 
mrjello said:
From what I understand changing the heap size can potentially make larger apps run more efficiently but could make smaller apps less efficient.

Anything besides heap size worth playing with?
Click to expand...

It's made every app I've ever used more efficient, so far as I can tell, at 64.

Otherwise, plenty. See the post above me, for example.
 
Artine said:
It's made every app I've ever used more efficient, so far as I can tell, at 64.

Otherwise, plenty. See the post above me, for example.
Click to expand...

From what I've learned the heapsize is set by the hardware to where there is a limit. If this is the case increasing it won't necessarily do anything unless the value is supported by the device. Also doing so won't give you noticeable performance boosts (could be wring about that ) but will help larger apps have a bit mire wiggle room.

I've actually decreased the size from 48 to 36 in my test build of TheLGE and I've had increased performance all around
 
kenharkey7 said:
From what I've learned the heapsize is set by the hardware to where there is a limit. If this is the case increasing it won't necessarily do anything unless the value is supported by the device. Also doing so won't give you noticeable performance boosts (could be wring about that ) but will help larger apps have a bit mire wiggle room.

I've actually decreased the size from 48 to 36 in my test build of TheLGE and I've had increased performance all around
Click to expand...

There is a heapsize limit set by the hardware, and you can go up to that limit via the software. 64 is supported by the OE, and stock is at 32. Try increasing it from 32 to 64, or 48 to 64, and you'll see a large performance boost in apps and games (especially). For example, try Fruit Ninja and/or Temple Run at 32. Now try them at 64. There's a noticeable, big difference in performance. And it does indeed allow larger apps more wiggle room. Since it doesn't appear to harm the device in any way having it higher, I would say that having more wiggle room and better performance at little to no negative consequence, is an improvement.

I've always seen more performance the higher it's set, not lower, though it should never, ever, be higher than 64 (for any device).
 
Artine said:
It doesn't appear to. If it does, it seems to be negligible/not noticeable.
Click to expand...

I think you are right. I just noticed that harmonia defaults to 64 Leslie Ann is good about stability so if there was an issue i don't think she would have used that setting.
 
Artine said:
If they're the right ones, they make plenty of difference. One example is the dalvik.vm.heapsize tweak. Normally, that line is dalvik.vm.heapsize=32m. Many of us have tweaked the build.prop so that line is, instead, dalvik.vm.heapsize=64m. I'm too tired to provide a quality wordy description of the difference, but try playing fruit ninja when the value is 32, versus when it's 64. The result is much smoother, higher FPS gameplay.
Click to expand...

Mine says 256m. Is a bigger no good or smaller?
 
You must log in or register to reply here.
Back
Top Bottom