This weekend my first scheduled backups were due during the night, and unfortunately I found my phone in recovery next morning. It was now in kind of “boot loop”, resetting shortly after logging into the phone.

Could stop this by quickly killing NeoBackup processes after login. Neo tried to again run the scheduled task each time, most likely as they before failed/did not run through.

So in summary it looks like my Lineage 18 device has issues with the scheduled backups of Neo.

Strange thing is that all my manual tests, even the same as configured for the scheduled tasks, worked perfectly fine. Just today’s first fully automatic runs seemed to make trouble (maybe cause mobile phone was in standby?)

Can only guess, but will keep Titanium for now on the older devices, and will keep Neo in mind for newer versions of Android, on which Titanium will not work any more :)

Latest version I know is 8.4.0.2 from 2020-05-16 downloaded from here http://www.matrixrewriter.com/android/files/TitaniumBackup_latest.apk.

I use Titanium since Android 4 and had indeed some troubles (related to storage access rights) on Android 11. After solving those, Titanium ran fine like on older versions of Android. Did not yet try Titanium on newer versions than Android 11.

Thank you for the hint and link to Neo Backup, I will give it a try. (Ah, just saw it is an incarnation of OAndBackup, nice.)

I am not aware of any advantage, but my family and friends are using either Threema, Signal or Telegram. So I use all three of them.

My Android paid must haves are: Titanium Backup (for scheduled backups and quick recovery), Threema (Messenger) and airMusic (former AirAudio, stream from mobile to e.g. Sonos).

Das gleiche gilt für mich leider auch. Mit VMware Infrastrukturen kannte ich mich mal aus, aber OpenStack kannte ich zuvor nicht. Ich fand das Projekt an sich aber interessant und alles sehr professionell dargestellt und dokumentiert.