Have I ever mentioned how much I hate
a) developing for Android
b) using Eclipse
c) developing for Android using Eclipse?
Well, I do. So often you spend more time fighting the tools than you do fighting with code, and today was yet another example.
I have some Moai code that worked perfectly well, both in the Windows host and on my device. I made some alterations to the Lua code testing it to work on iOS ( by the way, the process of getting Moai running on iOS is 10000000x times easier than getting it running on Android! ), so other than some scripting changes, I haven’t changed a thing.
I load up Eclipse click Run and…
[2012-09-03 14:54:20 – DeviceMonitor] Failed to start monitoring 84ef7369
[2012-09-03 14:54:20 – DeviceMonitor] Failed to start monitoring 84ef7369
[2012-09-03 14:54:20 – DeviceMonitor] Failed to start monitoring 84ef7369
[2012-09-03 14:54:20 – DeviceMonitor] Failed to start monitoring 84ef7369
[2012-09-03 14:54:20 – DeviceMonitor] Failed to start monitoring 84ef7369
[2012-09-03 14:54:20 – DeviceMonitor] Failed to start monitoring 84ef7369
[2012-09-03 14:54:20 – DeviceMonitor] Failed to start monitoring 84ef7369
WTF?
So I kill off adb ( adb kill-server ) and restart it ( adb start-server ). Still no luck.
I exit and restart Eclipse. No luck
I reboot my computer and phone. No luck
I switch devices and try a different Android device. No luck
Want to know what it is? USB3.
Seriously, ADB doesn’t play well with USB3, or at least Eclipse+ADB don’t play well with USB3.
I plug into a different port and everything is just fine. Well, except a few more gray hairs that is. 
Totally Off Topic