Root Build.prop edits for D1?

[Lock-N-Load]

I noticed an interesting thread in the Droid X forum about useful Build.prop edits and wonder why there is not one here?

For example (some listed from LexusBrian400 thread):

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.

Or not so useful, but possible for fun..

change your Build Number

ro.build.display.id=FRG01B

to

ro.build.display.id=FRG01B blah blah

now see something more personalized in the settings > about phone > Build Number. Mine says FRG01B Locked & Loaded

To make the phone ring faster when dialing out

ro.telephony.call_ring.delay=3000

to

ro.telephony.call_ring.delay=1000

Now the phone rings pretty much instantly when dialing out.

 

[kratos]

I've read through the build.prop and don't really know what everything stands for. Those are good edits, but I don't really find much use for them for myself.

Thanks for posting this though.

Kratos

 

[Lock-N-Load]

Change Your LCD density

ro.sf.lcd_density=240

to

ro.sf.lcd_density=200

now your icons, text and such will be smaller like changing resolutions on your computer

thanks to altimax98 but it is also first shown in LexusBrian400's above thread

 

[johnlgalt]

be careful about using the last one - it has really odd effects in landscape mode inside of apps, as well as weird effects in certain games.

 

[Lock-N-Load]

sure, all of these could have ill effects. just like any kernel, any ROM, any metamorph or any tweak you try to your phone. Just backup your Build.prop file so you can always go back. use at your own risk.

However, on these tweaks, they are as easy to undo as do.

 

[GirLuvsDroid]

For months now, before installing any new ROM, I always edit the build.prop file to change the wifi scan interval to 360, the ringer delay to 300 and the dalvik.vm.heapsize to 64M (this keeps my very heavy SH2 theme from lagging and having other errors).

 

[Lock-N-Load]

For months now, before installing any new ROM, I always edit the build.prop file to change the wifi scan interval to 360, the ringer delay to 300 and the dalvik.vm.cache to 64M (this keeps my very heavy SH2 theme from lagging and having other errors).

wow that is a high wifi scan interval

care to elaborate here on the dalvik.vm.cache edit? I see some heap size info in our Build file, but not cache?

here is some heap info

 

[GirLuvsDroid]

wow that is a high wifi scan interval

care to elaborate here on the dalvik.vm.cache edit? I see some heap size info in our Build file, but not cache?

here is some heap info

I've found that the 360 scan interval doesn't have any negative effect at all. When I first turn on wifi, it scans and connects, and from there I don't need it to scan anymore.

With respect to what I called "dalvik.vm.cache" -- my apologies, I wasn't looking at the file at the time (and had just cleared my Dalvik cache in Titanium Backup) and I misspoke. I meant the dalvik.vm.heapsize.

 

[Lock-N-Load]

With respect to what I called "dalvik.vm.cache" -- my apologies, I wasn't looking at the file at the time (and had just cleared my Dalvik cache in Titanium Backup) and I misspoke. I meant the dalvik.vm.heapsize.

I was kind of thinking this might have been the case

anyway, what results, differences did you notice that makes you do this change and believe in it?

 

[GirLuvsDroid]

The ONLY reason I do it is because it allows my heavy SH2 theme to run with no redraw lag, FCs or bitmap errors, which I've found to be common on certain ROMs (mainly UD) even with the heapsize setting that large, and with any other ROM if it's set lower than that.