System app database

Package

com.qti.qcc

QCC

40device profiles
71observations
0user-facing hits
10 Nov 2026last seen

Guidance

verified 10 Sep 2026

A vendor system component labelled "QCC" (the same label in each locale recorded here), with no launcher entry and no user-facing observation in our sample. It is recorded on devices from many makers, including Samsung, Motorola, Fairphone, OnePlus, Xiaomi, Zebra, Datalogic and Crosscall, and where a signer is recorded it is that maker's own OEM key that also signs the Android framework, a platform-level key. No observation here is flagged as an updated system app. Its com.qti package prefix and the Qualcomm-named permissions it requests point to Qualcomm Technologies (QTI) as the originator, although no Qualcomm documentation for it could be found. What it does is not publicly documented. The explanations we found online come from APK catalogues and user forums rather than from Qualcomm or a device maker, so they are not repeated here. The observed evidence is its permission set: INTERNET, ACCESS_NETWORK_STATE, ACCESS_WIFI_STATE, RECEIVE_BOOT_COMPLETED and the privileged INTERACT_ACROSS_USERS, plus two permissions in its own com.qti.qcc namespace (QCCUI and VENDOR_QCC) and permissions named for other Qualcomm packages: com.qualcomm.qti.qccauthmgr (QCCAUTHMGR), com.qualcomm.qti.qdma (QDMA), and two in a com.qualcomm.qti.smq namespace, one of them named for a "feedback" provider. Requesting permissions named for those packages suggests it interacts with them, and this site does record com.qualcomm.qti.qccauthmgr (label "QCC-AUTHMGR") and com.qualcomm.qti.qdma (label "QDMA") on a small number of devices. A permission's name is a naming convention, though, not proof of which package declares it, and this site aggregates permissions across observations rather than per build, so which builds request which permissions cannot be established. The set is consistent with a networked vendor service that coordinates with other Qualcomm components, but its purpose is unconfirmed. Version note: in our sample it is recorded on devices running API 33 to 36 (Android 13 to 16), and the oldest and newest versions this site records are the same string, QCC14.2-20230818-959503a. Whether it ships on older releases, or whether its role has changed between Android releases, could not be sourced from the sample or from any publication. For Android Enterprise, EMM and kiosk use, no enrolment or management role is identified in the sources cited here. It requests INTERNET, so it may appear in audits of preinstalled software with network access; what, if anything, it sends and where could not be established. With its function undocumented and the same package shipped by many makers, the effect of disabling it cannot be predicted, so no disable rating is given here. Test on a single device before acting on it across a fleet.

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.

8
signing certs
OEM-forked / varies
11
permissions
largest set observed
1.1 MB – 1.3 MB
APK size
33 – 37
target SDK
QCC14.2-20230818-959503a
versions observed
14
device profiles
Declared permissions (11)

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.

PermissionDescription
ACCESS_NETWORK_STATE Allows the app to view information about network connections such as which networks exist and are connected.
ACCESS_WIFI_STATE Allows the app to view information about Wi-Fi networking, such as whether Wi-Fi is enabled and name of connected Wi-Fi devices.
INTERACT_ACROSS_USERS Signature or privileged system permission.
INTERNET Allows the app to create network sockets and use custom network protocols. The browser and other applications provide means to send data to the internet, so this permission is not required to send data to the internet.
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.
com.qti.qcc.permission.QCCUI -
com.qti.qcc.permission.VENDOR_QCC -
com.qualcomm.qti.qccauthmgr.permission.QCCAUTHMGR -
com.qualcomm.qti.qdma.permission.QDMA -
com.qualcomm.qti.smq.feedback.providers.write -
com.qualcomm.qti.smq.qcc.permission.QCCTRUI -

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.

Disable for the current user
adb shell pm disable-user --user 0 com.qti.qcc
Remove for the current user - a per-user uninstall; the APK stays on /system, so Restore re-adds it (-k keeps app data)
adb shell pm uninstall -k --user 0 com.qti.qcc
Re-enable
adb shell pm enable com.qti.qcc
Restore (re-install for the current user)
adb shell pm install-existing com.qti.qcc

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.

OEMModelAndroidProvenanceObservationsLast seen
Crosscall Stellar-X5 Android 15 OEM Crosscall 2 9 Nov 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 FP5 Android 15 OEM Fairphone 1 4 Aug 2026
HONOR LLY-LX3 Android 14 - 1 28 Jun 2025
Isafemobile IS540 Android 14 OEM isafemobile 3 3 Oct 2026
Lenovo TB352FU Android 15 OEM LENOVO 1 19 Oct 2026
Motorola moto g85 5G Android 14 - 1 21 Aug 2025
Motorola motorola edge 50 fusion Android 15 OEM Motorola 12 9 Jun 2026
Motorola motorola edge 50 fusion Android 16 OEM Motorola 2 1 Jul 2026
Motorola ThinkPhone by motorola Android 14 - 1 26 Sep 2025
Motorola ThinkPhone by motorola Android 15 - 1 11 Oct 2025
Nothing A063 Android 15 OEM Nothing 1 10 Nov 2026
OnePlus CPH2465 Android 14 - 1 17 Jun 2025
OnePlus CPH2653 Android 16 - 1 24 Nov 2025
OnePlus KB2005 Android 14 - 1 17 Sep 2025
Samsung SM-A057G Android 15 OEM Samsung 1 8 Aug 2026
Samsung SM-F721B Android 15 - 1 9 Jul 2025
Samsung SM-F971B Android 17 OEM Samsung 3 10 Nov 2026
Samsung SM-G766B Android 15 - 1 17 Oct 2025
Samsung SM-G766B Android 16 OEM Samsung 1 5 Sep 2026
Samsung SM-S921U Android 15 - 1 19 Jun 2025
Samsung SM-S928B Android 16 OEM Samsung 2 12 Jun 2026
Samsung SM-S928U1 Android 15 - 1 12 Sep 2025
Samsung SM-S931B Android 15 - 1 20 Sep 2025
Samsung SM-S931B Android 16 - 1 23 Nov 2025
Samsung SM-S936B Android 16 - 1 18 Dec 2025
Samsung SM-S937B Android 15 - 1 25 Aug 2025
Samsung SM-S938B Android 15 - 2 25 Aug 2025
Samsung SM-S948U Android 16 - 1 9 Sep 2026
Samsung SM-X716B Android 15 - 1 27 Jun 2025
Samsung SM-X910 Android 14 - 1 26 Jun 2025
Samsung SM-X910 Android 15 - 1 12 Sep 2025
Samsung SM-X910 Android 16 OEM Samsung 1 24 Oct 2026
Xiaomi 23124RA7EO Android 15 - 1 17 Jun 2025
Xiaomi M2012K11AG Android 13 - 1 1 Oct 2025
Xiaomi M2101K6G Android 13 OEM Xiaomi 1 8 Mar 2026
Zebra Technologies KC50 Android 13 - 1 22 Dec 2025

Known labels

Locale-aware display names seen in the wild.

LabelLocaleSeen
QCC en-us 28
QCC en-gb 20
QCC en 12
QCC de-de 4
QCC en-mt 3
QCC nl-nl 3
QCC sv-SE 3
QCC de-DE 2
QCC es-us 2
QCC ru-ru 2
QCC 1
QCC cs-CZ 1
QCC cs-cz 1
QCC en-BD 1
QCC en-US 1
QCC en-bd 1
QCC en-nl 1
QCC en-pk 1
QCC es-US 1
QCC es-es 1
QCC it-it 1
QCC pl-PL 1
QCC pl-pl 1
QCC sv-se 1