Ok this is driving me nuts so I gotta ask...I have a S20 Plus 5G (Verizon) and have a brand new custom-built computer with a ridiculous amount of USB 3.0, 3.1 ports. I have to tether my phone to my PC for internet so I use the USB-C to USB-C cable that came with the phone to connect to the single USB-C port on the computer. I also use said connection for Samsung DEX (not simultaneously, would if I could lol).
With this specific setup, I don't have any issues at all, but I know for a fact that it's not a 3.0 connection because of the cable (the "Device can perform faster when connected to USB 3.0" message confirms as much). The cable is obviously the limiting factor holding it back from 3.0 so I tried replacing it in the setup with various (both USB-C to USB-C and USB-C to USB-A) 3.0 cables and sure enough, I get the correct "connected through USB 3.0" message under my device's name in the devices menu.
However, no matter which 3.0 cable I try or which 3.0+ port I plug it into, I always run into the issue of the device randomly disconnecting/reconnecting every so often. I get the whole disconnected/reconnected sound deal and the "select what happens with this device" Autoplay message. I've tried turning off Autoplay, turning off the USB notification message option, going into device manager/registry and ensuring that every single thing related to the USB ports has the power conservation option turned of, etc.
One major thing is that when I created a USB 3.0 "certified" connection with my mom's slightly older custom-build computer, it seemingly had no problems holding the connection, so it appears as though it's something on my computer specifically that's causing it. I just frankly have no idea what that thing could be at this point. Any ideas?
lolDayus said:
Ok this is driving me nuts so I gotta ask...I have a S20 Plus 5G (Verizon) and have a brand new custom-built computer with a ridiculous amount of USB 3.0, 3.1 ports. I have to tether my phone to my PC for internet so I use the USB-C to USB-C cable that came with the phone to connect to the single USB-C port on the computer. I also use said connection for Samsung DEX (not simultaneously, would if I could lol).
With this specific setup, I don't have any issues at all, but I know for a fact that it's not a 3.0 connection because of the cable (the "Device can perform faster when connected to USB 3.0" message confirms as much). The cable is obviously the limiting factor holding it back from 3.0 so I tried replacing it in the setup with various (both USB-C to USB-C and USB-C to USB-A) 3.0 cables and sure enough, I get the correct "connected through USB 3.0" message under my device's name in the devices menu.
However, no matter which 3.0 cable I try or which 3.0+ port I plug it into, I always run into the issue of the device randomly disconnecting/reconnecting every so often. I get the whole disconnected/reconnected sound deal and the "select what happens with this device" Autoplay message. I've tried turning off Autoplay, turning off the USB notification message option, going into device manager/registry and ensuring that every single thing related to the USB ports has the power conservation option turned of, etc.
One major thing is that when I created a USB 3.0 "certified" connection with my mom's slightly older custom-build computer, it seemingly had no problems holding the connection, so it appears as though it's something on my computer specifically that's causing it. I just frankly have no idea what that thing could be at this point. Any ideas?
Click to expand...
Click to collapse
I have not understood your intention.
Why do you have to connect the phone via USB cable to your computer?
If you have internet via mobile data on your phone and want to share it with the computer, you can tether via mobile hotspot of your phone. Just connect the computer via wifi to your phone's hotspot.
And your device should be able to use Dex wirelessly. I read about it in one of the latest Android 11 OneUI 3.1 changelog.
Related
Hello, I have really odd problems with connecting devices to my sgs2. When I connect the cable my phone recognizes it and sometimes recognises also wireless mouse when I connect it. Problems starts when I want to connect pendrive or hard drive (with addictional power cable). The phone doesn't recognise it (already found that i need program to mount from market (doesn't work)) and hard drive shuts itself down after few moments.
Also when I take out cable from micro usb port my phone immidiatelly reboots sometimes it even does it when I just connect and disconnect cable without mouse etc on the second end. I am using rooted 4.0.3 XXLPW. Does anyone has similar problems or just my phone has something wrong with usb port? Looking forward for any helpful responses and sorry for my eng. Thanks.
problem with USB HOST
feaden said:
hello, i have really odd problems with connecting devices to my sgs2. When i connect the cable my phone recognizes it and sometimes recognises also wireless mouse when i connect it. Problems starts when i want to connect pendrive or hard drive (with addictional power cable). The phone doesn't recognise it (already found that i need program to mount from market (doesn't work)) and hard drive shuts itself down after few moments.
Also when i take out cable from micro usb port my phone immidiatelly reboots sometimes it even does it when i just connect and disconnect cable without mouse etc on the second end. I am using rooted 4.0.3 xxlpw. Does anyone has similar problems or just my phone has something wrong with usb port? Looking forward for any helpful responses and sorry for my eng. Thanks.
Click to expand...
Click to collapse
from donnyfer
yes man,i have had the same problem ,try to check the quality of your cable ,check wether its damaged because if there is shortcut among the wires,this might be the cause of the problem,
Hello all, I'm having what I would like to call one of the weirdest cases of USB troubles.
For some reason unknown to me, my Galaxy Nexus will simply not connect to my computer's front USB 2.0 and USB 3.0 ports whatsoever. It will simply throw the "USB device not found" message and if I'm blessed with a unicorn's presence, it will connect and show my Galaxy Nexus's file system and disconnect whenever it wants, specifically when transferring a file to the phone. Awkwardly enough, this only occurs on OEM Samsung cables, both on the original cable that came with the phone and a new one that I just purchased off eBay a couple of days ago. I have used the cable that came with my ASUS Nexus 7 (first gen) and it connects perfectly. The driver will install successfully and hold a connection until I physically disconnect it. I even gave the cable that came with my HTC G2 a try and the same thing. However, I decided to test this on two other computers, a school computer and a Dell machine I have at home and both of those machines will hold a perfect connection with the Samsung cables. Although I haven't tested it yet, I'm sure it will connect just fine to my laptop and to the USB ports located in the back of the computer (directly to motherboard)
If it helps any, the computer that is having troubles is encased in a Fractal Design Define R4. I'm thinking it could be a faulty USB header but other devices such as my Nexus 7 and various USB flash drives have connected without any issues. I have used USBDeview to uninstall the Galaxy Nexus driver and I have unchecked USB debugging to "ensure" a clean installation. At this point, I'm lost between re-installing Win7 or calling Fractal for what could be a very specific issue against my Galaxy Nexus.
Anybody have an idea on how to solve this? Much thanks in advance!
leikamkei said:
Hello all, I'm having what I would like to call one of the weirdest cases of USB troubles.
For some reason unknown to me, my Galaxy Nexus will simply not connect to my computer's front USB 2.0 and USB 3.0 ports whatsoever. It will simply throw the "USB device not found" message and if I'm blessed with a unicorn's presence, it will connect and show my Galaxy Nexus's file system and disconnect whenever it wants, specifically when transferring a file to the phone. Awkwardly enough, this only occurs on OEM Samsung cables, both on the original cable that came with the phone and a new one that I just purchased off eBay a couple of days ago. I have used the cable that came with my ASUS Nexus 7 (first gen) and it connects perfectly. The driver will install successfully and hold a connection until I physically disconnect it. I even gave the cable that came with my HTC G2 a try and the same thing. However, I decided to test this on two other computers, a school computer and a Dell machine I have at home and both of those machines will hold a perfect connection with the Samsung cables. Although I haven't tested it yet, I'm sure it will connect just fine to my laptop and to the USB ports located in the back of the computer (directly to motherboard)
If it helps any, the computer that is having troubles is encased in a Fractal Design Define R4. I'm thinking it could be a faulty USB header but other devices such as my Nexus 7 and various USB flash drives have connected without any issues. I have used USBDeview to uninstall the Galaxy Nexus driver and I have unchecked USB debugging to "ensure" a clean installation. At this point, I'm lost between re-installing Win7 or calling Fractal for what could be a very specific issue against my Galaxy Nexus.
Anybody have an idea on how to solve this? Much thanks in advance!
Click to expand...
Click to collapse
Yeah it sounds like a faulty usb cable. I have cables too that just won't hold a connection. Make sure you have "usb debugging" checked though when you want to use adb.
What I almost always use these days is wireless adb connection.
Go to settings >> developer options and check "ADB over network". Then in a terminal on your computer, "cd" to the directory you keep adb or adb.exe and type "adb connect 192.168.0.3" (or whatever ip is listed in settings >> developer options).
7175 said:
Yeah it sounds like a faulty usb cable. I have cables too that just won't hold a connection. Make sure you have "usb debugging" checked though when you want to use adb.
What I almost always use these days is wireless adb connection.
Go to settings >> developer options and check "ADB over network". Then in a terminal on your computer, "cd" to the directory you keep adb or adb.exe and type "adb connect 192.168.0.3" (or whatever ip is listed in settings >> developer options).
Click to expand...
Click to collapse
Thanks for the steps in regards to wireless ADB connection. As much I really want to say it's a faulty cable, I can confirm that the cable will provide a stable connection to the Dell machine I have sitting around and on the school computers as mentioned in the OP. I even got 2 new OEM Samsung cables and neither of them work on the computer that gives me that message with the Samsung cables. It's so frustrating
Hey Guys,
First of all, I am a new member here my name is Salem and its an amazing forum.
Anyway, I have a slight problem with my HTC M9 while connecting it into my laptop. First, when I connect it, the mobile starts charging, and it gives me no option as to change it to Media Transfer or anything... even it gives me "Slow Charging" Error, and my laptop is detecting nothing, as if nothing happened, nor its searching for any drivers...
I went to developer menu and used USB Debugging, and selected USB configuration as MTP, and it didn't work...
I installed HTC Sync to get the drivers, and it is the same.
Can you guys help me? because I wanna root the phone and I tried various Auto Root applications without using the PC and they didn't work. Thank you guys
No signal from the laptop probably means you have a faulty USB cable. Most likely a break in one of the data wires.
Try another good quality usb 2.0 cable.
Beamed in by telepathy.
Same issue. Tried multiple cables
I have the same issue. When I try to plug into any PC a slow charging message pops up but the phone won't give me the option to connect to PC. I have turned on USB Debugging and selected MTP (Media Transfer Protocol). Please help!
I am with TPG. Android 6.0 HTS 7.0 Software number 3.35.617.12
I only bought this phone a week ago and it updated when I turned it on.
jaystarrs said:
I have the same issue. When I try to plug into any PC a slow charging message pops up but the phone won't give me the option to connect to PC. I have turned on USB Debugging and selected MTP (Media Transfer Protocol). Please help!
I am with TPG. Android 6.0 HTS 7.0 Software number 3.35.617.12
I only bought this phone a week ago and it updated when I turned it on.
Click to expand...
Click to collapse
Most likely a crap or broken cable. Other cables, other sockets, other pc's are all worth a try.
You should leave the usb port in "charging only". When you successfully connect to a pc the phone will prompt you to allow data transfers to that computer.
I know this because mine does it. I'm sick to death of the effing thing promting me to connect to my xbox one when all i want to do is charge the effing thing... My phone is set to charging only.
I suppose rom choice will affect it too. Mine is rooted stock 6.0.
Beamed in by telepathy.
Still have same problem
I still can't connect my M9 to my PC. Still have slow charge message come up and no option to connect to PC. My work around has been transferring files using WiFi. However, now I need to do a presentation using scrcpy and will probably have to get a new phone. I'm tmepted not to buy HTC again. Pretty frustrating and no fix found on the internet...
since more than 6 months the PC or Laptop doesn't recognize the P605, I tried to change the microusb port, tried different USB ports, PCs with no luck.
When I'm connecting the tablet to PC the tablet will charge but nothing appear in the device manager, no detection at all.
appreciate your help guys solving it, I bought Tab S3 but I still like the old fellow more
No detection, so the thing's completely inert when plugged in?
When I plugged in my Note to my 3.0 USB laptop, out comes 'Device not recognised' in the taskbar, and that's it. However, it all works well when I plug it to a computer with USB 2.0 running XP/7. A brief search shows something about incompatible default/microsoft's driver with old(er) devices on USB 3.0.
As you've mentioned several attempts above including a hardware change, I believe the problem lies with software somewhere.
I have the same problem and get an "error 43" message. My Note 5 works fine when plugged in. I must have damaged the port upon changing the battery. I wanted to upgrade to 6.0 but looks like I'm out of luck....unless I can update via update.zip on my P600
Hello,
my new S22 is not visible in device manager so there's no way to enable file transferring, only charging works when connected to my Windows 10/11 PC.
Also the "USB for file transfer" notification below is not visible at all for me:
https://imgur.com/rr13tI9
I have tried with 2 different cables and 2 different PC (Windows 10 & 11).
File transferring works fine with S21.
I have tried enabling USB debugging, and installing the latest Samsung USB Drivers from https://developer.samsung.com/android-usb-driver
I have checked the "default USB configuration" is set to "Tranferring files" and *#08080# is set to "MTP + ADB".
Only "Link to Windows" (the problem with this is you can see only 2000 latest photos) and Samsung Dex works.
Is my brand-new phone defective ?
Daimie said:
Hello,
my new S22 not visible in device manager so there's no way to enable file transferring, only charging works when connected to my Windows 10/11 PC.
Also the "USB for file transfer" notification below is not visible at all for me:
https://imgur.com/rr13tI9
I have tried with 2 different cables and 2 different PC (Windows 10 & 11).
File transferring works fine with S21.
I have tried enabling USB debugging, and installing the latest Samsung USB Drivers from https://developer.samsung.com/android-usb-driver
I have checked the "default USB configuration" is set to "Tranferring files" and *#08080# is set to "MTP + ADB".
Only "Link to Windows" (the problem with this is you can see only 2000 latest photos) and Samsung Dex works.
Is my brand-new phone defective ?
Click to expand...
Click to collapse
This may sound stupid, but flip the cable over and plug it in. Yes, I know, it doesn't (or shouldn't) matter which way you plug in a USB-C cable. Not all USB-C cables are created equal.
I've had this happen to me. It wouldn't recognize my phone, but when I flipped it over and plugged it in, it worked.
I had to go through all of my cables to check for this. I tossed the ones that caused this phenomenon. It seemed to be all of my older cables I had purchased when I had a Note 8.
Use adb push and pull
gernerttl said:
This may sound stupid, but flip the cable over and plug it in. Yes, I know, it doesn't (or shouldn't) matter which way you plug in a USB-C cable. Not all USB-C cables are created equal.
I've had this happen to me. It wouldn't recognize my phone, but when I flipped it over and plugged it in, it worked.
I had to go through all of my cables to check for this. I tossed the ones that caused this phenomenon. It seemed to be all of my older cables I had purchased when I had a Note 8.
Click to expand...
Click to collapse
This didn't work. Tried flipping the original USB-cable.
mr.herbert said:
Use adb push and pull
Click to expand...
Click to collapse
The command "adb devices" returns 0 devices.
Daimie said:
The command "adb devices" returns 0 devices.
Click to expand...
Click to collapse
Is USB debugging on?
If so did you grant the computer authorization?
My USB-C -> USB-C stopped being recognized, hade to go with USB-C -> USB for computer to recognize it again. Device is S22 Plus.
Solved! I tried a 3rd cable and it started working.
So my original S22 USB-C cable is faulty, as only the charging works.
Yes, my S22 also works with only few cables (I have tried like 10pcs including completely new ones and like 1/3 is working). Samsung is restricting from using other cables for other purposes then charging. Its not the cable fault. They are working with other phones and charging S22 properly. Its just something between heaven and hell why Samsung is trying to f*ck us and make our daily lives more complicated...
Daimie said:
Solved! I tried a 3rd cable and it started working.
So my original S22 USB-C cable is faulty, as only the charging works.
Click to expand...
Click to collapse
Do you know what brand and model cable you got working?
What specs the proper cable should have? Having the same issue.
Having the same issue. And adb connect <ip>:5555 also refused for my case