Fuck Google with a stiff wire brush.

  • ORbituary@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    7
    ·
    1 day ago

    I hope so as well. This debacle with RCS not working on GrapheneOS has been a real dick-punch. I really don’t want to go back to a stock OS.

    • rhythmisaprancer@piefed.social
      link
      fedilink
      English
      arrow-up
      3
      ·
      17 hours ago

      I have accepted no RCS. I miss some of the features, sure, but until I can get more than one person to use something like signal I’ll stick with insecure SMS thru a FOSS provider I guess.

    • other8026@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      24 hours ago

      It’s my understanding that RCS was fixed for most users after this update: https://grapheneos.org/releases#2025092700. You may need to grant permissions to Google Play Services first, then clear Google Messages’ storage, grant permissions to Google Messages, then try setting it up again.

      • ORbituary@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        4
        ·
        edit-2
        23 hours ago

        It was not. I have been on the Discord #Testing channel working with others to troubleshoot. Those steps do not work.

        It seemed to be fixed on the 20251003 release, a lot of people got it working for a while, including me. It died within 24 hours.

        • other8026@lemmy.ml
          link
          fedilink
          English
          arrow-up
          1
          ·
          56 minutes ago

          I said “most users”. There are some who are still experiencing issues, which is being looked into. Other people have had issues that were fixed by clearing the storage for Google Play, Google Play Services, Google Messages, then granting all necessary permissions before launching Google Messages again.

    • Chulk@lemmy.ml
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 day ago

      I thought the RCS thing was also happening on stock Android? Wasn’t it more of a carrier thing?

      • ORbituary@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 day ago

        It’s been largely fixed for stock with select regions still being affected. RCS is failing on GOS because the correct device ID isn’t getting reported and the verification services won’t authenticate the OS.

        It’ll work for about 24 hours, give or take, from a fresh installation, but after that RCS dies and no longer works. Any groups you were in will see you as departed and you will lose any future messages to that group.

        It’s pretty fucked.

        • Chulk@lemmy.ml
          link
          fedilink
          English
          arrow-up
          6
          ·
          1 day ago

          Thanks, I had no idea of the severity. I wonder if they’ll be able to fix it.

          I convinced my fiance to switch over to GOS because I’ve had moderate success with it for about a year now. So of course this happens as soon as she made the switch. Now she’s talking about getting an iPhone.

          • ORbituary@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            3
            ·
            1 day ago

            Ain’t that how it always goes? Best I could do with mine was to get her to use Signal. Better than nothing, I guess.