Related
Hey guys, I probably have a pretty unusual question or rather observation. Sometime yesterday night when I connected the Galaxy Nexus to the power outlet it started to make a crackling noise. I immediately disconnected it but it already smelled like burnt plastic. As you can believe I was pretty shocked! Trying to turn on the phone worked flawlessly though, so I though, OK might have been my outlet and tried two different ones. Still to no avail, the phone works but won't charge.
I turned it off for the night and waited until the morning to try to connect it to my computer (thinking maybe it's the plug that's broken) and reset it to factory default. Big mistake! Windows pops up with a warning telling em that it detected a power surge on one of my USB ports, resulting in my phone still not charging, the USB port being broken (won't recognize my USB key anymore), and and the Micro-USB connector emitting some smoke after I unplug it from the Nexus.
Now, enough storytelling. Maybe you guys can help me with the mountain of questions I have after this episode:
A) Really, what happened here? I don't think it has something to do with the software side of it, can it? (eg Battery overloaded?) Then I would guess more people would have had the same problem... I'm running AOKP M3 and Franco Kernel 3.0.08-M1.
B) Did anyone have the same problem?
C) I guess it's unfixable from a software standpoint, so my only option would be to send it back to Amazon and hope they replace it. Any other ideas? I bought it at Amazon.de (Germany) but due to it having AOKP Rom and Franco Kernel installed getting a replacement might be difficult.
C) How do I get my USB port functioning again? It's a new notebook but I don't want to send it back for repairs as I bought it in Hong Kong (I have an international warranty though.) and need it to write my Thesis.
Update: Uninstalled and re-installed the USB drivers, that fixed the USB port.
Thanks for your time and hopefully help!
A confused GN user.
majar said:
Hey guys, I probably have a pretty unusual question or rather observation. Sometime yesterday night when I connected the Galaxy Nexus to the power outlet it started to make a crackling noise. I immediately disconnected it but it already smelled like burnt plastic. As you can believe I was pretty shocked! Trying to turn on the phone worked flawlessly though, so I though, OK might have been my outlet and tried two different ones. Still to no avail, the phone works but won't charge.
I turned it off for the night and waited until the morning to try to connect it to my computer (thinking maybe it's the plug that's broken) and reset it to factory default. Big mistake! Windows pops up with a warning telling em that it detected a power surge on one of my USB ports, resulting in my phone still not charging, the USB port being broken (won't recognize my USB key anymore), and and the Micro-USB connector emitting some smoke after I unplug it from the Nexus.
Now, enough storytelling. Maybe you guys can help me with the mountain of questions I have after this episode:
A) Really, what happened here? I don't think it has something to do with the software side of it, can it? (eg Battery overloaded?) Then I would guess more people would have had the same problem... I'm running AOKP M3 and Franco Kernel 3.0.08-M1.
B) Did anyone have the same problem?
C) I guess it's unfixable from a software standpoint, so my only option would be to send it back to Amazon and hope they replace it. Any other ideas? I bought it at Amazon.de (Germany) but due to it having AOKP Rom and Franco Kernel installed getting a replacement might be difficult.
C) How do I get my USB port functioning again? It's a new notebook but I don't want to send it back for repairs as I bought it in Hong Kong (I have an international warranty though.) and need it to write my Thesis.
Update: Uninstalled and re-installed the USB drivers, that fixed the USB port.
Thanks for your time and hopefully help!
A confused GN user.
Click to expand...
Click to collapse
A) Sounds like a short circuit somewhere. My guess would be the connector or close to it.
B) I certainly didn't but I'm sure it's happened to someone.
C) Unroot and Relock and send it back to Samsung if Amazon doesn't take it back. I'm not sure about their return policy since it's a cellphone that is under warranty. May also depend how long ago you bought it.
The more I think about it I wonder if it's just the USB cable... Since you said the smoke came from the Micro-USB connector... Plug it back into the computer without the phone and see if you get the USB power surge thing again. There may just be a short in the cable.
Of course checking it with a multimeter would be safer, do you have one of those?
Or do you have another Micro-USB you can try charging the phone with?
chjade84 said:
C) Unroot and Relock and send it back to Samsung if Amazon doesn't take it back. I'm not sure about their return policy since it's a cellphone that is under warranty. May also depend how long ago you bought it.
Click to expand...
Click to collapse
The problem is that I can't even unroot it since it is not being recognized by the computer (and I get the power surge warning). I will try with the new cable, and then send it back even if it works. might give me problems further down the line if I don't.
chjade84 said:
The more I think about it I wonder if it's just the USB cable... Since you said the smoke came from the Micro-USB connector... Plug it back into the computer without the phone and see if you get the USB power surge thing again. There may just be a short in the cable.
Of course checking it with a multimeter would be safer, do you have one of those?
Or do you have another Micro-USB you can try charging the phone with?
Click to expand...
Click to collapse
I don't have a different cable (or multimeter) near me at the moment but will give an update as soon as I do. I didn't get the power surge warning when I just plugged in only the cable, but as there is no source that could draw power that seems likely to me.
P.s.: Just bought it in january so generally sending it back shouldn't be a problem - if I can get it unrooted.
majar said:
The problem is that I can't even unroot it since it is not being recognized by the computer (and I get the power surge warning). I will try with the new cable, and then send it back even if it works. might give me problems further down the line if I don't.
Click to expand...
Click to collapse
Yes I kind of forgot about that...
majar said:
I don't have a different cable (or multimeter) near me at the moment but will give an update as soon as I do. I didn't get the power surge warning when I just plugged in only the cable, but as there is no source that could draw power that seems likely to me.
Click to expand...
Click to collapse
Well that's "good" in that we know the cable isn't shorted. I thought maybe some pins or wires were touching inside the cable that would cause a short (+5VDC and GND) even without the cable being plugged into anything.
So it does look like the fault is in the phone somewhere... And that could be just about anything.
Being that it's Amazon they probably will just replace it and not even bother with checking for it being rooted - especially since you can say it's smoking. As far as I know only the carriers will turn on the phone and look it over (not to mention most Amazon employees wouldn't know root it it reached out of the phone and smacked them across the face). Other 3rd party stores just mark it as defective and put it in a box to send back. I'm not sure how Amazon's return process works though.
I had several problems with my EVO (speakers mostly) and had it rooted when I took it in. They just fixed it anyway and even told me they liked what I had done with it a few times.
Hey, just to give an update I didn't get a specific explanation but Amazon replaced the battery, cable & charger. Now its working again. No problems with it being rooted, they even left rooted but installed stock android & kernel.
I'm currently having this problem, i called google, and they transferred me to samsung. And their department that handles this issue is closed on weekends
peacebomber said:
I'm currently having this problem, i called google, and they transferred me to samsung. And their department that handles this issue is closed on weekends
Click to expand...
Click to collapse
any update? i'm having this problem aswell. my phone wont charge through the wall charger but will when connected to a computer... but when it's connected to the computer it says that my usb device (phone) has malfunctioned.
because of that "malfunction" i cant revert back to stock everything and relock everything to get it repaired with bell mobility.
marrrio_ said:
any update? i'm having this problem aswell. my phone wont charge through the wall charger but will when connected to a computer... but when it's connected to the computer it says that my usb device (phone) has malfunctioned.
because of that "malfunction" i cant revert back to stock everything and relock everything to get it repaired with bell mobility.
Click to expand...
Click to collapse
when i sent them my phone i couldn't bring back to stock software but i still shipped it out either way, i actually got an email from samsung today saying a component has been replaced and being shipped out back to to me, so i guess they fixed it with it being rooted, so when i receive it ill let you know
Well I got back my phone today and its charging again. But they restored my phone back to factory setting. So I lost all my pics and phone didn't restore previous apps etc but oh well as long as they fixed it and no questions asked I'm happy
Sent from my Galaxy Nexus using xda app-developers app
Is anyone else experiencing this issue? Every time I plug a USB cable into the phone restarts.
I have to send my device back. It seems like the factory charger burned the USB port.
Started experiencing this yesterday after ARM Core update. Noticed whenever I use the anker usb-c cable in the car, the phone would reset and charge. If I used the google provided charger at home/office, phone seems to stay on without any issues.
SuperEd said:
Started experiencing this yesterday after ARM Core update. Noticed whenever I use the anker usb-c cable in the car, the phone would reset and charge. If I used the google provided charger at home/office, phone seems to stay on without any issues.
Click to expand...
Click to collapse
Its AR not ARM. And that app is only related to augmented reality stuff. Don't think that would cause any issue.
You might want to check the voltage and current output of your car charger btw
Thanks. I'm merely speculating as "some" recent update is causing this issue.
The car charger is an Anker 24w (link here: https://www.amazon.com/gp/product/B00B8M4IMK/ref=oh_aui_search_detailpage?ie=UTF8&psc=1) always plugged into the 2.9a. I've been using this since I received the P2XL without any issues until the above.
I can confirm I have the same issue with the car charger causing reboots but wall charger works fine. Problem didn't exist until about a week ago.
https://productforums.google.com/forum/#!topic/phone-by-google/4rkbD8ad4DA more experiences posted on google product support.
I have the same problem. After testing several chargers and cables I put the phone in fastboot mode. Funny that it works in fastboot mode and not the OS.
I couldn't figure out what caused the problem. The only thing we all have in common is that we all used a car charger
This happens to my 2 XL if I use the official pixel charger... Otherwise other charges work fine
1 out of 4 times it happens in my car when hooking up to android auto. Glad im not the only one.
equlizer said:
1 out of 4 times it happens in my car when hooking up to android auto. Glad im not the only one.
Click to expand...
Click to collapse
Check your charging port does it look burned? I just sent my phone back to Google for a replacement
State.of.mind said:
Check your charging port does it look burned? I just sent my phone back to Google for a replacement
Click to expand...
Click to collapse
my usb ports are fine and ive tried different cords. It started after the last android auto update.
This just happened to me! 2018 Jeep grand cherokee (uconnect) android auto working fine and dandy until Today.
Now I can't even get windows to recognize my device, adb devices, and fastboot devices while on the bootloader does not reconize it either.
Charging works fine but no more USB data or android auto
---------- Post added at 11:34 AM ---------- Previous post was at 11:03 AM ----------
thatsricci said:
This just happened to me! 2018 Jeep grand cherokee (uconnect) android auto working fine and dandy until Today.
Now I can't even get windows to recognize my device, adb devices, and fastboot devices while on the bootloader does not reconize it either.
Charging works fine but no more USB data or android auto
Click to expand...
Click to collapse
I've tried pluggin/unplugging a bunch with different cables... I get it to fully recognize and let me adb/fastboot properly or copy files in windows... It would seem the USB port is going bad.
I will message support and see what they say!
thatsricci said:
This just happened to me! 2018 Jeep grand cherokee (uconnect) android auto working fine and dandy until Today.
Now I can't even get windows to recognize my device, adb devices, and fastboot devices while on the bootloader does not reconize it either.
Charging works fine but no more USB data or android auto
---------- Post added at 11:34 AM ---------- Previous post was at 11:03 AM ----------
I've tried pluggin/unplugging a bunch with different cables... I get it to fully recognize and let me adb/fastboot properly or copy files in windows... It would seem the USB port is going bad.
I will message support and see what they say!
Click to expand...
Click to collapse
After chatting support they had me turn on developer tools, enable usb debugging and then reset all authorizations. After that it seems to be recognized again. Something with the April update they said may require a reset of the usb settings in this manner... seems to be working again for me.
thatsricci said:
After chatting support they had me turn on developer tools, enable usb debugging and then reset all authorizations. After that it seems to be recognized again. Something with the April update they said may require a reset of the usb settings in this manner... seems to be working again for me.
Click to expand...
Click to collapse
It's sporadic at best, but working more consistently. I assume somethin minor may have damaged the usb-c port on the phone... I can at least consider it usable again for now, but no 100% :\
Happened to me 3 days ago (phone rebooting when plugging a USB cable and audio dongle not getting detected) I tried rebooting it many times but it didn't help. When I turned off the phone completely and turned it back on, everything came back to normal...
Any update on this? This exact problem just stated happening to me tonight and I've had been using the same chargers for over a year. You have the steps they gave you on resetting the USB settings via USB debugging?
Sent from my Pixel 2 XL using Tapatalk
When this happened with mine they determined that the charging port was damaged and had to get a replacement. Could also be small debris in charging port possibly?
Yea I went thru Google support and it seems like their only answer is to RMA and get another phone.
Sent from my Pixel 2 XL using Tapatalk
I noticed that my Pixel 2 XL suddenly stopped connecting to the car via the USB cable (Android Auto). When I connect the cable, the phone charges but nothing happens on the monitor. When I try the same cable with my OG Pixel XL it works fine. I also tried connecting my Pixel 2 XL to my PC, and it didn't work either. Windows makes a sound, and then I get an error message saying "USB device not recognized. the last usb device you connected to this computer malfunctioned." Nothing shows up on the phone screen and I can't change the USB-connection type. I tried factory resetting the phone but I still have the same issue. I have tried many different cables, and all work with the OG Pixel XL but not the Pixel 2 XL.
Also the time estimate for how long a full charge will take is gone as well. It only says "charges rapidly" when I connect it to the charger that came with the phone.
Is my charging port damaged? Can I fix it somehow? I tried carefully cleaning it with water and a tooth brush and drying it, but still have the same issue. Could it be corrosion? Should I try using PRF TCC on the charge port?
YaKoStar said:
I noticed that my Pixel 2 XL suddenly stopped connecting to the car via the USB cable (Android Auto). When I connect the cable, the phone charges but nothing happens on the monitor. When I try the same cable with my OG Pixel XL it works fine. I also tried connecting my Pixel 2 XL to my PC, and it didn't work either. Windows makes a sound, and then I get an error message saying "USB device not recognized. the last usb device you connected to this computer malfunctioned." Nothing shows up on the phone screen and I can't change the USB-connection type. I tried factory resetting the phone but I still have the same issue. I have tried many different cables, and all work with the OG Pixel XL but not the Pixel 2 XL.
Also the time estimate for how long a full charge will take is gone as well. It only says "charges rapidly" when I connect it to the charger that came with the phone.
Is my charging port damaged? Can I fix it somehow? I tried carefully cleaning it with water and a tooth brush and drying it, but still have the same issue. Could it be corrosion? Should I try using PRF TCC on the charge port?
Click to expand...
Click to collapse
Cable could be going bad or it's missing the 100ohm resister the phone just went into protection it will work again at some point but I recommend getting a new cable direct from Google
Tired of buying ones that should have the resister but still not having quick charge work and issues like that.
Sent from my Pixel 2 XL using Tapatalk
YaKoStar said:
I noticed that my Pixel 2 XL suddenly stopped connecting to the car via the USB cable (Android Auto). When I connect the cable, the phone charges but nothing happens on the monitor. When I try the same cable with my OG Pixel XL it works fine. I also tried connecting my Pixel 2 XL to my PC, and it didn't work either. Windows makes a sound, and then I get an error message saying "USB device not recognized. the last usb device you connected to this computer malfunctioned." Nothing shows up on the phone screen and I can't change the USB-connection type. I tried factory resetting the phone but I still have the same issue. I have tried many different cables, and all work with the OG Pixel XL but not the Pixel 2 XL.
Also the time estimate for how long a full charge will take is gone as well. It only says "charges rapidly" when I connect it to the charger that came with the phone.
Is my charging port damaged? Can I fix it somehow? I tried carefully cleaning it with water and a tooth brush and drying it, but still have the same issue. Could it be corrosion? Should I try using PRF TCC on the charge port?
Click to expand...
Click to collapse
Check for these options, see if it got changed to charging only.
Unfortunately, I don't have these options available. Like I said, nothing happens. The phone only goes into charging mode. I've tried a bunch of different cables that works with my OG Pixel.
in developer options check to see if under "select USB configuration" you have it set to charging only.
I have also started to notice a weird charging issue with my Pixel 2 XL. First, I thought that it was the original cable - ordered a replacement via Google Support but today I started noticing a very similar issue. Basically, only 1 way of the reversible cable can charge my device, so if I turn it upside down it won't charge at all - no matter which of the sides I plug into it. When it's plugged in normally, it'll charge for a few seconds then off and on again - all of this at a very fast speed, so it'll keep my screen on at all times. I've noticed this as I've left my phone on the bed for half an hour to charge it then spot that my screen was on for like 5 minutes - when I picked up the phone, it was pretty warm and would charge and disconnect and then charge again - in a loop.
Meanwhile, if I plug in my Anker (a third party) USB-C cable, it will charge just fine - no matter which of the reversible sides I try it with. So having checked that, I thought it was the wall plug going crazy or something, so I plugged the USB-C cable into my computer (Thunderbolt 3) and it was the same issue - it would charge normally only with one of the sides, so when I turned it upside down, nothing would happen.
Also, what's weird is that the Pixel cable, both the old and the replacement one works fine with the Galaxy S9, but not my Pixel - so I assume it's a hardware (charging port) issue with my device, so tomorrow the UK team should get in touch with me to discuss my options :/
skimminstones said:
in developer options check to see if under "select USB configuration" you have it set to charging only.
Click to expand...
Click to collapse
Tried doing it. No change.
I tried using some contact spray to see if it's because of rust/oxidation of the pins in the charging port, no change.
I still think it's an hardware issue though. Like I said, not even factory resetting the phone fixed it. I'll just live with not having android auto and USB, not super important for me anyway. Thanks guys.
I wonder if there is a defect in the charging ports of these. I just got a replacement because mine wouldn't charge on any c to c charger (I have two factory chargers). It would only charge when connected to a computer with an A to C, or using the same cable type to a wall charger. It was really weird... This is also the second or third post in the last week or two I've seen about something pertaining to the port.
gettinwicked said:
I wonder if there is a defect in the charging ports of these. I just got a replacement because mine wouldn't charge on any c to c charger (I have two factory chargers). It would only charge when connected to a computer with an A to C, or using the same cable type to a wall charger. It was really weird... This is also the second or third post in the last week or two I've seen about something pertaining to the port.
Click to expand...
Click to collapse
There probably is .. I've read a lot of posts about people having similar issues.
Ok... So something weird just happened. I connected my phone to the charger as usual, and suddenly I could see the "estimated time until full charge" notification again, for the first time in weeks! I tried disconnecting it, and connecting it to my computer and I could browse the images on my phone! I thought my issue was fixed, so I disconnected it and connected it to the outlet again.. And now it is the same as before again. No estimate until full charge and windows says the device malfunctioned... What the hell happened there for a couple of minutes?
Pixel 2 XL and having the identcal issue as OP.
Phone charges only in car and computer. Once for just a few minutes the Android Auto just starter working and on PC I was briefly able to access phone storage. Then nothing. Went to dealer thinking it was car USB port but the technicians Samsung plugged in and Android Auto started right up.
Swapped cables, same isssue.
Wondering if I should even bother with factory reset or just pursue repair?
My Pixel 2 XL is from Verizon, anyone have any experience with warranty repairs?
(btw, checked in the developer sections and usb is set to MTP)
YaKoStar said:
I noticed that my Pixel 2 XL suddenly stopped connecting to the car via the USB cable (Android Auto). When I connect the cable, the phone charges but nothing happens on the monitor. When I try the same cable with my OG Pixel XL it works fine. I also tried connecting my Pixel 2 XL to my PC, and it didn't work either. Windows makes a sound, and then I get an error message saying "USB device not recognized. the last usb device you connected to this computer malfunctioned." Nothing shows up on the phone screen and I can't change the USB-connection type. I tried factory resetting the phone but I still have the same issue. I have tried many different cables, and all work with the OG Pixel XL but not the Pixel 2 XL.
Also the time estimate for how long a full charge will take is gone as well. It only says "charges rapidly" when I connect it to the charger that came with the phone.
Is my charging port damaged? Can I fix it somehow? I tried carefully cleaning it with water and a tooth brush and drying it, but still have the same issue. Could it be corrosion? Should I try using PRF TCC on the charge port?
Click to expand...
Click to collapse
Same exact problem here with XL2. The phone will charge anywhere with any cable but can not access phone storage from laptop and Android Auto no longer works. It worked fine last week, now no go. I called Google as I bought phone from them and they are are sending a replacement to me which will be here this Monday.
Has to be hardware issue as my XL works perfectly.
Hey i have the exact same problem. Cannot access the phone with usb cable. The problem for me is, that i have Lineage OS installed without root and it installed its own recovery, so i'm basically unable to go back to stock. The google support told me that because it's not the original software on the phone its out of warranty and i should just reflash the factory image, but i already told them that as long as i can't access the phone with usb i can't do that. Will see what i can do else. Maybe i just have to pay to get it fixed. I'm very sad about that.
Also same here. I contacted support and signs indicate that this is a warranty issue.
No USB data for me anymore. Charging only. The interesting thing is although the USB-C is symmetrical only one of the two possible orientations is actually charging the phone.
Same problem just happened with my pixel 2 XL. I believe this was some kind of a weird update that Google did last night that screwed everything up. I've tried hard factory reset as well as resetting the phone changing cables Etc. Nothing works
I was one of those people that cursed out Google regarding this particular issue. I was getting windows 10 errors "device not recognized", the USB-C audio adapter didn't work for my car, not did the audio adapter, so I was gonna chalk it up to the fact I got a faulty phone, that was until....
I had searched around and saw some articles on how the USB-C port was a dust collector. I used s toothpick to knock out some of the lint that was trapped inside the port, nothing changed.
Just about to RMA my phone and I decide to try one last attempt.
1) find the thinnest cardboard / oaktag you can find that can fit in either side of the port without having use force ( if you have an old Google fi data sim card cardboard laying around, it works perfect )
2) Get some rubbing alcohol and dip about 2 to 3 cm of it in the alcohol
3) Gently move the cardboard against the connectors in a left right motion, too and bottom side, when you hit the corners drag the cardboard up to remove any additional dust or lint. I ended up extracting more lint and dirt that rolled off both sides of the connectors
I let the USB-C connector dry and cleaned again in the same method.
Now when I plug in my device it's recognized by my PC, all USB-C peripherals work, even my SanDisk USB-C flash drive.
Before you quit after all your efforts, give cleaning the port a shot. You can't really do any damage because the phone is moisture resistant , and alcohol evaporates quick.
It's very easy for dirt to get lodged in the port, and when you plug in your phone to charge, it's just going to compress and smear the dirt all over the connectors ( possibly fuse the dirt on the contacts ). This happens with all USB-C ports in similar situations.
If you guys are still reading this , give it a shot if you haven't returned your units.
ugh .... just happened to mine. While the bootloader is unlocked. hopefully i can clean or replace the port.
Anony58 said:
I have also started to notice a weird charging issue with my Pixel 2 XL. First, I thought that it was the original cable - ordered a replacement via Google Support but today I started noticing a very similar issue. Basically, only 1 way of the reversible cable can charge my device, so if I turn it upside down it won't charge at all - no matter which of the sides I plug into it. When it's plugged in normally, it'll charge for a few seconds then off and on again - all of this at a very fast speed, so it'll keep my screen on at all times. I've noticed this as I've left my phone on the bed for half an hour to charge it then spot that my screen was on for like 5 minutes - when I picked up the phone, it was pretty warm and would charge and disconnect and then charge again - in a loop.
Meanwhile, if I plug in my Anker (a third party) USB-C cable, it will charge just fine - no matter which of the reversible sides I try it with. So having checked that, I thought it was the wall plug going crazy or something, so I plugged the USB-C cable into my computer (Thunderbolt 3) and it was the same issue - it would charge normally only with one of the sides, so when I turned it upside down, nothing would happen.
Also, what's weird is that the Pixel cable, both the old and the replacement one works fine with the Galaxy S9, but not my Pixel - so I assume it's a hardware (charging port) issue with my device, so tomorrow the UK team should get in touch with me to discuss my options :/
Click to expand...
Click to collapse
I had this exact same problem. I had never heard of anyone else having the issue. Both the original charger that came with the phone and a replacement from Google had the issue but the chargers I got with Nexus 5X phones worked fine.
During the same time period I also had issues with the phone only detecting the 3.5mm adapter one way or not at all. Others had reported this issue.
At some point recently, as randomly as it seemed to stop working (charger and 3.5mm adapter) both started working again.
jimv1983 said:
I had this exact same problem. I had never heard of anyone else having the issue. Both the original charger that came with the phone and a replacement from Google had the issue but the chargers I got with Nexus 5X phones worked fine.
During the same time period I also had issues with the phone only detecting the 3.5mm adapter one way or not at all. Others had reported this issue.
At some point recently, as randomly as it seemed to stop working (charger and 3.5mm adapter) both started working again.
Click to expand...
Click to collapse
Indeed, recently it has started working again, although I am still waiting for an original response from Google (been waiting for half a year and really doubt they'd come to a conclusion after all....)
I had contacted them and they still told me to wait... Really disappointed about the way this serious issue was handled and it is still being handled.
Anyways, everything seems to be working out of blue, that's what matters.
Anony58 said:
Indeed, recently it has started working again, although I am still waiting for an original response from Google (been waiting for half a year and really doubt they'd come to a conclusion after all....)
I had contacted them and they still told me to wait... Really disappointed about the way this serious issue was handled and it is still being handled.
Anyways, everything seems to be working out of blue, that's what matters.
Click to expand...
Click to collapse
The best guess I have is that the issue was caused by some bug in an update (the April or May update if my timeline is correct) and was fixed in the November Update.
Now I have a new issue that stated with the Pie update. Music metadata no longer shows up on my car's audio system when playing over Bluetooth. Many people are experiencing the issue. There is a work around but it's annoying.
I'm certain that this is a software issue, because it happened out of nowhere and the phone barely two weeks old,I only charge it on the provided charger,I don't have warranty bc I bought it as a reseller,I'm thinking of installing miui.eu to see if it starts to fast charge again,because I can't wait hours for it to charge.
The problem may be in the charger even when it is new.
You can try factory reset. How version do you have (EEA Stable ROM V10.2.9.0.PFBEUXM)?
https://mirom.ezbox.idv.tw/en/phone/grus/
Try to push the end of the cable further into the charger.
vecino said:
The problem may be in the charger even when it is new.
You can try factory reset. How version do you have (EEA Stable ROM V10.2.9.0.PFBEUXM)?
https://mirom.ezbox.idv.tw/en/phone/grus/
Click to expand...
Click to collapse
I did reset It three times already :/ and i on the version that you said
Im thinking of flashing the stock rom,is It possible with a locked bootloader?
Yes Mi Flash (fastboot) need unlocked bootloader. But you can install stock non fastboot version from https://c.mi.com/thread-2265065-1-0.html. I don't know where you are from, but I would use http://bigota.d.miui.com/V10.2.9.0.PFBEUXM/miui_GRUSEEAGlobal_V10.2.9.0.PFBEUXM_432d8a9116_9.0.zip
Try another charger too.
vecino said:
Yes Mi Flash (fastboot) need unlocked bootloader. But you can install stock non fastboot version from https://c.mi.com/thread-2265065-1-0.html. I don't know where you are from, but I would use http://bigota.d.miui.com/V10.2.9.0.PFBEUXM/miui_GRUSEEAGlobal_V10.2.9.0.PFBEUXM_432d8a9116_9.0.zip
Try another charger too.
Click to expand...
Click to collapse
Did everything i could with a locked bootloader,this is pathetic...
Edit: With a 2.1A normal charger i got 900ma,its for sure a bug right?
Have you tried:
1. A different USB A-C cable - sometimes minor cable damage can cause a low charge throughput
2. A different charger & cable completely
3. A different socket in the house
mwarner said:
Have you tried:
1. A different USB A-C cable - sometimes minor cable damage can cause a low charge throughput
2. A different charger & cable completely
3. A different socket in the house
Click to expand...
Click to collapse
Yes i have tried
Wow, so I'm not the only one with that issue. For me it started about month after receiving the device. Quick charge stopped working along with USB connection to PC. But surprisingly USB connection in TWRP worked fine.
I pushed and pull the plug several times and tried to move it a bit right and left and the issue was gone for about two weeks.
Within those 2 weeks quick charge was working every time I connected charger. Then suddenly it stopped working on 27 July. No updates made, the same cable and charger.
I already tried 3 different chargers and cables and it still doesn't work. I will try to flash stable MIUI in fastboot this weekend to bring it back to factory state.
maciek90 said:
Wow, so I'm not the only one with that issue. For me it started about month after receiving the device. Quick charge stopped working along with USB connection to PC. But surprisingly USB connection in TWRP worked fine.
I pushed and pull the plug several times and tried to move it a bit right and left and the issue was gone for about two weeks.
Within those 2 weeks quick charge was working every time I connected charger. Then suddenly it stopped working on 27 July. No updates made, the same cable and charger.
I already tried 3 different chargers and cables and it still doesn't work. I will try to flash stable MIUI in fastboot this weekend to bring it back to factory state.
Click to expand...
Click to collapse
I think the device is kind of thinking its at 90% and naturally slows down the charge
To flash miui via fastboot i Will need a unlocked bootloader right?
Have you tried usb connection? For me it doesn't work. Nothing happens after connecting it to PC.
maciek90 said:
Have you tried usb connection? For me it doesn't work. Nothing happens after connecting it to PC.
Click to expand...
Click to collapse
Im going to try It tomorrow and Will Tell you
Tried a usb connection today and it was connected and recognized with zero problems,still no fast charge tho...
Okay so i did a fastboot install of the rom and its the sane,so i Just gave up...
My "Quick-charging" is also slower on 10.0.3.3 than on 10.0.3.1. Although i can see the "circled flash" icon while charging, but the charging power only reaches 8W instead of 17W before (also my USB-Meter is showing, that the QC3.0 protocol is used during charging, but as i said only at 8W). Should be a software bug.
piaggiorider said:
My "Quick-charging" is also slower on 10.0.3.3 than on 10.0.3.1. Although i can see the "circled flash" icon while charging, but the charging power only reaches 8W instead of 17W before (also my USB-Meter is showing, that the QC3.0 protocol is used during charging, but as i said only at 8W). Should be a software bug.
Click to expand...
Click to collapse
I've got the same thing on MIUI 11.0.6 EU, charging very slow on 10W
Hi, I've been having this problem with my pixel 2 xl that won't recognize any usb-c to usb-c cables. It will only recognize a usb-c to usb-a cable but will keep restarting the moment I plug it in. I've tried many things like restarting, trying to charge while it is turned off, booting into safe mode, and even updating to the Android Q beta (hoped they would've fixed it then), but nothing seems to work. I'm confident that it's a software issue since there would be random glitches where the original charger would actually work, but every other time it doesn't.
Also, I'm actually considering switching to a custom software. I'm thinking since the software is the issue, maybe it might help to fix it. Has anyone ever experienced this issue as well?
Clean the usb port on the phone
siggey said:
Clean the usb port on the phone
Click to expand...
Click to collapse
That's the very first thing I did
siggey said:
Clean the usb port on the phone
Click to expand...
Click to collapse
That's the very first thing I did. It's not an issue with the port since it works perfectly with a Usb-c to usb-a cable. Just it doesn't fast charge and it constantly reboots with it.
I'm having the exact same prob. I've cleaned my port, tried it in safe mode, and did several resets (soft and hard). I spoke with Google and they offered an exchange since it's under warranty but my glass is cracked so that voids it out until I get it fixed. They said it would restart afterwards? I'm stuck trying to figure out if I want to fix it and do a swap, try different firmware or just get a different phone all together??
I'm having the same issue. Started this week.
Ali7000 said:
Hi, I've been having this problem with my pixel 2 xl that won't recognize any usb-c to usb-c cables. It will only recognize a usb-c to usb-a cable but will keep restarting the moment I plug it in. I've tried many things like restarting, trying to charge while it is turned off, booting into safe mode, and even updating to the Android Q beta (hoped they would've fixed it then), but nothing seems to work. I'm confident that it's a software issue since there would be random glitches where the original charger would actually work, but every other time it doesn't.
Click to expand...
Click to collapse
Your testing methodology is flawed. The restart loop occurs at the P2XL splash screen, which means control of the device is still in the hands of the bootloader. Since the bootloader is outside of Android, Android cannot be the culprit. As a result, neither safe mode nor Android Q would resolve the problem.
Have you attempted moving your data off the device's internal storage and reinstalling a stock ROM using the included flash-all bat with the -w flag present? While we have determined that Android itself isn't the culprit, Google's ROM images also install bootloaders and basebands, either of which could be the source of your issue.
Once a stock ROM from Google is installed, test your device. If the restart loop occurs, then your issue is NOT software, but hardware. So then you'll have to test the hardware. Find a charger from a different device and, using a USB-A to USB-C cable attempt to charge the phone. If the restart loop does not occur with this combination, then you know the P2XL charger is faulty. Otherwise, the charging circuit in the P2XL has malfunctioned and thus service will be required.
Are you all on Android q beta or is this happening to stock non rooted too? I'm on q
FYI, I had this same problem a few months ago and it turned out this is a relatively common hardware issue on Pixel 2 XL.
It usually starts by occasional failures to charge (original charger), then it becomes more frequent, then you can't charge and find that the only option is an usb-c/usb-A cable (less power involved). Finally every time you plug a cable it restarts the phone.
Did all possible known troubleshooting, cleaned the port, engaged Google remote support, ...
At the end, the conclusion is that sometimes the port gets loose and related wiring becomes unstable.
To fix it, I had to send the phone for a port replacement.
Working fine since then.
Ali7000 said:
Hi, I've been having this problem with my pixel 2 xl that won't recognize any usb-c to usb-c cables. It will only recognize a usb-c to usb-a cable but will keep restarting the moment I plug it in. I've tried many things like restarting, trying to charge while it is turned off, booting into safe mode, and even updating to the Android Q beta (hoped they would've fixed it then), but nothing seems to work. I'm confident that it's a software issue since there would be random glitches where the original charger would actually work, but every other time it doesn't.
Click to expand...
Click to collapse
I had a similar issue after the July update. If I plugged the original charger and cable in the phone turned off. The only way I could charge it was to use a USB-A to USB-C cable with a slow charger (non QC) and the phone had to be off. Did RMA with Google after doing safe boot, reset and other things. They noted the security update as reason so maybe that's the problem?
I have the problem since pie and even though Google accepted to RMA the device at first they then declined to do it because I didn't have the the purchase id of the device.
I'm doing the rma while I can. The more I read about it, the more I think it's due to the faulty fast charging. It might be damaging the charging port and causing these problems. What I find strange is that some other users also started having these problems a week ago like I did.
Ali7000 said:
I'm doing the rma while I can. The more I read about it, the more I think it's due to the faulty fast charging. It might be damaging the charging port and causing these problems. What I find strange is that some other users also started having these problems a week ago like I did.
Click to expand...
Click to collapse
Port overheating may be causing it to become loose. That's my impression due to what happened to me.
Mine started working again. Weird
I just did RMA because of this... The new (refurbished) device is working now....
I edited the post because when I first tested my charger wasn't plugged in and I though that the new device had the same issue... ....:silly:
In any case do RMA..... Before this happened my pixel only charged with one side of the cable connector (any cable) then it magically got fixed and after two weeks it didn't charge with originals chargers (only when it was turned off)... Definitely was something hardware related...