Pixel 6a to get mandatory update from Google to fix problems with overheating

Hostocall

de0u Well, just to be sure, I've checked and both numbers match :) .

nandohyphen1

My 6a gets warmish periodically. I dont have (or want) a google account. Is there any possible way to check if my phone is one of the affected ones without a google account? Because if not, then I guess I just won't check if mines affected...

de0u

nandohyphen1 My 6a gets warmish periodically.

Pretty much all phones get warmer under more load.

My understanding is that the issue with some 6a's is not that they get warm under load, but that in some circumstances the batteries catch fire. The reports I've seen so far relate to fires during charging.

nandohyphen1

Or would it work to create an 'anonymous' google account just to check this?

Psyonico

I'd create an anonymous google account.

The process for getting the repair or credit is to enter your email and your IMEI

nandohyphen1

Psyonico I may do that then. :)

nandohyphen1

de0u interesting. Mines never gotten hot while charging. Sometimes when its just in my pocket doing nothing I can feel it getting warm and I put it down on the counter for a bit to cool down

de0u

nandohyphen1 Based on what I've read about Google's program, the specific batteries that are most likely to be problematic do not behave in a very different way from other batteries before bursting into flames while charging. This is unlike the current 7a issue, where the batteries affected by that issue have an unusual tendency to swell.

My understanding about the current 6a issue is that the sole predictive factors are which manufacturer made the battery and cycle count. It is unlikely to be possible to infer the battery's manufacturer from how the phone behaves in one's pocket.

At present I believe the reliable ways to determine whether a particular 6a battery is affected are:

Google's web form
Running Google's stock OS

Probably the actions that can be taken by GrapheneOS users who can't or don't want to use Google's form are:

Use the "optimization" feature to limit charging to 80%,
Wait

nandohyphen1

de0u thanks for the suggestions! :)

Eirikr70

I have received an email awfully translated into French saying that I cannot benefit from the refunding program and apologising for that. Am I supposed to deduce that happily my battery does not put me at a risk of fire?

RatherVision

Eirikr70 I also got an email back denying me, saying "your device has been determined ineligible for an appeasement."

I told them my battery cycles were above the 400 limit where the update kicks in, that my battery duration has changed since the update, and that I'd contact my regulators claiming they were only putting on a public-facing facade of doing something while not actually providing compensation behind the scenes.

I was then seemingly moved straight into the support queue where they stop ending each email with the person's name, presumably because it's a more automated process, and now they're asking me for things like proof of purchase and to log in with my google account on the phone.

I signed in on the sandboxed Play Store, but it doesn't look like that worked, because they then asked me for a photo of the IMEI number on my SIM tray next to my phone.

I'd say maybe just email them back saying you've noticed your battery life change since the update, and threaten that you'll report them to whatever governmental agency applies to where you are, and they'll probably put you in the same queue where you can actually start the process again.

Eirikr70

RatherVision Well, to be honest I haven't noticed any change with my battery. So I suppose that I'm lucky enough to have a good battery...

de0u

RatherVision I signed in on the sandboxed Play Store, but it doesn't look like that worked, because they then asked me for a photo of the IMEI number on my SIM tray next to my phone.

That's a little weird, since SIM trays can potentially be swapped between devices.

One of the options available in fastboot mode is "Bar code", which shows bar codes for serial number, IMEI, etc., all at once. You might try including a photo of that in addition to what they requested.

RatherVision

Eirikr70 Go to Settings > About Phone > Battery Information and check where it says cycle count.

If it's above 400 and you haven't seen any changes in either how long your battery lasts on a daily basis, how fast it charges, or how the % indicator displays your battery percentage, then you probably don't even have an impacted device and can probably consider yourself safe from any possible negative consequences.

If it's below 400, then you'll have to wait till the number of charge cycles is above that for the update to kick in, and for you to actually file a claim they'll accept.

RatherVision

de0u Yeah, I also found it a little strange, but I think that considering they already have the IMEI I sent them prior combined with proof of purchase from a carrier, they probably just do it to deter fraud from people with a proof of purchasing a phone that they later sold to someone else. (e.g. I buy a phone, record the IMEI, sell the phone to someone else, then claim a credit from google using the proof of purchase even though I don't have the physical phone on me anymore)

de0u

RatherVision You may well be right.

CrYpT999

I just got my $100 deposit from Google. I filled out the form like 2 weeks ago. My phone ran GOS for two years but its registered with RCS. Its interesting that they are willing to compensate people on alternative OS.

pHr34kY

I got a response from Google...

Thank you for your patience as we reviewed your eligibility for the Pixel Battery Performance Program. Unfortunately, after careful review of your submission, your device has been determined ineligible for an appeasement. As a result, we have rejected your request.

Being a G1AZG manufactured in May 2022, I wasn't expecting it to get knocked back. I'm at 389 cycles. I asked if this means my device won't get restricted. It will be interesting to see how they respond.

RatherVision

pHr34kY I think they only even consider going further with the process after the cycles have gone past 400, since that's when the update would even kick in as it's not considered a risk by Google before that point.

You might end up having to just wait till it goes past 400 cycles, then try re-filing a request.

CrYpT999

pHr34kY I am at 367 cycles and got my compensation. There might have been an issue with the verification. I used my real name and birthdate for my Google account and they probably check that against information from the Payoneer account tied to your ID. I also have RCS, signed into play store, and verified my number with them. Google probably has some internal, opaque methods to make sure that people don't take a random IMEI off eBay and try to make $100 off of it. Also I got my phone used off eBay, so I don't have original purchase and they didn't check.

« Previous Page Next Page »