79
Google leaves older Pixels behind for Android's long-awaited Battery Health menu
(www.androidauthority.com)
this post was submitted on 08 May 2025
79 points (100.0% liked)
Android
18992 readers
212 users here now
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
🔗Universal Link: !android@lemdro.id
💡Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
📰Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Maybe, google should've included the necessary hardware if it was going to bring the feature to pixel down the line. 7 yrs of updates with missing features does not inspire confidence in them.
So you would like them to put hardware into a model, made before they decided to add said hardware? So how about any new hardware added in the next Pixel, should they also have put that into previous Pixels?
Software updates will always have hardware limitations
Pixel 8 did not get the multi model Gemini update simply because it lacked the additional RAM needed for the LLM. Its the same with this feature. They brought battery health and charge counter in android 14.
They could've bought this to pixel phones if google did not skimp on the hardware.
I know but, since they were going to work on this feature and had starting with android 14. It does not make sense to skimp on it for a year old hardware. Same with the RAM limitation on the pixel 8.
If they hadn't thought of the idea until say a year ago then it's not like they can go back in time or recall everyone's phones to install a piece of hardware
They have been working on the battery health feature for a time. Android 14 brought the charge counter to supported phones. It would be unreasonable to say they did not know.
Without knowing what these "product limitations" actually are then I think we're just arguing hypotheticals
@limerod they took a leaf out of Apple's playbook with this decision