I am not able to get my Google Glass on available devices list in Window > Open Perspective > DDMS in eclipse.
What I did - (1) Downloaded 4.0.3 SDK and GDK Sneak Peek (2) Turned on USB debugging on glass (3) Connected glass via USB (4) Opened eclipse and navigated thru' Window > Open Perspective > DDMS. Devices tab is empty and nothing is shown.
OS is Windows 7.
I think my question is duplicate of something that was asked already! Just found this on stackoverflow - how to upload to your code to Google Glass?
It solved my problem!
I had the same problem with my Galaxy S III, I am guessing you did not install the drivers for your device, this website seems to have some troubleshooting advice.
http://glassdev.blogspot.com/
Related
My GEE2 is currently running on version OPM1.190831.007, and I can't find a way to get a more recent version running. I've tried the flashing tool and manual flashing, but both methods came with their own issues. I'll give them below:
Flashing tool: I get either a 'device already in use' connection error or the device is offline. This besides the more common message that the flashing tool has some problems on windows sometimes, and that I should try refreshing the webpage.
Manual flashing: once I have given the adb reboot-bootloader command, the fastboot devices command won't recognize the device (listed as ???????? instead of the device name/number) or it will be offline. As a result, the commands that should be given afterwards according to the Readme file don't work.
I have the adb debugger from the Android Studio SDK platform-tools folder, so I updated the driver software of the GEE2 with the use of that folder initially. Afterwards I tried installing other adb software as well but that didn't help either.
I have also tried a couple of the simpler solutions, as unplugging and plugging, refreshing the site, using another computer, using another internet browser, deinstallation of the driver software, a factory reset of the GEE2, installing less recent firmware instead of the latest. None of these things changed the outcome.
Any suggestions would be highly appreciated!
Firstly, check if you have enabled developer options on EE2.
I had a hard time flashing it on Windows due to driver issues. My Android studio or ADB had no problem deploying apps to EE2, but the fastboot never worked. I ended up flashing it on a Mac using brew installed adb.
I had similar issues with Windows, the driver, and fastboot not working using the flash tool. I was told by support to use a USB 2.0 port. I used a Mac with USB 2.0 to flash it and it was successful.
There's a flaw with the instructions on google glass firmware update - for Windows only, there's a USB driver you need that is glass-specific which isn't mentioned anywhere on the page. I can't even find the page where I found that out right now and I know what I'm looking for. Which isn't very helpful.
The best I can give you is a link to this installer tool might sort out your problem judging this reddit post.
If that doesn't work, use a mac or linux.
Installed VMWare Remote Console 10.0.4 (latest as of writing this) on MacOS Mojave 10.14.3. installation went well, but running the app, nothing is shown on the Mac. seen some unanswered similar questions on VMWare forum here and added my question here. Have anyone seen the same issue and have a solution?
I may have sound something - when i go to a vSphere VM, i have two options: 'Launch Web Console' or 'Launch Remote Console' - if i click the latter, i get the application to open with the UI displaying as it should. so, unlike VMWare Horizon, Player and others, here it seems you need to connect to the VM first via browser, to open the desktop client. weird choice from VMware in my mind, but still some solution. See image below
I am trying to connect my google glass to my system but every time I connect it is being recognized as Android ADB Interface under Android Devices in the Device Manager (Screenshot attached).
Due to this i am not able to run my applications as it doesn't show up in the Device Picker of Android studio.
I tried connecting it to my friends system and it worked fine on that. But the only difference i noticed was that the device was being shown as Android Composite Device Interface under the Android Devices in the Device Manager.
I have already tried a fix to alter my android_winusb.inf and insert some custom lines but that also dint worked.
Can anyone else help me with some other solution?
Perhaps you aren't getting enough power on that USB hub.
I've created a small Glass app and am trying to help someone else side load the .apk file directly on on their Glass as part of internal testing. I had them install the Eclipse + ADT Bundle, run the SDK Manager, etc (i.e. the basic instructions from here). They verified that the Google USB driver does show up in the SDK Manager.
With the device plugged in, running "adb wait-for-device" hangs. So it doesn't appear device communication is working. The device also does not show up in DDMS in Eclipse.
They verified that USB debugging is enabled on the Glass itself under settings.
I also tried having them follow the instructions here but this also did not help. They are able to see the Glass removable storage device in windows.
Any suggestions on what else to try? I do recall that with my Glass device at one point I put it on and it asked me if I wanted to allow debugging from the computer where it was plugged in. I'm not sure if this could be a roadblock here or not but I'm also not sure how to get to that prompt.
Once you get the correct values into android_winusb.inf it works fine, see
Google Glass ADB devices doesn't find. OMAP4430 driver not installed (can't find it!)
Here's an example on a Win7 box:
(edited to include screen capture)
The easiest workaround is to find a Mac, Chromebook or Linux computer. Windows with ADB and Glass is nothing but pain.
I tried the instructions from
https://developers.google.com/glass/tools-downloads/system
$ adb reboot bootloader
$ fastboot oem unlock
$ fastboot flash boot boot.img
$ fastboot reboot
$ adb root
After step one, the glass either cannot boot up, or boot up normally, but not in fastboot mode. Basically, nothing shownup if I type "fastboot devices".
I am using a Win 7 machine, with usb cable connects to Google Glass.
(XE12 firmware).
By the way,
$adb devices works fine. I can see my glass got listed.
Dose anyone know the problem?
Thanks in advance.
I found the problem myself and would like to share with the community.
For Win 7,
the USB drivers from google don't have the Google Glass drivers listed. After installing the SDK, I couldn't find Google Glass as a valid device although Win 7 does
recognize Google Glass as an external storage. Basically, the adb.exe stuff won't
work.
I googled around, and some folk posted this issue, and posted the solution. I summarized here:
Go to "sdk/extras/google/usb_driver", open adnroid_winusb.inf (using notepad)
You will find Google Nexus 7, Nexus Q, ... but no google glass. Add the following:
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&REV_0216&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_00
You can find the VID_18D1... by opening the "Control Panel", "Hardware Sound",
"Device Manager", click on the unknown device, then click on the "Details" tab, then
click the Property description drop list, find the hardware id: You will get this
information.
You have to put the above lines in two places, one for Intel, one for AMD. After this,
the adb.exe will work. (Use "adb devices" command to check).
But fastboot still won't work. Then I found out there's one line missing.
SingleBootLoaderInterface is not set for google glass as fastboot has a different USB\VID.
To summarize, you should put the following in:
;Google Glass
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&REV_0216&MI_00
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_00
%SingleBootLoaderInterface% = USB_Install, USB\VID_0451&PID_D022&REV_0100
I am very disappointed to Google glass's support, and released SDK QA.
Happy Explore!
XD