Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
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 :)
Sorry to hear about that. I've been using Neo for a while and never had issues like that. Might be because your Android version is a bit older maybe. Hopefully it works on your future devices then.
Also maybe report the bug to the developer in whichever way they use for this project.