Hi all,
Pixel 3a, trying to connect to my desktop (Win10, fully updated) to transfer files for a backup.
USB C from the pixel to USB A on one of the back USB ports in the computer (3.1 gen 2, 3.0, 2.0) - charging but not recognized to transfer files. Not even showing on the pixel the option to select what the connection is for.
USB C from the pixel to USB C on the back USB port (3.1 gen 2) - the same thing, charging but not recognized.
Here's the funny bit. Same cables, same computer, FRONT USB ports (I have 1 A and 1 C, both USB 3.1 gen 1) recognized and working, able to switch between charging and file transfer, no problem.
The back USB ports on the computer work for anything else I connect to, microphone, mouse, keyboard, webcams... (there is data transfer, not just power)
Any ideas would be appreciated. Any information you need about the system would be supplied. Basically Ryzen 5 3600, MSI B550 A-pro mobo. I flashed the bios a month ago, there's nothing new there.
Thanks!
Update, MSI support instructed me to flash to the latest bios (A.72) and check again. I'll do it during the weekend and update.
Still open to hearing any suggestions or advice about this.
Thanks,
Well, I promised you this one's a doozy!
Flashed to the latest Bios, and now
Partial success.
Front USB A: Charging & Recognizing the google pixel phone
Front USB C: Charging & Recognizing the google pixel phone
Back USB 3.1 Gen 2 Type A: Charging & Recognizing the google pixel phone
Back USB 3.1 Gen 2 Type C: Charging, BUT not recognizing the google pixel phone
All other A type USB ports (3.0, 2.0/1.1): Charging & Recognizing the google pixel phone
Any idea why the Type C on the back panel won't recognize the phone while all the rest do? (including the type C on the front)
Thank you for your help
Leo
Related
The title was supposed to say C-C
As in the title really; When I plug the phone into my laptop (Lenovo ThinkPad L450) with a C-C cable, the following happens.
Some key points in trying to diagnose the issue:
Used three different C-C cables including the one that comes in the box
Tried a USB 3.0 A-C cable on the same laptop, works perfectly
Plugged a HTC 10 into the same port with the same cables, allows fast charging and 3.1 transfer rates
I have been into 'Developer Settings' and changed 'Select USB Configuration' to 'Charging',
Can anyone help, or is anyone experiencing a similar issue? I really don't want to have to RMA this.
for charging i cant really help but for data transfer try enabling usb debugging and getting the right drivers for the pixel 2. also connect as MTP for data transfer.
havent tried any of this myself as i dont need to transfer my files yet and theres no roms either but let me know if it works.
good luck!
I have kind of the same issue - while mine charges, it doesn't recognize the phone for MTP at all. Tried both the cable that came with the device, and the 5x cable I've been using since February. My husband's 5x is recognized, my Pixel 2 isn't. Have to use a USB-C to USB-A cable to do any data transfers.
This ticks me off, because I have 2 USB-C ports on my laptop. One that's a USB-C/Thunderbolt port (which always worked with the 5x), and the other that's just USC-C with USB 3.0 capability, which has my USB hub plugged into it. The hub won't work with the C/TB port, and now neither will the Pixel 2. So I either have to grab my C to A cable to load music and use ADB, or plug into the hub's port, losing my external keyboard, mouse, external HDD, printer, and Wacom tablet.
vido.ardes, is your C port Thunderbolt as well?
vido.ardes said:
The title was supposed to say C-C
As in the title really; When I plug the phone into my laptop (Lenovo ThinkPad L450) with a C-C cable, the following happens.
Some key points in trying to diagnose the issue:
Used three different C-C cables including the one that comes in the box
Tried a USB 3.0 A-C cable on the same laptop, works perfectly
Plugged a HTC 10 into the same port with the same cables, allows fast charging and 3.1 transfer rates
I have been into 'Developer Settings' and changed 'Select USB Configuration' to 'Charging',
Can anyone help, or is anyone experiencing a similar issue? I really don't want to have to RMA this.
Click to expand...
Click to collapse
I posted my problem on the Google Product forums, and got this answer. It worked for me.
"Nikhil Rastogi said:
Hi all,
I just faced this issue. Connected my Pixel to my PC, no indication of connection either on PC or on Phone, except that the phone was charging. Even the file explorer on Windows 10 wasn't displaying Pixel as a connected device.
I found a solution, I hope it works for you all,
Go to Settings->Apps & notifications->App info->Tap 3 dots in top right corner->Tap 'Show system'.
Then find 'External storage' and 'Media storage' apps in the list and clear cache and data for both these apps. Restart your phone and wait 5-10 minutes before connecting the phone to your PC.
After connecting, the phone should now show 'USB connected for charging', as it did in Nougat. You can tap that notification and select file transfer."
Click to expand...
Click to collapse
These are the exact steps I did on the Pixel 2:
Settings>Apps & notifications>See all 125 apps>3 dot menu>Show System>Media Storage>Storage>Clear Data (this got the cache, as well)>Back>Back>External Storage>Storage>Clear Data.
Then I plugged it into the C/TB port, and the computer made the "USB Connected" noise, and "USB Debugging" came up in my phone's notifications (yes, I've enabled developer options and USB debugging there.) I'm then able to go into Settings>Connected Devices>USB and choose Transfer Files.
I just cleared the cache, not data for both and it worked.
krelvinaz said:
I just cleared the cache, not data for both and it worked.
Click to expand...
Click to collapse
Now that you can connect to your PC, is there any way I could get you or some other kind soul, to pull the system/framework folder and system/priv-app/SystemUIGoogle folder for me? The system.img files cannot be unpacked at this time. Every method tried gives "List index out of bounds" error.
Danariel said:
I posted my problem on the Google Product forums, and got this answer. It worked for me.
These are the exact steps I did on the Pixel 2:
Settings>Apps & notifications>See all 125 apps>3 dot menu>Show System>Media Storage>Storage>Clear Data (this got the cache, as well)>Back>Back>External Storage>Storage>Clear Data.
Then I plugged it into the C/TB port, and the computer made the "USB Connected" noise, and "USB Debugging" came up in my phone's notifications (yes, I've enabled developer options and USB debugging there.) I'm then able to go into Settings>Connected Devices>USB and choose Transfer Files.
Click to expand...
Click to collapse
Thanks for the advice, but unfortunately no change for me. I fear I may have to RMA this, which I really don't want to have to do.
I have found on my other devices, that if I reboot to recovery mode, my computer can then read the file folders in my device.
This appears to be an issue with the laptop, not the phone, as it works on another PC with a USB-C port
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.
I have a custom designed & built USB hub board, where multiple such boards have been working with multiple android devices for multiple years. One thing I can always do with a new USB device is plug my board into the Android device, then plug a USB thumb drive into one of my boards hub inputs, and then from the Android device use Google Files to view the contents of the "disk" (the USB thumb drive). Note that most times I must first go to Settings, turn on Developer Options, and change the Default USB Configuration to allow File Transfer.
Now I'm trying it out with the very inexpensive B130DL. I've changed Default USB Configuration to allow File Transfer. I plug a USB thumb drive into my hub board in advance, and I plug my usb hub board into the B130DL in advance. Then I power up the usb hub board. SUCCESS... a moment later the BL130DL shows that USB trident icon at the top. From Google Files I'm able to view the contents of this disk. UH OH... a moment later I get a message that the usb device has been ejected. (I believe this message comes from Google Files. If I'm not currently running Google Files, I don't see this eject message. I just see the USB trident icon go away.)
Note that the B130DL is [disliking] my USB hub, specifically. If I plug in both B130DL and USB thumb drive, then it takes about 6.5 seconds from powering on the hub board to when the B130DL shows the USB trident icon. Then it takes another roughly 9 seconds for the USB trident icon to go away again. If I do the same test, plugging in the USB thumb drive 3 seconds after powering on the hub board, then the same things happen based on timing from powering on the hub board. Also, once ejected, removing and replacing the USB thumb drive doesn't repeat the test. I must remove and replace hub board power to repeat the test. In essence, it seems like the B130DL is ejecting the hub and thus everything on it. Meanwhile, a separate USB OTG cable works indefinitely when plugged into the B130DL. Note as well that this very same usb hub board works great and continuously when plugged into a different phone (Samsung A01, Android 11). I've been swapping between phones (B130DL and A01) repeatedly to make sure I haven't broken my hub board in any way. Also, In the past, this usb board has worked with Android 9 and 10. The B130DL is Android 10.
So what about the B130DL is it that causes it to first work with my usb hub board and then eject it? Any good ideas? Again, note that the problem is NOT intrinsically with my custom usb hub board, because that works great with many other Android devices. It's this specific B130DL that has the problem. True, it might be customized by BLU to refuse a number of USB OTG devices. Or it might be customized by BLUE to do something else. This is my question.
Thanks!