I am trying to get Eclipse and DDMS to see my Google Glass device. I have followed the instructions found here:
https://developers.google.com/glass/develop/gdk/quick-start
However the DDMS device list is still empty no matter what I do. I have tried multiple USB ports and different cables. The Device Manager can see the Glass device but the DDMS doesn't. The DDMS can see emulators however.
After doing a little digging it seems that you need to make sure that a driver is installed for actual devices vs emulators. However I can't find any instructions on how to do that with Google Glass. I tried installed the generic Google USB driver however that wouldn't install for the Glass device. I am running all of this on Windows 8.1, though I can't seem to find anything where that would make a difference. I am wondering if anyone else has had this problem or can offer any advise.
First - Disable driver signature enforcement for Windows 8. Google for a buffet of how-to tutorials/instructions, if you don't already know.
Second - Update android_winusb.inf file #
Example: C:\Development\adt-bundle-windows-x86_64-20131030\sdk\extras\google\usb_driver
[Google.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
[Google.NTx86]
;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
Once inf file is edited, go into your Windows Device Manager, right click on the Glass Device, select Update Driver Software. When prompted, choose "Select From Computer" and enter your android_winusb.inf parent folder location.
NOTE: During Driver Update you may receive an unsigned driver warning; you must proceed with the unsigned driver to succeed.
Open eclipse. If you don't see the Glass device in DDMS perspective right off, run your application/sample as an Android Application and the device should be available as an selectable option during an Android Device Chooser dialog (Provided Glass is running with debug on and plugged into the machine).
matthew06854's solution works well! Thanks. Just one thing, after connecting glass to the computer, one needs to confirm on the glass to allow this connection (trusted computer, or something like it).
It is necessary to check that VID and PID matches what you see in Control Panel/System/Device Manager/Portable Devices/Glass 1/Properties/Details/Hardware Ids. I only got USB\VID_18D1&PID_9001&REV_0216 and USB\VID_18D1&PID_9001, so I changed the file \adt-bundle-windows-x86_64-20131030\sdk\extras\google\usb_driver to reflect this:
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&REV_0216
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_9001&MI_01
Since I had already installed first version og the driver I had to remove driver before I could install with new settings. Now it works for me also :)
Easy way
Download these custmized drivers from
http://www.androidfilehost.com/?fid=22979706399752791
Then go to device manager look for glass-right click-update divers-custom brows location and provide the path of above folder
This link really helped me
http://appliedanalog.com/agw/?p=17
There's a missing step here ,that I figured out.
In my case, my andriod_winusb.inf already had some values under the ;Google Glass line.
That made the Google Glass device appear in the device manager, but as an "Android ADB Interface" instead of an "Android Composite ADB Interface".
Any changes to the andriod_winusb.inf didn't make any difference.
What worked for me was to click on the Andid ADB Interface in the Device Manager. Click uninstall, and (very important) check the check box that says : "Delete the driver software for this device".
Then I modified the andriod_winusb.inf file, and clicked on Glass 1 in the Device manager, and updated the driver.
I'm guessing that once Windows knows about a driver, it caches it somewhere, so uninstalling it and reinstalling ,without "deleting the driver software" just brings the cached driver back, and completely disregards the changes in the original driver folder.
Related
Does anyone know how to capture screenshot on Nokia 8110 4G (KaiOS)?
You may follow these steps to get screenshot via Firefox WebIDE.
On the device - dial *#*#33284#*#* to enable developer mode. There will be a bug icon on the status bar.
Download Firefox 58.
[Important] Disable your internet access, this is to prevent Firefox got updated to a newer version which might break the WebIDE functionality.
Launch Firefox 58 and disable auto update.
Resume your internet access.
Launch WebIDE in Tools > Web Developer > WebIDE.
Restart the WebIDE (because the ADB helper would be downloaded automatically, and need to restart it to take effect.)
Now you should be able to see Nokia 8110 detected under "USB devices" at the right panel. (if not, see below)
Click the device, "Nokia 8110", and then click Screenshot.
See here for a sample screenshot.
Troubleshooting if you failed to see Nokia 8110 detected:
I found it might fail if your Firefox got updated to a newer version automatically, in this case you might need to leverage creating new profile to start over again, see here for details.
If the Firefox version stays correctly at 58 but after you click the device, it shows an error saying "Failed to connect", try to reboot the phone and also restart the WebIDE as this post suggested.
EDIT: Yes it is - Joelbert W's answer worked and makes the other responses a bit silly by comparison, just * and # together :-)
Unfortunately, it is currently not possible :-(
https://twitter.com/KaiHelps/status/1072446931421593603
https://twitter.com/KaiHelps/with_replies
It is possible either with WebIDE connection or with a custom ROM such as GerdaOS where you can make screenshots by pressing Power with half-open slide lid.
However, I'd only recommend installing custom ROMs for experienced users only since you can't use any official updates after installing them.
So I have a go flip 3, and i stumbled on if u press * and # almost simultaneously, it takes a screenshot.
I believe it's possible on certain devices and OS versions using the Screen Capture API as well.
On a Macbook Pro with Yosemite -
After getting through the difficulties of getting Android SDK installed, I plug in the device, but it doesn't show. The command adb devices yields "List of devices attached" with nothing following. It's there on the USB, the About This Mac System Report shows it present on the USB.
This question looks similar to Issue setting up the development environment for ProjectTango developemnt Device but is not the same because I'm not using Eclipse.
Please ensure that USB debugging is enabled in order to enter ADB, go to Settings > About tablet > Build number and then press Build number seven times. Then press back and go to Developer options > USB debugging.
Make sure you're using the latest Google USB driver. I was having this problem (but on Win 8) and updating the driver fixed it, I'm now getting the device in adb devices and can push content to it.
I'm trying to sideload Lollipop onto my Nexus 5 from the OTA zip file.
At this point, the adb recognizes the device after I plug in the USB cable, and spits out the serial number.
As I understand the instructions for sideloading, once I get to this point, I just need to reboot into recovery mode, (which works as expected) and then bypass the red exclamation point icon using "volume up and power" simultaneously. That works too.
At the point where the screen on the Nexus 5 says, "Now send the package you want to apply to the device with 'adb sideload <filename>' I type "adb sideload + the OTA image file name", which I renamed for convenience". The file is in the platform-tools folder.
At which point the command window reports: error: device not found
So... the device is seen by the adb, but somehow is no longer found after the device reboots in recovery mode.
I've replaced all the usb drivers, enabled usb debugging and developer mode on the Nexus device. I've tried this in windows 7 and also in Linux (both from the android sdk tool kit and from an installation of Eclipse). I'm unable to get the adb to talk to the Nexus 5.
I read the android-windows usb inf file, and there is no section specifically for the Nexus 5, but I added a line under the "generic android" section with USB\VID_18D1&PID_D001 as has been suggested elsewhere for people who couldn't get the OS to see their nexus at all. My issue is not that the OS can't see it... and the adb sees it, too, until I try to sideload the OTA file in Recovery Mode.
Anyone else having this issue, or better yet... any ideas on how to solve it?
Thanks
It turns out that I had not enabled USB debugging before I tried to do this using Linux Ubuntu / Eclipse / Android SDK. So my problem was really a windows USB driver problem, I guess (though I can't be sure, since windows did see the device until I tried to transfer the file. Maybe that message was really conveying a permissions problem, too...)
I rebooted into Ubuntu and tried again and was able to transfer the update file. The only hitch I encountered at that point was to issue the sideload command as root. I didn't do that the first time I tried it, and got a message about lacking permissions.
I suspect the posted reply with a link to a universal USB inf file would have worked, but, though I'm grateful for the tip, I can't testify to that, since I managed to transfer the file without Windows.
Thanks to all who looked at this and especially to Alex P., for posting a possible solution. FW
IW, I'm glad to have finally been able to do this, but for anyone struggling to get Lollipop ahead of the OTA update... well, it's nice, but hardly worth a lot of effort.
I am trying to debug my android application in sony xperia J but the
adb devices
returns no devices
I have enabled USB debugging, Mass storage and installed sony pc companion.
I also allowed to install external applications.
I tried with enabling USB teathering.
Is there any additional setting I am missing?
I guess I have installed drivers for it but I am not very sure.
Can somebody help me on this it is really irritating.
You have to be sure about drivers installed or not.
in my job I see many devices that are not recognised by adb at first.
I have noticed that this is happening due to an auto-mount of the sdcard on the computer.
make sure there are no mounted drives on your computer and that should fix this
You can use PC companion software connect Phone to PC for debugging
Link: http://www.sonymobile.com/in/tools/pc-companion/
and also try it
Settings > Xperia > USB Connectivity > USB Connection Mode and select MASS Storage, not MTP
If your USC pc connection is to Media device try changing it to Camera (PTP) or Vice Versa.
First you have to configure your phone not to install PC companion when connecting to PC by deselecting it from the phone menu. Also enable USB debugging and Mass storage, then connect the phone to the PC. Delete all devices that look like your phone in the Device Manager by uninstallling them. Then right-click and scan for hardware changes. Go to Android, right-click and Update driver. Browse folder until sdk/extras/google/usbdriver. Then Let me pick... Select Android phone, then have disk browse until sdk/extras/usbdriver. Select android_winusb.inf. Open, then select Android Composite ADB Interface. Next install. Wait until it is done and reopen Eclipse. You will find your phone there under devices.
I am running W8.1 x64 Pro and all above solutions had failed because Windows would not recognize a driver inside of sdk/extras/google/usbdriver even with a manual install.
Anyhow, my solution was to use Sony's PC companion tool, which was able to automatically download the drivers for my PC.
Official doc: http://dl-developer.sonymobile.com/documentation/other/Get_drivers_through_PC_Companion.txt
Now the abd interface is installed, and the phone is detected in adb devices.
When the side button of the TI SensorTag is pressed, pairing with a device is possible for approx. 2-3 minutes. How do you modify the SensorTag's firmware so that it advertises forever and pressing the side button is not necessary every time?
And how do you upload the firmware with an iOS device, so without using CC-debugger?
How I did it, with help of Chris Innanen (thanks!!)
You will need a Windows virtual machine if you do it on a Mac.
Download IAR Embedded Workbench for 8051 (http://supp.iar.com/Download/SW/?item=EW8051-EVAL). Make sure to take the 30-day evaluation copy and not the 4k limited.
Download BLE-STACK from Texas Instruments (http://www.ti.com/tool/ble-stack) and install it on a Windows (virtual) machine. By default, the installer will install here: "C:\Texas Instruments\BLE-CC254x-1.4.0\Projects\ble\SensorTag\CC2541DB\SensorTag.eww".
Open this SensorTag.eww file with IAR Embedded Workbench.
Select "CK2541DK-Sensor-OAD-ImgA" in the dropdown menu in the "workspace" section on the left
To prevent a compiling error later on: go to Project -> Options... and change the value for "Number of virtual registers" from 16 to 8.
Find "SensorTag.c" in the filetree in the workspace section on the left: "SensorTag - CK2541DK-Sensor-OAD-ImgA/APP/SensorTag.c"
Search for GAP_ADTYPE_FLAGS_LIMITED and change it to GAP_ADTYPE_FLAGS_GENERAL to enable indefinit advertising
Make the build with Project -> Make. Wait until it's done
By default, the new firmware image (.bin file) is now in "C:\Texas Instruments\BLE-CC254x-1.4.0\Projects\ble\SensorTag\CC2541DB\CC2541DK-Sensor-OAD-ImgA\Exe" (Make sure to place it somewhere you can reach it from Mac OS X later, if you use a virtual machine)
Repeat steps 4 to 10, but now for "CC2541DK-Sensor-OAD-ImgB"
Now get the app to upload the new firmware over the air. Get it here: https://itunes.apple.com/us/app/ti-sensortag/id552918064?mt=8
Open iTunes in Mac OS X and open your iOS device, go to the 'Apps' section, scroll to the bottom to see the apps with filesharing possibilities. "SensorTag" should be in that list. Click on it and add the two new firmware files, both Image A and B.
If that's done, open the SensorTag app on your iOS device and connect it to the SensorTag. Then in the bottom of the app tap "Update FW" -> "Select FW file" -> Shared Files > And then tap Image B and upload it. It takes a few minutes. A firmware with type A is already on your SensorTag by default. Because you've put a B Image on it just now, with any new changes you would need to upload an Image A.
Good luck!
Additional: changing the signal strength
1) Find "HCI_EXT_ClkDivOnHaltCmd" and you'll add a new line (and optional comment) after it:
// ADDITION Adjust TX power level
HCI_EXT_SetTxPowerCmd( HCI_EXT_TX_POWER_0_DBM );
1b) You can change "_0_DBM" to "_4_DBM" or "_MINUS_6_DBM" or "_MINUS_23_DBM" as well
2) Find "GAP_ADTYPE_POWER_LEVEL" and change the value on the next line to match the above power level
The above solution didn't work for me until I changed:
initial_advertising_enable = TRUE;
In SensorTag_Init().
I am using this firmware and it will start broadcasting whenever it's not connected. The side button acts as an on and off switch.
http://www.myweathercenter.net/installing-a-new-firmware-for-ti-sensortag/