com.samsung.android.samsungpositioning Copy

A second Samsung location-related component, reported by devices under the terse label "SamsungPositioning". Like the Samsung Location SDK above, Samsung names it in its Knox Common Criteria mode application lists but publishes no description of it. It is Samsung-signed with a framework-signing certificate, has no launcher entry in our sample, and is the larger of the two at roughly 6 to 7 MB. The useful detail in our own record is what it does not hold. Despite the name, no Android location permission is recorded against it in our sample. Its recorded set is INTERNET, FOREGROUND_SERVICE, WAKE_LOCK, DEVICE_POWER and RECEIVE_BOOT_COMPLETED, plus Samsung-defined permissions for the Samsung keystore, for Samsung's diagnostic agent, DiagMon, and a Samsung Push Service token. So on the evidence here it is a network-connected background service that starts at boot and talks to Samsung services, rather than a component reading the platform location APIs directly. What it computes, and what relationship it has to the Samsung Location SDK beyond the shared subject area, is not published by Samsung and is not asserted here. Version note: the numbering here has moved much less than its companion's. Samsung's certified lists record 3.1.00.4 on the Galaxy S20 5G (Android 10) and 3.1.01.6 on both the Galaxy S21+ 5G and the Galaxy Z Flip 5G (Android 11), while our sample runs 3.1.03.6 to 3.1.03.30 across target SDKs 31 to 37. The numbering stays within the 3.1.x line throughout, though that on its own does not establish that the behaviour is unchanged, and we could not source any behaviour that differs by Android release. For Android Enterprise, EMM and kiosk fleets it is again a privacy and egress question rather than a management one. It has internet access, push and diagnostics permissions, so on a fleet with strict data-residency or telemetry requirements it belongs on the list of Samsung components you account for, alongside Samsung's diagnostic and push services documented separately on this site. We found no source making it an enrolment or policy dependency. As before, nothing published says what depends on it, so test removal on one device before applying it more widely.

• Galaxy S21+ 5G (SM-G996B, Android 11) Common Criteria mode application list - Samsung Knox Documentation →
• Galaxy Z Flip 5G (SM-F707B, Android 11) Common Criteria mode application list - Samsung Knox Documentation →
• Galaxy S20 5G (SM-G981N, Android 10) Common Criteria mode application list - Samsung Knox Documentation →
• Package provenance for com.samsung.android.samsungpositioning - 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 12 permissions: 1 signature or system-level, 5 install-time and 6 vendor or uncatalogued.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.