com.qualcomm.qti.remoteSimlockAuth 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 two copies of Qualcomm's source for it in vendor trees published on GitHub by third parties: an older copy whose cited source files carry Qualcomm copyright dates of 2017 and 2018, and a newer copy built with an Android.bp file. It describes those copies; what the builds recorded here contain could not be sourced. In both copies the package holds no code. Its manifest has an empty application element and does one thing: it defines the permission com.qualcomm.qti.permission.REMOTE_SIMLOCK_AUTH at protection level signatureOrSystem. The build file describes the module, which it names remoteSimLockAuthentication, as "the xml package for checking trusted application", and it carries one resource, an allow-list file of package names and SHA-256 signing certificate hashes. That file's own comment says "Only if EnableAuth is true service checks for signature"; in both copies EnableAuth is false and the list holds one entry, com.qualcomm.qti.uimremotesimlocktest. The service that comment refers to is not in this package. The client library built from the same directory binds to a service named RemoteSimLockService in a different package, com.qualcomm.qti.uim, documented separately on this site. That library's interface file says it "provides the APIs for remote simlock": sending a lock or unlock blob to what it calls the SIMLock engine, reading the current status (locked, temporary unlock or permanent unlock), and starting or stopping a timer that unlocks the device for a set time "to download the blob". Both build files use the platform certificate and install the package on the product partition. 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, Motorola, Nothing, OnePlus, Xiaomi and Zebra Technologies. Where this site holds signer data, which is 6 of those 11 makes (Crosscall, Fairphone, HMD Global, Motorola, Nothing and Xiaomi), each copy is signed by that maker's OEM key, a key that also signs the Android framework, a platform-level key. No permission requests are recorded here for it, which matches the cited manifests: they define a permission and request none. For Android Enterprise, EMM and kiosk use no enrolment, policy or management role for it is identified in the sources cited here. The cited copies tie it to a remote SIM lock arrangement. Whether any device recorded here uses that arrangement, and what stops working if the package is disabled, could not be sourced, so the rating below is caution and any change should be tested on one device with a SIM in use first. Version note: the two copies differ little. The older manifest targets SDK 28 and the newer one targets SDK 33; the permission, the allow-list and its EnableAuth value are the same in both. The older makefile skips the package on targets built without telephony and on low-RAM targets. The newer tree also carries a file, with Qualcomm copyright dates of 2021 and 2024, whose comment says it "is used by the framework to determine the list of applications that need to be disabled for modem-less targets"; it lists this package at /product/app/remoteSimLockAuthentication. It is recorded here on devices between API 28 and 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 which copy, if either, a given recorded build matches.

• RemoteSimlock AndroidManifest.xml - Sushrut1101/android_vendor_qcom_proprietary (GitHub) →
• RemoteSimlock Android.mk - Sushrut1101/android_vendor_qcom_proprietary (GitHub) →
• RemoteSimlock applist.xml - Sushrut1101/android_vendor_qcom_proprietary (GitHub) →
• IUimRemoteSimlockService.aidl - Sushrut1101/android_vendor_qcom_proprietary (GitHub) →
• IUimRemoteSimlockServiceCallback.aidl - Sushrut1101/android_vendor_qcom_proprietary (GitHub) →
• RemoteSimlockManager.java - Sushrut1101/android_vendor_qcom_proprietary (GitHub) →
• RemoteSimlock AndroidManifest.xml, newer copy - aospa-op13/proprietary (GitHub) →
• RemoteSimlock Android.bp, newer copy - aospa-op13/proprietary (GitHub) →
• RemoteSimlock applist.xml, newer copy - aospa-op13/proprietary (GitHub) →
• telephony_packages.xml, newer copy - aospa-op13/proprietary (GitHub) →
• Package provenance for com.qualcomm.qti.remoteSimlockAuth - Android System App Database →

• Re-signed by each device maker with its own platform key - 7 different certificates appear across 6 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.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.