• commander@lemmy.world
    link
    fedilink
    English
    arrow-up
    33
    ·
    1 day ago

    I’ll hold off on a new phone to watch for this. Android could be great without Google’s nonsense. An OS that has high end hardware support and continues to work on convergence with desktop Linux both by the communities development and Google’s

    • ChaoticNeutralCzech@feddit.org
      link
      fedilink
      English
      arrow-up
      29
      ·
      edit-2
      23 hours ago

      A HW manufacturer (aka OEM) will share specs and interfaces with the GrapheneOS team, who will develop an official port for the hardware, with support and everything. The OEM will allow bootloader unlocking and maybe even ship some of these phones with Graphene preinstalled, depending on what their contract with Google allows. To this day, only Pixels have officially received GrapheneOS releases because Google has documented their hardware interfaces in AOSP. Now, AOSP is no longer developed with the Pixel as a target but a virtual device, putting the future of GrapheneOS on Pixels into question (the team refuses to use reverse-engineered hardware interfaces, as they could result in bugs: for example, many Samsung cameras only expose a 16:9 section of the 4:3 sensor in the open Camera2 API; other frequent issues with custom ROMs include VoLTE, Play Integrity and bootloader relocking).

  • 𝕸𝖔𝖘𝖘@infosec.pub
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 day ago

    But if google goes on with locking out the app store with the developer verification bs, how would would this play into that? If Aurora won’t install the app or the app won’t run, then we’ve accomplished little in that area. I’m really hoping I’m missing something.

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

      Custom ROMs should be able to disable the checks. My bigger concern is what it does to the open app ecosystem as a whole.

      • cmhe@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        1
        ·
        23 hours ago

        TBH I would actually expect GrapheneOS not to disable these checks. GrapheneOS devs pride themselves to have the best implementation of the official Android security model, and enforcing signature checks is likely part of that…

        They might add additional certificates I guess, to allow their own apps, and maybe a selected few others.

        • Fiery@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          8
          ·
          15 hours ago

          Except this ‘signing’ is more of a control feature than a security feature. Just because Google markets it as a security feature doesn’t mean it is.

          • cmhe@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            12 hours ago

            Well… The Android security model, as it is implemented in stock android and GOS, is about top down control, the full trust is given to the system vendors, not the end users. No rooting for instance. From this perspective not allowing installation of apps that cannot be blocked by the system vendor, fits well with that model.

            TBH, I am not a fan of that security model. And this is my critique of GOS. It doesn’t allow the user full access to their device, so that they can check and control what each application is storing or sending to third-party servers. Instead it is on full security and allows apps to store and transfer information to which the user has no access to.

            But the system vendor/developers would have that access, because they control the whole base system.

            The focus of the Android security model and in turn of GOS is on security, at the cost of privacy or freedom.

      • 𝕸𝖔𝖘𝖘@infosec.pub
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago

        But the app might refuse to run without those checks being done. Or a new format, apkx2 I don’t know, might only be able to be decrypted with the proper key and only once verification. It’s not a new tactic. I’m very, very glad to see this type of development finally happening (though, admittedly, a couple decades later than of hoped), but it’s now a new ballgame, and google owns the stadium, the seating pricing, and concessions, the parking lot, and ticketing counter. I’m concerned we’ve waited too long. What’s GOS’s plans for this? They’re, essentially, going to have to create a new ecosystem, with most of the growing pains of new ecosystems.

  • fodor@lemmy.zip
    link
    fedilink
    English
    arrow-up
    25
    ·
    1 day ago

    Every cell phone manufacturer has some interest in diversifying the operating systems. Because Google develops Android and sells its own cell phones, it has an unfair market edge. And now Google is threatening to filter out apps that it doesn’t like which makes the risk even higher.

    So we can be sure all of the other major manufacturers of Android phones have considered if they’d like to support other distributions.

    • Axolotl_cpp@feddit.it
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 day ago

      Maybe they will make deal with other distributors to ship their exclusive app stores and so that would be a good economic move for them

      • Batmorous@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 day ago

        All I know is that whoever partners up with PostmarketOS, Mobian, and Ubuntu Touch will win big

  • Seefra 1@lemmy.zip
    link
    fedilink
    English
    arrow-up
    24
    arrow-down
    1
    ·
    2 days ago

    manufacturer will offer GrapheneOS support on future versions of their existing models, priced similarly to Pixels.

    Great, so I still won’t afford it…

  • Avid Amoeba@lemmy.ca
    link
    fedilink
    English
    arrow-up
    119
    ·
    2 days ago

    There aren’t too many OEMs that sell worldwide. So that would be one of Samsung, Sony, Moto, OnePlus.

      • atomicbocks@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        65
        ·
        2 days ago

        I agree, Motorola is owned by Lenovo. They have found middling success with the return of their Razr line and with phones in the lower to mid tier range. But they really want something super flagship. Something like the Think Phone would have probably sold really well with a Graphene option.

        • Avid Amoeba@lemmy.ca
          link
          fedilink
          English
          arrow-up
          38
          ·
          2 days ago

          Device hardware, firmware, and software are integrated to protect your most sensitive data from mobile threats. With Moto KeySafe, PINs, passwords, and cryptographic keys are isolated from other device data for an added layer of high-level security.

          Yeah this sounds like what Graphene insists on.

          • deafboy@lemmy.world
            link
            fedilink
            English
            arrow-up
            5
            ·
            1 day ago

            That sounds like a fancy speak for a Trusted Platform Module. Isn’t some kind of TPM mandatory to obtain a google certification for a new device?

        • Auli@lemmy.ca
          link
          fedilink
          English
          arrow-up
          7
          arrow-down
          12
          ·
          2 days ago

          The only way a graphene is phone gets major adaptation is if you could use pay with it.

          • atomicbocks@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            17
            arrow-down
            7
            ·
            2 days ago

            I think people overestimate that feature. Where I live you still have to hand your card to the teller most of the time and nobody is handing their phone over for tap to pay.

            • johan@feddit.nl
              link
              fedilink
              English
              arrow-up
              9
              ·
              edit-2
              2 days ago

              I pay with a normal card but I’d say the majority of people around me pay with their phone.

              Also, I need to use my bank app to pay for things online. I scan a QR code and confirm the payment with a pin or fingerprint. Correct me if I’m wrong but I think many bank apps also don’t work properly with graphene.

              Edit: maybe I’m getting confused, I thought bank apps normally needed google play services and that because of that they don’t work on grapheneOS, but I don’t know if that’s correct

            • brbposting@sh.itjust.works
              link
              fedilink
              English
              arrow-up
              3
              ·
              2 days ago

              hmm how bout round the world?

              Like Germans prefer cash but tons go all digital—yuge in China for example, Apple Pay’s big stateside (USA)…

              Curious your region btw to expand my knowledge on this

              • atomicbocks@sh.itjust.works
                link
                fedilink
                English
                arrow-up
                2
                ·
                2 days ago

                I live in the US and I also just got back from a 10 day trip that had me in 6 different airports around the US and saw basically nobody using their phones to pay. I saw a bunch of people using the translate app, the camera, FaceTime, Apple wallet for boarding passes, but no tap to pay.

                I think it’s because the places that use it also have their own apps, like Starbucks. You can order and pay in the app and if you are likely to setup Apple Pay you are probably fine going all the way with the app too. The same is true of Walmart and other major retailers who also specifically don’t take Apple or Google pay because they want you to use their app.

                • shinratdr@lemmy.ca
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  ·
                  edit-2
                  1 day ago

                  It’s heavily used everywhere else in the world, the US is well-known to lag behind on payment technology. It’s like travelling back in time when you go there.

                  I pay with my phone literally everywhere in Canada, haven’t opened my wallet in months. I was in the US last year and they didn’t have mobile payment terminals at restaurants so you always had to pay for sit down service at a counter, always wanted me to sign for tap, kept calling it Apple Pay instead of tap or contactless, had places that would only swipe a physical card which isn’t even allowed in other countries anymore, it’s crazy.

                  Walmart takes tap in Canada, they were one of the last holdouts. The “individual app for each service” thing is very American, even American companies abroad don’t do it because they’ll lose business. It’s the same thing with cash transfers. There are 100 different private ways to send money in the US. PayPal, CashApp, Facebook Pay, Apple Pay, Venmo, etc.

                  None of those exist in Canada because we just have Interac e-transfers. Hard to compete with free & automatic support by every bank account in the country. Other countries have similar systems. The US has Zelle but as far as I know that was implemented way later and doesn’t have the mindshare.

                • ilovepiracy@lemmy.dbzer0.com
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  arrow-down
                  1
                  ·
                  2 days ago

                  So random that the USA is lagging behind in this regard, travelled Europe - everyone using phone pay, and in Australia my home country, it’s pretty much the only way people pay nowadays.

          • Lka1988@lemmy.dbzer0.com
            link
            fedilink
            English
            arrow-up
            9
            arrow-down
            2
            ·
            2 days ago

            Not really. The kind of people this ROM caters to are exactly the kind of people who don’t use Google Pay to begin with.

        • Brown5500@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 day ago

          I have had several versions of the Moto G family and they’re pretty easy to repair. Usually under $30 for a screen. Trickiest part is glueing the back panel back on.

      • Revan343@lemmy.ca
        link
        fedilink
        English
        arrow-up
        10
        ·
        2 days ago

        Oh man, please. My current Motorola could use replacing, official Graphene support would be fantastic

      • Zink@programming.dev
        link
        fedilink
        English
        arrow-up
        4
        ·
        2 days ago

        Ooh yeah let’s get a 6" 2025 take on the OG Motorola Droid with the slide out keyboard, to make it more linux-phone-y.

        • picnic@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 days ago

          How come? I’d bet they’d be the most easiest “oem” to get started with.

          All western ones will be on the mercy of google licencing, so I’d guess no one wants to burn bridges.

          • kalapala@sopuli.xyz
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 day ago

            I’m quite sure no one would consider Chinese company as safe option for privacy and clearly security focused phone.

            Also as Sony already has the Sailfish support the company is likely going to be Sony.

        • Avid Amoeba@lemmy.ca
          link
          fedilink
          English
          arrow-up
          1
          ·
          2 days ago

          I wouldn’t bet on it. Lenovo is used across North American corporations, banks and government institutions.

    • IBoris@lemmy.world
      link
      fedilink
      English
      arrow-up
      41
      ·
      2 days ago

      I hope Sony simply because I want a headphone jack and an MicroSD card reader. Their phones are already pretty bloat free and their custom apps, usually focused on the camera system, would mesh very well with GrapheneOS. Would be a great way for them to become relevant again.

      • viking@infosec.pub
        link
        fedilink
        English
        arrow-up
        2
        ·
        14 hours ago

        Samsung is also a synonym for useless bloat, locked boatloaders, intrusive ads, and every other hostile feature ever. They are the last one to open up their phones.

  • SeductiveTortoise@piefed.social
    link
    fedilink
    English
    arrow-up
    89
    ·
    2 days ago

    According to details shared on Reddit, the partnered manufacturer will offer GrapheneOS support on future versions of their existing models, priced similarly to Pixels. These initial devices will feature flagship Snapdragon processors, which GrapheneOS notes provide significantly better CPU and GPU performance compared to Google’s Tensor chips. The Snapdragon platform also bundles high-quality wireless connectivity, eSIM support, and decent image processing capabilities directly into the system-on-chip.

    Oh thank you. Let’s hope for something nice for a change.

    • Fizz@lemmy.nz
      link
      fedilink
      English
      arrow-up
      41
      ·
      2 days ago

      This might be it. This might be the alt phone to defeat all others. Flagship chip + graphineOS features and long term support is a killer killer deal.

  • Lka1988@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    58
    arrow-down
    1
    ·
    2 days ago

    I’m skeptical. Even knowing how paranoid Daniel is about, well…everything.

    Who remembers the last time a custom ROM got an OEM deal? It is the reason Lineage OS exists today…

    • Lumisal@lemmy.world
      link
      fedilink
      English
      arrow-up
      42
      ·
      2 days ago

      With everything Google is doing with Android, they might not have a choice. It’s either this or possibly one day no longer being able to work on Graphene.

      • skuzz@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        17
        arrow-down
        11
        ·
        2 days ago

        Graphene would be better off cutting themselves off from Google’s OS future entirely and pivot the fork as quickly as possible to remove all dependencies. Probably too arrogant to consider it, though. Also becomes much more work.

        • warmaster@lemmy.world
          link
          fedilink
          English
          arrow-up
          18
          arrow-down
          1
          ·
          2 days ago

          Google will forever control Android. I would prefer if he just worked on Linux (phone & desktop) to the benefit of all.

          • skuzz@discuss.tchncs.de
            link
            fedilink
            English
            arrow-up
            15
            arrow-down
            1
            ·
            edit-2
            2 days ago

            You’re under-thinking it.

            In pseudo-correct but probably not order:

            • Step 1: Collect underpants
            • Step 2: Keep receiving Google security updates but stop updating Google mainline
            • Step 3: Start replacing the underbelly to just raw Linux (or BSD or whatever) and slowly shift the “Android” portion to a VM/container
            • Step 4: RIL and other stuff (probably should happen first) have to be packaged up and become their new entity on the modem side (also probably the biggest challenge, but manufacturers and ODMs provide dev kits)
            • Step 5: ???
            • Step 6: Once the Android side is safely firewalled away from the core OS, start embracing something like PostmarketOS
            • Step 7: GUI/graphics are built out with the Android pieces still running in a container
            • Step 8: Start writing applications that replace the Android applications, go one by one, remove dependence on each Android application as you go while still maintaining compatibility (I mean the core OS ones that make the device at least basically functional, the F/OSS devs will have to each rewrite/change their apps, or some other magic can be inserted here that isn’t really magic.)
            • Step 9: Once the OS itself is beefed up enough, retain Android container for the needs of some for some uncomfortably long frustrating time to maintain, but not too long
            • Step 10: Have Obtainium/F-Droid/etc. all simultaneously pivot and start providing apps for the native OS as well as maintaining backwards compatibility with the Android apps in the container
            • Step 11: Once some magic point, forced or otherwise happens, sunset the Android portion of the app stores. Keep the containerized Android around a little longer
            • Step 12: Sunset the Android container, at this point the phone should be running 100% “native” OS and apps and store
            • Step 14: Profit!

            There are industry blueprints for this. Apple is probably the best example of how to implement these shifts, from OS 9 (co-op MT proprietary OS)->OS X (BSD-NextStep-based Unix OS), 68k->PPC, Replacing Unix underpinnings with Apple Frameworks, PPC->Intel, OS X->iOS, Mac from Intel->ARM, etc. etc. They frequently used containerization to keep the old running while the new was built up around it and replaced. It is a solid proven design pattern.

            And edit72: I’m not just saying “hey magic people do this” - I’ve done this shit. I’m down to help, and I will. But the project owners need to step up for some actual work instead of just putting potpourri on something someone else built. Annoying side-story, I figured out how to cross-compile/rebuild/fix dependencies on a CPAP app called Oscar so it would be ARM-native on ARM Macs. Couldn’t figure out how to contact the devs after much digging to let them know, so. I have 1 of 1 copy of that app running ARM-MacOS native. Would be neat to help them replicate it though.

            • ProdigalFrog@slrpnk.net
              link
              fedilink
              English
              arrow-up
              4
              ·
              edit-2
              19 hours ago

              I think that sounds like a damn solid plan, personally. Not sure if the GrapheneOS devs would go for it. The lead dev (who I think stepped down, so may not be a factor now) had some strongly negative opinions towards a Linux phone due to all of its security holes compared to Android, but like… It’s not as if those things couldn’t be addressed like you describe. It would just take time.

        • rirus@feddit.org
          link
          fedilink
          English
          arrow-up
          4
          ·
          2 days ago

          Google has more people working in Android then GrapheneOS does, it’s not possible for them to go completely independent.

    • pirat@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      23 hours ago

      I dearly remember my OnePlus One with CyanogenMod, if that answers your question?

  • Zink@programming.dev
    link
    fedilink
    English
    arrow-up
    37
    ·
    2 days ago

    I can’t wait to hear more. Please just make a phone that I’ll want to buy. My phone is 4 years old and there’s just nothing I want to replace it with yet.

    It has become less and less of an issue over time though. Not only have I gotten used to using my phone FAR less with positive health results, but I have set myself up to have access to my Linux PC during the “chill with the family on the couch” times in the evening when one might zone out on their phone for a bit. That’s what I’m using right now!

  • skuzz@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    38
    arrow-down
    1
    ·
    2 days ago

    Qualcomm isn’t exactly the best vendor to choose either. They’re US-based, closely-aligned with the US government as a military contractor, and the baseband/processor are heavily integrated on many chipsets, even sharing memory. That means a compromised carrier network could twiddle bits that the operating system sees, if they so wanted. Among many other issues.

    There’s something about a Samsung Exynos designed to spec by Google that is actually more desirable even with the lack of compute performance. More fingers in the pot, less chance of some sneakiness working its way in.