Android’s new sideload settings will carry over to new devices
Google’s plan to add a 24‑hour delay and new restrictions to sideloading Android apps, with an opt‑out that can carry over to new devices via a Google account, is being framed by some outlets as a “win” for power users. Commenters largely reject that framing, arguing the changes are part of a broader push to turn Android into a walled garden, increase dependence on Google accounts, and disadvantage alternative app stores like F‑Droid. While Google cites scam prevention and user protection as justification, many see this as overstated compared to the real scam vectors and worry about the long‑term erosion of user control, especially for those who value rooting, custom ROMs, or using Android without Google services.
Scope of the change & “carry-over” setting
- Many see the ability for sideload opt-out to carry over to new devices as a tiny concession on top of a restriction Google itself created.
- Several point out this only works if you use a Google account / Play Services; people who run de-Googled or custom ROMs say this change is irrelevant to them.
- There is concern this effectively deepens account-based vendor lock-in: the privilege to sideload is now tied to Google’s cloud state.
User freedom vs paternalistic “safety”
- A large contingent frames this as another step toward a walled garden, eroding the idea that users truly own their devices.
- Some argue adults should be allowed to take risks and that “protecting the naive/elderly” is being weaponized to justify control.
- Others counter that many users are genuinely vulnerable to scams and that raising friction for sideloading is a pro‑consumer safety measure.
Scams and security rationales
- Skeptics note most real-world scams allegedly come via Play Store apps, ads, social media, phone calls, or remote-access tools like AnyDesk, not APKs from random sites.
- Supporters of Google’s move highlight specific scams where victims are coached over the phone to install malicious apps that intercept banking 2FA codes.
- Multiple comments say Google should first “clean its own house” (Play Store malware, scammy ads) if security is the real motive.
Impact on power users, F-Droid, and workarounds
- Many argue the high initial friction still deters non-technical users from F‑Droid and alternative stores; they’ll fall back to Play Store spyware instead.
- Power users note ADB installs are unaffected and can bypass the delay, so the change mainly hits non‑experts.
- Some fear Google can tighten these screws over time (“boiling the frog”).
Alternatives, rooting, and OS landscape
- Discussion ranges over GrapheneOS, LineageOS, CalyxOS, Sailfish, postmarketOS, Librem 5, etc., with tradeoffs in security, rooting, banking support, and usability.
- Big debate over root: one side insists root is essential to truly own the device; the other says easy root fatally undermines modern mobile security models and attestation.
Media framing and trust in Google
- Several criticize the article’s tone as cheerleading, portraying a net loss of freedom as a “huge win” and “nothingburger.”
- Motives attributed to Google include profit (30% cut), ecosystem control, and government pressure over scams; whether scam protection is sincere or pretext is contested and remains unclear.