Samsung Galaxy S3 Optimization via build.prop

One major point speaking for Samsung devices in general is the usual unlocked boot-loader that allows you to modify the system partition. The build.prop file is your device’s “ID Card”. It contains the device’s specifications that allows an application to customise the program according to your device’s specification.

Editing the build.prop file is most commonly used for changing LCD density, build number, the device’s model and manufacturer information. Changing the “fingerprint” of your device can trick some applications in the market into becoming compatible with your device 😉

What you will need

Simple work-around: remove all settings from parental controls

  • a rooted Galaxy S3
  • a file explorer that allows you to remount and explore /system partition (e.g. ES File Explorer)
  • Preferably a nandroid backup of your device (just in case)

Proceed with caution: Attempting to modify and/or overwrite core system files may be detrimental to the function of your device, which could result in lost and unrecoverable data. Make sure to back up your device before continuing with this guide.

Step 1. Open the build.prop file

Start ES File Explorer and navigate to /system. Press the menu button and choose the category: root explorer. Select Mount R/W and remount /system partition as writeable. Open the build.prop file with the included ES Note Editor.

Step 2. Choose the settings to add

#Fast Reboot

#Increasing the Video Recording Quality

#Screen Rotate to 270 Degrees

#Increase VM Heap Size (Resolve Some FC's)

#Render UI with GPU

#Increasing It Will Make Mobile Smoother

#Video Acceleration Enabled

#Increase Performance

#Disable Sending Usage Data

#Deeper Sleep / Better Battery Life


#Ringing Will Start Immediately

#Disable Error Checking

#Increase Quality of Media Streaming




#Disable BootAnimation

#Force Launcher to Remain in Memory

#Disable Waking Up of Phone by Volume Buttons

#Off the Proximity Quickly After Call

#Signal Tweaks

#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




#Increase Photo and Video Quality

#Touch Responsiveness


#Scrolling Responsiveness

#Power Save Tweaks


#Disables Debug Icon on Status Bar
Faster Scrolling


#Wi-Fi to Scan Less Frequently

#Improve Battery When No Signal

#Frees RAM to Allow Applications to Load Faster (edit existing line)

Step 3. Add chosen settings to the build.prop file

From the list above choose the options to add to your build.prop file. Scroll down to the bottom of the file and press the overflow button in the actionbar. Choose Edit and append the settings to the file.

Back-out of the editor to save the file

Step 4. Reboot the device + clean up

To apply those changes:

  1. reboot into recovery – mode by restarting the phone and holding down Volume Up + Home + Power Buttons
  2. in recovery mode choose: Wipe Cache and Wipe Dalvik Cache
  3. still in recovery mode choose: reboot now

Depending on the settings you added the changes might not be noticeable immediately.


MacOS X Mountain Lion parental control running at near 100%

After recently upgrading to Mountain Lion I now have the process named “parentalcontrolsd” running 24/7 even though I do NOT use any parental controls.

58174 parentalcontrolsd root 98.7 9 72.3 MB Intel (64 bit) 138.4 MB

Simple work-around: remove all settings from parental controls

  1. Disable parental controls on all users.
  2. Delete the folder /Library/Application Support/Apple/ParentalControls
  3. Restart the Mac
  4. Enable parental controls again (if needed).

Monitor HDD Temperatures in Debian

Modern storage drives (harddisk/ssd) support S.M.A.R.T (Self-Monitoring, Analysis, and Reporting Technology) and allow to examine the current drive status through a standardized interface. The design goal during S.M.A.R.T’s development was to anticipate drive failures before they actually happen. HDDTemp utility can read out the temperature of your hard drive by reading the data from S.M.A.R.T

Install hddtemp

To install hddtemp under Debian/Ubuntu enter the following command into a terminal.

$ sudo apt-get install hddtemp

You can also perform source code installation. Download the source code tar ball here.

$ tar -jxvf hddtemp-0.3-beta15.tar.bz2
$ cd hddtemp-0.3-beta15
$ ./configure
$ make
$ sudo make install

Monitor hard disk temperature

To see the temperature for /dev/sda, enter the following command:

# hddtemp /dev/sda

/dev/sda: Hitachi HDS723020BLA642: 36°C
# hddtemp /dev/sd[a-k]

/dev/sda: Hitachi HDS723020BLA642: 37°C
/dev/sdb: Hitachi HDS723020BLA642: 38°C
/dev/sdc: Hitachi HDS723020BLA642: 38°C
/dev/sdd: Corsair Force 3 SSD: 128°C
/dev/sde: WDC WD2003FYYS-02W0B1: 37°C
/dev/sdf: WDC WD2003FYYS-02W0B1: 37°C
/dev/sdg: WDC WD2003FYYS-02W0B1: 39°C
/dev/sdh: Hitachi HUA723020ALA640: 35°C
/dev/sdi: Hitachi HUA723020ALA640: 35°C
/dev/sdj: WDC WD2003FYYS-02W0B1: 41°C
/dev/sdk: WDC WD2003FYYS-02W0B1: 41°C

Dropbox error about monitoring file system

On Linux, the Dropbox client or in general all applications are subject to a default file system limit regarding the number of directories and files an application can monitor for changes.
Dropbox sooner or later will notify you with the following warning:

“Unable to monitor the filesystem – Please run: echo 100000 | sudo tee /proc/sys/fs/inotify/max_user_watches and restart Dropbox to correct the problem.”

The Linux version of the Dropbox desktop application is limited from monitoring more than 10000 folders by default. Anything over that is not watched and, therefore, ignored when syncing. There’s an easy fix for this.

# increases the max-file-watch limit

echo fs.inotify.max_user_watches=100000 | sudo tee -a /etc/sysctl.conf

# to apply the changes without restarting

sudo sysctl -p
sudo dropbox stop
sudo dropbox start