Set the wallpaper across your fleet with a signed Android app, ready to deploy via your EMM.
‹The Bayton Wallpaper App Generator produces a signed Android app that does exactly one thing: set the device wallpaper and keep it set. It is built for dedicated devices, kiosks, signage, and EMM-managed fleets where the wallpaper is part of the deployment rather than a user preference.
The app has a single control - tapping the status line reapplies the wallpaper, re-cropped to the device's current orientation, should an application issue occur. Once started manually, by your DPC, or through AMAPI role activation, it checks at boot, when opened, and on a schedule. Boot and role-change applies are forced, so they restore the configured image if a user has changed it. Its single screen reports what was applied, when, and what went wrong if anything did. Each build produces a unique package name, along with an optional source zip so you can audit or reproduce the build independently.
Generated apps target API 37 (Android 17) and require API 28 (Android 9 Pie) or above to install. Devices running Android 8.1 or older are not supported.
Lower API levels are achievable - the minSdk in the generator is a safe baseline that covers every option offered. You can drop the minSdk in app/build.gradle.kts from the downloaded source and rebuild if your fleet needs it.
Test on the API level you actually deploy to. Wallpaper behaviour - particularly whether a device exposes a separate lock-screen wallpaper at all - varies between OEMs and Android releases more than most platform surfaces do.
From September 2026, Android enforces a developer verification requirement on certified Android 7+ devices: apps must be registered against a verified Google developer account (Play Console or Android Developer Console) to install on consumer devices. Enforcement begins in Brazil, Indonesia, Singapore, and Thailand, with global rollout from 2027. Managed-device deployments are exempt.
http:// address. A wallpaper fetched over plaintext can be swapped in transit, and whatever arrives is what everyone sees on every unlock. Intended for operators on an internal network without TLS.ACTION_APPLICATION_RESTRICTIONS_CHANGED only to dynamically registered receivers, never to manifest-declared ones - and an app with no long-lived component has nowhere to register one. The periodic check is what makes a managed-configuration push land on a device sitting idle in a drawer. It is a deliberate design decision, not a workaround.DISALLOW_SET_WALLPAPER user restriction, the apply is refused however the app is started. SET_WALLPAPER does not override it - only a device owner or profile owner may set the wallpaper regardless of that restriction, and a generated app is neither. The app reports the refusal on its status screen rather than failing silently, but the wallpaper will not change. Clear the restriction on any fleet where this app is expected to work.If your EMM uses the Android Management API, the wallpaper app can start in the background without anyone opening it first.
SYSTEM_HEALTH_MONITORING, where available. Each role can belong to only one app, so it cannot also be assigned to your contacts app or monitoring agent. Roles grant additional privileges; choose one appropriate to your deployment. See AMAPI application roles.role_activation reports whether background work was queued. wallpaper_status and last_applied report the wallpaper result.Android Device Policy wakes the app through its role listener. The app schedules its checks and queues a forced wallpaper apply; fetching a URL image still depends on connectivity, and a policy blocking wallpaper changes still prevents the apply.
Role-change notifications, including removal of all roles, also queue a forced apply. A managed-configuration push alone is not a role-change notification. If an updated app already has its role assigned, change the assignment in your EMM to trigger a new notification.
Leave the option disabled if your custom-DPC EMM already starts the app after installation, or opening it once manually suits your deployment. Disabled builds omit the optional SDK and role service. This is a build-time option, separate from managed configuration.
Read more in Zero-touch initiation comes to the app generators.
The generated app publishes four managed-configuration keys, so your EMM can change an installed fleet without a rebuild. Every one of them defaults to the choice you make on this form, so a device that has never received a push behaves exactly as you built it.
wallpaper_urlapply_tohome, lock or both. Moves the image between the two wallpaper slots without a rebuild.check_interval_minutesallow_httphttp:// URL is still configured makes the app refuse to fetch and report why, rather than quietly continuing over plaintext - change the URL to HTTPS in the same push.SET_WALLPAPER does not override DISALLOW_SET_WALLPAPER. Only a device owner or profile owner may set the wallpaper regardless of that restriction, and a generated app is neither - so if your EMM sets it, the apply is refused and the app says so on its status screen.configuration_status, wallpaper_status (alert on this one: it carries a policy block or a failed fetch), wallpaper_source (url or bundled, so a device silently on the fallback is visible), last_applied and apply_to. Activation-enabled builds also report role_activation: work queued or an enqueue failure, separately from the wallpaper result. A device still in Android’s stopped state reports nothing at all, because the app has never run - silence is not success.Sets the colour used for the app's single status screen and its system bars. It does not affect the wallpaper - the image is applied exactly as fetched. Accepts any CSS hex colour (#rrggbb or #rgb), and defaults to white. Text and icon contrast is computed automatically using WCAG relative luminance, so dark colours receive white foregrounds and light colours receive dark ones.
Every new build generates a unique update code returned once in the submission response. Store it securely - it is never shown again. Only a SHA-256 hash is kept server-side, so the raw code cannot be recovered or regenerated; this is the security boundary that lets it work as a one-time recovery secret.
When you need to update an existing app and must keep the same Android package name (required for EMM silent-update flows and Managed Google Play uploads beyond the first), enter the original update code in the Update code field before submitting. The service will reuse the registered package name for the new build.
If you do not have an update code, a new unique package name is assigned. You can replace the app on managed devices by uninstalling the old version first or by pushing the new package as a separate app.
Every successful build offers a Download config button next to Download source - a portable JSON file (wallpaper_config.json) capturing every form field plus the build's update_code. Use it to skip refilling the form on later rebuilds.
To re-import, click Import config at the top of the form and pick a previously-downloaded JSON. Every field populates, including radio selections and Options toggles. Icon and keystore are not in the JSON (binary / sensitive). The icon is also not stored server-side, so it will need to be provided again on subsequent builds; submit without one and the default is used.
The exported file contains your update code in plaintext, so treat it like the code itself - it's effectively a per-app one-time recovery secret. The file expires alongside the artefact (5 min after first download) so the raw code doesn't linger server-side.
REST equivalent: POST the JSON as the config_json form field on /api/build. Other form fields submitted in the same request override the imported values, so a one-off colour change or output-format swap is one extra field, not a JSON re-edit.
Upload a 512 × 512 px PNG for best results. The generator produces all required mipmap densities automatically, including an adaptive icon for Android 8.0 and above. Optionally maskable icons with safe-zone padding produce better results in launchers that apply custom shapes. A default Bayton icon is used when no icon is provided.
Neither the icon nor the bundled wallpaper is stored, and both will need to be provided on subsequent builds. The config export / import flow round-trips every form field but those two - it records that an image was bundled, not the image itself - so re-attach them manually when rebuilding from a previously exported wallpaper_config.json or against a typed update_code. Submit without an icon and the default is used.
Download links expire 5 minutes after first click and build files are purged at that point. All builds are purged after 24 hours regardless of download activity. The source download includes post-substitution Kotlin, XML, and Gradle files so you can audit exactly what was compiled or reproduce the build with your own tooling. A source rebuild matches ours byte-for-byte except the versionCode, which is intentionally derived from build time so every build outranks the last for Play and EMM update ordering - for that reason, don't push a self-built APK to the same distribution channel as ours.
The PAG server itself is versioned (semver). Every APK is stamped with the server version that produced it, plus a build timestamp. Five ways to read the stamp, ranked by ease:
<package>_<job-id>_genver-<version>.apk (e.g. org.bayton.gen.wallpaper.pa1b2c3_58036933df5a_genver-0.1.0.apk). At-a-glance lookup; lost if the file is later renamed.unzip -p <file.apk> assets/pag-build.txt returns three lines: builder: pag, version: ..., build_timestamp: .... Universal unzip tool; works after rename.strings <file.apk> | grep '^builder:' surfaces the same three lines without any extraction.adb shell dumpsys package <pkg> | grep org.bayton.pag reads the manifest meta-data tags.api/status/<id> response includes builder_version; GET api/version returns the current PAG release.Quote the version in any support ticket so the issue can be tied to the exact build of PAG that produced your artefact.