Open fluoriteByte opened 3 months ago
so, why do you plan backups at a time when the device is off?
or does NB backup when it shouldn't? (which would be another kind of bug, may be related to another one)
Its just so happened that i booted at the same time that i scheduled the backup
This bug has since happened to me 2 times, all of them related to whatsapp decided to back up at the same time
so, what do you think, how to solve this?
we definitely will not look for all the apps that could possibly run a backup, find out how to detect that, etc.
delaying the backup could be a workaround, but in general I wouldn't want to delay the schedule.
btw. NB can be scheduled at a certain time, perhaps you should better ask the WhatsApp developers to add a time?
You could also disable pauseApps... or just not backup Whatsapp, when it has it's own backup?
Alr, im going to exclude whatsapp from my backups 👍
Description When booting from a cold boot, both whatsapp and neo backup launch at the same time, neo backup tries to backup whatsapp while whatsapp also tries to back itself up to google drive, if whatsapp wins the race condition and starts uploading at the same time that neo backup starts backing up its data, then they both softlock, which somehow cause my entire system to lag and glitch horribly
This has happened twice, this time i made sure to kill whatsapp before it started backing up
Steps To Reproduce
Expected behavior Neoback up and whatsapp do their backing up duty
Screenshots I couldn't really screenshot since that was also one of the bugged things before i rebooted two times
System Information(please complete the following information):