com.samsung.gpuwatchapp Copy

GPUWatch, a Samsung developer tool rather than a consumer app. Samsung's own Galaxy GameDev documentation describes it as "a tool for observing GPU activity in your application", built so that developers using Samsung devices can get GPU-related information with the least effort, and says the detailed information is overlaid onto the screen in real time. Its main selling point in that documentation is that no PC is needed: you turn it on at Settings, then Developer options, then GPUWatch, and launch the application you want to profile. It is not something a user opens. In our sample it has no launcher entry in any of the 64 observations recorded, it appears only on Samsung hardware, on 41 devices, and it is signed by the Samsung OEM key that also signs the framework on those devices. The permissions it declares are consistent with a Settings-driven overlay rather than an application: WRITE_SECURE_SETTINGS, READ_SEARCH_INDEXABLES, BROADCAST_CLOSE_SYSTEM_DIALOGS and FOREGROUND_SERVICE_MEDIA_PLAYBACK, plus one Samsung permission of its own. This site records declared rather than granted permissions, and declaring them is not evidence any of them is exercised. Version note, and this one is sourced from Samsung on both sides. Samsung documents three generations of the tool tied to platform releases: v1.0 for Android P, v1.5 for Android Q and v2.0 for Android R, each with its own list of supported Galaxy devices, and the S9 series is called out as having limited version support. Samsung's Common Criteria application lists corroborate where the package sat at the time: the Android 11 lists for the Galaxy S20 FE (G781B) and Galaxy S20 (G981U) both record GPUWatch as com.samsung.gpuwatchapp at version 2.0.40, while the Android 9 list for the Galaxy S10+ (G975F) does not include it at all. Absence from a single device list is not proof the package did not exist elsewhere on that release, so read that as a hint rather than a date. Current devices here carry 2.0.40 through 2.1.02.27015, observed from API 31 to API 37 and targeting API 31 to 36, so the v2 line documented for Android R has continued forward without Samsung publishing a v3 in the same place. For Android Enterprise, EMM and kiosk use the practical point is that Samsung documents enabling GPUWatch through developer options, and on a managed device that door is usually shut already. The Android Management API exposes advancedSecurityOverrides.developerSettings, whose default value DEVELOPER_SETTINGS_DISABLED "Disables all developer settings and prevents the user from accessing them", and which replaces the deprecated debuggingFeaturesAllowed and safeBootDisabled fields. A fleet on that default gains nothing from touching this package. Where you do want it gone anyway, on a Samsung fleet Knox Manage documents enabling or disabling a named preinstalled system app through its application policies. The rating below is caution rather than safe because nothing consulted establishes what else on a Galaxy build references it, and its READ_SEARCH_INDEXABLES and WRITE_SECURE_SETTINGS declarations suggest it is wired into Settings rather than standing alone, so disable it on one device and check Settings and developer options behave before rolling the change out.

• GPUWatch - Samsung Developers (Galaxy GameDev) →
• Galaxy S20 FE 5G (G781B) application list - Samsung Knox CC Mode documentation →
• Galaxy S20 5G (G981U) application list - Samsung Knox CC Mode documentation →
• Galaxy S10+ LTE (G975F) application list - Samsung Knox CC Mode documentation →
• Policy resource reference (advancedSecurityOverrides.developerSettings) - Android Management API →
• Enable or disable a specific system app - Knox Manage - Samsung Knox Documentation →
• Package provenance for com.samsung.gpuwatchapp - 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 19 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 5 permissions: 3 signature or system-level, 1 install-time and 1 vendor or uncatalogued. The signature/system share marks it as a privileged component, not an ordinary app.
• APK size ranges from 2.6 MB to 10.8 MB across the reporting device profiles, so the build differs substantially between them.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.