Confirmation every time on backup/restore?

[danjde]

Hi IzzySoft,
not really an issue,
I would like to understand if is it possible to automatize the backup (or restore) process, avoiding to give confirmation every time for every application.

Many many thanks!

Davide

[IzzySoft]

That's already possible, if your ROM supports it – at least for Backup there's "auto confirmed backup", even with auto-unlock of the device. But not all devices/ROMs support it. For details, please check the wiki. Keywords: AUTO_CONFIRM and MK_AUTOCONFIRM_DELAY (oh, and AUTO_UNLOCK).

[danjde]

Well, I found them and set.

About:

if your ROM supports it [..]

How I could verify?

Many thanks again!

Davide

[varac]

I tried with LinageOS 15.1 on a encrypted S5, and my phone asks for the encr. password for every app I backup using Adebar. Probably it's not in your hands @IzzySoft but is there any way around this ?

[varac]

The only way I can think of would be to backup all apps at once, so you only would need to give one time encryption pw/permission, and then later split the monolithic backup archive into the different apks/settings. Not sure if this is easily implemented. @IzzySoft ?

[varac]

Andrid backup extractor does this: https://github.com/nelenkov/android-backup-extractor/

https://nelenkov.blogspot.com/2012/06/unpacking-android-backups.html

[IzzySoft]

The only way I can think of would be to backup all apps at once

That you can do directly using adb backup. Adebar specifically avoids this, as a backup can only be restored completely. This is why Adebar creates one backup package per app, so you can also restore only the apps you want.

and then later split the monolithic backup archive into the different apks/settings

And how would you do that? Sure you convert the backup into a tar archive. But I don't know about a mechanism for the reverse, creating valid backup files. If you want to go that road, I suggest you use adb backup directly.

As I wrote, auto-confirmation is implemented for the backup process. What I could look into as soon as time permits (not this month I guess) is to implement the same for restore. But then, again: that might not work on all devices – and I especially cannot test it on all devices.

[IzzySoft]

@danjde @varac could you please re-check? @Catfriend1 and I have been working a lot in that area the past few days. Check the Configuration wiki for AUTOCONFIRM.

As for encryption password, that can be set via BACKUP_PASSWORD – but having a password stored plain-text in several files isn't the best idea. So if you want to have that routine, I'd suggest setting a dummy password in the variable, and adjusting it in the generated script just before you want to run them (setting it back afterwards). Thanks to the dummy, the corresponding routines in the backup/restore scripts will be created, so you just need to adjust them.

[IzzySoft]

As there's no activity here for about a year, I assume the issue is solved. Thanks to all who participated!