- cross-posted to:
- android@lemmy.world
- cross-posted to:
- android@lemmy.world
Google has now acknowledged the issue and confirmed it’s looking into it.
You must log in or register to comment.
Funny how GrapheneOS already fixed this bug while they were porting android 14 lol
And if you see their post about it on Mastodon, the tone is kind of like “I guess we fixed this one already, nbd.”
Well, Graphene is just superior
I think upstream might be the right word in this context.
I’d like Google to comment on why such a serious bug had not been detected sooner.
Was it not covered in testing? Perhaps telemetry failed on affected units?
I think the community deserves at least a comment considering that data loss has occurred.
