Voyager

8261 readers

7 users here now

The official lemmy community for Voyager, an open source, mobile-first client for lemmy.

Rules

Be nice.
lemmy.world instance policy

Sponsor development! 👇

💙

founded 3 years ago

MODERATORS

aeharding@lemmy.world

aeharding@vger.social

How to keep Voyager from closing? (sh.itjust.works)

submitted 2 weeks ago by schipelblorp@sh.itjust.works to c/voyagerapp@lemmy.world

33 comments fedilink hide all child comments

I just popped out to grab an image for a post, then realized I didn't have a photo app, then went to the play store to download Ente, then decided I should just download an image directly.... by the time I got back, Voyager had been closed and the draft was (apparently?) lost.

Any idea of how to prevent this from happening in the future?

And where is the draft supposedly saved?

you are viewing a single comment's thread
view the rest of the comments

[–] LodeMike@lemmy.today 1 points 1 week ago* (last edited 1 week ago) (2 children)

The reason is that Android is a piece of shit. It's so obnoxiously memory inefficient and kills apps all the time. I restart my phone regularly which helps. At a point it will unload my home screen app as soon as I open another. Sometimes it unloads the stock launcher too (used for multitasking)

[–] NewNewAugustEast@lemmy.zip 2 points 1 week ago

That is not my experience with any if my android phones or tablet.

Seems like their might be something going on with yours.

[–] schipelblorp@sh.itjust.works 2 points 1 week ago (1 children)

But, like, Windows 98 had a swap file for memory. Why doesn't Android in 2026? This is my stupid question for today.

[–] Quetzalcutlass@lemmy.world 2 points 1 week ago* (last edited 1 week ago)

Android (sometimes; some ROMs have it disabled) uses a system called zram where a portion of memory is compressed to store more data. This vastly increases the amount of memory available nearly for free, but the system doesn't play well with swap and actually degrades performance when both are enabled.

The other historical problem was that enabling swap on a phone could rapidly wear down flash storage such as EMMCs, but that's not as much of a concern these days.