I’ll post a complaint about this in 5 minutes when my phone’s UI is responsive again.

  • kronarbob@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    5 months ago

    Go to settings;

    type "build number " in the search bar;

    click on the build number until you’re a dev.

    Go into developer options;

    type “background process limit”;

    Choose the maximum number of applications you want to have in background.

    Profit

    • BlessedDog@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      5 months ago

      Does this apply to processes that have battery optimization disabled? Like say, for example, if I had the limit set to five, and had 5 apps open, would I still be able to receive signal notifications (not using GCM, I think it’s webhooks)

  • Melody Fwygon@lemmy.one
    link
    fedilink
    English
    arrow-up
    4
    ·
    5 months ago

    Recents [] > Scroll ALLL the way to the beginning > Clear All

    Then invoke your Phone’s power menu and Power Off. Wait 10s and then power phone back on.

  • qpsLCV5@lemmy.ml
    link
    fedilink
    arrow-up
    4
    ·
    5 months ago

    my phone won’t even do “force stop” anymore… fairphone 5 running whatever os fairphone ships, and all force stop does is put the app in the background or whatever, if it has an issue the issue will still be there when opening it again.

  • benji@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    5 months ago

    I felt that one. Been putting off doing a backup and hard reset for months now. I can’t run two apps simultaneously unless I restart my android.

  • Taleya@aussie.zone
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    5 months ago

    I still have app killer no matter how many times google whines it’s no longer supported

  • GissaMittJobb@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    5 months ago

    Apps leaking memory in Android are just going to get automatically get killed by the OOM killer, I don’t think a restart is going to address that particular concern.

    • ericatty@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      5 months ago

      I have an S7 (yes I know it’s old) I still like it and it works - but - something happens about once or twice a month and it starts hanging up whenever a phone call connects and/or an app will get super laggy.

      Anyway, reboot fixes it (so far) and nothing else I’ve tried does.

      There’s definitely something with these older phones that is like a slow leak and the simple, easy, lasts for weeks fix is to just take 2 minutes for a full “turn it off and back on again”

      Plus the overheating when something gets stuck doing a background thing. Reboot reboot.

      I plan to use this phone until it dies, reboot stops fixing things, or needed apps are no longer working/supported.

      Slack no longer works/supported, but that one I’m just like “oh, noooo” However I expect ones I actually need to start falling off and I’ll be lucky to get a couple more years of use.

      My meandering point, some of us are still using Android phones where reboot helps a lot

      • GissaMittJobb@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        It’s definitely not out of the question that a reboot helps, but an app-level memory leak is highly unlikely to be the culprit.

        • thewowwedeserve@feddit.de
          link
          fedilink
          arrow-up
          0
          ·
          5 months ago

          Especially since Most Android Apps are written in memory Safe languages Like Java or kotlin. It is most likely Apps getting stuck doing a Background process indefinitely

          • GissaMittJobb@lemmy.ml
            link
            fedilink
            arrow-up
            2
            ·
            5 months ago

            It’s not out of the question to have ‘memory leaks’ - apps accumulating more memory by keeping around references to more and more objects - but memory leaks in the stricter sense of not deallocating objects that you no longer have references to is less likely. Regardless, the OOM killer will come for your app, no matter how good you’ve been about managing your memory, as long as someone else wants to have the memory and you’re the one who has been active the least recently.

    • yonder@sh.itjust.works
      link
      fedilink
      arrow-up
      3
      ·
      5 months ago

      That’s the beauty of android. The Google Play store is trash so use something like f-droid instead.

      • baggachipz@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        5 months ago

        I just got so tired of trying to find things that don’t suck, messing with bootloaders and custom ROMs, troubleshooting device-specific problems, all of that. I’m too old for that shit now. I get people doing it, but I just said “fuck it” and got the device that mostly Just Works and pairs nicely with my mac. I know, evil blah blah, but I also think Google is worse.

  • papafoss@lemmy.world
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    5 months ago

    Yall have to have some shady apps I have never had this issue. Apps starting on boot is not normal

      • papafoss@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        5 months ago

        I have those apps too. I’m just saying I have never had this issue. I am not saying it’s not legit it’s just strange.

        I also don’t use any social media besides lemmy so that might also play a factor. And I block A LOT of ips on my phone.