Android’s stock backup misses a lot of things, apps can opt-out and many do, it also doesn’t backup files or documents or photos. Photos are “backed up” if you enable Google Photos cloud sync, but that’s separate. It basically just backs up your phone calls/SMS, system settings and what apps you have installed (but not their data unless they tie into the backup APIs).

Still waiting for an OTA image to fix the boot loop. Or, an admission from Google that users data is lost.

Except for those who had the issue and rebooted their phone and it’s stuck at “pixel is starting…”. This update doesn’t fix the issue for those devices. They are still working on it, possibly.

I used GitHub’s search across the entire Graphene org, but couldn’t find any references to the issue. Doesn’t mean its not there, I just couldn’t find it. If the technical details of the issue were public, it would help people know whether or not their data is recoverable if they are already stuck with a “pixel is starting…” phone that doesn’t boot.

Some rough estimates:

Even if it only affects 0.1% of users, that still puts the number of affected users in the thousands to 10s of thousands range, with an estimated 10-15 million Pixel 6-8 phones out there. T-Mobile (and Google Fi) haven’t even allowed Android 14 to go out as well. So between the 800 stars and 500 comments on the bug, and the other 564 votes and 260 comments on the community forum post, and given that only a fraction of people do that, many are going to contact Google Support privately, or take the phone to BestBuy or wherever, that somewhat lines up.

I’d still think someone would’ve run into in the beta, particularly since beta users are even more tech savvy and likely to use multiple users. But perhaps not enough reports to get Google’s attention.

But this is something that Google’s automated testing should’ve caught. You don’t have to do anything other than use the feature, and switch between accounts several times. Not a hard bug to hit at all.

They said that, but I couldn’t find the fix in their github repository. Does anyone know the commit that fixes this bug? It would help shed light on the technical details of the issue.

SDF has been having some scaling pains. But it looks like it federated to lemmy.world, how about this link? https://lemmy.world/post/304685

You will be pleased to know that Lemmy went to the source a few weeks back: https://lemmy.sdf.org/post/151820

To be fair, I think the idea would be to change the albedo of Earth so that more sunlight is reflected back into space. But it would need to reflect more light/heat than it produces in waste heat for the refrigeration, who wants to do the math?

Since you’re on another instance, it might need to sync.

If you use the search, and search for !dontstarve@sh.itjust.works

Then wait a few seconds, search again, it should sync and show up and let you click it.

I hope they improve this process in the new version of Lemmy.

A few thoughts:

• Unlike reddit, Lemmy provides a way for instances to not tolerate those sorts of activities by limiting what users can join their own instances and blocking entire instances where those activities are coming from.
• With karma not being a public profile stat, there shouldn’t be any needs to farm it.
• Without the corporate profit motive and centralized control Lemmy (as a whole) couldn’t do what reddit is doing with the APIs. An instance could and an instance could also serve ads, but people are free to move to another instance if they don’t like it while still maintaining access to most content.