this post was submitted on 18 Feb 2026
265 points (97.2% liked)

Android

21468 readers
133 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

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. 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.

  5. 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.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 2 years ago
MODERATORS
(page 2) 47 comments
sorted by: hot top controversial new old
[–] IronBird@lemmy.world 1 points 2 days ago* (last edited 1 day ago) (2 children)

i was gonna try turning a steam deck into all-in-one device including phone, with portable GSM router of whatever i'd to use it for calls (it does have a mic, right?)

not sure if/how that'll work out

load more comments (2 replies)
[–] roofuskit@lemmy.world 1 points 2 days ago (1 children)

Locked down platforms don't have opt outs for the locks. Though it is a concerning move in the wrong direction.

[–] Ulrich@feddit.org 5 points 2 days ago (2 children)

What opt outs are you referring to? Installing an alternative OS?

[–] roofuskit@lemmy.world -5 points 2 days ago (1 children)
[–] Ulrich@feddit.org 1 points 2 days ago (1 children)

No such "backing down" to speak of there

[–] roofuskit@lemmy.world -1 points 1 day ago (1 children)

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.

[–] Ulrich@feddit.org 0 points 1 day ago* (last edited 1 day ago)

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.

[–] roofuskit@lemmy.world 0 points 2 days ago (8 children)

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.

[–] davidgro@lemmy.world 2 points 1 day ago* (last edited 1 day ago) (1 children)

Did you actually read the link? They address this in a big red box:

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.

[–] Auli@lemmy.ca 1 points 1 day ago

You can always install with adb.

[–] Ulrich@feddit.org 4 points 2 days ago (2 children)

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.

[–] cowfodder@lemmy.world 1 points 2 days ago (2 children)

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

[–] Luminous5481@anarchist.nexus 6 points 2 days ago (1 children)

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

[–] cowfodder@lemmy.world 1 points 2 days ago (1 children)

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. 

[–] Luminous5481@anarchist.nexus 0 points 1 day ago

yeah, that's a whole lot of corporate speak that says absolutely nothing. they wrote two whole paragraphs that promise nothing and don't back down on their verification plans. and you fell for it, too.

you have no idea what that "advanced flow" means, or what it entails, or even if it will actually be there to begin with, or how long it will be there until they discontinue it.

[–] Ulrich@feddit.org 1 points 2 days ago (2 children)

Did you actually read it? That's not what it says at all.

[–] Auli@lemmy.ca 1 points 1 day ago

I mean what they pasted here sure sounds like that us what it says.

[–] cowfodder@lemmy.world 1 points 2 days ago (1 children)

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. "

[–] Ulrich@feddit.org 4 points 2 days ago* (last edited 2 days ago) (1 children)

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

[–] Pika@sh.itjust.works 1 points 1 day ago* (last edited 1 day ago) (2 children)

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.

[–] Ulrich@feddit.org 1 points 1 day ago

I hope you're right

load more comments (1 replies)
[–] roofuskit@lemmy.world -4 points 2 days ago (1 children)
[–] pkjqpg1h@lemmy.zip 3 points 2 days ago (1 children)

Why you are spamming?

Do you know how to read? Do you know how to click links?

If you do you would see this in this page https://android-developers.googleblog.com/2025/08/elevating-android-security.html

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.

[–] roofuskit@lemmy.world -1 points 1 day ago

I could ask the same.

Each individual asked for the evidence, I presented it.

[–] pkjqpg1h@lemmy.zip 0 points 2 days ago (1 children)

you can only do that if you use a custom ROM

but on official ROM, no you can't

[–] roofuskit@lemmy.world -5 points 2 days ago (1 children)
load more comments (5 replies)
[–] timewarp@lemmy.world -2 points 2 days ago (8 children)

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.

[–] skuzz@discuss.tchncs.de 3 points 2 days ago

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.

[–] Maestro@fedia.io 2 points 2 days ago (1 children)

Is it possible to try Graphene out, like dual booting on PCs? Without throwing the existing Android setup away or bricking it?

[–] frongt@lemmy.zip 2 points 2 days ago

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.

load more comments (6 replies)
load more comments
view more: ‹ prev next ›