• _sideffect@lemmy.world
    link
    fedilink
    English
    arrow-up
    38
    arrow-down
    2
    ·
    3 months ago

    It’s not only that, the issue is that they release updates that slows down the device, and you get so irritated that you buy a new “faster” device

    • SuperSaiyanSwag
      link
      fedilink
      English
      arrow-up
      10
      ·
      3 months ago

      I’m not an IT expert, so I don’t know how feasible this is, but they should have at least two branches of updates. One that is strictly security and the other that are all the bells and whistles. I would love to stick with an old os if it’s not vulnerable to the outside world.

      • andrewth09@lemmy.world
        link
        fedilink
        English
        arrow-up
        11
        ·
        edit-2
        3 months ago

        It’s called a LTS (Long Term Support) builds versus the current build. There is even sometimes ELTS (Extended Long Term Support)

        (Please do not start a Linux discussion by replying to this comment)

      • xthexder@l.sw0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        3 months ago

        It doesn’t need security updates if it doesn’t connect to the Internet*, and most of these things really shouldn’t need to anyway.

        I just recently returned some smart outlets that would only work with my local Home Assistant if my Internet was up, because it all went through some cloud server. Now I’m using a combination of Zigbee and Z-Wave devices, which all connect to a local hub I have on battery backup. Now everything keeps working even if my power and Internet go out.

        *Caveat: Wireless protocols could need updating too, but at least nobody’s going to recruit my Zigbee devices into a botnet. Worst case my neighbor figures out how to turn my lights on and off.

    • Agret@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      3 months ago

      Or they take out 70% of the features it had at launch and make you wonder why you still use the thing anymore.

      • _sideffect@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        3 months ago

        Android does the same shit, and I hate it.

        I’ve had to give up phones that still worked fine because the app updates killed the responsiveness

        • UnderpantsWeevil@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          arrow-down
          1
          ·
          3 months ago

          Android does the same shit, and I hate it.

          My OnePlus has been solid for the last five years. Idk about the Pixel, though.

          • skulblaka@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            4
            ·
            3 months ago

            Yeah I’ve never had this issue with Android, not least of which is because you’re able to just root it and install whatever ROM/OS you want. If Google pushes an unstable update just wipe that shit and put Lineage on it.

            Apple only gets away with it because they put their users in a walled garden where you have no choice but to receive Apple’s updates on their timeframe. I quit that life in 2006 when they updated my iPod Touch into uselessness and haven’t come across the problem again since switching to Android.

            • Jakeroxs@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              1
              ·
              3 months ago

              Back around android 3-6 it was more common, really hasn’t been a thing for a while IMO. Have non-daily driver Oneplus 5t and 6t, both Lineage os 14, they work well.

          • _sideffect@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            3 months ago

            Yeah it was an older model phone, so it could be the reason as someone else mentioned that older android versions had that issue