Unable to connect Glass to run gdk samples - android

I have Glass with version 4.0.4, XE 12.1
I just installed the latest ADT with Android 4.4.2 (API 19) and Glass Development Kit Preview.
My problem is when I try to run samples, DDMS shows the Glass device as being online but when I try to run the application, it gives the following error on the console:
Automatic Target Mode: Unable to detect device compatibility. Please select a target device.
When the Android Device Chooser window opens, there is no entry for Glass in the list.
Glass has debug mode turned on and is visible in DDMS but just not compatible for some reason.
This also brings me to a related question. I just received my device in the mail yesterday and left it charging overnight but still has not updated to XE 16. Glass is connected to wifi and the internet is fine on it. What do I need to do to force it to update itself?
Thanks for your help.

You might try the following:
First, make sure that your Google Glass is updated to XE16 (connect to your home/business wifi; plugin charging cable). Do not attempt to go further until your Google Glass has updated
Once that is done, you might look at some of the other answers to "how do I connect". Some of the steps for this are shown below.
What OS are you using (Windows?). Let me know and I will update the answer with what I had to do to see Google Glass (or look here )

I guess you set the wrong project target.
If you are using Eclipse, open project.properties and make sure the target looks like this:
# Project target.
target=Google Inc.:Glass Development Kit Sneak Peek:15
Not
# Project target.
target=android-15
You can try:
Open project properties (Alt+Enter) -> Android -> Project Build Target -> Glass Development Kit Sneak Peek
BTW, IMO, Glass update is pretty random. I have no idea how Google decides who gets the update. You can flash the system image if you don't want to wait. Please see https://developers.google.com/glass/tools-downloads/system. (Warning: Rooting, unlocking, or flashing your Glass voids your warranty.)

The fact that Glass is displayed under DDMS shows, it is being detected by ADB. The reason you are not able to run the app on Glass is that, your current version of GDK is not compatible with Glass XE 12.1. If you run projects with Android 4.0, you can see your device listed.
In order to resolve this issue, upgrade Glass XE to the latest and try running the app. Then your device will be listed under currently running devices.
Glass XE will be automatically upgraded. Make sure your device is connected to WIFI, connect device to the charger and restart.

Related

Why Android studio won't run app on Android Pie (9.0)?

I've upgraded my Google Pixel to Android 9.0/Pie.
When I try to run an application from Android studio I don't see the Google Pixel in the list, there's only a null device named FA69R0306649. When I run my application, Android studio tries to install the app but then fails.
It looks like Android Studio is not recognizing the phone anymore. It Worked perfectly fine a couple of hours ago under Oreo (8.x).
Also, if I deploy the app on google play as alpha and then download it runs perfectly under 9.0/Pie.
Any suggestions to get the run/debug working with android 9.0 phone under Android Studio (3.1.4)?
The Pixel running 9.0 requires USB 2.0 high speed.
Apparently the Pixel running Android Pie cannot talk to the PC using neither USB 3.0 nor USB 1.1 full speed nor USB 2.0 running at full speed.
I had a similar problem with my Xiaomi Mi A1. When I upgraded from Android 8.1 to 9 Android Studio would hang on "Installing application" forever.
After trying revoking USB debugging authorization and completely reenabling developer options with no success it turned out a simple restart did it.
Looks like there are multiple issues that lead to the same problem.
I had the same issue with a Xiaomi Mi A2 after upgrading to Android 9. If you are using Linux, try adding the udev permissions manually, following the steps described here. In my case, that was the only solution that worked.
Please re-enable developer options again after the OS version upgrade, the device name will appear and it will be working fine again
Install Sdk Platforms of Android 9. In Android studio Top Right besides Search Icon.Press That Icon of SDK manager and look either sdk platform is updated and installed.
A simple solution just go to your Developer option on your phone , right below the USB Debugging option it says to "install via USB" just enable it and you are all set to install an app through android studio into your 9.0 device.

Xamarin Fail to initialize device

Im a freshman of Xamarin. Pls help.
I just followed the guideline of Xamarin
https://developer.xamarin.com/guides/android/getting_started/hello,android/hello,android_quickstart/
until the step of 31
Finally, we can test our application by deploying it to an Android emulator. If you have not yet configured your emulator, please see Xamarin Android Player for setup instructions. In this example, we have installed the Nexus 4 (KitKat) (Android 4.4.2, API Level 19) virtual device and we have started it from the Xamarin Android Player Device Manager console:
I run the Xamarin Android player to test this quick start, it has a problem,
I got a message: Fail to initialize device
I google it with 0 answer
suck this account need a 10 reputation to upload a picture , how I can get the reputation?
Try to check your installed devices.
When I installed Xamarin Android Player no devices were downloaded automatically. You need download and install all you needed devices manually.
For now it's better to use Genymotion but in the future Xamarin Android Player will be a good alternative too,
if you want Xamarin Android Player for now, install the latest version and download manually a device, Make it start and try again.
The solution can be in enabling virtual technology in the bios.
I had same issue.
My solution was to enable
I had to go to My 'Network Connections' in my control panel, found the Connection named 'Virtual Box Host-Only Network', right clicked it and went to the properties and CHECKED the option 'VirtualBox NDIS6 Bridge Networking Driver' and reconnected. This fixed it for me.

Google Glass unknown for Eclipse(Android Device Chooser)

I know there are a few threads regarding the the connectivity between Google Glasses and Eclipse on Windows 7> but I think mine it's a bit different unfortunately.
I followed this threads:
Eclipse & adb Not Recognizing Glass as Running Android Device
Unable to connect to Google Glass on Windows 7 (using ADT)
but unfortunately non helped me 100%.
The PROBLEM:
Even though I followed the steps from the threads, when I go to eclipse and try to run the sample Compass application it shows in the Android Device Chooser(Run configurations) in the target section as unknown.
I must mention that:
enabled debugging on the glasses (several times)
In the Device Manager(Windows 7) it appears as Android Composite ADV Interface, under SAMSUNG Android Phone(?? on the threads they say that should be Android Devices; anyways it appears as ADV Interface)
Reboot system
SDK: GoogleUSB Driver(version 10)
What am I missing here? Thanks a lot for every tip! ;)
Have you tried ./adb devices ? what do you see when you do that?
Did you confirm that your computer is a trusted device on Glass?

Google Glass Application development startup on Eclipse

I am an Android Developer and I want to start working on Google Glass application. I have installed Eclipse in my computer but I learnt that it will not work for Google Glass development. Some blogs suggested I should use Eclipse Indigo.
I have checked and installed Eclipse Indigo and ADT and other plugins.
I am trying to run my glass on debug mode but system is not detecting it.
Can anybody please help me with how to set proper environment for Google Glass and how to make it detect?
Two things that you have to do first:
Install the Glass Development Kit preview via the SDK Manager (Should be under the 4.4.2 platform).
Ensure that you have Debug mode enabled on your Glass. After enabling Debug mode when you plug Glass in for the first time you should be asked if you'd like to trust the computer on the Glass. I select Always Allow so I don't get asked multiple times.
By the way, I am using Eclipse Kepler (but mostly IntelliJ), so I doubt that the version is critical.
Good luck!

qt for android doesn't find my physical device

I'm trying to write android applications with Qt5.1. I installed everything according to these instructions and I wrote my application and built it successfully. My problem is that when I click run on android version, instead of running the application on the device that I have connected or even asking whether I want to use the virtual device or physical device ( like eclipse does ) it just opens ADV.
I know I have connected my device properly because I can run applications I write with eclipse on my device. But not with Qt.
Can anybody help me?
Just in case you need to know I'm using the latest version of ndk and for sdk I'm using the one that comes with adt's latest version. If any other information I should provide please let me know.
thank you
I have had this problem as well, your device is not corresponding with the QT run settings. When you press run (probably in QT Creator?) it will search for devices which allow the application to run on.
There are a few possibilities when it comes to this:
Your device is not set up correctly:
run "adb start-server" and then "adb devices" in your command prompt. Does it say it found 1 device with status: "device"? If not your device probably doesn't have USB debugging enabled (you can enable this in the dev settings on your device).
You are building in the wrong mode:
Make sure you are creating a program for ARM (ARM GCC 4.7 QT 5.1 for example).
Deploying for the wrong API level:
Are you running the program on a device that supports API level 17 ? If not you can change these settings (API Level) in your QT project settings.
You don't have the recent API level installed:
Start the android sdk manager and download + install the new API's.
It worked for me after performing these steps, should you have any other difficulties feel free to ask!
Edit
If these steps did not work check if your android sdk is located in a location with write permission.

Categories

Resources