Android: Working with Eclipse’s quirks

January 21st, 2014


About the Author: Dan

I’m Dan Smart, a 38 year old website developer, based in Swansea, UK. I have worked in the software development industry for over 15 years, with experience in web development, mobile handset development, and mobile networks. I work both on websites and web applications with systems such as Wordpress, Laravel, Backbone, Angular.js, node.js and mobile app development with PhoneGap, iOS, and Android. When I’m not developing websites and software, I am a keen runner, involved with mime performance group Innovo Physical Theatre, and also actively involved in my local church.

* Follow me on Twitter or contact me


The Problem

One of the most annoying quirks for Eclipse when working with Android emulators (Android Virtual Devices – AVDs) is that sometimes once you’ve launched an AVD (which can take several minutes), it can lose connection with the emulator. This means that when you try to launch your app on the running emulator, it cannot find the app, and will not output any logs to Eclipse. Sometimes restarting Eclipse or the AVD helps, sometimes it doesn’t.

The Solution

To fix this, we can restart the Android Debugging Bridge (adb), which connects with the AVD, even whilst the AVD is running.

In the console, type:

adb kill-server
This will kill the adb server.

Then restart it:

adb start-server

Then try running your app again – it should find it then connect in Eclipse, and give you the logcat / console output.


Switch to mobile version