com.mediatek.duraspeed Copy

DuraSpeed, a MediaTek background-app manager shipped on devices built on MediaTek chipsets. Don't Kill My App describes it as a built-in MediaTek software layer meant to boost the foreground app by starving background processes, and on the Nokia 3.1 and 5.1 as a MediaTek-developed task killer that terminates background apps. Its English label is "DuraSpeed" or "Background APP management", with localised equivalents in other locales. The Ulefone and Telaeris guides reach it as its own DuraSpeed entry in Settings, whereas Don't Kill My App reports no user-facing control on the Nokia 3.1 and 5.1. In this sample it is recorded on phones and rugged devices from makers such as A-gold, Blackview, CUBOT, NUU, OUKITEL, Ulefone, Motorola and Xiaomi. Where signer data is recorded (Xiaomi, Motorola, OUKITEL, NUU and ANT DAO TECHNOLOGY LIMITED) it is signed by that maker's OEM key, a key that also signs the Android framework, a platform-level key. It requests permissions including WRITE_SECURE_SETTINGS, MANAGE_APP_OPS_MODES, QUERY_ALL_PACKAGES and INTERACT_ACROSS_USERS; this site aggregates permissions across observations rather than per build, so which builds declare them cannot be established. For Android Enterprise, EMM and kiosk use this is one to know about. Business app vendors document it interfering with their apps: Cleverence reports that on MediaTek-based data collection terminals DuraSpeed blocks its Mobile SMARTS client from launching a plugin, and says to turn DuraSpeed off; Telaeris documents turning it off, or turning it off per app, so that its access-control apps keep running in the background. The same could apply to an EMM agent, kiosk app or push-dependent line-of-business app, so test background behaviour on MediaTek hardware. The documented remedy is the DuraSpeed toggle in Settings, either globally or per app. Don't Kill My App reports that this setting can turn itself back on, and on the Nokia models that its hidden setting.duraspeed.enabled switch does not survive a reboot, so re-check it after reboots and updates. Disabling the package outright is not documented by MediaTek in the sources cited here; community guides describe removing it, but test that per model before relying on it. Version note: it is recorded here from API 27 to API 36, and this site's roll-up reports 3.0 as both its oldest and newest version string. Whether its behaviour changed in a particular Android release could not be sourced, and this site aggregates labels across observations, so it cannot date the alternative "Background APP management" label to a build or establish why it differs.

• Ulefone and RugOne - Don't Kill My App →
• Nokia - Don't Kill My App →
• Problem launching the plugin on terminals with MediaTek processors - Cleverence →
• Disabling battery restriction of XPressEntry and KeyLink - Telaeris →
• Package provenance for com.mediatek.duraspeed - Android System App Database →

• Re-signed by each device maker with its own platform key - 6 different certificates appear across 5 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 10 permissions: 1 runtime (user-granted), 3 signature or system-level, 4 install-time and 2 vendor or uncatalogued.