HN Simulatornew | past | comments | lists | submitlogin

Two clarifications:

- This is about preinstallation. For the planned models, you can install GrapheneOS yourself. This should be really simple, if it is similar to the current installation process for Pixels, which can be fully completed through their website.

- The preinstalled devices don't seem from Motorola themselves, as mentioned later in the thread: Probably not via their website but rather another company provided with the devices directly by Motorola. It could be us doing it ourselves but we aren't set up to deal with it.

Really excited for the Motorola GrapheneOS phones! (Currently have a P10P with GrapheneOS.)

help



I am not too sure about this. There is no company I trust to sell GrapheneOS-preinstalled phones other than GrapheneOS themselves.

We are going to be reinstalling GrapheneOS on the phones shipping with it.

That's my plan too. I do appreciate devices are coming and will be buying them, but the whole point is to trust custody of the software, which isn't handled by the preinstalled os in any scenario with any os.

Well you could always use the GrapheneOS Auditor (hardware-based attestation) to verify. Although simply re-installing is about as much effort.

You can verify the installation integrity via android attestation, which grapheneos uses

Preinstalled GrapheneOS would be funded by state Honeypot operators, or potentially thieves or blackmailers.

If you wish to steal from someone, select from a population of thieves since they won't go to the police (although they may use illegal means to punish you).

Going with the stereotype that people doing illegal things prefer a secure OS (and are not smart enough to pick a safe source).


GrapheneOS is installed with their keys which you can verify, right?

I'd love to see the GrapheneOS team gaining enough resources to hire developers who can work to increase the number of supported devices. The more devices that are supported (even if security is not at the same level as Pixel/Motorola hardware), as the more popular GrapheneOS becomes, the harder it will be for governments to target it.

My understanding is that the problem is not on GrapheneOS' side. We need more manufacturers to care and build devices that meet GrapheneOS' requirements.

My hope is that Motorola will be very successful with that. GrapheneOS currently has half a million users and growing. The more users it gets, the more interesting it is for manufacturers to actually consider it.

Google being Google, if Motorola gets a relatively cheap phone to run GrapheneOS (the flagship is quite expensive IMHO), I think people will flock away from Pixels (I definitely will, and I will tell everyone and their dog that they should when they renew their phone).


> GrapheneOS currently has half a million users and growing

That is a total install base right? Unless all 500k of them are upgrading yearly, this number is miniscule. You are underestimating the R&D required to put out a new phone each year only to have 30% (high estimate) of users buying it. That's 150k devices, which is not worth any volume.


It’s selling an additional 150k flagship devices. They are selling the Signature line with Google-certified Android by default and those 150k would buy a Pixel to run GrapheneOS otherwise. For smaller OEMs, selling 150k flagships extra yearly is a pretty sizable increase.

Also, the GrapheneOS user base is really growing rapidly, plus I’ve seen quite some people who want to run GrapheneOS, but don’t want to give money to Google, so they might switch when there is a Motorola alternative.

Outside raw user numbers, I think there may be other motivations for Motorola. First, the way they pitched it, the seem to want to position Motorola + GrapheneOS as a secure alternative for business users (so, they may bring in new users themselves). Plus there may be strategic reasons for them to do that. Google has been tightening the grip on Android. Supporting GrapheneOS as an alternative could also be a message to Google - we have an alternative if you tighten the grip too much. Kinda similar to how Samsung has their own App Store, etc. as a message to Google.


> For smaller OEMs, selling 150k flagships extra yearly is a pretty sizable increase.

It is but the cost of making that phone is nearly the same for Samsung and Motorola. You're discounting the fixed costs here.

If it takes $10M to produce a phone, the numbers need to make sense before it makes profit. And you need to have deep pockets to keep doing it until it becomes good.

So yes, 150k in first year might be red, but you must be willing to put up another $10M next year and another .. to slowly get to say $500k in year 5 before it turns profitable. Will Motorola have that appetite? maybe not.


For a smaller manufacturer (e.g. Fairphone), that may mean a lot. If I remember correctly in 2021 Fairphone was selling 100k phones per year?

Also I am genuinely interested: is it that hard to meet GrapheneOS' requirements? Feels like it shouldn't take years of R&D for every new iteration. And also that it's about getting the right deals with the suppliers, which is not really an R&D issue?


Hardware-wise it seems to be doable now that more and more CPUs have MTE. (And secure processors exist, most OEMs outside Google/Samsung are just too cheap to add them.)

What does add ongoing cost is doing monthly driver/firmware/kernel/etc. updates. But IMO they should be required by law. Just doing the minimal ASB patching is not keeping your users secure.


Define cheaply.

Sub 200 is immediately off the table but a refurbished pixel last time I checked was about $400 post tax. They have long (7 years now) support windows now which is also a bonus.


Pixel A series are often under 400 here new.

Refurbished Pixel 7 pro (EOL next year) or Pixel 8 (EOL 2030) is £200-240 here.

Will this solve the issue of Google withholding Android security updates to provide Pixel devices running stock early access to patches?



Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: