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
Hey folks, I have a N7 with some issues. I'm bashing my head against the wall on this one. I bought a 2nd gen N7 with a broken screen from some crook on eBay. He neglected to discuss it's other problems, however this is what I have. I replaced the screen, but even before doing so I found that a USB OTG mouse was not recognized (it works on my 1st gen), then I tried my little BT keyboard, BT wouldn't pair... Plug the tab into a PC and the PC completely ignores it. No device in device manager, I can even go to the port the tab is on is device manager and it shows nothing, not even current draw. The tablet does however charge on the PC, and it for some reason thinks that it is on AC charging, not USB. I have tried this on several computers with almost identical results. On a PC with USB 3 ports though, device manager sees it, just says that the device is unrecognized and may have a hardware problem.
So, I managed to get it to connect MTP one time by slightly twisting the USB cable. I then determine it must have a bad USB port, so I ordered some SMD USB sockets when I got other parts for a different project. I replaced the USB port tonight, and nothing changed, it is exactly the same. No data, always thinks it's on AC. On a whim I tried USB while in the bootloader, and it installs the fastboot drivers just fine and I am able to send fastboot commands.
After finding this, I figure it has to be something software or firmware related, so I flash it via fastboot back to bone stock. Reboot system and still no data connection, still thinks it's always on AC. I'm about at my wits end with it. I know there are other ways to move data to the tablet, but only having access to ADB via wifi is lameo and I happen to use USB host.OTG a lot.
Does anyone know what I am missing? I'm thinking it has to be something in the firmware at a level deeper than most the roms and images go. The PO is had it unlocked and cleanrom flashed. I have since tried AOKP, stock 4.4.4, now PA.
On a side note, if there is no fixing this SOB, do any of you know which of the flo roms have native wifi ADB? At least that will help...
Thanks,
Jason
No one has any ideas? No one else has had this issue? What it seems to me is that it is stuck in "USB fast charge mode" that's the only reason I can think that it would think it was on AC still even when on USB. I have tried three different kernels though now and enabled USB fast charge then disabled it, but it doesn't help.
Is it possible for someone to have put it in fast charge mode and made it stick regardless of kernel changes?
Just looking for ideas. Thanks folks!
Later,
Jason
I have exactly the same issue as yours! I couldn't connect my N7 via USB to PC. Gave me USB device not recognised error. I even fastory reset it. However, one time I did twist the USB cable and my device was recognised and it seemed to work fine during that day. I also managed to flash Android L developer's preview on top of that. The following day I started getting the same issue and haven't been able to resolve ever since. Even in fastboot, my device doesn't get recognised. It's the most frustrating thing ever!
Yeah, it definitely sucks. I was convinced it was the USB socket since twisting brought it alive that one time. However, I replaced my connector and it is the same. I then took it apart again and inspected all the traces and solder joints near the USB connector. I was still certain that the twisting meant it was a physical problem. It wasn't until much later that I found that fastboot worked.
I have done a ton of research trying to find an answer, but most everyone just pawns it off as a driver problem. I have tried every fix those people have offered, but it is never seen by the PC on USB 2, and only shows up as "device not recognized" on USB3. I have tried several different computers, but today I'm going to try an old XP machine. Several people seem convinced these issues are due to Win7. I'll let you know if I find anything.
Later,
Jason
jacampb2 said:
Yeah, it definitely sucks. I was convinced it was the USB socket since twisting brought it alive that one time. However, I replaced my connector and it is the same. I then took it apart again and inspected all the traces and solder joints near the USB connector. I was still certain that the twisting meant it was a physical problem. It wasn't until much later that I found that fastboot worked.
I have done a ton of research trying to find an answer, but most everyone just pawns it off as a driver problem. I have tried every fix those people have offered, but it is never seen by the PC on USB 2, and only shows up as "device not recognized" on USB3. I have tried several different computers, but today I'm going to try an old XP machine. Several people seem convinced these issues are due to Win7. I'll let you know if I find anything.
Later,
Jason
Click to expand...
Click to collapse
Try flashing 4.4.2 factory image. Maybe it starts working. For me, issues started 4.4.4+. currently I am stuck on Anroid L preview
Quick update, I asked Scott at Asus if he could give us any ideas, he said base don everything I told him that I had tried that it seems likely that it is a hardware problem with the USB board. I'm still not convinced, but the USB board is going to be my last resort.
Other than that, I tried the tab on a win XP computer and XP sees it as "unrecognized device" says that the USB needs unplugged/replugged and if that doesn't work to replace the device... I would think that the data pins are shorted or something, but mine works in fastboot, that is what has me stumped!
I'll try flashing 4.4.2.
Thanks,
Jason
Well, I just flashed back to 4.3.0 which looks to be the original software for this device. It did not behave any differently. I guess I am going to have to look into a new USB board. The things are expensive though, hopefully I can catch a decent used one for a good price. I'll let you all know if I order one and if it solves it.
Later,
Jason
New board is expensive. *sigh*
Yes they are, and I wouldn't trust ebay as far as I could throw it. I would hate to buy a used one and find out it has the same issue. I have another email into Scott asking if it is possible to buy parts direct from ASUS, and if so, what the board might cost. I'll keep you posted.
Later,
Jason
I heard back from Scott at Asus. They do not sell any parts. He suggested eBay... I guess I will start a saved search and see if I can catch one for a reasonable price. I can't see dropping $80 on a USB board. I guess if it doesn't fix it I could resell it... Still is retarded. This will make what this tablet has cost me much more than a brand new one Damn the crooked eBay sellers!!!
Later,
Jason
jacampb2 said:
I heard back from Scott at Asus. They do not sell any parts. He suggested eBay... I guess I will start a saved search and see if I can catch one for a reasonable price. I can't see dropping $80 on a USB board. I guess if it doesn't fix it I could resell it... Still is retarded. This will make what this tablet has cost me much more than a brand new one Damn the crooked eBay sellers!!!
Later,
Jason
Click to expand...
Click to collapse
Oh that's awful! I can't believe they don't sell replacement parts! I guess I have to live with a broken N7. I just hope Google pushes official L release OTA to devices running L preview.
I had a similar issue once. Turned out that MTP mode wasn't selected. Storage >Menu button > MTP should be selected.
Hi everyone!
When I connect my phone to the charger, it doesn't always start to charge the battery. Only about every 10th time it succeeds.
I tried 3 differnd usb cables, all original sony. It's the same with all of them.
I tried to move the cable in the phone, but it's stable. Also if it charges, I can't stopnit by moving the cable.
For me it looks like a software error, as if the phone doesn't allow to charge.
Does anyone have the same problems?
Any idea how to solve this (in best case without wiping the phone)?
Thank you in advance!
This is a recent problem or have you always had it? You think it's software so does it do it with different roms, or have you tried? I read somewhere the usb port on the phone becomes faulty easily, this seems more your cause, if your certain it's not the cable.
Not Charging as Well
My ZL is not charging as well i plug the AC charger and it gets bootloop.
It stop bootlooping after 1 hour and show the charging icon, but it does not charge.
Do you guys think it is the baterry or some issue with the power management.
I tryed to Charge the baterry with and old Universal Battery charger it hold a little power.
The Cell works when i turn it on with the wall charger but show only 1% of battery
Please guys help me with that.
ham5 said:
This is a recent problem or have you always had it? You think it's software so does it do it with different roms, or have you tried? I read somewhere the usb port on the phone becomes faulty easily, this seems more your cause, if your certain it's not the cable.
Click to expand...
Click to collapse
I don't think it's a hardware problem. I used 3 different cables, all original sony. Sometimes they work, sometimes not. I'm using USB otg a lot (got my videos and some mp3 on a stick), never had problems with usb connection.
I didn't have those problems for a long time, but I don't remember any special apps I installed in the last few weeks.
Didn't try any custom roms yet, I'm very satisfied with my current setup (except for the charging problem ). I'm using latest stock with google crap and bloatware uninstalled.
Hopefully the lollipop update is coming soon. If it's not too buggy I will give it a try.
SO yeah, I've seen where people have had software issues causing this on the Note 8, and S8 models, is it a bug that crept into the S9 as well? The tech at the Sprint store verified the cleanliness and dryness of the port, thinks it's the port, and they won't have parts to fix it for probably a month or so. I REALLY don't want to send it in to be fixed, so I bought a couple wireless chargers.
jporter12 said:
SO yeah, I've seen where people have had software issues causing this on the Note 8, and S8 models, is it a bug that crept into the S9 as well? The tech at the Sprint store verified the cleanliness and dryness of the port, thinks it's the port, and they won't have parts to fix it for probably a month or so. I REALLY don't want to send it in to be fixed, so I bought a couple wireless chargers.
Click to expand...
Click to collapse
It it showing constantly or only when a cable is plugged in? If it's with a cable, have you tried other cables? I had my phone give me that message earlier today when plugging in an incompatible hub. The hub wasn't even connected to anything.
Have you checked with your wife?
jporter12 said:
SO yeah, I've seen where people have had software issues causing this on the Note 8, and S8 models, is it a bug that crept into the S9 as well? The tech at the Sprint store verified the cleanliness and dryness of the port, thinks it's the port, and they won't have parts to fix it for probably a month or so. I REALLY don't want to send it in to be fixed, so I bought a couple wireless chargers.
Click to expand...
Click to collapse
Have you tried to reboot the phone? I'm not kidding.
Let me know
DeadlySin9 said:
It it showing constantly or only when a cable is plugged in? If it's with a cable, have you tried other cables? I had my phone give me that message earlier today when plugging in an incompatible hub. The hub wasn't even connected to anything.
Click to expand...
Click to collapse
All the time. It has a popup with sound when you plug it in. The rest of the time, it's just a notification in the tray.
spampa said:
Have you tried to reboot the phone? I'm not kidding.
Let me know
Click to expand...
Click to collapse
Yeah, tried rebooting, wiped cache, power down all the way, multiple times. Tried plugging the cable in while booting. It looks to be charging while plugged in and powered down.
So, the message went away, and it would charge with 2 different chargers, normal speed, not fast charge. Would not work with a charger I have here at home. None are Samsung chargers, but all are QC 3.0, which will report as fast charging on the phone. Then today it charged fast in the truck, and the one at home works, but only slow speed.
I'm not going to stress over it as long as the fast wireless charging keeps working. The battery life is more than enough to get me through a day, and I'm ordering stuff to integrate wireless chargers into the vehicles.
Thanks for reading and trying to help!
jporter12 said:
I'm not going to stress over it as long as the fast wireless charging keeps working. The battery life is more than enough to get me through a day, and I'm ordering stuff to integrate wireless chargers into the vehicles.
Thanks for reading and trying to help!
Click to expand...
Click to collapse
I probably missed to ask before, but are you sure you are using the original cable, together with the original power charger?
As stressed by @DeadlySin9 the problem may be the cable. Try other cables.
spampa said:
I probably missed to ask before, but are you sure you are using the original cable, together with the original power charger?
As stressed by @DeadlySin9 the problem may be the cable. Try other cables.
Click to expand...
Click to collapse
Yeah, I had tried the original cord and charger. whatever it was effected the phone before even plugging it in. The message would be there in the notifications, then plugging the cable in would set off an "alarm" telling me to unplug it and let it dry.
A couple weeks later and it is working just fine, charging with pretty much any cord, and charger. Ugh. I hope it stays that way! LOL At least Sprint DID give me a pretty good discount on a 2 pack of wireless chargers, which is what I use most of the time, now.
jporter12 said:
Yeah, I had tried the original cord and charger. whatever it was effected the phone before even plugging it in. The message would be there in the notifications, then plugging the cable in would set off an "alarm" telling me to unplug it and let it dry.
A couple weeks later and it is working just fine, charging with pretty much any cord, and charger. Ugh. I hope it stays that way! LOL At least Sprint DID give me a pretty good discount on a 2 pack of wireless chargers, which is what I use most of the time, now.
Click to expand...
Click to collapse
Thumbs up!
So, I've had this problem with my new Galaxy s9 as well. Here's the specifics - this only happens IF the phone dies from running out of power. If I let the battery drain on accident, I plug in the device...new cord/charger, original cord/charger, doesn't matter...and it shows the charging symbol for just a second, and then warning there's moisture in the charging port. There's not... If I set the phone on top of a wireless charging pad for a few mins, it charges just fine.
All I have to do is get 3 - 4 % so I can power on the device and get to the home screen. If I can get to the home screen, I can plug the phone in with the cord/charger and no problems.
I just did a warranty replacement because this problem is real annoying. I don't let the phone run out of power often, but sometimes when I'm traveling for work or camping with scouts, it happens. So, before I sent my old phone back for the warranty swap, I let the new phone run out of power and then tried to plug it in. Same error!!
If anyone has this problem follow this trick. "connect the charger half to the charging port." that is it. works fine to me..
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...