com.debug.loggerui Copy

"DebugLoggerUI", a device-side log capture tool. Its permission set is the clearest evidence of what it does: it holds READ_LOGS, SET_DEBUG_APP, MANAGE_EXTERNAL_STORAGE and WRITE_MEDIA_STORAGE, runs a special-use foreground service, and can post notifications, control the status bar and draw over other apps. In short, it reads system logs and writes them to storage, and it is visible while doing so: users who notice it usually do so because of a persistent notification saying the DebugLoggerUI service is running. Community analysis describes it as logcat-like, weighted towards graphics and network logging including Bluetooth, and notes that on some devices it keeps running in the background when not in use. Attribution needs care. It ships on ranges built around MediaTek chipsets, including Blackview, CUBOT, OUKITEL, TCL and Newland in our sample, and it is widely described as MediaTek's MTKLogger tool carried over under a new package name from around Android 10. That rename could not be confirmed from a MediaTek source, so it is flagged here rather than asserted. In our sample the signer is the device maker's own platform key, including Samsung and OPPO keys, so the signer tells you who built the image rather than who wrote the tool. The builds recorded here all report version 6.2.0 with target SDKs of 31 to 36, and no change of role across Android releases could be sourced beyond the possible rename noted above. For Android Enterprise, EMM and kiosk use this is a data governance question more than a functional one. A tool that copies system, network and Bluetooth logs into device storage puts diagnostic detail somewhere your retention and access policies may not cover, and it consumes storage on hardware that often has little to spare. It is not user-facing on the devices recorded here, and what else on a build might depend on it could not be sourced. Where it has been turned off per user it has been reported as reversible by re-enabling it the same way. Against that, vendor support and RMA processes sometimes ask for exactly these logs, so agree that trade-off before disabling it across a fleet.

• Disabling the DebugLoggerUI service app in Android - Fitzcarraldo's Blog →
• add DebugLoggerUI - Universal Android Debloater, issue 776 →
• Package provenance for com.debug.loggerui - Android System App Database →

• Re-signed by each device maker with its own platform key - 10 different certificates appear across 8 device makers in our sample. That is the signature of a stock AOSP/system package every OEM builds and signs itself, not a single maker's or a third party's preinstall. These are platform-level keys: they also sign the Android framework itself.
• Its largest observed manifest declares 16 permissions: 1 runtime (user-granted), 9 signature or system-level and 6 install-time. The signature/system share marks it as a privileged component, not an ordinary app.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.