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?
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