I seem unable to convince Windows 7 (32-bit) to let me manually install the driver for my G1. I recall some similar trouble before, but having looked through previous solutions, this seems -- well, worse.
Looking through the documentation and bug errors, I can't seem to find a fully-documented case of this issue. Once I'm satisfied I know what's going on on the Windows side of things, I'm happy to file the issue for Android's side. This was the previously-reported problem in the issues database: http://code.google.com/p/android/issues/detail?id=2676&q=adb%20windows%207&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars Steps to produce the problem: 1. Download the SDK drivers (for SDK 3). 2. Set the G1 to debug mode. 3. Connect via USB. Windows reports "USB Device Not Recognized" -- but that's correct, as I haven't yet pointed it to the drivers. 4. Open Device Manager, find the associated entry for "Unknown Device" (the one that's the Android). 5. Right click, select Update Driver Software. 6. Select Browse my Computer. 7. Point to the appropriate directory; e.g., C:\android-sdk3\usb_driver \ 8. Windows reports: The best driver software for your device is already installed. Windows has determined the driver software for your device is up to date. Unknown Device I've tried: 1. Manually uninstalling the driver in Device Manager. 2. Uninstalling USB Mass Storage and all the drivers associated with HTC Android using the utility usbdeview, which apparently had worked for some people. http://www.nirsoft.net/utils/usb_devices_view.html 3. Disabling automatic driver installation in the Group Policy Editor, as described here: http://www.addictivetips.com/windows-tips/how-to-disable-automatic-driver-installation-in-windows-vista/ ... and restarting, and unplugging, and trying again, and nothing works. Windows is absolutely convinced that it's smarter than me and its out-of-box drivers are correct, even though they're not. I'm also using the HTC cable; I know someone had even seen an issue with that. I've used this G1 with adb previously under Ubuntu and Windows Vista. These are the kind of USB driver issues on Windows that make me go absolutely bonkers (and I've even occasionally chatted with Microsoft engineers about them, which didn't make me feel any better). Anyone have any idea how to force this driver to install? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
