This is misunderstanding the problem, I think. This is not a weakness in GrapheneOS due to being an AOSP derivative, it’s a weakness imposed by Google on all alternative OSes whether they are AOSP derived or not. They present a scannable code that will only be cleared if you scan it with Google’s Android.
Unless there’s something else going on here. Either way, anger should be directed at Google, not GOS or its users. (annoying though they might sometimes be ;)
Right, I almost, and probably should have, mentioned that. They use a different, parallel system that is also not available to the kind of alternative devices people on this site are interested in.
Same. And I think it is even more ridiculous when you have to rely on their hardware too. They control the hardware drivers AND the OS upstream, how do you exist if not by their permission?
Sounds like the other shoe just dropped on all the people who’ve been religiously swearing by GrapheneOS.
If it’s based on Google: They can control it. You won’t ever catch me utilizing “alternative” chromium providers exactly because of shit like this lol
This is misunderstanding the problem, I think. This is not a weakness in GrapheneOS due to being an AOSP derivative, it’s a weakness imposed by Google on all alternative OSes whether they are AOSP derived or not. They present a scannable code that will only be cleared if you scan it with Google’s Android.
Unless there’s something else going on here. Either way, anger should be directed at Google, not GOS or its users. (annoying though they might sometimes be ;)
iOS does not have this problem
Right, I almost, and probably should have, mentioned that. They use a different, parallel system that is also not available to the kind of alternative devices people on this site are interested in.
Same. And I think it is even more ridiculous when you have to rely on their hardware too. They control the hardware drivers AND the OS upstream, how do you exist if not by their permission?