• kae@lemmy.ca
    link
    fedilink
    English
    arrow-up
    35
    arrow-down
    2
    ·
    1 year ago

    He followed this up this morning by saying that the reason it was removed was that it was not being used. So keeping the code in there increased the overall package size.

    Spread out over billions of devices and small changes make a huge difference. He also stated metered data plans as a primary motivation.

    So tinfoil hats off.

    • Moonrise2473@feddit.it
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      2
      ·
      1 year ago

      Removed from system and moved in an automatically downloaded package doesn’t make it smaller nor use less data. The opposite.

      • kae@lemmy.ca
        link
        fedilink
        English
        arrow-up
        9
        ·
        1 year ago

        You’re referencing a different thing. This is the open source version bundled into AOSP, not the Google Play Services version.

        Directly from the source:

        So, as I suspected, Fast Pair code was deleted from AOSP because it wasn’t being used by anyone.

        And because it wasn’t being used, it was just taking up space unnecessarily. Although HalfSheetUX was only a few megabytes in size, Mainline modules are served to many millions of people, a decent portion of whom are on metered connections.

        Note: This has no implications for the Fast Pair feature you’re already familiar with. Fast Pair started out as a feature bundled in Play Services and will remain that way for the foreseeable future. This news just means there’s no longer an open source version of Fast Pair.

    • danielfgom@lemmy.world
      link
      fedilink
      English
      arrow-up
      14
      arrow-down
      1
      ·
      1 year ago

      Yes and it is worrying. Google ought to make everything AOSP and but keep anything proprietary. They have nothing to lose so I don’t understand why they are stripping stuff from AOSP.

      • limerod@reddthat.comM
        link
        fedilink
        English
        arrow-up
        9
        ·
        1 year ago

        They want people to use and be reliant on Google’s version of android with play services and Google apps. That’s what they have to lose.

        • danielfgom@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          1 year ago

          With so many OEM’s running to get Google Play services I don’t think there’s any risk they would lose that. Anyone wanting to make their own phone without Google services is going to have a hard time selling that phone.

          Mostly it’s only the 3rd party ROM’s that use it the most, and they are a tiny niche.

        • ayyndrew@lemm.ee
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          Which OEMs don’t include Play Services other than the ones that aren’t allowed to?

          • limerod@reddthat.comM
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            OEMs selling smartphones in China. And those like amazon selling fireOS based tablets, TVs, and fire TV sticks.

    • Moonrise2473@feddit.it
      link
      fedilink
      English
      arrow-up
      27
      ·
      1 year ago

      They removed a rarely used function from the free android open source project to a paid, closed source program that Samsung/Xiaomi/OnePlus/Sony/etc are already paying.

      This affects only who uses Amazon or Huawei devices (or a Google-less custom ROM)

      But while nobody cares about this specific function, Google is slowly removing features from the open source project year by year. The calculator, the calendar, the email client, and so on

      • roneyxcx@lemdro.id
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        Also both Amazon and Huawei never used the AOSP Fast Pair. Huawei has their own proprietary implementation which was there before even Google came up with Fast Pair and FireOS is still on Android 11.

      • YⓄ乙 @aussie.zone
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        edit-2
        1 year ago

        So what happens when they removed all their bloat? We get a nice clean barebone OS?

        The trash is taking itself out. Noicee

      • Possibly linux
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        I guess lineage os will have to come up with there own implementation

  • smileyhead@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    10
    ·
    1 year ago

    I’m convienced in next 5-10 years I won’t be using Android anymore. This is sinking boat, the only thing keeping me on it is that other boats are just being build.