Gecko:StandardAndroidEnvironment

The goal of this page is collect all the goop needed to put together a good android development environment. The eventual goal is for this page to be "fab instructions", for churning out pre-set-up devices to send to developers.

Verizon Galaxy Tab (old one)

Not well supported. GSM models are though.

T-Mobile Vibrant (Galaxy X)

Not well supported. i9000 is though.

Nexus S

Note: the Nexus S has a different vendor ID, "18d1", than the Samsung one (for whatever reason). Make sure udev knows about it.

For the Sprint model ("crespo4g"), follow the directions here for downloading the binary blobs. Make sure to follow the Sprint-model-specific directions. Then follow the instructions to build and flash. Yep, it's that easy.

Motorola Xoom

The source for the Honeycomb version of the Android Open Source Project isn't available and never will be. That means we can't build custom development images ourselves.

Dependencies

You only need to set these up once on the host machine.

General

• Windows installation. Motorola drivers needed for fastboot are only released for Windows. We'll have to fix that somehow ...
• Android SDK. Since you're on Windows, you'll need to ensure you've copied all the .dll's from $SDK/platform-tools to $SDK/tools. Sigh.

Specific

Install Motorola USB drivers. Reboot.

Unlock the bootloader

WARNING: This voids your warranty, even if you later relock the bootloader. I doubt you care though.

Plug in your Xoom to USB.

Shift+right-click on the $SDK/tools folder in the Windows File Explorer. Choose "Open command window here" from the context menu. At the command prompt (tools>), type

adb devices

You should see a device identifier printed to stdout. If you don't, something in your setup is messed up.

Next type

adb reboot bootloader

which reboots the Xoom into the bootloader itself. You should see the normal Motorola splash screen along with some text in the top-left that says "Starting Fastboot Protocol Support.". (It never stops showing that, even when the "fastboot protocol support" is ready, which is kind of annoying.)

Now run

fastboot devices

You should see device identifier like the one printed by adb devices. If you don't, something is wrong. Now you're all set to unlock the bootloader, which requires wiping the entire system for some unknown reason.

WARNING: You're about to wipe the entire device. All your data etc. will be erased. This may not be what you want.

Run

fastboot oem unlock

If all goes well, the Xoom will warn you again about what was noted above, that unlocking the bootloader permanently voids your warranty. Follow the on-screen instructions to accept.

If all goes well, the Xoom will wipe itself and reboot into its first-boot setup screen.

Build a custom image

Placeholder

Galaxy S II (not ready yet)

The Galaxy S II will happily go into "download mode", ready to accept new images. To get there

adb reboot download

The instructions previously here were probably bad. New ones forthcoming.