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.

[TIPS] Share your Tweaks,Tips & Fixes for Dell Streak 5 :)

Hi Guys,
Thought I'd start a little thread for people to share their tweaks and tips so that others can enjoy too
Since I'm new to the Dell Streak, this would benifit me as well.
My Tweaks & Tips:
Boot Animation:
ICS Boot Animation Landscape (Full Screen Boot)
http://forum.xda-developers.com/showthread.php?t=1459717
Just edit the 'desc.txt' file to '800 480 24p 0 0 part0'
Apps:
-Rotation Locker (force landscape/portrait for all apps)
-Startup Manager (disable startup apps to save memory)
-Battery Defender (wifi off when screen turns off, bypass reboot bug! **WiFi Policy Bug**)
-Ram Manager Pro (great memory management app) ~50MB more
-System Cleanup (move apps from /data/app to/from /system/app/)
-Rescan Media (turn off media scanning service, to increase boot time)
Tweaks:
-Increase SD Cache (Speedup SD Write/Read Speeds) *Can be done by app*
Game Compatibility Tweak(Build.prop)
Change the build.prop brand & model :
ro.product.model=HTC Vision
ro.product.brand=HTC
ro.product.manufacturer=HTC
Signal Boost Tweak:
Follow djscopesofm's guide here:
http://forum.xda-developers.com/showthread.php?t=924440
Build.prop Tweaks:
**Make sure to Backup Nandroid before playing with Build.prop**
( I broke the WiFi connectivity while playing with some unknown settings, had to nandroid restore and test over and over again. )
#Signal Boost
ro.ril.enable.dtm=1
ro.ril.gprsclass=10
ro.ril.hep=0
ro.ril.enable.3g.prefix=1
ro.ril.hsdpa.category=8
ro.ril.hsupa.category=6
ro.ril.hsxpa=2
ro.ril.enable.a53=1
net.dns1=8.8.8.8
net.dns2=8.8.4.4
# Force launcher into memory
ro.HOME_APP_ADJ=1
#WiFi Scan to 3mins
wifi.supplicant_scan_interval=180
#Increase Touch Responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
# Net speed tweaks, choose what you need
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wimax = 4096,221184,524288,4096,16384,110208
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
The Following Tweaks causes instability on certain roms/builds. (Make sure to backup before changing settings to test)
**Broke my DHCP on WiFi**
# Allow power collapse, increases battery life
ro.ril.disable.power.collapse=0
# Puts the CPU into deep sleep but preserves registers
pm.sleep_mode=1
# When moving through zones or losing signal, having a delay
# smooths out constant disconnects and reconnects, saves battery life
ro.mot.eri.losalert.delay=1000
#To disable USB debugging popup
persist.adb.notify=0
#Disable error checking
ro.kernel.android.checkjni=0
#Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
#Decrease dialing out delay
ro.telephony.call_ring.delay=0
#Raise photo and video recording quality
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
#camera/video
ro.camcorder.videoModes=true
ro.media.capture.maxres=5m
#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
#Disable Boot Animation
debug.sf.nobootanimation=0
Click to expand...
Click to collapse
Fixes:
-change build.prop to HTC Vision/Google Nexus One for apps compatibility. (Games mostly)
-Delete Rogers's APN (isp.apn) to enable WiFi Tethering **Rogers AT&T Network related**
I will continue to keep adding to this list as I keep playing with my Streak.
Hope you guys share some tips with me too!

ROM
Official Olleh 407, thanks to http://www.streaksmart.com/ for the heads-up and to the Manii for the manual and support.
Set ro.secure=0 in default.prop by flashing a boot.img from GingerStreak 2.4
Cleanup
Used adb to delete unwanted apps:
Removed all Olleh market apps
Removed Lota, Logservice and Logmaster2 (both apk and odex files)
Removed Accuweather and ZinioReader
Tweaks
Installed free ADWLauncher from the market, replacing Dell Stage UI
Locked main screen to portrait
Custom Bootanimation
Removed the camera_click.ogg file from system/media/audio/ui
Custom /etc/hosts file sending advertising sites to 127.0.0.1

Dr Doppio said:
ROM
Set ro.secure=0 in default.prop by flashing a boot.img from GingerStreak 2.4
Click to expand...
Click to collapse
whats this sposed to do mate?

ro.secure is already set to 0 in all custom kernels.
I'm pretty sure you cant change it once the device has booted up, you need to modify the kernel (or rather it's ramdisk) and reflash.

crashDebug said:
whats this sposed to do mate?
Click to expand...
Click to collapse
Gives you root rights from adb without installing superuser and busybox. My approach may not be the proper way to achieve this, see below.
TheManii said:
ro.secure is already set to 0 in all custom kernels.
Click to expand...
Click to collapse
Yes, but I had flashed the official Olleh ROM, since that was the first time I was changing ROM and I wanted to be on the safe(r) side. I would now recommend to other noobs such as myself to go for a streamlined ROM, but then I didn't know better.
I'm pretty sure you cant change it once the device has booted up, you need to modify the kernel (or rather it's ramdisk) and reflash.
Click to expand...
Click to collapse
As far as I figured, changing dafault.prop required unpacking the bootimg, editing the file, repacking the image and flashing it back. I took a riskier shortcut to extract a bootimg from a different ROM that I assumed was pre-rooted and likely to have ro.secure=0. It was a stupid thing to do, but it luckily worked, and all it took was three lines with fastboot. I may add that the contents of the file changed a few times after reboots, and I noticed a file with ro.secure=1, ro.debuggable=1 at some point. I've also found in the file /firstboot/permissionadb.err a line "date time <adb>: permission secure=1", supposedly logging an error that I had caused by fooling around...

official olleh 407 installed + deodexed + language pack + portrait hack by themanii + superuser (rooted) + MattedbBlues theme + GoLauncher EX.
-tweaks
-using handcent sms (with darkness skin) for simple solution to everride the convertion from sms to mms
-i consider a tweak that i don't have any memory manager or things like that, i just use the applications i need and if something bothers me, i just freeze it using titanium backup.
-for end call freeze problem, i just use the option from settings>accesibility>power button ends call, solves that problem and i think is more "accesible".
-everything runs smooth, almost no problems i would say, but i noticed some problems, wifi tends to "lag" when using instant messaging applications, i know that this is a known bug, but works pretty ok otherwise, also i use Wifi Static for almost any wireless network i connect to.
-another problem i have noticed is that sometimes it just doesn't want to send SMS's, it just gives me a undelivered notification, and i resend it again, i also noticed that the sms is sent, but not entirely, so when this happens, if i resend it 4 times, that person recieves 3 incomplete messages and finally the complete one, also, this is a farly rare bug.
hope this helps!

Added new tweaks.

We thank you very much for your time in order to have the best settings in our phones...Is it possible to change the wifi settings in order to see channels 12-14 at 2.2.2 official android?

these are pretty 407/olleh related, and I confirm they are working in this rom ONLY.
here goes
ro.build.CUSTOMER_CONFIG_KT=0
to disable the sms/mms conversion in the stock messaging app.
note that there also is a line like this
ro.build.CONFIG_CUSTOMER_KT
which I have no idea what it does (but set it to 0 anyway)
ro.build.FEATURE.SHUTTERSOUND=0
set to 0 to show the shutter option in the camera app (note: this option alone does NOT disable the shutter sound, it just shows the option in the app!)
ro.build.OEM_PRESET_APN_LOCK=1
ro.build.OEM_PRESET_APN_HIDE=1
grants the ability to disable and delete preset APNs from Wireless Settings. They are locked in 407
debug.composition.type=gpu
to enable the "CRT off" animation which is disabled by default.
these are not all my findings, thanks to the original discoverers!

-----NEW FIX
I had a problem for some time now with long sms's, not the mms to sms convertion, solved it with handcent sms, but the phone would simply not send bigger than 3-4x160 sms's.
Code:
-put your mobile phone to GSM only mode, at mobile networks settings.
(this problem seems to be solved for now, hope this helps...)

Ya'll have covered just about everything I already do. One quick easy littke thing I found helpful is GPS Status & Toolbox for keeping the GPS and compass in line. Letting the app update AGPS data daily helps GPS lock time and there is a compass calibration app that I need to use regurely.

I'm not sure if other gb roms have it but in dsc 0.72 I stumbled upon the option to set up peak and non peak hours and shut data off after a set amount of time, if anyone's interested here's how to get to it
settings>wireless and networks>mobile networks>schedule data connection
with the non peak hours set up for when i'm asleep and peak to 15 minutes I'm able to get close to two and half days on a single charge with a few 5 minute phone calls and ~400 texts sent per day
Edit:
Setting this up WILL prevent all apps that rely on syncing while the phone is asleep from syncing, it's not much of an issue for me but to those who rely on apps syncing while the phone is asleep should be advised to set up non peak hours data shut off only.

[FIX] Wallstreak app - to center my 800 x 480 wallpapers perfectly
[TIP] Gingerstreak - 2.4.4 Rom with DSC-Team-Phoenix kernel , works flawless
[TIP] A Touch of ICS theme - to give it a nice black and blue look
[FIX] Widgetlocker - to bypass the default lock screen and make it a bit more usefull
[TIP] Extended controls - when the default power controll app is just a bit to limited for your taste
[FIX] Opera Mobile - a bug that my streak has is a browser that takes forever to load, Opera mobile solves this
[TIP] Streakled - a nice app that uses the Streaks led lights to notify you when youve received a e-mail or text message

simonbuschers said:
...
[FIX] Opera Mobile - a bug that my streak has is a browser that takes forever to load, Opera mobile solves this
...
Click to expand...
Click to collapse
I have noticed that cleaning up the cache changes browser load times immensely, from almost instanteneous after clean up to close to 1 minute after a couple of weeks without one. Other than that, I love desktop Opera, but haven't used the mobile version yet...

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 !

[CWM] Skeleton zips for system and user apps & build.prop optimization

http://forum.xda-developers.com/showthread.php?p=24233846
Just download the attached zip file according to your need, add apps.. flash.. enjoy.. Tested with cwm 5.0.2.7 touch..
********************************************************************************************************************************************************
Editing build.prop.
Even though some of the things are well known for us, some of them are new for me..So im jus posting it.
1.Force launcher into memory
Property
ro.HOME_APP_ADJ = 1
Function
This will force the Default launcher into memory. But your device should be having enough free memory, otherwise you will meet lags and performance will be reduced severely. Use a light weight launcher for this.
Values
0 : Turns off the feature. Frees up memory.
1: Keeps the default launcher in memory .Will have highest priority and Android auto kills it only when it’s really necessary.
2.Improving Camera Image quality
Property
ro.media.enc.jpeg.quality=100
Function
This will force the camera application to use 100% quality setting when saving camera images as JPEG
Values
1-100 : with 1 as the worst quality and 100 as the best quality.
3.Increase resolution of panorama image
Property
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
Function
This will force the panorama mode in the camera app to save the image at a higher resolution. This may not be supported by all phones. And since it is an Android 4.0 feature , you will need that android version as well.
Values
defres: Provide the full panorama image resolution.Consisting of all images.
frameres: Provide the resolution of each frame of panorama.
4.Improve performance in video playback and streaming
Property
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=true
Function
Android uses the media framework named “Stagefright” from Froyo ( Android 2.2 ) onwards. While Stagefright is more open and simple, it is sometimes buggy compared to the previously used OpenCore framework. However, Google has greatly improved its stability. These values might affect the stability of playback in some devices, if it is ruining your experience , then revert to the original values.
5.Improve touch responsiveness through Hardware Rendering
Property
debug.sf.hw=1
persist.sys.ui.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
debug.composition.type=gpu
Function
This will force the system to use GPU for rendering each 2D frame in applications. Since android uses frame by frame rendering of the screen normally, this will offload the rendering to GPU by a huge amount and will make the user experience smoother.
Values
debug.composition.type values : GPU / CPU . GPU will make use of the graphic chip on your device for rendering each frame.
6.Disable Error Profiler
Property
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
Function
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.
Values
0 :Enable the feature. Better to delete the property if you don’t want to disable it.
1: Disables the feature.
7.Modify WiFi network scanning time.
Property
wifi.supplicant_scan_interval=180
Function
This command will be already present in all build.prop files. This controls the number of seconds the device waits before scanning for WiFi networks.
Values
Default value is 180 . It is in seconds . You can increase the value if you want to save more battery and doesn’t use WiFi extensively. Or else , you can decrease it , if you are dropping your WiFi signal often.
8.Disable logcat – Android Logger
Property
logcat.live=disable
Function
This command controls the Android Logcat file generation. This file is mainly used for debugging. Expensive disk reads/writes can be reduced by disabling Android logcat.
Values
disable / enable
9.Improve Voice Call clarity
Property
ro.ril.enable.amr.wideband=1
Function
This command controls the AMR audio codec’s property.AMR codec is used for voice calls.
Values
1 or 0 .
10.Disable Extended JNI Checks
Property
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
Function
“JNI does very little error checking. Errors usually result in a crash. Android also offers a mode called CheckJNI, where the JavaVM and JNIEnv function table pointers are switched to tables of functions that do an extended series of checks before calling the standard implementation.” . That’s the definition from Android developers documentation. While disabling this may cause some data loss when the application crashes, most applications ,which are popular, have been thoroughly checked and hence will be using precious CPU time for extended checks . Save that time by disabling this.
Values
0 / 1 : disable / enable .
11.Disable Android Device Check In.
Property
ro.config.nocheckin=1
Function
Every Android device checks in at the Google Servers when an internet connection is found, this helps Google in tracking the number of installations and the statistics of different android versions. This can be disabled to save for saving traffic and some CPU time, due to the frequent polling for checking internet connection.
Values
1/0 for disabling and enabling , respectively.
12.Increase Voice Call Audio Adjustment Steps.
Property
ro.config.vc_call_steps=20
Function
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’t increase the volume if it’s already low. But you can manage it by more precisely.
Values
Number of steps as integers. 7-20 is recommended. 7 is the default.
Editing Build.Prop
For editing build.prop, your device should be rooted. That’s the first requirement.
It is at /system/
If you have Root Explorer / ES File Explorer installed on your device you can edit from the device itself. More easier method is to get he application named build.prop Editor . It can be used to change the values and add new fields.

works only in cm10 based roms.

Souron29 said:
works only in cm10 based roms.
Click to expand...
Click to collapse
Of course

doesn't CM10 Rom for O1 include this? U posted it separately so thought might be working with CM9 or CM7

Souron29 said:
works only in cm10 based roms.
Click to expand...
Click to collapse
Then what is the point?
Sent from my LG-P500

This tread should be named as:[APP][CM10] messaging app with quick reply, popup notifications
Sent from my LG-P500 using xda premium

It has been taken from the latest nightly.. I dono whether our cm10 build by rashed have this..:laugh:

carrthee89 said:
It has been taken from the latest nightly.. I dono whether our cm10 build by rashed have this..:laugh:
Click to expand...
Click to collapse
I think we have this
Sent from my LG-P500 using Tapatalk 2

Bump.Now the thread is usefull
Sent from my LG-P500 using xda premium

Updated with build.prop optimizations

[Guide]Build.prop Wiki

Alright great S2 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 Galaxy S2 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 v16.2 - XXLSJ
Your current Modem version
ro.build.version.incremental=I9100XXLSJ
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=Tue Nov 6 02:17:01 KST 2012
ro.build.date.utc=1352135821
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-111
This means its a official release
ro.build.tags=release-keys
Model Number plus Manufacturer
ro.product.model=GT-I9100
ro.product.brand=samsung
Name
ro.product.name=GT-I9100
Device
ro.product.device=GT-I9100
The phone’s board is listed as “smdk4210,” which means it will most likely use Exynos 4210, supporting a maximum clock speed of 1.2GHz.
ro.product.board=smdk4210
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=GT-I9100
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9100-user 4.1.2 JZO54K I9100XXLSJ release-keys
ro.build.fingerprint=samsung/GT-I9100/GT-I9100:4.1.2/JZO54K/I9100XXLSJ:user/release-keys
ro.build.characteristics=default
# Samsung Specific Properties
ro.build.PDA=I9100XXLSJ
ro.build.hidden_ver=I9100XXLSJ
ro.build.changelist=462349
# end build properties
#
# system.prop for smdk4210
#
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=240
Minimum brightness of your screen
ro.lcd_min_brightness=40
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 for Default Brightness
I think this point also need no explanation
ro.lcd_brightness=160
#
# 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
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=5m
The dalvik.vm.heapgrowthlimit property limits how large an Android application’s heap can get.
dalvik.vm.heapgrowthlimit=48m
The dalvik.vm.heapsize property defines an absolute maximum for the heap size for an application.
dalvik.vm.heapsize=128m
Same as above, setting the pixel per inch
ro.sf.lcd_density=240
No clue about the next point. Help is appreciated.
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=A_toy_watch.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
No clue. Maybe someone can light me up.
ro.com.google.apphider=off
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

Is it possible to have conditional statements in build.prop?
Is it possible to have conditional statements in build.prop?
For example:
if P1 == 0
ro.xxx.yyy=value1
else
ro.xxx.yyy=value2
endif
where P1 is either a parameter or a predefined setting.
Thanks

Ian5723 said:
Is it possible to have conditional statements in build.prop?
For example:
if P1 == 0
ro.xxx.yyy=value1
else
ro.xxx.yyy=value2
endif
where P1 is either a parameter or a predefined setting.
Thanks
Click to expand...
Click to collapse
I think you mean like a script. Imo that's not possible.
Sent from my GT-I9300 using XDA Premium 4 mobile app

Pure awesomeness thank very much

Nice thread ! Now I understant what's in the Build.prop . I will take a look to my Build.prop tonight !
Thanks man !

maxflay said:
Nice thread ! Now I understant what's in the Build.prop . I will take a look to my Build.prop tonight !
Thanks man !
Click to expand...
Click to collapse
Glade you like it. And thanks for the feedback!
Sent from my GT-I9300 using XDA Premium 4 mobile app

SystemUpdateServices
I need to stop Android System Update downloads from happening after I restart the phone.
I am using DisableService app to uncheck (OFF) SystemUpdateServices (under Google Services Framework). After I restart the phone the SystemUpdateServices is check (ON) again. Does anyone know which properties controls the SystemUpdateServices?
Thank you.

Help help help !!!!!
I have mistakely deleted my build.prop of samsung galaxy s2.... I beg you please send me its file of build.prop in my gmail please mail me .......:crying::crying::crying:....

Increase the touch responsive of the screen debug.performance.tuning=1
Can I increase this number?