Google Pixel users report experiencing the nefarious Nexus 6P shutdown bug

Once Google Nexus 6P owners started receiving the Android 7 Nougat update, a lot of them reported that their phones would lose all their remaining charge once the battery drops to somewhere below the 30% mark and would turn off until connected to a charger. Initially, this was believed to be a software problem and Huawei said it wouldn't be looking into any possible hardware malfunction, but many people rolled back to Android 6 Marshmallow and said the issue persisted. Just last week, we heard that Huawei has now jumped on board and is working together with Google to find out what causes that “shutdown bug”.

But it seems that the malfunctioning juicebox problem might not be isolated to just one phone. More troubling even — Google's new flagship Pixel phones are said to be exhibiting the same behavior since the last update.

A few Reddit users have reported that their Pixels will sometimes just randomly turn off when the battery charge is between 25% and 35%. The phones in question are the 32 GB and 128 GB variants of the regular Pixel and an unidentified version of the Pixel XL. So far, only a few people are reporting the bug, so there's hope that this could only affect a small batch of lemon phones. We'll keep an ear close to the ground for more information.

Interestingly enough, the iPhone 6s suffers from the very same issue right now — once it drops below 30%, it would either randomly turn off or drain the remainder of its battery in the matter of minutes. Apple has already started a free battery replacement program for certain batches of the 6s handsets, but many believe this might be an issue with iOS 10.2. We still doubt there's a connection between Apple's and Google's phones shutdown problems, but that's an incredible coincidence none the less!

source: Reddit

Related phones

  • Display 5.0" 1080 x 1920 pixels
  • Camera 12.3 MP / 8 MP front
  • Processor Qualcomm Snapdragon 821, Quad-core, 2150 MHz
  • Storage 128 GB
  • Battery 2770 mAh(26h talk time)
Pixel XL
  • Display 5.5" 1440 x 2560 pixels
  • Camera 12.3 MP / 8 MP front
  • Processor Qualcomm Snapdragon 821, Quad-core, 2150 MHz
  • Storage 128 GB
  • Battery 3450 mAh(32h talk time)



1. Mxyzptlk unregistered

I wonder what's causing this issue. Funny how people are quick to say Batterygate for the iPhone 6S but I haven't seen people do the same thing with Google but that's none of my business. *Sips coffee*

2. Tizo101

Posts: 598; Member since: Jun 05, 2015

I guess it might have something to do with the popularity of the phone in question and the standard that it claims from the beginning (like it just works).

5. Jason2k13

Posts: 1469; Member since: Mar 28, 2013

It's popularity... You should know by now that it's mostly just Samsung and Apple that gets most of the hate comments... Watch Kumar give hate comments on Samsung articles but never on other phone brands.

9. sissy246

Posts: 7129; Member since: Mar 04, 2015

Because batterygate is already apples. If someone else uses it ifans will cry that people copied batterygate name.

11. Subie

Posts: 2425; Member since: Aug 01, 2015

This is the first I've heard of the Pixel's doing it too. Give it time, and if the problem gets worse before getting fixed then so will the name calling...

16. JC557

Posts: 1925; Member since: Dec 07, 2011

Asian countries and their piss poor QA? As for some Android fans keeping their heads in the sand, yeah I've seen this too as if Google can do no wrong. I go to a reddit or Google forum where several people bring up the same or similar issues that Google is slow or refuses to fix only to be shouted down by apologists. Currently dealing with a Google Play Services battery draining bulls**t. Some days my Z Force can get 7hrs of screen on time w/ 28 hrs of up time while out and about and then struggle to make 3 hrs SOT in 20 hrs of up time despite staying home most of the day.

21. joey_sfb

Posts: 6794; Member since: Mar 29, 2012

QA issue are not specific to a region. US and European products could also have QC shortcomings As for fanboys, there are fan for every brands especially in the personal electronic segment. Each of us just need to stare at the mirror.

22. cheetah2k

Posts: 2297; Member since: Jan 16, 2011

No issues here with my pixel 128gb and several friends with them either. Sounds like its affecting a certain batch. Definitely not widespread across the board on all phones

3. zenun12

Posts: 205; Member since: Oct 31, 2016

battery issues here.....battery issues there......battery issues everywhere.

10. 47AlphaTango

Posts: 739; Member since: Sep 27, 2015

Easiest solution is to own and use a powerbank. More than that. If you own an iphone, or a samsung flagship phones. Get a powercase!

4. uchihakurtz

Posts: 428; Member since: Nov 12, 2012

one of the perks of being an early bug tester, why I prefer ironed out Android update of manufacturers than getting the latest and greatest right away. Seems like Google's QC Team are still not good.

12. Finalflash

Posts: 4063; Member since: Jul 23, 2013

Well that is why they have rolling updates and so fewer people will be affected with future updates receiving the fixed version.

18. JC557

Posts: 1925; Member since: Dec 07, 2011

Of course that won't stop the silent Google Play Services that updates itself every so often and can create wakelocks.

6. cmdacos

Posts: 4325; Member since: Nov 01, 2016

Another day another pixel issue. Stay away from the first gen is all i read.

7. Valdomero

Posts: 704; Member since: Nov 13, 2012

Gladly my Nexus 5X with Nougat 7.1.1 has no problems whatsoever.

8. gdawilson

Posts: 299; Member since: Jul 21, 2014

Mine too *knock on wood*. I didn't have the smoothest experience running 7.0, but 7.1.1 seems to have smoothed things out.

13. VZWuser76

Posts: 4974; Member since: Mar 04, 2010

Don't have this issue on either my 6p or my Pixel, but I'm starting to see an uptick in reports on the forums. Still not very widespread, but something to keep an eye on.

14. Valdomero

Posts: 704; Member since: Nov 13, 2012

Have you updated to 7.1.1?

15. VZWuser76

Posts: 4974; Member since: Mar 04, 2010

Yes I have.

17. jeroome86

Posts: 2314; Member since: Apr 12, 2012

Probably a hardware issue. Android updates are normally pretty solid.

19. joevsyou

Posts: 1093; Member since: Feb 28, 2015

i rather have my phone blow up then it just dying random on me

20. matistight

Posts: 1027; Member since: May 13, 2009


23. solidsnakeduds013

Posts: 221; Member since: Oct 20, 2010

I have the same problem with my 6P

Latest Stories

This copy is for your personal, non-commercial use only. You can order presentation-ready copies for distribution to your colleagues, clients or customers at or use the Reprints & Permissions tool that appears at the bottom of each web page. Visit for samples and additional information.