com.samsung.android.brightnessbackupservice Copy

Labelled "BrightnessBNR" on the device, this is a small Samsung background component with no launcher icon; this database records no user-facing observation of it. Two Samsung OEM signing keys are recorded for it here, both of which also sign the Android framework, that is platform-level keys. Its permission set is short, and it is most of the evidence available for what the package does: DEVICE_POWER, READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE and a permission named com.wssnps.permission.COM_WSSNPS. The package name says brightness backup service, and read alongside shared storage read and write access the natural reading is a component that saves and restores the device's brightness state. Samsung publishes nothing found here that names this package, and the purpose of the com.wssnps permission could not be sourced, so that reading is an inference from the name and the permissions rather than a documented fact. One thing worth stating plainly, because it is the sort of thing an administrator checks: on this site's provenance data the package requests no network permission at all, neither INTERNET nor ACCESS_NETWORK_STATE, so nothing here suggests it is itself a route for data leaving the device. Note also that this site aggregates permissions across observations rather than per build, so which builds declare which permission cannot be established from it. Samsung's Samsung Cloud backup documentation lists what the Settings category covers, namely "accessibility settings, ringtones (excluding default ringtones), Samsung keyboard options, Wi-Fi settings, paired Bluetooth devices, facial recognition settings, fingerprint settings and Always on Display settings". Brightness is not among them, so whatever this component handles is not explained by that page. For Android Enterprise, EMM and kiosk use, no role in enrolment or policy is identified in the sources cited here, and nothing in the permission set points at one. It has no user-visible surface to lock down. It is rated with caution rather than safe for a practical reason: if the inference above is right, the effect of removing it would not appear at the time of removal but at the next backup or device transfer, which is the worst moment to discover it. Test on one device and complete a restore before rolling it out. Version note: Samsung's certified application lists record this package at version 10 on the Galaxy Note20 Ultra 5G (Android 10) and version 11 on both the Galaxy S20 FE 5G and the Galaxy S21 Ultra 5G (Android 11). On those three builds the recorded version matches the Android major release. This database separately reports versions 12 to 17 and observed API levels 28 to 37, but those are independent minimum and maximum roll-ups across observations rather than a per-build pairing, so they cannot show whether that correspondence also holds on the builds recorded here. Samsung publishes no versioning scheme for the package. On those certified lists the application column repeats the package name instead of a friendly label, whereas this database records the label "BrightnessBNR".

• Samsung Cloud - How to back up data on your phone - Samsung UK →
• 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 →
• Package provenance for com.samsung.android.brightnessbackupservice - 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 4 permissions: 2 runtime (user-granted), 1 signature or system-level and 1 vendor or uncatalogued.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.