NeoApplications
[Bug] Yet Another "NB is very slow" bug....
I have a Surya (POCO X3 NFC) running official LineageOS21 (A14) with Magisk.
My backup experience with NeoBackup 8.3.6 (installed from f-droid) is somewhat bugging me:
- Start from a fresh installation of NB in an empty backup folder on SD card (external storage)
- Accept root popup
- Select a few apps (Firefox, AudioBookShelf, Catima, didUpFamiglia, EasyPark, Camera (non stock), ImageToolbox, Gaugin, Jellyfin, LibreTube, Markor, Summit, SolarMan, Termux)
- Start a full backup using NeoBackup defaults
- Backup ends successfully after some 12 hours, total backup size is about 12gb
Restore, on the other hand, is basically immediate or at least takes only seconds even for bigger packages.
Is this normal to be expected? Is there anything i can try to improve backup experience?
i also have similar experience with Whatsapp backup. But Neobackup also freezes other apps too I have to force reboot This is happening on lineage Os 21
previously I was using crdroid 10.2 (A14) on thag backups worked without any problem
if it's about freezing apps, then simply disable pauseApps. It is there to try to ensure consistency of backups, but from my experience it doesn't help.
Another reason might be that your device pauses NB (e.g. if you turn off the screen). I have a feeling that a few or even many ROMs don't respect battery optimization settings, especially stock ROMs or such derived from stock. People are obsessed with battery time and that is what you get.
My backups are about 15GB (e.g. 400 user apps) and take always less than 30 min (or much less), no matter what I do.
crdroid 10.2 (A14)
I have very bad experiences with crDroid from somewhere after 10 to let's say 10.3 or later. All kindsa of problems from wrong permissions in the Android folder to a hanging system (no reaction at all, and for a very loooong time, so I rebooted, may be it would have continued after hours). It seemed to be something with A14 QPR3 or whatever. I switched to Bliss (well, after crDroid 10.6) and everything was smooth again (while crDroid still had hickups). Note, I am a very long time crDroid user (for years), so up to now it was the goto-first ROM for me. My device is Xiaomi Redmi Note 10 Pro (sweet).
crdroid 10.2 (A14)
I have very bad experiences with crDroid from somewhere after 10 to let's say 10.3 or later. All kindsa of problems from wrong permissions in the Android folder to a hanging system (no reaction at all, and for a very loooong time, so I rebooted, may be it would have continued after hours). It seemed to be something with A14 QPR3 or whatever. I switched to Bliss (well, after crDroid 10.6) and everything was smooth again (while crDroid still had hickups). Note, I am a very long time crDroid user (for years), so up to now it was the goto-first ROM for me. My device is Xiaomi Redmi Note 10 Pro (sweet).
Sorry for necrobumping, but to prevent others to choose crdroid and to be fair, I am now using crdroid 16 and neobackup runs perfectly. The only issue I found was that I forget to set the password in the new device before recovering and I was in a never ending process without any warning.
yes, thanks for reporting your positive experiences... I used crDroid for years before that A14 desaster... so, I am far from saying "don't use crDroid", actually I recommended it all the time.
My experiences were only related to those versions of A14... though those seemed to be broken for several models, I guess Google changes in combination with crDroid functionality.