Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to the Power Users community on Codidact!

Power Users is a Q&A site for questions about the usage of computer software and hardware. We are still a small site and would like to grow, so please consider joining our community. We are looking forward to your questions and answers; they are the building blocks of a repository of knowledge we are building together.

Comments on How does Google's Android developer registration affect sideloading and other stores?

Parent

How does Google's Android developer registration affect sideloading and other stores?

+12
−0

Google has announced that

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.

They claim (emphasis in original)

To be clear, developers will have the same freedom to distribute their apps directly to users through sideloading or to use any app store they prefer. We believe this is how an open system should work—by preserving choice while enhancing security for everyone.

But I don't think I understand. This sounds to me like full application control by the OS manufacturer.

What are the implications for submissions to third-party stores like F-Droid? What about sideloading APKs?

History

1 comment thread

Has anyone coined the phrase "regulatory smoke testing" yet? (1 comment)
Post
+1
−0

2025-11

If com.google.android.gms, and its dependencies, are installed, some of the more basic application stores, as they are currently implemented, shall cease to operate. That is because com.android.vending/com.google.android.finsky.protectdialogs.activity.PlayProtectDialogsActivity hooks into com.google.android.packageinstaller, and shall [1] prevent the installation of any .APK/.AAB that isn't signed via a key stored in Play App Signing. [2]

This appears to be bypassable via adb shell's /system/bin/pm install. [3] If so, Settings.Global.ADB_WIFI_ENABLED provides a workaround for most clients. [4] [5]

2026-01

Google intends to allow competent users to continue to bypass its new restrictions. [6] However, it shall add additional steps to accomplish this. Ultimately, this renders the change unimportant.


  1. github.com/BOINC/boinc/issues/5941 ↩︎

  2. reddit.com/r/androiddev/comments/6hfmoj/comment/diz06fl ↩︎

  3. stackoverflow.com/revisions/28686006/4 ↩︎

  4. github.com/ImranR98/Obtainium/issues/25#issuecomment-1869342116 ↩︎

  5. github.com/NeoApplications/Neo-Store/issues/102#event-20509715904 ↩︎

  6. github.com/MM2-0/Kvaesitso/discussions/1643#discussioncomment-14961982 ↩︎

History

1 comment thread

Re Update: Premature to declare change unimportant (1 comment)
Re Update: Premature to declare change unimportant
troyp‭ wrote 7 months ago

It's premature to declare the change unimportant. Google hasn't given any details about the supposed "advanced flow", so we really know nothing about what it will or won't allow.

Certainly, f-droid are not reassured by this vague promise.