com.wssyncmldm Copy

Made by Samsung and labelled "Software update" on the device in every locale we have recorded, this package sits on the firmware update path on Galaxy hardware. It has no launcher entry of its own in our sample, and it is signed by Samsung OEM keys that also sign the Android framework. Samsung does not publish a page describing this package on its own, so treat the mapping between it and the Settings entry a user sees as inferred from the device label rather than as documented behaviour. What is documented is where it matters most in an Android Enterprise, EMM or kiosk deployment. Samsung's Knox E-FOTA FAQ states that on a device deployed as a kiosk the Knox E-FOTA client "needs to be cleared by adding additional packages (com.wssyncmldm, com.samsung.android.knox.efota, and com.samsung.android.knox.efota.plugin) to control the app allowlist, so that the device can receive firmware update notifications and apply updates". The Knox Manage knowledge base article for the same problem tells administrators to add com.wssyncmldm as a system app in the console. If your kiosk allowlist omits it, the usual symptom is a fleet that silently stops taking firmware and security updates, so this is a package to allow rather than to block. Note also that Knox E-FOTA changes what the consumer update path does: once a device is enrolled in Knox E-FOTA it no longer receives the consumer, or business-to-consumer, firmware updates, and unenrolling is what re-enables them. Where you want to hold or schedule updates, use policy rather than interfering with the updater: a DPC can set a system update policy of automatic, windowed or postponed, and on Android 9 (API level 28) or higher it can define freeze periods of up to 90 days. Version note: builds observed here run from 3.9.16 to 4.6.13, targeting API 31 up to 36, so it is maintained across current Android releases. Samsung ships more than one update-related package - com.sec.android.soagent is documented separately on this site and carries the same "Software update" label - and we could not source how the work is divided between them on a given build, so do not assume either one is the whole update stack.

• Knox E-FOTA frequently asked questions - Samsung Knox Documentation →
• How to enable FOTA notifications for devices in Knox Manage kiosk mode - Samsung Knox Documentation →
• Manage system updates (device policy controller) - Android Developers →
• Package provenance for com.wssyncmldm - Android System App Database →

• Signed by the device maker's own signing key (Samsung), so it is an OEM preinstall, but 2 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 44 permissions: 2 runtime (user-granted), 14 signature or system-level, 11 install-time and 17 vendor or uncatalogued.
• APK size ranges from 8.7 MB to 15.4 MB across the reporting device profiles, so the build differs substantially between them.
• Reported as an updated system app on 1 of 22 profiles - a newer build is installed over the one in the system image there.