17
How to keep Voyager from closing? (sh.itjust.works)
submitted 1 week ago by 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
[โ€“] [S] 1 point 1 week ago (2 children)

Yeah, but more often my Galaxy Tab A than my Pixel.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [โ€“] 1 point 1 week ago* (last edited 1 week ago) (1 child)

    I've gotten recommendations to turn off battery optimizations. Graphene or android seems to have gotten a bit better with not killing apps, especially with regular restarts (3-4 times a week)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] [S] 2 points 1 week ago (1 child)

    Just turned off optimization for Voyager. We'll see what happens, but, honestly, since getting closed out and a draft will be lost is a possibility, it's probably best to adopt a behavior that assumes it will happen.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] 1 point 1 week ago (1 child)

    Any update one day in?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] [S] 3 points 1 week ago* (last edited 1 week ago) (2 children)

    Yes! At least as far as information goes. From the nostupidquestions lemmy (see post history), Voyager isn't a proper Android app but basically a web page (????), so it doesn't have the same granular system access an app might and its behavior might be more limitted in that regard, so, yeah, lean on OS solutions here.

    I also got a recommend to try Interstellar.

    But what the heck, let me open a few tabs and get back to you in two minutes.

    Edit: I saved this comment, opened a bunch of stuff, and came back to Voyager saying it closed and that it noticed I was editing but to just "begin composing." So, yes, I'd say avoid leaving Voyager at all costs while writing or compose in an editor.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [โ€“] 2 points 1 week ago*

    Yeah, it's solely Voyager's fault (or at least the underlying cross-platform frameworks it's built upon). Gracefully handling app lifecycle events so this sort of thing doesn't happen was literally the first topic covered in the Android documentation back when I learned it. Android provides plenty of tools to save and restore state when an activity is destroyed, but I guess it's hard to hook into them when the Android app is just a wrapper around an embedded web app?

    Voyager is the only Fediverse app I've tried that has this problem, for the record.

  • permalink
  • fedilink
  • source
  • parent
  • [โ€“] 1 point 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)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [โ€“] [S] 2 points 1 week ago (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [โ€“] 2 points 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.

  • permalink
  • fedilink
  • source
  • parent