com.google.android.gmsintegration Copy

A preinstalled component that devices report under the label "Google Sample Home Screen". The name is misleading in one important way: despite sitting in the com.google.android namespace, it is not Google-signed on the devices this database has seen. Every observation of it is signed by the device maker's own key, sixteen distinct signers across seventeen device profiles, each classified as an OEM key that also signs the framework, with Zebra Technologies, Fairphone and Crosscall among them. In other words it is a Google-namespaced component that each manufacturer includes in its own platform image under its own signing key, and it turns up mostly on rugged, retail and industrial hardware rather than on consumer phones. Our record lists no declared permissions for it and no launcher entry in the sample. A preinstalled, platform-signed, resource-shaped package of this kind fits a documented Android pattern. The AOSP setup wizard support library finds a "partner" customisation package by querying for a broadcast receiver registered for the action com.android.setupwizard.action.PARTNER_CUSTOMIZATION, keeping only packages with FLAG_SYSTEM set, and taking the first match as the source of overriding resources for setup. That is the mechanism by which an OEM replaces parts of the out-of-box experience. We could not find a Google or AOSP source that names this package, so the specific claim that it is the sample partner-customisation package for GMS setup is not asserted here, only noted as the pattern it resembles. What it actually contains on a given device is not published. Version note: our sample carries builds whose version strings run from 11 to 16, on target SDKs from 27 to 36, so it has been carried across many releases rather than introduced or retired in one. The recorded package size varies enormously between devices, from roughly 46 KB to roughly 68 MB. That spread, together with the sixteen different signers, is the clearest signal that an identical package name does not mean identical contents here: treat this as a per-device component and do not assume behaviour observed on one make carries to another. We could not source a change tied to a specific Android version. For Android Enterprise, EMM and kiosk fleets we found no source making this package an enrolment, policy or compliance dependency, and it has no launcher entry in our sample. If it does supply setup customisation resources on your hardware, removing it could change what the out-of-box flow shows; we could not source whether it affects enrolment either way, and since the contents differ by manufacturer no single answer would hold across models. Treat removal as a change to test on one device of each model before rolling it out.

• Partner.java, setup wizard partner customisation lookup - Android (frameworks/opt/setupwizard) source →
• Package provenance for com.google.android.gmsintegration - Android System App Database →

• Re-signed by each device maker with its own platform key - 16 different certificates appear across 14 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.
• APK size ranges from 0.0 MB to 68.4 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.