I am trying to connect my NVidia Sheild to a powered usb hub with no luck at this point.
Heres what I'm using:
Powered Hub
USB to Ethernet
OTG to USB
Male to Male USB
So I am taking the OTG to USB and connecting it to the Sheild OTG port. From there I have a Male to Male USB connecting the OTG to USB to the Powered usb hub. When I do this I can see that the Sheild's power light is orange which indicates to me that it is getting power and not acting as the USB Host for the Hub?
I did notice when I tried to use an air mouse directly with the OTG to USB it works as it should but not when it's connected to the powered usb hub instead, then nothing works (just charging). Also my ethernet adapter doesnt work via the powered usb hub or the OTG to USB.
BTW this whole physical setup worked just fine (plug and play) with both android MK808 and MK908. I was surprised that the Sheild isnt picking this up as well.
Can anyone tell me if I have incompatable hardware and if so what is compatable? Also I do not have ROOT access to the Sheild...yet, could that be the issue?
Many thanks in advance.
Chris
Ok, so these devices have two USB host sockets hanging out of them on wires. But we also know that there is a "password" to enable USB debugging.
I've tried using a USB-A plug to USB-A plug cable for hooking up USB debugging, but of course, the USB port on the device is in HOST mode.
Anybody know how to tell the USB mode to switch to slave?
I think I'm doing something wrong, the Pixel 2 only works with certain cables, or something else (port defect, OS defect, special drivers needed, etc.). I wanted to transfer some files from my PC (Windows 10) to my phone. I have a USB 2.0 to type-C cable that I plugged in. The phone came up in Windows but the contents of the window were blank. I could not access any contents or view anything on the phone. In Settings under USB I saw it said "charging" so I selected "transfer files" and it disconnected from Windows and reconnected only to go right back to charging. I have locked/unlocked, restarted the phone, tried different USB ports, and nothing works. The only function that works is "charging." When I use the supplied type-C to type-C that came with the phone I can get it to work only if I plug into the computer, then the phone, lock the phone, and then unlock it using my PIN (not fingerprint). I ordered a USB 3.0 to type-C cable to see if that works. Is there something I'm missing on why the phone won't connect with a USB-A to USB type-C cable...except to charge? Drivers or something else?
Also...I've reset the phone once (that didn't work either)...and even tried enabling USB debugging.
Please help. Thanks in advance.
Well...I think I figured it out with more troubleshooting. Apparently, you can't connect this phone to a computer via a USB hub. I was able to get it to work by plugging directly into my computer. I tried it on two different powered USB 3.0 hubs and it didn't work. Not sure why or if there is a way around it for convenience.
I got an Anker OTG hub. It works completely if I connect it to my laptop, however, if I try connecting it to my phone, my USB mouse+keyboard combo (wireless with a receiver) doesn't work. It works with other devices, including my laptop's USB C port, and my old phone's USB C port.
I did turn OTG on prior to connecting anything (I'd love (root) to know to keep it on at all times).
I already ensured they work on other computers through that OTG adaptor, and that a USB storage stick works on this phone through it. In addition to that, HDMI works too (the adaptor also has an HDMI port), and the USB C passthrough passes power successfully, as well. No warp charging, but that is to be expected and that's alright.
I have TWRP and everything. Is there a kernel mod I need? I'd be happy to do whatever's needed.
Maybe OnePlus needs some updates
Even i have latency issus with my midi keyboard
But not with op5t
I don't own any USB-C devices or cables at this time.
I am planning to buy Pixel 3a soon and would like to understand whether it comes with everything I need to connect it to my PC that is 6 years old and equipped with USB-3 Standard A connectors on motherboard. The objective is to transfer files in both directions.
From what I understand 3a comes with USB-C to USB-A adapter in the box. Does it mean I don't need anything extra to connect to PC to transfer files? That is it seems I would plug this adapter to motherboard, then USB-C cable to the adapter, then another end of USB-C cable to the phone. Is this correct?
And if I wanted one-cable solution then this is what I would want: https://www.amazon.com/dp/B01E9W8KY...colid=DAYIUPLW7ZM8&psc=1&ref_=lv_ov_lig_dp_it, right?
JoeSchmoe007 said:
I don't own any USB-C devices or cables at this time.
I am planning to buy Pixel 3a soon and would like to understand whether it comes with everything I need to connect it to my PC that is 6 years old and equipped with USB-3 Standard A connectors on motherboard. The objective is to transfer files in both directions.
From what I understand 3a comes with USB-C to USB-A adapter in the box. Does it mean I don't need anything extra to connect to PC to transfer files? That is it seems I would plug this adapter to motherboard, then USB-C cable to the adapter, then another end of USB-C cable to the phone. Is this correct?
And if I wanted one-cable solution then this is what I would want: https://www.amazon.com/dp/B01E9W8KY...colid=DAYIUPLW7ZM8&psc=1&ref_=lv_ov_lig_dp_it, right?
Click to expand...
Click to collapse
You would need to get a cable like the one in your link to connect to PC.
The adapter it comes with allows you to connect a USB thumb drive to the phone.
kc6wke said:
You would need to get a cable like the one in your link to connect to PC.
The adapter it comes with allows you to connect a USB thumb drive to the phone.
Click to expand...
Click to collapse
Got it, thanks.
kc6wke said:
You would need to get a cable like the one in your link to connect to PC.
The adapter it comes with allows you to connect a USB thumb drive to the phone.
Click to expand...
Click to collapse
I'm pretty sure you could also use it to connect a male to male USB A cable to connect a phone to a computer.
But yea, a USB-A to USB-C cable is the easier option.
Sent from my Google Pixel 3a XL using XDA Labs
If you need to plug it in to your computer yes, you need an additional cable. But for data transfer only just use ftp, no cable need and probably faster
Artim_96 said:
If you need to plug it in to your computer yes, you need an additional cable. But for data transfer only just use ftp, no cable need and probably faster
Click to expand...
Click to collapse
I find adb is far faster for data transfer when it wants to work tbh.
Sent from my Google Pixel 3a XL using XDA Labs
I just got a 3a and can't get the phone to connect to my PC properly for file transfer or adb use despite the phone showing properly on device manager and having had it work fine with an S9, G7 power and even a previous 3a. I'm lost.
carnivalrejectq said:
I just got a 3a and can't get the phone to connect to my PC properly for file transfer or adb use despite the phone showing properly on device manager and having had it work fine with an S9, G7 power and even a previous 3a. I'm lost.
Click to expand...
Click to collapse
I don't have the 3a but I saw in one of the videos there is a setting in the phone that defines what to do when phone is connected to a computer. One is "Charge Only", another something like "File Transfer" (and I think there are others). Could it be that you have it set it to "Charge Only"?
carnivalrejectq said:
I just got a 3a and can't get the phone to connect to my PC properly for file transfer or adb use despite the phone showing properly on device manager and having had it work fine with an S9, G7 power and even a previous 3a. I'm lost.
Click to expand...
Click to collapse
It's likely one of three things.....
1) You haven't installed the latest ADB drivers (although this is unlikely if you had it working with this computer and another Pixel 3a).
2) As already noted, by default you have to manually change the connection type to "Data Transfer" anytime you plug your phone into a computer. When you plug the phone into the computer, you should see a new "Android System" notification on your phone. Open that notification and change the connection type from "Charge Only" to "Data Transfer".
3) To use ADB, you need to make sure you have turned on Developer Settings and turned on "USB Debugging" in the developer settings.
If all of these things are correct, then I would "Revoke USB debugging authorizations" in the developer settings and then plug the phone back into the computer. You will see a new authorization popup on the phone which you need to accept.
Skittles9823 said:
I'm pretty sure you could also use it to connect a male to male USB A cable to connect a phone to a computer.
Click to expand...
Click to collapse
Not really. There's no such thing as a Type-A to Type-A USB cable in USB 2.0. You can probably find a cable with USB 2.0 connectors on both ends, but they violate the spec, and can't properly be called "USB." (there's lots of crap like that around) In USB 3.1, there's a very specialized one "defined for operating system debugging and other host-to-host connection applications."
The adapter included with Pixels is a USB "On-The-Go" one, it tells the phone act as a USB host (so it can connect to a thumb drive, keyboard, USB headset, etc.). Per the spec "This cable assembly is defined for direct connect to a USB device (e.g., a thumb drive). System functionality of using this adaptor assembly together with another USB cable assembly is not guaranteed." Having said that, Google does provide the adapter to allow the Pixel to connect to another Android phone using its A to micro-B "charging" cable in order to copy data when changing phones.
To have the phone appear as a drive on a PC, the PC is the host. You need a USB Type-A to Type-C cable to connect to the Pixel.
mike.s said:
Not really. There's no such thing as a Type-A to Type-A USB cable in USB 2.0. You can probably find a cable with USB 2.0 connectors on both ends, but they violate the spec, and can't properly be called "USB." (there's lots of crap like that around) In USB 3.1, there's a very specialized one "defined for operating system debugging and other host-to-host connection applications."
The adapter included with Pixels is a USB "On-The-Go" one, it tells the phone act as a USB host (so it can connect to a thumb drive, keyboard, USB headset, etc.). Per the spec "This cable assembly is defined for direct connect to a USB device (e.g., a thumb drive). System functionality of using this adaptor assembly together with another USB cable assembly is not guaranteed." Having said that, Google does provide the adapter to allow the Pixel to connect to another Android phone using its A to micro-B "charging" cable in order to copy data when changing phones.
To have the phone appear as a drive on a PC, the PC is the host. You need a USB Type-A to Type-C cable to connect to the Pixel.
Click to expand...
Click to collapse
Thanks for the info.
Sent from my Google Pixel 3a XL using XDA Labs
sic0048 said:
It's likely one of three things.....
1) You haven't installed the latest ADB drivers (although this is unlikely if you had it working with this computer and another Pixel 3a).
2) As already noted, by default you have to manually change the connection type to "Data Transfer" anytime you plug your phone into a computer. When you plug the phone into the computer, you should see a new "Android System" notification on your phone. Open that notification and change the connection type from "Charge Only" to "Data Transfer".
3) To use ADB, you need to make sure you have turned on Developer Settings and turned on "USB Debugging" in the developer settings.
If all of these things are correct, then I would "Revoke USB debugging authorizations" in the developer settings and then plug the phone back into the computer. You will see a new authorization popup on the phone which you need to accept.
Click to expand...
Click to collapse
Turns out there was a heavy Windows update pending upon restart. The thing bugs me about them constantly so I usually ignore them. I restarted and let it do it's thing for 4 hours (damn Windows lol) and after it restarted the phone for file transfer, as well as adb started working correctly.