Android Tweaking Demystified [Part-I] “build.prop Scripts”

It’s been around 10 months when I laid hands on my first android device and since then it has been an adventurous ride full of surprises, navigated by my curiosity alone, with something to learn every moment, each day. Android is a playful platform which gives the user complete control over the device to manipulate and customize it according to his needs contrary to pre-existent operating systems, be it undervolting to draw out hours of battery life out dying moments of the phone or overclocking it to play processor priority seeking games, be it making the device snappier or running even unsupported apps on the device.

I’ve decided to share all the tweaks and scripts, those I implemented successfully, in this “tweaking demystified” series. So to start with, here is a bunch of ‘em which could boost your device making you realize its true capabilities. They work on most of the android devices be it on stock firmware or on Custom Roms, but most of the custom roms come with their own set of tweaks which doesn’t require further modifications as they are already hardware optimized by their developers.

So this set of codes specifically meets the requirements of those on stock firmware.

We aim to modify the build.prop file which is accessible via a file manager with root capability.

The build.prop file is your android handset’s ‘ID card’. It tells applications the specifications of your device, so that apps can change their interface or function for your specific device. Editing the build.prop file is most commonly used for changing LCD density, build number and your device’s model or manufacturer. Changing your ‘fingerprint’, model or manufacturer can trick some apps in the market to become compatible with your device.

WARNING: Be very careful when editing this file. Accidental deletion or alteration will cause some pretty serious inconvenience. If you don’t know what it does, don’t change it!

So better make a copy of that file and store it in your sdcard as a backup in case something goes wrong.


  1. Rooted device.
  2. Es File Explorer (free app)

Navigate to Your build.prop File:

Our build.prop file’s location is /system/build.prop. Open up the Es Explorer file manager .

Tap the “Favorites” icon on the top left corner .

Now choose the icon pointed by the arrow in the next picture. It will lead you the root directory of your device.

Choose the system directory and then the build.prop file.

And finally choose “ES Note Editor” and the build.prop file will open up

Tap anywhere to toggle soft keyboard on the file.

Having reached this file some scripts can be edited or written to optimize the overall performance of the device. Here’s the list.

debug.sf.hw = 1     (Render UI with GPU (relieves pressure on CPU).)

dalvik.vm.heapsize = 32m     (Set size of Dalvik Virtual Memory heap (how much RAM each instance of the VM is allowed); depending on how much RAM that is available to a device, this can be increased.)

windowsmgr.max_events_per_sec = 120     (Increase to improve scrolling response.)

debug.sf.nobootanimation = 1     (Disable boot animation(speeds up boot time).)

ro.sf.lcd_density = 240     (Set screen density; change according to your device or what suits you, a lower value will display more but may be too small to use on a device with a smaller screen. Also note that changing the pixel density will make some applications in the new market ‘incompatible with your device’.)

ro.telephony.call_ring.delay = 0     (Decrease dialling out delay.)

pm.sleep_mode = 1     (Increase battery saving potential.)

video.accelerate.hw=1 or 0     (Whether to use hardware acceleration to render videos, doesn’t work on all devices.)


pm.sleep_mode=1     (Saves battery.)


mot.proximity.delay=25     (Disable blackscreen issue after a call.)     (Fix some application issues.)


Please leave your useful comments below. I’ll try my best to resolve the issues, if any.

Disclaimer: Blogtechnika cannot be held responsible for any damages to your device. Perform these tweaks at your own risk.


2 Responses

Leave a Reply

Your email address will not be published. Required fields are marked *