I updated my gear sport several days ago. After updating to 4.0.0.2, I cannot connect to my watch anymore. Here is my command:
./sdb connect [IP]
It aways said:
error: failed to connect to remote target [IP]
How can I solve this issue?
On the device, go to Settings -> About watch -> Software, from there, tap repeatedly on Software version until Developer Mode is enabled. Then restart your device, and try to connect.
I can confirm the successful steps, it has to be ALL of those steps, and then restart the watch.
Bluetooth: Off, Wifi: On, Debugging: On, Developer Mode: On. Then restart watch.
It will connect after ALL of those settings are in those EXACT states.
No other combination worked, not even after a watch restart, additionally my pc is connect to the router via cat5 cable, but the watch is connected over wifi.
Windows 10, Tizen Studio 3.6 (2019-11-22), Galaxy Watch Active 2 (Tizen 4.0.0.7, One UI 1.5)
Here is the solution:
turn off BT
Restart Watch (OFF and ON)
Connect via Wifi with device manager.
I was having the same issue. I finally got my galaxy watch connected. Here are the config/status my watch had:
Developer mode:on,
Bluetooth:off,
Debugging:on,
Wifi:connected to my phone's AP,
laptop:connected to my phone's AP
After connecting both devices to the same AP, i was able to find and connect to my galaxy watch on tizen studio. So, connecting with a phone's AP worked for me.
You need to accept debugging rha fingerprint from your watch. That is, you need to check and press the tick on the watch.
I have a POS terminal (APEXA G from POSBank) that comes with multi-touch screen made by Silicon Works. The touch works perfectly on Windows there are official drivers for it. But for Linux the touch does not work at all. After inspecting the device on Linux Ubuntu distribution using [lsusb -v] command I get the follow information:
Silicon Works Multi-touch Device, VID:PID 29bd:4101
The touchscreen is connected through usb not serial connection.
I tried several generic drivers online but none of them worked for me.
After emailing POSBank technical support I received their quick response which solves my problem.
Following their instructions here is what I did:
1. Uninstall the old touch drivers:
- Lanuch Device Manager
- Human Interface Device -> Usb Input Device
- Remove a USB input device with a value of VID_29BD in the attribute (PID is 3711 or 4101)
2. install latest drivers chipset, LAN, touch, etc... (These drivers downloaded from POSBank official website)
-------------------------------------------------
Please note:
-You need Windows only to run the software that applies the touch firmware upgrade.
-Touch firmware v1.8 is still not available from POSBank official website yet
you have to contact technical support or email me.
-You Must Install SiW Daemon Control Panel to upgrade the firmware (it is included in the touch driver zip file from POSBank official website)
-------------------------------------------------
upgrade the touch firmware to V1.8 using instructions below:
Open SiW Daemon Control Panel
On device tab press F6
Select Multi-touch device 0
Click File open then select the firmware update file
Click FW update
After Ubuntu boots the touch should start working out of the box no special configuration is needed.
Note: After the upgrade the touch may not work on Windows. Don't Panic. You will hear a beeping sound every time you click on the screen which is a good sign. To fix do the following:
Open SiW Daemon Control Panel on the Device tap
select Multi-touch Device_0 then click Open Device
select Mouse table(2nd tap) and check Emulation Mode
select About tab and click Preserve Settings which preserves the settings through Windows restarts.
If you have any questions please let me know.
I am happy with their solution now touch works for me on Windows and Ubuntu.
Thank you POSBank and special thanks to Peter Kim from the technical support.
When I plug my Galaxy S6 Edge into my computer, Android Studio does not recognize it as an available USB device. I've tried to download a USB Driver update and I have USB Debugging checked on my phone, but nothing is working. What else do I need to do in order to run my app on my phone?
If your settings (S6 USB debugging, driver, Android Studio) are correct, you might try the following:
(On phone) turn USB Debugging OFF
Connect S6 to USB
Click on the notification "connected as MTP device", check the option "camera" (also appropriate for non-MTP connection)
turn USB Debugging back ON
If your device runs Android 6, the notification (step 3 above) should say "Use USB for" and offer 4 choices. You want to click on "Transferring Images".
I had the same problem. I tried with another USB cable (Not the one comes with my s6 edge or any samsung product ) and it worked.
(prior to this i spend almost a day by installing some software and all :(..but only above solution worked for me )
If you see the connected device in the "Other devices" of the Device Manager, try adding "Hardware Ids" of it to android_winusb.inf. Then select "Update Driver Software" in the Device Manager.
The detail can be found in the link below. In my environment, adb_usb.ini was not there, so I skipped it but could recognize my Galaxy S6 Edege.
http://jodieorourke.com/view.php?id=190&blog=news
There are different ways how to connect USB device.
MTP - to enable remote computer browse device's files. Need to be accesible for windows explorer.
Camera - device works as media (photos, videos, music) provider - these media could be imported to other device like PC. Typical usage is with Photo managing SW on PC like Zoner Photo Studi, LightRoom, ...
MIDI (Iam not sure, but another standard how to share music device)
Power only - device does not provide any functions to connected computer, it use only its power over USB cable.
So, change type to MTP or CAMERA and android studio show see your device.
W
Make sure you have enabled developers option this can be enabled by 7 times tapping on Build number in settings ---> About phone.
I know I'm a bit late to answer, but maybe it will help other people in future. Me too I've got a Samsung S7 Edge, and couldn't debug with it. After some checking I realized that the reason is the Knox/My Knox. See here: https://seap.samsung.com/forum-topic/can-i-use-usb-debugging-mode-device-running-knox
What I've done is just go to playstore, found there My Knox and clicked Uninstall, then switched on USB debugging in Developer options that was previously grayed out.
(There are some other manuals on how to disable Knox. Some of them require rooting, but after rooting, I believe Samsung warranty will not work, if something happens to your phone. )
This is quite a common question, but none of the solutions appear to work for me. First time asker, so apologies if I get the conventions wrong.
I am trying to connect my Galaxy S5 to my computer running Ubuntu 14.04 so I can do some android development. I have recently downloaded and installed Android Studio and the SDK and my device is detected when it's connected via USB but the device either appears as 'unauthorized' or 'offline'. I know I should be expecting the RSA key prompt but this never appears.
I have tried:
Checking debugging was enabled
Running adb kill-server and adb devices
Restarting (the device, developer options, the machine)
Simple unplugging and replugging the USB cable
Checking my adb version (it is 1.0.31)
Trying different USB ports
Revoking USB debugging authorizations
Toggling enabling ADB Integration from within Android Studio
Connecting as PTP device and MTP device
I have tried it on a separate machine that runs fedora and this works fine with no issues, the promopt appears right away. Therefore I imagine it is not the USB cable that is faulty.
Any ideas?
Try these:
Unplug and replug the USB cable.
If it still doesn't work, unplug the USB cable, disable then enable USB debugging in the device settings.
If the above two methods fail, reboot the device.
If rebooting the device also fails, reboot Android Studio too.
If reboot Android Studio still fail, try adb kill-server then adb start-server.
Try killing adb adb kill-serverthen disable usb debugging and then start adb by adb start-server then enable usb debugging and plug phone again and huh don't let phone sleep between process
EDIT
There turned out to be a problem with my laptop's ADB RSA key. I'm assuming my G3 was rejecting a bad key and disallowing my laptop to connect to it via ADB.
ADB saves a key file in one of multiple places on a Windows computer, the first is in the location where adb.exe is (C:\android), the second is in the user's >profile (C:\Users*username*.android), the third place is in the Windows system files (C:\Windows\System32\config\systemprofile.android), the file is >simply named "adbkey" with no extension. If there is no key file when ADB runs, it will generate one automatically.
Mine was located in my user folder (C:\Users*username*.android). All I had to do was delete the adbkey file (there was also a file named "adbkey.pub" which >I deleted as well), restart the adb server in command prompt (adb start-server) and plug my phone in. I instantly received the RSA Fingerprint Key window on my >G3 allowing connection between the two devices. Then typing "adb devices" returned my phone's serial number followed by "device" showing it was available. >I went back to the C:\Users*username*.android\ folder and sure enought there were new "adbkey" and "adbkey.pub" files.
got from XDA
EDIT 2
TRY this steps too
Navigate to where .android is stored
open .android and delete file named as adbkey and adbkey.pub
Start ADB then typeadb kill-serverand adb start-server
My fix to this issue:
Android settings
Developer options
Revoke USB debugging authorizations
Replug in device and accept authorization as usual.
Profit
Step 1: Turn off USB DEBUGGING in Developer Options
Step 2: Remove USB Cable
Step 3: Turn on USB Debugging(This rests USB Configurations)
Step 4: on Command Prompt enter adb kill-server and then adb start-server
Step 5: Connect the USB Cable
Step 6: Check Devices connected in Run in Android Studio(you should be able to see your device listed)
Step 7: If you want to continue running using the cable this would be good enough
(If you want to do Wireless Debugging continue with below step)
Step 8: type adb tcpip 5555. If no error is displayed remove USB Cable
Step 9: Look up IP Address of your phone from About abd then type adb connect xxx.vvv.b.n(your phone's IP)
Step 10: Check in Devices in Android Studio again and you shud see you r device in List of devices. If yes,
If you are on windows and you encountered the same problem, try killing the adb.exe process from task manager and then rerun your app.
Change the USB cable !!!!
I can't explain this technically, however after a lot of trial and error, this what have worked for me.
Could not get Samsung Note II (N7100) to connect.
Step 1. Follow answer from user4847410 above. Next time you connect your phone it will come up with an authorisation message and you're in.
Step 2. I also swapped my cable.
Step 3. Check USB port as if you install on one particular port then another port may not be ok for you.
Note: made two batch files
adb-fix.bat
adb kill server
adb start server
pause
adb-devices.bat
adb devices
pause
-- voted for that correct answer but I don't have enough kudos so it was removed! --
To fix this, use USB2 instead of USB3
A shorter cable did the trick.
It turns out that the wire thickness used inside the cable impacts on the resistance of the cable assembly – this resistance causes energy loss inside the cable when an attached load draws a current, and causes a voltage drop which can reduce the voltage to the end device to a point where it is not possible to charge quickly or completely.
http://goughlui.com/2014/10/01/usb-cable-resistance-why-your-phonetablet-might-be-charging-slow/
Change your USB Preferences to File Transfer if you use your smartphone to debug.
There are several option :
File Transfer /* Choose this one */
USB Tethering
MIDI
PTP
No Data Transfer
I had a long white cable. Just wouldnt stay connected. Switched to another, shorter, black cable and it works 100% of the time.
Disabling and Enabling the Developer options and debug mode on the Android phone settings fixed the issue.
Earlier for almost 3hrs I did:
I tried everything given in several sites and my android device never came online.
when I was running adb kill-server and then adb-startserver the "Device File Explorer" on the right bottom of the android studio showed "Device is not online (DISCONNECTED)".
Here is how solve this:
Revoked all USB debugging authorization on the device under "Develop options"
And I added sudo to command "sudo adb kill-server" and then " sudo adb start-server".
After this the message in "Device File Explorer" in android studio changed to "device is pending authentication please accept debugging session on the device". But no message appeared on the device. Tried stopping-restarting adb, connect reconnet usb cable, stop-start usb debugging but nothing worked.
Went back to device and changed the device usb settings from usb charging to "PTP", and, restarted the Android studio. And, boom, the message appeared on the phone to accept the debugging session on device.
use this command
-> adb disconnect
-> adb connect <ip address for your mobile:port number>
Eg : adb connect 192.168.2.58:5555
You can try this:
Go to tools/enable adb integration and uncheck it.
now check it and run again. Next time, android studio will restart adb and it may find your device.
Restart adb by issuing these commands in cmd
adb kill-server to kill existing adb session followed by adb start-server to start a new adb session
Disable and re-enable USB debugging on the phone and accept RSA fingerprints if asked by phone
Rebooting the phone if it still doesn't work.
If all above don't solve your problem, you may try delete environment variable named "ANDROID_SDK_HOME".
It really solved my problem. Hope it Help you!
This fixed for me
uncheck launch in tool windo
Source
https://github.com/google/android-emulator-m1-preview/issues/76#issuecomment-1023563846
This problem is because you have used an old adb version and not support on your device. or you have more than one adb
The key is:
make sure you have a latest adb executable on your SDK
Make sure to run adb command from "SDK_DIR/platform-tools/" because this should be the latest version (type command "which adb" to check) if u have more than one adb file, you can rename another one.
in my case, on my Windows 7 i have one more adb on "C:\Windows\adb.exe" and its an old version, so my adb command always run from that file. I fixed the problem by running adb form my sdk directory "SDK_DIR/platform-tools/adb.exe"
On windows--> Launch your terminal from the platform-tools folder inside android sdk.
Then use the following commands
adb kill server
adb start server
it should work
Try upgrade your Android SDK Platform as below steps:
Run the SDK Manager
Execute "Install packages…"
Restart the SDK Manager
I tried and it's ok for me.
ref: link
You maybe having an older version of the ADB, Update the tools package and that should bring down the latest ADB.
I also recently had this problem and I solved it by rebooting Android Studio. But my friend had to have the original cable for his device, no other cables worked.
In my case (same problem - that Nexus 5 is connected but with "offline" status) the problem was solved by "Invalidate caches and Restart" in Android Studio.
Suppose that problem was in adb and restarting Android Studio causes to adb restart.
Download and Install your device driver manually through visiting manufacturer website like :Samsung,micromax,intex etc.
In my case the problem was that I used a USB extension cable. As soon as I plug the microUSB cable right into the PC the device has detected.
In my case, turned out that you need to be logged as owner of device to properly accept the USB debugging.
Tried the "Disable and re-enable USB debugging on the phone" step but didn't get the RSA prompt on "normal" user, switched to owner and tried again and got it.
I had this issue on a device with USB-C using a microUSB cable with a USB-C adapter. After switching to a USB-C cable without any adapter it worked. I only saw this issue on a LeEco.
I tried most of the things on this page and none of them worked for my Samsung S5. However, when I switched the cable to a USB-C type the problem seemed to be solved...until next time.
Besides the solution mentioned above, try to download Samsung's Android USB Driver for your platform. Here is a link to the Windows one:
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
If your app doesn't manipulate WiFi connections - another slightly different solution, which bypasses USB issues entirely - enabling a wireless debugging connection - ADB over WiFi/TCP/IP.