Database Users

[MOD] Build.Prop Tweaks

I’ve been scouring XDA and the net for some ways to make our phones a little bit better. What I have found is that you can alter your Build.Prop to work to your advantage.
Did you know that if there is an app exclusive to the Droid X and only works for the Droid X (not withstanding hardware issues), we can change our Build.Prop from Milestone XT720 to Droid X (whatever that model number is) and get into the market and download it?
There also other “tweaks” to you Build.Prop that are beneficial in many other ways, Data strength, Video and Camera resolution, GPS lock, Power saves,…
The below is what I have been able to find, save and test for most of our builds on the Milestone XT720, but first…
Choice is something that has been fought for, relinquished, dreamt of and lost. Here in XDA we have a choice to either use on not to use. This is YOUR choice. If YOU decide to use these tweaks, any problems that arise are YOUR responsibility. Now that is out of the way, here you are.
Oh and one other thing:::::::::::Make a backup of at the very least your /system because if something goes awry while editing the Build.Prop, all you have to do is restore your /system, since that is where the Build.Prop is located.
**XT720 Users->I have not tested these on any of the MIUI builds or Fjfalcon's CM7 release (per Sebastiman -all tweaks but camera work on Fjfalcon's CM7).**
Per Fjfalcon some of these are NOT working on [ROM][KANG][2012.01.30] CyanogenMod 7.2.0 RC0 Milestone XT720
If any Devs want to use these, that is cool. Just make sure you put in your OP that they are already on there so no one duplicates them on their Build.Prop.
Motorola XT720 "Stock" Build.Props are located here (thanks to AA1973 and 3rdstring) http://forum.xda-developers.com/show....php?t=1327141
I presume most of us are using Root Explorer or something extremely similar. You just need to have Root access and able to edit the Build.Prop text. I user Root Explore so that is what these are based off.
1, Open "Root Explorer" and click the R/W
2, Go to /system/build.prop.
3, Long-presson Build.Prop and you’ll see a pop up.
4, Text Editor.
5, Type in those few line of words below into the last line of the text then save.
6. Reboot twice
Data Tweaks Increase download/upload/3G speeds
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=0
ro.ril.hsdpa.category=8 (or 10,12,14) Still looking for more of these though.
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=6
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
For some reason XDA won't let me take out the spaces between 4096, 16384. I have edited it twice and it still shows up with the spaces on OP. Should read 4096,16384 for all 5 (default, wifi, umts, gprs and edge) with no space between 6,1 or 16384
For the "ro.ril.hsxpa" ******* 0=UMTS, 1=HSDPA, 2=HSDPA/HSUPA
POWER SAVES
Allows the phone to sleep better
ro.ril.disable.power.collapse=1
Saves power when phone is sleep
pm.sleep_mode=1
Allows your wifi to scan less, saving more battery
wifi.supplicant_scan_interval=150 or 180 (your choice)
Helps Scrolling Responsiveness
windowsmgr.max_events_per_sec=150
Increase overal touch responsivenss
Debug.performance.tuning=1
Video.accelerate.hw=1
MEDIA TWEAKS
Makes streaming videos stream faster
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=false
Increases quality of photo and videos
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
Raises quality of JPEG images
ro.media.enc.jpeg.quality=90 or 100 (your choice)
Better camera and video taking results
camera/camcorder mods
ro.media.capture.maxres=8m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=120
ro.media.capture.flash=led ***May interfere with Xenon
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=40
ro.media.capture.flashIntensity=70
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.camcorder.videoModes=true
BOOT TWEAKS
Gives your phone no boot animation
debug.sf.nobootanimation=1 ***This might freak out some people not seeing their animation and cause unnecessary battery pulls***
SYSTEM TWEAKS
Forces your home launcher into memory
ro.HOME_APP_ADJ=1
Change the Dalvik VM heap size
dalvik.vm.heapsize=64m can use 24, 32 is default, 48, 64
To disable usb debugging popup
persist.adb.notify=0
To give your phone an HD effect fitting a little more on the screen, look for this in your current build.prop and change the 240 to:
qemu.sf.lcd_density=X (225 or 230) ***This has been known to cause FC’s for the Market, so may not be a good tweak but I still put it in here just in case*** See Changelog
To stop the phone from waking up when pressing the volume key
ro.config.hwfeature_wakeupkey=0
To make the phone ring faster when dialing out
ro.telephony.call_ring.delay=800
Disable black screen issue after call
ro.lge.proximity.delay=25
mot.proximity.delay=25
Screen ppi or font density
ro.sf.lcd_density=240
THESE ARE ONES THAT I DO NOT KNOW WHAT THEY DO AND HAVE NOT TESTED
To enable the hard key lights to stay on while the screen is on and not timeout
ro.mot.buttonlight.timeout=0
Try disabling BLN if your having trouble getting this to work
To make the phone come off of the "black screen" in the middle of, or the end of phone calls when you pull the phone away from your face
mot.proximity.delay=150
**May kill the dialer**
Render UI with GPU
debug.sf.hw=1
Fix some application issues
ro.kernel.android.checkjni=0
Defrags database files
for I in \
‘find /data –iname “*.db”’
do \
sqlite3 $i ‘VACUUM; ’ ; ***This might be something for devs to look into using for something, not sure what***
Credits to the following and links to their pages.
Master&Slaves http://forum.xda-developers.com/showthread.php?t=1151608
knzo http://forum.xda-developers.com/showthread.php?t=1227269
Jokersax11 http://forum.xda-developers.com/showthread.php?t=1263768
Change/Edit log:
11/4/11:::
1-Per peshovec qemu.sf.lcd_density::: if that is different from the default 240 or from 160, chances that some application from the market will be reported as incompatible with your device (web market), or dosen't show in the market (phone) are great.
So use what you want, but when you want to be sure, that you see all the applications, change temporary to 240 or 160
2-Per Sebastiman all tweaks work on Fjfalcon's CM7 except camera ones (caused boot loop)
11/9/11:::
Took out spaces in net.tcp.buffersize as was a copy/paste issue from Word.doc to XDA.
1/6/12:::
Took out some of the Motorola XT720 ROM specific verbiage as this is being view by way more people/devices than the XT
2/1/12:::
Noted the some of these are not working on [ROM][KANG][2012.01.30] CyanogenMod 7.2.0 RC0 Milestone XT720

WOW Awesome dude! Nice work! Can't wait to test them! I wonder if there are reversals? Or probably is if I knew anything about coding lol. Great job dude looks promising. Can't believe the excitement we are still getting out of our phones lol.

LibertyMonger said:
I wonder if there are reversals?
Click to expand...
Click to collapse
Just make sure you have a back up of /system because that is where the build.prop "lives". Also I have found that when I edit them, it creates a .bak backup, but you can never fail restoring a nandroid of just the /system.
As a side note, AA1973 gave the "stock" Build.Pro for the MIUI and 3rdstring (of course) uploaded a .zip with damn near the rest of them here http://forum.xda-developers.com/showthread.php?t=1327141
Plus is you adjust a value, wirte down what the original was and if new doesn't work for you, jsut pust back in the original. This way you shoudl only have to restore /system nandroid is something screws up majorly.

Great work there!
I'd like to call attention to
Code:
Change the Dalvik VM heap size
dalvik.vm.heapsize=64m
Since we have rather limited memory, its better if we stick to a heap size of 32 (default in most roms) personally I use 24 and feel that multitasking is much better than at 32 when most apps get killed repeatedly.

That's cool. I know that when I was on Kahl's V4, mine was at 48 and never had a problem with it. Think the intervals are 24, 32, 48, 64
Edited OP with that.

look cool man, will be take time to check & test soon!

ro.media.capture.flash=led ***Might want to check with MZ or Fjfalcon on these b/c of Xenon... In tweaking the camrera and camcorder is it ok to skip this one if it is not sure?

abet1017 said:
ro.media.capture.flash=led ***Might want to check with MZ or Fjfalcon on these b/c of Xenon... In tweaking the camrera and camcorder is it ok to skip this one if it is not sure?
Click to expand...
Click to collapse
Try it out but ok to skip too. I have read that this might have something to to with the LED notifications that we have all been looking for. Will keep looking into this weekend for that part.

build.prop text files
Hey Wood, would we be able to use these build.prop tweaks? There are text files to download and place on SDCard rename them to build.prop then use root explorer to move them to /system

Woodrube said:
To give your phone an HD effect fitting a little more on the screen, look for this in your current build.prop and change the 240 to:
ro.sf.lcd_density=X (225 or 230) ***This has been known to cause FC’s for the Market, so may not be a good tweak but I still put it in here just in case***
Screen ppi or font density
ro.sf.lcd_density=240 ***This is how MZ and Peshovec fixed the tiny little Korean keyboard on CM6***
Defrags database files
for I in \
‘find /data –iname “*.db”’
do \
sqlite3 $i ‘VACUUM; ’ ; ***This might be something for MZ, Fjfalcon and Peshovec could use for something, not sure what***
Click to expand...
Click to collapse
Thanks for your hard work, i'd like to put some comments
ro.sf.lcd_density -> if that is different from the default 240 or from 160, chances that some application from the market will be reported as incompatible with your device (web market), or dosen't show in the market (phone) are great.
So use what you want, but when you want to be sure, that you see all the applications, change temporary to 240 or 160
qemu.sf.lcd_density (here there is typo for the keyboard it should be qemu.sf.lcd_density, instead of ro.sf.lcd_density)
about defraging the database, may be including as part of openrecovery is better. I don't see the point to be defraged at every start..

After applying the tweaks, headset is not working... I don't know if it is related with the tweaks..... I'm using mz cm6 rc3 rom.
By rebooting I resolve the issue......

abet1017 said:
After applying the tweaks, headset is not working... I don't know if it is related with the tweaks..... I'm using mz cm6 rc3 rom.
By rebooting I resolve the issue......
Click to expand...
Click to collapse
Cool dude! Be interested in your feedback!

abet1017 said:
By rebooting I resolve the issue......
Click to expand...
Click to collapse
Don't forget you have to reboot twice.

peshovec said:
ro.sf.lcd_density -> if that is different from the default 240 or from 160, chances that some application from the market will be reported as incompatible with your device (web market), or dosen't show in the market (phone) are great.
So use what you want, but when you want to be sure, that you see all the applications, change temporary to 240 or 160
qemu.sf.lcd_density (here there is typo for the keyboard it should be qemu.sf.lcd_density, instead of ro.sf.lcd_density).
Click to expand...
Click to collapse
I will edit OP later on when I get to PC. Thanks for re-checking the lcd.density issue too

build.prop
All tweaks work fine on fjfalcons cm7
except the camera tweaks. it causes the phone to bootloop.

sebastimau said:
All tweaks work fine on fjfalcons cm7
except the camera tweaks. it causes the phone to bootloop.
Click to expand...
Click to collapse
Excellent. Will update OP and start working on fixing the camera tweaks.

Woodrube said:
Data Tweaks Increase download/upload/3G speeds
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=0
ro.ril.hsdpa.category=8 (or 10,12,14) Still looking for more of these though.
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=6
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
For the "ro.ril.hsxpa" ******* 0=UMTS, 1=HSDPA, 2=HSDPA/HSUPA
Click to expand...
Click to collapse
Hey Wood, do I type in all these commands? save after the first set? Or what do I do...?
---------- Post added at 08:47 PM ---------- Previous post was at 08:27 PM ----------
Woodrube said:
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[/B]
For the "ro.ril.hsxpa" ******* 0=UMTS, 1=HSDPA, 2=HSDPA/HSUPA
Click to expand...
Click to collapse
You see any typo's in here? The space between 163 84,? Is that correct?
***also have you tested these on Bravo?
***I got all the tweaks saved but I think I better leave well enough alone lol. Bravo is almost perfect as is everything is running great. What do you think Brian? Should I try these?

LibertyMonger said:
Hey Wood, do I type in all these commands? save after the first set? Or what do I do...?
Click to expand...
Click to collapse
You can type them all in at the same time, but when I did it I did ti in pieces to make sure each one was taking effect and if I got looped was able to determine which one caused it problem (like typo ro something like that).
LibertyMonger said:
You see any typo's in here? The space between 163 84,? Is that correct?
***also have you tested these on Bravo?
***I got all the tweaks saved but I think I better leave well enough alone lol. Bravo is almost perfect as is everything is running great. What do you think Brian? Should I try these?
Click to expand...
Click to collapse
I'll fix that in the OP. No spaces between 163 84. Should be 16384. XDA must have remarginalized them when I put it in here. I copied them from a WORD.doc when I was compiling.
I tested the data tweaks and a few of the system tweaks on Bravo and they worked fine. But if you have everything working fine for you, I would suggest either leaving it alone or bit-piece them in there. Don't want the lightning rod effect like you had in HM's ROM.
p.s. - Sorry I didn't respond sooner, I was mostly off-line this weekend and took a few extra days off. Kind of a brain recharge thing.

anybody have descriptions of these?
A lot of these are smaller / larger than what the "change to" value is...not sure how they're going to affect things, such as--
1. why are there 6 numbers for the tcp buffer sizes
2. I don't notice any performance diff modifying the max_events_per_sec
3. Proximity Delay-- is that in ms? If I think my prox delay is "too long" when I take phone away from face, I should make this smaller, right? How small is OK?

rancur3p1c said:
anybody have descriptions of these?
A lot of these are smaller / larger than what the "change to" value is...not sure how they're going to affect things, such as--
1. why are there 6 numbers for the tcp buffer sizes
2. I don't notice any performance diff modifying the max_events_per_sec
3. Proximity Delay-- is that in ms? If I think my prox delay is "too long" when I take phone away from face, I should make this smaller, right? How small is OK?
Click to expand...
Click to collapse
What ROM are you running? That would help me answer your questions a bit more clearly.

[Q] huge laggs on *simple* games

Hello community,
Im having a rooted kf with cm7 and Im a beginner
Id like to tell you my problem. I was trying to play several games starting with fruit ninja or world of goo and was suprised by really low fps around ~5. Im having setcpu from the forum without any additional settings. Its really not fun and I wonder how some of you can plwy mw CoD f.e. .
I wonder whether youre having any additional program on your kf or any advice for me.
Thanks

hello jvizz
this works also on cm7:
http://forum.xda-developers.com/showthread.php?t=1412663
use editor on kf to edit - beware of the permissions
maybe this helps ...

Hello
I have done this the very first day.
That gave a real boost from 1 to 5 fps hehe

there are some tweaks for build.prop - did you something ?
but as allways - beware the permissions !
# Rendering User Interface With GPU
debug.sf.hw=1
# Increase overall touch responsiveness
video.accelerate.hw=1
windowsmgr_max_events_per_sec=150
debug.performance.tuning=1
# Enhance JPG Image Quality To 100 %
ro.media.enc.jpeg.quality=100
# Save Battery
wifi.supplicant_scan_interval=180
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
# Makes streaming videos stream faster
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=false
# Change the Dalvik VM heap size
dalvik.vm.heapsize=48m
# Internet Speed Enhancement
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
# Fix App Issues
ro.kernel.android.checkjni=0

I will try tomorrow, thanks

in /system/build.prop - i use es file exploer for editing (adding at the end)
settings are active after reboot
and use only the ones you need
try it one after the other for testing
i used:
debug.sf.hw=1
video.accelerate.hw=1
and it gave a performance boost in quadrant
double check what you do - you can brick it

Im having the trouble its not saving. Seems not be writable. Can I add this anyway?

if you'r using es file explorer you have to set "root explorer" and i think "mount file system" in settings. if superuser asks then yes and remember.
there is also a way to copy it to computer with adb but it's risk is to set wrong permissions - would try with es first

b63 said:
there are some tweaks for build.prop - did you something ?
but as allways - beware the permissions !
# Rendering User Interface With GPU
debug.sf.hw=1
# Increase overall touch responsiveness
video.accelerate.hw=1
windowsmgr_max_events_per_sec=150
debug.performance.tuning=1
# Enhance JPG Image Quality To 100 %
ro.media.enc.jpeg.quality=100
# Save Battery
wifi.supplicant_scan_interval=180
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
# Makes streaming videos stream faster
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=false
# Change the Dalvik VM heap size
dalvik.vm.heapsize=48m
# Internet Speed Enhancement
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
# Fix App Issues
ro.kernel.android.checkjni=0
Click to expand...
Click to collapse
Hi. I need to try this.
Should i add the lines I try at the end of build.proportional?

yes - simply add the new lines at the end of build.prop

Hey,
I tried that. My system seems to be quicker Button there is no improvement online apps

I really don`t get it how this guy could have made this video playing all the games lagging on my device:
http://www.youtube.com/watch?v=U6MaGr4FCN8

jvizz said:
I really don`t get it how this guy could have made this video playing all the games lagging on my device:
http://www.youtube.com/watch?v=U6MaGr4FCN8
Click to expand...
Click to collapse
do you talk about online games ? that depends on the network speed also
i don't think the guy shows online games
furthermore i'm not the game expert - sorry - can't help you much further

I know youre not an expert for this
Maybe you can find the problem here :
In setcpu is written that only a very low amount of RAM is free. About only 80mb are free to usw.
Any idea?

no - sorry - i don't have setcpu - allthrough i know there are some performance settings in setcpu but i'm pretty shure you allready tried to fiddle with it - the used ram is how android work - it is loading/unloading apps on demand - i think there are also settings in setcpu where you can change the values when an app will be unloaded

List Of Some Build.prop Tweaks

List Of Some Build.prop Tweaks
You Know the Drill i'm NOT responsible if anything happens to you phone
Click to expand...
Click to collapse
# Fast Reboot
persist.sys.purgeable_assets=1
# Increasing The Video Recording Quality
ro.media.enc.hprof.vid.bps=8000000
# Screen Rotate To 270 degree
windowsmgr.support_rotation_270=true;
# Increase VM Heap Size(resolve some fc's)
dalvik.vm.heapsize=64m
# Render UI With GPU
debug.sf.hw=1
# Increasing It Will Make Mobile Smoother
windowsmgr.max_events_per_sec=150
# Video Acceleration Enabled
video.accelerate.hw=1
# Increase Performance
debug.performance.tuning=1
# Disable Sending Usage Data
ro.config.nocheckin=1
# Deeper Sleep/Better battery life
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
# Ringing Will Start Immediately
ro.telephony.call_ring.delay=0
# Disable Error Checking
ro.kernel.android.checkjni=0
# Increase Quality Of MediaStreaming
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=false
# Disable BootAnimation
debug.sf.nobootanimation=1
#Force To Remain Launcher In Memory
ro.HOME_APP_ADJ=1
# Disable Waking Up Of Phone By Volume Buttons
ro.config.hwfeature_wakeupkey=0
# Off The Proximity Quiclky After Call
mot.proximity.delay=25
ro.lge.proximity.delay=25
# Signal Tweaks
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
# NetSpeed Tweaks
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
# Google DNS Tweak
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
# Photo And Video Quality
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.jpeg.quality=100
# Touch Responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
# Scrolling Responsiveness
windowsmgr.max_events_per_sec=500
# Power Save Tweaks
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
# Disables Debug Icon On Status Bar
persist.adb.notify=0
#Faster Scrolling
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
#wifi to scan less frequently
wifi.supplicant_scan_interval=180
#improve battery under no signal
ro.mot.eri.losalert.delay=1000
#makes apps load faster and frees more ram. (Edit exsisting line)
dalvik.vm.dexopt-flags=m=v,o=y
Wipe both Caches in Recovery after adding or changing the above lines.
Use NotePad++ to edit via PC

Nice and usefull thread mate.
I don't know about windowsmgr.max_events_per_sec=500.Are you sure about? Cause for example in sgiii the default is 300 that is the highest i ever saw.
I just want to add a warning for new users who want to change build.prop.
The most of explorers like es explorer will make a stuck on boot after the changes (on ics ROM at least), so its recommended to edit build.prop before rom installation via pc.
Sent from my GT-N7000 using Tapatalk 2

eliashadow said:
Nice and usefull thread mate.
I don't know about windowsmgr.max_events_per_sec=500.Are you sure about? Cause for example in sgiii the default is 300 that is the highest i ever saw.
I just want to add a warning for new users who want to change build.prop.
The most of explorers like es explorer will make a stuck on boot after the changes (on ics ROM at least), so its recommended to edit build.prop before rom installation via pc.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
try to adjust between 150 to 500

eliashadow said:
Nice and usefull thread mate.
I don't know about windowsmgr.max_events_per_sec=500.Are you sure about? Cause for example in sgiii the default is 300 that is the highest i ever saw.
I just want to add a warning for new users who want to change build.prop.
The most of explorers like es explorer will make a stuck on boot after the changes (on ics ROM at least), so its recommended to edit build.prop before rom installation via pc.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
For me, editing with root explorer works perfectly.
Sent from my GT-N7000 using Tapatalk 2

I usually make a copy of build.prop in system. In case of boot issue, you can go in CWM and replace the modded with original.

eliashadow said:
Nice and usefull thread mate.
I don't know about windowsmgr.max_events_per_sec=500.Are you sure about? Cause for example in sgiii the default is 300 that is the highest i ever saw.
I just want to add a warning for new users who want to change build.prop.
The most of explorers like es explorer will make a stuck on boot after the changes (on ics ROM at least), so its recommended to edit build.prop before rom installation via pc.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
how to edit via pc?, notepad is weird

crossmedia said:
how to edit via pc?, notepad is weird
Click to expand...
Click to collapse
use Notepad++

Really useful topic Thanks. Will see if this helps gaining some more battery time.
Edit : added end of post.
Sent from my GT-N7000 using xda premium

thx that was very helpful, but i have one question
thehackersz said:
List Of Some Build.prop Tweaks
# Increasing The Video Recording Quality
ro.media.enc.hprof.vid.bps=8000000
Click to expand...
Click to collapse
as far as i know the note records 720p videos at 11mbps and records 1080p videos at 17mbps
how can a lower value (8mbps) increase recording quality
it would be more logical to set it to something like 20000000 (20mbps) or even more in order to improve quality
as it turns out, samsung camera parameters are stored /system/etc/media_profiles.xml
so changing these probably wont change anything
on the other increasing bitrate in the mentioned file does the trick and you can set very high bitrates (up to 30mbps for me)
but you can experiment with lgcamera tool before stting a defintive value
https://play.google.com/store/apps/details?id=rubberbigpepper.lgCamera&hl=fr

ro.ril.hsxpa=2 should be 3
And gprs class 12

thehackersz said:
List Of Some Build.prop Tweaks
#Force To Remain Launcher In Memory
ro.HOME_APP_ADJ=1
Click to expand...
Click to collapse
This might result in the constant FC of Apex launcher. Apex conflicts being getting forced in memory from bootup after rom flash and hence FC. So kindly keep a second launcher in your /system/apps if you gonna use Apex with this tweak until Apex gets fixed.
(Side note - Happens in JB)
Thanks for listing everything out

With notecore kernel you so not breed does tweaks.

thehackersz said:
List Of Some Build.prop Tweaks
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
Click to expand...
Click to collapse
Ancient obsolete options that do nothing on recent Samsung devices
# Off The Proximity Quiclky After Call
mot.proximity.delay=25
ro.lge.proximity.delay=25
Click to expand...
Click to collapse
I think the fact that these will do nothing on a Samsung should be obvious from the "mot" (Motorola) and "LGE" (LG Electronics)...
# Signal Tweaks
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
Click to expand...
Click to collapse
Similarly, these will do nothing on a Samsung device. The reason why should, just like the above, be obvious...
Most of the others you listed likely won't do anything either - Over in the Infuse community, they were tested and found to do nothing. In addition, doing "strings" on the RIL binaries didn't find those other items in Samsung RILs.
# Power Save Tweaks
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
Click to expand...
Click to collapse
You copypastaed these twice? And as stated before, these are ancient obsolete options that do nothing on modern Samsung devices.
#improve battery under no signal
ro.mot.eri.losalert.delay=1000
Click to expand...
Click to collapse
This will do nothing. The reason why should be obvious (see above)

Config
Whats the best build.prop config for Cleanote 5 and Notecore kernel performance wise?
Any toughts?

Indeed the bitrate mentioned previosly is indeed lower than the stock figure, ive pulled this from my version also.
as well as max events build prop. This has been confirmed as useless even google states 90 is the most as it should be 1.5 times default fps which is 60. By setting this above 90 you induced stutter and lag, as the remaining processing time required to handle the additional values is counteractive
The link below is a good read on why some tweaks are counter productive
http://www.jeffmixon.com/examining-build-prop-tweaks-for-android-ics-a-comprehensive-guide-part-1/

thehackersz said:
List Of Some Build.prop Tweaks
Wipe both Caches in Recovery after adding or changing the above lines.
Use NotePad++ to edit via PC
Click to expand...
Click to collapse
Both Caches ?

nokiamodeln91 said:
Both Caches ?
Click to expand...
Click to collapse
I guess that is refering to cache and dalvik.

Im sory if this doesnt make snse.. But in cwm.. There is option to wipe dalvik cache. .. Wheres the other... Is that cache partition?

nokiamodeln91 said:
Im sory if this doesnt make snse.. But in cwm.. There is option to wipe dalvik cache. .. Wheres the other... Is that cache partition?
Click to expand...
Click to collapse
yes, wipe cache partition and under advanced wipe dalvik cache

Drivingdroids said:
Whats the best build.prop config for Cleanote 5 and Notecore kernel performance wise?
Any toughts?
Click to expand...
Click to collapse
Flash speedmod kernel !

Need some HELP with a few build.prop tweaks !

Heya guys if someone could just try these build.prop tweaks or tell me whether these actually work on SGY i'd be gratefull ! i tried but can't be sure so if anyone espeacially on stock can help then it is appreciated ! thanks in advance
# Render UI with GPU
debug.sf.hw=1
persist.sys.composition.type=gpu
#Lock Launcher in memory
ro.HOME_APP_ADJ=1
# Increase overall touch responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
windowsmgr.max_events_per_sec=250
#Save Some battery
pm.sleep_mode=1
# Improve overall media quality
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
# Tweaks for battery saving
pm.sleep_mode=1
wifi.supplicant_scan_interval=120
# Turn on Just In Time in dalvik virtual machine
dalvik.vm.execution-mode=int:jit
Click to expand...
Click to collapse

Bump

then...why don't you test it by yourself (lol)

kurotsugi said:
then...why don't you test it by yourself (lol)
Click to expand...
Click to collapse
Like i said in the above post i tried but didn't see any difference so i need to know whether these are valid or not !

type getprop and you'll see your tweak there.

thanks kuro! that was all I needed!

nope...that command only use to check whether your script is executed or not. it doesnt tell you whether if the new prop really working or not.
EDIT:
if you want a proof, in terminal type
Code:
su
setprop kucing.meong.lucu 1
getprop
you'll find kucing.meong.lucu in your prop list.

kurotsugi said:
nope...that command only use to check whether your script is executed or not. it doesnt tell you whether if the new prop really working or not.
EDIT:
if you want a proof, in terminal type
Code:
su
setprop kucing.meong.lucu 1
getprop
you'll find kucing.meong.lucu in your prop list.
Click to expand...
Click to collapse
Okay got it!
My scripts are getting executed btw is there a way to know whether they are working?

unless if you know all the prop stuff inside android system, you'll never know which one is really working or not. some of rom have additional hidden prop. some of prop mod will work on all rom but some of them only work in certain rom. in your tweak,
Code:
# Render UI with GPU
debug.sf.hw=1
persist.sys.composition.type=gpu
# this one will mostly working. however, the differences isn't significant.
#Lock Launcher in memory
ro.HOME_APP_ADJ=1
# seems doesn't work in ICS
# Increase overall touch responsiveness
debug.performance.tuning=1 #work
video.accelerate.hw=1 #work
windowsmgr.max_events_per_sec=250 # the max value is 90. when you set higher than 90 you'll get nothing.
#Save Some battery
pm.sleep_mode=1 #work
# Improve overall media quality
ro.media.enc.jpeg.quality=100 #work
ro.media.dec.jpeg.memcap=8000000 # I highly doubt this one.
ro.media.enc.hprof.vid.bps=8000000 #work
# Tweaks for battery saving
pm.sleep_mode=1
wifi.supplicant_scan_interval=120 #work. be carefull with the value
# Turn on Just In Time in dalvik virtual machine
dalvik.vm.execution-mode=int:jit #the devault set is jit. no need to set it again.
# the other famous stuff,
dalvik.vm.heapsize=128m #if you set it higher than 64 it doesn't affect your system. 48 is enough. it doesn't matter since it doesn't improve your devices performance at all

Okay thanks kuro learned a lot from you!

[Guide]Build.prop Wiki

Alright great N2 users!
I´m Chris from Omega Team and today I present to you my little tutorial about build.prop file. Couldn't find something similar in here, so I decided to start this thread. I already got a thread about it in Galaxy S3 section and decided to port it also to Note 2 forum.
So before I start just one thing. It took me many hours to get all the information and as you can see there are still some points missing. So if you got some information about them, please pm me and for sure I put you on the credit list! If you try to mod the build.prop, please back it up first and make a nandroid backup in case something went wrong. Also don´t do anything unless you have a clue about it! Please hit thanks if you think the information in here are useful! And I´m glade for any feedback and suggestion from you guys! I´m not responsible for any damage you phone get when you messing around with this values!
Credits:
To Vegeta1, for give me a first start and his great support!
To Omega Rom Team, for their great support and being like a second family!
1. You will find the build.prop file in root path/System. You can open it with a build.prop editor from Play store or open it for example with the build in text editor in an app like root explorer.
2. For what you need a build.prop? Here´s a good explanation from TheManii: Build.prop is what holds the majority of the runtime flags that are used when android boots, think of it as being similar to config.sys on dos or environment variables in various OS's. It only holds variables, it cant run any scripts on it's own. Whatever is placed inside depends on android itself to pay attention to the flag and actually use it.
3. Let´s get started
# begin build properties
# autogenerated by buildinfo.sh
Version Number of 4.1.2
ro.build.id=JZO54K
Current Rom version on Phone: by editing this value, you will change what are standing in Settings/About Phone/Buildnumber. For Example you can change it to Omega by Indie or what ever you like.
ro.build.display.id=Omega v8.0 - XXDLK7
Your current Modem version
ro.build.version.incremental=N7100XXDLK7
Current sdk version of Framework plus Codename
ro.build.version.sdk=16
ro.build.version.codename=REL
Android Version on Phone
ro.build.version.release=4.1.2
Current Kernel version
ro.build.date=Mon Nov 26 18:23:18 KST 2012
ro.build.date.utc=1353921798
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-78
This means its a official release
ro.build.tags=release-keys
Model Number plus Manufacturer
ro.product.model=GT-N7100
ro.product.brand=samsung
Name
ro.product.name=t03gxx
Device
ro.product.device=t03g
The phone’s board is listed as “smdk4x12,” which means it will most likely use Exynos 4212 or 4412 supporting a maximum clock speed of 1.4GHz (1.6GHz).
ro.product.board=smdk4x12
System Images
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
Nothing to say
ro.product.manufacturer=samsung
Current default Country settings. If you change that line for example to ro.product.locale.language=de and ro.product.locale.region=De, the phone will set to German after a factory reset
ro.product.locale.language=en
ro.product.locale.region=GB
If you not able to connect to your wifi, you can try to set here the same number of channels as your router currently got. For example: Your router is set to 14 channels you can paste the same number in here.
ro.wifi.channels=
Nothing interest on the next few points. Most are explained above.
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=t03g
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=t03gxx-user 4.1.2 JZO54K N7100XXDLK7 release-keys
ro.build.fingerprint=samsung/t03gxx/t03g:4.1.2/JZO54K/N7100XXDLK7:user/release-keys
ro.build.characteristics=default
# Samsung Specific Properties
ro.build.PDA=N7100XXDLK7
ro.build.hidden_ver=N7100XXDLK7
ro.build.changelist=590308
# end build properties
#
# system.prop for smdk4x12
#
Ril Specific: Here some from aosp to that: RIL daemon reads rild.lib path and rild.libargs system properties to determine the Vendor RIL library to use and any initialization arguments to provide to the Vendor RIL
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
Here you can set the Pixel per inch. The smaller you set it the smaller apps, icons and fonts will be. But be careful if you set it to low apps can crash! Also you can´t set it higher than the default value!
ro.sf.lcd_density=320
Minimum brightness of your screen
ro.lcd_min_brightness=20
This point is about rooting. It´s setting if the device running on the emulator or running in secure mode
ro.kernel.qemu=0
This point speak for itself
ro.tvout.enable=true
Maybe someone can light me up on that point.
persist.sys.storage_preload=1
Same here
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/
# Multimedia property for Smart View
media.enable-commonsource=true
# System property ril adb log on
persist.radio.adb_log_on=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
Support for OpenGl 2.0
ro.opengles.version=131072
System property used to enable or disable dirty regions invalidation.
debug.hwui.render_dirty_regions=false
Same as above, setting the pixel per inch
ro.sf.lcd_density=320
System property defining default error report receiver
ro.error.receiver.default=com.samsung.receiver.error
This controls the smallest amount of memory given to a single application.
dalvik.vm.heapstartsize=8m
The dalvik.vm.heapgrowthlimit property limits how large an Android application’s heap can get.
dalvik.vm.heapgrowthlimit=64m
The dalvik.vm.heapsize property defines an absolute maximum for the heap size for an application.
dalvik.vm.heapsize=256m
No clue about the next three points. Help is appreciated.
ro.hdcp2.rx=tz
ro.secwvk=220
ro.sec.fle.encryption=true
Here you can set the standard media sounds for each notification. But they got to match with the one in system/media/audio/...
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
That means your phone is still usable, even you got no Sim card in it.
keyguard.no_require_sim=true
Format of date
ro.com.android.dateformat=MM-dd-yyyy
Setting this value from unknown to wifi-only can fix some stand by issues.
ro.carrier=unknown
Needed for Play store. Some guys modded it to pay with her Phone bill, but i don't know if that still works.
ro.com.google.clientidbase=android-samsung
Defines weither to use UMTS (0), HSPDA/UMTS(1), or HSDPA/HSPUA(2) respectively.Here you can improve your Data speed if your provider supports it. Set this to 0 if you want lower speeds, and up to 2 for faster speeds.
ro.ril.hsxpa=1
Defines what class speeds to use with EDGE. Setting this value to 12 can improve the data speed significant on lower connections.
ro.ril.gprsclass=10
Value for adb. Is a pipe connection in the adb client.
ro.adb.qemud=1
Google Mobile Service Version with build number
ro.com.google.gmsversion=4.1_r3
Basically you control the class-loading and dalvik-vm there. Here you can set different values. v=a means verify all, v=f means verify full, o=v means optimize verify, u=n means do not optimize for unprocessor and m=y means register maps yes
dalvik.vm.dexopt-flags=m=y
Bluetooth name of the device
net.bt.name=Android
The dalvik.vm.stack-trace-file property allows you to specify the name of the file where the thread stack traces will be written.
dalvik.vm.stack-trace-file=/data/anr/traces.txt
This point stands for "Debug SurfaceFlinger Hardware" or GPU hardware acceleration
debug.sf.hw=1
Video Acceleration
video.accelerate.hw=1
Increase the touch responsive of the screen
debug.performance.tuning=1
Disable sending usage data
ro.config.nocheckin=1
Increase the quality of JPEG pics
ro.media.enc.jpeg.quality=100
increasing the recording quality of Pics and videos
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
Here you can set the delay of time your phone starts to ring when you recieve a call. 0=disabled
ro.telephony.call_ring.delay=0
This point set the delay after a call. This fix Black screen issues.
ro.lge.proximity.delay=15
mot.proximity.delay=15
Next two points should safe some battery if they are enabled but the problem is that they are not in source code elsewhere and should have no effect. This means that adding this value to your build.prop will have no effect at all. This parameter is a kernel parameter and will only work when passed directly to the kernel on boot.
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
Already explained
ro.config.nocheckin=1
For the last two points. These commands enable or disable the error profiler in the android. For most android users, there is no use in having error profiling . however , some applications might make use of this for generating error reports.
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1

I just wondering why this useful thread has no reply. Good work thank you:thumbup:
Sent from my A90S using xda app-developers app

Great thread. Thanx for sharing the info. You really put in a lot of effort making this :thumsbup:

shahulakthar said:
I just wondering why this useful thread has no reply. Good work thank you:thumbup:
Sent from my A90S using xda app-developers app
Click to expand...
Click to collapse
zeeshanonlyme said:
Great thread. Thanx for sharing the info. You really put in a lot of effort making this :thumsbup:
Click to expand...
Click to collapse
Thank you both for your report! Really appreciate that!

Will changing ro.product.locale and language will change csc ?
Sent from my GT-N7100 using xda app-developers app
---------- Post added at 02:48 AM ---------- Previous post was at 02:45 AM ----------
Persist.systemstorage.preload imao means will it use the same preload folder or something
Sent from my GT-N7100 using xda app-developers app
---------- Post added at 02:50 AM ---------- Previous post was at 02:48 AM ----------
Tz is something related to radio and bootloader and kernel
Therr is a tz.img in dll7 rom tar. :beer:
Sent from my GT-N7100 using xda app-developers app

UtkarshGupta said:
Will changing ro.product.locale and language will change csc ?
Sent from my GT-N7100 using xda app-developers app
---------- Post added at 02:48 AM ---------- Previous post was at 02:45 AM ----------
Persist.systemstorage.preload imao means will it use the same preload folder or something
Sent from my GT-N7100 using xda app-developers app
---------- Post added at 02:50 AM ---------- Previous post was at 02:48 AM ----------
Tz is something related to radio and bootloader and kernel
Therr is a tz.img in dll7 rom tar. :beer:
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
No it won't change csc. If you modified it in the rom zip and flash the rom afterwards with full wipe it will automatically set phone to the region you modified before.
Edit: Are you sure about the other two? If yes that would be perfect!

What will happen if we put more than 800000000 for the quality of pics ?
And now I've already android 4.2

JCVD_ said:
What will happen if we put more than 800000000 for the quality of pics ?
And now I've already android 4.2
Click to expand...
Click to collapse
I'm not quiet sure. But i think the actual number should be the maximum or a little bit above. But it can't get better then better. Otherwise you could imagine what numbers I would past in for some points.

I just want add some of the important tweeks done by senior member mv_style. Most of them already in the thread.
# Signal Tweaks
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
# NetSpeed Tweaks
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
# Google DNS Tweak
net.rmnet0.dns1=8.8.8.8
net.rmnet0.dns2=8.8.4.4
net.dns1=8.8.8.8
net.dns2=8.8.4.4
# Photo And Video Quality
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.jpeg.quality=100
# Touch Responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
# Scrolling Responsiveness
windowsmgr.max_events_per_sec= 500
# Call Tweaks
ro.telephony.call_ring.delay=0
ro.lge.proximity.delay=25
mot.proximity.delay=25
# Power Save Tweaks
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
# Performance Tweaks
ro.kernel.android.checkjni=0
ro.config.nocheckin=1
# Disables Debug Icon On Status Bar
persist.adb.notify=0
I hope this will be helpful for noobs like me
Sent from my A90S using xda app-developers app

shahulakthar said:
I just want add some of the important tweeks done by senior member mv_style. Most of them already in the thread.
# Signal Tweaks 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
# NetSpeed Tweaks 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
# Google DNS Tweak net.rmnet0.dns1=8.8.8.8 net.rmnet0.dns2=8.8.4.4 net.dns1=8.8.8.8 net.dns2=8.8.4.4
# Photo And Video Quality ro.media.dec.jpeg.memcap=8000000 ro.media.enc.hprof.vid.bps=8000000 ro.media.enc.jpeg.quality=100
# Touch Responsiveness debug.performance.tuning=1 video.accelerate.hw=1
# Scrolling Responsiveness windowsmgr.max_events_per_sec=500
# Call Tweaks ro.telephony.call_ring.delay=0 ro.lge.proximity.delay=25 mot.proximity.delay=25
# Power Save Tweaks ro.ril.disable.power.collapse=1 pm.sleep_mode=1
# Performance Tweaks ro.kernel.android.checkjni=0 ro.config.nocheckin=1
# Disables Debug Icon On Status Bar persist.adb.notify=0
I hope this will be helpful for moons like me
Sent from my A90S using xda app-developers app
Click to expand...
Click to collapse
Thank you very much mate for sharing this! Thumb's up to you!

Chris_84 said:
Thank you very much mate for sharing this! Thumb's up to you!
Click to expand...
Click to collapse
Credits goes to mv_style
Sent from my A90S using xda app-developers app

shahulakthar said:
Credits goes to mv_style
Sent from my A90S using xda app-developers app
Click to expand...
Click to collapse
I know my friend but also to you for sharing this.

I am not sure.
But from the name I think they could be.
Try chainfire or some rom dev dto confirm.
I might be completely right or maybe completely wrong
Sent from my GT-N7100 using xda app-developers app

UtkarshGupta said:
I am not sure.
But from the name I think they could be.
Try chainfire or some rom dev dto confirm.
I might be completely right or maybe completely wrong
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Will do it. Thank you for your help!

Adding a line to build.prop (at the end) will enable sofykey navigation bar(virtual key) like nexus
qemu.hw.mainkeys=0
below mentioned thing is not related to build prop but it is useful when you add navigation bar with build prop
You can disable hardware button by editing
/system/usr/layout/Generic.kl
there are three key 172, 158,139 for Home,Back and menu.
add # before number of key to disable it.
Sources : I have read somwhere and sorry original source not knowing.

dr.ketan said:
Adding a line to build.prop (at the end) will enable sofykey navigation bar(virtual key) like nexus
qemu.hw.mainkeys=0
below mentioned thing is not related to build prop but it is useful when you add navigation bar with build prop
You can disable hardware button by editing
/system/usr/layout/Generic.kl
there are three key 172, 158,139 for Home,Back and menu.
add # before number of key to disable it.
Sources : I have read somwhere and sorry original source not knowing.
Click to expand...
Click to collapse
Bro, I like to remove soft key already I have. How to remove?
Sent from my A90S using xda app-developers app

Just removed the line you added which is given in the above lines.
Sent from my GT-N7100 using xda app-developers app

can i change the mac address of the wifi from the build.prop??
or can it be change?

AW: [Guide]Build.prop Wiki
ktgohdt125 said:
can i change the mac address of the wifi from the build.prop??
or can it be change?
Click to expand...
Click to collapse
Hi mate! Sorry for my late reply. You can't change the Mac address in build prop. You can just change the number of channels your router use. It can help with stand by issues.

Chris_84 said:
Hi mate! Sorry for my late reply. You can't change the Mac address in build prop. You can just change the number of channels your router use. It can help with stand by issues.
Click to expand...
Click to collapse
thank you for your prompt respond.
do u mean that we have no way to change the Mac address??