com.sec.android.desktopmode.uiservice Copy

Recorded as "Samsung DeX", this is a system component of Samsung's DeX desktop mode. Samsung describes DeX as a desktop-like experience run from a Galaxy phone or tablet, either wired to a monitor over USB-C or HDMI or cast wirelessly to a compatible smart TV, with multiple resizable app windows, a taskbar and the phone usable as a touchpad. This package is not an app a user launches: in our sample it has no launcher entry on any device. Its label, its package name and its permission set (Bluetooth, Wi-Fi and display-related permissions) place it in the DeX desktop-mode user interface, though Samsung does not publish a component-level breakdown of DeX, so the precise division of work between it and the DeX home package below is inference rather than documented fact. It is a Samsung system component, not a downloadable app. Every observation in our sample is signed by the same Samsung key, that key also signs the framework, and no observation is Play eligible, so it arrives in the system image and updates with the firmware. It is seen only on samsung devices, on API levels 28 to 36, with version names from 4.2.03.4 to 5.0.15. Version note: DeX is not static across releases. Android 16 added desktop windowing to the platform itself, and Google states that it and Samsung collaborated on that work and that the advances "will enhance Samsung DeX". Reporting on One UI 8 describes Samsung replacing the classic DeX implementation with one built on Android 16's desktop mode, and removing the dedicated DeX settings tab in favour of a general connected display menu, so the options an administrator or user sees differ by One UI version. How that rebuild changed this specific package's role could not be sourced. Samsung's own Knox documentation shows the same version sensitivity from the management side, marking some DeX policies as not supported on Knox 3.12 or later and others as requiring Knox 3.14 and higher or Android 12 or later. Check behaviour against the specific One UI and Knox version in your fleet rather than assuming it carries over. For Android Enterprise, EMM and kiosk use, note first that Samsung's Knox documentation states plainly that DeX is not supported on devices running in Kiosk mode or Lock task mode, so DeX is not a route to a locked-down single-app deployment on an external display. Where DeX is wanted on managed devices that do not use those modes, control it by policy rather than by removing packages. Knox Service Plugin exposes DeX controls including "Allow Dex connection", enforcing an Ethernet connection, managing a list of apps disabled in DeX mode and Tap2DeX, plus a DeX customisation profile (needing a free Knox Platform for Enterprise Premium licence) that can auto-start DeX on HDMI connection, auto-launch an allowlist of apps, hide apps in the app drawer, set the wallpaper and loading logo and skip the welcome screen. Disabling this Samsung-signed component instead of using those controls should be expected to affect DeX and connected-display behaviour, and the effect was not verified here, so test on a device before applying it to a fleet. Treat it with caution.

• Samsung DeX - Samsung UK →
• DeX policies - Knox Service Plugin, Samsung Knox Documentation →
• Developer preview: Enhanced Android desktop experiences with connected displays - Android Developers Blog →
• Desktop windowing - Android Open Source Project →
• Samsung killed its classic DeX mode in One UI 8, but there's a good reason - Android Authority →
• Package provenance for com.sec.android.desktopmode.uiservice - 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 9 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 (580 packages, 11729 observations).
• Its largest observed manifest declares 26 permissions: 4 runtime (user-granted), 8 signature or system-level, 6 install-time and 8 vendor or uncatalogued.
• APK size ranges from 0.1 MB to 7.0 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.