• Moonrise2473@feddit.it
    link
    fedilink
    English
    arrow-up
    0
    ·
    10 months ago

    A forced nag screen “please buy a new phone to continue” seems shitty, can’t they just stop targeting that specific android version instead of bricking the functionality with an automatic update?

    I don’t see the issue of using an older version of Android auto on an older phone, just stop getting new features…

  • jayandp@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    10 months ago

    You can probably just disable auto updates for Android Auto and the apps you use with it, but inevitably things will start breaking, like Play Services APIs that Android Auto relies on, or the APIs those older third-party apps you use rely on.

    It sucks, but it was kinda inevitable for a system that has so many moving parts.

    • Moonrise2473@feddit.it
      link
      fedilink
      arrow-up
      0
      ·
      10 months ago

      For Android auto you can’t really disable automatic updates as it checks by itself and refuses to run if it’s too much outdated

  • setVeryLoud(true);@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    10 months ago

    Why hasn’t someone made an open-source implementation of the Android Auto client?

    We already have open-source implementations of the AA head unit, and we have the AAwireless project.

    I’d be kinda cool to run Android Auto on a Linux phone.

  • reddig33@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    10 months ago

    This makes no sense to me. How do these two devices that are currently working together stop functioning? Does it require updating/auto updating the software on your phone to kill it? Seems ridiculous.

    Or is this saying newer head units installed in cars might require a newer version of Android Auto that won’t work on an older phone OS?

    • jemikwa@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      0
      ·
      10 months ago

      This looks to be Google ending support for the Android Auto framework on older Android versions, that’s all. It’s not about the car, it’s about the phone.

      • potustheplant@feddit.nl
        link
        fedilink
        English
        arrow-up
        0
        ·
        10 months ago

        I mean, Android Auto runs on your phone and just transmits the video/audio to your car so yeah. It’s just like any other app dropping support for older versions of the OS.

  • IHeartBadCode@kbin.social
    link
    fedilink
    arrow-up
    0
    ·
    10 months ago

    What’s getting yanked is that older phones won’t connect to Android Auto enabled vehicles if the phone is running Android Nougat. It must be Running Android Oreo or later.

    For those not remembering, Nougat was released in 2016 and went out of support in 2019. By the most recent metric (Dec. 2022) about 4% of all Android devices currently run Nougat. So this will affect all fifteen of the people still running this OS.

    Most devices that were originally sold with Nougat have an upgrade path to Oreo. The bigger problem is folks who purchased devices with Marshmallow (orig. 2015) or Lollipop (orig. 2014) who stopped receiving upgrades past Nougat. These are the devices that will most likely be impacted by this change.

    Personally, I like to keep my devices for at least five years, so them deprecating 2016 and earlier is okay with me.

    • erwan@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      10 months ago

      We need to get to a point where smartphone work for more than 5 years. Hardware wise the battery is the only part that is guaranteed to need to be replaced.

      Now whether they do it by stopping the race on Android version or supporting every device is up to them.

      Desktop OS (Windows or Linux) support any version as long as the PC is powerful enough. Why on phone we’re limited not by the capabilities of the CPU but its release date?

    • Skull giver@popplesburger.hilciferous.nl
      link
      fedilink
      English
      arrow-up
      0
      ·
      10 months ago

      On the one hand: I don’t see a reason for Google to keep supporting old versions.

      On the other hand: pushing an update to an old device and sabotaging it by showing an “install updates” popup (as if that’s even possible for devices still running Android 7, that’s bullshit) is just dickish.

      The old version of Android Auto works perfectly fine. Show a popup once if you want (“your device will no longer receive Android Auto updates, third party apps may stop working”) but don’t actually disable anything that’s working perfectly fine.

      Google pulled that shit before. I would understand if they had a customer support department that’d get flooded when newer hardware stopped working, but all Google has is a forum that no Google employees ever pay any attention to.

      • XTornado@lemmy.ml
        link
        fedilink
        English
        arrow-up
        0
        ·
        10 months ago

        The issue is they probably want to change serverside stuff without caring about the old stuff and the alternative to the update and it’s prompt is that it will simply crash, show errors, hang or whatever…

        • Skull giver@popplesburger.hilciferous.nl
          link
          fedilink
          English
          arrow-up
          0
          ·
          10 months ago

          I don’t really see what server side stuff an app on the dashboard of a car would need. Their Google Maps API works all the way back to the one installed with Android 2, and failing that users can install a number of navigation apps. Same with their music app (they already killed Play Music anyway).

          The only thing I can think of is that they’d be killing Google Assistant on old phones, but that wouldn’t mean the rest of Android Auto couldn’t still work.