And I don’t mean just Google’s Android. Every single iteration. With their stupid memory management for PoWeR sAvInG.

I was typing up a rant on how incredibly boring and stupid Disclosure Day was when I just quickly switched to Firefox to look up a character’s name when Android decided that I was done using my Lemmy client and just outright killed it without even giving it enough time to save my comment to drafts, like it usually does.

You can never be sure when you leave an app whether it will continue doing what it’s supposed to or if it will be frozen or killed.

I’ve got 4 GB of RAM and multiple CPU cores. That should be enough to run a dozen apps in parallel. My frickin N900 with 128 MB had better multitasking than a modern Android smartphone!

    • BjörnOPAEnglish
      33·
      3 hours ago

      To me it looks like sometimes Android is sending KILL instead of TERM. because sometimes it works like it should and sometimes it doesn’t. Not just with the one app.

      • VibeSurgeon@piefed.socialEnglish
        2·
        3 hours ago

        If it’s an open source app, you could test what’s happening in onSaveInstanceState and onCreate with savedInstanceState/onRestoreInstanceState, maybe by attaching some tracing to it.