{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihovrkwhmswdunldkw4iiv7e6tc5yvsqqilu7kqmnzyd3bwmvsr2e",
    "uri": "at://did:plc:34cg4tn4iwemk3v5k3n3adwf/app.bsky.feed.post/3mekcgvs7n2u2"
  },
  "path": "/t/smartphones-are-not-safe/34004?page=2#post_37",
  "publishedAt": "2026-02-10T23:51:22.000Z",
  "site": "https://forum.f-droid.org",
  "textContent": "confidenseuide:\n\n> Pixel open source smartphone.\n\nNo. It is NOT!!! Only Android part is open source. Firmware is NOT. Processors’ firmware’ is not. You can’t build firmware. You can only include binaries.\n\nAndroid does not have access to processors’ firmware, which is a mini OS in of itself. Android have no control over it. This is why that glaring Pixels vulnerability (access to unencrypted data in fastboot) could only be fixed by Google: The back door was in closed source firmware.\n\nEdit: You are simply misinformed. Google does have some old repositories for its Titan chips, but you can’t build from them for Pixels. It’s like Chromium: Google uses some sources from open source Chromium, but the finished product - Chrome is a black box. The same is with Pixels firmware: Black box.\n\nKnowing Google’s appetite for grabbing data, Pixel’s firmware is Gapps on steroids, because Gapps can be disabled or not included. You can’t do the same with processors’ firmware and other binaries. Without them, the phone will be a brick.",
  "title": "Smartphones are not safe"
}