grapheneos

That's available here:

https://www.motorola.com/us/en/p/phones/signature/motorola-s...

There's a picture at the top of the article. The regular page for the device is available here:

https://www.motorola.com/us/en/p/phones/signature/motorola-s...

It's a news post with detailed information. The main page for the device is available here:

https://www.motorola.com/us/en/p/phones/signature/motorola-s...

> would need to pay for a license to use it for new product lines

Also, Motorola Mobility would have no obligation to accept it.

https://www.sec.gov/Archives/edgar/data/1495569/000119312510...

All of the camera features should end up supported. We support using Pixel Camera on Pixels and plan to do the equivalent for the Signature 27. It's not a priority for launch but rather will likely be added afterwards. We plan to support other relevant hardware features too but there isn't much else important beyond the camera functionality and app.

How do you even draw the connection between this person not posting on social media since August 23rd and that somehow being a problem with GrapheneOS? What could that possibly have to do with GrapheneOS>

Pixel 11 was released in August and he asked about it on Matrix on August 31st. Therefore, he didn't disappear after August 23rd. We replied on September 1st and can now see his client sent read receipts afterwards.

There's nothing public about anything happening with him. There's certainly no basis for claiming it has anything to do with GrapheneOS. The post above is making a completely baseless claim about GrapheneOS based on someone who said they use it and has no involvement in the project. The claim is based on him last posting on X on August 23rd and previously posting about using GrapheneOS. That doesn't indicate he disappeared and certainly doesn't mean it had anything to do with GrapheneOS in any way. He likely just stopped posting on X.

Those are outrageous fabrications as part of your serial lying and bullying towards the founder of GrapheneOS. He has been repeatedly targeted with swatting attacks aimed at killing him. It's verifiable from Toronto police records available upon request. That's an objective fact and pushing outright fabrications about it gets you nowhere.

Rossmann is a Kiwi Farms user with a career based around serially dishonest rant videos attacking people and companies. He's not a credible source at all. He thoroughly lied about what had happened because he was scared he would be exposed for what he'd done and decided to harm as much as he could. We had no intention of publicly exposing his abuse but he decided to do this anyway. He'd publicly live streamed himself engaging in vile bullying towards our founder who he'd openly helped direct harassment towards with months of public jabs and support for harassment content. His video published later the same day was to make excuses for what he'd done. He lied about no longer using the OS, lied about what had happened and nearly everything else about it.

GrapheneOS isn't based on the stock OS of the devices it supports. It will be the same GrapheneOS on Motorola devices as it is on Pixels. It's only the firmware, drivers and other device support code which will be different. We'll gradually work on supporting all the hardware features. We plan to add support for installing and using Motorola's camera app similarly to how we support using Pixel Camera on Pixels.

It's worth noting Motorola Mobility owns the Motorola trademark and can use it for any purpose. Motorola Solutions has a perpetual but very limited license for the trademark from a subsidiary for holding the trademark owned by Motorola Mobility. Motorola Solutions can continue making Motorola branded products in the same spaces as they did before but can't enter new spaces with the brand. Most people wrongly assume it's the other way around since Motorola Solutions is the original legal entity. They kept the legal entity the same for the company focused on government contracts and kept the trademark for the faster moving retail focused company where the brand is more important.

That's not an inconsistency but rather the only way to reliably wipe user data. It would be completely broken to attempt wiping data by zeroing the userdata partition. That wouldn't get rid of all the data from the SSD even with secure erase commands for overwriting it.

A modern SSD has both static and dynamic wear leveling. An SSD redirects writes to the free blocks with the least wear and also moves around used blocks to free up the least heavily written parts of the storage. An SSD with a proper whole drive secure erase implements it by securely wiping keys.

You made an inaccurate attack on GrapheneOS and included a personal attack on the founder of the project with no basis too.

We're more confident in our ability to properly support it long term than Pixels. Pixels did pull the rug out from under us and everyone else relying on them having AOSP support. We had to do a lot of work to keep supporting them, to add support for new Pixels and to keep up with new releases. We have to backport the drivers from QPR1 and QPR3 to the yearly and QPR2 releases on an ongoing basis along with much more. Motorola is doing more than we expected them to do. They're helping port and maintain GrapheneOS for their devices.

Motorola has a lot of budget devices and wants more affordable devices to support GrapheneOS too. Qualcomm hasn't yet made MTE available for anything below a flagship SoC likely priced at a couple hundred dollars per phone. We chose not to remove MTE as a requirement in order to support more devices and that's entirely our decision.

Motorola is providing us with the drivers/firmware we need, publishes kernel sources on GitHub rather than behind a form for a tarball and has MTE from launch.

Pixel 11 series should get MTE with Android 17 QPR2 and we plan to support those once they have it. Our requirements were not lowered due to Pixels missing a security feature. We had Pixel 11 support essentially completed but didn't ship it due to this. We didn't know it was going to get fixed via updated firmware but that now appears to be the case. We were expecting that we'd have to skip supporting the devices after doing most of the work.

There will be multiple cheaper Motorola devices with GrapheneOS in the future. This is the highest end flagship with the SoC alone costing more than low end devices. There are already budget Pixels with GrapheneOS. A used Pixel 8a can be found for $200 and has over 4.5 years of support remaining.

There's no Pixel with a flagship SoC. Signature 27 has over 2x higher GPU performance, ~60% higher single threaded performance and ~80% higher multithreaded performance. It also has higher end cameras too. Pixel 11 Pro XL is cheaper but at the cost of having budget Snapdragon performance. Tensor is acceptable in the 'a' series Pixels and helps provide extremely good updates and security compared to other budget devices since it matches the flagships. A flagship Snapdragon SoC likely costs $200-$300 and combined with the fancy cameras fully explains the price difference.

It should be similar than Pixels and perhaps without the internet requirement. Details will definitely be made available.

There will be lower end devices supported too but MTE is currently exclusive to flagships for Snapdragon. The shortages for RAM and also SSDs are making computers very expensive in general. Google increased the Pixel 11 prices and also downgraded RAM for the Pixel 11 Pro base model at the same time. The RAM shortage has only gotten worse since then. Google also has a lot more leeway since they use their own in-house SoC which is nowhere close to being a flagship despite being used in flagship priced devices. They're likely saving a couple hundred dollars per flagship Pixel due to their Tensor SoC compared to a Snapdragon flagship.

That's only assembled in the US. The important components such as the SoC aren't made in the US.

There will be more devices supported in the future. It had to start with flagships because Qualcomm doesn't yet provide MTE for their lower end SoC variants. Even the Snapdragon 8 Gen 5 didn't have MTE, only the higher end Snapdragon 8 Elite Gen 5 which was a hard blocker for Motorola Signature 2026 support. However, there's a lot of other stuff which had to get done and the extra time was needed regardless.

We plan to add support for using their camera app similarly to how we did it for Pixel Camera. Our own camera app will also be heavily improved over the next year.

Signature 27 has USB-C 3.2 Gen 2 with audio output and DisplayPort 1.4 alternate mode. It does have UWB. Look at the official specifications:

https://www.motorola.in/smartphones-motorola-signature-27/p?...

It definitely isn't US exclusive. We aren't sure when it will launch in each country and don't have a list. We'd be quite surprised if it didn't launch in Canada though.

Motorola has worked on implementing all of the hardware and firmware security features needed by GrapheneOS. They're helping us port GrapheneOS to their devices themselves and will be helping maintain it. They're also going to be providing us with the driver and firmware code we need and we'll have an opportunity to help harden it. It will be much better than Pixels when it comes to this. We won't have to do reverse engineering and won't be stuck with what's provided since we can get things improved or fixed.

We use frontier AI models to review all our code but it hasn't replaced human review and humans need to review the output from it. It adds significantly more work and has resulted in a lot of issues being fixed.

We're not currently putting a large amount of resources into finding Linux, AOSP or Chromium vulnerabilities this way because many others are doing it with far more resources including Google. There are much higher impact things for us to focus on instead. Our focus remains systemic privacy and security improvement rather than case-by-case fixing of bugs. We definitely do that much better through shipping Linux and Android patches much faster than the Pixel OS along with fixing many issues ourselves but it's not our priority for the most part. Certain parts of it are priorities such as finding and fixing VPN leaks because Google doesn't consider it to be a relevant security issue.

A used Pixel 8a is a great option for trying GrapheneOS. It's still one of the recommended devices with over 4.5 years out of the original 7 years of support remaining.

Fairphone has a transparency report on their website about the manufacturing and supply chain which nearly entirely only provides a list of the companies, the location of their HQ and a link to their website for a subset of the companies. There's no information provided on the working conditions, pay or environmental impact of the supply chain. Past posts with vague details about this were mainly about their original ODM and they switched to 2 different ODMs since then. T2Mobile is their ODM since the Fairphone 4 and there's nearly no information available about it. Why did they switch ODMs twice and how do they compare? Is the supply chain for the T2Mobile-made devices more sustainable? Are they still prioritizing the ethics of the supply chain? None of that is clear.

Fairphone is marketed as being a sustainable device with good long term updates and an ethical supply chain. However, the updates are very poor from the beginning and get much worse over time. It isn't clear that the marketing about the supply chain is much more accurate. Pixels and iPhones get much better updates and hold up better over the long term. It isn't clear whether a Fairphone has better working conditions than an iPhone and it's quite possible an iPhone has lower overall environmental impact per device mainly due to the efficiency of scale.

There will be cheaper Motorola devices with GrapheneOS support too. It's initially going to be limited to flagships due to Qualcomm not yet having MTE for a non-flagship SoC. A flagship SoC is easily more expensive than a lot of low-end phones. Pixels have a much easier time providing high security and long term updates for the budget 'a' series line because they have an in-house SoC used across their devices. Pixels also have no flagship SoC with competitive performance despite selling flagship devices using the same SoC as the lower end devices. It has drastically lower performance than a Snapdragon flagship to the point that the flagship Snapdragon will be an upgrade of ~60% to single threaded performance, ~80% to multithreaded and over 100% for GPU performance.

Motorola has directly seen the immense interest in GrapheneOS from both individuals and businesses. This post is an example of how it greatly increases in the interest in their devices. They're aware not everyone is going to buy a high end flagship and want to have cheaper devices with it.

Motorola has seen that there's immense interest in GrapheneOS and is very interested in expanding it to more devices. They want to have cheaper devices with it and the blocker for that isn't at all Motorola but rather Qualcomm not providing MTE support for lower end SoC variants yet.

People will be able to install GrapheneOS on supported devices themselves but it hasn't been stated that it will be the only option. There will be further announcements about support for it.