I really don’t like how Graphene users will hate all over MicroG. MicroG is a great project but there are so many misconceptions that were started by the Graphene OS core team.
I agree. It’s actually why I chose CalyxOS. The CalyxOS users and team will suggest a degoogled aosp depending on the posture you provide them, while the grapheneos team and users tend to only ever suggest grapheneos. It feels a lot like the Mac fans of the past. I wasn’t diggin it.
As another user stated in reply to you earlier, this is debatable. Debating does not equal hate, I used to use MicroG a ton (I was a CalyxOS/LineageOS user before). But, you must acknowledge that MicroG still communicates with Google, and you can’t disable this at the OS level. That’s the primary benefit of sandboxed Google Play - you can take away full access and many apps will continue to function, and on top of that, the sandboxing layer ensures that the rest of your phone is secure.
MicroG is fine, it’s great, even. But it’s not infallible, and depending on your threat model, that’s something to at least consider.
Can you explain more about how it’s a trap, though? This is an open source project that you can build yourself.
How do you configure it to do that, then? Because calyx’s docs only say that it’s either disabled, enabled without a Google account, or fully enabled. The last two send some data to Google regardless. I’m genuinely asking, because this is the main reason why I left Calyx for Graphene. I saw my phone hitting Google services when I wasn’t even using it. Graphene lets me disable network for apps entirely, something that wasn’t a thing for Calyx either (at the time).
Does Calyx allow you to disable your USB port as well?
Also, I’m still curious about what you said earlier about GrapheneOS being a ‘trap’. Can you elaborate?
I really don’t like how Graphene users will hate all over MicroG. MicroG is a great project but there are so many misconceptions that were started by the Graphene OS core team.
Honestly Graphene OS feels like a trap.
I agree. It’s actually why I chose CalyxOS. The CalyxOS users and team will suggest a degoogled aosp depending on the posture you provide them, while the grapheneos team and users tend to only ever suggest grapheneos. It feels a lot like the Mac fans of the past. I wasn’t diggin it.
deleted by creator
As another user stated in reply to you earlier, this is debatable. Debating does not equal hate, I used to use MicroG a ton (I was a CalyxOS/LineageOS user before). But, you must acknowledge that MicroG still communicates with Google, and you can’t disable this at the OS level. That’s the primary benefit of sandboxed Google Play - you can take away full access and many apps will continue to function, and on top of that, the sandboxing layer ensures that the rest of your phone is secure.
MicroG is fine, it’s great, even. But it’s not infallible, and depending on your threat model, that’s something to at least consider.
Can you explain more about how it’s a trap, though? This is an open source project that you can build yourself.
MicroG only communicates with Google if you tell it to. It is very configurable and you can configure and customize it to your likening.
How do you configure it to do that, then? Because calyx’s docs only say that it’s either disabled, enabled without a Google account, or fully enabled. The last two send some data to Google regardless. I’m genuinely asking, because this is the main reason why I left Calyx for Graphene. I saw my phone hitting Google services when I wasn’t even using it. Graphene lets me disable network for apps entirely, something that wasn’t a thing for Calyx either (at the time).
Does Calyx allow you to disable your USB port as well?
Also, I’m still curious about what you said earlier about GrapheneOS being a ‘trap’. Can you elaborate?