Torsten Grote

> Set it to "once a week" then back to 3 days. Let's see what happens. What is shown in the UI for the next estimated run time?

Thanks for the report. Could you give me the output of `adb shell dumpsys jobscheduler | grep -B 6 -A 33 "Service: com.steve"` please?

> I'm having 2 options active: backup every 3 days AND only backup if being charged. I feel that the backup starts as soon as one of the options is...

Interesting that [`backupInForeground`](https://developer.android.com/guide/topics/manifest/application-element#backupInForeground) doesn't seem to get respected. It is `false` by default. Maybe this is only when the system requests the backup itself and not when we request it...

Also relevant here: [`android:killAfterRestore="true"`](https://developer.android.com/guide/topics/manifest/application-element#killrst)

> If that's the case, than a perfect solution for me would be to be able to select which apps will use D2D and which won't. @t-m-w Is it d2d...

> Do D2D backup for most apps excluding some and then normal backup for those excluded apps. Backup is snapshot based. . You will end up with two snapshots each...

You probably only noticed it now, because we now do d2d which includes more apps into the backup. Before, few apps got backed up, so the ones you use daily...

the main issue here is that this happened to all key/value backups, even `@pm@` which then caused the entire backup to fail and the system to do a re-init of...

Still happening sometimes with smaller chunks with 5.0 ```ruby 10-23 17:37:49.275 16116 16763 E FullBackup: Error handling backup data for org.fdroid.basic.debug: 10-23 17:37:49.275 16116 16763 E FullBackup: java.io.IOException: unexpected end...