So, I will no longer be allowed to install APKs that aren't from the Play Store? I thought they backed down on that.
this post was submitted on 18 Feb 2026
122 points (95.5% liked)
Android
21454 readers
287 users here now
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
🔗Universal Link: !android@lemdro.id
💡Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
📰Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
founded 2 years ago
MODERATORS
not just play store it's worse, if the developer didn't pay to google and give ID to Google, no-one can install that app
Right now the best solution is using custom ROMs
A lot of people reported that they did. I don't know why. Nothing in their statement said that. They did say they were going to add some "advanced workflows" but didn't elaborate anymore than that. It says it right in the link in OP:
Update: Google has not “backed down” from developer verification: Contrary to a vague mention of a possible “advanced flow” that may eventually allow “experienced users to accept the risks of installing software that isn’t verified”, Google’s description of the program continues to state plainly that: "Starting in September 2026, Android will require all apps to be registered by verified developers in order to be installed on certified Android devices". Until such time that they have shown evidence that it will be possible to bypass the verification process without undue friction, we must believe what is stated on their official page: that all apps from non-registered developers will be blocked once their lock-down goes into effect.
FuckGoogle
Use Custom ROMs with MicroG
Here is active and good custom ROMs
LineageOS (many devices) e/os (many devices) crDroid (many devices) GrapheneOS (only pixel)
that's just it, they're targeting custom ROMs with this too. the number of security updates for AOSP is being cut by Google in order to make custom ROMs less secure, so that they can then close down the project while claiming it's to protect users. make no mistake, the end goal here is make everyone who uses Android have to do so on their terms.
it's why Linux phones being mainstream is an absolute priority.
the number of security updates for AOSP is being cut by Google in order to make custom ROMs less secure
Please don't spread misinformation. Google didn't cut security updates. You can still get monthly security updates on Custom ROMs.
Also it's just on certified devices
Starting next year, Android will require all apps to be registered by verified developers in order to be installed by users on certified Android devices. source
https://discuss.grapheneos.org/d/27068-grapheneos-security-preview-releases
This is probably where they got the 3 month number. It is fuckery and they are making the lives of custom rom developers more difficult than they need to be.
Here is a good information from LineageOS;
Over the last few years, AOSP has been shifting to a quarterly release cadence, meaning that new features and bug fixes are released every three months. link
misinformation and grapheneos, again?
https://www.androidauthority.com/android-risk-based-security-updates-3597466/
They're not releasing the list of vulnerabilities each month but instead doing it quarterly, so how are custom ROM devs supposed to patch vulnerabilities if google isn't reporting them to manufacturers and developers like they've done for over a decade now?
Wow you're completely full of shit aren't you
what do you mean?
This is only fuel on the EU open source initiatives.
But I'm pretty sure Google wont get away with locking down EU customers anyway, as this is clearly a breach of the DMA.
They could clam a web app is the "alternative" I guess.
They'll shut that down too. Somehow. For "security" I'm sure, even as the Play Store is infested with scam apps.
Play Store is infested with scam apps
Last time when I checked most of the apps was scam
They mandate 3rd party app stores. I think we are passed that.
Google is just power grapping what they can towards everyone else to make up for lost profit.
this is clearly a breach of the DMA
Is it? I think the DMA should have been written so that it is, but Apple does essentially the same thing and EU regulators don't seem to be claiming that it's a violation.
Good news on the GrapheneOS front: Graphene will be available on hardware other than Pixels.
I like my Pixel 6 Pro just fine, but I'm nonetheless thrilled about this.
https://piunikaweb.com/2026/02/02/grapheneos-non-pixel-hardware-announcement/
good but I don't have couple months
So, I guess this means that f-droid can only be installed via Google Play. /s
I'm getting flashbacks to using Internet Explorer to install Firefox.
edit: made sarcasm more obvious.
Locked down platforms don't have opt outs for the locks. Though it is a concerning move in the wrong direction.
What opt outs are you referring to? Installing an alternative OS?
Not sure if you've been following but the app lockdown does not prevent you from installing apps. You can opt out of the controls they are implementing. They backtracked after the outrage.
Yeah but theyre obviously gonna try again once everyone has move on
Yup, which is why we have to be diligent and prepared. But false information doesn't solve that issue because you get dismissed.
They didn't fully backtrack. They haven't given details but there are still questions about what "advanced flow" means and whether it'll involve Google spying on what people install. Even if they backed off the worst part of it, this is still monopolist, anti-consumer, and likely privacy-violating behavior, and the correct action isn't to go "eh they compromise a little so I'll shut up and eat my slop"
load more comments
(2 replies)
Not sure if you've been following but there's no way to opt out. They did not backtrack on anything, despite widespread erroneous reporting. If you click the OP, it says as much. If you have a source that shows they did, please share it because I'd love to read it.
Here's Google's official blog where they back off from complete lockdown
Android Developers Blog: Android developer verification: Early access starts now as we continue to build with your feedback https://share.google/5jCv5uDMFcFnc11UN
that's not backing down at all. they speak of a possible workflow, but they don't say you'll be able to install unverified apps. they still say they'll require it, in fact.
Starting in September 2026, Android will require all apps to be registered by verified developers in order to be installed on certified Android devices
Empowering experienced users
While security is crucial, we’ve also heard from developers and power users who have a higher risk tolerance and want the ability to download unverified apps.
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.
Did you actually read it? That's not what it says at all.
Sure did. Did you?
"Empowering experienced users
While security is crucial, we’ve also heard from developers and power users who have a higher risk tolerance and want the ability to download unverified apps.
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. "
As I said earlier, only a vague mention of an "advanced flow" that's still in the works. Nothing saying they are no longer going to require distributors to register with Google, but it does say that they will require it on Google's own website:
Starting in September 2026, Android will require all apps to be registered by verified developers in order to be installed on certified Android devices
Just adding in, The Android developer page does clarify this problem. It will be a default on and will require the user going out of their way to turn it off.
They have a direct question there labeled as the following.
If I want to modify an app and install it on my own device, or if I'm a power user, is there a way to turn this verification requirement off
And then the response is as follows.
We understand this is an important use case for many developers and power users. While the verification requirement itself is a core OS feature to help protect the broader ecosystem from malware and can't be turned off, we plan to offer two paths for experienced users to install unverified apps:
- Advanced flow: We are building a flow that allows experienced users to proceed with installing an unverified app after going through a series of clear warnings. This new mode is designed to resist social engineering, helping users fully understand the risks, but ultimately gives experienced users the choice to accept the heightened security risk and install the software. We are gathering early feedback on the design of this feature now and will share more details in the coming months.
- Android Debug Bridge (ADB): Developers and power users can still use Android Debug Bridge (ADB) to build, test, and install modified or unverified apps on their own devices, which remains the standard method for development work.
Honestly, it doesn't seem all that different than how fdroid is currently configured on Google. I expect that you'll have to enable an option on top of the unofficial sources toggle that also states unverified apps.
Being as they also specify what the Android debugging bridge is as a second bullet point, I expect that it's not going to be through ADB like a lot of people were worried about as well.
load more comments
(2 replies)
load more comments
(4 replies)
No such "backing down" to speak of there
All Google has said is that “it’s not a sideloading restriction, but an ‘Accountability Layer.’ Advanced users will be able to’Install without verifying,’ but expect a high-friction flow designed to help users understand the risks.”
That quote comes from the director of product management from Google Play. It has not been altered or deleted since posted.
Again, a bunch of vague nonsensical horseshit. That sounds like their previous strategy where they said you could use adb, which is completely unrealistic, and is 1000% a sideloading restriction.
Time to finally move to GrapheneOS. Hope they finish polishing it, including things like automated backups. I'm going to donate to them. They have consistently proved themselves to be a legitimate project.
GrapheneOS is ok but the people behind don't have good reputation on open-source; They smear F-Droid, Firefox, Linux even uBlock Origin https://lemmy.zip/post/59060122
What Google has been doing to Android the past few years puts the future of Graphene in jeopardy. Especially with closing off third-party access to the binary blobs needed to enable newer Pixel hardware.
Is it possible to try Graphene out, like dual booting on PCs? Without throwing the existing Android setup away or bricking it?
Yes, but I don't know if it works with grapheneos. You can live-boot an image with fastboot boot boot.img. You need the grapheneos img file obviously, and a working fastboot connection, and an unlocked bootloader. Usually unlocking the bootloader means wiping the device before you can do anything else though.
If you have a pixel, grapheneos should work just fine. Except adding payment cards to Google wallet (non-payment cards and digital tickets work fine though). Some apps may refuse to work on uncertified devices. RCS support depends on your carrier. Outside of those things, though, literally everything else I've done has worked.
view more: next ›