How to Install Apps to the SD Card by Default on Froyo

asforel

Member
Joined
May 4, 2010
Messages
136
Reaction score
0
The Android 2.2 Froyo feature that most people have been looking forward to is likely official support for installing apps to the SD card. It’s something that many feel should have been included from the start, and I beliwve all android users have gotten the dreaded “phone storage is getting low” notification on our Android devices at one point or the other.
There are certain tricks to regain a couple of MB here and there, like clearing the cache that some applications use, but for those with a taste for apps and games, the phone storage limitation has been quite a nuisance. Android users with root access have been able to enjoy the Apps2SD utility, but getting it to work is a comparatively complicated process. Frozen yogurt to the rescue!
To install an app to the SD card on Android Froyo, the application itself needs to support it. Actually most current apps can be moved to the external storage. However, the Froyo system installs all new applications on your device’s internal memory by default, except for those that explicitly request external installation. Luckily, it’s possible to make your Android 2.2 phone put apps on the SD card by default instead. Here’s how:

  1. First you have to enable USB debugging on your Android device from Settings > Applications > Development > USB debugging.
  2. Now you need to download and install the Android SDK on your computer from Android SDK | Android Developers. Once you’ve downloaded and extracted the package . to the folder of your choice, run SDK Setup.exe and click on Available Packages to the left. If you get an error message at this point, enable “Forcehttps://... in the Settings. From the list of available packages, select “Usb Driver package”, click on the Install Selected button in the bottom right corner and follow the prompts.
  3. Connect your phone to your computer with a USB-cable. Your OS will prompt you to install new drivers. Choose to install them from the android-sdk/usb_driver folder. Do not mount your device; you only need to plug-in the cable.
  4. Next, run a command prompt and navigate to the Android-SDK\tools folder. In Windows, this is done by selecting Run from the Start Menu (or by pressing Win+R) and typing cmd. You change drives in the command prompt by entering the drive letter followed by a colon (
    smile.gif
    , and change folders with the CD command. For example, to enter the Android-SDK folder, simply type cd android-sdk.
  5. In the Android-SDK\tools folder, type in adb devices and you should get a serial number starting with “H” in return. All you have to do next is entering adb shell pm setInstallLocation 2. Voilà, you’re done! Android will now install apps to the SD card by default.
  6. To switch back to storing software on the internal memory, enter adb shell pm setInstallLocation 0.
It’s preferable to install certain apps to the main memory, since it will take a while before the SD card becomes available when you start your phone. Applications installed on the memory card will also be unavailable to the system each time you mount your phone as a disk drive. The internal storage is probably quicker as well, even though Google claims that “there is no effect on the application performance so long as the external storage is mounted on the device.” In general, apps that integrate with the Android OS and that often run in the background is better to install on the internal storage, while games and most other applications will have no problem chilling outside on your SD.
 

Ken_photo

Member
Joined
Dec 14, 2009
Messages
53
Reaction score
0
Thanks, but feels too involved for my abilities. Is there a simpler method to move apps already installed by default on the internal memory to the SD card? Very few apps seem to allow it either through manage applications settings or through an app such as "SD move".
 

Rouge

Member
Joined
Jan 8, 2010
Messages
51
Reaction score
0
I keep getting error device not found, any ideas?

Got it drivers were corrupt, thanks for the info.
 
Last edited:
Top