| ▲ | microtonal 4 hours ago |
| 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.) |
|
| ▲ | ysnp 4 hours ago | parent | next [-] |
| I am not too sure about this. There is no company I trust to sell GrapheneOS-preinstalled phones other than GrapheneOS themselves. |
| |
| ▲ | Peacefulz 3 hours ago | parent | next [-] | | We are going to be reinstalling GrapheneOS on the phones shipping with it. | | |
| ▲ | snapplebobapple 3 hours ago | parent [-] | | 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. | | |
| ▲ | AmazingEveryDay 3 hours ago | parent [-] | | Well you could always use the GrapheneOS Auditor (hardware-based attestation) to verify. Although simply re-installing is about as much effort. |
|
| |
| ▲ | robocat 2 hours ago | parent | prev | next [-] | | 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). | |
| ▲ | palata an hour ago | parent | prev | next [-] | | GrapheneOS is installed with their keys which you can verify, right? | |
| ▲ | preisschild 2 hours ago | parent | prev [-] | | You can verify the installation integrity via android attestation, which grapheneos uses |
|
|
| ▲ | EmbarrassedHelp 2 hours ago | parent | prev [-] |
| 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. |
| |
| ▲ | palata an hour ago | parent [-] | | 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). | | |
| ▲ | bitpush 38 minutes ago | parent [-] | | > 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. | | |
| ▲ | palata 27 minutes ago | parent [-] | | 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? |
|
|
|