com.samsung.android.networkdiagnostic Copy

Labelled "NetworkDiagnostic" in English, with localised equivalents in other locales such as "Netzwerkdiagnose" and "Diagnostica di rete", this is a Samsung background component with no launcher icon; this database records no user-facing observation of it. It is Samsung platform-signed, on an OEM key that also signs the Android framework. Its permission set on this site's provenance data reads as network fault-finding and reporting. It requests fine, coarse and background location, ACCESS_WIFI_STATE and CHANGE_WIFI_STATE, ACCESS_NETWORK_STATE, INTERNET, WRITE_SECURE_SETTINGS, RECEIVE_BOOT_COMPLETED and WAKE_LOCK, a Samsung permission named sec.permission.NETWORK_DIAGNOSTIC, two permissions named for Samsung's DiagMonAgent (the diagnostics component documented separately on this site), and a Samsung Push Service token permission. The location permissions are less surprising than they look: Android requires ACCESS_FINE_LOCATION plus CHANGE_WIFI_STATE to start a Wi-Fi scan, and ACCESS_FINE_LOCATION plus ACCESS_WIFI_STATE to read scan results, for apps targeting Android 10 or higher, with location services enabled. That does not make the location access harmless, but it does mean a Wi-Fi diagnostic tool cannot work without it. Samsung documents a user-facing Phone diagnostics feature, reachable from the Samsung Members app or from Settings, Device care, Diagnostics, whose test list includes Mobile network and Wi-Fi. A package named NetworkDiagnostic plausibly sits behind network testing of that kind, but Samsung's page describes the Members feature and does not name this package, so treat that link as a reasonable reading rather than a documented one. 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. The administrator's interest is a privacy one: this is a component that can see the device's location and Wi-Fi surroundings and has internet access and a push token, so it sits on the data-egress side of the estate rather than the management side. It is rated with caution because it is platform-signed and long-standing, its relationship to Samsung's other diagnostics components is not documented, and WRITE_SECURE_SETTINGS means it is trusted to change system settings, so removing it may have effects that only show up later; test on one device first. Version note: this is a long-standing component rather than a recent addition. Samsung's certified application lists record NetworkDiagnostic at 2.0.01.15 on the Galaxy S9 (Android 9), 2.5.04.3 on the Galaxy Note20 Ultra 5G (Android 10), 2.5.05.2 on the Galaxy S20 FE 5G (Android 11) and 2.5.05.3 on the Galaxy S21 Ultra 5G (Android 11), while this database records 2.5.06.13 to 2.5.07.5 across observed API levels 28 to 37. No change of role across Android releases could be sourced, so it is treated as evergreen here; if that is wrong, the change is one Samsung has not published.

• Check your Samsung Galaxy device status and run diagnostics - Samsung US →
• Wi-Fi scanning overview - Android Developers →
• Galaxy S9 LTE (G960F) Application List, Android 9 - Samsung Knox CC Mode →
• 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.networkdiagnostic - 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 21 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 20 permissions: 3 runtime (user-granted), 1 signature or system-level, 8 install-time and 8 vendor or uncatalogued.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.