com.google.android.apps.wallpaper Copy

Google's variant of the same "Wallpaper and style" app family documented above under com.android.wallpaper. The link is visible in AOSP itself: the WallpaperPicker2 and ThemePicker manifests declare package="com.google.android.apps.wallpaper", and the AOSP build renames the result to com.android.wallpaper through package_name in Android.bp, so this is the name the upstream source carries before that rename. In our sample this entry is Google-signed, whereas com.android.wallpaper is signed by OEM platform keys. We could not source how closely Google's shipping build tracks the AOSP one, so treat the two as the same app family rather than as byte-for-byte the same application. Version note: as with the AOSP build, the personalisation options behind it follow the Material You work introduced in Android 12, so the feature set differs by platform version. Which of the two package names a device carries depends on whether the vendor ships Google's build or its own AOSP build, so check your fleet before writing either name into a policy. For Android Enterprise, EMM and kiosk use the guidance is the same: use the Android Management API setWallpaperDisabled policy to stop users changing the wallpaper rather than disabling the app, since removing it takes the wallpaper and personalisation entry points out of Settings and the home screen.

• WallpaperPicker2 AndroidManifest.xml - Android Open Source Project →
• ThemePicker Android.bp - Android Open Source Project →
• Material You design - Android Open Source Project →
• Policy resource (setWallpaperDisabled) - Android Management API →
• Package provenance for com.google.android.apps.wallpaper - Android System App Database →

• Signed by Google's own signing key (the same key Google uses across devices), so it is a Google-provided preinstall that updates independently of the system image, though 2 different Google signing keys appear across the fleet. This certificate spans 10 device makes - the hallmark of a globally distributed Google key.
• Its largest observed manifest declares 33 permissions: 2 runtime (user-granted), 9 signature or system-level, 9 install-time and 13 vendor or uncatalogued.
• APK size ranges from 6.2 MB to 17.4 MB across the reporting device profiles, so the build differs substantially between them.
• Reported as an updated system app in 1 of 75 observations - a newer build was installed over the one in the system image. Multiple observations can come from the same device profile.