Hey Guys,
Switching back to android...my Smartwatch 3 arrived before my oneplus one. Trying to get ghostracer running on my watch before my phone arrives, but in adb I keep getting unauthorized. The device shows, but no matter what I try it keeps say "unauthorized" in adb. Is that because I am not connected to a phone as well? Any help would be appreciated.
Thanks,
John
The watch needs to be connected to a phone/tablet. On first connection you have to authorize your computer.
Thank you. I had used a friends phone to get past the initial setup on the watch. Then when I brought it home I thought maybe I could connect to the PC and sideload, but I guess I have to have that phone in the chain. Thanks for your help.
yeah you have to have a phone I had the same problem
Hi, my SW3 was connected to my Mi 4, setup done and working fine. I used Titanium Backup to backup Android Wear and all the watch faces apps.
After I flashed a new custom ROM, used Titanium Backup to restore Android Wear and watch face apps, and also Bluetooth connections on my Mi 4. When SW 3 is connected to my computer, in Adb, it says unauthorised.
So does it mean that my only option is to reset my SW 3? I read from http://forum.xda-developers.com/showthread.php?p=60611744
that I could use the following command to force the Bluetooth connection. The command can't work since my device is unauthorized.
Any suggestions?
What's the problem with a reset? It just needs some time to sync the wearable APKs after connecting to the phone.
My phone is connected but it still says unauthorized, do you mean my phone needs to be connected to the computer?
You probably have this sorted now but do you have the drivers installed properly?
Sent from my Sony Xperia Z5 using XDA Labs
Related
hi folks,
first time it happend to me with an adroid device, so i guess i ve missed something
i can t connect the watch to my computer on iwich i have no prob with all my other android device ans sony z2 & z3
in the device manage i keep having a yellow triangle warning, i ve re installed sony companion, changed nothing, and if i activate adb debut, it s not seing by the pc
i ve also tried different pc, and cables, so waving the white flag and asking for help!!!!!
thxx for your time
best regards
nocomp said:
hi folks,
first time it happend to me with an adroid device, so i guess i ve missed something
i can t connect the watch to my computer on iwich i have no prob with all my other android device ans sony z2 & z3
in the device manage i keep having a yellow triangle warning, i ve re installed sony companion, changed nothing, and if i activate adb debut, it s not seing by the pc
i ve also tried different pc, and cables, so waving the white flag and asking for help!!!!!
thxx for your time
best regards
Click to expand...
Click to collapse
Yep, I have the same issue. Its not being detected at all. I've troubleshooted this on linux. No udev events are emitted when the device is plugged in and on. A mass storage device is detected when I switch the device off though. I'm on 5.0.2.
Hi, I had this very problem and found that that you have to switch the watch off then attach the mini us to the watch only, then hold the power button of the watch (don't let go) and eventually the watch screen will come on with an attach usb picture, now plug the main usb end into the PC and it should be recognised by Sony PC companion. I forgot to mention that the PC companion program should be started before plugging it in. Good luck Grant.
hi grant, thxx a lot for your message
i tried that before and no luck :/
I am currently on Android Wear 2.0 preview 2. My Huawei watch is not being detected by my PC although I have ADB enabled. In fact, the watch is not even detected as an unknown device in the device manager. I am able to get Bluetooth debugging working. However, since fastboot doesn't detect my device I am unable to flash either a new recovery or upgrade my watch. I am able to enter the fastboot/recovery mode manually by clicking on the button when the huawei logo appears during boot. However, I get an error message saying /sdcard cannot be mounted and am unable to flash any zip file due to this using the Droid recovery. The watch boots up normally and works well otherwise except that i am stuck with the preview 2.0.
Is the issue due to a faulty cable or a badly flashed recovery or is there anything else i can try so that i can revert back to stock or flash a new rom? Any suggestion is greatly appreciated..
I'm having the same issue on two separate watches, and have been for quite some time. Have tried multiple computers, multiple chargers, to no avail... Using stock recovery, preview 2. Watch will charge, no problem, but the PC won't notice that the watch is plugged in in any way no matter fastboot, recovery, or just booted.
same here, watch will charge but no prompt to access interal memory. Is simply stock, so no preview version
Same here. Flashed the 2.0 preview and now can't get ADB through a wired connection. Hoping someone can help.
Are you guy's using linux? I had the same problem on multiple linux distro's. As soon as I went back to windows 10 I was able to connect through ADB and flash the beta firmware.
vicvon said:
Are you guy's using linux? I had the same problem on multiple linux distro's. As soon as I went back to windows 10 I was able to connect through ADB and flash the beta firmware.
Click to expand...
Click to collapse
I've tried on Mac OS X Sierra and Windows 10.
firefurby said:
I've tried on Mac OS X Sierra and Windows 10.
Click to expand...
Click to collapse
On Windows 10 did you install all the ADB stuff? I had to install a bunch of stuff for ADB to actually work.
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
vicvon said:
On Windows 10 did you install all the ADB stuff? I had to install a bunch of stuff for ADB to actually work.
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Click to expand...
Click to collapse
Yeah, I've tried the Minimal ADB and Fastboot as well as a full install of Android Studio. I'll give this walk through a shot too. I'm desperate.
Anyone have any luck getting their watch to be recognized again?
try pdanet adb drivers
also, sometimes even if fastboot doesn't register as detected, you can still flash anyways
Anyone ever get anywhere with this? I'm still hoping for a solution.
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Hmmm... I'm using a Mac mainly. I'll give this a try on my windows machine later. Thanks!
Pkt_Lnt said:
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
First, remove all other drivers using USBDeview.
http://www.nirsoft.net/utils/usb_devices_view.html
Then use this tutorial to manually install the Google USB driver.
http://visualgdb.com/KB/usbdebug-manual/
Click to expand...
Click to collapse
Pkt_Lnt said:
I've posted this many times in the various Huawei forums and it has worked for everyone so far.
Click to expand...
Click to collapse
The problem is that you can´t do anything if the watch isn´t recognized on the pc, it doesn´t matter if an adb driver is installed or not...
Same problem, watch is charging only, tried 7 pcs an no one can handle the device...nothing.
Same here. The Android Wear version on the watch is 1.3.0.2145535.
Device Manager does not detect the watch at all. Nada (no entries with exclamation marks). Just charging. Does that mean the cable has a defect?
It's driving me nuts, as I am not able to get OTA updates, adb debugging would be my only chance to upgrade to Android Wear 1.5.
Build Number: LCA37B
Android Wear: 1.3.0.2145535
Goolge Play Services: 7.8.99
Android OS: 5.1.1
SirRobin78 said:
The problem is that you can´t do anything if the watch isn´t recognized on the pc, it doesn´t matter if an adb driver is installed or not...
Same problem, watch is charging only, tried 7 pcs an no one can handle the device...nothing.
Click to expand...
Click to collapse
mysteray said:
Same here. The Android Wear version on the watch is 1.3.0.2145535.
Device Manager does not detect the watch at all. Nada (no entries with exclamation marks). Just charging. Does that mean the cable has a defect?
It's driving me nuts, as I am not able to get OTA updates, adb debugging would be my only chance to upgrade to Android Wear 1.5.
Build Number: LCA37B
Android Wear: 1.3.0.2145535
Goolge Play Services: 7.8.99
Android OS: 5.1.1
Click to expand...
Click to collapse
Have you tried just running the flash-all.bat? I've have seen posts and experienced it myself that the watch is not detected after a screw up on my part, yet the flash-all.bat will run and install the OTA, even though I was in panic mode. Manually boot the watch to bootloader mode with the watch button and try, it might work, worth a try. Good luck.
Even though I was pretty convinced that this could never work, I nevertheless gave it a try. After executing flash-all.bat it just says < waiting for any device > and does nothing, as was expected by me. Would have been magic, if it had communicated with the watch having no entrypoint for it in the system.
Pkt_Lnt said:
Have you tried just running the flash-all.bat? I've have seen posts and experienced it myself that the watch is not detected after a screw up on my part, yet the flash-all.bat will run and install the OTA, even though I was in panic mode. Manually boot the watch to bootloader mode with the watch button and try, it might work, worth a try. Good luck.
Click to expand...
Click to collapse
mysteray said:
Even though I was pretty convinced that this could never work, I nevertheless gave it a try. After executing flash-all.bat it just says < waiting for any device > and does nothing, as was expected by me. Would have been magic, if it had communicated with the watch having no entrypoint for it in the system.
Click to expand...
Click to collapse
Use the watch button to reboot to bootloader when you the the < waiting for any device > message and it *might* work. That is what happened to me. Sorry I was not clear about that in my post above. You need to boot into bootloader mode while that message is displayed.
Tried that, as well. Doesn't make any difference.
Thanks for the suggestion, though.
Pkt_Lnt said:
Use the watch button to reboot to bootloader when you the the < waiting for any device > message and it *might* work. That is what happened to me. Sorry I was not clear about that in my post above. You need to boot into bootloader mode while that message is displayed.
Click to expand...
Click to collapse
Same issue here
I'm also having this problem but not on Android Wear 2. I'm using stock, non rooted, and locked bootloader and therefore Android Wear 1.x. I only became aware of this issue when I decided that I wanted to get Android Wear 2 on my watch (using the preview).
The watch charges but in no way can I get my PC to detect that the watch is actually there, tried two Windows 10 PCs but both have the same issue. I think the problem is either with the watch itself or with the charging dock/cable. I rebooted into fastboot mode but this does not make a difference. The fact fastboot also does nothing makes me think its more likely that the charging dock is at fault. Unfortunately, installing ADB/Fastboot drivers is pointless if the PC can't even see the device to communicate with.
Hi,
Last night my phones touchscreen suddenly stopped responding. Everything is working, except the touchscreen. I did not drop the phone and there is no water-damage. (Brought it to a phone-repairshop). My phone is unlocked, rooted and running a pretty old cyanogenmod rom (Android 6.0.1). I was told that it probably is a software related issue. So I wanted to reset my phone. Problem is that my laptop isn't recognizing my phone. When I connect my phone to my laptop, it doesn't show up or it says an error has occured, but my phone does start charging. It looks like it disconnects imediatly. So I am not able to install correct drivers.
Another problem is that I am using a touch recovery, so I also can't reset my phone through the recovery menu.
I also tried to connect in the bootloader menu, but than my laptop doesn't see any device connected.
In ADB i tried the command ''adb devices'', but no device is found.
I tried different laptops and usb-cables.
What can I do to make it working again?
Thanks, Jidde
Is my watch bricked? PC & Device Manager not recognizing watch, drivers are installed
I was running on the latest (v2.7) Negalite Rom NX 1 when I got the notification to update the watch. Upon rebooting (and presumably installing), the watch got stuck in loading screen (4 dot animation) so I force rebooted the watch into recovery and wiped everything (Advanced Wipe, everything).
Upon connecting my watch to my computer (watch in recovery (TWRP)), I was not able to connect the watch to ADB nor Fastboot; adb/fastboot devices returns nothing.
I tried reinstalling, uninstalling, deleting and reinstalling the drivers but I haven't gotten any success
I've tried several ports (and another computer) without any success
The watch does not show up at all in Device Manager (definitely not in "Other Devices")
I'm unable to manually install the device drivers because the watch does not show up in Device Manager
The device is connected because it's charging, but there's no notification sound when plugging the watch/USB cable into the computer
I have previously been able to connect the watch through ADB, to be able to transfer Negalite rom, likely half a year ago
I've tried installing Pdanet ADB Drivers, but it requires the watch to be detected otherwise it closes the installer
I am using Windows 10
Has anyone else had this problem? Is there a way to check if the drivers are installed or not?
Every thread I've read instructs to install the drivers manually for the device, but I don't have the device in Device Manager.
I'd love to be able to use the watch again (currently sitting @ 100% battery, in TWRP).
Thank you
Edit: When I boot system from recovery (I know I don't have an OS installed), I get a message that I haven't seen before: "Device software can't be checked for corruption"
I read that it was caused by unlocked bootloader, but I've never encountered that before, if I had accidentally booted system without OS.
Hi,
I have a question regarding DEX...
My Note 10+, Windows 10, DEX and samsung USB driver are up tp date. Everytime i connect, DEX launches on my PC, i get the notification in my phone that DEX is running. However, in my pc, DEX will just shut down immediately after connected. This had happened since i received the phone after it was launched in my country. Initially DEX was able to run, occasionally. All i need to do is to restart my PC, and DEX will be able to connect. However, after the 2nd phone update, I'm unable to use DEX anymore. I used the original samsung cable and a few other cables to connect to PC, USB C to USB 2 type, tried them on all available ports in my PC.
Additional Steps other than updating phone and DEX that i had taken to try to resolve the issue:
1. Clear phone cache
2. Restart pc and phone
3. Change cable
4. Google (unable to find similar issue)
5. Search through samsung FAQ.
6. Searched in this forum.
Any help will be much appreciated.
Thanks in advance...
Sent from my SM-N975F using Tapatalk
radiikal said:
Hi,
I have a question regarding DEX...
My Note 10+, Windows 10, DEX and samsung USB driver are up tp date. Everytime i connect, DEX launches on my PC, i get the notification in my phone that DEX is running. However, in my pc, DEX will just shut down immediately after connected. This had happened since i received the phone after it was launched in my country. Initially DEX was able to run, occasionally. All i need to do is to restart my PC, and DEX will be able to connect. However, after the 2nd phone update, I'm unable to use DEX anymore. I used the original samsung cable and a few other cables to connect to PC, USB C to USB 2 type, tried them on all available ports in my PC.
Additional Steps other than updating phone and DEX that i had taken to try to resolve the issue:
1. Clear phone cache
2. Restart pc and phone
3. Change cable
4. Google (unable to find similar issue)
5. Search through samsung FAQ.
6. Searched in this forum.
Any help will be much appreciated.
Thanks in advance...
Click to expand...
Click to collapse
Dex was working for me ever since i got my Note 10 +
months back (launch dateAug / October ..? ) with my Lenovo laptop.
However a few day back, i got a notification to update Dex.
(I have done a few Dex updates.) No issues.
Done the update and now basically have the same issues as you.
Launch Dex.... does not launch..
Notifications on my phone Dex running...
Bottom line,
I'm sure it has to be a Dex bug..... software .!
I did not even attempt to investigate, as all Dex was working 100.%
Just waiting for the next Dex update.
My phone companion which was always buggy, is now working fine.
Good luck
radiikal said:
Hi,
I have a question regarding DEX...
My Note 10+, Windows 10, DEX and samsung USB driver are up tp date. Everytime i connect, DEX launches on my PC, i get the notification in my phone that DEX is running. However, in my pc, DEX will just shut down immediately after connected. This had happened since i received the phone after it was launched in my country. Initially DEX was able to run, occasionally. All i need to do is to restart my PC, and DEX will be able to connect. However, after the 2nd phone update, I'm unable to use DEX anymore. I used the original samsung cable and a few other cables to connect to PC, USB C to USB 2 type, tried them on all available ports in my PC.
Additional Steps other than updating phone and DEX that i had taken to try to resolve the issue:
1. Clear phone cache
2. Restart pc and phone
3. Change cable
4. Google (unable to find similar issue)
5. Search through samsung FAQ.
6. Searched in this forum.
Any help will be much appreciated.
Thanks in advance...
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
Just an update , to my post above .
I again , downloaded the "Dex exe "from the official Samsung site .
https://www.samsung.com/za/apps/samsung-dex/
Then "ran/launched " the exe , that then prompted me to completely ,uninstalled Dex on my laptop .
After uninstall ,i again ran the exe to install .
I did not have to install anything else eg ..drivers again .
Dex is now working ( launching ) ) on my laptop .!
Secondly/alternatively ,
have you connected you phone ,to just a capable tv /monitor and launched Dex this alternative way , is " that method" working , for you ...??
Good luck .
I'll try your method and report back.
As for 2nd method, i had only tried to connect to the usb hub that came with my monitor (and of course the usual usb ports on the motherboard ). So far it's a no go.
Thanks for the suggestions and hope it will work.
Much love!
Sent from my SM-N975F using Tapatalk
willcor said:
Just an update , to my post above .
I again , downloaded the "Dex exe "from the official Samsung site .
https://www.samsung.com/za/apps/samsung-dex/
Then "ran/launched " the exe , that then prompted me to completely ,uninstalled Dex on my laptop .
After uninstall ,i again ran the exe to install .
I did not have to install anything else eg ..drivers again .
Dex is now working ( launching ) ) on my laptop .!
Secondly/alternatively ,
have you connected you phone ,to just a capable tv /monitor and launched Dex this alternative way , is " that method" working , for you ...??
Good luck .
Click to expand...
Click to collapse
After i did what u did, DEX actually worked.... For one time only LOL
After that same thing happened, DEX shut down immediately after connected.
Looks like i dont have the luck to use DEX after all
Sent from my SM-N975F using Tapatalk
radiikal said:
After i did what u did, DEX actually worked.... For one time only LOL
After that same thing happened, DEX shut down immediately after connected.
Looks like i dont have the luck to use DEX after all
Click to expand...
Click to collapse
Some additional questions, Maybe it can help...?
Does Dex work, if you connect with cable to only a eg tv screen.?
I just tested my device,
connected my device with HDMI/USB C to a tv screen and working fine..?
Is your pc /laptop, anti-virus may not killing Dex..?
Or your Note 10 device anti virus killing it ....
if you have any installed on device.?
Have you maybe disabled any apps eg with Package Disabler etc and now hav a knock on effect.?
Can you check with someone near you or local forums
to see if Dex is working for them.?( If they have any issues.)
Is Dex not maybe blocked by service provider.?
If Dex shuts down, does it pop up any "toast texts"? before shutting down?
If it does install a any "Toast " app form Play store
eg "Toast Source" app works fine for me. to "catch"
the toast popup, so that you can read reason for shutting down.
Question is according to you,
Dex starts, but is killed by either
the Device System or a 3rd party app?
Yes "something" eg app, anti virus etc is killing Dex,
as you are able to install Dex fine etc...... until launching Dex.!
Then Dex gets killed by.....?
Look for the culprit /app thats killing Dex..!
I can imagine this must be very frustrating for you !
Good luck
I've had the same issue for a every now and then. The fastest and easiest way I found to fix this is to pull the shortcuts and notification down There should be a small notification "Android System" USB for file transfer. tap this and change the USB mode to something else and then change it back to file transfer. This should allow Dex to see the phone or the phone see the PC again. Hope this helps!
Hello,
Can you try to update the Dex app with aptoide ?
Do you use CCSWE and you deactivated a service related to Dex ?
I had similar issue, it doesnt work if Samsung Keyboard is disabled
saurabhsun said:
I had similar issue, it doesnt work if Samsung Keyboard is disabled
Click to expand...
Click to collapse
THIS! Re-enabling the Samsung Keyboard stopped DEX from crashing. Thank you, it's been driving me crazy!
I've tryed another USB port and it work fine.
radiikal said:
Hi,
I have a question regarding DEX...
My Note 10+, Windows 10, DEX and samsung USB driver are up tp date. Everytime i connect, DEX launches on my PC, i get the notification in my phone that DEX is running. However, in my pc, DEX will just shut down immediately after connected. This had happened since i received the phone after it was launched in my country. Initially DEX was able to run, occasionally. All i need to do is to restart my PC, and DEX will be able to connect. However, after the 2nd phone update, I'm unable to use DEX anymore. I used the original samsung cable and a few other cables to connect to PC, USB C to USB 2 type, tried them on all available ports in my PC.
Additional Steps other than updating phone and DEX that i had taken to try to resolve the issue:
1. Clear phone cache
2. Restart pc and phone
3. Change cable
4. Google (unable to find similar issue)
5. Search through samsung FAQ.
6. Searched in this forum.
Any help will be much appreciated.
Thanks in advance...
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
Turn off Link to Windows. This happened to me yesterday. On the second try I say a very brief pop up on my phone telling me to turn off Link to Windows.
As soon as I did that it worked fine.
Sent from my SM-N976V using Tapatalk
Sorry for being silent all these while...been trying all the suggestions here but none works for me. Updated dex no help too.
Thanks again for all the suggestions. Will update if i managed to find a solution.
Sent from my SM-N975F using Tapatalk
I had this issue. Was tinkering around until I turned off the "Link to Windows". Dex worked for me afterwards
radiikal said:
Hi,
I have a question regarding DEX...
My Note 10+, Windows 10, DEX and samsung USB driver are up tp date. Everytime i connect, DEX launches on my PC, i get the notification in my phone that DEX is running. However, in my pc, DEX will just shut down immediately after connected. This had happened since i received the phone after it was launched in my country. Initially DEX was able to run, occasionally. All i need to do is to restart my PC, and DEX will be able to connect. However, after the 2nd phone update, I'm unable to use DEX anymore. I used the original samsung cable and a few other cables to connect to PC, USB C to USB 2 type, tried them on all available ports in my PC.
Additional Steps other than updating phone and DEX that i had taken to try to resolve the issue:
1. Clear phone cache
2. Restart pc and phone
3. Change cable
4. Google (unable to find similar issue)
5. Search through samsung FAQ.
6. Searched in this forum.
Any help will be much appreciated.
Thanks in advance...
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
You may have to turn off "Link to windows" on your phone first.
I got the Samsung Note 10+.
i have been trying to troubleshoot this same problem for the longest time, where i connect my phone from usb-c to my pc, press start now on phone and samsung dex will just close immediately.
finally today i went to the my phone setting, searched for "dex" and saw "Samsung DeX" under "Advanced features".
This is my first time going into "Advanced features" and I noticed many settings were turn off here.
So i turn on "Samsung DeX" and it seemed to have worked!!! I press start now and the connection went ahead to my pc and samsung dex started loading with the UI. I have not seen this app for a long time.
Now the question on why is it turn off by default? I don't know. I was able to connect to samsung dex on pc without problems.
i tried again and it didn't work! so i had to trial and error again. i can't do the normal unplug and re-plug in usb and press start now because samsung dex will exit immediately like before.
I had to plug in usb and then press the Samsung DeX to turn it on in my settings and it worked again. I don't know why it has to be this way.
I also went ahead and turn on Link to Windows, Call & text on other devices, Continue apps on other devices as well. Just because I want to use all these features when I connect my phone to pc.
hope this helps anyone with similar situation