{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiaz5svzybcuqwgbfjevhuxs6b7rsclfrfg6lc6x5trffdtdm36qja",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3mfjlgvei5en2"
  },
  "path": "/t/grapheneos-will-drop-google-pixel-exclusivity-with-major-snapdragon-powered-devices-coming/32097?page=9#post_166",
  "publishedAt": "2026-02-23T10:31:39.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "Encounter5729:\n\n> Why?\n\nI’m just spitballing, but devices from OEM preinstalled with GrapheneOS might add layers of regional and legal complexity that a web installer simply doesn’t have.\n\nIf you buy an Android device in Japan, they’re mandated to come with what looks like an MCC‑triggered camera shutter sound restriction. I think South Korea has the same rule. There are likely hundreds of requirements like that worldwide which either don’t apply to user‑installed OSes or can’t be reliably enforced. There are also proprietary carrier customizations of all kinds that GrapheneOS rejects, which would likewise create issues for properly selling these devices.\n\nEncounter5729:\n\n> Why would they need to meet those criterias if they build the phone themselves (trough an OEM but more or less the same) ?\n\nMotorola, or whichever OEM they choose, will likely have to navigate the legality of selling these preinstalled devices alongside their usual GMS devices, and would have to do so on a per‑market basis, too. Whether it’s possible is beside the point.",
  "title": "GrapheneOS will drop Google Pixel exclusivity with 'major' Snapdragon-powered devices coming"
}