Voyager

[–] AzuraTheSpellkissed@lemmy.blahaj.zone 6 points 1 week ago

Honestly it is not just an OS issue. Mobile apps need to expect to be memory evicted in general any time they aren't in foreground, so they should preferably handle state restoration well.

That said, I don't mean to sound demanding.

parent

[–] artyom@piefed.social 8 points 1 week ago (2 children)

This is more of an operating system issue.

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

Then where are the drafts that Voyager is saving?

parent

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

Voyager's drafts are weird. To use them, you need to find the same comment/post you were replying to when the app closed and try replying again. It'll automatically restore your previous text and (AFAIK) immediately delete the draft.

There is no way to view or save your drafts, nor know or jump to the comment/post that it applies to. I'm also not sure if they're persistent beyond the first time you open the app after a crash. The whole system is one of Voyager's rougher edges.

parent

[–] LillyPip@lemmy.ca 1 point 1 week ago*

The clipboard is basically the first thing to suffer. It’s the most expendable thing you have.

This is what I meant by suggesting you’re attributing this to the app you’re interacting with more. Are you mainly noticing this with comments disappearing when you switch to other apps before you can submit them?

Your device may be at the limits of its working memory.

parent

[–] kingofras@lemmy.world 3 points 1 week ago

Correct. This is the OS on the device that doesn’t have enough RAM to swap between the two apps and hold whatever they’re trying to copy into memory. Wouldn’t happen on a device with more physical memory.

parent

[–] CompactFlax@discuss.tchncs.de 6 points 1 week ago (1 child)

It dumps itself if there’s not enough RAM available and there never is. Voyager doesn’t save your scroll/community position unfortunately and it just puts the draft up when you start writing your next post - no matter where you are.

[–] schipelblorp@sh.itjust.works [S] 3 points 1 week ago (1 child)

There could be a little section for drafts? Fact is, I cóuldn't find my draft anywhere, and another user here says they never find theirs either.

As far as OS, I think I've had apps that never close out. I always assumed they dumped themselves to a swap file until I opened them again. ?

parent

[–] CompactFlax@discuss.tchncs.de 3 points 1 week ago* (1 child)

Pay attention to them. They’ll lose context sometimes. Safari reloads tabs. You lose your place in Facebook or whatever. App Store goes from a search result to the homepage. Happens all the time. Some apps are better about saving context than others.

There should be a drafts section saving the post context, I agree. No idea how it would be done.

parent

[–] schipelblorp@sh.itjust.works [S] 2 points 1 week ago

Yeah, I freaked out a bit just now because CPU 9 crashed on my Mint box and I thought I'd lost my post in Firefox, but it was right there when I opened the right history tab.

I think I'm just going to avoid leaving voyager mid-composition. I can add external links and media after I submit.

parent

[–] BertramDitore@lemmy.zip 5 points 1 week ago* (1 child)

It’s a common issue for me, connected to some other common issues. I lose my place multiple times a day, lose entire drafts when the app decides to blank itself out and reload the feed on its own, and still have the problem of accidentally going to the communities list and then losing my place in the feed when it forces a refresh. And yeah, good luck finding your drafts, I never can.

I’ve liked this app for the most part, and have been using it since I came over from reddit years ago, but frankly I feel like it has not improved over time, and has in fact gotten noticeably buggy and counterintuitive as it has matured. Might be time for me (and you) to try out some others, I’ve been off the market for Lemmy apps for so long that I have no idea how the other apps have progressed.

Edit: I’m on iOS, iPhone 16 Pro, no shortage of memory as far as I know.

[–] schipelblorp@sh.itjust.works [S] 3 points 1 week ago (1 child)

I spent an hour composing a post today; 20 minutes in I remembered what happened yesterday and finished it inside a text editor.

It may partially be an OS issue, but I couldn't find my draft in Voyager, which is a Voyager problem.

Also have to say I'm pretty disappointed in this community. It's great at describing how Voyager works, but most any suggestions for Voyager is met with cold indifference at best.

parent

[–] BertramDitore@lemmy.zip 2 points 1 week ago (1 child)

100% agree. My only two full posts, on this account and my previous instance accounts combined, were to this community about issues that seemed to me to be easily fixable, and lots of people chimed in to agree, but nope, indifference.

parent

[–] schipelblorp@sh.itjust.works [S] 3 points 1 week ago

Voyager troubleshooting steps:

Have you tried a different app?
Have you tried programming your own app?

parent

[–] miseducator@lemmy.world 3 points 1 week ago (1 child)

I have a similar issue when opening a website from voyager in Firefox. When I return to voyager, it's closed and boots back up.

[–] LillyPip@lemmy.ca 3 points 1 week ago* (1 child)

Does this only happen with Firefox? Is Firefox the main other app you use? I mean, do you mostly use Voyager and Firefox, or do you use other apps more regularly?

It’s pretty normal for an app to dump its memory, and you may be attributing this to the app you use a lot, because that’s where you’re noticing.

parent

[–] miseducator@lemmy.world 1 point 1 week ago

Yeah, just when I press "Open in Firefox". Switches over to FF, opens the page normally and when I try to go back to Voyager, it restarts from scratch.

parent

[–] LodeMike@lemmy.today 3 points 1 week ago (1 child)

Android?

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

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

parent

[–] LodeMike@lemmy.today 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)

parent

[–] schipelblorp@sh.itjust.works [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.

parent

[–] LodeMike@lemmy.today 1 point 1 week ago (1 child)

Any update one day in?

parent

[–] schipelblorp@sh.itjust.works [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.

parent

[–] Quetzalcutlass@lemmy.world 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.

parent

[–] LodeMike@lemmy.today 1 point 1 week ago

Neat, thanks

parent

[–] LodeMike@lemmy.today 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)

parent

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

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

Seems like their might be something going on with yours.

parent

[–] schipelblorp@sh.itjust.works [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.

parent

[–] Quetzalcutlass@lemmy.world 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.

parent

[–] FoxAlive@lemmy.zip 1 point 1 week ago* (1 child)

I think iOS basicially closes an app when you leave it, and that's partially the reason they have such good battery life.

If you have a custom ROM like graphene, or Volla's ROM I think by default the settings are similar to iPhone where basicially nothing runs in the background and doesnt constantly ping home to google. You have to dig in the settings and let it happen.

If you have a low spec phone that might be another reason it closes it out when doing another task.