Android Development

Sometimes I am a bit over motivated. Thats the reason I upgraded my Ubuntu to 9.10 RC1 yesterday.
Nearly everything worked fine and after 90 minutes downloading and installing Ubuntu 9.10 booted the first time.
The disillusion followed today: What happened with my Eclipse installation?
The LogCat view has no logging type buttons, the Devices view has lost its button for stopping processes and some windows don’t accept a mouse click on their buttons (mostly the OK button). I have to press Enter to get them work.

After a short search I found this bug report for ubuntu: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/442078

A workaround is also mentioned there:

Create a launch script for eclipse with the following code:

#!/bin/sh
GDK_NATIVE_WINDOWS=1 /path/to/eclipse

I am not sure if Ubuntu is responsible or Eclipse, but after using this launch script, everything worked fine.

Android is a great platform which makes creating applications for mobile devices much easier than before. But in the progress of creating your applications you are bound to face bugs. For this purpose you need a good understanding of debugging your software. In this article I will explain how to debug your applications using the Eclipse IDE with the Android plugins.

We’ll use the Android Debug Bridge (ADB) which basically is a tool that runs on both your android platform (emulator or device) and your development computer. The ADB can be used via the command line interface, or just simply via Eclipse. We will be using Eclipse to debug since it’s much easier. If you are debugging on a device, you first have to enable USB debugging. Go to the settings of the machine > software > development > USB-debugging (or something like that, my phone is Dutch!)
(continue reading…)