3 ms·
What do you think are the non-shady android distros?
by ChrisRR 3mo ago
What do you think are the non-shady android distros?
- nunobrito 3mo ago[flagged]
- deleted 3mo ago[deleted]
- HybridStatAnim8 3mo agoSaying "and that is a fact" doesnt somehow make it a fact. Youre making stuff up. You will gain privacy by using GrapheneOS. The wifi and cellular hardware are not compromised. GrapheneOS only supports devices that meet the baseline hardware security requirements. Pixels arent "poisoned" and there is no evidence to suggest any hardware backdoors exist, and quite a lot of evidence to show they dont exist.
- grapheneos 3mo ago> Android itself is shady as heck In what sense is anything shady about the Android Open Source Project (AOSP)? > WiFi and SIM card chips are compromised right out from the factory This is an unsubstantiated claims not only lacking evidence but heavily contradicted by a large amount of available evidence. It also has nothing to do with Android. > People are usually OK with options like postmarketOS (non-Android) or with the most popular distros like LineageOS. Some jump to things like SailFishOS (attention: russian financial hands on that one). postmarketOS and the desktop software stack it uses is far less private and secure than AOSP. SailfishOS isn't open source like AOSP and is far less private and secure than it. It combines many of the worst aspects of desktop operating system security with low-end Android device security. LineageOS is another fork of AOSP but doesn't preserve all the standard updates and privacy/security protections. None of those are a hardened OS greatly improving privacy and security compared to the baseline of AOSP. None are as private and secure as unmodified AOSP. Those aren't in the same space as GrapheneOS. > Even a cheap chinese smartphone with their "stock" Android can argue for being less shady and raise less attention to yourself than a distro which forces you into specific poisoned hardware. That is just dumb. You aren't backing up your claims of hardware being compromised with evidence. You're also not being specific about what it is you consider to be a problem. You have an issue with us using Pixels. Does that also apply to the upcoming Motorola Mobility (Lenovo) devices too? Which specific hardware do you think would be okay to use? We need hardware meeting our requirements for updates and hardware-based security features which is why Motorola needs to improve their devices to meet our requirements. GrapheneOS also needs extensive porting work to devices due to the hardware-based security features and the need for drivers/HALs to be made compatible with the exploit protections.