I can't tell if your still kidding around or not, but that's just unnecessary . And maybe my reply had a little too much snark (probably because I was quoted in the complaint). So here it goes.

none of this is officially supported:

There shouldn't be anything that is killing your adb session. Starting DDMS will kill it though, but it should be able to be reconnected after DDMS is started. After you enable debug, even if you go back to the screen and the check box in not checked, adb is still enabled (until reboot). If you attempt to check the box again and put in the wrong password, you'll get kicked off of adb. There are many logger android apps out there that could give you insight as to what is killing your connection (if it is occurring on the device side, as opposed to your PC side). If your a linux user, dmesg for kernel traces.

There still might be issues installing an app via "adb install", so I would (genuinely) suggest email/USB just for the install process if adb install doesn't work.

All that being said, the eDGe is not an android development platform. If you would like to develop Android (only) apps that work on the eDGe, I would use the 1.6 emulator from the google SDK. If you are trying to write an app that will utilize both sides of the eDGe I would suggest waiting until our SDK (yeah...I know) comes out, or you are just going to frustrate yourself. If you still want to develop and test on the eDGe, please do so, but understand that you're using the product in a way we haven't given full design support to yet. So if something quirky happens, such as getting knocked off of a developer debug connection, you're on your own for the time being.

I hope this helps.