Torsten Grote

Most likely explanation is that most notifications come from foreground services and are shown because of that. However, app backup is done by the system, so we don't keep a...

It could be that returning `412` is this server's strange way of telling us that it doesn't support the request header `Depth: infinity`. If we had such a server to...

From the logs it looks like a 3rd party app is hammering the system hard, causing ANRs and lots of `DeadObjectException`s. Didn't see anything related to Seedvault. Was this a...

Unfortunately, we don't always know. The backup process is controlled by the Android system and it doesn't give us reasons why it failed. As a workaround, we could somehow remember...

The language mix is most likely because Seedvault isn't completely translated to German: https://hosted.weblate.org/projects/calyxos/seedvault/de/

> touching that notification leads to a screen like: > > "do you want to restore your device from an existing backup or start a new backup?" This sounds like...

This sounds like a ROM integration issue. I assume that the google account refers to you having the possibility to choose google backup as another backup provider. But that code...

@mikeNG have you ever seen Seedvault trying to do backups on LOS before it was even set up?

Related docs: https://developer.android.com/reference/android/content/pm/InstallSourceInfo This may be [`getInitiatingPackageName()`](https://developer.android.com/reference/android/content/pm/InstallSourceInfo#getInitiatingPackageName()).

As update owner and installer can be different, we probably need to backup both and if we don't know the owner, we just set the installer.