Oddbean

No. Even Gmail gets killed from time to time. It all depends on the amount of memory being used by all of your apps. If they need more, something will get killed. I need to change my architecture to store read positions in all tabs so that I can recover it. The issue is that encrypted storage on phones are quite slow. So, scrolling and saving things is not a good idea. I need to batch all these things up.

Android forces each app to be with in 512MB memory, with some exceptions for 1GB ones. The browser will take a lot. Indie non-native apps usually take a ton of memory. Apps that play video or deal with large images also take a good amount just because of the content. So, it's not that difficult to reach maximum. + Amethyst has a growing cache issue. We clean a lot of things your are not seeing anymore, but many events still stay and it grows until it explodes. For regular users this doesn't happen because Android usually kills Amethyst before the cache even passes 50MB or so. But for "pro" users, the cache might grow so much that it triggers its own destruction. This is specially true if you see a lot of GIF profiles. Many animated profile pictures use 20-50MB. If there are too many on the screen, like on the Notification's little profile parties, it will easily pass over 512MB and then it's up to Android to decide to kill or not. And what to kill. Sometimes Android just kills threads and leaves things in an inconsistent state. But those are rare.

Wait, performance or posts jumping around? Performance should be pretty good these days, especially on higher-end devices. What are you seeing? I am currently fighting the video player cache which hangs for a few milliseconds when opening new videos and is quite annoying. But other than that, Amethyst should run smoothly. You can go to the phone Settings/Apps/Amethyst and "Force Close" it to clear the memory cache and see if that was your source of issues.

I will try to figure out what can be happening with the jumping posts. I am not sure what can trigger that. The only code that makes that jump is a click on the home tab twice. But yeah, Amethyst also downloads 50MB or so on every cold start (all your posts, all your DMs, all your notifications, etc). So, it's a 50MB over Tor issue. I need to reduce that amount and spread it better over the loading time.

i have noticed jumping in the thread view. fairly easy to reproduce, you open a thread that is longer than the screen, and scroll up, it will keep jumping back to the post you opened. i wasnt gonna mention it because i dont wanna distract AT ALL from relay feeds 😂

Yeah, that has been fixed. I am just delaying the new release to finish the Blossom integration that nostr:nprofile1qqsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36cpz4mhxue69uhhyetvv9ujuat50phjummwv5hszymhwden5te0wahhgtn4w3ux7tn0dejj7qg4waehxw309an8yetwwvh82arcduhx7mn99uuwx66a has been bugging me about.

nostr:nprofile1qqsw9n8heusyq0el9f99tveg7r0rhcu9tznatuekxt764m78ymqu36cpz4mhxue69uhhyetvv9ujuat50phjummwv5hszymhwden5te0wahhgtn4w3ux7tn0dejj7qg4waehxw309an8yetwwvh82arcduhx7mn99uuwx66a hope its worth 😂 #relayfeeds #soclose

Some apps are "active apps" that run in the background even when you're not using them, like signal, VPN, or amber/citrine. You see all active apps in the bottom right of the notification drawer. Might this help to not kill amethyst?

Amethyst should never run in the background (besides the seconds that it takes to process notifications). If the app is running then there is something wrong with the setup. I have noticed that some graphene users find the app running in the background. Others have forced the app to keep running. It doesn't seem to be happening on Pixels and Samsungs.. I am still investigating what could be the issue.