Live data from Hacker News

Keep Android Open

f-droid.org

331–340 of 764 posts

Re: Keep Android Open

#331
I remember not long ago arguing that having Chromium become a monopoly was a bad thing, as it would mean Google could totally twist the web standard in something much more closed. I think this is a prime example.

Re: Keep Android Open

#332
post #38

Earlier quoted context omitted.

If you really don't have an alternative in Europe, buy the cheapest Googled Android device (less than $100 or euros), and use that as a glorified 2FA device. It's not ideal because you have to pay for it, but on the other hand Android devices with unlockable bootloaders (mostly Google Pixels now) tend to be cheaper than iThings. A Pixel 9a or 10a running Graphene for everyday use plus a cheap Android phone that stays…

Yes, that's the endgame, an Android device in a drawer at home. But what do I have to carry on my pocket to use the minimum amount of apps? Firefox, WhatsApp with video and audio calls, Telegram no video no audio, a mail client, a YouTube client (possibly not from YouTube), a maps and navigation app (for cars), phone calls, SMS.

YouTube on Firefox is a much better experience than the official YouTube app, so you can drop one from the list.

Re: Keep Android Open

#334

Earlier quoted context omitted.

If this finally pushes adoption of truly open Linux phones, then this will end up being a good thing, and the greatest favor that Google could do for the open source community. Tragically, Linux phones have languished and are in an absolute state these days, but a lot of the building blocks are in place if user adoption occurs en masse. (Shout out to the lunatics who have kept this dream alive during these dark years…

Even if you have linux, there are still third parties that have control over your hardware. Even if you're using graphenos, you can't block the sim or the cellular radio stack, and likely other modules on the SoC, from at-will access to every sensor on the device. You can at least protect your files, unless there's a mitm or other vector that graphenos can't cope with. And at worst, they can simply clone all your enc…

My phone has hardware kill switches for modem, WiFi/Bluetooth and mic/camera. All three together also kill all sensors.

Re: Keep Android Open

#335

Earlier quoted context omitted.

Personally I'm excited about the death of Android, now resources can be put toward mainstreaming and maturing the Linux Phone ecosystem Hopefully 2026 or 2027 will be the year of the Linux Phone

This is one of the most naive things I see people repeat. The reality is that we're lucky to have mostly-good things at all that align with most of our interests. Yet people get so comfortable that they start to think mostly-good things are some sort of guarantee or natural order of the world. Such that if only they could just kill off the thing that's mostly-good, they'll finally get something that's even better (or…

Agreed that there is a ton of baby in this bathwater.

Also, the open nature of AOSP gave Google its advantage during the early days. Since then, Google has morphed into a company that would likely not make the same decision to create an open-source OS free for others to use and contribute to.

So in the end, what we as consumers actually get, in 2026:

- Google encourages application developers to use hardware attestation to prevent themselves from running on non-blessed, third-party AOSP distributions.

- Google builds basic functionality people care about (including passkeys!) into Play Services, a closed mega-application that happens to require a Google account for most features, and is a moving target for open distributions to mimic.

- Google has closed AOSP contributions to themselves and OEM partners only. AOSP releases are now quarterly source dumps.

- OEMs which traditionally allowed bootloader unlocking (and thus actual ownership of the hardware) have removed it as a matter of policy.

So what exactly is open about Android anymore? Does "source-available OS you can see and not touch" align with your interests? Because it's increasingly not aligned with mine.

Re: Keep Android Open

#336

Earlier quoted context omitted.

If this finally pushes adoption of truly open Linux phones, then this will end up being a good thing, and the greatest favor that Google could do for the open source community. Tragically, Linux phones have languished and are in an absolute state these days, but a lot of the building blocks are in place if user adoption occurs en masse. (Shout out to the lunatics who have kept this dream alive during these dark years…

The limitation of linux phones is hardware. I have been watching the progress of postmarketOS on the fairphone 4, and looks promising.

https://puri.sm/posts/the-danger-of-focusing-on-specs/

Sent from my Librem 5.

Re: Keep Android Open

#337
Could anyone provide me some clarifications?

If I understood correctly, to "protect" users, Google wants to control what is installed on Android phones. I guess it means the Play store will be the only way to install an app, which in turn means: - That users won't be able to install what they want and that they would need a google account to install apps - That app developers have to go through google to distribute their apps, with identity verification etc. Obviously this is awful and would mean the end of F-droid and Aurora store etc. However, I'm also reading here and there that it is a threat to alternative ROMs. To me it sounds at the contrary as an amazing opportunity, as they can strip this verification and be the only truly open Android, or am I missing something? Why do people link this app verification thing with a possible closing of AOSP?

Also, Mozilla was already saying it 10years ago with Firefox OS but... The web is the platform. 90% of the apps out there could be websites. We have all technologies needed for this including offline with service workers. And it works on every damn platform, even the most obscure OS has a web browser. Don't want to be locked to an ecosystem? Just target the web!

Re: Keep Android Open

#338

Could anyone provide me some clarifications? If I understood correctly, to "protect" users, Google wants to control what is installed on Android phones. I guess it means the Play store will be the only way to install an app, which in turn means: - That users won't be able to install what they want and that they would need a google account to install apps - That app developers have to go through google to distribute t…

90% of apps are just websites with a wrapper UI.

Re: Keep Android Open

#339
post #299

Earlier quoted context omitted.

It won't though, because there's a ecosystem of banking/insurance/whatever apps that have bought into the android/iphone lockdown mindsete that people will simply be locked out of. Open alternatives can grow when there is a viable means of slow growth, and cutting off the oxygen to such things is the implicit intent.

> banking/insurance/whatever apps I know banking apps are the typical example, but I've always wondered why. I use my bank's app maybe once or twice a year when I need to Zelle someone, which I only need to do when they don't have Venmo. (Unless we consider Venmo a banking app.) I only have one bank's app installed, the rest of my banks I only interact with over their website, on desktop. As for insurance, I've never…

2FA is a requirement in Europe. I can't log into my bank account without my phone being able to run the app.

Re: Keep Android Open

#340

Earlier quoted context omitted.

Even if you have linux, there are still third parties that have control over your hardware. Even if you're using graphenos, you can't block the sim or the cellular radio stack, and likely other modules on the SoC, from at-will access to every sensor on the device. You can at least protect your files, unless there's a mitm or other vector that graphenos can't cope with. And at worst, they can simply clone all your enc…

My phone has hardware kill switches for modem, WiFi/Bluetooth and mic/camera. All three together also kill all sensors.

If it's got a sim card, it's still phoning home and providing location data. You can't escape the panopticon. A faraday bag gets you mostly there, though, but the point isn't that you can maneuver against it, it's that the device and its operation is fundamentally compromised by design.

There's a whole lot of shady crap underlying the infrastructure and the hardware that consumers cannot touch, pinephone / librephone or otherwise. It's not designed for consent. At best you can gain ephemeral relief, but even that is illusory, because by simple process of elimination, differential analysis allows fine grained ID and tracking of people even if they don't have accounts, phones, interact with websites, etc.

It's not a shady cabal of lizard people, it's just the grubby natural alignment of interests by a wide ranging set of companies and regulators and groups who allow it to happen without imposing any accountability, and ensuring that the system remains structured such that no effective accountability can be imposed.

Extorting constant streams of data for adtech is too valuable and the entire thing is too complex for silly things like ethics to interfere.

Post reply on HN