![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
The native Android client just can’t do two way sync. Just put a text file or something into any folder (from the web or desktop). Now sync that folder to Android. Now edit it on the web/desktop, and look for the changes on Android (without actively telling it to “sync”). Then change the file on Android, these 2nd changes are never sent back to the server unless you explicitly tell it to “sync” again, manually. That’s what I mean with 2 way sync.
There are quite a few files where you just need that to work to use them properly, like the database of a password manager as a prime example. Mine can talk to Nextcloud natively, so I don’t need the client for that, but I was incredibly close to just switching to syncthing, if I didn’t have active users that use the web office integration of Nextcloud.
The point is you physically and locally back up the database. Put it on your computer, or a flash drive or whatever. You can set a different, longer password for backups, and I would recommend you do that. When you get your new phone, you just copy the database into it and load it into a freshly installed Aegis. You don’t even need to self host anything, there is nothing to host.
Not everything needs to be “in the cloud”. I think this event illustrates nicely why.