Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • GOS no longer depends on Google Pixel, and honestly, they should focus on Motorola as the main focus and ditch Google future releases.

    We should receive the first Motorola phones compatible with GOS somewhere in 2027.

    by h4kunamata
  • My pixel 7 is starting to get long in the tooth, I know I'll run it into the ground but I'm starting to wonder where I'll go for the next one now that Google is increasingly locking down their platform.
    by Pxtl
  • Not surprised, since it wasn't used in Android to begin with they probably thought nobody will notice if it's removed. And indeed, for the vast majority of people nobody will notice.
    by podocarp
  • Quite a bad signal-to-noise ratio in this link.

    It's an emotional discussion about Google not supporting MTE on Pixel 11 (old news of August, GrapheneOS had to roll back that statement in September [0]).

    Now the question is whether MTE will be enabled by Google as part of a future OS-upgrade, to which there is no definite answer AFAIK

    [0] https://news.ycombinator.com/item?id=49536384

    by rickdeckard
  • Most recent comment from them (9/30)

    https://discuss.grapheneos.org/d/41564-pixel-11-doesnt-yet-m...

    GrapheneOS:

    ``` We're not going to add support for the Pixel 11 series unless it ships MTE support. It has hardware level support for MTE but it shipped without firmware support for it. It's unknown why that's the case and it could be due to flaws in the hardware implementation which have to be worked around. It isn't yet clear if it's going to support MTE but we've decided we won't support it unless it ships. Android 17 QPR2 Beta launched for the Pixel 11 after we made our initial posts about this and added preliminary firmware support for MTE while keeping it fully disabled for the OS even as a developer option. It isn't clear if something is severely wrong with it or not yet so we can't make any commitment to supporting the Pixel 11 series. ```

    by jonaustin
  • >It appears Google cut an important security feature to save money.

    If you're doing comms for a serious project, it's probably best not to speculate on the justification of an internal decision at a different org, even if you're reasonably sure.

    by rgblambda
  • The Pixel 11 is the first Pixel phone to be released after the RAMpocolypse. It has made a lot of compromises in the name of lowering cost. I am definitely going to skip that generation. I tend to upgrade every 3 years, but there really isn't a big driver to do so right now. My Pixel 8 is holding up great. If I broke it and needed to buy a new phone today, I'd probably get a used Pixel 10 instead of a new 11.
    by aftbit
  • As others have said, this is not the most recent status update (it depends on future Google changes in QPR1 or QPR2).

    The much more interesting recent news IMO is that Google is not allowing (non-Samsung) OEMs to sell devices with GrapheneOS:

    https://news.ycombinator.com/item?id=49946698

    See the last paragraph.

    For example, non-Samsung Android OEMs aren't allowed to directly sell devices with GrapheneOS and Google will only permit it within a quota. It can and is being worked around and there will be devices sold with GrapheneOS as the stock OS without Google restricting how many can be sold.

    My guess is that the workaround is that Motorola sells them with Google-certified Android. A third-party (non-OEM) buys them in bulk and preinstalls GrapheneOS.

    But this is really end-90s/begin-00s Microsoft levels of anti-competitiveness. I'm surprised that (particularly non-US) regulators are not investigating them yet.

    by microtonal

Explore Birbla archives