Author Archive

SVN – How to fix “working copy locked”

What causes this problem

Sometimes when you try to perform a svn action (such as commit, add, revert, etc), the connection or something else fails partway through.  SVN will lock itself so that it cannot be corrupted by any other subsequent failures.  I’ve mainly experienced this while using TortoiseSVN, although I bet it can happen if you are using SVN via command line or any other client.

Usually when you find out that your SVN repo is locked, you receive a message like this:

svn: Working copy ‘/myrepo/repodirectory’ locked
svn: run ’svn cleanup’ to remove locks (type ’svn help cleanup’ for details)

Every now and then it won’t tell you to try to execute a cleanup to fix the issue.  This can be frustrating.

How to fix it

Running svn cleanup typically fixes your problem.  If not, you will need to make sure you are at the root of your repository.  For example,  if you are in ‘/myrepo/repodirectory,’ you will need to ‘cd ..’ so that you are at ‘/myrepo’ and then try executing ‘svn cleanup’ again.

Here’s an example of what I had to do to fix this issue:

C:\myrepo\repodirectory> cd ..
C:\myrepo> svn cleanup

Its nice when fixing something is as simple as a svn cleanup.


Your Words are Wasted

Recently, I read “Your Words are Wasted” by Scott Hanselman:

You are not blogging enough. You are pouring your words into increasingly closed and often walled gardens. You are giving control – and sometimes ownership – of your content to social media companies that will SURELY fail. These companies are profoundly overvalued, don’t care about permalinks, don’t make your content portable, and have terms of service that are so complex and obtuse that there are entire websites dedicate to explaining them.

This is the main reason why I’m going to start blogging again.  Very insightful.

How to: Install an ADW theme and apply it

So you have ADW.Launcher and you’ve been hearing all this great stuff
about how you can theme it. Here’s a quick how to that can help you
get a theme running on your android device to theme adw.launcher.

Step One: Download ADW.Launcher
You need adw.launcher to be able to use an adw theme.  So the best way
to do this is to search in the android market and install

click here to download it from your phone

Step Two: Download an ADW Theme
In order to theme the adw.launcher, you must download an adw theme
from the android market.  This is easy, search for “adw theme” and
then pick whichever theme you like best. ( some of my favorites are
gala s adw theme, adw ubuntu theme and adw elegant theme )

Step Three: Set the Theme
This is where most people get lost.  If you follow my directions, this
will be really simple.

  1. go into adwlauncher settings (from home
    screen hit menu->adwlauncher or if you’re using a custom rom it could
    be in your settings)
  2. click on theme preferences (if you do not see this, you may have an
    old version of adw.launcher –themes came out in version 1.0)
  3. click on select theme and choose which theme you would like.
  4. click apply theme and you’re done!

Tip: How to fix the GPS issue on the T-Mobile Samsung Vibrant

Some of you might have received your T-Mobile Samsung Vibrant this past week and thought, “hmm.. lets test out google maps/navigation” and were disappointed to find that you get an error saying somewhere along the lines of “GPS was unable to find your location.”

i found a solution online, from a user called ‘e-wrecked’, that fixes the GPS issue within five minutes! i used this exact method to fix mine and now mine is working perfectly.  so here it is..


1 – Disable “Use Wireless Networks” – Settings / Location & Security

2 – Dial *#*#1472365#*#*

3 – Under “Application settings” Change “Operation Mode” to MS Based

4 – Under “SUPL/CP Settings” Change the SERVER & PORT to and port 7276 [ Do not use www. in front of supl]


6 – Turn back on the “User Wireless Networks”

7 – Done! you now have a working GPS!

if you ever feel the need (i don’t know why you would) to revert back to the old SUPL/CP server here’s what it was at default:

Server –
Port – 7275

Tip: How to speed up your T-Mobile Samsung Vibrant

The T-mobile Samsung Vibrant is, in general, a very fast device.  Every now and then, the phone lags up or gets stalled in an application and you have to reboot to get it to work quickly again.  I’ll show you a way to speed up your phone and prevent it from these problems.

***This will work on the T-Mobile US branded Vibrant and generic Galaxy S models***


I was directed to this thread discussing issues with the way Samsung stores app data on the phone. Apparently the app data is stored on the internal SD vs. NAND and that is considerably slower. Here are the two methods to fix:

*Both Methods require ROOT* (click here for instructions on how to get root)
*Method 1 limits the space of app data, which can possibly cause issues*
*Method 2 requires writing a new Kernel, which comes with it’s own possible issues*

Method 1:…oted-try-this/
Method 2:…gging-problem/

Hopefully this will be helpful moving forward with the development of this phone!

Note: I have used method 1 which moved the app data from the SD space to the NAND space which significantly increased the speed of my phone, but PLEASE read the links and associated discussion. You are limited to 130MB app space on NAND, which can be limiting depending on which apps you use. Method 2 purports to fix this limitation…

How to check how much app memory you are currently using:

adb shell
cd /data/data
busybox du -h|busybox grep M

How to apply method 1

adb shell
busybox cp -rp /data/data /dbdata
mv /data/data /data/data.bak
ln -s /dbdata/data /data/data

How to undo method 1 (no loss)

adb shell
busybox cp -rp /dbdata/data /data/data.tmp
rm -r /data/data
mv /data/data.tmp /data/data

How to undo method 1 (point of application)

adb shell
rm /data/data
mv /data/data.bak /data/data


How to: Root your T-Mobile Samsung Vibrant

So you have your new Samsung Vibrant from T-Mobile and want to root it? Well, you came to the right place.  Rooting the Samsung Vibrant is A LOT easier than rooting any of the other android phones out there (except probably the Nexus One–That one was practically made to be rooted).

***This will work on the T-Mobile US branded Vibrant and generic Galaxy S models***



1. download the Samsung root update file from here

2. rename the file to

3. mount your phone to your computer and put the to the internal micro sd (the one that is 16GB, not the 2GB one with the folder Movie on it)

4. power off your phone after you unmount your phone

5. now press the power button then right away hold down the vol up and vol down keys until your phone boots into recovery (you might have to try this a few times to get to that point)

6. In Recovery menu select ‘Reinstall Packages’ (use vol down then power to select)

7. Done! you now have root! your device will now reboot

Now that you have root you can overclock your phone, use it as a internet tether, etc.  you can also access/change the internals of your device..

Why should or shouldn’t you root your Samsung Vibrant?


  • Being able to have the lastest Android operating system that has been optimized by developers (e.i. The vibrant is running Android 2.1 and soon here we will be able to have Android 2.2 on our vibrants thanks to the developers at xda forums)
  • Apply themes to the graphics on your device (e.i. make your status bar vanilla instead of black)
  • Use your device as an AP (e.i. connect your computer to your phones internet connection just as you would wifi)
  • Have FULL access to your phones internals
  • and A lot more!


  • Once you’re running a custom ROM you won’t receive OTA updates from samsung
  • you have to depend on developers to continue to provide ROMs to run on your phone

Source :

Test: How changing the max amount of memory per VM Heap can effect your ROM (Cyanogen)

The latest release of Cyanogen’s CM6 features a new feature in Settings called ‘Cyanogen Settings.’  In one of my other posts, ‘Cyanogen CM6 for the nexus one (Review)‘, i briefly covered these new settings that cyanogen has added.  In this post i decided to explore deeper into ‘Cyanogen Settings.’

What are the ‘Cyanogen Settings’?

Cyanogen settings are setting that cyanogen put into settings that allow you to tweak how certain things are shown, how applications are installed, tweak Dalvik VM settings that could speed up your phone and input settings.

Here is a brief summary of each setting from within Cyanogen Settings:

  • Application settings :    allows you to modify your rom to allow application moving and to set the default install location
  • Input settings :    allows you to tweak haptic feedback, change what happens when you long-press home, enable trackball wake/unlock, enable menu unlock and to have the trackball always pulse while the screen is on
  • Performance settings :   allows you to enable JIT (just-in-time compiling), enable surface dithering (which improves image quality) and to change the VM heap size (32 m, 24m, 16m, 12m)
  • User Interface :     allows you to change the color of various different framework variables (such as the clock, notifications, notification bar) –previously in spare parts.

How can changing my VM Heap size speed up my ROM?

I’m not going to go into the physical effects of changing the VM Heap size in cyanogen settings (Note: this is for advanced users only.. i take no responsibility for anything that can potentially happen to your advice.

Cyanogen’s Warning

“Warning dragons ahead! The options in here will change the performance of your system, potentially for the worse. They are included for experimentation and we that you do not file bug reports if you have changed any from the defaults”

But i have decided to experiment and run some tests on how changing the maximum memory size per VM Heap can speed up your phone–or slow it down.

All of the tests i have performed have been in the most controlled environment for consistent tests (fresh reboot, airplane mode on, no programs running, Cyanogen default kernel overclocked to 1113 MHz).  Here are the results of my linpack benchmarks for each memory size using Linkpack for Android:

From the results of my tests, you can see that 12m reigns superior and 32m is pretty close to matching it.  32m is the default that cyanogen ships with his roms, but maybe 12m should be? These tests are just my results when i experimented with them, If you have tested on your phone, you should comment on this with your results and we can see what is the best for our Android devices (make sure to include your device)

A quick tutorial: How to change the max amount of memory per VM Heap using Cyanogen Settings


  1. Install cyanogenmod (CM6) on your android device — only certain devices have CM6 out for them — go to for the download and if needed, to check if your device has Cyanogenmod made for it
  2. From your homescreen, hit menu->settings->cyanogen settings
  3. From Cyanogen settings, click on performance settings
  4. Click VM Heap size to then select the max amount of memory you’d like per VM Heap
  5. Reboot
  6. Done! once your device is booted up, the Dalvik VM will now be running how you specified

UPDATE: These were just the results that i got while using Linpack for Android.  After speaking with Cyanogen, I found out that using 12M IS really fast with small applications BUT with bigger applications this can cause crashes everywhere.  The lower max amount of memory options are there because they work well with smaller devices (G1/MyTouch)

%d bloggers like this: