Database Develop

Build.prop Tweaks

I have an ATT atrix on the Rogers network in canada. I have abysmal up/down-link speed. I was skimming over the build.prop HSUPA thread and i decided to do some research about the build.prop file and made a few changes.
First off, the connection speed tweak:
Code:
## Rogers Speed Tweak
#
ro.ril.hsxpa=3
ro.ril.hsdpa.category=8
ro.ril hsupa.category=5
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.gprsclass=32
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
## End Tweak
#
With this I experianced a much higher download speed and a more stable upload speed. The results were as follows:
Before:
Server 1:815 kbps down 354 kbps up
Server 2:618 kbps down 259 kbps up
Server 3:701 kbps down 301 kbps up
After:
Server 1:1224 kbps down 331 kbps up
Server 2:1358 kbps down 320 kbps up
Server 3:1206 kbps down 390 kbps up
Caveat! This is for an ATT Atrix on the rogers network so YMMV
Upon my research i found a few more parameters i decided to change. I changed the following:
Code:
#proximit sensor screen off delay
mot.proximity.delay=150
This changed the delay in the sensor when you are in a call and you move the phone away from your face. I found this delay to be WAY to long. The orginal value was 450
Code:
# for larger screen support
# 3.75" WVGA == 248dpi
# 4.0" qHD == 275dpi
ro.sf.lcd_density=275
****NOTE: THIS KILLS THE DIALER...i am going to figure out why, best keep it at the stock 240****
I changed this to 275 as thats what it said. It filled in the icons better on my homescreen and made the widgets fill the screen more. This was a personal preference for me.
Code:
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 90
Pretty self explanitory. I am a wifi always on kind of guy and i am hoping this saves some battery. The original was 30 i believe.
I am going to do some more testing to confirm the speed increase throughout the day and also see how the battery life is effected. It may not be much, but so far the speed change has been well worth it!
STEPS
I did it the following way:
Here were my steps:
1. adb pull /system/build.prop /yourdirectoryhere
2. Open build.prop with notepad++ and make changes
3. adb push /yourdirectoryhere/build.prop /mnt/sdcard
4. Used Super Manager to navigate to the /system folder and rename the old build.prop to buildstock.prop then copied the new build.prop into the folder from /mnt/sdcard .
5. adb reboot
As GibMcFragger mentioned, you can do this all through your phone via root explorer and it will save the original as .bak as well.

Did you edit the build.prop file on the fly or had to modify it before reflash ?
As for the density of the screen, did it affect the layout in landscape as opposed to portrait and was there anything out of place on the home screens ?

Woh! Thanks dude. I just edited my lcd density to 275 and it looks much better! My custom dock fits now too. It was a little short at the default dpi of 240.
I just edited my build.prop in Root Explorer and when you save it, it automatically saves the original as a .bak
Sent from my soon-to-be-hacked Bell Atrix.

Would be awesome if the same speed settings worked with At&t though I know that would be too good to be true, wonder if we can pull the settings from another device and input them in the values you changed such as taking the values from a captivate rom...

molotof said:
Did you edit the build.prop file on the fly or had to modify it before reflash ?
As for the density of the screen, did it affect the layout in landscape as opposed to portrait and was there anything out of place on the home screens ?
Click to expand...
Click to collapse
The layout in the landscape lines up much better.
EDIT to OP: Added steps

MKVFTW said:
Code:
# for larger screen support
# 3.75" WVGA == 248dpi
# 4.0" qHD == 275dpi
ro.sf.lcd_density=275
Click to expand...
Click to collapse
This kills the dialer. Even 248 does not work. If you are using stock dialer like I am you have to keep the density at 240.

Immix said:
This kills the dialer. Even 248 does not work. If you are using stock dialer like I am you have to keep the density at 240.
Click to expand...
Click to collapse
Holy crap, your right it does. Hmmm. Ill make note in the OP and start figuring out why. Are you stock? Or using gingerblur?

MKVFTW said:
Holy crap, your right it does. Hmmm. Ill make note in the OP and start figuring out why. Are you stock? Or using gingerblur?
Click to expand...
Click to collapse
I am rooted and deodexed (DG's adeo ROM), running 4.1.26. Do you know what was the original screen density? I don't think it was 240 and I messed up my build.prop.bak too.

yeah i just was gonna comment on how changing the dpi to 275 kills the dialer/contacts
I just changed it back to the original build.prop and everything is working again
Im using stock .157 if that helps anyone (rooted)
**EDIT
original density is 240

Immix said:
I am rooted and deodexed (DG's adeo ROM), running 4.1.26. Do you know what was the original screen density? I don't think it was 240 and I messed up my build.prop.bak too.
Click to expand...
Click to collapse
Yes it is 240

Immix said:
I am rooted and deodexed (DG's adeo ROM), running 4.1.26. Do you know what was the original screen density? I don't think it was 240 and I messed up my build.prop.bak too.
Click to expand...
Click to collapse
says 240 on my phone:
# for larger screen support
# 3.75" WVGA == 248dpi
# 4.0" qHD == 275dpi
ro.sf.lcd_density=240

Yep. Dialer dead. Damn.

Dialer is dead, however you can still use contacts app to dial for what its worth

the DPI setting has no effect if you're using a launcher like Go Launcher or LP right?

dLo GSR said:
the DPI setting has no effect if you're using a launcher like Go Launcher or LP right?
Click to expand...
Click to collapse
It does. It changes the dpi for everything.
Sent from my soon-to-be-hacked Bell Atrix.

I use 230 LCD density, and use dialer one instead of the stock dialer which only works at 240 density. I like being able to fit more on the screen with the smaller densitiy setting.

So any u/d speed reports from any at$t users who inserted these settings ?
You can over come the dialer problem by setting a market dialer in place of the stock dialer if you like the new density.
Sent from my MB860 using XDA Premium App

hey guys anyone tried changing the
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
max number to more than 2? i tried it on 3 but still it allows only 2, however apparently the sensor would allow up to 10 max points

I've used 220 LCD Density for a few weeks now - means I can set LauncherPro to 5 cols by 7 rows, so plenty of widget space. I like to have almost everything on my front screen.
Only issues I've encountered are the dialer (so I use Dialer One instead), and I think it's responsible for my fingerprint settings page being unavailable. If you set the fingerprint lock before changing density though, the settings are retained.

Had similar speeds before the tweak as you.
Tests afterwards have been getting:
1200-3200kbs and 350kbs~ up
What exactly do your tweaks change?

[TWEAKS] List of build.prop tweaks (can be applied to stock ROM)

I'll share with you the /system/build.prop tweaks I have in the upcoming Nova.
You can do this on any ROM, even on stock, you just need a file manager with root access and built-in editor. Edit this file and add/change/remove values as follows.
Here we go:
Code:
# Force launcher into memory
ro.HOME_APP_ADJ=1
# Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
# VM Heapsize; 512MB RAM = 48 is better
dalvik.vm.heapsize=48m
# Render UI with GPU
debug.sf.hw=1
# Decrease dialing out delay
ro.telephony.call_ring.delay=0
# Helps scrolling responsiveness
windowsmgr.max_events_per_sec=150
# Save battery
wifi.supplicant_scan_interval=180
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
# Disable debugging notify icon on statusbar
persist.adb.notify=0
# Increase overall touch responsiveness
debug.performance.tuning=1
video.accelerate.hw=1
# Photo and video recording quality tweak
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
# 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
# Net tweaks
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
# Disable blackscreen issue after a call
ro.lge.proximity.delay=25
mot.proximity.delay=25
# Fix some application issues
ro.kernel.android.checkjni=0
# Phone will not wake up from hitting the volume rocker
ro.config.hwfeature_wakeupkey=0
# Force button lights on when screen is on
ro.mot.buttonlight.timeout=0
# Disable boot animation for faster boot
debug.sf.nobootanimation=1
# Miscellaneous flags
ro.config.hw_menu_unlockscreen=false
persist.sys.use_dithering=0
persist.sys.purgeable_assets=1
dalvik.vm.dexopt-flags=m=y
ro.mot.eri.losalert.delay=1000
# LG flags
persist.service.pcsync.enable=0
persist.service.lgospd.enable=0
Adding some more (14/08/11) for Nova v4...
Code:
# Change ROM name
# (forgot to add this one before)
ro.build.lge.version.release=My ROM name
# Disable LG ****
# (flex must be enabled or phone app will FC) - [U]needs moar testing[/U]!
user.feature.flex=true
user.feature.lgdrm=false
user.feature.lgresource=false
user.feature.lgpoweroff=false
user.feature.ls_event=false
user.feature.ls_normal=false
user.feature.sui=false
If anyone has some other tweaks or better values (tested of course) please do share.

Thanks! I go to try with the Orange stock rom v10b.

Nice Noejn.
# Helps scrolling responsiveness
windowsmgr.max_events_per_sec=150
Here I use 260 and it is very smooth and responsive. The maximum value for this tweak is 300.
# Save battery
wifi.supplicant_scan_interval=180
180 is the scan interval in seconds so you can use a lower or higher value.
Good topic

Noejn said:
Code:
# Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
This will make for very large files. I would suggest using a value of 90-95, this will be indistinguishable from quality 100 while leaving smaller files. You can test this yourself by encoding any high quality image using various JPEG quality settings with the image tool of your choice.
Code:
# Net tweaks
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
I don't know what those values used to be in their default state, but I am sure that it isn't sensible to use the same values for all networks. TCP buffer sizes should consider bandwidth and delay of the connection, which are both vastly different between edge and wifi for example.
Other values which seem interesting are:
Code:
user.feature.lgdrm=false # disable lg drm service
I can confirm this will disable the lg drm service - I have no idea what it does, but apparently I don't need it.
Code:
user.feature.flex # don't disable this
flex must be enabled, else com.android.phone and com.android.mms will crash constantly.
These can be disabled without visibly breaking something:
Code:
user.feature.lgresource
user.feature.lgpoweroff
user.feature.ls_event
user.feature.ls_normal
user.feature.sui
Anyone know what they do?
Click to expand...
Click to collapse

launcher into memory
ro.HOME_APP_ADJ=1
Click to expand...
Click to collapse
can also be used using another launcher, like Launcher7 or Zeam? Have i change something?

Wady el-Natrun said:
can also be used using another launcher, like Launcher7 or Zeam? Have i change something?
Click to expand...
Click to collapse
Of course =) It will do the same for every launcher. It isn't specific for LG.

I really don't get it... If this value actually given a better performance, why didn't those LG's engineer use this value for stock ROM?
They do know aren't they?

i04055 said:
I really don't get it... If this value actually given a better performance, why didn't those LG's engineer use this value for stock ROM?
They do know aren't they?
Click to expand...
Click to collapse
Ask them, they come to this forum.

don't tell me they come here to learn how to make a better ROM...

Maybe the factory setting is for failsafe defaults. Like ones on computer BIOS, only advanced user dare to change to their own setting.
Sent from my LG-P970 using Tapatalk

Noejn, but...his change are already in your NOVA rom?
Becouse when i open the build.prop i found all this tweaks. (i have your rom)

of course, it is already included in teh Nova ROM....

digitalfrost said:
Noejn said:
Code:
# Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
This will make for very large files. I would suggest using a value of 90-95, this will be indistinguishable from quality 100 while leaving smaller files. You can test this yourself by encoding any high quality image using various JPEG quality settings with the image tool of your choice.
Click to expand...
Click to collapse
I would also prefer a quality factor of 90-95% in Nova as 100% results in much larger files and only slightly better quality.
Click to expand...
Click to collapse

lesp4ul said:
Maybe the factory setting is for failsafe defaults. Like ones on computer BIOS, only advanced user dare to change to their own setting.
Click to expand...
Click to collapse
My guess is they can't lose time on experimental values.
They will go for stable and heavily tested ones already.
digitalfrost said:
Code:
# Raise JPG quality to 100%
ro.media.enc.jpeg.quality=100
This will make for very large files. I would suggest using a value of 90-95, this will be indistinguishable from quality 100 while leaving smaller files. You can test this yourself by encoding any high quality image using various JPEG quality settings with the image tool of your choice.
Click to expand...
Click to collapse
Irrelevant. You have plenty of space in /system partition and having this really won't affect your internal memory because:
a) you already have reserved space for system partition
b) we're talking about 3 MB, tops. considering I removed 80% of LG applications which account for like 150 MB do you think that system partition is that small?
So it's a luxury we can perfectly have. Besides, I do notice 10% of quality difference.
digitalfrost said:
Other values which seem interesting are:
Code:
user.feature.lgdrm=false # disable lg drm service
I can confirm this will disable the lg drm service - I have no idea what it does, but apparently I don't need it.
Click to expand...
Click to collapse
Nice tip.
But they have a whole partition for that service, it's strange you don't notice a difference.
Wady el-Natrun said:
Noejn, but...his change are already in your NOVA rom?
Becouse when i open the build.prop i found all this tweaks. (i have your rom)
Click to expand...
Click to collapse
In the new version yes. In the old one I guess a missed a few.

@Noejn
build.prop tweak. it can use in stock firmware v10e?

Noejn said:
My guess is they can't lose time on experimental values.
They will go for stable and heavily tested ones already.
Click to expand...
Click to collapse
Yes it could be, too, LG r&d guys surely knew about this and decided to setup this defaults. That's why smart devs like you and other nova contributors should maximize this phone potential, what next?
Sent from my LG-P970 using Tapatalk

i04055 said:
of course, it is already included in teh Nova ROM....
Click to expand...
Click to collapse
Yeah, I didn't found any changeable because they are already tweaked haha.
Sent from my LG-P970 using Tapatalk

Is it right that i must add the most of your tweaks in stock rom?
Because i can't find these lines in stock rom build.prop!
There is only "dalvik.vm.heapsize=32m" to find!
And if i add these tweaks, i can simply write them on the end of the page?
With or without the "#" line?
Thank you

# Disable blackscreen issue after a call
ro.lge.proximity.delay=25
mot.proximity.delay=25
this option didn't work for me... I even tried to change do 10, 3, even 1, I didn't see any difference...

Applied only few tweaks to stock 10e:
mod sql by Noejn
ro.HOME_APP_ADJ=1
debug.sf.hw=1
debug.performance.tuning=1
video.accelerate.hw=1
And now UI seems a bit too responsive and fast in some cases, heheheh

Build.prop tweaks

Hi,
I found this in the Optimus 3D section:
http://forum.xda-developers.com/showthread.php?t=1249628
I thought, it can work on the 2X, too:
adixtra said:
You must add entire line and restart phone.
To make the phone ring faster when dialing out:
ro.telephony.call_ring.delay=0
Disable blackscreen issue after a call:
ro.lge.proximity.delay=25
mot.proximity.delay=25
Better scrolling speed:
windowsmgr.max_events_per_sec=160
To save battery by decreasing the amount of time Wifi looks for an access point:
wifi.supplicant_scan_interval=250
and save battery
pm.sleep_mode=1
ro.ril.disable.power.collapse=0
Increase touch responsiveness
debug.performance.tuning=1
Change the Dalvik VM heap size:
Edit this value, the line exist in oryginal build.prop
dalvik.vm.heapsize=32m(standard value)
Enable the hard key lights when screen is on:
ro.mot.buttonlight.timeout=0
Disable boot animation:
debug.sf.nobootanimation=1
Render UI with GPU
debug.sf.hw=1
Keep launcher into memory:
ro.HOME_APP_ADJ=1
Click to expand...
Click to collapse

Flix123 said:
Hi,
I found this in the Optimus 3D section:
http://forum.xda-developers.com/showthread.php?t=1249628
I thought, it can work on the 2X, too:
Click to expand...
Click to collapse
So what you waiting for to try?

Aint those allready in build.blah... looks like that..

jaspi72 said:
Aint those allready in build.blah... looks like that..
Click to expand...
Click to collapse
Sorry but that not true!

I've found these together with more in here:
http://forum.xda-developers.com/showthread.php?p=16833651
I am currently using some of them and the phone works nicely!

I tested some of these, but I can't find a difference.

kabecilhas said:
Sorry but that not true!
Click to expand...
Click to collapse
Sorry but thats true!!! In thanatos i have allmoust all of those.

In thanatos, but not in stock V20L.

Im using gr5 and dont get any improvement.

Nexus 7 touch response FIX

Hey Guys,
So i got my nexus 7 about a week ago and had noticed a touch response delay and it made scrolling through the homescreen and webpages a pain. I searched around last night and this morning and found these build prop tweaks.
#Response
debug.performance.tuning=1 - Increases touch responsiveness.
video.accelerate.hw=1 - Increases touch responsiveness.
windowsmgr.max_events_per_sec=150 - Increases scrolling responsiveness.
I aslo have fauxclock 123 installed from the play store and disabled the tegra 3 smart dimmer. After doing both i see a substantial increase in responsiveness. let me know if anyone else gets the same result.

Do you add these to the build prop yourself, or are these supposed to be in there already with a different value?

Did you update to 4.2.1? It fixed all my issues.
Sent from my Nexus 7 using xda premium

Im on stock rooted 4.2.2 and still have slow scrolling and bounce back issues, i have just added these lines to my build prop and am giving it a go, i will report back with result, thanks for this! I hope it makes it better!

leonclement said:
Im on stock rooted 4.2.2 and still have slow scrolling and bounce back issues, i have just added these lines to my build prop and am giving it a go, i will report back with result, thanks for this! I hope it makes it better!
Click to expand...
Click to collapse
I am running Glazed build 4.1.2. How do I apply these fixes? Is this something I can do by myself or should I rely on a dev?
Edit: Upon further research, it seems that these values should be applied to /system/build.prop right? I don't see those headings anywhere, do I just copy and paste those 3 lines anywhere into the file?

Worked perfectly on my 8GB Nexus 7 running Paranoid Android 3.15. You rock!

Atrix2destroyer said:
I aslo have fauxclock 123 installed from the play store and disabled the tegra 3 smart dimmer. After doing both i see a substantial increase in responsiveness. let me know if anyone else gets the same result.
Click to expand...
Click to collapse
there are cheaper options to disable smart dimmer than spending $4.
in terminal:
echo "0" > /sys/devices/tegradc.0>smartdimmer/enable
if you have rom toolbox, you can go into the scripter app, create a new script with that command and set it run at boot.
if you want purchase an app to do it for you: https://play.google.com/store/apps/details?id=com.widgets.big.tegra.prism.toggle

cnstarz said:
there are cheaper options to disable smart dimmer than spending $4.
in terminal:
echo "0" > /sys/devices/tegradc.0>smartdimmer/enable
if you have rom toolbox, you can go into the scripter app, create a new script with that command and set it run at boot.
if you want purchase an app to do it for you: https://play.google.com/store/apps/details?id=com.widgets.big.tegra.prism.toggle
Click to expand...
Click to collapse
Thanks for the heads up... Definitely kind of a waste to spend $4 just to disable that file. But fauxclock is a great app definitely worth the money

Homescreen icons always redraws

hi all
my Xperia TX 4.3 maybe have problem all icon at main home screen always redraw when i run an app then quit by press Home button, i add
this code ro.HOME_APP_ADJ=1 to build.prop but didn't solve my problem. please help me. thanks.

ok, i've got it. check Disable HW overlays in develop options and no more redraw icons

devilmaycry2020 said:
ok, i've got it. check Disable HW overlays in develop options and no more redraw icons
Click to expand...
Click to collapse
http://www.jeffmixon.com/examining-build-prop-tweaks-android-ics-comprehensive-guide-part-2/
I recommend reading part 1 also, but just to summarize:
ro.HOME_APP_ADJ – BUSTED
This property is supposed to “keep the launcher in memory” under the assumption that it would somehow make it faster. Unfortunately, this is a leftover Gingerbread property that no longer functions in ICS.
Gingerbread:
Code:
// These values are set in system/rootdir/init.rc on startup.
...
HOME_APP_ADJ = getIntProp("ro.HOME_APP_ADJ", true);
ICS:
Code:
static final int HOME_APP_ADJ = 6;
Google likely removed the ability to configure this value via a build.prop setting in ICS so that users could not set inappropriate values here.
SUMMARY
As we have seen many times already, there are no “magic properties” that you can set that will simply make your phone [insert desired superlative]. That is not to say that all build.prop settings are pointless. Some can actually provide some useful functionality. The key is not to blindly throw a slew of “tweaks” into your build.prop, but to carefully consider each one and know what they do (if anything) before using them.
That’s it for part two. Let me know what build.prop settings you want to see in part three!
Click to expand...
Click to collapse
If you really want to keep your launcher in memory, you can use App Settings (xposed module); I know for a fact it works because I use it, or you can even do it yourself with a script such as:
#!/system/bin/sh
sleep 60
PPID=$(pidof com.whatsapp)
echo "-17" > /proc/$PPID/oom_adj
Click to expand...
Click to collapse
To lower the oom value of the app you want to avoid getting killed off by android.