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
π¬Matrix Chat
π°Our communities below
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.
Our Communities
Lemmy App List
Chat and More
I just hate that 100-0% is a cycle regardless of the actual usage. 100-0% is more damaging to the battery than 80-30% twice.
I've turned it off on my P9ProXL just for that reason, i'm treating my battery well and will just swap it out if it's shagged.
I didn't understand why we didn't set the expectation years ago of phones ignoring the top and bottom 20%. Change it so 80 is the new 100, 20 is the new 0, and then play up the longevity factor and some marketing bs around "we squeeze every last drop out of the last 5%" (ie letting the phone go to 18% or something).
We did. Your phone's battery controller already does that, and the percentage displayed to you is normalized to the available range.
Then why are we still having to manage 80-20?
You aren't. If you choose to limit it even further, you're actually limiting it to 80-20% of that first 80-20%, or to 68-32% of the battery's true capacity, if I did that math right. (I probably didn't, but you get the idea.)
That doesn't ring true when I read the voltage of my phone and compare it to the cell specs.
The fix is called Graphene OS.
From what I've read, Graphene pushed the battery updates though
Probably makes sense. They don't want to be responsible for your phone exploding.
Can this be installed even of your OEM Unlocking is greyed out?
No, you need to unlock your bootloader during installation (and then relock it after).
There were news recently that there won't be grapheneos for newer models.
This isn't fully true. The GOS team said that it would be much more work since they couldn't use their automated tools to build the image, but not that it's going to be impossible.
https://grapheneos.social/@GrapheneOS/115062657359884451
However, Google is definitely moving in the direction of locking everything down.
Do you have a definitive source for this? All I found was speculation.
GrapheneOS team has extra work cut out for them but nothing that they can't over come.
But this is the beginning of the end IMHO
Over next few years Sundar the creep will ensure they are ml viable
Whats the reason?
Android is open source but Google is starting to move certain things behind closed doors.
This year they decide to no long provide "device trees" for pixel phones... Ie GrapheneOS will need to recerwse engineer android for each pixel devices where before this was provided.
Extra work, hard work but it is doable.
No there wasn't.
Sure, in the same way that the fix for a smoke alarm going off is taking out the battery.
Whatever the case I know that I'm very concerned about getting a pixel until they demonstrate several models that don't swell or spontaneously combust into flames. I mean, if they had to kill the 4A, the 6A, which bursts into flames, and the 7A, that makes me highly concerned.
If it's any consolation, my 4XL, 6 Pro and 8 Pro have all been fine.
I wonder if they're using worse quality batteries in the "A" series since it's a cheaper device. I haven't heard reports of the main devices exploding or bursting into flames. Just the "A" series.
I'm pretty sure the cost cutting is responsible.
Yeah my old 6a by the end of it had to be charged 2x a day. And it was less that 3 years old. My theory is they cheaped out on some component or the batteries themselves. The software just made it even worse for those of us who actually use the phone. But beats it exploding I guess.
Still haven't received my money.
we are an American company so we will lie and steal and cheat. Get used to it
I can get rid of this fucking phone and get one not made by Google.
Can custom Roms not prevent this behavior?