152
submitted 1 month ago by BookSwiftieAndrew@kbin.earth to c/android
  • The Android 15 update for Pixel devices is causing unexpected bricking of Pixel 6 devices.
  • Users report their Pixel 6 becoming completely unresponsive, with troubleshooting methods yielding no results.
  • The issue might be related to the Private Space on Android 15, but further investigation is needed.
top 25 comments
sorted by: hot top controversial new old
[-] LiveLM@lemmy.zip 28 points 1 month ago

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

[-] umbrella@lemmy.ml 8 points 1 month ago* (last edited 1 month ago)

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.

[-] limerod@reddthat.com 4 points 1 month ago

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.

[-] MaXimus421@lemmy.world 20 points 1 month ago* (last edited 1 month ago)

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)

[-] Markaos@lemmy.one 11 points 1 month ago

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.

[-] CuriousRefugee@lemmy.ml 15 points 1 month ago

Just updated this morning, shit. Working okay so far, though.

[-] unrushed233@lemmings.world 10 points 1 month ago

Absolutely no issues with the GrapheneOS Android 15 releases

[-] we_avoid_temptation@lemmy.zip 7 points 1 month ago

Too late for me. It's been fine so far, but I'm also not really using anything new.

[-] can@sh.itjust.works 7 points 1 month ago

How does this even happen?

[-] AbidanYre@lemmy.world 34 points 1 month ago
[-] 7oo7@lemmy.dbzer0.com 22 points 1 month ago

"Customers do the QA for us now."

[-] Andromxda@lemmy.dbzer0.com 10 points 1 month ago

That's been Microsoft's slogan for decades

[-] IllNess@infosec.pub 13 points 1 month ago

Note Google fired more than 12,000 people in the last two years.

[-] AbidanYre@lemmy.world 10 points 1 month ago

Is that why we haven't gotten any new messaging apps lately?

[-] IllNess@infosec.pub 5 points 1 month ago

We have Meet, Voice, and Messages.

Welcome to Google Messages Meet Voice. All the messaging apps combined in to one!

[-] AbidanYre@lemmy.world 2 points 1 month ago

So, basically what hangouts was before it became allo and duo then messages?

[-] PriorityMotif@lemmy.world 2 points 1 month ago

They want you to buy a new phone. My 5a screen died just after 2 years. They had extended the warranty by a year because of screens going bad. If I would have known that I would have tried to get it replaced before the two years was up.

[-] BigMikeInAustin@lemmy.world 7 points 1 month ago

That's why I thought ahead and stayed with the Pixel 5A, so that I would not get Android 15.

/s

Doh!

[-] pietroSV2 4 points 4 weeks ago

So Google's own software bricks Google's own phones? No waaay :-D

[-] lazycouchpotato@lemmy.world 4 points 1 month ago

Upgraded to Android 15 with no issues on my 6a, but stuff like this is concerning.

[-] isVeryLoud@lemmy.ca 4 points 1 month ago

My Pixel 6 survived the update! \o/

[-] Albbi@lemmy.ca 3 points 1 month ago

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.

[-] WR5@lemmy.world 2 points 1 month ago

I'm running Android 14 on a Pixel 5, no updates available for it but seems to be running fine.

[-] scala@lemmy.ml 2 points 1 month ago

Hope my pixel 7 doesn't get effed.

[-] pietroSV2 1 points 4 weeks ago

Classic Pixel problems. Every model 1000s complaints

this post was submitted on 21 Oct 2024
152 points (98.7% liked)

Android

17709 readers
56 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

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. 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.

  5. 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.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 1 year ago
MODERATORS