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

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

  • SeductiveTortoise@piefed.social
    link
    fedilink
    English
    arrow-up
    86
    ·
    1 month 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
      ·
      1 month 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
    cake
    link
    fedilink
    English
    arrow-up
    54
    ·
    1 month 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
      40
      ·
      1 month 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
        15
        arrow-down
        9
        ·
        1 month 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
          ·
          1 month 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
            17
            arrow-down
            1
            ·
            edit-2
            1 month 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
              1 month 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
          5
          ·
          1 month 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
      ·
      1 month ago

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

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

          Nope, only from what I’ve read about it more recently. Back then I was just hyped about getting an even smarter smartphone with a better OS and all the new possibilities it brought to me. It was by no means my first smartphone, and I had already explored using my phones in interesting, useful or smart ways, but the OnePlus One felt like a very big upgrade in my daily life, especially since things were moving pretty fast on that area 10-15 years ago. CyanogenMod was definitely an important part of that improved Android experience, and I don’t think the corporation clusterfuck affected that, really, as I did not at all notice what was going on over there.

          • Lka1988@lemmy.dbzer0.com
            cake
            link
            fedilink
            English
            arrow-up
            2
            ·
            edit-2
            30 days ago

            That situation destroyed CM and its team. Lineage OS was the proverbial phoenix that rose from the ashes of CM.

            • pirat@lemmy.world
              link
              fedilink
              English
              arrow-up
              1
              ·
              24 days ago

              Yeah, I knew about LOS being the continuation of CM, and it seems to be still going strong with support for a multitude of devices, which is great!

  • Scrubbles@poptalk.scrubbles.tech
    link
    fedilink
    English
    arrow-up
    38
    ·
    1 month ago

    So who do we think? It’s not Fair phone and it sounds like it’s not oneplus. I’ll be needing a new phone within the next couple of years, if they roll it out soonish

    • kata1yst@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      16
      ·
      1 month ago

      I mean those are the first two I’d suspect too. Maybe Sony or Pico? They’re both pretty dev friendly.

      • the_weez@midwest.social
        link
        fedilink
        English
        arrow-up
        10
        ·
        1 month ago

        I actually think this could be it. Nokia has always been a little adventurous with their operating systems, and I think they are eager to claw back their old reputation.

        • Lumisal@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          arrow-down
          1
          ·
          1 month ago

          It’s not.

          Have a friend who works at a decently high position here in Finland and they actually are considering exiting the smartphone market all together because the margins are too small and they make easy more money on other things, like 5G equipment. They kind of want to move past being associated with phones basically.

          • andz@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 month ago

            Nokia just extended their existing contract with HMD for several years. Doesn’t seem like they’re going anywhere in the foreseeable future.

  • skuzz@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    33
    arrow-down
    1
    ·
    1 month 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.

  • Zink@programming.dev
    link
    fedilink
    English
    arrow-up
    32
    ·
    1 month 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!

  • commander@lemmy.world
    link
    fedilink
    English
    arrow-up
    31
    ·
    1 month 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

    • Scrollone@feddit.it
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      1 month ago

      Exactly. Google is evil, and I don’t want Google-related things on my phone.

  • fodor@lemmy.zip
    link
    fedilink
    English
    arrow-up
    26
    ·
    1 month 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@feddit.it
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 month 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 month 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
    ·
    1 month 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…

    • Synapse@lemmy.world
      link
      fedilink
      English
      arrow-up
      41
      arrow-down
      1
      ·
      1 month ago

      The only reason I bought a Pixel is for GrapheneOS and the only reason my SO has one is also GrapheneOS.

    • foggenbooty@lemmy.world
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      1
      ·
      1 month ago

      I can’t see how it would. Techies are the only people who know what GrapheneOS is, and even then it’s a small percentage of us. The average person still asks if you have an iPhone or a Samsung.

      I hope it takes off, but even if it does the dent will be small.

    • the_weez@midwest.social
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 month ago

      I would assume it will, if the SoC performance is in the same ballpark. Pixels have good NPU specs but their CPU, GPU and RAM feel like mid range options compared to snapdragons. So I don’t think that’s a high bar to hit. I don’t run graphene because I’m not buying a google phone, but I would consider running it on something else.

    • Auli@lemmy.ca
      link
      fedilink
      English
      arrow-up
      6
      arrow-down
      1
      ·
      1 month ago

      Yes it well. Their chips are pathetic and they seem to have no motivation to do anything about it.

    • Echolynx@lemmy.zip
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 month ago

      I want to try GrapheneOS. But my current Samsung phone still works. If I ever do switch, I would be looking for a Pixel on the local resale market so as to avoid giving Google money, anyway.

        • Echolynx@lemmy.zip
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 month ago

          Using current phone rather than buying a different one to replace it is a lot less ewaste.

          I am also going to see what happens with Graphene’s new partnership. I don’t really like the idea of being locked down to specific hardware.

      • sorghum@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 month ago

        It’s what I did. I bought a used pixel 8 and only regretted it after the recent strong of Google shenanigans. I’m still looking for a proper Linux phone solution in the meantime. I’d rather not have to be reliant on anything Google does in the future.

  • courval@lemmy.world
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    2
    ·
    1 month ago

    Disappointed to learn about Fairphone lagging behind in terms of security… I really wanted to get one. But still good news I guess.

    • fodor@lemmy.zip
      link
      fedilink
      English
      arrow-up
      12
      arrow-down
      3
      ·
      1 month ago

      I’m not saying the information about Fairphone is wrong, but you shouldn’t assume it’s all as bad as they made it out to be. You’re reading a marketing pitch from one group that works with one vendor saying why another vendor isn’t that good.

    • DupaCycki@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      1 month ago

      Not really a ‘Fairphone issue’ and more a general ‘smartphone issue’. The vast majority of OEMs don’t invest into security and just use random parts with mostly stock Android. Sometimes they actually make it worse by replacing AOSP apps with their less secure ones. Which sadly will become more common with Google abandoning AOSP.

      Fairphone simply isn’t focused on security. Should that change? Are Fairphone users interested in improved security?