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 thought this sounded familiar and sure enough, second paragraph:
The Pixel 6 series has a history of running into issues after Android updates. Last year, the Android 14 update locked some users out of their storage, and earlier this year, factory resets left many Pixel 6 devices unresponsive.
Disappointing, you'd think this wouldn't happen with Google controlling both hardware and software
you'd think this wouldn't happen with Google controlling both hardware and software
i only expect more problems with more google control instead of less.
Disappointing, you'd think this wouldn't happen with Google controlling both hardware and software
Perhaps, the testing folks thought the same thing as you, and skipped testing a thing or four. π€£/s
Anyway, the 1st gen pixel users suffered the most. The latest gen pixel 8 series (and perhaps pixel 9) are not critically hit and have less heating problems. It sucks being early adopter for beta hardware and software. Google should compensate the affected users with upgrade to pixel 7/8 or even 9 series if possible.
I'm curious, what's the recourse here when this happens? Does Google make it right somehow when their own software bricks their own devices?
Or is just "Oops, our bad. Just buy a new one, best of luck!!"?
Does reflashing a ROM fix it? (aside from some data loss, of course)
Don't know about the rest, but...
Does reflashing a ROM fix it?
The phones appear to be simply dead with no response to anything. No way to connect ADB, no way to connect fastboot, nothing.
Also the bootloader allows flashing over the cable only when it's unlocked (at least on Pixels; I couldn't find anything relevant in the Android documentation). The vast majority of Pixels should have their bootloaders locked, and it is only possible to unlock it through the system settings, so it's pretty safe to say that most Pixels cannot be recovered if Android fails to boot because you cannot unlock the bootloader if you can't get into settings.
Just updated this morning, shit. Working okay so far, though.
Absolutely no issues with the GrapheneOS Android 15 releases
How does this even happen?
Lack of QA.
"Customers do the QA for us now."
That's been Microsoft's slogan for decades
Note Google fired more than 12,000 people in the last two years.
Is that why we haven't gotten any new messaging apps lately?
We have Meet, Voice, and Messages.
Welcome to Google Messages Meet Voice. All the messaging apps combined in to one!
So, basically what hangouts was before it became allo and duo then messages?
Too late for me. It's been fine so far, but I'm also not really using anything new.
That's why I thought ahead and stayed with the Pixel 5A, so that I would not get Android 15.
/s
Doh!
So Google's own software bricks Google's own phones? No waaay :-D
Upgraded to Android 15 with no issues on my 6a, but stuff like this is concerning.
My Pixel 6 survived the update! \o/
I wonder if the is just happening on the 6 or the 6xl is also affected. Either way I'll not be exploring the private spaces for a while.
I'm running Android 14 on a Pixel 5, no updates available for it but seems to be running fine.
Hope my pixel 7 doesn't get effed.
Classic Pixel problems. Every model 1000s complaints