device unrecognised over ADB (I want to write secure settings)

[Matevz Leskovsek]

-USB debugging allowed, 

-permission to access phone and data is given on the phone when USB connects

- USB settings cannot be set to other device controls USB, so they are set as in screenshot in attachment

- image.png shows cmd output

Android 10 (non root), Windows 10

[Matevz Leskovsek]

Of course I already tried killing and restarting server and I got the same results. There is no other confirmation poping up on android device when i run adb, only the one confirmation when USB connects (as described in previous post)

[Tulio Farias]

Hi, I had the same issue and I've fixed it doing this:
https://www.addictivetips.com/android/fix-adb-device-unauthorized-message-android/
Hope this helps for you.

[Matevz Leskovsek]

Thank you but in my case I apparently just needed to use another shell on windows 10. "Windows Powershell" worked nicely and all is good now.

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/0f7a81ba-240a-4dd1-a62a-260d808f2e92o%40googlegroups.com.

[matevz.l...@gmail.com]

I have this problem again: device is simply not recognised by PC and no permission is being prompted on android when I connect USB. Also device is not discovered in windows file explorer. I am using same android with same settings, same powershell on the same windows laptop, same cable in the same USB port.

Obvsly I tried deleting adbkey in windows, killing adb server, restarting windows, 

and on android: revoke usb permissions, set USB default to transfer files, disable usb debugging, restart device, enable usb debugging, connect USB

Any ideas? This is kinda frustrating... Samsung A40, windows10

[matevz.l...@gmail.com]

another device (android 8.1) connects nicely so it may be a faulty microUSB connector or some android10 issue

[Matevz Leskovsek]

Solved: i switched usbc orientation many times, everytime doing all the steps mentioned above, and it connected somehow. This is kinda scary though. I need to learn adb via wifi as i think that would be more reliable.

To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/a3c72a85-e4c6-4d5b-ad38-9c6b5ede396en%40googlegroups.com.

[logan...@gmail.com]

I had to scroll thru various connection types to get my first ADB Wifi permission granted to phone. Since then, it has always been immediately recognized when plugged in

[Matevz Leskovsek]

Honestly I havent tested adb wifi yet, but in adb via usb you also have to change usb connection type from file transfer to something else and back to allow device to be recognised in adb, but still it doesnt work always. Hope adb/wifi is more reliable. Probably our cables or usb connectors are getting unreliable.

To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/3265bc76-5a7d-4521-a083-3064e4fcbb37n%40googlegroups.com.