adb devices cmd not showing my glass

[GoogleCodeExporter]

Hi,

I put the glass on debugging mode. and connected it to my windows 7 system.
And updated the android_winusb file located inside usb_driver with the below 
text for both NTx86 and NTamd64:-

;GoogleGlass
%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_4E11&REV_0216
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_4E11&MI_01
%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_9001&REV_0216
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_9001&MI_01

and then updated the glass driver with the updated file.
When i check device manager it shows my glass under Android device as Android 
ADB Interface.

But when i try to run adb devices it does not list my glass device. So i am 
unable to side load my .apk to glass.

adb command works properly for my android phone

What should i do?

Original issue reported on code.google.com by tricongl...@gmail.com on 20 Jan 2014 at 10:52

[GoogleCodeExporter]

It seems that this is an issue for Windosw 8 and Windows 8.1 too, with 
workarounds needed to get this working, would love to see this supported when 
the developer preview comes around, some Stack Overflow posts on the same 
issue: 
http://stackoverflow.com/questions/20390624/ddms-unable-to-see-google-glass & 
http://stackoverflow.com/questions/20556137/google-glass-isnt-showing-up-as-a-de
vice-on-eclipse-under-ddms-help-please

Original comment by chris...@gmail.com on 21 Jan 2014 at 4:12

[GoogleCodeExporter]

I solved the issue. To make you device detectable as usb updated the 
android_winusb file with below:-
;GoogleGlass
%SingleAdbInterface%        = USB_Install, USB\VID_18D1&PID_9001&REV_0216
%CompositeAdbInterface%     = USB_Install, USB\VID_18D1&PID_9001

Where VID and PID is your hardware ids.You can find these values from device 
manager > properties > details then in property select Hardware Ids.

After this update your glass driver and select browse my computer then select 
let me pick  from a list of device drivers then select android composite 
interface. and you are done.

Original comment by tricongl...@gmail.com on 22 Jan 2014 at 9:18

[GoogleCodeExporter]

Original comment by ala...@google.com on 24 Jan 2014 at 9:14

• Changed state: Accepted
• Added labels: Component-Other-API, log-12722024

[GoogleCodeExporter]

In order for my XE-C to be seen as "Unknown Device" I had to add &REV_0000 to 
the end of the compositeAdbInterface value. Once it was an "Unknown Device" in 
Windows, I was then able find the device ID, which ended up being, as above, 
but with &MI_01 appended. Once I did that, Glass was visible via adb and MTP.

Otherwise, I was having the same issue as OP - either Android ADB Interface but 
no visibility via adb, or as an MTP device (mounted fine), but not both.

Original comment by ghchinoy on 24 Jan 2014 at 9:23

[GoogleCodeExporter]

I am also having the same problem and I did the Device driver trick. It did not 
work at all. I still can't get ADB to recognize my device in windows 8.1 This 
is ridiculous. I just sprung for the glasses to get development going and I get 
crap support.

Original comment by timothy...@gmail.com on 23 Mar 2014 at 12:30

[GoogleCodeExporter]

@timothy ADB connectivity to the computer's not an API issue. Please check 
Stackoverflow for some solutions, including getting Win8 to recognize the driver

ref
http://stackoverflow.com/questions/16928983/google-glass-adb-devices-doesnt-find
-omap4430-driver-not-installed-cant-find/17138336#17138336
http://tivadj-tech.blogspot.com/2012/09/certificate-check-error-when-installing.
html

Original comment by ghchinoy on 23 Mar 2014 at 5:53

[GoogleCodeExporter]

The Android's driver definitions have been updated to include Glass' device IDs.

Original comment by ala...@google.com on 21 Apr 2014 at 3:58

• Changed state: Fixed