ADB debugging needs connection between Android Studio and Wear 3.0 smartwatch (Samsung Galaxy SW 4). How make them work together?
Switch ON Developer Mode on your Smartwatch, including A) Activation Developer Mode in Settings (in most cases push many times on Settings-> About watch -> Software -> Software Version) B) Set ON ADB Debugging C) Set ON Wi-Fi Debugging
Connect work station with Android Studio and smartwatch wear 3.0 to the same wi-fi network
Connect smartwatch via usb charger with workstation (obligatory in most cases at least once)
Send the command in Terminal - adb connect XXX.YYY.Z.A:5555, where XXX.YYY.Z.A - address of your Wi-fi - find it in settings of wifi in smartwatch or workstation
Accept the request on the smartwatch (always allow / always trust);
Check in Studio the change from No Device to your smartwatch.
Notes:
sometimes it's obligatory to turn on \ off ADB Debugging and Wi-Fi Debugging on smartwatch and try again;
sometimes the connection between smartwatch and Studio is working without USB connection at all (but mostly one time and you need to repeat "adb connect XXX.YYY.Z.A:5555";
sometimes you need smartphone in the same Wi Fi network with workstation and smartwatch, sometimes it works well without smartphone.
Related
I have a usb device for transmitting data. the device works perfect in windows OS. I am to use the device in Android 13 the Device acts as Human Interface Device.
I am using Android Emulator for programming. It seems the emulator work only for UI and not for external hardware.
And I achived that in android app, It can able to read that pendrive. When I run that app in Emulator it is not detecting.
Can you suggest how can I make Android emulator detect the usb device.
Thank you for your kind interest.
Regards
I want to connect USB device on Emulator.. and need to view that contents.
I used to run applications in my Redmi 3s Prime device. Usually it worked, but now it's showing as no USB devices detected.
Developer options and USB debugging is ON, but it is still not detecting. What should I do?
Please check the Android Studio "event log" information.
If the information is like "ADB server didn't ACK * failed to start daemon *", it means that other software holds the port. Referring to this can solve it.
If you cannot find log information, probably it failed to install the driver.
You may disconnect the phone from your computer, restart the mobile phone and try again.
I have a Redmi 3S and that happened to me too. I solved it by installing the correct drivers from here and MI PC Suite and connected the device.
Also in developer options, turn on "Install via USB", "USB debugging" and turn off "Verify apps over USB". If nothing works, try another USB cable or other port.
Restart PC, Restart phone, if no luck,
Try installing usb driver from this link
http://gsmusbdriver.com/xiaomi-redmi-3s
and try again
Download suitable USB Driver, ADB driver and fastboot driver for Xiaomi Redmi 3s Prime from below link and install them on your computer.
https://www.androidusbdrivers.com/xiaomi-redmi-3s-prime-usb-drivers/
After installing restart your computer.
I am trying to debug a memory leak on a Android based VOIP desk phone with Android Studio 2.1 (For what it's worth it's a Grandstream GXV3275 phone, which has a 7in Android tablet embedded in it).
As best I can tell this device has no direct USB connection. I've enabled "Developer Mode" on the phone and am able to connect to it using "adb connect" from the command line. I can use Android Studio to then download and run/debug applications over the network.
But Android Device Monitor will not connect to the device and the phone does not show up in Device Monitor's list of devices. In the Device Monitor's console i see:
[2016-08-30 15:17:32 - DeviceMonitor] Adb connection Error:EOF
[2016-08-30 15:17:32 - DeviceMonitor] Connection attempts: 1
[2016-08-30 15:17:33 - DeviceMonitor] Connection attempts: 2
[2016-08-30 15:17:34 - DeviceMonitor] Connection attempts: 3
Any ideas how to make Device Monitor recognize devices over the network?
Well, the alternative is to use the Android Monitor tab built into Android Studio. This does indeed seem to work without a direct usb tether. Android Monitor supports initiating GC and performing heap dumps (HPROF). The downside that I have seen, is that performing an HPROF dump temporarily disconnects my ethernet connected Android desktop phone from the network.
In Samsung Galaxy S6 Edge with Android 6.0, when the device is rebooted, phone complains that the connected computer doesn't recognize the phone and the device is not any more reachable over ADB from the connected Linux PC. The phone in fact instructs user to install proper drivers for Windows or Mac OS, but as the phone is connected to Linux host, there is no help here.
This means, that in order to continue debugging over ADB, one must manually toggle the USB mode from phone from MTP to PTP, after which phone is connected through ADB again. This makes test automation impossible, as the test scheduler needs to reboot the target device between test rounds.
With previous Android versions, rebooting the device remotely and getting ADB connection back was possible, but with Android 6.0, this became a problem. This particular device had earlier Android 5.1 and there were no problems with remote reboots.
As manually toggling of USB mode solves the problem, it might help, if this mode could be automatically toggled after reboot. So far, only solutions I have seen require device rooting and that is out of question.
Does someone have any idea, how Android 6.0 device could be automatically recognized by ADB after reboot?
The solution was after all simple: the Linux user, who starts up the adb server, needed to be added to the "plugdev" group. This group was defined in file /etc/udev/rules.d/51-android.rules with line:
SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", MODE="0666", GROUP="plugdev"
With previous Android versions, this didn't seem to be important as we didn't have any users in that group and everything worked fine.
When I try to connect my plantronics wireless headset via Bluetooth to my windows 8.1, I find that the device is not visible to pair.
Hence I am not able to connect to it.
I have made the settings to enable my laptop detect the bluetooth devices. Still its not able to search.
Try to install [Broadcom Bluetooth 4.0 Driver for Windows 8.1 ] LINK=>> 1 !
At least works fine on my HP-EliteBook-8570p with stereo "BlueDio 99B" headset. After switching the headset ON the Windows connect the device automatically, and switch Audio-Stream into new-attached device. Optimal!
PS - Unfortunately it is still the Problem with Windows 8.1 + Skype( MIC-Problem) :( Windows 8 is the first OS, than not support Skype at all! ;)