It is a disgrace how Google has managed this situation.
To recap the storyline, as far as I understand it: last August, Google announced plans to heavily restrict sideloading. Following community pushback, they promised an "advanced flow" for power users. The media widely reported this as a walk-back, leading users to assume the open ecosystem was safe.
But this promised feature hasn't appeared in any Android 16 or 17 betas. Google is quietly proceeding with the original lockdown.
The impact is a direct threat to independent AOSP distributions like Murena's e/OS/ (which I'm personally using). If installing a basic APK eventually requires a Google-verified developer ID, maintaining a truly de-Googled mobile OS becomes nearly impossible.
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.)
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.
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 had an insurance company's app installed.
Am I just an outlier here? Honestly, if I switched to a non standard OS, I'd be more annoyed about losing, say, Google Maps, Uber/Lyft, or various chat apps. Banking and insurance just don't come to mind at all as something I need my phone for.
I can get alerts in email or messages, no need dedicated app for that, I can track there also my balance, so only useful thing app provides are easy wire transfers from phone, which I never do, if I wanna transfer money is much more convenient work big display, proper keyboard and mouse than from phone.
No. The "banking app doesn't work" argument against non-corporate mobile OS, raised incessantly is HN comments, is bogus
I want a "phone", i.e., small form factor computer, that can run something like NetBSD, or Linux. But I have no intention of using it for commercial transactions. Mobile banking is not why I want to run a non-corporate OS
I want to use it for recreation, research and experimentation
> I want a "phone", i.e., small form factor computer, that can run something like NetBSD, or Linux. But I have no intention of using it for commercial transactions. Mobile banking is not why I want to run a non-corporate OS
> I want to use it for recreation, research and experimentation
I am a firm believer that phones are personal computers and should have all the end user freedom we have come to expect from personal computers. I am totally behind what your saying. (The amount of irrational anger that wells up in me when I hear someone make the argument that phones are somehow not general purpose personal computers and shouldn't provider their owners software freedom would astound you.)
Personally, I opt out of services that require the use of phone "apps" and any potential attestation they provide. Unfortunately, I just offload those needs onto my wife and her iPhone.
Want to go to a concert in a TicketMaster venue? You have to have a phone. Pay to park in some places requires a phone. Mobile ordering for some restaurants requires a phone.
I don't think it should be this way, but it is. I think we need consumer regulation to insure software freedom on phones and curtail awful user hostile "features" like remote attestation.
Until that happens (if it ever does) there is a realpolitik with needing corporate phones for some activities that can't be denied.
I would stop using bank requiring phone app to do banking, simple as that, both my main EU accounts use sms verification codes and extra password, which is fine with me. If they will require an app, they will lose customer.
That's true, but the notion that we're still using paper checks in 2026 is so crazy. And yet they remain the cheapest way to handle many transactions in the US financial system. Like a lot of small healthcare providers still prefer to receive paper checks from insurance companies because the electronic payment processors take a 3% fee.
I haven't had issues with the mobile apps of 3 of the most major US brokerages. They run fine on rooted phone. They do everything I'd want a bank to do anyway.
Ditch your bank if they have issues. If their retention department asks why you're leaving, tell them their app doesn't work.
The best solution for this is to buy a $30 burner phone at Walmart and use it unactivated, tethered to your main de-Googled device. You can use the burner for only tasks requiring Play Integrity.
Make sure to leave one star reviews on all such apps that you run into.
For me as a desktop linux poweruser, I find this potential transition pretty intimidating, I've never flashed a phone with a custom rom let alone switch to a completely different OS, and I am not sure if the phone can even be reset to its original OS, if things go south.
I flash phones almost every other week. And tablets. I have been flashing since Androids came out. But never bricked. But maybe that is why I don't have any problems.
> Are you seriously implying that flashing phones doesn’t risk bricking them or you’re not aware of that risk are you serious?
Yes, that is generally the case. As a general rule with an Android phone reflashing the OS itself or the bootloader carries no risk of bricking the device (meaning making it impossible to recover without specialized hardware and/or opening up parts that were not intended to be opened).
There are plenty of ways to "soft-brick" a device such that you might need to plug it in to a computer, and adb/fastboot can definitely be a pain in the ass to use (especially on Windows), but if you have a device with an unlocked bootloader it's very rare to be able to actually brick the device while doing normal things.
Now, if you're doing abnormal things like reflashing the radio firmware you can absolutely brick some devices there, but you don't have to do that just to boot an alternative OS and generally shouldn't be doing it without very good reason and specific knowledge of exactly what you're doing.
I'm not going to say there are no devices where the standard process to flash an alternative OS is dangerous, but none of the relatively common ones I've ever owned or used have been built that way because OEMs don't want their own official firmware updates to be dangerous either.
tl;dr: It is sometimes possible to brick a device by flashing the wrong thing incorrectly, but the risk of doing that if you are just installing an alternative OS through a standard process is basically zero.
The challenge I've found when looking for instructions for flashing one of my old phones is the assumption of knowledge some rom builders have, or perhaps an assumption about their audience. This seems like it has the potential to bit someone in the ass because if they're relying on other sources like the lineageOS wiki or forum posts elsewhere for example there's no guarantee it'll stay available, complete, or relevant to their variant over time. It's an added burden for what is a gracious volunteer role, but it's a handicap if they want more people using the fruits of their labor.
Expecting Google to give up control of one of the only alternative operating systems is right up there with believing in the tooth fairy.
What you're saying should happen, but it will only happen when the government legislates it happens; which frankly they should be doing (along with nationalizing a few other software projects to be fair).
A trillion dollar transnational corporation with massive monopolistic tendencies will never ever do the right thing. Expect to force feed it down their throats.
In general, governments seem to be much more invested in making it illegal to have anything that is too open and too free. Even EU is lusting for draconian control features like chat control where you don't own and operate the software you installed on your device even if, at the same timem, they're trying to gnaw on the influence of Big Tech.
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 encrypted bits and wait on Moore's law or sufficient cubits to go back and crack the copy, on the off chance there's anything they want with your data in the first place.
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.
For sure - and you can use WiFi only, set yourself up with a HaLow rig and give yourself a ~10mbps connection anywhere up to 10 miles from your home, suitable for voip and low rate streaming, throw in VPN, and remain completely off-net as far as cellular networks go. I'm actually planning on using a wireless touchscreen and mobile halow/raspberry pi network/storage stack to completely replace my phone, but the bigger issue is automated tracking of everything - if you're the only blank spot in a sea of known individuals, it's just a matter of seconds to id you, since everything everywhere about everyone is tracked online.
We should be enforcing informed consent regulation of network infrastructure, treating privacy and anonymity as synonymous with liberty and freedom. Allowing the system to operate as it does is a choice; those with lots of money get to make it grow by exploiting a constant invasion of privacy with no concurrent return to the society being exploited.
Phones aren't built to be privacy respecting, and kill switches are a mitigation of a symptom, they don't do anything to address the disease.
I don't care about specs, I care about functionality and price. The camera on the pinephone doesn't practically work because it is too slow and the quality sucks. You basicially cannot record videos whatsoever. I can't use the device for GPS navigation. I can run whatsapp within waydroid, but it isn't practical due to the battery life and startup limitations that imposes. The GPU on the pinephone sucks, is underpowered, doesn't support OpenGL ES 3 or vulkan, and the user interface is always slow as hell to navigate.
So practically I cannot use it as a daily driver.
Librem 5 does have enough GPU horsepower, a functioning camera, and good pmOS support. But $800 is a lot to ask to test out switching to linux with no guarantee that my workflow will work or I will have enough battery life. It looks like the librem 5 can't record videos or do GPS navigation yet.
I am looking at the librem 5 specs again. The EG25-G is probably a better starting point for the modem now that it has been better documented and reverse engineered as a result of the pinephone project. It is interesting that the L5 has a generic smartcard reader though.
There is an implicit shame in disgrace but faceless entities have no shame. They'll just put out another press release written in corporate newspeak by an LLM and move on withe the plans anyway. This is standard Google behaviour. They do it with Chrome, they do it with Android, they'll keep doing it with all their captive markets. I fear that in practice even having an "advanced flow" will make little difference as some applications will refuse to work if you have it enabled anyway (in the same vein if debugging is enabled, for example).
Nothing about Android is open except the absolutely minimum amount of linux kernel that's required to boot the thing. Then it's blobs and restrictions all the way to the screen.
Good news: You (as a community) can now finally wake up from your dreams and get some things right!
It's really a shame that you always wait until you really get forced. Particularly in situations when every individual's inability has consequences for the others as well. I really gave up all ideas of a better world. With this community, the best you can hope is that the decay will be slow.
So everyone who would describe himself/herself as a FOSS enthusiast, or at least a friend of a somewhat open system where the user has some actual rights beyond sole consumption, put some pressure towards having actually de-Googled systems. A system that mostly comes from Google, would not fit my definition of that term at all! Even if they removed some parts of it. It's an euphemism. And it's dangerous because you constantly get trapped by these euphemisms. Ever. Single. F'ing. Time.
Good thing restricting side-loading isn't legal in the European Union! Not a problem here. Apple had to enable side-loading on their EU-based phones and so will Google if they restrict it.
Yes it is, and no they didn't. Apple has to allow (heavily restricted) alternative app stores, and I'm not clear on whether any actually exist right now.
If a lawsuit tackles this problem in the EU, will we finally also see somebody go after MS for their obnoxious code signing certificates?
While MS code signing certs are more circumventable for power-users than Android's new approved developer program, their pricing is far more prohibitive for independent OSS developers and hobbyists, costing hundreds of USD per year.
The kind of "side-loading" of notarized apps outside the manufacturer's app store that Apple allows in the EU is exactly what Google proposed to do for all its Android builds. We don't want that.
The only reason I was sticking to Android for years is this. And I think there is no moat for Android. I would rather switch to iOS if both platforms are same restrictive.
The impact is a direct threat to independent AOSP distributions like Murena's e/OS/ (which I'm personally using).
I don't think this is true, right? An AOSP build can just decide to still allow installing arbitrary APKs. Also see this post from the GrapheneOS team:
You can’t really do that long-term as Google will change code that will not match however you are not enforcing this policy
So at the very least you’d have to keep patches up to date.
Long term divergence could be enough that’s it’s just a hard fork and/or Google changes so much that the maintainer can’t keep the patches working at the same pace
I couldn’t read your link as it asks to join mastodon.social
Strong disagree. Linux, its permission system and its (barely existent) application isolation are lightyears away from the security guarantees that Android brings.
Desktop OSes and their derivatives are woefully behind in this regard, and unfortunately the will to bring them up to par is incredibly weak. Of those in mass use (Qubes OS is neat but its user base isn’t even a rounding error), macOS probably does the most, but it’s still lagging behind iOS and what’s been implemented has come with much consternation from the technically inclined peanut gallery.
I understand some amount of reticence with commercial OSes, but there’s no justification for being against it on open Linux based desktops and mobile OSes. We really need to get past the 90s-minded paradigm of everything having access to everything else all the time with the only (scantly) meaningful safeguards coming in the form of *nix user permissions.
> We really need to get past the 90s-minded paradigm of everything having access to everything else all the time
I do agree with that, and I strongly believe that the iOS and Android security model is way ahead of Desktop Linux. But what I observe is that nobody seems to care about the security model. A recurrent complaint I see against anything AOSP-based (including Android) is that people "want to be root".
It comes from a history of using mostly trusted application sources like Debian/Ubuntu package archives with manual review being the norm. And few supply chain attacks.
But both Flatpak and Snap offer this new model from the two biggest desktop players in the Linux world: Red Hat and Canonical.
As the sibling comment said though, being an administrator for your own computer (including a phone) does not mean that you will be running untrusted applications as one: on the contrary, if you assume an administrator role and run an untrusted application, naturally, all bets are off. But even as a power user, I'd love to be able to safely run programs I do not necessarily trust, feeding it only data it needs and no more.
Again, Snap/Flatpak provide this model, but we need to see more application authors take them up to ship their software.
Allowing the owner of the device root access doesn't necessarily break the security model. It just means that the user can grant additional privileges to specific apps the owner has decided to trust. Every other app still has to abide by the restrictions.
The fact that Android complains and tells any app that asks whether the owner actually, you know, owns the device they paid for is an implementation detail.
A Linux distribution that adopts an Android style security model could easily still provide the owner root access while locking down less trusted apps in such a way that the apps can't know or care whether the device is rooted.
Do you have any source for that claim? That would be a pretty serious security issue even unrelated to any security hardening (eg. on a multi-user system, one user could read out the password from another user — even with desktop usage, second user could be SSHed in).
As a datapoint, everything in /dev/input/* is owned by root:input on my Debian Bookworm install, and my main user is not a member of the "input" group either.
Biggest problem with most security hardening for Linux desktop is that it breaks the natural usage pattern: I store my files by their content, not by their format (eg. I might have a folder for my project containing image files, spreadsheets, FreeCAD files, maybe even some code or TeX/ODF files). If programs are restricted to access the entirety of my $HOME though, there is not much benefit to that protection since that's where my most valuable data is. If they are restricted to per-program folder, I need to start organizing my data differently and unnaturally.
Android mostly does not use the "files" metaphor and basically does exactly that (per-app data): coming up with a security model and file management UX that does both is where the challenge is.
It's the same reason I choose to keep my front door unlocked basically all the time - I know my neighborhood, the risk is really low and the convenience is high.
Further... practically everyone agrees that they don't need bank vaults as front doors. It makes zero practical sense: The cost is incredibly high, and the convenience is very low.
There are ALL sorts of wonderfully cool things you can do on a system where applications are allowed to trust each other, and the system is permissive by default.
You can customize behavior more easily, you can extend software more easily, you can add incredibly detailed & functional accessibility support, you can create incredibly powerful macros and commands.
This is so important that fundamental OS design from the early 90s actually prioritized and catered to exactly this style of open, trusted, platform (ex - all of COM in windows...). This is what made personal computing a reality...
All of those fall flat when you try to impose "well funded" security efforts.
Those efforts have a place, in the same way that bank vaults have a place. Whether that place is a personal computer is a different question.
Implying those folks are hostile for no reason is... at best a woeful misunderstanding of the situation, and at worst a malicious mischaracterization.
Flatpak and Snaps are built to solve this. They do conflict with some expectations from users to be able to play around with things, though, so they do not have the penetration one might want.
They only cover the user-facing app part of the story. The rest of the system needs isolation and safeguards, too, including things like the desktop environment and whatever random daemon.
A solution that's integral to the system and not just loosely taped on is required.
This might be a strange take in these times, but I feel like the browser largely solved the "I need to run potentially adversarial application code in a sandbox". For native applications, stick to stuff that's vetted and in well-maintained repositories, or well-known open source projects that you trust. All of this technical work just to be able to run hostile native code ignores that you don't have to, and probably shouldn't want to, run sketchy code on your device. Installing random untrusted software is bad, even with the most advanced security model in the world. At the very least it will probably abuse whatever permissions it has to spy on you to any degree it can (which is a lot, even for web pages) and to send you advertising notifications.
This assumes that the mentioned systems are the only security considerations on a Linux system. Clearly this is not the case so I am unsure why you omit other security-related aspects of Linux here.
Android, being based upon the Linux kernel, has all those and its own app permission system built on top. Linux on its own comes nowhere close to this.
I understand why mobile/tablet OSs are so crappy compared to desktop; in the past these devices had no resources cpu and ram wise and had to heavily watch battery consumption (the latter is still true mostly, but that should be up to the user), but my phone is more powerful than my laptop and yet runs crap with no real usable filesystem and all kinds of other weirdness that's no longer needed.
However, I have 2 Linux phones and Linux on phones is just not there. Massive vendors (Samsung, Huawei, etc) would need to get behind it to make it go anywhere. Also so banking etc apps remain available also on those phones. We can already run android apps on Linux, Windows apps, so it would be a bright future but really it needs injections and support for large phone makers.
I hope the EU/US mess will give it somewhat of a push but I doubt it.
FWIW, Nokia did develop a pretty good Linux phone back in the day (Maemo/Meego) with Nokia N9 (it even received rave reviews from consumer tech sites like engadget), but it did get killed off as they got absorbed into Microsoft (we all know that didn't age well).
Similarly, Palm Pre, and especially HP Pre 3 was a wonderful WebOS incarnation.
Ubuntu Touch did seem like it had a future, but it was a massive sink for Canonical so it was defunded as well.
The user experience was there on all of these: the apps, not so much.
Ubuntu Touch is not dead though, I use it happily on my primary device for 8 years. It's working like a charm. And waydroid allows you to run APKs, even if some bank apps may not work.
I.. don't think it will happen. For several reasons too. It is not that I don't think Android will change substantially, but the following constraints suggest a different trajectory:
- AI boom or bust will affect hardware availability
- there is a push on its way to revamp phones into 'what comes next' -- see various versions of the same product that listens to you ( earing, ring, necklace )
- small LLMs allow for minimal hardware requirements for some tasks
- anti-institutional sentiment seems to be driving some of the adoption
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 rather, more aligned with their interests rather than anyone else's).
In reality, mostly-good things that align with most of our interests is mostly a fluke of history, not something that was guaranteed to unfold.
Other common examples: capitalism, the internet, html/css, their favorite part of society (but they have ideas of how it could be a little better), some open-source project they actually use daily, etc.
If only there weren't Android, surely your set of ideals would win and nobody else's.
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.
>The impact is a direct threat to independent AOSP distributions like Murena's e/OS/ (which I'm personally using). If installing a basic APK eventually requires a Google-verified developer ID, maintaining a truly de-Googled mobile OS becomes nearly impossible.
I have trouble understanding why this is a threat to AOSP distribution. I would have said quite the opposite actually, I don't see why they would not remove the verification and that's an incentive for people to use their project instead of Google Android.
I like it, because more and more people see Google as what it is: a ruthless, selfish and extremely greedy mega-mega-corporation. The less we depend on it the better.
Who could Android be possibly recommended to at this point?
I know iPhones aren't affordable for the layman in many countries. But for anyone with an option, why would you buy an Android? All the "customization" things I cared about when I was on Android are either doable on an iPhone now with better implementation, or something I don't care about.
I was a die-hard until I went through enough cycles of Google deprecating and reinventing their apps and services every year, breaking my workflow/habits, that I got sick of them and moved to Apple everything. And all the changes I've seen since then are only making me happier I got out of the ecosystem when I did. Unlimited Google Photos backups with Pixels are gone, Google Play Music is gone, the free development/distribution environment is gone, etc.
If people can't even develop for the thing without going through the Google process, they're really just a shitty iOS knockoff.
But this thread is about the option to install apps on your device regardless of OS vendor approval, and that's not possible either with iOS nor is iOS open source. And that's what this is all about. If you don't care about open-source and user freedom, then this change wouldn't matter to you anyway.
I switched back to Android in large part for KDE Connect. You can get continuity esque features that work with any desktop operating system. I also get to use real Firefox instead of a Safari wrapper. I still use as few Google services as possible, pretty much just Maps.
It "works" but it is significantly less useful. Notification mirroring doesn't work, you can't read/respond to text messages, it can't reliably run in the background.
These are all due to limitations imposed by Apple.
At this point, I wouldn't recommend Android other than enjoying the much steeper discount with the headset. For me, the only thing that is keeping me on Android is easier access to commas on the keyboard.
I love the Java/Kotlin userspace, even if it is Android Java flavour, and the our way or the highway attitude to C and C++ code, instead of yet another UNIX clone with some kind of X Windows into the phone.
In the past I was also on Windows Phone, again great .NET based userspace, with some limited C++, moving into the future, not legacy OS design.
I can afford iPhones, but won't buy them for private use, as I am not sponsoring Apple tax when I think about how many people on this world hardly can afford a feature phone in first place.
However I also support their Swift/Objective-C userspace, without being yet another UNIX clone.
If the Linux phones are to be yet another OpenMoko with Gtk+, or Qt, I don't see it moving the needle in mainstream adoption.
The fundamental problem is that we are relying on the good graces of Google to keep Android open, despite the fact that it often runs run contrary to their goals as a $4T for-profit behemoth. This may have worked in the past, but the "don't be evil" days are very far behind us.
I don't see a real future for Andrioid as an open platform unless the community comes together and does a hard fork. Google can continue to develop their version and go the Apple way (which, funny enough, no one has a problem with). Development of AOSP can be controlled by a software foundation, like tons of other successful projects.
Yeah, that's the biggest issue. And it all originally stemed from phone carriers wanting to lock customers into their services.
We need some pro-consumer regulations on hardware which mandate open platforms. Fat chance of that happening, though, as the likes of both the EU and US want these locked down systems so they put in mandatory backdoors.
Google's own phones do not have a locked booloader. You can buy a Pixel and put GrapheneOS on it in like 10 minutes. But basically no one does this, because no matter what people say in online forums they actually value ease of use and shiny features over privacy and software freedom.
Even if locked bootloaders weren't a thing, not being able to just buy a phone with an open Android pre-installed means it would get relegated to the Linux Zone, with a whole lot of "security alert" and "device not supported". Also, low popularity leads to fewer development resources, so it would probably suffer from lack of polish.
People will keep using the OS their phone comes with and that would be Google's Android. It's worse than with Windows PCs and Windows to be honest because phones have a locked bootloader.
A hard fork is not needed. Non-Google Android do not have to enforce this requirement. It's more important to get as many people on alternatives like GrapheneOS as possible. And fund them by donating to them. If every ~0.5 million GrapheneOS users donated 10 Euro per month, they would be very well-funded.
There is no such thing as non-Google Android. At most you have people applying tiny patches on top of AOSP, but 100% of the code in the underlying project is still Google-approved, and none of the alternatives have control over that.
It's the same as the situation with Chrome/Chromium. There are a million "de-Googled"/"privacy focused" alternatives to Chrome all using the same engine, and when Google pushed manifest v3 changes to block ad-blockers every single one of them was affected.
At most you have people applying tiny patches on top of AOSP, but 100% of the code in the underlying project is still Google-approved, and none of the alternatives have control over that.
You are making an orthogonal point. Yes, Google maintains AOSP. No, that does not mean that AOSP OSes that are not in Google's Android program (calling it that to avoid semantics games) have to adopt this change. If you want to hear it from the experts: https://grapheneos.social/@GrapheneOS/116103732687045013
Unless these different Android flavors all have the resources to indefinitely rewrite AOSP and remove all Google code they don't agree with - no, they pretty much have to adopt the changes (see the earlier Chromium example). And if they do somehow manage this after a point all the patching basically becomes a fork, which is exactly what I started the conversation with.
I see your point, but it all hinges on when you consider the changes to be a patch set and when a fork. I don't think there is a very clear definition, except I don't think most of these projects would call themselves AOSP forks.
At any rate, this particular Google anti-feature does not require a large patch (or maybe none at all).
> and when Google pushed manifest v3 changes to block ad-blockers every single one of them was affected.
That's just objectively wrong, both Brave and Opera still support manifest v2 and are committed to continue doing so for the foreseeable future. Even Edge apparently still has it, funnily enough.
Nope, actually "both Brave and Opera still support manifest v2" is objectively wrong.
Brave does NOT support manifest v2. They have instead hand picked exactly 4 manifest v2 extensions (AdGuard, NoScript, uBlock Origin, and uMatrix) and have hard-coded special support for them. They quite literally say in https://brave.com/blog/brave-shields-manifest-v3/ that all other v2 extensions will go away from Brave once Google fully removes support for them (which may have happened already, since it was posted a while ago).
> They have instead hand picked exactly 4 manifest v2 extensions (AdGuard, NoScript, uBlock Origin, and uMatrix) and have hard-coded special support for them. They quite literally say in https://brave.com/blog/brave-shields-manifest-v3/
You're misreading that page, they have special cased the hosting of those 4 extensions, because they do not have their own addon web store and are relying on Chrome's instead. You can still install any manifest v2 addon manually, not that there are going to be many outside of those 4 that care about v2.
As for Opera:
"Today, we reiterate what we said back in October 2024: MV2 extensions are still available to use on Opera, and we are actively working to keep it that way for as long as it’s technically reasonable."
which begs the question, why ublock origin is not native on all browser yet?
addons for firefox were at first a way to test features. we only have devtookls because one person wrote an addon copying ie6 dev tool. next Firefox release it was part of the core browser.
Get a large phone vendor to get a flagship phone with Graphene or so on the market. Otherwise nothing will happen. Even starting with the smaller ones like Blackview would do something. But almost no one will do that because users are said to want android; like my parents care... But they will care of course when their banking app stops working... That is the real issue imho.
What about the Android SDK? I don't think that this is open source, is it? As a developer, when you download an Android SDK you have accept a licence that is not open source, right?
Who else is going to maintain and develop it? It's the same issue as with Chrome, even if you force Google to give it to some other company, they're all just as bad. And it's too big and too costly to maintain for anyone else but tech giants.
The only other options would be convincing users to pay 5 bucks a month for their software, or have some Government fork over the tens of millions required to pay open source developers. And good luck with that.
I'm thinking with ever increasing seriousness: let's split any company that grows past a certain size. Each side gets a copy of the codebase and half the assets, no one who's been on the board on one side can be on the other side's board, and neither side can buy off the other. They can use the existing branding for a limited time and with a qualifier (say Google Turnip vs Google Potato) but after that it's on the strength of the new brand which they're each building and for which they're competing against each other and the rest of the market.
This is not happening in my lifetime, of course it isn't. But by god does it need to happen.
Right? We need a "You won capitalism!" award where everybody in the org gets a huge bonus and then the company is split into small pieces and then they start over. On top of it we do what you describe and enforce the split so they can't collude.
I don't think you understand what that word means.
Regardless, your opinion (and mine) is irrelevant. People want at least some of the features of modern android, and any alternative lacking those is not going to be adopted by most people. Just look at how many people try GrapheneOS and find the minor things to be dealbreakers for them.
And as long as that's the case you can't expect people to vote for a scenario where they'll end up with a, in their eyes, worse product.
Historical meaning is pretty worthless though. It's like saying CPU's are going backwards because the 386 was a bigger jump. Technology matures eventually and that's not a bad thing.
Android doesn't really work on hardware changes as AOSP doesn't run on a single phone on earth anyways, not even the emulators, this is the goal of the manufacturers.
For the features you can read here for example what Android 16 changed:
The gigantic task of maintaining and developing a mobile OS that needs to retain compatibility with AOSP/GPS anyway to tap into the huge amount of applications that are available?
It will cost a lot of money and as long as Google is still doing regular AOSP code drops, what's the point?
I contacted the EU DMA team about my concerns and got a real reply within 24 hours. Not just an automated message, it looked like a real human read my message and wrote a reply. I'd urge other EU citizens to do the same.
Great idea, I just did the same. I encourage other EU citizens to do the same. Keeping at least one of the two major mobile ecosystems open is important.
(And install GrapheneOS, the more successful open Android becomes, the better.)
True. I'm really happy that they are working with an OEM to bring an alternative in 2027. Until then:
- A refurbished Pixel works (except some weird Verizon locking that I heard about the other day).
- Pixels get really heavily discounted near the end of the cycle (e.g. 9a currently). Google probably doesn't make much on it if you are opting out of your ecosystem.
Wow, someone replied to an email. From the same organization that is pushing for chat control. That would give you hope... European tax payers have this funny belief that their bureaucratic overlords are all there in Brussels acting with the taxpayer's interest and privacy in mind. One can dream, I suppose...
I am genuinely curious, what is your moral justification to attempt to use party A to forcefully influence how party B develops/sells *their* intellectual property? Party B owes you nothing. You are free to not use their products or start a company to compete. How do you justify it, and how would you feel if you were on the receiving end of such a dictum?
Well, Google has marketed Android as an open source operating system (AOSP) and openness about the system [1] and encouraged manufacturers and developers to build on it based on the premise of openness and of course being "free". People advocated for Android because it was open source compared to other alternatives. But with this change they are simply ending that openness. People that have developed F-Droid and other alternative stores have contributed to the platform value (such as not being able to de-google their phone), the same goes for many other developers who have spent countless of hours developing for Android.
To say they don't owe you nothing seems like a betrayal on the promise that Android was an open platform (and open source).
> You are free to not use their products or start a company to compete
That's not an option as you are making it out to be. For a user switching means buying a new phone, repurchasing apps (if you bought) and maybe apps won't be even available to the new system, for developers that means all their knowledge about the system gone. Building a mobile operating system requires millions if not billions of dollars, years of work and convincing developers and businesses (hardware makers) to use your operating system. The barrier to enter is so high that telling people to just compete with Google is not a realistic solution.
Maybe "intelectual property" is really imaginary property given how the same big companies just gobble data from other people and companies wothout permission to feed their AI models (Facebook with books, recently NVIDIA with milions of videos from Youtube).
I guess they would not due that if they really believed some questionable synthetic construct like "intelectual property" really existed ?
Party A does not owe Party B the right to sell in Party A:s legal area.
Party B is allowed to choose not to sell in EU. If you wanna sell in EU you have to comply with EU rules. If you wanna sell in US you have to comply with US laws. That simple.
That is not how the European Union works. One of the core goals of the EU is to guarantee the European single market. One of the core principles of the single market is the Freedom to establish and provide services [1]. The Apple/Google duopoly have effectively created a market within the single market where the core principles of the single market do not apply anymore.
Tech has a strong tendency to favor outcomes with only a handful large players that make competition impossible due to network effects, etc., distorting the market. The Digital Markets Act was made to address this problem.
IANAL, but Google's Android changes seem like a fairly clear violation of the DMA.
This is typically hard for people from the US to grasp (I saw that you are not originally from the US though). In Europe, capitalism is not the end goal, the goal of capitalism is to serve the people and if that fails, it needs to be regulated.
---
As an aside, the lengths people go to defend a company with $402.836B yearly revenue :).
Yes. I am effectively asking you what the moral justification for DMA is. I understand that lawmakers can make whatever law they want. I understand they made it. I am curious how people who agree this should be possible think of this from a moral angle, especially as engineers who make their living by creating intellectual property and probably wouldn’t want to see control of it seized randomly
I'd ask the inverse of the question: morally, should a single gatekeeper have the right to deny two consenting parties the ability for one to run the other's software?
Especially when that ability has been established practice and depended upon for decades? And the gate-kept device in question is many users' primary gateway to the modern world?
There's nuance here, of course - I'm not morally obliged to help you run Doom on your Tamagotchi just because you want to do so. But many people around the world rely on an Android device as their only personal computing device (and this is arguably more true for Android than it is for iOS). And to install myself as an arbiter of what code they can and cannot run, with full knowledge that I could at any time be required to leverage that capability at the behest of a government those worldwide users never agreed to be dependent on? That would be a morally fraught system for me to create.
The moral justification is that I am a citizen, and can demand the laws I want. When enough people think like me, we can actually make it a law. By holding the smartphone OS oligopoly these companies hold a lot of power on the people. I do not like that. Hence I like laws that try to change that.
> especially as engineers who make their living by creating intellectual property and probably wouldn’t want to see control of it seized randomly
If these people try to use their intellectual property to control my device and hence my ability to do things, I want to have a say what they do. Yes, that is what software is: directions to machines. I own the machine, hence I want a say what it does. You are free to keep your intellectual property for yourself, if you want to.
At some point free markets become fiction. There's no financially viable way to start competing businesses in markets as entrenched as mobile OSes. Otherwise this would have happened. And if that becomes anti consumers, then the consumers start changing the rules the companies operate under. Because in a democracy we have more consumers than CEOs,so they vote with majority.
(This obviously simplifies things, but ultimately we as humans still haven't found the one and only true philosophy or moral, and maybe that's not possible (I'm no philosopher))
There are no absolute morals. But I think in general healthy societies are arranged around the ideas that people should have: the basics of living (housing, food, vacation, and some luxory), agency, and equal opportunities.
It should be clear that having a small number of companies murder all competition and personal freedoms (like doing what you want to do with something you own like a phone) are in contrast to these basic values.
---
Or the alternative, more blunt answer: it does not require a moral justification. EU citizens directly elected the EP, the EP ratified the DMA. So Google can either comply or leave the EU as a market (which they wont do because it's too large and others would be happy to take it).
The moral argument is that vertically integrated monopolies threaten the rights of consumers, who are human beings. Corporations are legal fictions and their "rights" are another convenient fiction to align incentives. They carry zero moral weight.
Are we still talking about massive companies with power to arbitrarily decide how billions of people use the personal computers they bought? Who's doing the feeling? Why would we presume all of their conduct to be moral?
> Party B owes you nothing. You are free to not use their products or start a company to compete.
When 99% of government/banks/etc require you to use a certain service to access basic services, you need some way of ensuring you don't have to sell your soul to use it. Alternatives would be really great, but Google is part of a duopoly.
Just because you build the rails doesn't mean you get to decide who gets to use the trains.
That is not their fault, though. I can see how you could complain to the people who mandate you use B’s products. Otherwise what you’re saying is that control of any intellectual property can be stolen from its owners simply by becoming popular outside of their control
It is though. They are actively working on increasing their marketshare. That doesn't happen by accident. They have chosen to place the interests of the corporation over the interest of their fellow people. They are fine to do that, because we separated that responsibility. Corporations can only chase for profit, because we have governments, that make the rules, so that chasing profits is in the interests of the people.
Maybe you don't like that, and that is fine for you, although I don't like that you don't like that. Maybe you want a society where might makes right. However a lot of people don't feel that way, hence why we outsourced that world model to the government.
People don't like that their neighbor is stronger than them and takes there stuff, so they pay feudal lords. Then the feudal lords want some security, so they outsource that to elected emperors. After a while the feudal lords misuse their power, so parliaments are invented. Eventually people have enough and demand voting rights. The elected leaders betray the people by sending them to war, so they created multinational institutions, that try to prevent this (EU). They haven't used their power to betray the people enough, so we are still fine with them.
"Wealth comes with obligations" is literally in my country's constitution. You, may don't like that, but I do. I think a lot of other people do as well. It is of course always for discussion how much.
It kind of is their fault because of Google Play Integrity APIs. They are effectively developing tools that are designed to make their product mandatory. There wouldn't be a backlash that big if we could just unlock our bootloaders and run a patched version of Android.
> any [] property can be [taken by the state] from its [original] owners simply by [those owners becoming more powerful than the state wants]
When rephrased like the above, I think what you’re describing is pretty common in history. Many industries and assets have been nationalized when it serves the state’s interests.
IMO the moral justification is that there is no ownership or private property except that which is sanctioned by the state (or someone state-like) applying violence in its defense. In this framing, there’s little moral justification for the state letting private actors accrue outsized power that harms consumers/citizens.
People outsource the brutality (to the government), so that they don't need to deal with it in their daily life. If we couldn't force companies to act in ways we want through a formal system, then the world would look much more brutal.
I can ban persons from doing things, I rather not have them do. Companies are legal persons, so why shouldn't this apply to them? At some point ignoring behaviour is not making it go away, it needs to be actively worked against, otherwise it will become (practically) mandatory.
the core problem with banning is who is doing it and why, right? once we allow it, it goes into the hands of the “politicians” and then books get banned today, ice scream gets banned tomorrow, math gets banned the next day…
Which is why the more serious consequences a law has the harder it is to change it and the more people need to sign off on it. There is stuff that needs simple majorities, stuff that is in the constitution and requires a super majority, stuff that can't be changed short of abolishing the current state and stuff that can't be changed at all, because it is just an assertion that is independently on anyone asserting it.
This is kind of a "solved*" thing in theory, not so much in practice of course.
*solved meaning we have a proper process established
My moral justification is that my right to do with the physical property I have in my physical hand is more important than any noncorporeal corporation's right to do anything with their noncorporeal intellectual property.
The truth is, I gave party C money for a product. Party B does not get to say anything about what party C gave me. And they absolutely do owe me something, and that is the use of the product they gave me for my money. Whatever their terms of service say about licensing versus owning should not trump the fact that I made a one-time purchase and I have physical ownership that they cannot revoke. This is not a car lease where I have a contract with the dealership and they can reposses the car if I don't make the payments.
And you can use it. You can, in fact, keep using the software that shipped on it. What you want is access to further intellectual property they develop (updates, features), that just so happens to be able to run on your hardware and ability to shepherd it in a direction you want and they don’t.
> What you want is access to further intellectual property they develop (updates, features), that just so happens to be able to run on your hardware and ability to shepherd it in a direction you want and they don’t.
Well yeah, I am paying them with money (and data) and thereby with power and expect them in turn to provide directions for my device, so that is does what I want. That's kind of the deal. If they don't want to provide that, then they can just not accept my money (and data). They can of course produce devices, that to what they want, and want me to carry them around, but then they better pay me.
If they use the power I gave them against me, then I will demand my power projection as a service provider (aka. the government) to project power in my interest.
> that just so happens to be able to run on your hardware
the hardware is specifically locked down with "trusted computing" features to facilitate this. It's not a random coincidence. The problem here lies in the network effects and the use of trusted computing. If my bank app mandates that I use "real deal 100% certified android", then I can't just develop my own OS. So it's an antitrust situation.
If every company in the world teamed up with MegaCorp and made their services contingent on wearing a MegaCorp shock collar powered by trusted computing, would you wear it? You are free to not use the collar... and starve to death in the woods I suppose.
I don't usually even care about intellectual property. It's a hack to grant a temporarily exclusive monopoly as a way to incentivize R&D. The R&D in this case is just solving the question of "how do we establish a larger monopoly". So why should the public be forced to uphold it?
Asking me if I am willing to violate intellectual property in this situation is like if I was being lowered into a pit of liquid hot magma and in order to get out I had to break the flag code or jaywalk or something.
Google is engaging in immoral business practices. Since they are immoral, it is morally justified to say they must be stopped.
> how would you feel if you were on the receiving end of such a dictum?
I continue to be astounded how people still just flat out assume that everyone must be a capitalist.
If I were on the receiving end of a dictum aimed at stopping immoral behavior, I would cease my immoral behavior. But I'm not going to be on the receiving end in the first place because I don't aim to do immoral things in the first place.
The moral justification is the same anyone else employs. I have a tool to create an outcome and I'm going to use that tool to produce that outcome. It's that simple.
Just to put out what Google actually said in their blog post [0]:
> We appreciate the community's engagement and have heard the early feedback – specifically from students and hobbyists who need an accessible path to learn, and from power users who are more comfortable with security risks. We are making changes to address the needs of both groups.
> We heard from developers who were concerned about the barrier to entry when building apps intended only for a small group, like family or friends. We are using your input to shape a dedicated account type for students and hobbyists. This will allow you to distribute your creations to a limited number of devices without going through the full verification requirements.
> Based on this feedback and our ongoing conversations with the community, we are building a new advanced flow that allows experienced users to accept the risks of installing software that isn't verified. We are designing this flow specifically to resist coercion, ensuring that users aren't tricked into bypassing these safety checks while under pressure from a scammer. It will also include clear warnings to ensure users fully understand the risks involved, but ultimately, it puts the choice in their hands. We are gathering early feedback on the design of this feature now and will share more details in the coming months.
It is also true that they have not updated their developer documentation site and still assert that developer verification will be "required" in September 2026 [1]. Which might be true by some nonsensical definition of "required" if installing unverified apps requires an "advanced flow", but let's not give too much benefit of the doubt here.
> We heard from developers who were concerned about the barrier to entry when building apps intended only for a small group, like family or friends. We are using your input to shape a dedicated account type for students and hobbyists. This will allow you to distribute your creations to a limited number of devices without going through the full verification requirements.
In classic Google fashion, they hear the complaint, pretend that it's about something else, and give a half baked solution to that different problem that was not the actual issue. Any solution that disadvantages F-Droid compared to the less trustworthy Google Play is a problem.
Even restricting the mitigation to "students and hobbyists" is bad.
I should have the right to have parents, friends or anyone use a "free" store that is not under control of Google if the user and app developer wish so. But also, somehow there should be something done to avoid the monopoly forcing to use the Google services. Like major institutions like bank, gov and co being forced to provide alternatives like a webapp when they provide app tied to the Google play store.
I think you've omitted the next section, which seems more relevant. It seems like they will still allow installs, just hide it behind some scare text. Seems reasonable?
> It seems like they will still allow installs, just hide it behind some scare text.
This was already the case for enabling sideloading at system level: it warned you. Nobody really says having this toggle is a bad thing, basically the user shouldn't get an ad network installing apk's just browsing around the web without their informed consent (and android has been found to be vulnerable to popunder style confirmations in the past).
They also already had the PlayProtect scanning thing that scans sideloaded APK's for known malware and removes it. People already found this problematic since what's to stop them pulling off apps they just don't like, and no idea what if any telemetry it sends back about what you have installed. There have been a handful of cases where it proved beneficial pulling off botnet stuff.
Finally, they also have an additional permission per-application that needs to be enabled to install APK's. This stops a sketchy app from installing an APK again without user consent to install APK's.
The question is: How many other hurdles are going to be put in place? Are you going to have to do a KYC with Google and ping them for every single thing you want to install? Do you see how this gets to be a problem?
Why not? It's their operating system, and they're trying to balance quite a few competing priorities. Scammers are not a threat to dismiss out of hand (i've had family who were victims).
For it to be truly considered open source, you should be able to fork it and create your own edits to change the defaults however you wish. Whether that is still a possibility or not, is a completely separate issue from how they proceed with their own fork.
Of course it's your phone, but the whole point of using Android is that it makes a lot of choices for you. It forces a billion things on you, and this is really no different than any of the others. Everything from UI colors, to the way every feature actually works. For instance, should you be able to text message one million people at a time? You might want to, but Android doesn't offer that feature. Do you want to install spyware on your girlfriends phone? Maybe that's your idea of complete freedom, but the fact that Google makes it harder, is a good thing, not a bad thing.
If you don't like their choices, you should be able to install other software you do like. There should be completely free options that people can choose if they desire. But the majority of people just want a working phone, that someone like Google is taking great pains to make work safely and reliably.
> Of course it's your phone, but the whole point of using Android is that it makes a lot of choices for you. It forces a billion things on you, and this is really no different than any of the others. Everything from UI colors, to the way every feature actually works.
There is a difference between making a choice because there has to be something there (setting a default wallpaper, installing a default phone/sms app so your phone works as a phone) and actively choosing to act against the user (restricting what I can install on my own device, including via dark patterns, or telling me that I'm not allowed to grant apps additional permissions).
> For instance, should you be able to text message one million people at a time? You might want to, but Android doesn't offer that feature.
There's a difference between not implementing something, and actively blocking it. While we're at it, making it harder to programmatically send SMS is another regression that I dislike.
> Do you want to install spyware on your girlfriends phone? Maybe that's your idea of complete freedom, but the fact that Google makes it harder, is a good thing, not a bad thing.
Obviously someone else installing things on your phone is bad; you can't object to the owner controlling a device by talking about other people controlling it.
> If you don't like their choices, you should be able to install other software you do like. There should be completely free options that people can choose if they desire. But the majority of people just want a working phone, that someone like Google is taking great pains to make work safely and reliably.
Okay, then we agree, right? I should be able to install other software I like - eg. F-Droid - without Google getting in my way? No artificial hurdles, no dark patterns, no difficulty that they wouldn't impose on Google Play? After all, F-Droid has less malware, so in the name of safety the thing they should be putting warning labels on is the Google Play.
The problem is that step by step ownership of your device is taken away. First most phones stopped supporting unlocking/relocking (thank Google for keeping the Pixel open), now the backtracked version of this, next the full version, etc.
Yes, that is a real problem. But it doesn't justify arguing uncritically or unrealistically in other areas. I think people should be free to do anything they want with their own devices. They should be able to install any software they want. That's very different than demanding someone make their software exactly how you desire. ie. You should be able to install your own operating system, you don't get to tell them how theirs should operate.
There are legitimate concerns being addressed by these feature restrictions.
> You should be able to install your own operating system
So you draw the line between the bootloader and the OS. Other people draw the line between the OS and applications. Most (nearly all) people can't write either, so for them it is just part of the device.
> you don't get to tell them how theirs should operate.
I paid for it, and I allow it to be legal in the jurisdiction I (partly) control. So it is not only theirs anymore.
> demanding someone make their software exactly how you desire
IMO the way this should work is that Google can make their software however they want provided they don't do anything to stop me from changing it to work the way I want.
Unfortunately, they've already done a lot of things to stop me from changing it to work the way I want. SafetyNet, locked bootloaders, closed-source system apps, and now they're (maybe) trying to layer "you can't install apps we don't approve of" on top of that.
> IMO the way this should work is that Google can make their software however they want provided they don't do anything to stop me from changing it to work the way I want.
That's exactly how it is. You're free to get your soldering iron out, or your debugger and reverse engineer anything you want. I don't mean to argue unfairly, but all we're talking about here is the relative ease with which you can do what you want to do. How easy do they have to make it?
As for their software, as delivered, there are literally an infinite number of ways that it stops you from changing it. Maybe you want everything in Pig Latin, or a language you made up yourself. Do they have to design around this desire? Do they have to make this easy to do?
> They should be able to install any software they want. That's very different than demanding someone make their software exactly how you desire. ie. You should be able to install your own operating system, you don't get to tell them how theirs should operate.
I don't think the distinction exists the way you're trying to describe. If I should be allowed to install any software I want, surely that includes any .apk I want? Conversely, someone could make the exact claim one step down the chain and argue that you don't get to tell them how their firmware should work and if you want to install your own OS you should just go buy a fab, make your own chips, write your own firmware, and make your own phone. And that's absurd, because users should be allowed to run their own software without being forced to ditch the rest of the stack for no reason.
No, I don't think you have the inerhent right to install any apk you desire, if their OS is designed to prohibit it. You should be free to try to alter their OS any way you want, but they should not have to make it easy.
And the argument is the same lower down the stack. You shouldn't be able to tell someone how to design their firmware.
The only problem is where the law prohibits us from trying to undo these restrictions, or make modifications ourselves. It's government that restricts us, and we should focus our efforts there.
> No, I don't think you have the inerhent right to install any apk you desire, if their OS is designed to prohibit it. You should be free to try to alter their OS any way you want, but they should not have to make it easy.
> And the argument is the same lower down the stack. You shouldn't be able to tell someone how to design their firmware.
Earlier, you claimed,
> They should be able to install any software they want.
but it sounds like actually you only mean that users should be allowed to futilely attempt it, not that there should actually be allowed to run software at will. If the firmware only allows running a signed OS, and that OS only allows running approved apps, then the user is not able to install any software they want.
The whole point of using Android for most users is that they have no other choice if they need a mobile phone.
Google killed every other competition via dumping and shady business practices. Sure, you can go to iOS, but that is even more closed and restrictive, not to mention the devices are overpriced.
100%. If I buy something, it's mine. I should be able to resell it, modify it, or generally work on it however I see fit. Licensed digital media bound to platforms is different (barring some kind of NFT solution?) but an OS that my phone cannot function without (and that cannot be replaced in many cases) absolutely must be under my jurisdiction.
You paid for it but Google still has the control. I understand that you prefers things to be different (as do I) but the reality is that we don’t have control over devices we paid for.
You might choose to not have control. The reason people protest is because we should have more control over the things we own. Sure this might create a better market for alternatives but it is worse for most people. F-droid is spectacular.
Why is it reasonable that installing software is behind an "advanced flow" what ever that means? I find it not very reasonable at all that the only way to install software on my phone is by jumping through hoops. I don't think it reasonable that the Play Store is the only portal. I don't even find it reasonable to call installing software "sideloading". Downloading and installing software from a vendor's page has been the norm for decades before smart phones came along but all of a sudden when it is on a small screen the user can not be trusted? That's ridiculous and not at all reasonable.
It's not the screen size, it's the demographic shift. By 2000, only half of U.S. households had a shared living room PC, mostly for work and/or games. Everybody having a phone in their pocket later was a change that we did very much have to account for. Non-technical people can be scammed very easily into life-ruining mistakes with a little social engineering and a little bit of access to powerful tools already on their devices.
I remember when big sites started having to put big banners in your browser console warning you that if you weren't a dev and someone told you to paste something there, you had been scammed, and not to do it. They had to do that because the average Facebook user could be tricked very easily by promises of free FarmVille items or the opportunity to hack someone else's account, and those are fairly low stakes bait. Now people bank with real money on their phones.
The whole point of TFA, if you read it, is that they SAID they would do that, but there has since been ZERO evidence that they actually will. This feature is not present in anything they have released since that statement.
It would be foolish to depend on that & far harder to get ridd of it if they put it in place. There needs to be clear statement and verification method to make sure they really are backtracking.
> It seems like they will still allow installs, just hide it behind some scare text.
That describes the current (and long-established) behavior. App installation is only from Google's store by default and the user has to manually enable each additional source on a screen with scare text.
> We are designing this flow specifically to resist coercion, ensuring that users aren't tricked into bypassing these safety checks while under pressure from a scammer. It will also include clear warnings to ensure users fully understand the risks involved, but ultimately, it puts the choice in their hands.
I've lived through them locking down a11y settings "to resist coercion, ensuring that users aren't tricked into bypassing these safety checks while under pressure from a scammer", and it's a nightmare. It's not just some scare text, it's a convoluted process that explicitly prevents you from just opening the settings and allowing access. I'm not giving them the benefit of the doubt; after they actually show what their supposed solution is we can discuss it, but precedent is against them.
> Seems reasonable?
No. As I said before, any solution that disadvantages F-Droid compared to the less trustworthy Google Play is a problem.
It's deliberately written to be vague and not say anything, and given the original intention, it's hard to believe that means it should be interpreted generously.
> shape a dedicated account type for students and hobbyists.
Even that is a step too far in the wrong direction. Doesn't matter if it's free, or whatever, simply requiring an account at all to create and run software on your own device (or make it available to others) is wrong.
There exists no freedom when you are required to verify your identity, or even just provide any personal information whatsoever, to a company to run software on your device that you own.
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!
> I guess it means the Play store will be the only way to install an app
No, non-Play stores will still work, but developers will need to register a developer account with Google that is tied to some real identity. They already need to do this to distribute through the Play store, but now it'll apply regardless.
This is to make it harder for scam apps to churn app signatures. Kind of like requiring code-signing, but with only one CA.
> That users won't be able to install what they want
No, sideloading will still work, but it won't work if the APK isn't signed by someone in the Google developer registry.
> and that they would need a google account to install apps
Nope.
> That app developers have to go through google to distribute their apps, with identity verification etc.
They don't need to distribute through Google, but they will need to be involved with Google and do identity verification.
> 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?
You're being misinformed. They won't even need to strip the verification. The verification is only for certified Android -- OEMs that partner with Google. Custom ROMs and the OEMs that aren't certified (Amazon, some Chinese manufacturers) won't have verification.
The target audience for verification and who would ever use a custom ROM has basically zero overlap.
This isnt going to be a popular post because the HN crowd is very much a "China bad" crowd but I hypothesize China will likely step in and offer a fork that's compatible with open ecosystems not under the direct control of the us state department. This might be in the form of commits and investment in fdroid and pinephone, or a tiktok like alternative to the wests walled garden.
Edit: this will likely exist "uncensored" in other markets but conform to the PRCs standards and practices domestically, similarly to how tiktok operated prior to selling a version specifically taylored to US censorship and propaganda.
Not a chance. A fork that is under China's control, maybe, but not an "open" fork. They don't even pretend to have that as a value.
You may theoretically find it advantageous to use such a system anyhow. To a first-order approximation, the danger a government poses to you is proportional to its proximity to you. (In the interests of fairness, I will point out, so are the benefits a government may offer to you. In this case it just happens to be the dangers we are discussing.) Using the stack of a government based many thousands of miles/kilometers away from you may solve a problem for you, if you judge they are much less likely to use it against you than your local government.
But China certainly won't put out an "open" anything.
Not sure if you have been following the LLM space or even the emulator handhelds space, but Chinese companies have been doing great with putting out open source software lately.
The irony is that software coming from China is a lot more open than western software. Biggest examples are huggingface models mostly coming from Chinese institutions. Its also strategicaly wise for China to go this path.
Maybe a shift to Huaweis HarmonyOS with its android compatibility layer or SailfishOS if they play their cards right.
As far as HarmonyOS i dont see many uptakes outside strict US free requirements as the other OEMs are lazy and also dont want to be locked into a competitor.
SailfishOS looks like its your time to faceplant once more , by not having a proper stratergy on monetizing on the many missteps from the current monopoly.I thonk at this point they need a leadership/biz stratergy overhaul - the tech is nice and polished, user demand is off the charts for an alternative . And they are just .. missing. Not even in th e conversation.
Pinephone is tragic, bought a bunch of Pine64's devices (PP, PPP, PB, PBuds, arm tablet, eInk tablet) but old tech, missing drivers, can't blame em no money no drivers... Still the community on Discord is great/helpful people.
That'd be great but I'm not feeling like the Chinese market is too worried about open development. I got a Huawei Watch 5 as a gift and I liked it enough to try to develop my own apps (their app store is a wasteland) but to my surprise Harmony OS is not Android compatible (just Android based somehow). The watch's developer mode is useless. Trying to register a developer account is almost impossible and it seems they only allow chinese nationals and there's no plan to open registration. I couldn't even download their custom IDE (something like Android Studio) without an account.
Yeah, I’m amazed at how far the western surveillance apparatus has been able to coast on plausible deniability. Folks, please don’t stick your head in the sand domestically just because there’s an even more obvious or egregious example abroad.
Say it with me: “Living in a police state is bad no matter who’s running it”.
I'm just imagining the poor intern at the NSA having to sit in a dimly lit room with an array of 64 x 64 monitors mounted on a wall, watching the O-faces of thousands and thousands of fat, balding, middle age men for hours straight.
The link is to the f-droid blog. The official "Keep Android Open" site is at https://keepandroidopen.org/, and contains good information on how you can contribute by contacting regulators.
It's also heavily influenced by businesses. Most employers will happily hand you an Apple or Android phone for work, but I don't think there is a single company out there that would dare to hand normal people an Ubuntu Touch based phone.
We (people who live in a country/confederacy with working antitrust laws) have power to keep large companies from anticompetitive practices such as this one.
If they close things up with no alternative, the free open source software will likely start to catch up. it will take a few years though. This could be a blessing in disguise.
There is just no reasonable way that the open source community can compete with a $3.8T company. And before you say something along the lines of, "But they don't need to compete, they just need to be good enough", that still requires business to put their apps on some open source app store and make them compatible with the open source OS, and there is close to zero incentive for them to do so.
it's becoming ever more clear to me that i'll have at least two devices: one running software i trust, one running software corporates trust, with a very narrow pipeline connecting the two, if it all. my demon-haunted device can stay offline in my bag and get hotspot'd in to my trustworthy device as necessary.
not happy about it, but i don't see a path forward that lets one participate in the wider ecosystem and maintain their own sovereignty and sanity.
If I can't use banking or my NFC wallets on my phone, it has become 90% useless. The other 10% of usefulness is texting and calls, which every other phone can do.
Unfortunately, this mostly means using the closed android ecosystem.
I run Graphene on my Pixel and banking apps just work. There is no Google Pay, obviously, since Google dependencies have been stripped out from the system. I just carry a credit card.
No inherent reason all that stuff can't work on an open platform. It works just fine on my Linux box with yubikeys, fido2, and smart cards. Gcloud even let's you authenticate with them only to put a medium lived token in plaintext into a sqlite file on disk.
That's pretty much my usage pattern too, including some group texting, the occasional call and sometimes taking photos/videos. Otherwise my phone pretty much stays in my pocket or on my table the entire day. What are you using your phone for that makes that so unbelievable?
Web browsing (like right now), photos, e-books, lots of messaging, music, sometimes video.
I use NFC payments often, but I wouldn't say that amounts to more than a few percent of my total usage.
Everyone uses their phones differently, of course. I don't think your use is unbelievable or odd, but I do think your use patterns are not the common case.
The ability to install signed and unsigned APKs directly correlates to the financial institution policy regarding mobile devices and banking apps. Unsure how you've separated these two.
I run GrapheneOS and use several US-based banking apps. I'll not name them since I don't really want my HN account associated with my financials in any way, but I've got a mix of well-known national bank apps and smaller local credit union apps working.
I'll admit there is a single institution's app I've found that doesn't work, but that is just one of several that I use.
For me, the showstopper would be NFC payments. From what I understand, Google Pay doesn't work on Graphene. I have all my credit cards in GPay, as well as a transit card. I use it for boarding passes when I fly, and any other tickets/passes that support it, since it tends to be much more reliable than the airline or ticketer's app. I've come to heavily rely on it, unfortunately.
I haven't tried this, because I try to minimize Google exposure, but I think Google Wallet (minus NFC payments) works on GrapheneOS. So, tickets, boarding passes, etc. should work fine.
>this mostly means using the closed android ecosystem
Maybe, but there's no technical reason for this. As I've mentioned before, I can do banking just fine on my Gentoo machine where the entire corpus of software on it, is FOSS and compiled by myself.
This is a common answer but it does not apply to at least most of Europe. Because of regulations most banks require to install their app either on iOS or Android to act as a 2FA device. One of my banks gave me a hardware device 20 years ago. When its battery dies I'll have to use their app and my fingerprint.
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 are home are still considerably cheaper than Apple and Samsung devices, and give the users far more privacy and freedom.
How do you install the bank app if google does not allow you to install APKs manually / with a 3rd party store? You have to go with Google Play. Which requires a Google account. So I can't do it. That's the whole point of this thread: it would not be possible to use Android without a Google account.
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.
When I was still rooting it was possible to bypass this on a rooted device with enough effort. It wasn't unsecure either. Padentic corporate security doesn't really make us more secure. Just more lazy.
Since smartphone apps are often times required to do banking or identifying yourself now and there's tons of special apps in order to use appliances, and by that I mean really the only way to use modern appliances is by a smartphone app, emulating an Android environment on a laptop or PC with a bluetooth dongle is essential if you want to leave that smartphone era behind you for good, but still be able to function in this society.
The biggest surprise I had in attempting to distribute my first Android app is how difficult it is to get beta-testers through the "standard" channels. It requires a 1 week review and 25 beta-users invited by email addresses
In contrast, Apple has a ~48 hour turnaround for reviews before you can upload to TestFlight and distribute a beta with a link
Not sure if I am in some "trusted developer" cohort on iOS but not Android - but the difference was enough for me to stop trying on Android
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.
I question whether an OS that has always been controlled by Google has ever been open.
Sure parts of it were, but Google has always remained in control of Android. Anyone who expected that to change (in favor of more openness) hasn't been paying attention to the actions of tech companies for the past several decades.
The relative openness is the reason I gravitated towards Android and Google. I've never really taken advantage of it, but it's nice knowing it's there and that my phone (a Google Pixel) is something I have more control over than with other vendors.
Amusingly, if Microsfot didn't have a such an awful reputation ( both recent and old ), their newly announced phones could have actually been a viable competitor.
This is where I wish someone like MKBHD and others with big Android followings would speak up and say they will both blast this practice and not review any new Android phones/(Google) apps unless there's a full walk-back of this position.
the frustrating part is that the "advanced flow" alternative Google mentioned still doesn't exist in practice. the media ran with the reassurance headline and most people think the issue was resolved.
What people forget is that the real monopoly is in how the AOSP hardware OEM contract is written....
Remember how hard Amazon had it to attempt an Android fork?
I was due to OEM SOC access being locked out due to those contracts....
Any open source mobile OS attempting to complete with AOSP needs access to mobile OEM soc providers not touched by AOSP contracts and currently that is somewhat hard.
Crazy idea: when companies change their product, they have to change the name.
Do you ever feel like the same food item doesn't taste the same it did 10 years ago? Maybe it's your memory being faulty or maybe the company got new management which decided to cut costs while keeping prices, extract the differential value from customer inertia and move on when the product stops being profitable.
Android is the same. Certain freedoms were a part of the offering - a part of the brand name. They no longer are. Not only should lose their trademark[0], they should be legally forced to change the name.
[0]: The purpose of which is to identify genuine product from counterfeits - in this case, the counterfeit just happens to be by the same company which released the original product.
>But Google said… Said what? That there’s a magical “advanced flow”? Did you see it? Did anyone experience it? When is it scheduled to be released? Was it part of Android 16 QPR2 in December? Of 16 QPR3 Beta 2.1 last week? Of Android 17 Beta 1? No? That’s the issue
A bit ironic to not believe Google is doing this. The same questions have same answers when asked about when Google is locking down side loading. A bit self-serving to pick and choose which things you want to believe are happening.
Google made the first move with their initial plan to lock it down, so the onus is on Google to calm the fears they caused if they don't want people to distrust them.
Android was never open. User apps are limited, only system apps can do X which means third party apps can't compete with Google and this is not a coincidence.
Let's focus on making it possible to use really open Linux systems on smartphones.
I still can't comprehend why they implemented FIDO/WebAuthn support in Play Services. Passkeys are extremely difficult to support in apps that don't depend on Play Services client libraries.
I'm not sure what you're referring to, but I was talking about the whole permissions system where the user is a third class citizen. Device manufacturers are second class citizens (restricted by Google via CDD/CTS) and the only true winner on that system is Google.
Regarding some concrete examples - Google can deeply integrate Gemini, but a competitor can't do this and users get no final say here either. Competitors are restricted by the permission system, Google is not restricted at all.
While rooting can alleviate this to some extent, Play Integrity is there to make sure the user regrets that decision to break free..
Just like Microsoft screwed up Windows, Google will screw up Android and people will move to Linux on PCs and some open version of Android, or Harmony, or whatever new mobile system comes up, on their phones.
Nothing lasts for ever. The sooner you make the switch, the better off you will be.
Capitalism is the privatization of human needs. As long as these tech platforms are owned privately they will be used to police and make money.
This view NEEDS to be central to the tech freedom rhetoric, else the whole movement is literally just begging politicians and hoping corporations do the right thing... useless.
Aren't the politicians or their appointed bureaucrats who'd be making all the decisions if these needs were government owned? Why would state control lead to less policing? What incentive structure would lead to innovation without a profit motive, when even the modern communist world relies on capital markets?
> Aren't the politicians or their appointed bureaucrats who'd be making all the decisions if these needs were government owned?
Well that would be true under a capitalist government.
> Why would state control lead to less policing?
Its not just "the state runs it", its "we actively become the state".
Collective ownership through peoples councils, peoples courts with a world view that keeps it all open: socialism.
The world view of not allowing individual ownership over collective goods, the world view of socialism, is the life line of the movement. The actual practice of daily democracy, of running production and of deciding social functions is everyones responsibility and it should not be left to what has become a professional class of liars.
Public office members, which should only exist where absolutely necessary, should be locals and serve as messengers with 0 decision making power. All power should be in the local councils. We can mathematically implement this today (0 knowledge proofs).
Every single book on socialism is on theory and practices of acheiving this. Thats what the "dictatorship of the proletariat is", the dictatorship of working people, collectively.
> What incentive structure would lead to innovation without a profit motive, when even the modern communist world relies on capital markets?
We've been innovating for hundreds of thousands of years before capitalism. You dont need to generate money to innovate, the innovation itself is the driver, AKA a better life. No need to lock and limit production behind the attaining of profits of those who lead it.
A lot of people are allergic to this rhetoric and will just assume I have a deep irrational bias, but I was actually a staunch free market supporter before.
Once I decided to be more intellectually honest with myself and read more about what both sides meant historically and currently, it really just made sense.
I'm so exhausted of the partisan "my team vs your team" politics in the US that shuts down conversation, overlooks the blatant hypocrisies on either side, simplifies every issue to a single label to plaster on your opponent, etc etc.
I take honest conversation where I can get it, even when I don't agree. And to be clear I don't agree with most of your points and think it's idealistic and couldn't work in the real world. But I appreciate the spirit of what you're arguing for (in my interpretation) power with the people vs power with corporations and government and I think that's a very fundamental principle that is very important common ground.
If we force it upon them by begging politicians, corporations still have the incentive to find a way to remove it or circumvent it.
Youre playing the cat and mouse game because you've been taught that solving it is too extreme (thats not a coincidence).
We dont need to endlessly fight a whole class of people, capitalists, for them not to use the things we require against us. Only socialism can solve that.
From a marketing standpoint it seems like a baffling decision on Google's part.
I own a Pixel and while the hardware seems decent, I've had a buggy and annoying experience with Android, and it's been getting worse lately.
Are Google so high on their own supply that they think people use their phones out of preference for the OS? Because frankly it's not very good. That's like Microsoft thinking people use Teams because of its merits.
People buy Android phones because they can be had cheaper than an equivalent iPhone and because in spite of the buggy and inconsistent mess of an OS, you aren't beholden to Apple's regimented UX. Locking down Android will not give it a "premium experience"... It'll always just be "Temu iOS" at best.
Have you considered Graphene since you own a Pixel? It's a huge upgrade over the stock OS in terms of security, privacy and general reduction of bloat.
Having just gone from an iPhone as my main phone to a Pixel with GrapheneOS, GrapheneOS is such a breath of fresh air. No constant push of AI, iCloud services, etc. plus I actually feel owner of my phone and not living on some feudal landlord's plot.
There are several topics where Android is significantly ahead to the point that iOS is just a toy, and there are areas where the reverse is true.
And I say that as a recent convert, so it's not like I have a decade out of date view of any of the OSs. In my experience I had more visual bugs in case of iOS than android (volume slider not displaying correctly in certain cases when the content was rotated as a very annoying example).
It's not, though. Google phones are not going to suddenly become luxury devices.
It's going to remain at the same level of polish (i.e. mediocre), except now without the major selling point of being able to run your own apps and have alternative app stores, etc. Back around Ice Cream Sandwich or thereabouts they got rid of "phone calls only mode" and forced us to rely on their half-baked "priority mode" that's an opaque shitshow.
When my wife is on call she gets random whatsapp notifications dinging all night, whereas when I had an iphone I could set Focus mode and achieve proper "phone calls only".
Android is not good. I use it despite its flaws, because of the trade-offs, not because it's better.
> Google phones are not going to suddenly become luxury devices
Pixel Fold disagrees.
> When my wife is on call she gets random whatsapp notifications dinging all night, whereas when I had an iphone I could set Focus mode and achieve proper "phone calls only".
You can do that with do not disturb.
> Android is not good. I use it despite its flaws, because of the trade-offs, not because it's better.
You can definitely make a "phone calls only" mode: create a mode, allow certain apps to interrupt, and add only phone calls to the list.
I do think they should offer more pre-configured notification modes by default, if only to show people what they can do with the feature. Perhaps "phone calls only" should be one of those.
People buy high-end Android phones like crazy, I don't know what bubble you live in. Samsung Folds and Flips are the luxury phones, not the iPhone Pro Max S eXtreme Edition 32 GB that looks exactly like the base model but has a slightly better camera. People show off their S Pen and perfectly stabilised 100x zoom lens, not their liquid ass. Multi-window and DeX are features for professionals who need to Get Shit Done^TM, iPhones are the toys kids use to send memojis to each other.
And yes, I can also click one button and go into phone calls only mode. I can even set it on a schedule or based on my calendar. I don't know where you're getting your half-baked Android, mine Just Works.
You might not agree with every one of those points, but you can't seriously think everyone thinks like you. Go outside your bubble some time.
Putting "Samsung" and "luxury" in the same sentence is lunacy. Their proprietary Android is even worse than Google's.
Where do you live? I've literally never seen anyone using a Fold or Flip device, ever. My kids are at the age where some of their peers are starting to get phones. All those kids have iPhones.
If your plan is to keep saying unsubstantiated bullshit, take that to Reddit. Go to a store and try modern OneUI - it's just AOSP with a slightly different layout and more features. The apps are worse than Google's, but the OS is better. Both are miles above iOS in features, especially for power users. Split screen, windows, chat bubbles, DeX, notification categories and history, vendor-neutral PC integration and TV casting, ...
And I don't quite see your point about your kids' friends using iPhones. I sure as hell wouldn't give a kid a "luxury" phone. I'd take the cheapest thing that does the job and lasts a long time. An iPhone has a very long software support window so the cheaper models actually end up cost-competitive with budget Androids.
As for folds and flips, I've mostly seen people in suits using them, along with a few techy power users and some kids with rich parents. That's a luxury phone in my book.
> Are Google so high on their own supply that they think people use their phones out of preference for the OS? Because frankly it's not very good
Honestly having gone back and forth between iOS and Android every three years or so, both OS are the same. It's not like the grass is really greener on the Apple side. The UX is virtually identical for anything that matters. Personally I put material Android above liquid glass iOS. The alleged polish of the Apple UX was lost on me when I had my last iphone.
The reason Google's moves are surprising has more to do with them embracing being a service player more and more with the arrival of Gemini and them having regulators breathing down their necks everywhere.
I guess they did it after the truly baffling US decision in the Epic trial but it's very likely to go against them in the EU.
The rumors that I have heard (and one government document I read that was poorly translated from Thai) is that there are some countries who are pressuring Google on this to combat info-stealing malware. Apparently, account-takeover/theft is very prevalent in SE Asia where most banking is done via Android phones.
Maybe but lobbying is extremely strong in SE Asia. It's hard to distinguish from governments putting pressure for something and companies suggesting it would be a good idea.
Fairphone 4 looks close, hopefully fairphone 4 support will continue to improve at this rate. Pinephone is another close one, but underpowered hardware and camera support kills it.
I am not even that intensive of a phone user. but there is no way I could daily drive pmOS.
It is a disgrace how Google has managed this situation.
To recap the storyline, as far as I understand it: last August, Google announced plans to heavily restrict sideloading. Following community pushback, they promised an "advanced flow" for power users. The media widely reported this as a walk-back, leading users to assume the open ecosystem was safe.
But this promised feature hasn't appeared in any Android 16 or 17 betas. Google is quietly proceeding with the original lockdown.
The impact is a direct threat to independent AOSP distributions like Murena's e/OS/ (which I'm personally using). If installing a basic APK eventually requires a Google-verified developer ID, maintaining a truly de-Googled mobile OS becomes nearly impossible.
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.)
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 had an insurance company's app installed.
Am I just an outlier here? Honestly, if I switched to a non standard OS, I'd be more annoyed about losing, say, Google Maps, Uber/Lyft, or various chat apps. Banking and insurance just don't come to mind at all as something I need my phone for.
My bank sends me an alert when my card is used to make a transaction - handy for spotting fraud.
I get an alert when a payment comes it - handy for knowing if a client has paid.
I can quickly check my balance - handy for knowing if I can afford another round of drinks.
I can repay a friend in two taps - handy if they've paid for dinner.
Is anything essential? No. Is it something people use multiple times per day? Yes!
Could all of these be handled through openbanking?
Yes
I can get alerts in email or messages, no need dedicated app for that, I can track there also my balance, so only useful thing app provides are easy wire transfers from phone, which I never do, if I wanna transfer money is much more convenient work big display, proper keyboard and mouse than from phone.
That's great for you but unfortunately the overwhelming majority of people do indeed regularly use these features.
"I'm am just an outlier here?"
No. The "banking app doesn't work" argument against non-corporate mobile OS, raised incessantly is HN comments, is bogus
I want a "phone", i.e., small form factor computer, that can run something like NetBSD, or Linux. But I have no intention of using it for commercial transactions. Mobile banking is not why I want to run a non-corporate OS
I want to use it for recreation, research and experimentation
> I want a "phone", i.e., small form factor computer, that can run something like NetBSD, or Linux. But I have no intention of using it for commercial transactions. Mobile banking is not why I want to run a non-corporate OS
> I want to use it for recreation, research and experimentation
I am a firm believer that phones are personal computers and should have all the end user freedom we have come to expect from personal computers. I am totally behind what your saying. (The amount of irrational anger that wells up in me when I hear someone make the argument that phones are somehow not general purpose personal computers and shouldn't provider their owners software freedom would astound you.)
Personally, I opt out of services that require the use of phone "apps" and any potential attestation they provide. Unfortunately, I just offload those needs onto my wife and her iPhone.
Want to go to a concert in a TicketMaster venue? You have to have a phone. Pay to park in some places requires a phone. Mobile ordering for some restaurants requires a phone.
I don't think it should be this way, but it is. I think we need consumer regulation to insure software freedom on phones and curtail awful user hostile "features" like remote attestation.
Until that happens (if it ever does) there is a realpolitik with needing corporate phones for some activities that can't be denied.
2FA is a requirement in Europe. I can't log into my bank account without my phone being able to run the app.
But 2FA is moot if it’s the same device as your bank app, is it not?
Yes. Please tell my bank that.
I would stop using bank requiring phone app to do banking, simple as that, both my main EU accounts use sms verification codes and extra password, which is fine with me. If they will require an app, they will lose customer.
2FA and Google SafetyNet are two completely different things. Your banking app can implement 2FA without SafetyNet.
Banks often use their app for a second factor auth. here.
I can't deposit checks over the website, and I use a bank with no physical locations near me.
That's true, but the notion that we're still using paper checks in 2026 is so crazy. And yet they remain the cheapest way to handle many transactions in the US financial system. Like a lot of small healthcare providers still prefer to receive paper checks from insurance companies because the electronic payment processors take a 3% fee.
I haven't had issues with the mobile apps of 3 of the most major US brokerages. They run fine on rooted phone. They do everything I'd want a bank to do anyway.
Ditch your bank if they have issues. If their retention department asks why you're leaving, tell them their app doesn't work.
The best solution for this is to buy a $30 burner phone at Walmart and use it unactivated, tethered to your main de-Googled device. You can use the burner for only tasks requiring Play Integrity.
Make sure to leave one star reviews on all such apps that you run into.
Have a look at this post
https://news.ycombinator.com/item?id=46723594 from Emre @emrekosmaz
It is a smartphone that runs Android, launches Debian, and dual-boots Windows 11
Actual link https://nexphone.com/blog/the-tale-of-nexphone-one-phone-eve...
Until Android is crippled it will continue to take resources away from Linux Phone development and companies that will launch phones for it
For me as a desktop linux poweruser, I find this potential transition pretty intimidating, I've never flashed a phone with a custom rom let alone switch to a completely different OS, and I am not sure if the phone can even be reset to its original OS, if things go south.
It's relatively easy. It's basically a command for each step you want to do and it tends to fail gracefully nowadays.
If you can install a linux distro you can flash a custom rom on a well-supported phone.
If it were more mainstream I could see GUI apps to manage all this for people, if they don't already exist. Idk I just use adb.
It's also high risk. I've bricked two phones doing it.
I flash phones almost every other week. And tablets. I have been flashing since Androids came out. But never bricked. But maybe that is why I don't have any problems.
I've been flashing phones for over 2 decades and have never bricked a phone. How did you manage that?
Same here. Just follow the LineageOS steps.
Are you seriously implying that flashing phones doesn’t risk bricking them or you’re not aware of that risk are you serious?
I am seriously unaware of the risks and also flashing brand new phones :)
> Are you seriously implying that flashing phones doesn’t risk bricking them or you’re not aware of that risk are you serious?
Yes, that is generally the case. As a general rule with an Android phone reflashing the OS itself or the bootloader carries no risk of bricking the device (meaning making it impossible to recover without specialized hardware and/or opening up parts that were not intended to be opened).
There are plenty of ways to "soft-brick" a device such that you might need to plug it in to a computer, and adb/fastboot can definitely be a pain in the ass to use (especially on Windows), but if you have a device with an unlocked bootloader it's very rare to be able to actually brick the device while doing normal things.
Now, if you're doing abnormal things like reflashing the radio firmware you can absolutely brick some devices there, but you don't have to do that just to boot an alternative OS and generally shouldn't be doing it without very good reason and specific knowledge of exactly what you're doing.
I'm not going to say there are no devices where the standard process to flash an alternative OS is dangerous, but none of the relatively common ones I've ever owned or used have been built that way because OEMs don't want their own official firmware updates to be dangerous either.
tl;dr: It is sometimes possible to brick a device by flashing the wrong thing incorrectly, but the risk of doing that if you are just installing an alternative OS through a standard process is basically zero.
Potential for a brick varies massively depending on phone model, doesn't it?
it's pretty much impossible to hard brick phone, you can almost always recover it
I'm running custom ROMs for the last 15 years
That describes relatively easy for you, but not for the average person who can’t even be bothered to change the default ringtone.
The challenge I've found when looking for instructions for flashing one of my old phones is the assumption of knowledge some rom builders have, or perhaps an assumption about their audience. This seems like it has the potential to bit someone in the ass because if they're relying on other sources like the lineageOS wiki or forum posts elsewhere for example there's no guarantee it'll stay available, complete, or relevant to their variant over time. It's an added burden for what is a gracious volunteer role, but it's a handicap if they want more people using the fruits of their labor.
Expecting Google to give up control of one of the only alternative operating systems is right up there with believing in the tooth fairy.
What you're saying should happen, but it will only happen when the government legislates it happens; which frankly they should be doing (along with nationalizing a few other software projects to be fair).
A trillion dollar transnational corporation with massive monopolistic tendencies will never ever do the right thing. Expect to force feed it down their throats.
In general, governments seem to be much more invested in making it illegal to have anything that is too open and too free. Even EU is lusting for draconian control features like chat control where you don't own and operate the software you installed on your device even if, at the same timem, they're trying to gnaw on the influence of Big Tech.
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 encrypted bits and wait on Moore's law or sufficient cubits to go back and crack the copy, on the off chance there's anything they want with your data in the first place.
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.
> If it's got a sim card, it's still phoning home and providing location data
Only when the kill switch is on. I control it.
Also, it's possible to get AweSIM service hiding your data from the mobile operators.
For sure - and you can use WiFi only, set yourself up with a HaLow rig and give yourself a ~10mbps connection anywhere up to 10 miles from your home, suitable for voip and low rate streaming, throw in VPN, and remain completely off-net as far as cellular networks go. I'm actually planning on using a wireless touchscreen and mobile halow/raspberry pi network/storage stack to completely replace my phone, but the bigger issue is automated tracking of everything - if you're the only blank spot in a sea of known individuals, it's just a matter of seconds to id you, since everything everywhere about everyone is tracked online.
We should be enforcing informed consent regulation of network infrastructure, treating privacy and anonymity as synonymous with liberty and freedom. Allowing the system to operate as it does is a choice; those with lots of money get to make it grow by exploiting a constant invasion of privacy with no concurrent return to the society being exploited.
Phones aren't built to be privacy respecting, and kill switches are a mitigation of a symptom, they don't do anything to address the disease.
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.
I don't care about specs, I care about functionality and price. The camera on the pinephone doesn't practically work because it is too slow and the quality sucks. You basicially cannot record videos whatsoever. I can't use the device for GPS navigation. I can run whatsapp within waydroid, but it isn't practical due to the battery life and startup limitations that imposes. The GPU on the pinephone sucks, is underpowered, doesn't support OpenGL ES 3 or vulkan, and the user interface is always slow as hell to navigate.
So practically I cannot use it as a daily driver.
Librem 5 does have enough GPU horsepower, a functioning camera, and good pmOS support. But $800 is a lot to ask to test out switching to linux with no guarantee that my workflow will work or I will have enough battery life. It looks like the librem 5 can't record videos or do GPS navigation yet.
I am looking at the librem 5 specs again. The EG25-G is probably a better starting point for the modem now that it has been better documented and reverse engineered as a result of the pinephone project. It is interesting that the L5 has a generic smartcard reader though.
> If this finally pushes adoption of truly open Linux phones...
It won't.
There is an implicit shame in disgrace but faceless entities have no shame. They'll just put out another press release written in corporate newspeak by an LLM and move on withe the plans anyway. This is standard Google behaviour. They do it with Chrome, they do it with Android, they'll keep doing it with all their captive markets. I fear that in practice even having an "advanced flow" will make little difference as some applications will refuse to work if you have it enabled anyway (in the same vein if debugging is enabled, for example).
Nothing about Android is open except the absolutely minimum amount of linux kernel that's required to boot the thing. Then it's blobs and restrictions all the way to the screen.
Good news: You (as a community) can now finally wake up from your dreams and get some things right!
It's really a shame that you always wait until you really get forced. Particularly in situations when every individual's inability has consequences for the others as well. I really gave up all ideas of a better world. With this community, the best you can hope is that the decay will be slow.
So everyone who would describe himself/herself as a FOSS enthusiast, or at least a friend of a somewhat open system where the user has some actual rights beyond sole consumption, put some pressure towards having actually de-Googled systems. A system that mostly comes from Google, would not fit my definition of that term at all! Even if they removed some parts of it. It's an euphemism. And it's dangerous because you constantly get trapped by these euphemisms. Ever. Single. F'ing. Time.
Good thing restricting side-loading isn't legal in the European Union! Not a problem here. Apple had to enable side-loading on their EU-based phones and so will Google if they restrict it.
Yes it is, and no they didn't. Apple has to allow (heavily restricted) alternative app stores, and I'm not clear on whether any actually exist right now.
My understanding is that how Apple is restricting the alternative app stores is also illegal in EU, so I don't thinkt this is the end of this story.
It's almost two years and they are still doing it. So they are moving mighty slow if that is the case.
Yes, these things move slowly, but they do move =)
How specific is the law? What if side loading requires a "trusted" signed certificate where trusted means from Google Play?
Not even playing devil's advocate, just wondering how many loopholes actually exist.
If a lawsuit tackles this problem in the EU, will we finally also see somebody go after MS for their obnoxious code signing certificates?
While MS code signing certs are more circumventable for power-users than Android's new approved developer program, their pricing is far more prohibitive for independent OSS developers and hobbyists, costing hundreds of USD per year.
The kind of "side-loading" of notarized apps outside the manufacturer's app store that Apple allows in the EU is exactly what Google proposed to do for all its Android builds. We don't want that.
The only reason I was sticking to Android for years is this. And I think there is no moat for Android. I would rather switch to iOS if both platforms are same restrictive.
The impact is a direct threat to independent AOSP distributions like Murena's e/OS/ (which I'm personally using).
I don't think this is true, right? An AOSP build can just decide to still allow installing arbitrary APKs. Also see this post from the GrapheneOS team:
https://mastodon.social/@GrapheneOS@grapheneos.social/116103...
You can’t really do that long-term as Google will change code that will not match however you are not enforcing this policy
So at the very least you’d have to keep patches up to date.
Long term divergence could be enough that’s it’s just a hard fork and/or Google changes so much that the maintainer can’t keep the patches working at the same pace
I couldn’t read your link as it asks to join mastodon.social
All distributions involve maintaining patch sets. The question is what the marginal burden of this particular patch is.
Doesn't require me to sign in or create account...
The patch set for graphene is substantial, this is a relatively minor change.
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
Strong disagree. Linux, its permission system and its (barely existent) application isolation are lightyears away from the security guarantees that Android brings.
Desktop OSes and their derivatives are woefully behind in this regard, and unfortunately the will to bring them up to par is incredibly weak. Of those in mass use (Qubes OS is neat but its user base isn’t even a rounding error), macOS probably does the most, but it’s still lagging behind iOS and what’s been implemented has come with much consternation from the technically inclined peanut gallery.
I understand some amount of reticence with commercial OSes, but there’s no justification for being against it on open Linux based desktops and mobile OSes. We really need to get past the 90s-minded paradigm of everything having access to everything else all the time with the only (scantly) meaningful safeguards coming in the form of *nix user permissions.
> We really need to get past the 90s-minded paradigm of everything having access to everything else all the time
I do agree with that, and I strongly believe that the iOS and Android security model is way ahead of Desktop Linux. But what I observe is that nobody seems to care about the security model. A recurrent complaint I see against anything AOSP-based (including Android) is that people "want to be root".
It comes from a history of using mostly trusted application sources like Debian/Ubuntu package archives with manual review being the norm. And few supply chain attacks.
But both Flatpak and Snap offer this new model from the two biggest desktop players in the Linux world: Red Hat and Canonical.
As the sibling comment said though, being an administrator for your own computer (including a phone) does not mean that you will be running untrusted applications as one: on the contrary, if you assume an administrator role and run an untrusted application, naturally, all bets are off. But even as a power user, I'd love to be able to safely run programs I do not necessarily trust, feeding it only data it needs and no more.
Again, Snap/Flatpak provide this model, but we need to see more application authors take them up to ship their software.
Allowing the owner of the device root access doesn't necessarily break the security model. It just means that the user can grant additional privileges to specific apps the owner has decided to trust. Every other app still has to abide by the restrictions.
The fact that Android complains and tells any app that asks whether the owner actually, you know, owns the device they paid for is an implementation detail.
A Linux distribution that adopts an Android style security model could easily still provide the owner root access while locking down less trusted apps in such a way that the apps can't know or care whether the device is rooted.
Fun fact - on most Linux distros any user program can see almost any event, yes including key presses, by reading from the right /dev/... file.
This is not surprising. The desktop Linux community reacted with hostility to the well funded security efforts (selinux, apparmor, grsecurity, etc)
Do you have any source for that claim? That would be a pretty serious security issue even unrelated to any security hardening (eg. on a multi-user system, one user could read out the password from another user — even with desktop usage, second user could be SSHed in).
As a datapoint, everything in /dev/input/* is owned by root:input on my Debian Bookworm install, and my main user is not a member of the "input" group either.
Biggest problem with most security hardening for Linux desktop is that it breaks the natural usage pattern: I store my files by their content, not by their format (eg. I might have a folder for my project containing image files, spreadsheets, FreeCAD files, maybe even some code or TeX/ODF files). If programs are restricted to access the entirety of my $HOME though, there is not much benefit to that protection since that's where my most valuable data is. If they are restricted to per-program folder, I need to start organizing my data differently and unnaturally.
Android mostly does not use the "files" metaphor and basically does exactly that (per-app data): coming up with a security model and file management UX that does both is where the challenge is.
Security is a tradeoff (fucking always...)
It's the same reason I choose to keep my front door unlocked basically all the time - I know my neighborhood, the risk is really low and the convenience is high.
Further... practically everyone agrees that they don't need bank vaults as front doors. It makes zero practical sense: The cost is incredibly high, and the convenience is very low.
There are ALL sorts of wonderfully cool things you can do on a system where applications are allowed to trust each other, and the system is permissive by default.
You can customize behavior more easily, you can extend software more easily, you can add incredibly detailed & functional accessibility support, you can create incredibly powerful macros and commands.
This is so important that fundamental OS design from the early 90s actually prioritized and catered to exactly this style of open, trusted, platform (ex - all of COM in windows...). This is what made personal computing a reality...
All of those fall flat when you try to impose "well funded" security efforts.
Those efforts have a place, in the same way that bank vaults have a place. Whether that place is a personal computer is a different question.
Implying those folks are hostile for no reason is... at best a woeful misunderstanding of the situation, and at worst a malicious mischaracterization.
Flatpak and Snaps are built to solve this. They do conflict with some expectations from users to be able to play around with things, though, so they do not have the penetration one might want.
They only cover the user-facing app part of the story. The rest of the system needs isolation and safeguards, too, including things like the desktop environment and whatever random daemon.
A solution that's integral to the system and not just loosely taped on is required.
Flatpak provides very weak sandboxing compared to android. It was more about packaging and distribution than security.
Aren't all the necessary pieces for something better essentially in place now that unprivileged namespaces are well-established?
They've for sure had more than their fair share of security issues, but those are bugs, not fundamental design problems as far as I understand?
This might be a strange take in these times, but I feel like the browser largely solved the "I need to run potentially adversarial application code in a sandbox". For native applications, stick to stuff that's vetted and in well-maintained repositories, or well-known open source projects that you trust. All of this technical work just to be able to run hostile native code ignores that you don't have to, and probably shouldn't want to, run sketchy code on your device. Installing random untrusted software is bad, even with the most advanced security model in the world. At the very least it will probably abuse whatever permissions it has to spy on you to any degree it can (which is a lot, even for web pages) and to send you advertising notifications.
This assumes that the mentioned systems are the only security considerations on a Linux system. Clearly this is not the case so I am unsure why you omit other security-related aspects of Linux here.
Android, being based upon the Linux kernel, has all those and its own app permission system built on top. Linux on its own comes nowhere close to this.
You can build those things on top of Linux, like Android did. Linux has containerization and all.
Not lightyears. About 20 years, which is how long it took Google to pile on the mountain of complexity and inefficiency to accomplish this.
I understand why mobile/tablet OSs are so crappy compared to desktop; in the past these devices had no resources cpu and ram wise and had to heavily watch battery consumption (the latter is still true mostly, but that should be up to the user), but my phone is more powerful than my laptop and yet runs crap with no real usable filesystem and all kinds of other weirdness that's no longer needed.
However, I have 2 Linux phones and Linux on phones is just not there. Massive vendors (Samsung, Huawei, etc) would need to get behind it to make it go anywhere. Also so banking etc apps remain available also on those phones. We can already run android apps on Linux, Windows apps, so it would be a bright future but really it needs injections and support for large phone makers.
I hope the EU/US mess will give it somewhat of a push but I doubt it.
FWIW, Nokia did develop a pretty good Linux phone back in the day (Maemo/Meego) with Nokia N9 (it even received rave reviews from consumer tech sites like engadget), but it did get killed off as they got absorbed into Microsoft (we all know that didn't age well).
Similarly, Palm Pre, and especially HP Pre 3 was a wonderful WebOS incarnation.
Ubuntu Touch did seem like it had a future, but it was a massive sink for Canonical so it was defunded as well.
The user experience was there on all of these: the apps, not so much.
Ubuntu Touch is not dead though, I use it happily on my primary device for 8 years. It's working like a charm. And waydroid allows you to run APKs, even if some bank apps may not work.
I.. don't think it will happen. For several reasons too. It is not that I don't think Android will change substantially, but the following constraints suggest a different trajectory:
- AI boom or bust will affect hardware availability - there is a push on its way to revamp phones into 'what comes next' -- see various versions of the same product that listens to you ( earing, ring, necklace ) - small LLMs allow for minimal hardware requirements for some tasks - anti-institutional sentiment seems to be driving some of the adoption
I think adoption will hinge on whether existing Android apps will just run on it with something like waydroid/anbox or not.
Gaming on Linux took off with Proton. Linux on phones might go the same path.
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 rather, more aligned with their interests rather than anyone else's).
In reality, mostly-good things that align with most of our interests is mostly a fluke of history, not something that was guaranteed to unfold.
Other common examples: capitalism, the internet, html/css, their favorite part of society (but they have ideas of how it could be a little better), some open-source project they actually use daily, etc.
If only there weren't Android, surely your set of ideals would win and nobody else's.
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.
> death of Android
death of personal computing freedom, sovereign compute, and probably soon our ability to meaningfully contribute to the field as ICs?
A lot of really bad things are happening to our field, and Google is one of the agents responsible for much of it.
> A lot of really bad things are happening to our field, and Google is one of the agents responsible for much of it.
I mean, breaking news from 2010, but of course never assume things are so bad that they can’t get worse.
>The impact is a direct threat to independent AOSP distributions like Murena's e/OS/ (which I'm personally using). If installing a basic APK eventually requires a Google-verified developer ID, maintaining a truly de-Googled mobile OS becomes nearly impossible.
I have trouble understanding why this is a threat to AOSP distribution. I would have said quite the opposite actually, I don't see why they would not remove the verification and that's an incentive for people to use their project instead of Google Android.
I like it, because more and more people see Google as what it is: a ruthless, selfish and extremely greedy mega-mega-corporation. The less we depend on it the better.
Who could Android be possibly recommended to at this point?
I know iPhones aren't affordable for the layman in many countries. But for anyone with an option, why would you buy an Android? All the "customization" things I cared about when I was on Android are either doable on an iPhone now with better implementation, or something I don't care about.
I was a die-hard until I went through enough cycles of Google deprecating and reinventing their apps and services every year, breaking my workflow/habits, that I got sick of them and moved to Apple everything. And all the changes I've seen since then are only making me happier I got out of the ecosystem when I did. Unlimited Google Photos backups with Pixels are gone, Google Play Music is gone, the free development/distribution environment is gone, etc.
If people can't even develop for the thing without going through the Google process, they're really just a shitty iOS knockoff.
But this thread is about the option to install apps on your device regardless of OS vendor approval, and that's not possible either with iOS nor is iOS open source. And that's what this is all about. If you don't care about open-source and user freedom, then this change wouldn't matter to you anyway.
I switched back to Android in large part for KDE Connect. You can get continuity esque features that work with any desktop operating system. I also get to use real Firefox instead of a Safari wrapper. I still use as few Google services as possible, pretty much just Maps.
KDE Connect works just fine on iOS.
It "works" but it is significantly less useful. Notification mirroring doesn't work, you can't read/respond to text messages, it can't reliably run in the background.
These are all due to limitations imposed by Apple.
At this point, I wouldn't recommend Android other than enjoying the much steeper discount with the headset. For me, the only thing that is keeping me on Android is easier access to commas on the keyboard.
I love the Java/Kotlin userspace, even if it is Android Java flavour, and the our way or the highway attitude to C and C++ code, instead of yet another UNIX clone with some kind of X Windows into the phone.
In the past I was also on Windows Phone, again great .NET based userspace, with some limited C++, moving into the future, not legacy OS design.
I can afford iPhones, but won't buy them for private use, as I am not sponsoring Apple tax when I think about how many people on this world hardly can afford a feature phone in first place.
However I also support their Swift/Objective-C userspace, without being yet another UNIX clone.
If the Linux phones are to be yet another OpenMoko with Gtk+, or Qt, I don't see it moving the needle in mainstream adoption.
> But for anyone with an option, why would you buy an Android?
How the heck this is true?!? iOS is just bad.
Its usability is bad, its interface is bad, its apps are just a ton of crap, and it _will_ keep getting worse.
I'm not even talking about its "walled concentration camp" app model.
you're a really vanilla user then.
wake me up when there's an adblocker on an iphone.
There are several that plug into Safari, and Pihole just works. Does Android have ad blockers that do more? It's been a few years since I switched.
I can run proper uBlock Origin in Firefox on Android. Sure something like Pihole works, but I am often on mobile data or other WiFi networks.
Thankfully you don't really need an adblocker for apps on an iPhone. Your browser could use one, but thankfully those do exist :)
That said, I want off the iOS ecosystem, but Google has basically said guess what? We are going the way of Apple, so we don't care about you either.
So right now there isn't really anywhere else to go. I'm going to keep trucking in iOS for now, but I hope I find something better soon.
> Thankfully you don't really need an adblocker for apps on an iPhone. Your browser could use one, but thankfully those do exist :)
uBlock Origin on Firefox Mobile is significantly better than any Safari adblocker I've been able to find. (1Blocker's the best I've found for Safari.)
> Thankfully you don't really need an adblocker for apps on an iPhone.
That's for me to decide, thank you very much.
who is talking about app adblockers. power android users get their apps from fdroid. You relly are out of touch.
And you know very well, There are only meme adblockers for the browser on IOS.
The fundamental problem is that we are relying on the good graces of Google to keep Android open, despite the fact that it often runs run contrary to their goals as a $4T for-profit behemoth. This may have worked in the past, but the "don't be evil" days are very far behind us.
I don't see a real future for Andrioid as an open platform unless the community comes together and does a hard fork. Google can continue to develop their version and go the Apple way (which, funny enough, no one has a problem with). Development of AOSP can be controlled by a software foundation, like tons of other successful projects.
A hard fork doesn't matter when the vast majority of phones have a locked bootloader.
Yeah, that's the biggest issue. And it all originally stemed from phone carriers wanting to lock customers into their services.
We need some pro-consumer regulations on hardware which mandate open platforms. Fat chance of that happening, though, as the likes of both the EU and US want these locked down systems so they put in mandatory backdoors.
The other big issue is the closed source binary only drivers for almost everything.
Google's own phones do not have a locked booloader. You can buy a Pixel and put GrapheneOS on it in like 10 minutes. But basically no one does this, because no matter what people say in online forums they actually value ease of use and shiny features over privacy and software freedom.
That's probably their next target once android is fully locked down
A google tax which google's grace bestows upon us for as long as its whim want.
Even if locked bootloaders weren't a thing, not being able to just buy a phone with an open Android pre-installed means it would get relegated to the Linux Zone, with a whole lot of "security alert" and "device not supported". Also, low popularity leads to fewer development resources, so it would probably suffer from lack of polish.
People will keep using the OS their phone comes with and that would be Google's Android. It's worse than with Windows PCs and Windows to be honest because phones have a locked bootloader.
People give a lot of flack to the EU, but this is the sort of thing they would regulate.
Or the fact that you need device drivers for every piece of hardware in a phone.
A hard fork is not needed. Non-Google Android do not have to enforce this requirement. It's more important to get as many people on alternatives like GrapheneOS as possible. And fund them by donating to them. If every ~0.5 million GrapheneOS users donated 10 Euro per month, they would be very well-funded.
There is no such thing as non-Google Android. At most you have people applying tiny patches on top of AOSP, but 100% of the code in the underlying project is still Google-approved, and none of the alternatives have control over that.
It's the same as the situation with Chrome/Chromium. There are a million "de-Googled"/"privacy focused" alternatives to Chrome all using the same engine, and when Google pushed manifest v3 changes to block ad-blockers every single one of them was affected.
At most you have people applying tiny patches on top of AOSP, but 100% of the code in the underlying project is still Google-approved, and none of the alternatives have control over that.
You are making an orthogonal point. Yes, Google maintains AOSP. No, that does not mean that AOSP OSes that are not in Google's Android program (calling it that to avoid semantics games) have to adopt this change. If you want to hear it from the experts: https://grapheneos.social/@GrapheneOS/116103732687045013
Unless these different Android flavors all have the resources to indefinitely rewrite AOSP and remove all Google code they don't agree with - no, they pretty much have to adopt the changes (see the earlier Chromium example). And if they do somehow manage this after a point all the patching basically becomes a fork, which is exactly what I started the conversation with.
I see your point, but it all hinges on when you consider the changes to be a patch set and when a fork. I don't think there is a very clear definition, except I don't think most of these projects would call themselves AOSP forks.
At any rate, this particular Google anti-feature does not require a large patch (or maybe none at all).
> and when Google pushed manifest v3 changes to block ad-blockers every single one of them was affected.
That's just objectively wrong, both Brave and Opera still support manifest v2 and are committed to continue doing so for the foreseeable future. Even Edge apparently still has it, funnily enough.
Nope, actually "both Brave and Opera still support manifest v2" is objectively wrong.
Brave does NOT support manifest v2. They have instead hand picked exactly 4 manifest v2 extensions (AdGuard, NoScript, uBlock Origin, and uMatrix) and have hard-coded special support for them. They quite literally say in https://brave.com/blog/brave-shields-manifest-v3/ that all other v2 extensions will go away from Brave once Google fully removes support for them (which may have happened already, since it was posted a while ago).
As for Opera (https://blogs.opera.com/news/2025/09/mv2-extensions-opera/):
> MV3 extensions are the new standard and will offer a more stable and secure experience. Opera itself will shift to an MV3-only extension store.
> They have instead hand picked exactly 4 manifest v2 extensions (AdGuard, NoScript, uBlock Origin, and uMatrix) and have hard-coded special support for them. They quite literally say in https://brave.com/blog/brave-shields-manifest-v3/
You're misreading that page, they have special cased the hosting of those 4 extensions, because they do not have their own addon web store and are relying on Chrome's instead. You can still install any manifest v2 addon manually, not that there are going to be many outside of those 4 that care about v2.
As for Opera:
"Today, we reiterate what we said back in October 2024: MV2 extensions are still available to use on Opera, and we are actively working to keep it that way for as long as it’s technically reasonable."
> for as long as it’s technically reasonable
Read: for as long as Chromium allows this via a flag.
which begs the question, why ublock origin is not native on all browser yet?
addons for firefox were at first a way to test features. we only have devtookls because one person wrote an addon copying ie6 dev tool. next Firefox release it was part of the core browser.
Get a large phone vendor to get a flagship phone with Graphene or so on the market. Otherwise nothing will happen. Even starting with the smaller ones like Blackview would do something. But almost no one will do that because users are said to want android; like my parents care... But they will care of course when their banking app stops working... That is the real issue imho.
Google's moat with Android is the same as it's moat with Chrome: complexity. There are very few entities that could fork Android.
What about the Android SDK? I don't think that this is open source, is it? As a developer, when you download an Android SDK you have accept a licence that is not open source, right?
The answer has to come from anti trust legislation. Android is too big for Google to control.
Who else is going to maintain and develop it? It's the same issue as with Chrome, even if you force Google to give it to some other company, they're all just as bad. And it's too big and too costly to maintain for anyone else but tech giants.
The only other options would be convincing users to pay 5 bucks a month for their software, or have some Government fork over the tens of millions required to pay open source developers. And good luck with that.
I'm thinking with ever increasing seriousness: let's split any company that grows past a certain size. Each side gets a copy of the codebase and half the assets, no one who's been on the board on one side can be on the other side's board, and neither side can buy off the other. They can use the existing branding for a limited time and with a qualifier (say Google Turnip vs Google Potato) but after that it's on the strength of the new brand which they're each building and for which they're competing against each other and the rest of the market.
This is not happening in my lifetime, of course it isn't. But by god does it need to happen.
Right? We need a "You won capitalism!" award where everybody in the org gets a huge bonus and then the company is split into small pieces and then they start over. On top of it we do what you describe and enforce the split so they can't collude.
I welcome feature stagnation on mobile!
Every single release is a step backwards.
Android 15 cannot hold a candle to what cynogenmod did on top of android 2.3. And that's objective.
> And that's objective.
I don't think you understand what that word means.
Regardless, your opinion (and mine) is irrelevant. People want at least some of the features of modern android, and any alternative lacking those is not going to be adopted by most people. Just look at how many people try GrapheneOS and find the minor things to be dealbreakers for them.
And as long as that's the case you can't expect people to vote for a scenario where they'll end up with a, in their eyes, worse product.
Historical meaning is pretty worthless though. It's like saying CPU's are going backwards because the 386 was a bigger jump. Technology matures eventually and that's not a bad thing.
Android doesn't really work on hardware changes as AOSP doesn't run on a single phone on earth anyways, not even the emulators, this is the goal of the manufacturers.
For the features you can read here for example what Android 16 changed:
https://www.android.com/articles/android-16-features/
Under what law is that a legal or ethical thing to do? Why not suggest ios be taken away from Apple as well and windows from Microsoft?
Can you be more specific on exactly what "that" you are thinking of which would be illegal or unethical?
Parent-poster just referenced past/future legislation in general.
I'd be fine with that too
What is stopping a hard fork?
The same reason nobody is doing a hard fork of Chromium.
The gigantic task of maintaining and developing a mobile OS that needs to retain compatibility with AOSP/GPS anyway to tap into the huge amount of applications that are available?
It will cost a lot of money and as long as Google is still doing regular AOSP code drops, what's the point?
I contacted the EU DMA team about my concerns and got a real reply within 24 hours. Not just an automated message, it looked like a real human read my message and wrote a reply. I'd urge other EU citizens to do the same.
Great idea, I just did the same. I encourage other EU citizens to do the same. Keeping at least one of the two major mobile ecosystems open is important.
(And install GrapheneOS, the more successful open Android becomes, the better.)
GrapheneOS is great. But that currently means you have to buy a phone from Google to work around Google looking down Android.
True. I'm really happy that they are working with an OEM to bring an alternative in 2027. Until then:
- A refurbished Pixel works (except some weird Verizon locking that I heard about the other day).
- Pixels get really heavily discounted near the end of the cycle (e.g. 9a currently). Google probably doesn't make much on it if you are opting out of your ecosystem.
When I do this for family I buy a used pixel. Then no dollar goes directly back to Google.
They say they will announce a partnership with a major OEM manufacturer in March 2026!
For posterity, what was their sentiment?
Wow, someone replied to an email. From the same organization that is pushing for chat control. That would give you hope... European tax payers have this funny belief that their bureaucratic overlords are all there in Brussels acting with the taxpayer's interest and privacy in mind. One can dream, I suppose...
EU did bring regulations that helped consumers. I have a feeling that criticism of EU regulations mostly come from people who are not in the EU.
Maybe daddy won't beat me this time?
I am genuinely curious, what is your moral justification to attempt to use party A to forcefully influence how party B develops/sells *their* intellectual property? Party B owes you nothing. You are free to not use their products or start a company to compete. How do you justify it, and how would you feel if you were on the receiving end of such a dictum?
Well, Google has marketed Android as an open source operating system (AOSP) and openness about the system [1] and encouraged manufacturers and developers to build on it based on the premise of openness and of course being "free". People advocated for Android because it was open source compared to other alternatives. But with this change they are simply ending that openness. People that have developed F-Droid and other alternative stores have contributed to the platform value (such as not being able to de-google their phone), the same goes for many other developers who have spent countless of hours developing for Android.
To say they don't owe you nothing seems like a betrayal on the promise that Android was an open platform (and open source).
> You are free to not use their products or start a company to compete
That's not an option as you are making it out to be. For a user switching means buying a new phone, repurchasing apps (if you bought) and maybe apps won't be even available to the new system, for developers that means all their knowledge about the system gone. Building a mobile operating system requires millions if not billions of dollars, years of work and convincing developers and businesses (hardware makers) to use your operating system. The barrier to enter is so high that telling people to just compete with Google is not a realistic solution.
[1] https://blog.google/company-news/inside-google/around-the-gl...
Maybe "intelectual property" is really imaginary property given how the same big companies just gobble data from other people and companies wothout permission to feed their AI models (Facebook with books, recently NVIDIA with milions of videos from Youtube).
I guess they would not due that if they really believed some questionable synthetic construct like "intelectual property" really existed ?
Party A does not owe Party B the right to sell in Party A:s legal area.
Party B is allowed to choose not to sell in EU. If you wanna sell in EU you have to comply with EU rules. If you wanna sell in US you have to comply with US laws. That simple.
That is not how the European Union works. One of the core goals of the EU is to guarantee the European single market. One of the core principles of the single market is the Freedom to establish and provide services [1]. The Apple/Google duopoly have effectively created a market within the single market where the core principles of the single market do not apply anymore.
Tech has a strong tendency to favor outcomes with only a handful large players that make competition impossible due to network effects, etc., distorting the market. The Digital Markets Act was made to address this problem.
IANAL, but Google's Android changes seem like a fairly clear violation of the DMA.
This is typically hard for people from the US to grasp (I saw that you are not originally from the US though). In Europe, capitalism is not the end goal, the goal of capitalism is to serve the people and if that fails, it needs to be regulated.
---
As an aside, the lengths people go to defend a company with $402.836B yearly revenue :).
[1] https://en.wikipedia.org/wiki/European_single_market#Four_fr...
Yes. I am effectively asking you what the moral justification for DMA is. I understand that lawmakers can make whatever law they want. I understand they made it. I am curious how people who agree this should be possible think of this from a moral angle, especially as engineers who make their living by creating intellectual property and probably wouldn’t want to see control of it seized randomly
I'd ask the inverse of the question: morally, should a single gatekeeper have the right to deny two consenting parties the ability for one to run the other's software?
Especially when that ability has been established practice and depended upon for decades? And the gate-kept device in question is many users' primary gateway to the modern world?
There's nuance here, of course - I'm not morally obliged to help you run Doom on your Tamagotchi just because you want to do so. But many people around the world rely on an Android device as their only personal computing device (and this is arguably more true for Android than it is for iOS). And to install myself as an arbiter of what code they can and cannot run, with full knowledge that I could at any time be required to leverage that capability at the behest of a government those worldwide users never agreed to be dependent on? That would be a morally fraught system for me to create.
The moral justification is that I am a citizen, and can demand the laws I want. When enough people think like me, we can actually make it a law. By holding the smartphone OS oligopoly these companies hold a lot of power on the people. I do not like that. Hence I like laws that try to change that.
> especially as engineers who make their living by creating intellectual property and probably wouldn’t want to see control of it seized randomly
If these people try to use their intellectual property to control my device and hence my ability to do things, I want to have a say what they do. Yes, that is what software is: directions to machines. I own the machine, hence I want a say what it does. You are free to keep your intellectual property for yourself, if you want to.
At some point free markets become fiction. There's no financially viable way to start competing businesses in markets as entrenched as mobile OSes. Otherwise this would have happened. And if that becomes anti consumers, then the consumers start changing the rules the companies operate under. Because in a democracy we have more consumers than CEOs,so they vote with majority.
(This obviously simplifies things, but ultimately we as humans still haven't found the one and only true philosophy or moral, and maybe that's not possible (I'm no philosopher))
There are no absolute morals. But I think in general healthy societies are arranged around the ideas that people should have: the basics of living (housing, food, vacation, and some luxory), agency, and equal opportunities.
It should be clear that having a small number of companies murder all competition and personal freedoms (like doing what you want to do with something you own like a phone) are in contrast to these basic values.
---
Or the alternative, more blunt answer: it does not require a moral justification. EU citizens directly elected the EP, the EP ratified the DMA. So Google can either comply or leave the EU as a market (which they wont do because it's too large and others would be happy to take it).
They are 100% free to not sell to European customers
The moral argument is that vertically integrated monopolies threaten the rights of consumers, who are human beings. Corporations are legal fictions and their "rights" are another convenient fiction to align incentives. They carry zero moral weight.
Are we still talking about massive companies with power to arbitrarily decide how billions of people use the personal computers they bought? Who's doing the feeling? Why would we presume all of their conduct to be moral?
> Party B owes you nothing. You are free to not use their products or start a company to compete.
When 99% of government/banks/etc require you to use a certain service to access basic services, you need some way of ensuring you don't have to sell your soul to use it. Alternatives would be really great, but Google is part of a duopoly.
Just because you build the rails doesn't mean you get to decide who gets to use the trains.
That is not their fault, though. I can see how you could complain to the people who mandate you use B’s products. Otherwise what you’re saying is that control of any intellectual property can be stolen from its owners simply by becoming popular outside of their control
> That is not their fault, though.
It is though. They are actively working on increasing their marketshare. That doesn't happen by accident. They have chosen to place the interests of the corporation over the interest of their fellow people. They are fine to do that, because we separated that responsibility. Corporations can only chase for profit, because we have governments, that make the rules, so that chasing profits is in the interests of the people.
Maybe you don't like that, and that is fine for you, although I don't like that you don't like that. Maybe you want a society where might makes right. However a lot of people don't feel that way, hence why we outsourced that world model to the government.
People don't like that their neighbor is stronger than them and takes there stuff, so they pay feudal lords. Then the feudal lords want some security, so they outsource that to elected emperors. After a while the feudal lords misuse their power, so parliaments are invented. Eventually people have enough and demand voting rights. The elected leaders betray the people by sending them to war, so they created multinational institutions, that try to prevent this (EU). They haven't used their power to betray the people enough, so we are still fine with them.
"Wealth comes with obligations" is literally in my country's constitution. You, may don't like that, but I do. I think a lot of other people do as well. It is of course always for discussion how much.
It kind of is their fault because of Google Play Integrity APIs. They are effectively developing tools that are designed to make their product mandatory. There wouldn't be a backlash that big if we could just unlock our bootloaders and run a patched version of Android.
> any [] property can be [taken by the state] from its [original] owners simply by [those owners becoming more powerful than the state wants]
When rephrased like the above, I think what you’re describing is pretty common in history. Many industries and assets have been nationalized when it serves the state’s interests.
IMO the moral justification is that there is no ownership or private property except that which is sanctioned by the state (or someone state-like) applying violence in its defense. In this framing, there’s little moral justification for the state letting private actors accrue outsized power that harms consumers/citizens.
Brutal, but understandable and well-argued. Thank you.
People outsource the brutality (to the government), so that they don't need to deal with it in their daily life. If we couldn't force companies to act in ways we want through a formal system, then the world would look much more brutal.
or alternatively we can just stop using products/services of said companies
I can ban persons from doing things, I rather not have them do. Companies are legal persons, so why shouldn't this apply to them? At some point ignoring behaviour is not making it go away, it needs to be actively worked against, otherwise it will become (practically) mandatory.
the core problem with banning is who is doing it and why, right? once we allow it, it goes into the hands of the “politicians” and then books get banned today, ice scream gets banned tomorrow, math gets banned the next day…
Which is why the more serious consequences a law has the harder it is to change it and the more people need to sign off on it. There is stuff that needs simple majorities, stuff that is in the constitution and requires a super majority, stuff that can't be changed short of abolishing the current state and stuff that can't be changed at all, because it is just an assertion that is independently on anyone asserting it.
This is kind of a "solved*" thing in theory, not so much in practice of course.
*solved meaning we have a proper process established
My moral justification is that my right to do with the physical property I have in my physical hand is more important than any noncorporeal corporation's right to do anything with their noncorporeal intellectual property.
The truth is, I gave party C money for a product. Party B does not get to say anything about what party C gave me. And they absolutely do owe me something, and that is the use of the product they gave me for my money. Whatever their terms of service say about licensing versus owning should not trump the fact that I made a one-time purchase and I have physical ownership that they cannot revoke. This is not a car lease where I have a contract with the dealership and they can reposses the car if I don't make the payments.
And you can use it. You can, in fact, keep using the software that shipped on it. What you want is access to further intellectual property they develop (updates, features), that just so happens to be able to run on your hardware and ability to shepherd it in a direction you want and they don’t.
> And you can use it.
Tell that to the locked bootloader.
> What you want is access to further intellectual property they develop (updates, features), that just so happens to be able to run on your hardware and ability to shepherd it in a direction you want and they don’t.
Well yeah, I am paying them with money (and data) and thereby with power and expect them in turn to provide directions for my device, so that is does what I want. That's kind of the deal. If they don't want to provide that, then they can just not accept my money (and data). They can of course produce devices, that to what they want, and want me to carry them around, but then they better pay me.
If they use the power I gave them against me, then I will demand my power projection as a service provider (aka. the government) to project power in my interest.
> that just so happens to be able to run on your hardware
the hardware is specifically locked down with "trusted computing" features to facilitate this. It's not a random coincidence. The problem here lies in the network effects and the use of trusted computing. If my bank app mandates that I use "real deal 100% certified android", then I can't just develop my own OS. So it's an antitrust situation.
If every company in the world teamed up with MegaCorp and made their services contingent on wearing a MegaCorp shock collar powered by trusted computing, would you wear it? You are free to not use the collar... and starve to death in the woods I suppose.
I don't usually even care about intellectual property. It's a hack to grant a temporarily exclusive monopoly as a way to incentivize R&D. The R&D in this case is just solving the question of "how do we establish a larger monopoly". So why should the public be forced to uphold it?
Asking me if I am willing to violate intellectual property in this situation is like if I was being lowered into a pit of liquid hot magma and in order to get out I had to break the flag code or jaywalk or something.
Party B has access to the market of Party A at Party A's mercy.
Google is engaging in immoral business practices. Since they are immoral, it is morally justified to say they must be stopped.
> how would you feel if you were on the receiving end of such a dictum?
I continue to be astounded how people still just flat out assume that everyone must be a capitalist.
If I were on the receiving end of a dictum aimed at stopping immoral behavior, I would cease my immoral behavior. But I'm not going to be on the receiving end in the first place because I don't aim to do immoral things in the first place.
Party A enforces Party B's intellectual "property"
The moral justification is the same anyone else employs. I have a tool to create an outcome and I'm going to use that tool to produce that outcome. It's that simple.
Just to put out what Google actually said in their blog post [0]:
> We appreciate the community's engagement and have heard the early feedback – specifically from students and hobbyists who need an accessible path to learn, and from power users who are more comfortable with security risks. We are making changes to address the needs of both groups.
> We heard from developers who were concerned about the barrier to entry when building apps intended only for a small group, like family or friends. We are using your input to shape a dedicated account type for students and hobbyists. This will allow you to distribute your creations to a limited number of devices without going through the full verification requirements.
> Based on this feedback and our ongoing conversations with the community, we are building a new advanced flow that allows experienced users to accept the risks of installing software that isn't verified. We are designing this flow specifically to resist coercion, ensuring that users aren't tricked into bypassing these safety checks while under pressure from a scammer. It will also include clear warnings to ensure users fully understand the risks involved, but ultimately, it puts the choice in their hands. We are gathering early feedback on the design of this feature now and will share more details in the coming months.
It is also true that they have not updated their developer documentation site and still assert that developer verification will be "required" in September 2026 [1]. Which might be true by some nonsensical definition of "required" if installing unverified apps requires an "advanced flow", but let's not give too much benefit of the doubt here.
0: https://android-developers.googleblog.com/2025/11/android-de...
1: https://developer.android.com/developer-verification
> We heard from developers who were concerned about the barrier to entry when building apps intended only for a small group, like family or friends. We are using your input to shape a dedicated account type for students and hobbyists. This will allow you to distribute your creations to a limited number of devices without going through the full verification requirements.
In classic Google fashion, they hear the complaint, pretend that it's about something else, and give a half baked solution to that different problem that was not the actual issue. Any solution that disadvantages F-Droid compared to the less trustworthy Google Play is a problem.
Even restricting the mitigation to "students and hobbyists" is bad.
I should have the right to have parents, friends or anyone use a "free" store that is not under control of Google if the user and app developer wish so. But also, somehow there should be something done to avoid the monopoly forcing to use the Google services. Like major institutions like bank, gov and co being forced to provide alternatives like a webapp when they provide app tied to the Google play store.
I think you've omitted the next section, which seems more relevant. It seems like they will still allow installs, just hide it behind some scare text. Seems reasonable?
> It seems like they will still allow installs, just hide it behind some scare text.
This was already the case for enabling sideloading at system level: it warned you. Nobody really says having this toggle is a bad thing, basically the user shouldn't get an ad network installing apk's just browsing around the web without their informed consent (and android has been found to be vulnerable to popunder style confirmations in the past).
They also already had the PlayProtect scanning thing that scans sideloaded APK's for known malware and removes it. People already found this problematic since what's to stop them pulling off apps they just don't like, and no idea what if any telemetry it sends back about what you have installed. There have been a handful of cases where it proved beneficial pulling off botnet stuff.
Finally, they also have an additional permission per-application that needs to be enabled to install APK's. This stops a sketchy app from installing an APK again without user consent to install APK's.
The question is: How many other hurdles are going to be put in place? Are you going to have to do a KYC with Google and ping them for every single thing you want to install? Do you see how this gets to be a problem?
No, because it isn't something that should be up to google's control.
Why not? It's their operating system, and they're trying to balance quite a few competing priorities. Scammers are not a threat to dismiss out of hand (i've had family who were victims).
For it to be truly considered open source, you should be able to fork it and create your own edits to change the defaults however you wish. Whether that is still a possibility or not, is a completely separate issue from how they proceed with their own fork.
> Why not? It's their operating system
It's my phone.
Of course it's your phone, but the whole point of using Android is that it makes a lot of choices for you. It forces a billion things on you, and this is really no different than any of the others. Everything from UI colors, to the way every feature actually works. For instance, should you be able to text message one million people at a time? You might want to, but Android doesn't offer that feature. Do you want to install spyware on your girlfriends phone? Maybe that's your idea of complete freedom, but the fact that Google makes it harder, is a good thing, not a bad thing.
If you don't like their choices, you should be able to install other software you do like. There should be completely free options that people can choose if they desire. But the majority of people just want a working phone, that someone like Google is taking great pains to make work safely and reliably.
> Of course it's your phone, but the whole point of using Android is that it makes a lot of choices for you. It forces a billion things on you, and this is really no different than any of the others. Everything from UI colors, to the way every feature actually works.
There is a difference between making a choice because there has to be something there (setting a default wallpaper, installing a default phone/sms app so your phone works as a phone) and actively choosing to act against the user (restricting what I can install on my own device, including via dark patterns, or telling me that I'm not allowed to grant apps additional permissions).
> For instance, should you be able to text message one million people at a time? You might want to, but Android doesn't offer that feature.
There's a difference between not implementing something, and actively blocking it. While we're at it, making it harder to programmatically send SMS is another regression that I dislike.
> Do you want to install spyware on your girlfriends phone? Maybe that's your idea of complete freedom, but the fact that Google makes it harder, is a good thing, not a bad thing.
Obviously someone else installing things on your phone is bad; you can't object to the owner controlling a device by talking about other people controlling it.
> If you don't like their choices, you should be able to install other software you do like. There should be completely free options that people can choose if they desire. But the majority of people just want a working phone, that someone like Google is taking great pains to make work safely and reliably.
Okay, then we agree, right? I should be able to install other software I like - eg. F-Droid - without Google getting in my way? No artificial hurdles, no dark patterns, no difficulty that they wouldn't impose on Google Play? After all, F-Droid has less malware, so in the name of safety the thing they should be putting warning labels on is the Google Play.
The problem is that step by step ownership of your device is taken away. First most phones stopped supporting unlocking/relocking (thank Google for keeping the Pixel open), now the backtracked version of this, next the full version, etc.
Yes, that is a real problem. But it doesn't justify arguing uncritically or unrealistically in other areas. I think people should be free to do anything they want with their own devices. They should be able to install any software they want. That's very different than demanding someone make their software exactly how you desire. ie. You should be able to install your own operating system, you don't get to tell them how theirs should operate.
There are legitimate concerns being addressed by these feature restrictions.
> You should be able to install your own operating system
So you draw the line between the bootloader and the OS. Other people draw the line between the OS and applications. Most (nearly all) people can't write either, so for them it is just part of the device.
> you don't get to tell them how theirs should operate.
I paid for it, and I allow it to be legal in the jurisdiction I (partly) control. So it is not only theirs anymore.
> demanding someone make their software exactly how you desire
IMO the way this should work is that Google can make their software however they want provided they don't do anything to stop me from changing it to work the way I want.
Unfortunately, they've already done a lot of things to stop me from changing it to work the way I want. SafetyNet, locked bootloaders, closed-source system apps, and now they're (maybe) trying to layer "you can't install apps we don't approve of" on top of that.
> IMO the way this should work is that Google can make their software however they want provided they don't do anything to stop me from changing it to work the way I want.
That's exactly how it is. You're free to get your soldering iron out, or your debugger and reverse engineer anything you want. I don't mean to argue unfairly, but all we're talking about here is the relative ease with which you can do what you want to do. How easy do they have to make it?
As for their software, as delivered, there are literally an infinite number of ways that it stops you from changing it. Maybe you want everything in Pig Latin, or a language you made up yourself. Do they have to design around this desire? Do they have to make this easy to do?
> They should be able to install any software they want. That's very different than demanding someone make their software exactly how you desire. ie. You should be able to install your own operating system, you don't get to tell them how theirs should operate.
I don't think the distinction exists the way you're trying to describe. If I should be allowed to install any software I want, surely that includes any .apk I want? Conversely, someone could make the exact claim one step down the chain and argue that you don't get to tell them how their firmware should work and if you want to install your own OS you should just go buy a fab, make your own chips, write your own firmware, and make your own phone. And that's absurd, because users should be allowed to run their own software without being forced to ditch the rest of the stack for no reason.
No, I don't think you have the inerhent right to install any apk you desire, if their OS is designed to prohibit it. You should be free to try to alter their OS any way you want, but they should not have to make it easy.
And the argument is the same lower down the stack. You shouldn't be able to tell someone how to design their firmware.
The only problem is where the law prohibits us from trying to undo these restrictions, or make modifications ourselves. It's government that restricts us, and we should focus our efforts there.
> No, I don't think you have the inerhent right to install any apk you desire, if their OS is designed to prohibit it. You should be free to try to alter their OS any way you want, but they should not have to make it easy.
> And the argument is the same lower down the stack. You shouldn't be able to tell someone how to design their firmware.
Earlier, you claimed,
> They should be able to install any software they want.
but it sounds like actually you only mean that users should be allowed to futilely attempt it, not that there should actually be allowed to run software at will. If the firmware only allows running a signed OS, and that OS only allows running approved apps, then the user is not able to install any software they want.
The whole point of using Android for most users is that they have no other choice if they need a mobile phone.
Google killed every other competition via dumping and shady business practices. Sure, you can go to iOS, but that is even more closed and restrictive, not to mention the devices are overpriced.
100%. If I buy something, it's mine. I should be able to resell it, modify it, or generally work on it however I see fit. Licensed digital media bound to platforms is different (barring some kind of NFT solution?) but an OS that my phone cannot function without (and that cannot be replaced in many cases) absolutely must be under my jurisdiction.
What makes it “yours”?
You paid for it but Google still has the control. I understand that you prefers things to be different (as do I) but the reality is that we don’t have control over devices we paid for.
You might choose to not have control. The reason people protest is because we should have more control over the things we own. Sure this might create a better market for alternatives but it is worse for most people. F-droid is spectacular.
> What makes it “yours”?
The law. The contract. The money I paid.
> the reality is that we don’t have control over devices we paid for
So, the reality is that a company is exerting ownership rights on things they don't own. If that is exclusive, then that is called theft.
> What makes it “yours”?
You answered the question here:
> You paid for it
If you paid for hardware, legally that makes it yours.
> Google still has the control
Therein lies the problem. Google should not exercise such control over devices which are yours, not theirs.
Microsoft got penalized for way less.
Why is it reasonable that installing software is behind an "advanced flow" what ever that means? I find it not very reasonable at all that the only way to install software on my phone is by jumping through hoops. I don't think it reasonable that the Play Store is the only portal. I don't even find it reasonable to call installing software "sideloading". Downloading and installing software from a vendor's page has been the norm for decades before smart phones came along but all of a sudden when it is on a small screen the user can not be trusted? That's ridiculous and not at all reasonable.
It's not the screen size, it's the demographic shift. By 2000, only half of U.S. households had a shared living room PC, mostly for work and/or games. Everybody having a phone in their pocket later was a change that we did very much have to account for. Non-technical people can be scammed very easily into life-ruining mistakes with a little social engineering and a little bit of access to powerful tools already on their devices.
I remember when big sites started having to put big banners in your browser console warning you that if you weren't a dev and someone told you to paste something there, you had been scammed, and not to do it. They had to do that because the average Facebook user could be tricked very easily by promises of free FarmVille items or the opportunity to hack someone else's account, and those are fairly low stakes bait. Now people bank with real money on their phones.
The whole point of TFA, if you read it, is that they SAID they would do that, but there has since been ZERO evidence that they actually will. This feature is not present in anything they have released since that statement.
On the other hand, blocking installation of non-notarized apps is not present in anything they released since that statement either, as far as I know.
It would be foolish to depend on that & far harder to get ridd of it if they put it in place. There needs to be clear statement and verification method to make sure they really are backtracking.
Anything else won't do.
> It seems like they will still allow installs, just hide it behind some scare text.
That describes the current (and long-established) behavior. App installation is only from Google's store by default and the user has to manually enable each additional source on a screen with scare text.
> We are designing this flow specifically to resist coercion, ensuring that users aren't tricked into bypassing these safety checks while under pressure from a scammer. It will also include clear warnings to ensure users fully understand the risks involved, but ultimately, it puts the choice in their hands.
I've lived through them locking down a11y settings "to resist coercion, ensuring that users aren't tricked into bypassing these safety checks while under pressure from a scammer", and it's a nightmare. It's not just some scare text, it's a convoluted process that explicitly prevents you from just opening the settings and allowing access. I'm not giving them the benefit of the doubt; after they actually show what their supposed solution is we can discuss it, but precedent is against them.
> Seems reasonable?
No. As I said before, any solution that disadvantages F-Droid compared to the less trustworthy Google Play is a problem.
It's deliberately written to be vague and not say anything, and given the original intention, it's hard to believe that means it should be interpreted generously.
> shape a dedicated account type for students and hobbyists.
Even that is a step too far in the wrong direction. Doesn't matter if it's free, or whatever, simply requiring an account at all to create and run software on your own device (or make it available to others) is wrong.
There exists no freedom when you are required to verify your identity, or even just provide any personal information whatsoever, to a company to run software on your device that you own.
So basically the Apple model but worse.
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!
There's a lot of misinformation here.
> I guess it means the Play store will be the only way to install an app
No, non-Play stores will still work, but developers will need to register a developer account with Google that is tied to some real identity. They already need to do this to distribute through the Play store, but now it'll apply regardless.
This is to make it harder for scam apps to churn app signatures. Kind of like requiring code-signing, but with only one CA.
> That users won't be able to install what they want
No, sideloading will still work, but it won't work if the APK isn't signed by someone in the Google developer registry.
> and that they would need a google account to install apps
Nope.
> That app developers have to go through google to distribute their apps, with identity verification etc.
They don't need to distribute through Google, but they will need to be involved with Google and do identity verification.
> 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?
You're being misinformed. They won't even need to strip the verification. The verification is only for certified Android -- OEMs that partner with Google. Custom ROMs and the OEMs that aren't certified (Amazon, some Chinese manufacturers) won't have verification.
The target audience for verification and who would ever use a custom ROM has basically zero overlap.
90% of apps are just websites with a wrapper UI.
This isnt going to be a popular post because the HN crowd is very much a "China bad" crowd but I hypothesize China will likely step in and offer a fork that's compatible with open ecosystems not under the direct control of the us state department. This might be in the form of commits and investment in fdroid and pinephone, or a tiktok like alternative to the wests walled garden.
Edit: this will likely exist "uncensored" in other markets but conform to the PRCs standards and practices domestically, similarly to how tiktok operated prior to selling a version specifically taylored to US censorship and propaganda.
Not a chance. A fork that is under China's control, maybe, but not an "open" fork. They don't even pretend to have that as a value.
You may theoretically find it advantageous to use such a system anyhow. To a first-order approximation, the danger a government poses to you is proportional to its proximity to you. (In the interests of fairness, I will point out, so are the benefits a government may offer to you. In this case it just happens to be the dangers we are discussing.) Using the stack of a government based many thousands of miles/kilometers away from you may solve a problem for you, if you judge they are much less likely to use it against you than your local government.
But China certainly won't put out an "open" anything.
Not sure if you have been following the LLM space or even the emulator handhelds space, but Chinese companies have been doing great with putting out open source software lately.
Or the TikTok space - TikTok got worse privacy/data collection wise after the US government intervention/acquisition.
https://arena.ai/leaderboard/text?license=open-source
The irony is that software coming from China is a lot more open than western software. Biggest examples are huggingface models mostly coming from Chinese institutions. Its also strategicaly wise for China to go this path.
Maybe a shift to Huaweis HarmonyOS with its android compatibility layer or SailfishOS if they play their cards right.
As far as HarmonyOS i dont see many uptakes outside strict US free requirements as the other OEMs are lazy and also dont want to be locked into a competitor.
SailfishOS looks like its your time to faceplant once more , by not having a proper stratergy on monetizing on the many missteps from the current monopoly.I thonk at this point they need a leadership/biz stratergy overhaul - the tech is nice and polished, user demand is off the charts for an alternative . And they are just .. missing. Not even in th e conversation.
As of version 5, HarmonyOS doesn't have the Android compatibility layer. There are emulators that allow APKs to run, but they're a bit clunky.
Ah if they can get the emulators to the level that Rosetta worked on OSX would be acceptable for hardto port apps.
> China will likely step in and offer a fork that's compatible with open ecosystems not under the direct control of the us state department.
Where you been? They already had Huawei get kickbanned by Google and made their own OS (it's not more open): https://en.wikipedia.org/wiki/HarmonyOS
Pinephone is tragic, bought a bunch of Pine64's devices (PP, PPP, PB, PBuds, arm tablet, eInk tablet) but old tech, missing drivers, can't blame em no money no drivers... Still the community on Discord is great/helpful people.
As far as I know, China forbids open bootloaders on its territory so it's not where you'll see any open ecosystem.
Not Google controlled for sure but also not open.
I don’t think China will do that at all. They’ll move to HarmonyOS.
That'd be great but I'm not feeling like the Chinese market is too worried about open development. I got a Huawei Watch 5 as a gift and I liked it enough to try to develop my own apps (their app store is a wasteland) but to my surprise Harmony OS is not Android compatible (just Android based somehow). The watch's developer mode is useless. Trying to register a developer account is almost impossible and it seems they only allow chinese nationals and there's no plan to open registration. I couldn't even download their custom IDE (something like Android Studio) without an account.
Maybe it's just my experience.
Competition needs to come from somewhere due to lack of antitrust enforcement in the US. If not China then hopefully elsewhere.
The US system is dying from lack of competition.
I would rather put my phone in the microwave than run Chinese Communist Party OS.
Half, or more, of the world thinks exactly the same in regards to the US
If 50% of the world started running the CCP backed fork and 50% of the world ran the US backed fork, which one would you choose for your phone?
Whatever one that lets me install what I want
Chinese, they won't rat me out to three letter agencies when I say social media CTOs should be public ally executed
If there were truly no other choice, CCP without a doubt. At least they claim to have good intentions, whether that's true or not
The Chinese one, obviously.
Chinese of course. Never used it. Can't wait to test out something different.
Meanwhile the NSA and Mossad can see you fapping on your phone and scan your face in real time and you're implicitly fine with it
This is what lack of options does to a MF
Yeah, I’m amazed at how far the western surveillance apparatus has been able to coast on plausible deniability. Folks, please don’t stick your head in the sand domestically just because there’s an even more obvious or egregious example abroad.
Say it with me: “Living in a police state is bad no matter who’s running it”.
This made me laugh cause of how true it is.
I'm just imagining the poor intern at the NSA having to sit in a dimly lit room with an array of 64 x 64 monitors mounted on a wall, watching the O-faces of thousands and thousands of fat, balding, middle age men for hours straight.
Nah, that can't be true. Just imagine the traffic peak the first day after NNN if they're streaming from your phone in real time.
The judge told Google that Apple is not anti-competitive because Apple has no competitors on it's platform (this all stemming from the Epic lawsuits).
Google listened.
Blame the judge for one of the worst legal calls in recent history. Google is a monopoly and Apple is not. Simple fix for Google...
The link is to the f-droid blog. The official "Keep Android Open" site is at https://keepandroidopen.org/, and contains good information on how you can contribute by contacting regulators.
We ("you") have no power to keep android open. Unfortunately it is in the hands of a company that is building it for profit, in a way or the other.
It's been our choice to drink this glass of wishful thinking while giving that company a solid dominant position in the market.
We ("you") can only make choices that will overturn that trend.
Fully opensource hardware with fully opensource software? Maybe, but also this is wishful thinking.
It's also heavily influenced by businesses. Most employers will happily hand you an Apple or Android phone for work, but I don't think there is a single company out there that would dare to hand normal people an Ubuntu Touch based phone.
We (people who live in a country/confederacy with working antitrust laws) have power to keep large companies from anticompetitive practices such as this one.
If they close things up with no alternative, the free open source software will likely start to catch up. it will take a few years though. This could be a blessing in disguise.
There is just no reasonable way that the open source community can compete with a $3.8T company. And before you say something along the lines of, "But they don't need to compete, they just need to be good enough", that still requires business to put their apps on some open source app store and make them compatible with the open source OS, and there is close to zero incentive for them to do so.
https://en.wikipedia.org/wiki/Linux
MSFT Market cap: 2.951T AAPL Market cap: 3.883T
You've made my point. How many people use Linux as their primary desktop or mobile OS? And that's arguably the world's largest open source project.
Enough. Linux has finally caught on. I literally never use windows or mac and life has been fine.
Somehow, Stallman returned.
it's becoming ever more clear to me that i'll have at least two devices: one running software i trust, one running software corporates trust, with a very narrow pipeline connecting the two, if it all. my demon-haunted device can stay offline in my bag and get hotspot'd in to my trustworthy device as necessary.
not happy about it, but i don't see a path forward that lets one participate in the wider ecosystem and maintain their own sovereignty and sanity.
I would caution the decision makers on this. The line between a secure device and a useless toy is perforated and hard to see.
If I can't use banking or my NFC wallets on my phone, it has become 90% useless. The other 10% of usefulness is texting and calls, which every other phone can do.
Unfortunately, this mostly means using the closed android ecosystem.
I run Graphene on my Pixel and banking apps just work. There is no Google Pay, obviously, since Google dependencies have been stripped out from the system. I just carry a credit card.
Even with the sandboxed Play Store, Google Pay disables NFC payments as it requires hardware attestation against Google's root keys.
No inherent reason all that stuff can't work on an open platform. It works just fine on my Linux box with yubikeys, fido2, and smart cards. Gcloud even let's you authenticate with them only to put a medium lived token in plaintext into a sqlite file on disk.
No inherent reason, just Visa/Mastercard requirements around host card emulation for payment cards.
Sounds like a duopoly that needs to be broken up.
Same, some banks even proactively fix things to work on GrapheneOS when customers ask.
Curve pay works!
90% of your usage on your phone is banking apps or NFC payments? That seems hard to believe.
I don't know if it is generational or regional or what, but there is a solid segment of people that live in very close contact with their bank.
On average, people spend 4 hours and 37 minutes on their phone, per day [1].
I find it hard to believe someone would spend 4 hours and 9 minutes _per day_ looking at their banking app or using NFC payments.
[1] https://explodingtopics.com/blog/smartphone-usage-stats
Your assumption they used their phone an average time was false probably.
That's pretty much my usage pattern too, including some group texting, the occasional call and sometimes taking photos/videos. Otherwise my phone pretty much stays in my pocket or on my table the entire day. What are you using your phone for that makes that so unbelievable?
Web browsing (like right now), photos, e-books, lots of messaging, music, sometimes video.
I use NFC payments often, but I wouldn't say that amounts to more than a few percent of my total usage.
Everyone uses their phones differently, of course. I don't think your use is unbelievable or odd, but I do think your use patterns are not the common case.
I used my bank app yesterday, but since then I've used:
whatsapp, phone, push authenticator, safari (having followed a link from a message), spotify, slack, mail, calandar, disney plus and camera
Do you not do any of that on a mobile device?
No idea why you are even bringing this up. It works just fine right now.
It verifiably does not on open source and free android roms like Graphene. Unsure where you're getting your info.
No one even brought that up. We're discussing being able to install unsigned/self signed APKs. Please stay on topic and take your strawman elsewhere.
The ability to install signed and unsigned APKs directly correlates to the financial institution policy regarding mobile devices and banking apps. Unsure how you've separated these two.
I use GrapheneOS with the Dutch ASN banking app and the ICS credit card app. Pretty much all other major Dutch banks work as well.
https://privsec.dev/posts/android/banking-applications-compa...
Google Pay does not work, but some other NFC payment apps do (e.g. Curve).
[citation needed]
I run GrapheneOS and use several US-based banking apps. I'll not name them since I don't really want my HN account associated with my financials in any way, but I've got a mix of well-known national bank apps and smaller local credit union apps working.
I'll admit there is a single institution's app I've found that doesn't work, but that is just one of several that I use.
For me, the showstopper would be NFC payments. From what I understand, Google Pay doesn't work on Graphene. I have all my credit cards in GPay, as well as a transit card. I use it for boarding passes when I fly, and any other tickets/passes that support it, since it tends to be much more reliable than the airline or ticketer's app. I've come to heavily rely on it, unfortunately.
I haven't tried this, because I try to minimize Google exposure, but I think Google Wallet (minus NFC payments) works on GrapheneOS. So, tickets, boarding passes, etc. should work fine.
>this mostly means using the closed android ecosystem
Maybe, but there's no technical reason for this. As I've mentioned before, I can do banking just fine on my Gentoo machine where the entire corpus of software on it, is FOSS and compiled by myself.
To you.
Laptops exist.
This is a common answer but it does not apply to at least most of Europe. Because of regulations most banks require to install their app either on iOS or Android to act as a 2FA device. One of my banks gave me a hardware device 20 years ago. When its battery dies I'll have to use their app and my fingerprint.
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 are home are still considerably cheaper than Apple and Samsung devices, and give the users far more privacy and freedom.
How do you install the bank app if google does not allow you to install APKs manually / with a 3rd party store? You have to go with Google Play. Which requires a Google account. So I can't do it. That's the whole point of this thread: it would not be possible to use Android without a Google account.
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.
I'm using NewPipe and PipePipe. Both are better than the browser app.
Most European banking apps work fine though on a relocked GrapheneOS phone.
https://privsec.dev/posts/android/banking-applications-compa...
I'm using my GrapheneOS phone to log on to their web app without issues (though I typically only do banking on my phone, much more secure).
When I was still rooting it was possible to bypass this on a rooted device with enough effort. It wasn't unsecure either. Padentic corporate security doesn't really make us more secure. Just more lazy.
Have you talked or met anyone born after the 90s? Everyone banks on their phone, it's the norm not the exception.
Edit: Someone also made a good point, one of my CC's I can barely even manage without the app since the website barely works.
Since smartphone apps are often times required to do banking or identifying yourself now and there's tons of special apps in order to use appliances, and by that I mean really the only way to use modern appliances is by a smartphone app, emulating an Android environment on a laptop or PC with a bluetooth dongle is essential if you want to leave that smartphone era behind you for good, but still be able to function in this society.
The biggest surprise I had in attempting to distribute my first Android app is how difficult it is to get beta-testers through the "standard" channels. It requires a 1 week review and 25 beta-users invited by email addresses
In contrast, Apple has a ~48 hour turnaround for reviews before you can upload to TestFlight and distribute a beta with a link
Not sure if I am in some "trusted developer" cohort on iOS but not Android - but the difference was enough for me to stop trying on Android
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.
Looks like I'm staying in my custom ROM lol
https://archive.is/https://f-droid.org/2026/02/20/ .htmlhttps://archive.is/https://f-droid.org/2026/02/20/twif.html
I question whether an OS that has always been controlled by Google has ever been open.
Sure parts of it were, but Google has always remained in control of Android. Anyone who expected that to change (in favor of more openness) hasn't been paying attention to the actions of tech companies for the past several decades.
The relative openness is the reason I gravitated towards Android and Google. I've never really taken advantage of it, but it's nice knowing it's there and that my phone (a Google Pixel) is something I have more control over than with other vendors.
Amusingly, if Microsfot didn't have a such an awful reputation ( both recent and old ), their newly announced phones could have actually been a viable competitor.
This is where I wish someone like MKBHD and others with big Android followings would speak up and say they will both blast this practice and not review any new Android phones/(Google) apps unless there's a full walk-back of this position.
the frustrating part is that the "advanced flow" alternative Google mentioned still doesn't exist in practice. the media ran with the reassurance headline and most people think the issue was resolved.
https://archive.is/https://f-droid.org/2026/02/20/twif.html
Should device manufacturers be worried about this direction? Could they eventually be locked out too?
What would it take for Linux phones to gain the ability to run Android apps?
EU should fork Android
The number one problem is locked hardware
The Control Society is way lamer than I could have imagined. Deleuze! I demand a refund!
What people forget is that the real monopoly is in how the AOSP hardware OEM contract is written....
Remember how hard Amazon had it to attempt an Android fork?
I was due to OEM SOC access being locked out due to those contracts....
Any open source mobile OS attempting to complete with AOSP needs access to mobile OEM soc providers not touched by AOSP contracts and currently that is somewhat hard.
Crazy idea: when companies change their product, they have to change the name.
Do you ever feel like the same food item doesn't taste the same it did 10 years ago? Maybe it's your memory being faulty or maybe the company got new management which decided to cut costs while keeping prices, extract the differential value from customer inertia and move on when the product stops being profitable.
Android is the same. Certain freedoms were a part of the offering - a part of the brand name. They no longer are. Not only should lose their trademark[0], they should be legally forced to change the name.
[0]: The purpose of which is to identify genuine product from counterfeits - in this case, the counterfeit just happens to be by the same company which released the original product.
>But Google said… Said what? That there’s a magical “advanced flow”? Did you see it? Did anyone experience it? When is it scheduled to be released? Was it part of Android 16 QPR2 in December? Of 16 QPR3 Beta 2.1 last week? Of Android 17 Beta 1? No? That’s the issue
A bit ironic to not believe Google is doing this. The same questions have same answers when asked about when Google is locking down side loading. A bit self-serving to pick and choose which things you want to believe are happening.
Google made the first move with their initial plan to lock it down, so the onus is on Google to calm the fears they caused if they don't want people to distrust them.
Android was never open. User apps are limited, only system apps can do X which means third party apps can't compete with Google and this is not a coincidence.
Let's focus on making it possible to use really open Linux systems on smartphones.
There are some functionality limited to google play services, but it really is not too much in my opinion.
The amount of open stuff that was migrated into the Play Services closed source blob over the years just keeps growing.
I still can't comprehend why they implemented FIDO/WebAuthn support in Play Services. Passkeys are extremely difficult to support in apps that don't depend on Play Services client libraries.
I'm not sure what you're referring to, but I was talking about the whole permissions system where the user is a third class citizen. Device manufacturers are second class citizens (restricted by Google via CDD/CTS) and the only true winner on that system is Google.
Regarding some concrete examples - Google can deeply integrate Gemini, but a competitor can't do this and users get no final say here either. Competitors are restricted by the permission system, Google is not restricted at all.
While rooting can alleviate this to some extent, Play Integrity is there to make sure the user regrets that decision to break free..
Just like Microsoft screwed up Windows, Google will screw up Android and people will move to Linux on PCs and some open version of Android, or Harmony, or whatever new mobile system comes up, on their phones.
Nothing lasts for ever. The sooner you make the switch, the better off you will be.
What is the advantage of moving sooner vs. moving later when rough spots have been smoothed over?
> We see a battle of PR campaigns and whomever has the last post out remains in the media memory as the truth
You must find truth. Lies will find you.
Good thing
Capitalism is the privatization of human needs. As long as these tech platforms are owned privately they will be used to police and make money.
This view NEEDS to be central to the tech freedom rhetoric, else the whole movement is literally just begging politicians and hoping corporations do the right thing... useless.
Aren't the politicians or their appointed bureaucrats who'd be making all the decisions if these needs were government owned? Why would state control lead to less policing? What incentive structure would lead to innovation without a profit motive, when even the modern communist world relies on capital markets?
(these are honest questions and not "gotcha")
> Aren't the politicians or their appointed bureaucrats who'd be making all the decisions if these needs were government owned?
Well that would be true under a capitalist government.
> Why would state control lead to less policing?
Its not just "the state runs it", its "we actively become the state".
Collective ownership through peoples councils, peoples courts with a world view that keeps it all open: socialism.
The world view of not allowing individual ownership over collective goods, the world view of socialism, is the life line of the movement. The actual practice of daily democracy, of running production and of deciding social functions is everyones responsibility and it should not be left to what has become a professional class of liars.
Public office members, which should only exist where absolutely necessary, should be locals and serve as messengers with 0 decision making power. All power should be in the local councils. We can mathematically implement this today (0 knowledge proofs).
Every single book on socialism is on theory and practices of acheiving this. Thats what the "dictatorship of the proletariat is", the dictatorship of working people, collectively.
> What incentive structure would lead to innovation without a profit motive, when even the modern communist world relies on capital markets?
We've been innovating for hundreds of thousands of years before capitalism. You dont need to generate money to innovate, the innovation itself is the driver, AKA a better life. No need to lock and limit production behind the attaining of profits of those who lead it.
Thanks for responding.
Yeah, dude thanks for the good faith.
A lot of people are allergic to this rhetoric and will just assume I have a deep irrational bias, but I was actually a staunch free market supporter before.
Once I decided to be more intellectually honest with myself and read more about what both sides meant historically and currently, it really just made sense.
I'm so exhausted of the partisan "my team vs your team" politics in the US that shuts down conversation, overlooks the blatant hypocrisies on either side, simplifies every issue to a single label to plaster on your opponent, etc etc.
I take honest conversation where I can get it, even when I don't agree. And to be clear I don't agree with most of your points and think it's idealistic and couldn't work in the real world. But I appreciate the spirit of what you're arguing for (in my interpretation) power with the people vs power with corporations and government and I think that's a very fundamental principle that is very important common ground.
edit: clarity
Copyleft fixes this.
They have the incentive to never chose this.
If we force it upon them by begging politicians, corporations still have the incentive to find a way to remove it or circumvent it.
Youre playing the cat and mouse game because you've been taught that solving it is too extreme (thats not a coincidence).
We dont need to endlessly fight a whole class of people, capitalists, for them not to use the things we require against us. Only socialism can solve that.
From a marketing standpoint it seems like a baffling decision on Google's part.
I own a Pixel and while the hardware seems decent, I've had a buggy and annoying experience with Android, and it's been getting worse lately.
Are Google so high on their own supply that they think people use their phones out of preference for the OS? Because frankly it's not very good. That's like Microsoft thinking people use Teams because of its merits.
People buy Android phones because they can be had cheaper than an equivalent iPhone and because in spite of the buggy and inconsistent mess of an OS, you aren't beholden to Apple's regimented UX. Locking down Android will not give it a "premium experience"... It'll always just be "Temu iOS" at best.
Have you considered Graphene since you own a Pixel? It's a huge upgrade over the stock OS in terms of security, privacy and general reduction of bloat.
Yep it's definitely on my list but my Pixel is on its last legs and I'm considering going back to iOS.
Having just gone from an iPhone as my main phone to a Pixel with GrapheneOS, GrapheneOS is such a breath of fresh air. No constant push of AI, iCloud services, etc. plus I actually feel owner of my phone and not living on some feudal landlord's plot.
GrapheneOS is great!
I urge you not too. iOS is fully locked down -- Apple won't allow you to exert control over the hardware that you bought and own, it's shocking.
> "Temu iOS"
Come on, that's absolutely laughable.
There are several topics where Android is significantly ahead to the point that iOS is just a toy, and there are areas where the reverse is true.
And I say that as a recent convert, so it's not like I have a decade out of date view of any of the OSs. In my experience I had more visual bugs in case of iOS than android (volume slider not displaying correctly in certain cases when the content was rotated as a very annoying example).
>Come on, that's absolutely laughable.
It's not, though. Google phones are not going to suddenly become luxury devices.
It's going to remain at the same level of polish (i.e. mediocre), except now without the major selling point of being able to run your own apps and have alternative app stores, etc. Back around Ice Cream Sandwich or thereabouts they got rid of "phone calls only mode" and forced us to rely on their half-baked "priority mode" that's an opaque shitshow.
When my wife is on call she gets random whatsapp notifications dinging all night, whereas when I had an iphone I could set Focus mode and achieve proper "phone calls only".
Android is not good. I use it despite its flaws, because of the trade-offs, not because it's better.
> Google phones are not going to suddenly become luxury devices
Pixel Fold disagrees.
> When my wife is on call she gets random whatsapp notifications dinging all night, whereas when I had an iphone I could set Focus mode and achieve proper "phone calls only".
You can do that with do not disturb.
> Android is not good. I use it despite its flaws, because of the trade-offs, not because it's better.
That is your opinion. My opinion is different.
> Android is not good. I use it despite its flaws, because of the trade-offs, not because it's better.
Android is good, but Googled Android is not. You should check out GrapheneOS to see what Android done properly looks like.
You can definitely make a "phone calls only" mode: create a mode, allow certain apps to interrupt, and add only phone calls to the list.
I do think they should offer more pre-configured notification modes by default, if only to show people what they can do with the feature. Perhaps "phone calls only" should be one of those.
People buy high-end Android phones like crazy, I don't know what bubble you live in. Samsung Folds and Flips are the luxury phones, not the iPhone Pro Max S eXtreme Edition 32 GB that looks exactly like the base model but has a slightly better camera. People show off their S Pen and perfectly stabilised 100x zoom lens, not their liquid ass. Multi-window and DeX are features for professionals who need to Get Shit Done^TM, iPhones are the toys kids use to send memojis to each other.
And yes, I can also click one button and go into phone calls only mode. I can even set it on a schedule or based on my calendar. I don't know where you're getting your half-baked Android, mine Just Works.
You might not agree with every one of those points, but you can't seriously think everyone thinks like you. Go outside your bubble some time.
Putting "Samsung" and "luxury" in the same sentence is lunacy. Their proprietary Android is even worse than Google's.
Where do you live? I've literally never seen anyone using a Fold or Flip device, ever. My kids are at the age where some of their peers are starting to get phones. All those kids have iPhones.
If your plan is to keep saying unsubstantiated bullshit, take that to Reddit. Go to a store and try modern OneUI - it's just AOSP with a slightly different layout and more features. The apps are worse than Google's, but the OS is better. Both are miles above iOS in features, especially for power users. Split screen, windows, chat bubbles, DeX, notification categories and history, vendor-neutral PC integration and TV casting, ...
And I don't quite see your point about your kids' friends using iPhones. I sure as hell wouldn't give a kid a "luxury" phone. I'd take the cheapest thing that does the job and lasts a long time. An iPhone has a very long software support window so the cheaper models actually end up cost-competitive with budget Androids.
As for folds and flips, I've mostly seen people in suits using them, along with a few techy power users and some kids with rich parents. That's a luxury phone in my book.
babe wake up new hn copypasta just dropped
I'm talking about the OS though.
Me too. The OS sucks.
> Are Google so high on their own supply that they think people use their phones out of preference for the OS? Because frankly it's not very good
Honestly having gone back and forth between iOS and Android every three years or so, both OS are the same. It's not like the grass is really greener on the Apple side. The UX is virtually identical for anything that matters. Personally I put material Android above liquid glass iOS. The alleged polish of the Apple UX was lost on me when I had my last iphone.
The reason Google's moves are surprising has more to do with them embracing being a service player more and more with the arrival of Gemini and them having regulators breathing down their necks everywhere.
I guess they did it after the truly baffling US decision in the Epic trial but it's very likely to go against them in the EU.
The rumors that I have heard (and one government document I read that was poorly translated from Thai) is that there are some countries who are pressuring Google on this to combat info-stealing malware. Apparently, account-takeover/theft is very prevalent in SE Asia where most banking is done via Android phones.
Maybe but lobbying is extremely strong in SE Asia. It's hard to distinguish from governments putting pressure for something and companies suggesting it would be a good idea.
https://postmarketos.org/
It's time to say goodbye.
I love postmarketos, but there is not even one "Main" phone with all of the hardware feature supported.
https://wiki.postmarketos.org/wiki/Devices
Fairphone 4 looks close, hopefully fairphone 4 support will continue to improve at this rate. Pinephone is another close one, but underpowered hardware and camera support kills it.
I am not even that intensive of a phone user. but there is no way I could daily drive pmOS.
>F-Droid Basic Great, now they can spread themselves even thinner. Just revert the entire trash rewrite from years ago. Problem solved