Why is the default .apk installer called "Sounds" ?

graphenediscoverer4

I tried to sideload my first 3rd party app on top of default apps, so I get prompted to the Install Unknown Apps permission page. It says the system app responsible to do so is called "Sounds", with an android appicon. Is it AOSP who decided to call it this way ?

Might be unintuitive afterwards to look for the app that needs such permission removed

CyberOtter

graphenediscoverer4 You're confusing something here. The package "com.android.soundpicker" aka "Sounds" is used to pick Ringtones, that's it. It is not the default apk installer, and you should not change the settings of this app.

User2288

CyberOtter no he isn't confusing anything. I've seen this too.

graphenediscoverer4 CyberOtter
This has happened to me too where the "installing source" is declared as some system app other than the actual app doing the installing. Sometimes "sounds" and sometimes other components (cant recall). And as mentioned the special app access is also not listed correctly after.

@GrapheneOS @matchboxbananasynergy do you guys know anything about this?

traveller

CyberOtter

I remember that happening to me as well - a message popping up "Do you want to allow Sounds to install packages" (or similar), when I downloaded and opened .apk from GrapheneOS File manager (or MaterialFiles). That surprised me too, and seemed like a bug.

CyberOtter

traveller I could reproduce the bug with "MTP Host" system app instead of "Sounds". Same bug here on latest GrapheneOS Stable on Pixel 8. Tried installing an apk from stock files app. When i granted the permission to "MTP Host", the files app then was able to install the apk. Could not find the files app in Special App Access -> Install unknown apps.

matchboxbananasynergy

It's an upstream bug due to these components using the same UID, if I recall correctly.