The only reliably persistent thing which keeps running in background is Termux.
I don’t know how, but it just doesn’t die in background. I also use it for downloads with wget. I can lock the phone, and it will keep working until it’s done. Any browser just has a high chance of dying.
Make sure the browser’s battery usage is set to unrestricted and the swap file (called “RAM Plus”, “RAM Extension” or similar) is enabled and set to a high amount.
A web UI could keep drafts indefinitely like that too. It doesn’t even need to send anything to the server; local storage has been a thing in browsers for a long time.
Go to answer a text and when you return to the lemmy tab your whole reply is gone.
What app are you using to compose responses?
If it doesn’t have enough memory, Android will kill an app…but my understanding — I haven’t written Android software — is that apps are supposed to be able to save state before this happens.
I’d think that if the app isn’t saving state, that’d probably be an app bug.
If you want to use that particular client, you might be able to work around it by composing your response in a Markdown editor (that does save state before being killed) and then just pasting it into the reply.
Go to answer a text and when you return to the lemmy tab your whole reply is gone.
You need to set the battery usage as Unrestricted on your phone, and disable sleeping tabs on your PC.
You shoudld also make sure “RAM Plus” or “RAM Extension” is enabled if you have an Android phone and the swap/page file is enabled on your PC.
The only reliably persistent thing which keeps running in background is Termux.
I don’t know how, but it just doesn’t die in background. I also use it for downloads with wget. I can lock the phone, and it will keep working until it’s done. Any browser just has a high chance of dying.
Make sure the browser’s battery usage is set to unrestricted and the swap file (called “RAM Plus”, “RAM Extension” or similar) is enabled and set to a high amount.
Get yourself a lemmy app. I use Voyager and my drafts are saved between fuckin’ reboots
(And no, as far as I can tell it doesn’t have any tracking)
A web UI could keep drafts indefinitely like that too. It doesn’t even need to send anything to the server; local storage has been a thing in browsers for a long time.
What app are you using to compose responses?
If it doesn’t have enough memory, Android will kill an app…but my understanding — I haven’t written Android software — is that apps are supposed to be able to save state before this happens.
I’d think that if the app isn’t saving state, that’d probably be an app bug.
If you want to use that particular client, you might be able to work around it by composing your response in a Markdown editor (that does save state before being killed) and then just pasting it into the reply.