• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

7.1.1 from google: how is your battery life&new features

@12321, I'm very sorry to hear that you've had a poor experience with Google supporting your 6P.

It's important to remember that despite Google's marketing, the Nexus devices are not Google devices. Yes, they are born out of a partnership, but they are wholly designed and built by the manufacturer. The hardware would have been all-but-final before Huawei even pitched their concept for the Nexus 6P to Google. Google would have worked with Huawei to tailor the software to the hardware in a Googly way, but it's still a Huawei device - with Huawei hardware.

In fact, one of the driving causes for Google to change things up with last year's Pixel phones is reported to have been a desire to take more control (and, thus, responsibility) for devices bearing their branding.

You'll notice one of these phones has a Google logo on the back, and the other clearly displays the manufacturer at the bottom:
pixel-xl-nexus-6p.jpg


As a Huawei device, the 6P is covered by Huawei's standard warranty policy which, in the US, covers the phone for "a period of 12 months from the date of purchase." Since Google isn't the device manufacturer, they are legally unable to impose a different warranty for the devices - but, as the retailer, they can offer replacement at their discretion for devices sold by them.

This might be like Amazon selling the Samsung Galaxy S 15 Pro+ and offering different replacement options than Samsung's standard warranty and return policy. Amazon is free to offer exchanges outside of the manufacturer's warranty period - but they can't force Samsung (or Best Buy, or Verizon) to match that policy.

The Pixels are different. Those phones were designed and spec'd out entirely by Google. They then handed the blueprints to an OEM (HTC, in this case) and told them "build this" - the same way that Apple gets Foxxcon to build their devices. This isn't a partnership like the Nexus devices were - this is HTC being relegated to contractor status. Google owns the entire product, the entire process - and, as a result, takes full responsibility for handling warranty claims.

You can see this difference yourself by comparing Google's warranty information page for the Nexus 6P (where the customer is advised to contact Huawei directly for devices which weren't purchased from the Google Store or Project Fi)) versus that for the Pixel XL (which applies to phones purchased from Google or authorized retailers).

I know it doesn't help anyone currently having problems with their Nexus 6P, but it's an important distinction that I think needs to be made - and as such it would be silly to write off the Pixel line simply because Huawei is bad at handling warranties (an observation that can be made about other Huawei devices as well).
 
@12321, I'm very sorry to hear that you've had a poor experience with Google supporting your 6P.

It's important to remember that despite Google's marketing, the Nexus devices are not Google devices. Yes, they are born out of a partnership, but they are wholly designed and built by the manufacturer. The hardware would have been all-but-final before Huawei even pitched their concept for the Nexus 6P to Google. Google would have worked with Huawei to tailor the software to the hardware in a Googly way, but it's still a Huawei device - with Huawei hardware.

In fact, one of the driving causes for Google to change things up with last year's Pixel phones is reported to have been a desire to take more control (and, thus, responsibility) for devices bearing their branding.

You'll notice one of these phones has a Google logo on the back, and the other clearly displays the manufacturer at the bottom:
View attachment 118218

As a Huawei device, the 6P is covered by Huawei's standard warranty policy which, in the US, covers the phone for "a period of 12 months from the date of purchase." Since Google isn't the device manufacturer, they are legally unable to impose a different warranty for the devices - but, as the retailer, they can offer replacement at their discretion for devices sold by them.

This might be like Amazon selling the Samsung Galaxy S 15 Pro+ and offering different replacement options than Samsung's standard warranty and return policy. Amazon is free to offer exchanges outside of the manufacturer's warranty period - but they can't force Samsung (or Best Buy, or Verizon) to match that policy.

The Pixels are different. Those phones were designed and spec'd out entirely by Google. They then handed the blueprints to an OEM (HTC, in this case) and told them "build this" - the same way that Apple gets Foxxcon to build their devices. This isn't a partnership like the Nexus devices were - this is HTC being relegated to contractor status. Google owns the entire product, the entire process - and, as a result, takes full responsibility for handling warranty claims.

You can see this difference yourself by comparing Google's warranty information page for the Nexus 6P (where the customer is advised to contact Huawei directly for devices which weren't purchased from the Google Store or Project Fi)) versus that for the Pixel XL (which applies to phones purchased from Google or authorized retailers).

I know it doesn't help anyone currently having problems with their Nexus 6P, but it's an important distinction that I think needs to be made - and as such it would be silly to write off the Pixel line simply because Huawei is bad at handling warranties (an observation that can be made about other Huawei devices as well).

When my Nexus 6P was running Marshmallow 6.0, it worked perfectly. Best device I ever owned. As soon as I installed Nougat 7.0, my battery began draining quickly and the device began shutting off randomly. Other people experienced similar issues, as well as boot looping - but only after installing Nougat 7.0. The hardware isn't the problem. Google's Nougat 7.0 update ruined thousands of Nexus 6P devices.

I disagree with your statement that Huawei is bad at handling warranties. When an issue is as widespread as this one with the same common denominator, how can any rational person hold Huawei responsible? Why should Huawei be held responsible for fixing thousands of devices that worked perfectly until Google's Nougat 7.0 update was installed?

I understand that Huawei manufactured the phone. The fact remains, it is known as a Google Nexus 6P, not a Huawei Nexus 6P. If Google is going to market the device as a Google phone even though it is manufactured by another company, if they are going to call it a Google Nexus 6P, and if they are going to sell it through their website, they should at the very least share some responsibility if there are issues with the phone.

When the issue has been shown to be caused by Google in thousands of cases, Huawei should not be held accountable. Google should be.

Google had two choices on how to handle this situation:

1) Google can ignore the issue, and if pressed, legally claim that they didn't manufacture the phone, are not legally responsible to fix the issue, and wash their hands of the situation that has screwed thousands of their customers.

2) Google can acknowledge that they caused the issue and state that although they may not be legally responsible to fix the issue, they want to do right by their customers by fixing the issue, upgrading customers to a comparable device, or recalling the device and offering refunds.

Unfortunately for thousands of Nexus 6P owners, Google has chosen the former.

Clearly, Google is aware of the problems that this issue has created, evidenced by the link you provided that they are trying to do everything in-house and be more like Apple. Unfortunately, this doesn't help thousands of Nexus 6P owners who have no recourse, after spending up to $650 on their ruined Google Nexus 6P flagship devices.

I find it humorous when so many people reply in threads like this bashing Apple and the iPhone, yet Google is trying to be more like them. Clearly Apple is doing something right. Google is learning, but it's a shame that they don't mind screwing thousands of their customers in the process.
 
Last edited:
Update from today. Read the comments at the end of the article. NOT FIXED.

http://www.androidpolice.com/2017/04...1-2-changelog/

The comments below by Middlefinger hit the nail on the head and resonated loudly with me:

Middlefinger • 18 hours ago
The number of bugs in Android just lately is unacceptable, and exactly why OEMs dont update as quickly as some would like. If this was pushed to all phones immediately there would be hundreds of millions all shutting down randomly.

Google puts out a half finished product, gets everyone else to fix it, then blames the OEMs for being 'slow' to update.

Francisco Franco • 16 hours ago
Every software on Earth has bugs. It gets worse when the entire phone has software from a dozen different vendors. Even the iPhone has weird bugs and Apple controls the device's hardware & software stack.

That generalization is stupid and uninformed.

Middlefinger • 9 hours ago
So why are OEM devices more reliable than googles own? I realise all software has bugs, but Google rushes out poor quality software, whereas the OEMs actually seem to spend time testing theirs.

Ive done the whole Nexus thing, and im never going back. The hardware was poor quality, the software buggy. Im sticking to slower updated, but reliable OEM devices now. I would rather be an entire version behind Googles latest if it actually worked properly.

You want to know what's really stupid and uninformed? That Google knows best, that AOSP based devices are the way to go and that having the latest version of Android instantly is desirable.

Felonious Monk • 8 hours ago
A big hearty amen to that.
 
GOOGLE NEXUS 6P BATTERY EARLY SHUTOFF AND BOOTLOOPING – CLASS ACTION INVESTIGATION

I filled out the form at the first link below, and a few hours later I received a call from attorney Jessica L. Titler. Attorney Titler asked me to tell her about the issues I experienced with my Nexus 6P, and how Google and Huawei responded to my requests to get a satisfactory resolution. Attorney Titler then informed me that her law firm, Chimicles & Tikellis LLP, will be filing a class action lawsuit today before midnight or on Monday, naming Google and Huawei as defendants.

Any Nexus 6P owners who have experienced rapid battery discharge, random/early shutoff, or bootlooping, and have not received a satisfactory resolution from Google or Huawei are encouraged to fill out the form at this link:

https://chimicles.com/google-nexus-6p-battery-early-shutoff-bootlooping-class-action-investigation/

----------

Chimicles & Tikellis LLP is the same law firm that has filed a class action lawsuit against LG for how they responded to thousands of complaints regarding bootloop issues in certain LG devices:

https://chimicles.com/?s=LG
 
Last edited:
Class Hits Google With Suit Over 'Defective' Nexus Phones

Law360, Dallas (April 17, 2017, 5:29 PM EDT) -- Google Inc. and Huawei Technologies USA Inc. were hit with a putative class action in Texas federal court Friday over an allegedly defective smartphone, the Nexus 6P, which the user claims suffers from premature battery drainage.

Plaintiff Alex Gorbatchev wants to represent a class of consumers who bought the Google Nexus 6P phones, which he says also suffer from a problem that sends the phone into a “death spiral” in which the phones suddenly switch off and then restart in what is referred to as an...

https://www.law360.com/texas/articles/913933/class-hits-google-with-suit-over-defective-nexus-phones

https://www.courthousenews.com/wp-content/uploads/2017/04/Bad-Cellphones.pdf
 
Android 7 is using file level encryption. It should take more power to process. Does anybody knows if encryption is optional? Can you disable it?
 
Android 7 is using file level encryption. It should take more power to process. Does anybody knows if encryption is optional? Can you disable it?
While Android 7 introduced file-based encryption (FBE), that is only enabled by default for devices which shipped with Android 7. Devices which were upgraded to Android 7 (like the Nexuses discussed in this thread) continue to use full disk encryption (FDE) unless the user manually enables file-based encryption through Developer Options. This is because switching from one encryption scheme to the other requires the existing data to be wiped, so that naturally wouldn't be forced upon users.

FBE versus FDE should not make any difference on power requirements: the data still needs to be decrypted before it can be accessed. FBE just allows some files (like those needed for booting the OS) to be decrypted before the user has entered their passcode to decrypt everything else.

Android 6.0 actually made encryption mandatory for all devices that can physically support it. There's not really a user-accessible way to disable encryption other than switching to a custom ROM which doesn't require it.
 
Back
Top Bottom