I had recently lost my Samsung Note 2 android device which forced me to get a brand new OnePlus 3 device. I had hoped everything would just be a smooth ride for Android development.
It was until I was using my MacBook pro in which I had faced no problems with by just installing all the basic required SDKs with the USB Driver using the Android SDK manager in Android Studio Tools> Android > SDK Manager
Under the SDK Tools menu option > Google USB Driver. Mine looked something like the below:
Not to forget I wont be going through all the default configurations you need to make to enable developer options in your device and then enable USB Debugging etc. There are plenty of tutorials that handle all the basic settings.
However when I started installing and setting up Android Studio on my Windows Laptop same didnt work. Firstly Windows was not by default detecting my device. Had to workaround this to find out my OnePlus3 USB driver separately.
The common error I was trying to workaround was:
No USB Devices or running emulators detected
I used the following Video to figure out some basic settings for windows to enable USB Debugging in Windows.
There was a point where I had to find Oneplus 3 specific USB Driver which I found and installed from the link here:
I went ahead and installed both the USB Driver as well as ADB/Fastboot drivers just in case. Just followed the instructions from the youtube link. And then if you still face problems try to reset the device debugging setting, disconnect the USB cable and then connect it again:
Once I had the device settings worked up and I could find the device using Android Studio the next error I faced was:
ADB Android Device Unauthorized
error: device unauthorized.
This adb server’s $ADB_VENDOR_KEYS is not set
Try ‘adb kill-server’ if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Below steps solved the problem for me:
unplug your Android Device
revoke USB debugging authorizations in Android Developer Options
plug your Device. You can accept the fingerprint once more.
If that doesnt help there are some really long length of steps that might work for you over the below link, just give it a try and comment below on this post which worked for you. That might help others fix it too.