Google pulls Android 15 DP1 OTA images due to corruption issuebaatliwala@lemmy.world to Android@lemdro.id – 47 points – 4 months ago9to5google.com6Post a CommentPreviewYou are viewing a single commentView all commentsSo... Third major data loss update in the last 6 months?I mean, it's a Developer Preview. If someone is installing these without expecting things to go wrong sometimes that's entirely on them.A Developer Preview should allow Developers to Preview it, not brick the device. This should have been caught internally before release.The last one was on a QPR beta, and the one before that was on the A14 stable launch version. This case is definitely more understandable but after 2 worse ones it's still a bad look.At this point ::: spoiler spoiler (even for preview builds) ::: you are doing this to yourself. Knowing Google's rich software history and all.
So... Third major data loss update in the last 6 months?I mean, it's a Developer Preview. If someone is installing these without expecting things to go wrong sometimes that's entirely on them.A Developer Preview should allow Developers to Preview it, not brick the device. This should have been caught internally before release.The last one was on a QPR beta, and the one before that was on the A14 stable launch version. This case is definitely more understandable but after 2 worse ones it's still a bad look.At this point ::: spoiler spoiler (even for preview builds) ::: you are doing this to yourself. Knowing Google's rich software history and all.
I mean, it's a Developer Preview. If someone is installing these without expecting things to go wrong sometimes that's entirely on them.A Developer Preview should allow Developers to Preview it, not brick the device. This should have been caught internally before release.The last one was on a QPR beta, and the one before that was on the A14 stable launch version. This case is definitely more understandable but after 2 worse ones it's still a bad look.
A Developer Preview should allow Developers to Preview it, not brick the device. This should have been caught internally before release.
The last one was on a QPR beta, and the one before that was on the A14 stable launch version. This case is definitely more understandable but after 2 worse ones it's still a bad look.
At this point ::: spoiler spoiler (even for preview builds) ::: you are doing this to yourself. Knowing Google's rich software history and all.
So... Third major data loss update in the last 6 months?
I mean, it's a Developer Preview.
If someone is installing these without expecting things to go wrong sometimes that's entirely on them.
A Developer Preview should allow Developers to Preview it, not brick the device.
This should have been caught internally before release.
The last one was on a QPR beta, and the one before that was on the A14 stable launch version.
This case is definitely more understandable but after 2 worse ones it's still a bad look.
At this point ::: spoiler spoiler (even for preview builds) ::: you are doing this to yourself. Knowing Google's rich software history and all.