-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Schedued backups are started over and over #933
Comments
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.
|
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 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) . 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. EDIT: |
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 |
Guidelines
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
The text was updated successfully, but these errors were encountered: