Package
vendor.qti.qesdk.sysservice
QesdkSysApp
Package intelligence
Observed signing, permission, version and size signals from contributing devices - descriptive of that sample, not a verdict. These come from the v2 Package Search sync, which not every device has contributed to yet, so for some packages this detail is partial or not present at all.
- Signed by the device maker's own signing key (Crosscall), so it is an OEM preinstall, but 2 different certificates appear across the fleet, so OEMs ship their own builds of it.
- Its largest observed manifest declares 4 permissions: 3 signature or system-level and 1 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.
Declared permissions (4)
Largest permission set observed for this package. Text is Android's own published description where one exists; platform permissions Android does not document show their granted protection level (in grey) instead; vendor or unknown constants show the name only.
| Permission | Description |
|---|---|
INTERACT_ACROSS_USERS |
Signature or privileged system permission. |
OBSERVE_GRANT_REVOKE_PERMISSIONS |
Signature or privileged system permission. |
REAL_GET_TASKS |
Signature or privileged system permission. |
RECEIVE_BOOT_COMPLETED |
Allows the app to have itself started as soon as the system has finished booting. This can make it take longer to start the phone and allow the app to slow down the overall phone by always running. |
Manage on devices
ADB commands for this package (the inverse of each is included so you can undo). Run from an authorised shell or wire the equivalent into your DPC. Verify on a test device first - this database doesn’t yet classify which packages are safe to change. --user 0 targets the current user; drop it (and use a privileged shell) to act device-wide.
/system, so Restore re-adds it (-k keeps app data)Seen on
Each record is a device profile (make + model + Android version). Each unique handset that syncs against a matching profile will increase the observations of a package, thereby increasing confidence that a package is expected to be on a device.
| OEM | Model | Android | Provenance | Observations | Last seen |
|---|---|---|---|---|---|
| Crosscall | Stellar-X5 | Android 13 | - | 1 | 16 Jul 2025 |
| Crosscall | Stellar-X5 | Android 14 | - | 3 | 1 Sep 2025 |
| Crosscall | Stellar-X5 | Android 15 | OEM Crosscall | 1 | 9 Apr 2026 |
| Datalogic | Memor 35/35X | Android 15 | - | 1 | 11 Nov 2025 |
| Elo Touch Solutions | 15in-I-Series-5 | Android 14 | - | 12 | 22 Nov 2025 |
| Fairphone | Fairphone 6 | Android 15 | - | 2 | 6 Nov 2025 |
| Fairphone | FP4 | Android 13 | - | 1 | 20 Dec 2025 |
| Fairphone | FP4 | Android 15 | - | 1 | 28 May 2026 |
| Isafemobile | IS540 | Android 14 | - | 2 | 17 Sep 2025 |
| Lenovo | TB352FU | Android 15 | - | 1 | 8 Apr 2026 |
| Motorola | moto g85 5G | Android 14 | - | 1 | 21 Aug 2025 |
| OnePlus | HD1903 | Android 12 | - | 1 | 10 Sep 2025 |
| Xiaomi | 23124RA7EO | Android 15 | - | 1 | 17 Jun 2025 |
| Zebra Technologies | KC50 | Android 13 | - | 1 | 22 Dec 2025 |
| Zebra Technologies | KC50 | Android 14 | OEM Zebra Technologies | 1 | 2 Jun 2026 |
Known labels
Locale-aware display names seen in the wild.
| Label | Locale | Seen |
|---|---|---|
| QesdkSysApp | en-us | 19 |
| QesdkSysApp | en-gb | 10 |
| QesdkSysApp | en | 1 |
| QesdkSysApp | en-US | 1 |
| QesdkSysApp | fr-fr | 1 |