Android

33751 readers

14 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

Rooki@lemmy.world

L3s@lemmy.world

L4s@lemmy.world

974

Google is requiring mandatory developer verification for all Android apps in 2026 (infosec.pub)

submitted 1 week ago by TheTearMiser@lemmy.world to c/android@lemmy.world

229 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] mrbutterscotch@feddit.org 3 points 1 week ago (2 children)

Looking at the hardware it almost seems like they are using the same rear camera:

Motorola:

50 MP Sony Sensor - LYTIA ® 700C f/1.8 Blende 1 µm Pixelgrösse | Quad-Pixel-Technologie für 2 µm Quad PDAF Optische Bildstabilisierung (OIS) 13 MP Kamera mit Ultra-Weitwinkelobjektiv (120° Sichtfeld) Macro Vision f/2.2 Blende 1,12 µm Pixelgrösse PDAF 10 MP Teleobjektiv 3x optischer Zoom f/2.0 Blende 1,0 µm Pixelgrösse PDAF Optische Bildstabilisierung (OIS)

FP6:

50MP Sony Lytia 700C sensor, 1/1.56", 1.0μm pixel size Quadpixel Autofocus, 10 cm minimum focusing distance, time of flight sensor Up to 10x digital zoom Optical (OIS) image stabilization Ultra Wide camera: Image sensor: 13MP, 1/3.06", 1.12μm pixel size ƒ2.2 5 elements Autofocus, Macro Mode, 2.5cm minimum focusing distance, time of flight sensor Electronic (EIS) image stabilization

But I am no expert, I'm sure there are differences due to software.

[–] determinist@kbin.earth 2 points 1 week ago (1 children)

Hey, thanks!

I didn't think to check HW specs. Not very clever.

so ... thanks. again :))

[–] mrbutterscotch@feddit.org 1 points 1 week ago

My pleasure!

[–] mrbutterscotch@feddit.org 2 points 1 week ago

Ah damn, I messed up the formatting, but I think the info is discernible. They seem to be similar