com.samsung.android.audiomirroring Copy

Labelled "AudioMirroring" on the device, this is a Samsung background component with no launcher icon; this database records no user-facing observation of it. It is Samsung platform-signed, on an OEM key that also signs the Android framework. An honest starting point: no Samsung documentation naming this package was found for this note. Web results for the package name are APK catalogue listings, which are not a basis for a functional claim, so what feature it serves is not established here and no safe_to_disable rating is given. What can be said comes from this site's provenance data. It requests RECORD_AUDIO, MODIFY_AUDIO_ROUTING, MEDIA_ROUTING_CONTROL and MEDIA_CONTENT_CONTROL, together with INTERNET, ACCESS_LOCAL_NETWORK, ACCESS_WIFI_STATE and ACCESS_NETWORK_STATE, FOREGROUND_SERVICE and POST_NOTIFICATIONS, MANAGE_EXTERNAL_STORAGE, QUERY_ALL_PACKAGES and REAL_GET_TASKS, plus Samsung permissions named for personal media and for SCPM. Read together that is a component able to capture audio, control where audio is routed and which media session is in charge, reach the local network and the internet, and run a foreground service with a notification, which is consistent with moving audio between this device and another over a network link, as the name suggests. Note that this site aggregates permissions across observations rather than per build, so which builds declare which permission cannot be established from it. For Android Enterprise, EMM and kiosk use, no role in enrolment or policy is identified in the sources cited here. The permissions worth an administrator's attention are RECORD_AUDIO and MANAGE_EXTERNAL_STORAGE alongside internet access: a preinstalled component that can reach the microphone, read shared storage broadly and reach the network is the sort of thing a sensitive deployment reviews on its own terms, whatever the intended feature. Nothing in this data shows it capturing audio without a user action, and nothing here shows that it does not; the provenance data records what a package may do, not what it does. Where microphone access is the concern, the supported controls are the platform and vendor ones rather than removing this package: the Android Management API exposes a microphoneAccess policy field, which supersedes the deprecated unmuteMicrophoneDisabled field, and Samsung's Knox HDM mediates microphone hardware below the operating system. Version note: this database records builds from 3.1.00.29 to 4.1.00.5 across observed API levels 33 to 37, that is Android 13 and later, with a roll-up target SDK range of 33 to 36. The package does not appear on the Samsung certified application lists checked here for the Galaxy Note20 Ultra 5G (Android 10), the Galaxy S20 FE 5G (Android 11) or the Galaxy S21 Ultra 5G (Android 11). That is consistent with the package arriving after those releases, though a list that does not name a package is not proof it was absent from that firmware generation, and the release it arrived in could not be sourced.

• Galaxy Note20 Ultra 5G (N986B) Application List, Android 10 - Samsung Knox CC Mode →
• Galaxy S20 FE 5G (G781B) Application List, Android 11 - Samsung Knox CC Mode →
• Galaxy S21 Ultra 5G (G998B) Application List, Android 11 - Samsung Knox CC Mode →
• Hardware Device Manager - Samsung Knox Documentation →
• Policy resource, microphoneAccess - Android Management API reference →
• Package provenance for com.samsung.android.audiomirroring - Android System App Database →

• Signed by the device maker's own signing key (Samsung), so it is an OEM preinstall, and that single certificate is consistent across all 20 device profiles. 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 17 permissions: 2 runtime (user-granted), 5 signature or system-level, 5 install-time and 5 vendor or uncatalogued.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.