com.qti.qualcomm.datastatusnotification Copy

A Qualcomm-named system component with no label of its own: it is recorded here under its package name in each locale recorded, and has no launcher entry in any observation recorded here. No Qualcomm documentation for it was found. The description below comes from a copy of Qualcomm's source for it in a LeEco MSM8996 vendor tree published on GitHub, whose files carry a Qualcomm copyright date of 2014. It describes that copy; what current builds contain could not be sourced. In that copy it is a small service that keeps the modem informed of the device's mobile data settings. The manifest uses the phone shared user ID and the com.android.phone process, and the makefile builds the package with the platform certificate. A receiver starts the service when subscription (SIM) information is updated. The service then watches three things for each phone: the mobile data setting, the data roaming setting and the carriers (APN) database. When one changes it passes the new value to the RIL through Qualcomm's qcrilhook library: whether mobile data is enabled, whether data roaming is enabled, and the preferred or default APN and the IMS APN for the SIM's operator. A comment in the code says the values are also sent when the service starts "since modem needs to know the values at start of service". The two source files in that copy contain no code that posts a notification to the user; the notification in the name is to the modem. Although it carries a Qualcomm name, it is shipped by device makers. It is recorded here on devices from CipherLab, Crosscall, Datalogic, Elo Touch Solutions, Fairphone, HMD Global, isafemobile, Motorola, Nothing, OnePlus, Xiaomi and Zebra Technologies. Where this site holds signer data, which is 8 of those 12 makes (Fairphone, Motorola, Nothing, Xiaomi, Crosscall, Zebra Technologies, isafemobile and HMD Global), each copy is signed by that maker's OEM key, a key that also signs the Android framework, a platform-level key. The five permissions recorded here are WRITE_APN_SETTINGS, com.qualcomm.permission.USE_QCRIL_MSG_TUNNEL, READ_PHONE_STATE, READ_PRECISE_PHONE_STATE and RECEIVE_BOOT_COMPLETED; the cited manifest requests only the first two, so at least one recorded build differs from that copy. This site aggregates permissions across observations rather than per build, so which builds request them cannot be established. For Android Enterprise, EMM and kiosk use no enrolment, policy or management role for it is identified in the sources cited here. It is relevant where mobile data, roaming or APN settings matter to a deployment, because in the copy cited it is the component that tells the modem when those settings change. What the modem does with those values, and what stops working when it does not receive them, is not covered by the sources cited here, so the rating below is caution and any change should be tested on one device with a SIM in use, including roaming and APN changes where those apply. Version note: it is recorded here on devices from API 28 to API 36, and this site's roll-up reports version strings from 13 (oldest) to 16 (newest) and target SDK levels from 28 to 35. Those figures do not establish how the package has changed. The source copy cited is far older than the builds recorded here, and whether its role differs on current Android releases could not be sourced.

• DataStatusNotification AndroidManifest.xml - bcyj/android_tools_leeco_msm8996 (GitHub) →
• DataStatusNotification Android.mk - bcyj/android_tools_leeco_msm8996 (GitHub) →
• DataStatusNotificationService.java - bcyj/android_tools_leeco_msm8996 (GitHub) →
• SubInfoReceiver.java - bcyj/android_tools_leeco_msm8996 (GitHub) →
• QcRilHook.java - bcyj/android_tools_leeco_msm8996 (GitHub) →
• Package provenance for com.qti.qualcomm.datastatusnotification - Android System App Database →

• Re-signed by each device maker with its own platform key - 9 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 5 permissions: 1 runtime (user-granted), 2 signature or system-level, 1 install-time and 1 vendor or uncatalogued.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.