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?
Related
First off my devices and software:
Smartphone: Samsung Galaxy S5 (Android 4.4.2)
Smartwatch: Motorola Moto 360 First generation (Android 6.0.1)
Development software: Android Studio 3.1.3
Operating system: Windows 7 Pro 64 Bit.
I was able to install my own app on my Smartphone.
The only thing I did was generating an APK file, copying it to the sd card of my phone
and installing it.
(The phone was connected via USB.)
I had to change the minimum sdk to 19 (target sdk = 27).
Now I tried to do the same with my 2nd app (which is just for the watch).
Unfortunately, I haven't had success yet.
When I copy the app to my phone, I can't start it -> Parsing error.
The problem is that I can't set the minimum sdk to lower than 23.
After reading a lot on the Internet I tried out a completely different way.
For both devices I enabled the dev mode and turned on USB debugging + Bluetooth USB debugging.
Additionally I went to Windows 7 system settings and added the path of Android.
Right now, I'm able to type in commands like "adb devices" in cmd.exe
Sadly, I can't connect to my watch.
In on YT tutorial they say, "adb forward tcp:6666 localabstract:/adb-hub".
Whenever I try this, I receive the error message: "error: unknown host service"
Also another hint didn't work:
adb forward -remove tcp:4444
adb forward tcp:4444localabstract:/adb-hub
adb connect 127.0.0.1:4444
As you can see, both ways don't lead to success.
Do you have any suggestion how I can install my app on my watch?
I don't prefer any specific way, the main point is that it works.
Thanks for any help!
P.S. If you need further details, please let me know.
Regards
Have you tried it with another phone? Have you installed the needed dependencies for target sdks below 23? It seems you need API21 for android wear.
See example here https://www.telerik.com/blogs/build-your-first-google-wear-app
Problem:
My smartphone model (Lenovo Vibe B) doesn't have a official driver listed in the OEM USB Driver List (it has for Vibe C and other, I've tried the one for C, because phones are kind of similar but didn't work), so I can't use it in Android Studio to test my apps.
What I've tried
So my ADB is not recognized or, when I installed an ADB that was found on Device Manager, I got the error Code 10. Updated the drivers, reinstalled all USB drivers, ADB drivers, tried different software like LeTools, LenovoSmartAssistant, MagicPlus, something in chinese, an universal ADB from a developer named Koushik.
Tried different youtube tutorials... also read articles and tried them:android won't connect, installing adb driver - lenovo, how to fix code error 10
Also checked official documentation from Google,switched from MTP to PTP** and back to MTP,tried even MIDI
Still my device isn't visible in Android Studio and in Device Manacer is marked with an exclamation sign, or now it's not visible at all.
I mention that I also accept a solution in which I can install my app created on Android studio on the phone and test it without Android Studio. I need to do that because I'll work on an app that requires to be tested few month's, in order to have a database to predict a future behaviour.
Thank you in advance for your help provided!
For Android Development using the real device you need a tool called Wondershare MobileGo. Its a pcsuit app for Android and ios.
I am using it for 2 years and its the only final solution for all ADB related issues.It contains all type of ADB drivers of android devices currently on market.
You only have to use it once to get the ADB driver installed according to your device model and you can remove it from your pc after that.
I am using the latest version of Android Studio(2.1.2) at the time of writing this post . The problem that I am experiencing is that the ADB instance used by Android Studio doesn't seem to be able to find my Galaxy Core Prime device (SM-G361F, stock Android version - 5.1.1). It can connect to an emulator just fine.
What I had tried (most of these multiple times):
enabling/disabling developer options
enabling/disabling USB debugging
revoking USB debugging authorization
changing MTP to PTP and vice versa (my device doesn't allow deselecting both options, one must be chosen)
reinstalling the drivers
powering on and off both the phone and the PC
installing Samsung's Smart Switch software
using different USB ports
trying out different Android Studio versions (x86 and x64 with the latest respective JDKs)
This is what it looks like in Android Studio:
I had installed the official Samsung's USB drivers from here.
This is what the Device Manager is showing (Windows 7 64-bit SP1):
Afterwards, I've also tried installing the Universal USB drivers from here.
This is what firing up its installation of ADB looks like:
It has obviously successfully found the device.
My device also politely prompted me to allow the PC to connect to it using a generated RSA key which never happened with Android Studio.
The only thing I've not tried is installing Samsung's Kies software.
I really don't know what is the problem here.
Maybe I should just give up and instead use the emulator but it is a damn shame not to be able to debug on an actual physical device, if you ask me.
Thank you in advance.
Android in general does not support all phones for a debug connection. I have a samsung s6 and for me that works. I don't know about the Core Prime though. However, in most cases(in my experience):
The phone does not support the connection
You did not install all the required files in terms of the android SDK you might have not gotten the latest update that supports more phones
The OS is not supported - Mainly caused because Samsung and a lot of other brands insist on having their own updates. And some times they - on purpose or by accident - forget to support USB debugging for developers.
My tablet did not support the USB debugging connection untill it reached android 6.
The cable is a charge-only cable (yes, those exist for some reason). Try with a different cable
You don't have the necessary drivers. Make sure they're installed
It might be circumstantial that your phone model does not support the connection for some reason, but it is really hard to tell. The only way to get proper help is to contact Samsung customer support, but in my experience it is just a waste of time. They don't know their own products. If you try with another device it might work.
After some continued tinkering I managed to get Android Studio to recognize my device. All I did was adding the path to the ClockworkMod's ADB .exe to the PATH environment variable. That seems to have done the trick as Android Studio now allows me to run the application on my device even though it is still running its own instance of ADB (located in the platform-tools folder).
It might be completely unrelated but I'm not considering undoing the modification made to the environment variable.
Here is the proof:
I have installed the and adb driver on my android device which is yu-yuphoria
now in device manager my device is listed as android adb interface . But when i run any app on android studio that device is not listed . I have changed the usb mode from media to camera again installed the adb interface and restarted both system and device still the device is not listed in android studio.
i have spend hours in fixing the problem but cannot do.
few days earlier there was no such problem but now it came from no where
any possible solution
I had all those weird problems with Windows showing perfect configuration but devices not visible. With three different phones, I always fixed it with this free tool (from XDA I believe):
http://adbdriver.com/
Ofcourse this will not help if it is actually a problem with Android Studio.
This is not a duplicate post. I have searched and read extensively and none of the solutions I've come across have been successful.
Win 7 64 bit
LG Spectrum II running build VS93022A (Android 4.1.2)
Eclipse version...from the SDK as downloaded on 09/07/13...so, the latest
I did install the actual vendor drivers for my device, not just using the default from Windows that kick in when you first connect it. I can view the device and SD card contents via windows explorer. It is by any criteria clearly and correctly connected to my computer.
Allow USB debugging is checked on the device. The USB connection mode is "Media sync (MTP)".
Used "adb devices" from command line and it lists no devices.
Restarted everything multiple times.
The selected minimum Android version for the project is Gingerbread. My device, as stated above, is running the absolute most recent Android build available (updated itself two nights ago, actually).
The device still does not show up. Any ideas?
edit: The advice found here:
http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver
cannot be follow because it is incorrect. In Device Manager, there is no entry under Portable Devices (where my phone appears) which reads "Android Composite ADB Interface."
On a side note, is all of the Android developer documentation this terrible?
I had the same problem with my device. To solve it I plugged it in with usb debugging unchecked then checked it. A notification came up on the phone saying "allow this computers RSA?" or something similar and then it worked.
Something I just came across after I had installed iTunes on my PC (previously I was able to debug over USB, then it stopped working). Go to Services and stop "Apple Mobile Device Service" as it interferes with the USB for Android debugging.