NeoApplications
Schedued backups are started over and over
Guidelines
- [X] I have read the FAQ and it doesn't cover the issue.
- [X] I have searched the issue tracker for open and closed issues that are similar to the feature request I want to file, without success.
- [X] I'm on the latest version.
- [X] I'm not using a test build (alpha/beta/release-candidate).
- [X] This issue contains only one bug.
Describe the bug
Configure a backup schedule, in my case at 0:05 once a week.
Expected Behavior
When a scheduled backup time approaches it is started multiple times. Backup processes are started until CPU is used 100%. Phone heats up and is not usable any more. To "solve" it I went back to 8.3.6, which works as expected.
Neo Backup's Version
8.3.10
Installation Source
Official F-Droid repo
Last Known Working Version
8.3.6
Relevant information
- Device: Fairphone 4
- Android Version: 11
- ROM: (AOSP, CalyxOS, MIUI, GOS...) stock Android
Experienced this today too, my scheduled backup isn't even enabled as well (I manually trigger it via intents in my Tasker automations).
I can confirm the issue. It starts just randomly in any time of day.
There seems to be some people effected by this and others who aren't (8.3.11 doesn't change much on this front), but it'll be the main topic for next release. For now just disable the schedules and run zhem manually when wished.
Thanks for the heads up. I'd just like to reiterate that my schedule isn't even enabled when this happens (for me). I use Tasker to trigger the backup on specific conditions (screenshots provided). Now yes with this scenario it could be an "issue on my end" but I haven't edited the automation since I first installed Neo Backup several months ago. Not sure where the issue lies.
~~Honestly this is probably irrelevant when it comes to debugging, but whatever lol~~
i have to confirm that this bug is still present in version 8.3.11 (fdroid build).
for me it even seems to be the case if i start a scheduled backup manually... at the latest - for sure after completing the backup - if i swipe Neo Backup away from the app-history (not even a force close via app-info) it starts over again.
...unfortunately i had to go back to version 8.3.8 to avoid the annoying filter-bug (#928) and this even more severe bug. 😦
Confirmed with my Pixel 4a (sunfish) running LineageOS 21.0, F-Droid build 8.3.10.
You have to be quick to force close the app or it will just keep going.
I had set up schedules to make it easier for me to perform batch backups, but they were never enabled. Only one of three schedules was running free. On a whim, I toggled the enable boxes on then off, but that made it worse, as all schedules I configured started running amok.
something simmilar happens to me on android 15 (lineageOS 22.1) on a xiaomi redmi note 10 pro (sweet) with neo backup 8.3.11 i don't use automatic sheduled backups though i manually start my backup
when i once made a backup manually, neobackup is starting the same backup again by itself in the background if i close the app (but only once i think) . it doesn't matter if i just close the app or if i kill the app. the same thing happens if i don't close the app but restart my phone.
that forces me to either abort the backup(in the notifications of my phone), wich leads to broken backup data or to let it just happen... wich leads to two practically identical backups and the loss of the previously made backup.
it also happened when i changed something in that backup preset(or backup plan?). i tried to set a time for this backup preset and activate the automatic backup for a certain time every day(hoping that i can avoid this behaviour). after making that setting and closing the app, the backup startet again too. (lucky me i found this bug report wich made me deactivate the automatic scheduled backup again)
EDIT: for some reason, the scheduled backup was not deactivated even though i deactivated it. and the next morning i saw, that the backup was made once as it should be(as long as it was really selected) so in my case i don't get this backup loop that is described in the original bug report when backups are scheduled. in my case the manually triggered backups are the bigger problem. but still random things happen. like right now. i started my phone again(for another reason) after one backup was completed. and it did a new backup again after the restart.
Anything new on this? How can I help to solve it (without Android programming skills)?
The old logic was restored and the issue shall be fixed with the next release
You attempt failed. Rel. 8.3.12 did a scheduled backup last night: good. But when I started the app 5 minutes ago, it again started a backup, which has not been planned. The is reproducible, a backup is started when the app is started.
Also there are notifications re. planned backups. I don't want them to be shown between scheduled backups all the time.
I'm not sure about the notifications (maybe a screenshot would help make things more clear?).
On the schedules running on each start: this resembles the stuck workers and is possibly carried over from the earlier versions because a schedule was enabled, while the newer version replaces the backend but keeps the other one in place. The straight forward way to clear the situation would be that you uninstall and then reinstall NB.
Thank you. I'll try the update with disabled schedules. May take a few days, very busy in the moment...
After a scheduled backup it turns out, that the backup works. After the successful backup 2 more notifications remains. They cannot be deleted (swiped out) manually. Former releases just left the notification re. success of backup, which is the desired level of information. See screen shots ("retrieve app list" and "planned backup" or "backup planned"?)
The last two notifications are redundent and remains visible until neo backup is killed or the phone is restarted.
The schedule logic is still defective. The backup is started when the application is started. Even if no scheduled backup is pending for execution. I had to go back to 8.3.6, the most recent version I am sure that's working.
I'd be guessing that you had a schedule enabled when updating 8.3.11→8.3.12 resulting this. Just disable all schedules before updating to 8.3.12 and all should be fine.
For me it is still not fixed, too. A clean install of 8.3.12 does not start scheduled backups at all but it does when launching the app manually. No problems with 8.3.6.
Scheduled backups are started multiple times. When I start neo backup manually a few hours later, a new backup will be started, even if it's not time for a scheduled backup. Like johnassel I had to go back to 8.3.6.
For me it is still not fixed, too. A clean install of 8.3.12 does not start scheduled backups at all but it does when launching the app manually. No problems with 8.3.6.
I'm seeing this exact issue after upgrading. Scheduled backups dont run, but immediately trigger when the app is opened.
I'd be guessing that you had a schedule enabled when updating 8.3.11→8.3.12 resulting this. Just disable all schedules before updating to 8.3.12 and all should be fine.
Uh, that seems rather counter intuitive -- I'm normally just updating from FDroid (when presented with an upgrade) and have never had to disable my schedules before upgrading, alas, I've had 8.3.11 installed for months, so I dont even have an older backup to go back to.....
I (and I guess others) just need to have their schedules working again with 8.3.12
I'm seeing this exact issue after upgrading. Scheduled backups dont run, but immediately trigger when the app is opened.
Same for me. Even with a clean install of version 8.3.12 (Android 15)
Should be fixed with 8.3.13 (with a side-effect, that will be is already fixed for 8.3.14)