android - Google Glass ADB devices doesn't find. OMAP4430 driver not installed (can't find it!)

Question

Plugging in Glass via USB allows me to browse files and such. But even with debug mode ON I can't get it to show up with the adb devices command. Also my Windows system said it couldn't find an OMAP4430 device driver (which is the Glass SoC I believe).

What do?

Answer 1

This was pretty frustrating, but I got this to work on Windows 7 with these steps, which are similar to what Jenny Murphy described except this actually works and has the right file names etc:

1 - Find your usb driver folder within the adt bundle folder, on my computer it was here:

C:UsersmscheelDevelopmentadt-bundle-windows-x86_64-20130219sdkextrasgoogleusb_driver

2 - Open up the file called android_winusb.inf

Add this magical snippet to both the [Google.NTamd64] and [Google.NTx86] section, which includes the correct PID and VID for Google Glass (Updated May 2014 after helping a student at Boston AnDevCon):

;Google Glass %SingleAdbInterface% = USB_Install, USBVID_18D1&PID_0d02 %CompositeAdbInterface% = USB_Install, USBVID_18D1&PID_0d02

[Update August 2013 - In windows you can find the values for the above by going into Device Manager, right clicking your device > Properties > Details Tab > Change Dropdown to Hardware Ids. Once you have them make sure they match what you put into your inf file, for a developer I helped recently we had to comment out the top two lines above and just use the last two lines]

3 - Go into Device Manager and find the yellow warning icon for Glass, right click it and select Update Driver Software, choose select from computer and enter in the path in step #1 (just the parent folder of android_winusb.inf). My computer gave an anti-virus warning that I dismissed, and shortly after I was able to use Droid AT Screen to mirror my Glass display onto my windows PC, which is great for presentations.

The sweet taste of success:

Note that after this Glass will display in Device Manager as "Android Phone > Android Composite ADB Interface".

Another addition, May 2014, from helping a user: Sometimes Windows will cheerfully tell you that your drivers are already up to date and you are using the correct ones. Even though you made modifications to the inf file. "The best driver software for your device is already installed”. If this happens look for the bottom option during the workflow “Let me pick from a list of device drivers on my computer”. Its not easy to spot and seems like the same choice you are making, but keep an eye out for it. This will help force Windows to start using your changes.