ADB, Eclipse, and Android SDK the Easier Way

Update:  For an even easier installation process, use my 32-bit or 64-bit .deb installers.  Just double click on them and follow the prompt.


Outdated Information: (still works, but not as easy)

Easy Access Links: *** Please read the installation instructions at the bottom of the page. Also the long version is designed to talk you through every step of the process. The short version is for people that just want the abridged version that are comfortable with Eclipse or Terminal. ***


GitHub (if you know how to use it)

DropBox

If my script has been helpful to you, feel free to donate to the cause.


Changelog

• 1.0.3 (6/18/2011) - Setup 99-android.rules automatically, created a symlink for ddms so it can be executed from anywhere -- has to be typed twice sometimes the first time it is run for some reason (multiple displays error).
• 1.0.2 (6/17/2011) - ./android update adb wasn't launching properly.  *Should* now.  The script should end with Eclipse wanting you to install Android SDK Platform-tools.
• 1.0.1 (6/15/2011) - ./android update adb added to script.  Eclipse interaction minimal.
• 1.0.0 (6/14/2011) - Android SDK, Android NDK, Eclipse, ia32-libs automatically installed.  Eclipse and ADT require prompting.

Introduction

Now that I've finished my first release of the script, it has gone through some testing on 64-bit and 32-bit Linux Mint 11 systems and the installer seems to work. Now I wasn't able to completely install ADB with this script because I haven't been able to figure out a way to configure Eclipse from within the script, nor do I know if it is possible. So there is SOME work that you will have to do. I started learning how to program about 5-7 days ago and that was when I set out to make this script. That said, there are bound to be some errors that arise that I probably cannot fix.

BORING STUFF

One thing I'd like to discuss is the logic of the script (skip ahead if you just want the download link and instructions). I wanted to make it so the script could be run multiple times on accident and error check itself. I also wanted to make sure that as long as you had the Android SDK or NDK that you would not encounter problems with them installing again on my script. This will also carry over to any other of my scripts that I plan to make that will call on either of these libraries.  The following files will be installed by the end of the script:  Android SDK, Android NDK, Eclipse, and for 64-bit systems ia32-libs will be installed.  An ADB environment will also be set up so that once the script has been run and terminal has been restarted you will be able to run ADB anywhere by simply typing "adb" after setting up Eclipse.

Things Changed on Your System and Instructions

• To access Android Debug Bridge at anytime after the script has been run and your terminal reset (bash typed or terminal closed and opened) you can type the command "adb" from any location.
• To access the Dalvik Debug Monitor, you can access it by typing the command "ddms" and if you get an error about multiple displays then type "ddms" again and it should start.
• To reference the Android SDK to compiling something, it will be located in the following directory: /usr/local/android-sdk
• To reference the Android NDK for compiling something, it will be located in the following directory: /usr/local/android-ndk
• Eclipse is now installed and most likely located in Applications -> Programming.
• 64-Bit Operating Systems had the package ia32-libs installed for compatibility reasons.

INSTALLATION INSTRUCTIONS (Short Version)
These instructions are for people that are able to more confident with Terminal and Eclipse.  The instructions are not overly complicated, but I have provided a more in-depth tutorial for those that need it.

• Download the file
• chmod +x installer.sh
• sudo ./installer.sh
• Install "Android SDK Platform-tools" and accept the licensing agreement.
• *** Close all instances of Terminal once this is done or type bash ***
• Test ADB in terminal by typing "adb" from any directory. (without quotes)

INSTALLATION INSTRUCTIONS (Long Version)

If you have a GitHub account then you can download the latest version of my code from this link.  That link should provide the latest version of my code when and if I need to make any changes.  The other link that will probably not be updated as frequently is this dropbox link.  If you're getting the code from GitHub, for the sake of this tutorial I will assume you know how to obtain the file.

Step #1:  Download the file and find it in terminal.

When you open terminal, you will need to find where the file is located.  If you're using Linux Mint 11 and Google Chrome, it is most likely going to be in the "Downloads" folder (case sensitive, no parenthesis).  We can change to this directory in terminal by typing "cd Downloads" (notice that the Downloads has a capital D).  You can list the file and directories by typing the "ls" command.

Step #2:  Grant executable properties to the installer.

Once the file has been found and you're in the same directory type the following commmand:

chmod +x installer.sh

Step #3:  Install the file and go afk.

This part takes a long, long time depending on how fast your internet connection is.  Even longer if you have a 64-bit operating system (Don't worry!  The installer figures that out for you!) and has to do a lot of things right now.  You can either read ahead or go do something fun, I'd suggest the latter.  So to initiate this part type the following command and then enter your password:

sudo ./installer.sh

Notice how there is a period and then a forward slash before installer.sh?  Very important to put those in there.

Step #4:  Install Android SDK Platform-Tools


The Android SDK Platform-tools contains the ADB.  Also, if you plan to do any developing in Android this screen will probably be of some use to you.  Start by selecting "Available packages" from the left side and then under Android Repository install the "Android SDK Platform-tools."








Accept the next screen and if you have a pop up that asks if ADB can restart say "Yes."  Close out of Eclipse if you are done with it.

Step #5:  Test ADB and Done!


IF YOU HAVE ANY OPEN TERMINAL WINDOWS RIGHT NOW CLOSE THEM TO REFRESH THE ADB ENVIRONMENT.  Open terminal and type "adb" without the quotes (it doesn't matter which directory you do it from).  You should see a bunch of commands go across your screen to indicate that it worked like below:

If "adb" doesn't prompt anything, try typing "bash" first and then type adb again.

Just a little talk about a side project

Since I have been working more on Linux and Android together, I just wanted to keep people up to date on what I've been doing with my projects and the website. I managed to get the VLC source code compiled into an APK and working. It runs smoothly for various formats, I'd like to do a write up on how I got that working soon and also make an automated script to download the lasted script from their git repository. My hope is to allow the user to learn about it and also give them a quick alternative to updating their APK for the phone that they can swap out for the latest build of VLC while it's still in the alpha state.

The other thing I've been working on is automating as much of the Android SDK / Eclipse process as possible for people that want to start programming and are afraid to come to Linux. I want to do this because I love the idea of an open source community, be it in Linux or Android and really want them to thrive. Linux can be intimidating when you first start using it and can require you to format your computer every time you screw up your system. At least until you figure out the file system and then you can fix almost every problem pretty easily. Google however, seems to make it fairly difficult for a first time person coming to Linux to start programming and I'd like to try to bridge that gap by automating as much of the Eclipse set up as necessary to get more developers working on Android in a Linux environment. I don't know if I'll be able to automate everything required to get a system installed with ADB, but possibly one or two steps away and just requiring GUI interaction in Eclipse (I'm still researching this part, to see if I can do any of this).

In the mean time, if you'd like to make any suggestions for write-ups I'll gladly take suggestions in the comments section or on twitter at @ArchDukeDoug (still waiting for the title to be granted in any country, probably not going to happen). Suggestions allow me to help you and also help myself, so don't be shy with them. If I'm able to do them I will definitely try.

Sync Music to your Android OS Device in Linux with Banshee Media Player

I always had a hard time finding a way to sync my music and playlists easily to my Android phone in Windows. I tried using Doubletwist, Winamp, and even some strange AdobeAIR playlist editor. There was just never a clear cut way to go back and forth with my playlist. Once you figure out how to get Banshee and your Android phone on the same page, the two coexist wonderfully with only a few exceptions. "What are those exceptions?" You might ask. Or you may just skim past this and completely ignore this part and figure out that it's difficult to sync certain file types later. Those exceptions are that you have to edit a file with the MIME Type of the extensions that you want to add. I'll give you a sample of the file I used which includes as many of the MIMES as I could think of at the time and try to include an example in case I missed one so that you can add more to the list.

First thing we want to do is switch Banshee to daily build to get the most up-to-date version. To do this open up terminal and type:

sudo add-apt-repository ppa:banshee-team/banshee-daily
sudo apt-get update
apt-get upgrade

If for some reason Banshee is not installed right now (it is by default with Linux Mint 11), you can install it with: sudo apt-get install banshee

Now connect your phone by USB to your computer and set your phone to USB Mass Storage. Open the root SD card directory with nautilus and create a new empty file (right click -> create document -> empty file) called .is_audio_player and edit it with gedit.





In the empty gedit file put the following information (like above) into the text file:

audio_folders=Music/, Video/

folder_depth=2

output_formats=audio/mpeg,audio/mp3,audio/x-aac,audio/ogg,audio/aac,video/mp4,video/mp4-generic,video/mpeg4,video/quicktime,video/x-matroska,audio/x-matroska,video/vnd.avi,video/avi,video/msvideo,video/x-msvideo

Adding the file to the folder allows Banshee to see that your Android phone is actually a music player. Editing the contents of it will tell Banshee what file formats that the phone supports. The one format that I've had trouble getting to work are *.avi because they use different codecs and I get an error. Now start Banshee up and you should see your phone listed under "Devices" now.





You can import the music from your phone by right clicking on right clicking on the x GB Filesystem and selecting "Import to Library" and that will copy all of your files into the folders. Otherwise you could manually copy the folders from your SD card to the ~/Music and ~/Video folders as well as the playlists and import them into Banshee. If you're importing a playlist, you need to open the playlist with gedit and convert all of the backslashes (\) to forward slashes (/) with the search -> replace -> replace all feature. Once you've replaced all the slashes, try importing the playlist under File -> Import Playlist (try doing them one at a time if you have problems with them leaving songs out).

That's it.  Your device should now be capable of syncing to your Banshee Media Player.  It may take a little playing with to get the playlists set up for your device and your music set up in Linux and organized.  Your videos may also error out depending on if it is supported by the .is_audio_player.

** Extra Notes**

If your video is unsupported by Banshee, you can try adding the MIME-Type to the .is_audio_player by following the format: video/name or audio/name and you can find the name from looking up the extension on wikipedia.  For example:  audio/mpeg,audio/x-wav,video/mpeg,video/quicktime

I believe Apple devices (iPhone, iPad, and iPod) should all work out of the box with this program because of a plugin that comes installed by default.  I'm not 100% positive though, but under Extensions there is one listed for Apple Devices Support listing the three I previously mentioned.  I just am not sure what is required to set that up.