{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicnewpgipakeuf6td3uyqs2bbspvkal5h7vurgh2jylawm5sbwonq",
    "uri": "at://did:plc:haakkg7y3xdghcdmprxeexso/app.bsky.feed.post/3ml5bgyqlivm2"
  },
  "path": "/t/calyxos-progress-report-our-test-build-with-android-16-is-here/37651#post_16",
  "publishedAt": "2026-05-05T22:28:27.000Z",
  "site": "https://discuss.privacyguides.net",
  "textContent": "I don’t particularly want to rag on Calyx, but this thread as-is may give a novice the impression that CalyxOS is a viable option. Let me be clear: _**CalyxOS is not a viable mobile OS**_.\n\nLet’s recap. This project shut down overnight & left their entire user base with unsupported devices for the better part of a year. They’ve been completely opaque as to what actually happened. They’ve since had staffing & infrastructure issues that’s led to unacceptable delays to the update, production, and release process. And now they’re apparently shipping an OS with unstable beta softwares\n\nI’m almost tempted to claim stock Android would be a better choice; at least you can rest easy with the knowledge that you are on a secure system that will 100% exist tomorrow.\n\nYes, the mobile OS landscape is in a sorry state. Yes, more options would be great. Do not lower your standards out of desperation. Whether through malice, incompetence, or a series of unfortunate events, CalyxOS betrayed the privacy community. They have a _**tremendous**_ hill to climb before they are worth revisiting",
  "title": "CalyxOS progress report - Our test build with Android 16 is here"
}