{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieffnf354nsflqncju2mqk5fzuydu6yutyv3cr5yokgncsddvf5xa",
    "uri": "at://did:plc:34cg4tn4iwemk3v5k3n3adwf/app.bsky.feed.post/3mfsrtmqmxhq2"
  },
  "path": "/t/smartphones-are-not-safe/34004?page=4#post_67",
  "publishedAt": "2026-02-27T01:37:54.000Z",
  "site": "https://forum.f-droid.org",
  "textContent": "The firmware code for the security chips, especially Titan M, maximally open to the public, so the claim that Google Pixel develops its own security chips something’s bad or wrong, absolutely unfounded. I also want to remind, that it is mostly exactly Google post the source code of their phones (specifically phones, for example the same USB stack and not just the security chip), and although starting with Pixel 10 they do it partially or with a delay, many other companies don’t do this at all. Developers of open operating systems exactly therefore are oriented exactly on Pixel phones. Among consumer smartphones, now only on Pixel can offer maximum control and security, in particular, use Verified Boot on third-party firmwares. In the context of operating systems, which you were talking about recently: there was once a project called DivestOS, but it was closed precisely because it couldn’t provide deep control over a many devices with closed source and proprietary drivers, yes and security patches they couldn’t make them that deep. As a result, from the group of security leaders remains only GrapheneOS, the first name of which was AndroidHardening, which directly spoke about deep change in the level of security, which is the same DivestOS allow to itself can’t, but AndroidHardening(GrapheneOS) could, because it only worked on Google Pixel phones. Any security is known in comparison. Or you choose the safest method from availables and the most secure device from availables, or you lose if you choose inaction.",
  "title": "Smartphones are not safe"
}