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
Comment on Why doesn't Android save app memory into storage instead of killing the process in RAM?
JelleWho@lemmy.world 4 weeks ago
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.
schipelblorp@sh.itjust.works 4 weeks ago
schipelblorp@sh.itjust.works 4 weeks ago
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.
sniggleboots@europe.pub 4 weeks ago
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
JelleWho@lemmy.world 4 weeks ago
Indeed, RAM is a memory latch by use of a capacitor. And on an interval it replenishes the charge of this capacitor . Thus when there is no power it will lose all its data.
These days it is possible (and Android has/does this) to just write old programs from RAM memory to the SSD, this is a slow process back and forth. But it saves RAM space and power.
schipelblorp@sh.itjust.works 4 weeks ago
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.