FORUMS

What Do You Think About Fingerprint Scanners?

More and more phones are featuring fingerprint scanners, and with many promising … more

What’s Next for Samsung and Its Flagships?

If we were to say that the Galaxy S6 was a leap of faith made by Samsung, we … more

The Ultimate Showcase of dBrand Skins

In the search for ways to protect, accessorize, and personalize; a user has many options. One … more

Huawei’s Rapid Rise to Third Place in the Smartphone Race

Huawei has quickly grown to become one of the world’s biggest … more

[UPDATED][MOD] LOTS of Build.prop edits!

1,200 posts
Thanks Meter: 163
 
By LexusBrian400, Senior Member on 1st September 2010, 08:26 AM
Post Reply Subscribe to Thread Email Thread
UPDATED 9/4



Ok, so I went through the build.prop tonight and tried a few things out. I figured I'd just post all of my edits for you guys to try and use also. Here goes...

I am listing the changes one by one w/ descriptions, as well as providing all the mods rolled up into a single build.prop which will be posted at the end of these directions. Enjoy

To make the phone ring faster when dialing out, I changed

ro.telephony.call_ring.delay=3000

to

ro.telephony.call_ring.delay=1000

Now the phone rings pretty much instantly when dialing out.


To enable better scrolling speed through lists, I changed

windowsmgr.max_events_per_sec=55

to

windowsmgr.max_events_per_sec=60

Scrolling through the app drawer and contacts and any lists really is now smoother


Now, to save battery by decreasing the amount of time Wifi looks for an access point, I changed

wifi.supplicant_scan_interval = 60

to

wifi.supplicant_scan_interval = 90

Now wifi will scan once every 1.5 minutes when not around a known location instead of once every minute which will save battery.


I also changed the Dalvik VM heap size from

dalvik.vm.heapsize=30m

to

dalvik.vm.heapsize=32m


I remember doing this on my Eris and I was able to run JIT w/ sense enabled (which was a major hassle at the time) So I'm only assuming it will help performance on the X also.


To change LCD Density (How much is displayed on screen) visit my other build.prop mod page

Here -- Droid Life Forum • View topic - [MOD] LCD Density - DIY! - Droid X


And To fix your 2.2 market to display all apps Go

Here -- Droid Life Forum • View topic - [FIX] - 2.2 Market Issues - Show All Apps


Now for everything listed here all rolled up into one single build.prop, download this
http://www.mediafire.com/?25xh9gjwx5meds9

Install using any method of your choice
Method 1 - ADB

1. Download
2. Put the build.prop in your android-sdk\tools folder
3. Connect your phone via usb, make sure it shows up with adb devices
4. adb remount (or whichever way u prefer to mount ur system)
5. adb push build.prop /system/build.prop
6. adb reboot


Method 2 - Root Explorer

1. Copy the build.prop to the root of your SD card
2. Long press on build.prop
3. Select "Copy"
4. Navigate to /system
5. Click R/W in the top right corner
6. Paste, and overwrite
7. Reboot

My results - 1484



EDIT: If you do not like or want to use the LCD Density mod, use this build.prop. Everything else is included.
http://www.mediafire.com/?w4860c0fddw4ao2

-----------------------------------------------------------------------------------
UPDATED BUILD.PROP


Ok here are a few updates.

To enable the hard key lights to stay on while the screen is on and not timeout, I changed

ro.mot.buttonlight.timeout=1
to
ro.mot.buttonlight.timeout=0


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, I changed

mot.proximity.delay=450
to
mot.proximity.delay=150

The delay is almost no longer NOTICEABLE at all. (It was very annoying to me personally)

*Note - this will not include the lcd density mod, but everything else mentioned on this post included. Thanks guys! Enjoy

UPDATED Build.Prop
Last edited by LexusBrian400; 5th September 2010 at 02:28 AM.
The Following 4 Users Say Thank You to LexusBrian400 For This Useful Post: [ View ]
 
 
1st September 2010, 03:05 PM |#2  
LexusBrian400's Avatar
OP Senior Member
Thanks Meter: 163
 
More
WOOT! These made it into an option on Birdmans FlyX in Rom Manager.

Birdmans twitter Update - Added Beesleys buid.prop edits
1st September 2010, 05:08 PM |#3  
Member
Thanks Meter: 1
 
More
Anyone have a stock build.prop? Everything worked fine, I just want a file to fall back on.
1st September 2010, 05:51 PM |#4  
Senior Member
Thanks Meter: 14
 
More
not what you're going to want to hear... but my score dropped. my build.prop before only had the market fix and when i ran the test (immediately after reboot) i got 1390. i pasted your build.prop in and rebooted and ran test again (immediately after reboot) and the score dropped to 1304.

not a huge drop but no where near your score and certainly not a gain.

any ideas as to why?
1st September 2010, 06:11 PM |#5  
Senior Member
Flag Santa Clara
Thanks Meter: 20
 
More
Quote:
Originally Posted by byproxy

not what you're going to want to hear... but my score dropped. my build.prop before only had the market fix and when i ran the test (immediately after reboot) i got 1390. i pasted your build.prop in and rebooted and ran test again (immediately after reboot) and the score dropped to 1304.

not a huge drop but no where near your score and certainly not a gain.

any ideas as to why?

Did you run it multiple times? I am able to get a wide range of scores that are over 100 points in difference each run sometimes....
1st September 2010, 06:18 PM |#6  
acidbath5546's Avatar
Senior Member
Thanks Meter: 37
 
More
@OP
Good post..nice one.

I was wondering if u messed with some other buil.prop.
Couple other thoughts I had to edit :

#Proximity sensor debounce time
mot.proximity.delay=450
# disable touch below 60 pixels
mot.proximity.distance=60

Seems plausible to edit the delay for quicker response .

This defines the max event window manager can
# handle in 1 s. We may adjust this # for performance
# reason later
windowsmgr.max_events_per_sec=55
# This defines the min duration between two pointer event
ro.min_pointer_dur=10

Messed with this at all?
Last edited by acidbath5546; 2nd September 2010 at 03:02 AM.
1st September 2010, 06:25 PM |#7  
Senior Member
Thanks Meter: 14
 
More
Quote:
Originally Posted by cbaty08

Did you run it multiple times? I am able to get a wide range of scores that are over 100 points in difference each run sometimes....

ahhh... nope. just once. ran a couple more times and got the following:

1304 (first one mentioned before)
1482
1486
1481

so ya... that's good. lol. should have run it multiple times with the old build prop to see the difference. suppose i still could, but too lazy to load the old file. hehehehe. thanks for the tip!
1st September 2010, 07:07 PM |#8  
Senior Member
Flag Santa Clara
Thanks Meter: 20
 
More
Quote:
Originally Posted by byproxy

ahhh... nope. just once. ran a couple more times and got the following:

1304 (first one mentioned before)
1482
1486
1481

so ya... that's good. lol. should have run it multiple times with the old build prop to see the difference. suppose i still could, but too lazy to load the old file. hehehehe. thanks for the tip!

No sweat man, enjoy.
1st September 2010, 07:08 PM |#9  
Senior Member
Flag Santa Clara
Thanks Meter: 20
 
More
Quote:
Originally Posted by acidbath5546

Good post..nice one.

I was wondering if u messed with some other buil.prop.
Couple other thoughts I had to edit :

#Proximity sensor debounce time
mot.proximity.delay=450
# disable touch below 60 pixels
mot.proximity.distance=60

Seems plausible to edit the delay for quicker response ...?

ro.telephony.call_ring.delay=3000

Seems like we can lower.

This defines the max event window manager can
# handle in 1 s. We may adjust this # for performance
# reason later
windowsmgr.max_events_per_sec=55
# This defines the min duration between two pointer event
ro.min_pointer_dur=10

Messed with this at all?

I like the idea of making the sensor quicker to respond.... It isn't as bad as it was on 2.1, but I still think it could be quicker
The Following User Says Thank You to cbaty08 For This Useful Post: [ View ]
1st September 2010, 07:46 PM |#10  
acidbath5546's Avatar
Senior Member
Thanks Meter: 37
 
More
I agree...but im not sure if it will have any adverse effects if changed.
It seems to me that as of right now ..with stock rooted 2.2 it takes about 1-2 seconds for the phone to switch between landscape and.potrait ...like counting out loud One ...Two...it switches as soon as I.say two....same for you?

EDIT :
I edited #Proximity sensor debounce time mot.proximity.delay=450
Took it down to 100....and well I really can't tell if its quicker or not ...it seems it but might be a placebo effect ...hasn't given me any issues ...someone else wanna test that and tell me what they think?
Last edited by acidbath5546; 1st September 2010 at 08:01 PM.
1st September 2010, 09:13 PM |#11  
Member
Flag South Ga.
Thanks Meter: 1
 
More
Quote:
Originally Posted by cbaty08

Did you run it multiple times? I am able to get a wide range of scores that are over 100 points in difference each run sometimes....

This is why I dislike quadrant, it's really not a good benchmark tool. Too many factors can influence the score, take the lagfix for some phones, they just replace the file system with the faster ex2, offers little real world difference but because the I/O section of quadrant jumps through the roof then the total score goes much higher than other phones that are actually faster. The paid quadrant is a little better in that it shows how much of the score is from what subsytem or whatever, but the score is too easily influenced by too many factors to be really effective as a benchmark tool. Not to mention it's easy to trick.

Read More
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes