com.qualcomm.location Copy

A Qualcomm vendor location component, shown on devices with the label "LocationServices". On the devices observed by this database it is signed by Qualcomm and by the OEM platform keys of Snapdragon-based makers, has no launcher icon and is not user-facing, which is consistent with it being part of the vendor location stack built into the system image rather than a separate app. Its role is assisted GNSS, better known as A-GPS: the device fetches Qualcomm's predicted satellite data so it can work out a fix in seconds instead of downloading almanac data from the satellites themselves over several minutes. That assistance service launched in 2007 as gpsOne XTRA, was renamed IZat XTRA Assistance in 2013, and more recently became the Qualcomm GNSS Assistance Service. Qualcomm does not publish per-package documentation for this component, so the identification rests on its package name, vendor label and signer together with the public record of the assistance service. In an Android Enterprise, EMM or kiosk context this is vendor platform infrastructure rather than preinstalled bloatware. A-GPS is strictly an optimisation and basic GPS can still work without it, but on Qualcomm devices this component is wired into the location stack, so treat disabling it with care: it can slow down or degrade GPS fixes. Test on a single device before applying any policy across a fleet. If your concern is the network calls to Qualcomm's assistance servers rather than positioning itself, that is a privacy or telemetry trade-off to weigh against slower and less reliable fixes. Version note: the branding has changed over time (gpsOne XTRA, then IZat, then Qualcomm GNSS Assistance Service), but this is tied to the chipset and vendor image rather than to a specific Android release.

• How A-GPS works, and whether Qualcomm is tracking you - Kaspersky →
• Package provenance for com.qualcomm.location - Android System App Database →

• Re-signed by each device maker with its own platform key - 6 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.
• Its largest observed manifest declares 30 permissions: 5 runtime (user-granted), 12 signature or system-level, 7 install-time and 6 vendor or uncatalogued.
• APK size ranges from 0.8 MB to 3.6 MB across the reporting device profiles, so the build differs substantially between them.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.