I swear I saw something like this here on Lemmy but I can’t find it.

I know android manages the RAM very differently than any desktop OS as it frees up RAM in order to have it available for other processes being third party or core ones.

I remember I saw something that you could fiddle with within the Firefox config page.

Or is it not possible on Android?

I’m using Firefox Nightly, because I think it is the only version that has a working pull to refresh.

  • AbsolutelyNotCats@lemdro.idEnglish
    6·
    1 year ago

    Cannot reply to your question but there are more firefox versions and forks that support pull to refresh:

    • Mull (If your device screen supports more than 60Hz this one may feel choppy, because Firefox’s Resist Fingerprinting setting limits the refresh rate to 60Hz since v102)

    • Fennec

    • Firefox beta (Available on GPlay)

    • kratoz29@lemm.eeOPEnglish
      5·
      1 year ago

      Thank you for the heads up, I didn’t see this when I tried FF beta, maybe I need to look again lol.

      But honestly what is the difference between beta and nightly? Is nightly unstable for daily basis? Because I haven’t found any bugs in the wild.

      • kratoz29@lemm.eeOPEnglish
        1·
        1 year ago

        Damn, I must have overlooked that because I have it installed and it is not working.

  • Jay K@lemmy.ml
    5·
    1 year ago

    I’m using Firefox Nightly, because I think it is the only version that has a working pull to refresh.

    Firefox Beta for Android has pull to refresh that works.

    • kratoz29@lemm.eeOPEnglish
      2·
      1 year ago

      Really? Does it need to be activated? I tried it and it didn’t work a few days ago.

        • kratoz29@lemm.eeOPEnglish
          3·
          1 year ago

          lol, definitely overlooked it then, thanks for the heads up!

          Although I’m struggling to see the differences in all these FF clients.

    • raker@lemmy.worldEnglish
      2·
      1 year ago

      Using Beta 114, I confirmed that setting dom.ipc.processPrelaunch.lowmem_mb to 0 MB fixes this issue which seems to happen when there’s a memory pressure in the system

  • WhoRoger@lemmy.worldEnglish
    2·
    1 year ago

    You mean you want to avoid FF flushing your tabs?

    Um, I don’t know if stock FF has that, but in IceRaven there’s an option for the exact opposite - to flush the content of tabs so that when the browser is minimised, Android is less likely to kill it outright. I assume it’s just some config option being exposed as a menu item.

    But note the meaning of the feature - if your tabs stay active, they take up resources and so it’s more likely Android will kill the entire browser process.

    IR also has pull to refresh btw, as do other forks.

    • kratoz29@lemm.eeOPEnglish
      1·
      1 year ago

      You mean you want to avoid FF flushing your tabs?

      Yeah well not permanently, as I recently moved from Chrome I think Chrome holds them on the RAM a longer time, so you can be multitasking within the browser and other apps.

      I don’t understand why IceRaven would do that, why kill the tabs to have a browser without content running in the background?

      But if it is an option as you said, maaaaybe that is what I saw here on the wild 🤷🏻

      • WhoRoger@lemmy.worldEnglish
        2·
        1 year ago

        why kill the tabs to have a browser without content running in the background?

        It doesn’t kill the tabs, just removes their content from active memory.

        If you have private tabs open and the fucking OS kills the browser, then those tabs are gone and you need to reopen them from scratch, log in again etc. With this option enabled, the browser can free up more memory so the OS is less likely to kill the browser.

        Now, with some phone brands it might not matter as their background process culling is more aggressive, but with default Android there’s a difference.

        But it’s just an option, idk if it’s disabled by default. Maybe there’s an extra config option for it somewhere.

        Yea FF on Android does take up more memory than Chromium, maybe because Chromium can share more Android core things, idk. Either way, if you run out of memory, the browser will start flushing things regardless, so it doesn’t crash.

        Chromium also does a different thing where it still shows the unloaded website but in “preview” mode and you need to refresh it anyway, which I find even more annoying.

      • SleepyWheel@sh.itjust.works
        1·
        1 year ago

        Yes. If I’m away long enough they might, but I’ve just switched back to Brave after about an hour away, and no refresh. Whereas Firefox would refresh every time I switched app, which made it unusable for me. E.g. enter username on a webpage, switch to password manager to copy password, switch back and Firefox reloads the page. Infuriating

          • SleepyWheel@sh.itjust.works
            1·
            1 year ago

            It’s a shame because I really want to use Firefox. I’m sure this is partly aggressive memory management on Android, and maybe especially on MIUI (do you have a Xiaomi by any chance?) But none of the Chrome derivatives have this issue (Brave, Vivaldi, Privacy Browser all work fine for me)

        • sugar_in_your_tea@sh.itjust.works
          1·
          1 year ago

          I’ve only had that happen on some websites, most don’t seem to do it. So maybe it only unloads heavier pages?

          That said, most of the time my password manager, Bitwarden, will prompt to auto fill on web pages so it’s not an issue. So I don’t run into this issue all that often, surely not enough to warrant switching browsers, especially when I value Firefox features like tab sync.