Remove Applications from Location Services in Security & Privacy on OS X 10.8

After removing an application in OSX 10.8 it still showed up in location services under the security and privacy settings in system preferences. (see picture below)
The reason is that it saves the entries in a binary plist file. You could delete the file and OSX will automatically recreate it. However you would have to re-authorize all the apps that you previously had authorized.
The following process shows how to edit the file and just remove the single application.

Preparation

1. Start terminal and then sudo to a root shell

sudo -s

2. Navigate to /var/db/locationd

 cd /var/db/locationd

3. Make a backup of the clients.plist file

cp -p clients.plist clients.plist.save

4. The plist file is in binary format and to make it editable/readable you need to convert it to xml

plutil -convert xml1 clients.plist

Edit the file

5. Use vi (vim) to edit the clients.plist file and remove the application

vi clients.plist

6. The file will likely contain many application entries. Here is the format of a single application entry (Safari in this case). The entire entry needs to be deleted. (dd for deleting complete lines in vi)

com.apple.Safari  

Authorized

BundleId
com.apple.Safari
Executable
/Applications/Safari.app/Contents/MacOS/Safari
LocationTimeStopped
376348187.80421197
Registered
/Applications/Safari.app/Contents/MacOS/Safari
RequirementString
identifier "com.apple.Safari" and anchor apple
Whitelisted


7. Convert the clients.plist file back to binary format

plutil -convert binary1 clients.plist

8. Restart locationd daemon by force-killing it. Launchd will automatically restart the daemon

killall locationd

In case things go badly, then copy back the original file and restart locationd

cp -p clients.plist.save clients.plist
killall locationd

This should remove the invalid entries from the security and privacy tab in system preferences.

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
persist.sys.purgeable_assets=1

#Increasing the Video Recording Quality
ro.media.enc.hprof.vid.bps=8000000

#Screen Rotate to 270 Degrees
windowsmgr.supportrotation_270=true;

#Increase VM Heap Size (Resolve Some FC's)
dalvik.vm.heapsize=64m

#Render UI with GPU
debug.sf.hw=1

#Increasing It Will Make Mobile Smoother
windowsmgr.maxevents_per_sec=150

#Video Acceleration Enabled
video.accelerate.hw=1

#Increase Performance
debug.performance.tuning=1

#Disable Sending Usage Data
ro.config.nocheckin=1

#Deeper Sleep / Better Battery Life
ro.ril.disable.power.collapse=1

pm.sleep_mode=1

#Ringing Will Start Immediately
ro.telephony.callring.delay=0

#Disable Error Checking
ro.kernel.android.checkjni=0

#Increase Quality of Media Streaming
media.stagefright.enable-meta=true

media.stagefright.enable-scan=true

media.stagefright.enable-http=true

media.stagefright.enable-record=false

#Disable BootAnimation
debug.sf.nobootanimation=1

#Force Launcher to Remain in Memory
ro.HOME_APP_ADJ=1

#Disable Waking Up of Phone by Volume Buttons
ro.config.hwfeature_wakeupkey=0

#Off the Proximity Quickly After Call
mot.proximity.delay=25
ro.lge.proximity.delay=25

#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

#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
net.rmnet0.dns1=8.8.8.8

net.rmnet0.dns2=8.8.4.4

net.dns1=8.8.8.8

net.dns2=8.8.4.4

#Increase Photo and Video Quality
ro.media.dec.jpeg.memcap=8000000

ro.media.enc.hprof.vid.bps=8000000

ro.media.enc.jpeg.quality=100

#Touch Responsiveness
debug.performance.tuning=1

video.accelerate.hw=1

#Scrolling Responsiveness
windowsmgr.maxevents_per_sec=500

#Power Save Tweaks
ro.ril.disable.power.collapse=1

pm.sleep_mode=1

#Disables Debug Icon on Status Bar
persist.adb.notify=0
Faster Scrolling
ro.max.flingvelocity=12000

ro.min.fling_velocity=8000

#Wi-Fi to Scan Less Frequently
wifi.supplicantscan_interval=180

#Improve Battery When No Signal
ro.mot.eri.losalert.delay=1000

#Frees RAM to Allow Applications to Load Faster (edit existing line)
dalvik.vm.dexopt-flags=m=v,o=y

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

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

##Output
/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