USB Debugging Not Active when connected to Pc

[BluSpark85]

Hey guys. I wanted to ask if anyone was having issues with getting USB Debugging to work on the beta. I tried everything I can think of. Autoblocker is off. I tried disabling and reenabling developer options. Turning USB Debugging on and off. Revoking adb authorizations. Uninstalling and reinstalling USB and adb drivers. 

I have the latest platform tools for my computer. I tried different cables. Two PCs. 

I tried switching from file transfer, usb tethering, midi and picture transfer. Nothing has worked. Is this normal for a beta? I wasn't sure how this work. 

I apologize for not being clear. What I'm referring to is that when I connect my device to a PC, there's no prompt or notification of USB debugging being active. Adb doesn't recognize my device when I type in adb devices. 

[AlJalali]

Turn auto blocker off then exit setting , then go back to settings and turn it on. Last step go developer options and then you should be able to turn debugging on.

[BluSpark85]

Thank your for the response. I apologize because I don't think I was being very clear. USB debugging is switched on my device. The issue is there is no prompt or notification of it being on when connected to my PC's. Adb doesn't even pick up my device as being connected. Not even when I type in the command adb devices. That's why I tried all of these options I listed. Have you connected your device to a PC to see if USB debugging is enabled on your notifications?

[AlJalali]

No, unfortunately I didn't have time to do that yet.

[USBetaModerator3]

Hello @BluSpark85,

Thank you for your feedback on USB Debugging issue.

It seems that you have followed the correct step (Dev mode ON, USB Debugging ON > Connect to PC > Not showing any prompts to allow Debugging) and still not getting the proper connection unlike the below screenshot. 

Also, your expectation of "adb devices" command is not prompting on your CMD tool (which is very bizarre).

exp) adb devices
* daemon not running; starting now at tcp:5xxx
* daemon started successfully
List of devices attached
R3CW****** device

We believe that you've already Restarted your device / turned off dev mode On/Off (debugging mode On/Off) and reconnected (along with Unlocking your screen), but please try to do so once more.

If the issue persists, please don't hesitate to submit error report via Samsung Members (prior to 15 minutes of issue). 

Regards,

One UI Beta Team

[BluSpark85]

Hi there. I saw your message today and thank you for reaching out.  Upon looking at your pic that you posted. It does feel bizarre that my device experienced this. 

I didn't get the usual output that you posted which is what I was looking for. I wish I had took a screenshot. The results were hanging with no output after I typed in adb devices. Yes I did follow those steps correctly in that order with no dice. After I tried everything. I actually sent in my bug report within the first few minutes of experiencing this issue after plugging in the device and typing the command. 

Then I went ahead and rolled back to the stable release of ui 6.1 and retryed to enable USB debugging. I was successful on the stable release. Which told me there might be an issue with USB debugging on the beta. I was glad to test it and send in the report. Thank you so much for reaching out. If anyone else is experiencing this. It will definitely get fixed. I believe this is priority issue. Have a good day. 😁