this post was submitted on 21 Mar 2026
974 points (98.6% liked)

Android

33749 readers
2 users here now

DROID DOES

Welcome to the Android community on Lemmy. Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules


1. All posts must be relevant to Android devices/operating system.


2. Posts cannot be illegal or NSFW material.


3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.


4. Non-whitelisted bots will be banned.


5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.


6. Memes are not allowed to be posts, but are allowed in the comments.


7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.


8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.


Community Resources:


founded 2 years ago
MODERATORS
 

If you haven't seen this yet, Google is planning to require mandatory developer identity verification for all Android apps, including apps distributed outside the Play Store, taking effect September 2026. This affects every independent and open source Android developer directly.

This is not just about the Play Store. After September 2026, on any certified Android device, applications from unverified developers will be blocked by default. The only proposed bypass, the "advanced flow", exists only as a blog post and has not appeared in any beta, dev preview, or canary release. No one outside Google has seen it.

The community has been fighting back at keepandroidopen.org:

  • Read the full breakdown of what this means
  • Sign the open letter (organisations only)
  • Contact your national regulators — contacts listed by country on the site
  • Add the countdown banner to your project

September 2026 is closer than it looks. The time to push back is now.

(page 2) 50 comments
sorted by: hot top controversial new old
[–] inari@piefed.zip 10 points 1 week ago

Moved to GrapheneOS because of this crap

[–] foodvacuum@lemmy.world 10 points 1 week ago (3 children)

Google is trash. Next phone will absolutely be one of those upcoming graphene supporting Motorola phones. I'll grab an old phone to test out postmarketos too

[–] moopet@sh.itjust.works 5 points 1 week ago

The flow goes like this: Governments make a law requiring verification of devices on phone networks, phone carriers require an encrypted key to connect to the network, that key is only made available to approved OS developers... we need an entirely protected chain.

load more comments (2 replies)
[–] anticurrent@sh.itjust.works 10 points 1 week ago

Google is the biggest threat to anything good in technology, this cancer must be eradicated

[–] ColeSloth@discuss.tchncs.de 9 points 1 week ago (2 children)

Keep fighting this shit.

As to the "flow" thing, it's an extra 2 warnings and a mandatory 24 hour waiting period after you select to install apks from unknown sources. It can be permanently enabled, so the 24 hour wait will be a one and done thing if you choose the indefinite option. Googles stated reasoning for this is to prevent non tech people from falling for scam calls or messages using scare tactics like "your bank transfered out your savings" or whatever made to get people to panic and follow whatever commands they're told to do and install before having time to speak to a family member or contact their bank or card company themselves.

For what it's worth, I think that 24 hour part of it would prevent some people from getting scammed. There's a lot of naive people who still fall for stuff like that.

My issue is that I believe this is just a stepping stone to make it even harder or impossible to side load in the future. Like, a year or so later or whenever Google thinks they can get away with it they'll try removing the option to permanently allow side loading. So right now it will just be a few extra clicks and a 24 hour wait one time, but where will they move the bar next?

[–] outerspace@lemmy.zip 6 points 1 week ago (1 children)

And then your banking app and phone operator application will refuse to work if you have any of custom apk installed, like they do now if you have accessibility permission enabled for any applications or have enabled the developer mode. (Bangkok bank, AIS)

load more comments (1 replies)
load more comments (1 replies)
[–] ljosalhusky@lemmy.world 8 points 1 week ago (2 children)

Ah, how I love my Jolla C2 with SailfishOS ❤️, and how exited I am to get the new Jolla Phone I pre ordered. ✌️🙏❤️

load more comments (2 replies)
[–] coredev@programming.dev 7 points 1 week ago (5 children)

How will this affect MDM-solutions that installs apps from outside the GMS world

load more comments (5 replies)
[–] determinist@kbin.earth 7 points 1 week ago (17 children)

Opinions invited.

I currently have a Motorola Edge 50 Neo. It's a great phone, a little more than a year(?) old. It can't have LineageOS due to it's Dimensity chipset.

I'm considering buying a Fairphone 6, then put LineageOS on it.

Is the Fairphone decent? How's the camera?

Are there any other phones that I should consider (decent camera, will run LineageOS or similar)? Maybe the new Jolla phone?

[–] bennypr0fane@discuss.tchncs.de 5 points 1 week ago* (last edited 1 week ago) (4 children)

You should definitely consider the Jolla, but cameras are basically never great on degoogled devices, because flashing a new rom also deletes the OEM proprietary firmware, which was tailor-made for that device. What you get instead is a generic software that never comes close to matching the original quality. I think the hardware makers who sell degoogled phones, like Fairphone, would have chance to make good cameras, but none of them have actual years of experience making cameras, as companies like Samsung and Sony do.

load more comments (4 replies)
load more comments (16 replies)
[–] Trilogy3452@lemmy.world 6 points 1 week ago (1 children)

And it can't be disabled in forks? Or will the google sdk require that from the OS (for apps that use it)?

load more comments (1 replies)
[–] LowlandsFreak@sh.itjust.works 6 points 1 week ago

I was already looking flashing my Fairphone with Sailfish. But this move of Google is the final straw. Sailfish fully supports android apps. I'm already running every google app in a sandbox and stopped using my contactless payment.

[–] dependencyinjection@discuss.tchncs.de 5 points 1 week ago (2 children)

Wait that’s not a thing already?

So people can just make scam apps and once you report it to the App Store there is no recourse because even the company doesn’t know who they are?

[–] deathbird@mander.xyz 8 points 1 week ago (4 children)

The recourse has been removal.

And the solution proposed is not requiring identification specifically for Play store developers, but any developer at all.

load more comments (4 replies)
load more comments (1 replies)
[–] veniasilente@lemmy.dbzer0.com 5 points 1 week ago

Welp my next phone will be a used phone up to 2024 manufacturing. My current phone is already a used one, although one of 2018 manufacturing.

load more comments
view more: ‹ prev next ›