I can't figure this out... I have an ASRock Motherboard Motherboards Z370 EXTREME4 motherboard with a USB-C output on it and using Win10. I've tried using the P2XL USB-C to USB-C cord to connect my phone to the computer to transfer files. I get nothing that shows up on the phone, yet everything is updated and working on the computer.
Any ideas?
Also as a side note, I have a dozen or so regular USB-C cords. Only 1 actually works just connecting it to a USB port on the computer. Some don't recognize anything, some will recognize the phone and let me transfer files only to have it drop the connection and reconnect to the phone. The 1 cord that actually does work, works as expected. Also this same issue happened on my old PC as well. Only 1 cord works with this phone and everything is updated. I've tried other computers with same issue.
I've also noticed I can only charge my phone with a couple of 120v USB outlets. Lots of them won't charge my phone, even though the phone says it's charging.....just never gains any charge.
I have a pretty similar issue with a C to C connection using my Razer Blade. I have this happen with the OEM cable and a couple of non-OEM C to C cable. I can't remember ever having an issue with my HTC 10 using a C to C, or when I use a USB A to C cable with this phone. While I'm not entirely convinced it's not my USB C port on my laptop, more evidence points to it being my Pixel rather than the port.
It's not the biggest issue for me because it's not a constant hindrance and I can usually get any transfer to finish.
Think I've been down this road... No fix. No idea what is happening or why.
The only option I have is to use my 1 cord to transfer. I usually am transferring several gigs at a time. I never had this issue with same cords for my original pixel XL.
What gets me is I even has issues using us chargers even. They say it's charging but never gain any charge.
Kind of thinking my phone has been defective
Wiped it yesterday and tried again with the OEM USB-C to USB-C cable, no luck even recognizing the phone, even to charge. I did however use a USB-A to USB-C 3.0 cable that didn't ever work originally and it copy 15gb of music without an issue.
I'll keep testing, as well as test it on the chargers that didn't work previously. I will also contact ASRock as I believe possibly my motherboard's port for the C-to-C not to work with the phone. It's not the worst thing not being able to use it, as I'm happy I can finally transfer files at 3.0 speeds now! SO MUCH quicker copying files back onto the phone than when I pulled them off!
Related
Sometimes my phone will not charge when connected to the wall or my computer. The problem usually goes away on it's own, but when I need to charge I generally need to charge.
Sometimes I cannot access my phone via USB on PC either.
Only with data to and from the computer. No charging issues at all.
I've never had issues when plugged in to computer (USB). I frequently have issues when plugging into wall charger, but I think I have a bad cable. Phone will recognize charger connect, sit for a second, and lose the connection. Charging stops while cable is in. I bought a cheap cable on-line for the wall charger. I guess you get what you pay for....!
I have issues with usb connnect to computer since flashing cm6 8/13 nightly. Will not charge or mount usb.
Restoring back to 8/11 seems to fix issue but can't seem to get any newer nightlys to work or rc2.
Sent from my PC36100 using XDA App
michaelvibe said:
Sometimes my phone will not charge when connected to the wall or my computer. The problem usually goes away on it's own, but when I need to charge I generally need to charge.
Sometimes I cannot access my phone via USB on PC either.
Click to expand...
Click to collapse
Kind of sounds like a loose connector. I bought some micro USB cables from monoprice and the size of the connector was just a tad smaller than the plug for the phone. So if the cable wasn't plugged in and propped up in a certain way, the phone wouldn't charge. I just bought some new cables from monoprice (the ferite core ones) and problem solved.
I guess when this happens to you, wiggle the cable a little and then hold it for a few seconds at a certain angle and see if it starts charging... if it does then you know you need a new cable.
I was having similar issues and with my sd card permission issues I simply uninstalled my usb drivers and my removable disc drivers for the phone on the computer I think there was like 3 sets and haven't had an issue since.
I went to use a portable charger with USB C connector (Anker) and my Pixel XL did not indicate that it was charging. I had another cable that is USB A to C. When I plugged that into the USB A port it worked.
Thinking that the issue was either with the USB C port on the charger or with the cable I did some playing around when I got home. No combination of USB C cables or chargers would charge the phone. Any USB A to C worked.
This morning, just for kicks, I shut down and restarted the device. And..... all is as it should be on all cables/chargers. Very strange.
Has anyone else experienced this or is able to offer a possible explanation?
Hey kenorian,
No new info, but there is a thread discussing this issue with a small handful of people.
https://forum.xda-developers.com/pixel-xl/help/charge-boot-t3535269
For me, Google RMA'd me a new device, except for a single instance, the charging issue has not returned in a few weeks with the new device.
Hi,
Got my Pixel2XL, love it!
But 1 strange thing, I had the Nexus 6P before and a few cables some that I got in it's package and some that I bought (USB-A to USB-C) all work both for charging and for data transfer (more important for me adb and fastboot) except 1 cable, let's call it ORANGE (since it's color) that only worked for charging.
When I connect my Pixel2XL none of those cables work for data, only for charging! the PC doesn't recognize anything in device manager and the phone doesn't show any option and only charging. that is regardless of the cables or ports and even tried on another PC with same cables. same with USB debugging enabled and disabled.
BUT, when I connect ORANGE it works! now the strange part is that some of my cables are high quality and even pretty good companies like Choetech (if I wrote correctly) and the ORANGE, is some lame cable from Aliexpress.
So I wonder if maybe there are few standards that are supported/not supported on the Pixel2XL? or how do I buy now cables? same was when I tried an older USB-A to MicroUSB with an USB-C adapter.
I couldn't find any official data by Google.
Please assist, Thanks.
No Issues here
dimiboy said:
Hi,
Got my Pixel2XL, love it!
But 1 strange thing, I had the Nexus 6P before and a few cables some that I got in it's package and some that I bought (USB-A to USB-C) all work both for charging and for data transfer (more important for me adb and fastboot) except 1 cable, let's call it ORANGE (since it's color) that only worked for charging.
When I connect my Pixel2XL none of those cables work for data, only for charging! the PC doesn't recognize anything in device manager and the phone doesn't show any option and only charging. that is regardless of the cables or ports and even tried on another PC with same cables. same with USB debugging enabled and disabled.
BUT, when I connect ORANGE it works! now the strange part is that some of my cables are high quality and even pretty good companies like Choetech (if I wrote correctly) and the ORANGE, is some lame cable from Aliexpress.
So I wonder if maybe there are few standards that are supported/not supported on the Pixel2XL? or how do I buy now cables? same was when I tried an older USB-A to MicroUSB with an USB-C adapter.
I couldn't find any official data by Google.
Please assist, Thanks.
Click to expand...
Click to collapse
Sorry to hear that Bro.
I am using all the same cables I used with my 1 XL and can connect to both my win7 and win 10 machines
Try USB 2.0 port and Spigen cable
Edit: https://www.amazon.com/dp/B00ZE36WH8/ref=cm_sw_r_cp_apa_sXhaAb7Z5356G
Icyou said:
Try USB 2.0 port and Spigen cable
Edit: https://www.amazon.com/dp/B00ZE36WH8/ref=cm_sw_r_cp_apa_sXhaAb7Z5356G
Click to expand...
Click to collapse
Checked now in USB2 and USB3 ports with some of my cables, same
Have you rebooted the Pixel?
When I first got mine and I set it up and I finally wanted to copy over my ringtones, my laptop and PC wouldn't detect the Pixel. It would make a ding sound then go back to Charging. I then rebooted for the first time and then it worked.
Ok, seems that my "high quality" cables wasn't so good.
It seems that 1 of them wasn't choetech and the other that I though came with the Nexus 6P was something I got from the store since in those days they provided the n6p with a different charger (they couldn't deliver US plug chargers than)
after I found the box of the n6p I found the short USB-A to USB-C cable and it works both for data and for charging!
Thanks for all the help and everything, it was my mistake and a big learning curve of why cheap cables won't work.
I still wonder how does the phone know which one is good or not.
Last week I wanted to plug in my phone into our shop's stereo, using the the official included USB-C to 1/8th headphone adapter. I plug in the phone, fire up my music, but the audio continues out of the phone's speakers.
So I unplug and replug in the adapter, and the aux cable a couple of times with no luck, even restarted the phone to see if that would do it.
At that point I thought that somehow the adapter was damaged, so I ordered a replacement (making sure to get one with a DAC [sidenote: **** any manufacturer that makes you not only have to get an adapter for headphones, but makes you have to get a SPECIAL adapter])
No dice with the new adapter.
I went a couple of days not really worrying about it, the phone charges just fine, like it always has, so I didn't think it was a hardware issue. I thought it was just bad luck with these stupid, terrible, superfluous, awful adapters.
But today I had to pull a file off the phone to my computer, using multiple known good Type-C to USB-A 3.0 cables.
Phone says it's charging, but I didn't get the notification to select USB mode, and USB ADB debugging never showed up.
Windows is constantly making the device connected, disconnected sounds, and device manager is showing me an "Unknown USB Device (Port Reset Failed)"
Is it possible that somehow the data connections on the port on the phone are damaged, without it affecting power delivery? I have no idea how that would work, Like I said, it charges just fine, and all my cables feel pretty secure when plugged in, there's no play or wobble and I don't know what to do to troubleshoot it further.
You can try to clean the port
I have the same issue. Ive requested a replacement aux dongle from Google and still no go. It charges fine, connects to my computer fine adb, data transfer etc all work, only for music it continues to play from the speaker even when connected.
Yes it's possible for the phone to get power but have no data connection it's happend to my Nexus 6p I paid for the insurance so I had to pay the deductible to replace I have had some data issues with the pixel 2 xl but always seems to come back after a few days could just be a dirty connection since I work construction and some times gets very dirty.
But I'd be careful of what cables you buy when they are usb a to c but seem to have no issues with c to c
I have the same problem and are trying to work with Google for a fix. I have tried everything and they are pretty useless. I am now requesting a new device as I'm still under warranty.
I noticed that when I connect the phone via an USB-C cable to my computer or to an USB stick, the connector only works in one direction, like in the old USB-B days. When I rotate the plug it no longer works reliable.
Haven't faced such an issue. You should try another cable and if the issue is persistent, maybe the USB connector itself is having issues and you should reach out to Nokia service.
I tried several cables and eventually got in contact with retailer and received a new device. On the night before the new device arrived, I couldn't really charge the phone. Hopefully this won't happening again.