Torsten Grote

New theory: In the same millisecond (above one ms before) we cancel the notification, we update the same notification with the status of the app backup (`NotificationBackupObserver: Completed`). So *maybe*...

Comment [from the code](https://cs.android.com/android/platform/superproject/main/+/main:frameworks/base/services/core/java/com/android/server/notification/NotificationManagerService.java;l=10419;drc=c28964b60e08271b118ed58189db375c85eac14a): // In enqueueNotificationInternal notifications are added by scheduling the // work on the worker handler. Hence, we also schedule the cancel on this // handler to...

hacky debug code we used to check for notification flags: ```kotlin Log.e("TEST", "CANCEL NOTIFICATION!") val mustHaveFlags = 0 val mustNotHaveFlags = (FLAG_FOREGROUND_SERVICE or Notification.FLAG_USER_INITIATED_JOB or Notification.FLAG_AUTOGROUP_SUMMARY or 0x00010000) nm.activeNotifications.forEach {...

@DDvO from the above log, it looks like you tried to validate your recovery code and made the app crash. somehow it received 13 instead of 12 words. do you...

Thanks so much @UjuiUjuMandan, that's really helpful!

I created https://github.com/stevesoltys/backup/wiki/ROM-Integration, but we should probably link it from main readme. anything else?

What version of Seedvault are you running? Based on your description, it sounds outdated. Also, can you post the logcat export of the backup process?

Do you have package names of some apps that are in "Waiting to back up.." still and could you also grab a log right after kicking off manual backup?

It looks like the `no.nrk.yr` app was backed up successfully indeed and `1708032 bytes` written. Unfortunately, there's no hint in the log why the backup status of the app wasn't...

> You should really add to-the-point status/error reporting and logging. We really should? Could you dial down your entitlement please? Also you might want to read one of the many...