• db2@lemmy.one
    link
    fedilink
    English
    arrow-up
    35
    arrow-down
    1
    ·
    1 year ago

    Just checked mine, 1.6 gigs of cache. Anything over a couple hundred megs is extreme.

  • zachatrocity@lemmy.worldM
    link
    fedilink
    English
    arrow-up
    33
    ·
    1 year ago

    Woah nice find. This is outta control. I think our new infinite scroll library will make this better. That should be in the next release and I’ll personally keep a close eye on this. Pretty wild. Thanks for reporting!

  • Cheesebaron@feddit.dk
    link
    fedilink
    English
    arrow-up
    29
    arrow-down
    1
    ·
    1 year ago

    LRU cache seems like a good choice for caching images. Then set a max size and/or age of items in the cache and evict as necessary. This is the defacto caching mechanism in Apps.

    • ඞmir
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      I don’t like every app having its own max size, I’d hope Android at some point starts making an automatic cache control tool system-wide (that’s not a third party app) but it seems we’re stuck with this mechanism

      • Cheesebaron@feddit.dk
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        It is a bit of wishful thinking, but could be cool if they had an AndroidX package with some kind of global caching system. Problem is though, how do you make a caching mechanism that can fit all use cases.

        • ඞmir
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Start with LRU and maybe a frequency counter to keep frequently useful data. Then go from there. Same as most apps do themselves right now but redistribute as needed; slowly take a bit away from all other apps when one app needs more

  • WhoRoger@lemmy.world
    link
    fedilink
    English
    arrow-up
    19
    ·
    edit-2
    1 year ago

    Every Android app needs to be better at handling cache. It’s ridiculous how some apps can accumulate gigabytes of old crap, sometimes not even marked as cache so one needs to wipe all the data and set up the app again from scratch.

    • Generator@lemmy.pt
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 year ago

      Many times i’ve seen people changing their phones because of low storage, and then have the same issue.
      When cleaning apps cache colde solve the problem without spending any money.

      I have SD Maid scheduled to clean apps cache once a day, most apps don’t have more that 200MB of cache, and plenty of free storage.

      On Liftoff can be easily fixed by cleaning cache on exit, some apps have this options so don’t eat all of your storage.

      • WhoRoger@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        I have SD maid too, but to actuality clear the caches automatically it needs accessibility services enabled, and that can totally fuck up Android security so I’m stuck with doing it manually. (Dunno if newer droid versions don’t have this issue.)

        There’s no doubt in my mind that the removal of “clear all cache” button that used to be in Android was purely so that partners can sell more hardware.

        I’ve begun to care about this when at one point I was running low on storage and found that even random apps like Revolut or a weather radar app can easily accumulate a gigabyte of garbage over time. So it’s not a jab against Liftoff… Android apps overall just suck at this hard.

        At least those that can export/import settings can be reset easily, but the rest… Ugh.

    • mykl@lemmy.worldM
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I assume it’s Settings > General > iPhone Storage, and then search for Liftoff using the magnifying glass once the spinner clears.

      Mine only shows 61MB in Documents and Data though so I wonder if iOS isn’t telling me everything or if there’a an Android-specific issue here.