I use e os, i think it breaks most apps trying to access too much and does not support the google services. sadly cant say if it feeds fake data or not
This is the way (non-ironic, non-meme statement). We are beyond being able to preserve privacy, the best we can do is feed them shit until they are no longer able to discern user data from complete garbage. Drown all the tracking data in a sea of irrelevant garbage. Make the algoritmh think you’re an 11 year old PhD from Sentinel Island with a penchant for nordic paganism, that revels in discovering post-jazz and regularly eats fajitas at a cozy little place in Antarctica.
GrapheneOS does this- contacts and storage have scopes such that you can fake out the app into thinking it has access but really quarantine it to a specific folder. I use this for things like applications where I want it to have file access for photos, but only the photos I send to that folder.
Yes, but I really think the project would benefit greatly from better adoption, even if there’s a second unofficial branch that people can just compile for their own devices. Lineage made it so easy i can make my own compilation even if they no longer support it. Download official distro, run command that sets your phone’s drivers (grin their repo, even if no longer supported), compile… Go for a lunch break, profit. I’ve done this a few times for an S7, even though i have a pixel 7 running graphene now.
Why though? There was a recent post around here that I think really hit this home- “whatabboutism”. We don’t need Graphene to fulfill every scenario. We need it to do it’s job well, which is does, and if it doesn’t fulfill your needs, then pick something else like LineageOS which has much more broad support at the expense of a less secure OS.
You sure can compile Graphene on other devices with varying results, the supported/tested device list used to have things other than Google devices on it- part of this comes down to support and dev time too.
Add comment