zlacker

[return to "Google restricts Android sideloading"]
1. tdeck+o9[view] [source] 2025-06-05 17:26:21
>>fsflov+(OP)
I've got to say, some of the comments here are pretty funny.

> "The sideloading restriction is easily solved by installing GrapheneOS"

> "Unless they block ADB, I wouldn't say it's accurate to claim they're "blocking sideloading"".

Not to pick on these folks but it's like we on HN have forgotten that ordinary people use phones too. For some of us, it's not a limitation as long as we can solder a JTAG debugger to some test pads on the PCB and flash our own firmware, but for most users that's just about as possible as replacing the OS.

◧◩
2. rvnx+Na[view] [source] 2025-06-05 17:37:12
>>tdeck+o9
And official Android-based OS bring advantages too. For example, Samsung has lot of proprietary and useful features, and GrapheneOS you cannot use Google Pay (one major feature of a phone).
◧◩◪
3. umbra0+Oc[view] [source] 2025-06-05 17:51:03
>>rvnx+Na
The primary reason why I haven't bought a Pixel and switched to GrapheneOS is because Samsung's OneUI is just so far ahead of the curve. They innovate new software features years before anyone else does.
◧◩◪◨
4. behnam+od[view] [source] 2025-06-05 17:55:30
>>umbra0+Oc
I mean, Samsung and Xiaomi at this point pretty much just copy Apple, sometimes shamelessly.
◧◩◪◨⬒
5. crossr+Hi[view] [source] 2025-06-05 18:28:03
>>behnam+od
> just copy Apple, sometimes shamelessly

Right.

And something that Apple has been doing generally from Android (while trying really hard to catch up) - feature after feature and shamelessly releasing it as the next biggest revolutionary thing since the moon landing, or an invention shadowed only that of the wheel and fire.

In fact last few years of Apple's phone advancement has been nothing along with some features which has been Android for years. Or maybe that's not "copying", that's bringing "at par" which is of course different?

[go to top]