I have tried with zero success to get a USB debug connection from a WinXP dev box to a brand X Android 1.6 tablet. I believe I had everything configured correctly on the Android and installed correctly on the dev box, but when the two are connected with a USB cable NOTHING HAPPENS; i.e. Windows finds no new hardware much less a new USB device; therefore, I cannot then install the Android SDK USB drivers on Windows and do the debug thing with Eclipse.
Either the mfg of the Android tablet device has disabled USB debugging and just didn't remove the UI that appears to enable it -- or I've left out some crucial step(s). (The device manual is 100% Chinese and I'm 0% Chinese, so it's no help. The tablet is very nearly, but not, the model A84 7" touch screen 'laptop' at 'www.lezestar.com' in case this helps.)
On the tablet:
• 'Settings/Application/Development/USB Debugging' is enabled.
• Tried 'Settings/Application/Development/Allow mock locations' enabled and not.
• Has 500MB internal flash 'hard disk'
• Has installed 2G SD card
• Firmware: 1.6
• Kernel: 2.6.29-002360g4f8dbbb-dirty
• Build No: 1.7.3
On Dev box:
• Windows XP SP3
• Device Manager finds no 'new hardware' when XP<-->Android USB cable is connected.
• Neither USBDeview.exe (Nirsoft) nor USBView.exe (Microsoft) find any evidence of connection with the Android
• Eclipse Galileo (3.5.2) with Android SDK (for 1.6) and ADV Manager.
• USB Driver package, rev 3. downloaded using ADV Manager.
Other:
• USB ports on both Tablet and dev box successfully connect a USB mouse.
• Tablet and Windows XP have been rebooted often.
Is permanently disabling debugging something that Android manufacturors are allowed to do and therefore I'm trying something that can't be done?
If the mfg has 'disabled' debugging, is there a way to work around this; e.g. download a tool that can change Android OS configuration to reenable it?
Thanks in advance for ideas on what I've missed or could try.
Paul S...