Q
qw2b1

  • Joined Jul 8, 2024
  • qw2b1

    How did you install MBWAY, when I install MBWAY either from the Google Play Store or the Aurora Store, it breaks after i set my passcode with a message

    Para aceder ao MB WAY, confirme se ativou e atualizou os Serviços do Google Play

    With a link that leads to the settings of Google Play services

    I am using a Pixel 7a

    Ps: Currently testing https://github.com/PrivSec-dev/banking-apps-compat-report/issues/289

  • Thank you all for your answers.
    You have been a great help.
    I think i understood what i need to make my decision.
    Thanks

  • @qw2b1 Removed your statements about RMS because it's not relevant to this thread and we don't want people to harass him.

  • qw2b1 GrapheneOS is of course an open source project, and that is important. It means people can have their own builds of the OS, or that somebody can fork it etc.

    We don't mislead people by claiming that something being open source somehow magically makes it more secure, though it can help. "Advertising" as open source can be pretty disingenuous depending on how a project does it.

    I think the distinctions are pretty silly in the context of what GNU deems or does not deem "open source". Unless you're doing things that actively worsen security, you will not meet their outlandish and out of touch standards.

    In that sense, GrapheneOS is a security and privacy project. We would never consider doing something like what Purism did just to appeal to the GNU crowd if it meant worsening privacy and security.

    • GNU is an entirely unserious organization. The specific claims made about GrapheneOS make no sense.

      What does "firmware programs for installation" even mean? Are they referring to the web installer, because that's completely open source.

      and it appears that at least some of them are binaries without source code

      What does this even mean?

      It is said to be “de-Googled,” but includes a way to download and install the nonfree Google Play program.

      I wouldn't have addressed this in the first place due to how ridiculous of a statement it is, but some people in this very thread are confused themselves, so let me make it clear just so we're all on the same page.

      GrapheneOS does not come with Google services, Google Play Services or otherwise.

      We provide the option to install Google Play Services in a sandboxed manner. If you don't install that, there are NO Google Play Services by default. GmsCompat, the compatibility layer is NOT a Google service, and is completely open source, as is all of GrapheneOS.

      qw2b1 Even if there is non-free software in GrapheneOS (which technically the Google Play Services installers could count as such, since they are built into the operating system),

      Are you referring to "Apps" mirroring Play Services, or something else? If you're referring to that, then GrapheneOS by GNU's standards was fine when it had links to get them on the site and not a way to get them from within the OS itself? It would be pretty ridiculous to claim that either way.

      All in all, GNU isn't someone anybody serious should listen to in 2024. They haven't had anything relevant to say in years, and that's being generous.

      To understand how silly their entire process is, Purism essentially made their phone have firmware that cannot be updated in order to get GNU's certification. Of course, that doesn't mean the hardware doesn't have closed-source firmware. It just means you can't ship security updates to it anymore, and that's a-okay with GNU. It's just silly.

      • starkle I thought it's been said that the firmware is in fact open source for Pixels, but perhaps not free software. But I can't find a source for that.

        There are no phones with open-source firmware to my knowledge.

        Google said it wanted to make the Titan M2 open-source but still hasn't done.

        starkle What are your thoughts?

        My thought is not to take GNU seriously in any way.

        • 83639273 Thanks! This also worked for me (Pixel 8 Pro on T-Mobile USA). Worked straight away after a reboot.

          I granted READ_DEVICE_IDENTIFIERS the old fashioned way via adb:

          adb shell appops set com.google.android.gms READ_DEVICE_IDENTIFIERS allow

          The state of the permission can be found with:

          adb shell appops get com.google.android.gms | grep READ_DEVICE_IDENTIFIER

          Previously, I had:

          READ_DEVICE_IDENTIFIERS: deny; rejectTime=+2m21s554ms ago

          After enabling the permission, I have:

          READ_DEVICE_IDENTIFIERS: allow; time=+47s616ms ago; rejectTime=+7m4s585ms ago