com.samsung.android.beaconmanager Copy

Both this package and com.samsung.android.easysetup below report the user-visible label "Nearby device scanning" in our sample, which is the name of a single Galaxy setting. Samsung describes that setting as a way to "easily set up connections to other available devices", sending a notification when there are devices available to connect to, and puts the toggle under Settings, Connections, More connection settings. This package is made by Samsung and signed by a Samsung OEM key that also signs the framework. It has no launcher entry in our sample; Samsung exposes the user-facing control through this setting. Its permissions in this database are the clearest evidence of what it does: BLUETOOTH_SCAN, BLUETOOTH_ADVERTISE, BLUETOOTH_CONNECT and BLUETOOTH_PRIVILEGED for discovering and advertising to nearby hardware, ACCESS_WIFI_STATE, CHANGE_WIFI_STATE, READ_WIFI_CREDENTIAL and NETWORK_SETTINGS on the Wi-Fi side, POST_NOTIFICATIONS for the prompts the feature raises, BIND_QUICK_SETTINGS_TILE for a quick-settings tile, and RECEIVE_BOOT_COMPLETED so it starts with the device. Samsung does not publish a component-level breakdown of the feature, so which part of it each of the two packages performs is not something we can source. For Android Enterprise, EMM and kiosk fleets this is a background discovery and prompting feature, and we found no source identifying it as an enrolment or management dependency. The relevant questions are whether unsolicited "device found" notifications are acceptable on a locked-down device, and whether continuous radio scanning is acceptable in a site where it is not wanted. Knox Service Plugin does carry an "Allow bluetooth scanning" advanced restriction, which Samsung describes as blocking the device from scanning for in-range Bluetooth devices to improve location detection accuracy, along with the equivalent "Allow Wi-Fi scanning" restriction that requires Knox 3.2 or above; both need a Knox Platform for Enterprise Premium licence. Note that Samsung frames those policies around location accuracy rather than around this setting, and we have not found documentation confirming they switch this feature off, so verify the effect on a test device rather than assuming it. Disabling the package itself should be expected to impair part or all of "Nearby device scanning" and the notifications it raises, but because Samsung does not document how the feature is split between this package and com.samsung.android.easysetup, the package-specific effect is undocumented and needs confirming on one device first. We found no source indicating any effect on ordinary Bluetooth pairing. Version note: the builds recorded here run from 11.0.00.21 to 11.6.11.3 with target SDKs from 31 to 36, so this has been observed across several Android releases without a change of major version. Four observations are marked Play-eligible, which suggests the component can also be updated outside a firmware release on some devices.

• Connection options for your Galaxy phone or tablet - Samsung →
• Advanced Restriction policies - Knox Service Plugin, Samsung Knox Documentation →
• Package provenance for com.samsung.android.beaconmanager - 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 (493 packages, 7791 observations).
• Its largest observed manifest declares 29 permissions: 4 runtime (user-granted), 12 signature or system-level, 7 install-time and 6 vendor or uncatalogued.
• Reported as an updated system app on 4 of 15 profiles - a newer build is installed over the one in the system image there.