com.samsung.android.secsoundpicker Copy

The second sound chooser Samsung ships. It is labelled "SecSoundPicker" on the device, and that label is recorded untranslated in every locale on this site, which is the pattern of an internal component rather than something presented to a user. It is signed by Samsung OEM keys, the dominant one being a key that also signs the Android framework, a platform-level key. Samsung's Common Criteria application lists name it as "SecSoundPicker", com.samsung.android.secsoundpicker, at version 10 on the Galaxy Note20 Ultra 5G Android Q listing and 1.0.00.23 on the Galaxy S21 Ultra 5G Android R listing. This site records builds from 2.0.00.32 to 4.0.01.31 targeting API 30 to 37. Those are the version strings observed; on their own they count changes without describing them, so treat them as figures rather than as evidence of what changed between releases. Both Samsung listings above record this package and com.samsung.android.app.soundpicker on the same firmware, so on those builds the two ship alongside each other rather than one standing in for the other. In this site's sample com.samsung.android.secsoundpicker is not observed below API 31 while com.samsung.android.app.soundpicker is observed from API 28; observation data establishes presence rather than absence, so treat that as indicative rather than as a release boundary. Its recorded permissions go further than the other picker's: alongside READ_MEDIA_AUDIO it holds READ_MEDIA_IMAGES and READ_MEDIA_VIDEO, MODIFY_AUDIO_SETTINGS and its privileged variant, MANAGE_NOTIFICATIONS, WRITE_SETTINGS and WRITE_SECURE_SETTINGS, MANAGE_EXTERNAL_STORAGE, and the cross-user permissions INTERACT_ACROSS_USERS, INTERACT_ACROSS_USERS_FULL, QUERY_USERS and MANAGE_USERS. That is consistent with a picker that also serves per-app notification sound selection and operates across Android users, which would include a work profile. This site aggregates permissions across observations rather than per build, so which builds declare them cannot be established from it. For Android Enterprise, EMM and kiosk use the practical guidance matches the other picker: no enrolment or management role, nothing user-visible to remove, and a real chance that disabling it breaks tone selection somewhere in Settings. Test before removing it fleet-wide.

• Galaxy Note20 Ultra 5G (N986B) Application List - Samsung Knox Documentation →
• Galaxy S21 Ultra 5G (G998B) Application List - Samsung Knox Documentation →
• Package provenance for com.samsung.android.secsoundpicker - Android System App Database →

• Signed by the device maker's own signing key (Samsung), so it is an OEM preinstall, but 3 different certificates appear across the fleet, so OEMs ship their own builds of it. It also signs the Android framework, so it is a platform-level key on its device(s). Inferred from the certificate appearing only on Samsung devices (508 packages, 10196 observations).
• Its largest observed manifest declares 29 permissions: 4 runtime (user-granted), 13 signature or system-level, 6 install-time and 6 vendor or uncatalogued.
• APK size ranges from 2.8 MB to 11.4 MB across the reporting device profiles, so the build differs substantially between them.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.