Google Pixel

7719 readers

5 users here now

The World's Google Pixel community!

This community is for lemmings to gather and discuss all things related to the Google Pixel phone and other related hardware. Feel free to ask questions, seek advice, and engage in discussions around the Pixel and its ecosystem.

We ask you to be polite when addressing others and respect Lemmy.world's rules.

NSFW content is not allowed and will immediately get you banned.

It also goes without saying that self-promotion of any nature and referral links are not allowed. When in doubt, contact the mod team first.

Also, please, no politics.

For more general Android discussions, see !android@lemmy.world.

This community is not in any way affiliated with Google. If you are looking for customer support regarding your Pixel phone, look here instead: https://support.google.com/pixelphone/

founded 2 years ago

MODERATORS

mandlar@lemmy.world

AlmightySnoo@lemmy.world

hackitfast@lemmy.world

Pixel users report battery drain issues after March update, and this could be the reason (www.androidauthority.com)

submitted 4 days ago by WesternInfidels@feddit.online to c/googlepixel@lemmy.world

22 comments fedilink hide all child comments

My Pro 7 is making the sad-trombone "almost dead" sound quite a lot in the past few weeks, and the first time I heard it, I didn't know what it was. Because, although I've had the phone for 18 months, I'd never heard that sound before.

This article doesn't have much authoritative information, it's mostly recapping Reddit posts, I guess. But: Is anyone else here having the same issue?

...numerous reports point to an undiagnosed issue causing batteries in Pixel phones, including the new Pixel 10 series, to drain much faster than they did previously.

...one user claims it may be because of a GPS-related bug preventing the CPU from entering into a “suspended” state — also known as Doze specifically in Android’s context — when not being used. The user points out, “the Exynos baseband/GNSS module is caught in a persistent polling loop, causing a hardware interrupt storm even when the device is completely isolated in Airplane Mode with all radios manually toggled off.” This, in turn, keeps the CPU up and running, resulting in the drain.

you are viewing a single comment's thread
view the rest of the comments

[–] 2inchesoffury@lemmy.blahaj.zone 2 points 4 days ago (1 children)

Same. I feel like google just decided fast charging is no longer a thing. Charging from 49-77% will take 25~ mins then 77-80% will take 30+ mins. I'm having to walk around with a battery pack now. Horrible update.

[–] binom@lemmy.world 2 points 3 days ago* (last edited 3 days ago) (1 children)

apparently that was a change to prolong battery life: https://www.androidauthority.com/google-pixel-charging-optimization-77-percent-3648012/

https://issuetracker.google.com/issues/485148344?pli=1#comment4

This behavior is related to the 80% Charge Limit feature. In the current software build, the device charges at normal speeds until it reaches approximately 77%, at which point it transitions to a lower current to reach the final 80% limit.

While this may result in slower charging speeds near the limit, it is intended to manage battery health and should not impact normal device usage. We are currently working on optimizing this user experience

[–] 2inchesoffury@lemmy.blahaj.zone 2 points 3 days ago

Oh yeah I noticed the lower charging current when using a wireless charger. That battery pack goes a little crazy when it switches over. I just hate that fast charging is effectively gone now and the estimated time remaining till full charge is more unreliable than ever.