Tethering + Android Development = FAIL

So I wanted to update my BetterTouchTool version while I was on my work network. You would think this was a simple thing, but the damn proxy seems to almost arbitrarily drop connections. So to get around this I was planning to use my Droid X with the free PdaNet app and client to tether my MacBook Pro.  For details on how you can do this yourself, check out this link.

But I hit a snag when initiating the tethered connection:

PdaNet: Unable to open interface (e00002c5)

Really helpful and descriptive error, right? There’s another factor here, though. I neglected to mention that I was actively developing in the Android SDK with Eclipse. As it turns out, the Android Debug Bridge (adb) doesn’t play nice with the PdaNet tether Android app. In fact, it likely that it doesn’t work with any other tether app since it takes full control of the USB debugging connection.

So how do you fix it? Well, you can’t really. The best you can do is make sure you aren’t doing both at the same time. If you are developing in Eclipse for Android against a physical device via USB, you will have to do the following to be able to tether:

  1. Close Eclipse
  2. Kill the adb process
  3. Restart your tether app

With those applications closed, you should be able to successfully tether your computer once again. Hopefully this will save the someone the frustration of tracking down this error themselves.

2 Responses to “Tethering + Android Development = FAIL”

  1. Derjyn says:

    I too stumbled across this disagreement with tethering and development. One question that I’ve yet to find an answer too is? How to update through Eclipse if tethering is your source of internet.

    I believe some work should be done on ADB to allow multiple applications to play nicely… that would be a welcome update.

  2. Anthony says:

    Great fix Tony worked great. Sounds like this is a problem that needs to be fixed but who would we go after Eclipse or Google or someone else…