I lost a draft post in Voyager on Android while I was a few apps away doing research and looking for a photo to add to the post.
That brought to me an understanding that Android will just kill apps for memory purposes.
Then I thought back to Windows 98 and how it had a page file that would write RAM information to the hard disk and use it as RAM. It was slow af, but it worked.
So I’m wondering: it’s 2026; why is Android just killing apps instead of writing them to a much faster drive for recall when needed?
When you develop an Android app it follows a defined lifecycle. The app is notified about changing states and is supposed to persist it’s data in some of them. So ideally you wouldn’t even notice that the app was killed since it would continue exactly where it was killed.
This is it, and it’s arguably a much better model. Apps are able to manage their own persistent storage, and you can always be sure that your RAM is actually RAM (and not deal with the speed and timing issues that result in you “RAM” actually being flash memory).
Problem is that it’s not at all trivial to implement, so it often isn’t implemented.
That’s true. But it’s also not trivial to implement an app that may have its “RAM” located on disk. It’s a complex problem with multiple solutions, and giving apps the freedom to do what they want with it is the way Android structured things.
And here the Voyager lemmy community insists it’s an OS issue.
That’s because voyager is a web app. It is a well designed and integrated PWA which makes it look and feel close to a native mobile app. The above mentioned preferred solution is Android specific and many multiplatform apps skip such optimization.
Nice! Thank you! That puts a lot of things in their proper context!!
It’s the app’s responsibility, not the system’s.
On a mobile, apps must be aware that they can get killed at any time.
So instead of coming up with a technical solution, they came up with a political one… maybe historically because space, even storage space, was initially so limitted?
Edit: This isn’t “judgmental” or “mockery framing.” Linux DOES have swap files available, but acknowledging the OS is designed to run on extremely limited hardware and thereby passing responsibility for persistence onto developers because the OS can’t guarantee a memory backstop IS a political solution.
Such a mockery framing is not helpful for anything. Android and iOS are doing it in a similar way. Small and limited devices still exist in 2026, and in the future as well.
I mean, even when working on any other OS, I always assumed apps would get killed at any time either intentionally or not. It’s just a matter of saving to storage at the right time. This isn’t political, have you never used alt+F4?
Not by accident, no.
Ah, yes, show your ignorance of how Linux works by being judgemental.
Impressive.
Contact the developer of Voyager and request a feature to automatically save drafts. This is handled at the app level in Android, and it’s 100% possible for the app to handle this transparently.
It’s supposed to save drafts; it just didn’t in my case, and in other people’s cases as well.
The Voyager lemmy hasn’t been too interested in my feedback.
That’s a lot of read/write cycles to your storage for no real reason. Some phones do this now, though, bc android sucks with being resource heavy. They call it “16GB RAM with RAM boost” and it’s usually 8GB + 8GB meaning that 2nd 8GB is like the ReadyBoost cache in Windows old days. It is using your local storage for extra RAM storage, but, again, that’s a little ridiculous, personally.
My voyager will let me know my comment was recovered if I’m gone too long, so maybe that’s a setting you can tweak.
2nd 8GB is like the ReadyBoost cache
RAM boost? ReadyBoost?
So it all just swap?
Yup, it’s common on chinese phone/tablet where they advertised things with 16GB of ram while it’s 8+8. First thing I disabled on my first phone that supported this fake RAM. This would be slow and kill your flash.
You wouldn’t gain anything speed or durability wise from disabling swap. Normal ram is always the priority if it is available, so any time the phone retrieves data from the swap it avoids having to relaunch an app killed due to memory pressure, which would take longer. As Android is already pretty aggressive about killing apps to save battery, in the majority of cases the swap would be used to ease the blow of a sudden, memory intensive task like high resolution video editing.
Let’s assume the phone storage can take 256 read write cycles (which is a low estimate). Considering that phones have at least 256 gigs of storage nowadays that gives an allowance of 18 gigs written per day for a phone with 10 year lifespan. Considering that I very rarely change the contents of the storage and the memory will likely not spill over by that amount, or at all most days, it’s safe to say flash health isn’t a concern.
The one time I did lose my draft, I couldn’t get it back. There’s no setting for memory on Android on Voyager.
So you’re saying there is a swap file (I’m on a cheapier Samsung Tablet A right now), but even that’s too small to hold much memory. I know in Windows you could set the size of the swap file; honestly, I’d much rather wait an extra second to get the program back into RAM than lose a draft, so I think there really must be a good technical reason it’s not happening.
Idk the Samsung tablet. And yeah it might be device dependent, too. I guess I didn’t think of that being the case.
I’m guessing it’s more a matter of having a cheaper product with less RAM than it is about the manufacturer. I’m guessing the behavior is standard across all Android devices.
I believe in the developer setting you can set up howmuch you wish to store in memory and such. But this has an impact on your battery life.
Why does it necessarily have an impact on battery life? Can it just be dumped into memory and frozen there as a snap shot? It doesn’t need to be running.
I’m not a computer scientist, but doesn’t keeping RAM engaged cost energy? You can’t turn off your computer and expect the RAM to be unaffected like a hard drive is
I think it costs electricity to flip bits, but unless things are moving, there’s not much going on. If the app isn’t actively being used, I was wondewring why it couldn’t just get frozen in carbonite and dumped into storage until the user needed it again.
I see under memory only that I can turn of Memory Profiler, which I guess will tell me what’s going on under the hood. Also looks like I have a whole 4G of memory, more than anyone would ever need! lol
Because Linux and Windows take a different approach to memory management.
And Android is based on Linux.
Thanks for that. Pretty cool how that works. Linux does have swap files, though.
