Setting up the Android debug bridge can be a tad tricky, but given enough time I’m sure you’d figure it out. The gist is that you have to download a USB driver from Archos, and it links you to an article on developer.android.com for instructions on how to install it. The instructions seem a little confusing, as Google has made its own template USB driver and mentions it in this article. Once you realize how to sift through that, you have to actually install the darn thing.
The ADB driver for the Archos is available under the downloads section of the support center, which is currently available at this link. Scroll down until you see the section on the ADB, and download the driver.
The article only mentions Vista and XP, but what if you have Windows 7? It really shouldn’t be too much more difficult. What initially causes confusion about the article is what to overwrite with the new driver you were given, as by now you have no doubt already connected your android device. The answer: potentially nothing. Go to your device and turn on USB debugging first (mine is under Application -> Development ). When that device is detected (or if you’ve already turned on debugging before), that is the one that is going to be replaced by the driver. Keep in mind that you should probably unplug and plug your device in again to the computer if you enable USB debugging while connected, otherwise Windows might not notice.
Under Windows 7 (in my case, 64 bit), it’ll say it found new hardware and start looking for drivers. You cannot cancel this process or specify a driver from the start. The only thing you can cancel is the search on Windows Update, which I did to save time.
Once it fails to find a suitable driver (or installs some random driver of its choosing), go into the device manager located under the control panel category Hardware and Sound.
When that loads, look for your device, right click it, and select “Update driver software”.
Select “Browse my computer” and locate the directory where you extracted the ADB driver. Make sure that search subfolders is checked on that screen. Allow the unverified driver to be installed, and look back in the device manager.
Don’t forget at this point to follow the instruction on Archos’ website (link provided earlier) about the create of the ini file with the manufacturer ID.
From here, I recommend restarting both your PC and Android device; I initially had connection problems without doing so. If the adb server is running, you could try adb kill-server and start-server to see if it’ll notice without a restart.
You can check if the device is happy by following instructions in that article. If you’ve got Eclipse set up for development, you can simply select your project and choose “Run as -> Android Application”. If you’ve set it to ask you what device every time, you’ll see a list that contains your AVDs and actual device. If your device says “Offline” it’s having some connection problems. If you haven’t yet, try restarting both devices. If you have already restarted both devices, try unplugging your device and plugging it back in again (as per the advice to enable USB debugging before connecting the device). Otherwise, hit up google. Then you simply wait 10-15 seconds and your application will magically start on your device. Fun!
From here, under Eclipse I like to set it up to ask me how to run the application each time. Go to run -> run configurations. Select your project (or create a new config) and hit the Manual radio button.
