Google Pixel XL may overcharge due to Android 8.1 bug (UPDATE)

by Mihail Nikolov / Mar 19, 2018, 9:19 AM

Google Pixel XL may overcharge due to Android 8.1 bug (UPDATE)

If a phone has been on the market for almost two years, it doesn't necessarily mean that all bugs have been eliminated or that it won't ever get new ones. The best example for that has to be the Google Pixel XL, which has been plagued by issues ever since its inception in late 2016. After it got the Android 8.1 update, some users on Reddit have reported their Pixel XL was overcharging, taking more power than it normally should.

The bug occurs when charging the Pixel XL with the supplied charging cable. Reportedly, the smartphone sometimes will pull 25W (9V/2.8A), instead of the supposed 18W (9V/2A). After that, the phone will stop charging in an attempt to regain the normal power delivery. This process can happen couple of times during a charging session and can be spotted if you see the "charging rapidly" notification pop-up on your display multiple times when you plug-in the charger.

The bug has been reported by a user on Google's issue tracker, but the company is yet to tackle it. Overcharging is just one of the many bugs that have been part of the first-gen Pixels' lifespan. Random Bluetooth shutdowns, various audio issues and halo apparitions are the other issues to make up the list of Pixel bugs.

UPDATE: A Google representative has contacted us, saying the bug will be fixed soon. There was also an official response regarding the issue on the forums, and here's what it said:

Thank you for submitting information on this bug. Our engineering team has verified a fix that will be rolling out in the coming weeks to prevent this from occurring.
Tests run by our safety engineers have also confirmed that even if a momentary overcurrent draw of the kind described were to occur in normal-use conditions, it would not pose a safety hazard. In addition, Pixel XL was designed with multiple layers of safety protections to further prevent overheating:

1) the phone input circuit is designed to carry more than the observed level of current;

2) both the battery and the phone have multiple layers of protection to avoid battery and phone overheating and overcharging;

3) the in-box charger, as well as any third party chargers that meet safety industry standards (UL and similar), have overcurrent protection.

John McNulty
Head of Safety and Compliance Engineering for Google Consumer Hardware

source: Reddit via Android Police

Options

9 Comments

1. JohnR

Posts: 135; Member since: Sep 08, 2017

No phone is immune to bugs, especially after receiving updates. Which is why this obsession with fast updates perplexes me. I want STABLE updates, even if they take longer.

posted on Mar 19, 2018, 9:29 AM 10

2. bucky

Posts: 3771; Member since: Sep 30, 2009

As an iOS user, I definitely agree with this.

posted on Mar 19, 2018, 9:40 AM 10

3. Settings

Posts: 2942; Member since: Jul 02, 2014

And that's why faster updates are needed, to let you not suffer from current bugs longer than usual. Wash rinse repeat.

posted on Mar 19, 2018, 9:47 AM 5

8. medtxa

Posts: 1655; Member since: Jun 02, 2014

Pixel bugs happens exactly because Google overworked their developer for the sake of updates not thorough testing for stable experience.

posted on Mar 19, 2018, 10:30 PM 0

4. TechSceptic

Posts: 1156; Member since: Feb 05, 2018

Overcharging a phone can drastically reduce the cycle life of a battery, they should fix this immediatly, or they're going to have a scandal on their hands, like the Apple one. I doubt Google users is going to simply accept a cheaper battery replacement charge as an "apology", they aren't as "loyal" as IOS users.

posted on Mar 19, 2018, 11:35 AM 3

5. NarutoKage14

Posts: 1275; Member since: Aug 31, 2016

You're very right. Apple users have to pay for their "apology" whereas Android users would expect that "apology" to be completely free.

posted on Mar 19, 2018, 12:30 PM 3

6. gamehead unregistered

And here's another issue with this phone

posted on Mar 19, 2018, 1:46 PM 0

7. speedingcheetah

Posts: 75; Member since: Jul 22, 2017

If u use the Google charger and cable you are fine. it has the overcharge smart detections and will activate, thus preventing such overcharging current. Only only at real risk if you use a 3rd party charger, even a PD compliment one. Good ones have the same overcharge detections. Google does not make a 12V car (cig) charger, so that is where the real risk lies, those users who have to charge using a third party charger in car or elsewhere. A workaround, use a lower power charger, one that does not support rapid charge at all and only puts out 1AMP max. Phone will not try to Rapid Charge then. I don't care for rapid charge. Phone easily lasts a whole day, 2 sometimes. I only charge my phone overnight. It has about 6-8 hrs to charge. I wish they would give the user the option to disable Rapid Charge as slower charging is always better and safer for cell battery life. This seems like it would be a big issue, bit Google doesn't seem to think it is. So I am not that worried. The phone has done the few cycles of Rapid charge notifications when first starting even back when I first got the XL and it was on 7.1.1. And such an issue was not reported back then...(or was it?)

posted on Mar 19, 2018, 3:58 PM 3

9. speedingcheetah

The April update does not fix the Pixel XL overcurrent charging issue. Infact. its worse. i see my phone doing its stop and start cycle at least 4 times now. before it was only 2x.