Atmo Engine is an open-source Android live wallpaper studio inspired by the distinctive Atmosphere transition in Nothing OS. It offers optional lock-screen-to-home-screen transitions or continuously applied effects, accurate previews, flexible image fitting, and wallpaper playlists without uploading your images.
Atmo Engine is available from Google Play Store, F-Droid and Orion Store.
Current Testing Status: This application has currently been tested exclusively on the Samsung Galaxy S25 Ultra and Nothing Phone 1.
While it may work on other Android devices running Android 13+ (API 33+), behavior on different manufacturersâ skins (FuntouchOS, OxygenOS, etc.) is not guaranteed.
Follow these steps to set up the effect properly on your device.
The fastest way to apply a wallpaper. Instead of opening the app and browsing for a file, you can send an image straight to Atmo Engine from anywhere:
Open the app and choose your desired atmosphere style from the selection screen:
For Atmosphere or Atmosphere Reverse, enable Add glass effect while setting the image or from Fine tuning â Effect. The Fine Tune screen also exposes the rib count, rib thickness, and Background only subject isolation while Glass is enabled. With transitions enabled, the animation remains an Atmosphere transition: Atmosphere moves from the glass-treated image into its ambient state, while Atmosphere Reverse finishes on the glass-treated image. With transitions disabled, Atmo holds the fully atmospheric effect state on the selected screen or screens, while any screen assigned the original remains genuinely unchanged.
Canvas Sketch, Glass Effect, Atmosphere with Glass, and Halftone Print share the same on-device subject model. Canvas Sketch can use Subject segmentation to anchor its sketch to a prominent person, character, animal, or object. Glass and Halftone provide Background only, which keeps the detected foreground subject clear while applying the selected effect behind it. Model delivery depends on the app distribution:
If Canvas Sketch cannot find a confident foreground subject, it falls back to sketching the complete wallpaper. A background-only effect waits for a usable mask instead of applying across an unprotected subject. Wallpaper image contents and generated masks never leave the device. Atmo Engine does not request the INTERNET or ACCESS_NETWORK_STATE permission. In the Google Play build, Google Play services may use its own network access only when the user requests the optional model download.
Every effect can draw a clock into the wallpaper itself (Advanced Settings â Clock; single-image mode only, because in playlist and theme modes the image changes underneath it). Turn on Show clock on wallpaper, then open Choose style, position & size for a live preview of the clock on your wallpaper. A box is drawn around it: drag inside the box to move the clock, pinch with two fingers anywhere to make it larger or smaller, or pull a corner or edge to reshape it. A centre guide lights up when it is exactly centred. There are no size sliders â the box is the size, and it always stays on screen, clear of the edge where the system back gesture lives. The settings sit in a compact panel with Style, Colour, Adjust and More tabs; tap its handle to fold it down, or tap the photo to hide everything and judge the result. The clock is also always shown in the wallpaper pickerâs preview, whichever screen it is set to appear on.
Hide the system clock: the wallpaper clock looks best when your phoneâs own lock-screen clock is hidden, so you donât see two. Tap the â next to the Clock heading for instructions matched to your deviceâs brand and Android version (Samsung, Google Pixel, Nothing, OnePlus/OPPO/realme, Xiaomi/Redmi/POCO, Motorola), or a suggested web search for other brands. The device is identified from its build information, with no permissions. These methods may not work on every device or software version, so check for your own model.
Six faces, in three kinds, each offered as one row or stacked:
A stacked glass face puts the hours above the minutes, which goes much larger on a phone, with the separatorâs two dots turned on their side in the gap between them. Glass in one row is the default.
Colour (on the glass faces, Glass tint) offers a palette, a colour wheel, and an eyedropper that samples the wallpaper itself. Auto follows the image. The Adaptive faces add an Adaptive colour: a light gradient in the colour of the whole wallpaper, a little deeper at the top and paler further down. The shade depends on how far down a stroke is, so every digit shows the same shade at the same length, and at arrival the digits fade from a uniform muted shade into the gradient. Auto and Adaptive also follow the effect as it changes the wallpaper, for example going grey while Color Fill shows the image in black and white.
The glass digits are stored as distance fields rather than as pictures of glyphs, and the Adaptive digits are generated from their strokes, so the wallpaper rebuilds the outlines at whatever size you set â the clock is sharp at any size, and so is the date beside it.
Back in Advanced Settings:
After selecting an effect, you will be prompted to choose your wallpaper mode:
Single Image: Standard mode. Pick one image, crop it, and apply.
Multiple Images (Playlist): Select multiple images from your gallery to create a wallpaper playlist. Apply it directly or adjust and crop each image first. Once finished, Atmo rotates through the collection using your selected interval.
Theme Playlists: Build separate Light and Dark playlists with one or more wallpapers in each. Atmo switches to the matching collection when the system theme changes, then rotates within that collection using your selected interval.
Edit Existing Playlist: If you already have a standard or theme-based playlist running, this option loads your saved wallpapers (including their exact zoom and crop settings). You can remove images, add new ones, or tweak existing crops without starting over. The playlist editor also allows you to define a default crop setting for newly added images.
Saved Playlists: Every playlist you apply is saved automatically, so switching to a single image or to theme playlists no longer discards it. Open Saved playlists to switch back to, rename, or delete any of them. Tap the pencil in the playlist editor to name a playlist.
Playlist from Folder: Pick one or more folders in Androidâs own folder picker; their images become the playlist, and the playlist stays in sync with them: images you add are added and images you delete are removed, whenever the screen turns off and whenever you open Atmo Engine. If the image on screen is deleted, it is replaced at the next screen-off. A folder playlist is never emptied by a sync, so it keeps its images if its folders become unreadable (for example, an unmounted SD card, or a folder that was renamed or moved; pick it again to resume). No permission is needed: picking a folder gives Atmo Engine read access to that folder alone, so it works in every build. Only images directly inside a picked folder are used, not its subfolders. Android doesnât allow picking the root of the storage or of Download.
Please follow these simple steps to apply the wallpaper:
Open Fine tuning â Timing and use Animate transitions to choose how the wallpaper behaves:
When transitions are off, Keep effect applied on controls what the same live-wallpaper service renders:
These choices do not install a static wallpaper and do not move Atmo to only one destination. Atmo remains the live wallpaper on both screens; only the rendered state changes.
Disabling transitions does not disable other live-wallpaper features. Playlists and theme playlists continue rotating, Fine Tune controls remain available, Background only subject isolation continues working, and wallpaper scrolling remains active where the launcher supports it.
Fine tuning â Timing â When the screen turns on adds an animation as the lock screen arrives, whether the phone wakes from off or from the always-on display. It is separate from the unlock transition and works with transitions on or off. Every style has its own settings, and Length (50â1000 ms, default 250 ms) applies to all of them. The wake is timed on the displayâs own frames rather than Androidâs animation scale, so it plays at the length you set even on ROMs that lower or turn off animations. It starts when the screen turns on, so it still plays on phones that keep the wallpaper visible while the screen is off.
Zoom moves only the photo, through the same zoom every renderer already uses. Every other style is drawn over the finished frame, clock included, by one post pass shared by every effect on both Vulkan and OpenGL ES.
Atmo Engine uses Jetpack Compose and Material 3 throughout the setup flow. Material Expressive styling follows the deviceâs system color palette when enabled, while the appearance panel also supports fixed colors, System/Light/Dark modes, and an optional pitch-black dark background.
Effect cards, the active-wallpaper dashboard, crop screens, and playlist cards use in-process previews matched to the live effect settings and selected graphics API. This lets you inspect the selected wallpaper and effect behavior before applying it through Androidâs live wallpaper screen. Controls use short, finite, meaning-aware motion: for example, Settings rotates, Help tilts, and Back nudges in its travel direction. Motion and related haptics follow the existing Material Expressive preference and stop immediately when expressive motion is disabled.
Every effect and reverse variant can use a native Vulkan renderer for both in-app previews and the live wallpaper when the device and installed driver support it. Fine tuning > Display > Graphics API provides three app-local choices:
The saved choice is global. In-app effect previews recreate immediately with the new backend, and an already-running live wallpaper safely replaces its active render host without losing the current effect state, surface state, scrolling position, or playlist image. At runtime, Atmo negotiates the highest common core API exposed by the Android Vulkan loader and a render-capable physical device, from Vulkan 1.4 down through 1.1.
Atmo does not use Shizuku, change Androidâs global graphics settings, or restart other apps. The wallpaper service probes Vulkan inside its own process and switches a failing effect back to its equivalent OpenGL ES renderer if native setup, preprocessing, texture upload, or presentation fails. That effect remains on OpenGL ES for the current device and app version so reopening Androidâs wallpaper preview cannot enter a crash loop; a failure in one effect does not disable Vulkan for the others. In-app previews use the same source image, progress, and fine-tune state, but a Vulkan failure falls back locally for that preview without changing the live-wallpaper runtime status. The animated renderer footer at the bottom of the main screen reports Vulkan and its negotiated version only after the wallpaper has successfully presented a Vulkan frame. During initialization it makes no active claim, and once OpenGL ES is genuinely active it identifies that backend instead.
Take full control of the animation and look. You can now tweak the following settings dynamically:
Fine tuning is kept when you change only the image or playlist under the same effect, including the clockâs style and settings. Applying a different effect starts fresh from that effectâs defaults.
0 renders the original continuous tones instead of dots.(Available when using Playlist or Theme Playlists mode)
When an Atmo wallpaper is active, tap the Atmo Engine title seven times to open the device-specific palette diagnostics screen. It compares Atmoâs locally extracted colors, Androidâs Wallpaper API colors, and the current system color resources. The Force Apply test is available only while Sync System Colors is enabled. Diagnostic values and engine traces remain on the device.
Iâve made a Telegram group for discussing issues and feature suggestions. You can join it using this link.
This project is built using Kotlin, C++17, the Android NDK, and Gradle. The project pins NDK 29.0.14206865; Android Studio or Gradle can install that accepted SDK component automatically. Vulkan GLSL sources live under app/src/main/shaders, while the packaged SPIR-V binaries for all effect families live under app/src/main/assets/shaders/vulkan (these are generated during the build process to keep the repo clean of binary files).
Atmo Engine keeps one shared codebase and combines two flavor dimensions:
All artifacts in the table below use version name 7.4.6. The version code carries the API tier in its leading digit and the version name in the rest, so every flavor of one release shares a name while Play still sees a higher code for the build with the higher minimum.
| Flavor | Minimum Android | Target SDK | Version code | Intended release |
|---|---|---|---|---|
v33Play |
Android 13 / API 33 | API 33 | 300746 |
ML Kit APK |
v33Fdroid |
Android 13 / API 33 | API 33 | 300746 |
FOSS APK for F-Droid |
v35Play |
Android 15 / API 35 | API 36 | 400746 |
Google Play ML Kit AAB |
v36Play |
Android 16 / API 36 | API 36 | 500746 |
ML Kit APK |
v36Fdroid |
Android 16 / API 36 | API 36 | 500746 |
FOSS APK |
The play source set contains only the ML Kit implementation and explicit model-download controller. The fdroid source set contains only U2NetP, its model files, and the source-built FOSS LiteRT runtime. UI, effects, playlists, palette behavior, and settings remain shared in main. No build requests photo access: folder playlists use the system folder picker. Model and runtime provenance is recorded in THIRD_PARTY_NOTICES.md.
Betas are built from develop and each is published as its own pre-release, titled Beta <build> (<version>) and tagged beta-<build>(<version>), for example beta-108(7.3.7). Their APKs are named <version>-beta.<build> and use a version code one below that versionâs stable code, so the stable release always installs over them. A beta tag points at an empty commit dated 2000-01-01 rather than at the appâs source: F-Droid builds the highest version it finds in the 5 newest tags (ordered by commit date), so it never picks up a beta, and beta tags never crowd a stable tag out of those 5. Only stable releases from master get a version tag (v<version>). After a stable release, raise the version on develop before the next beta, so its betas install over the new stable.
Stable and beta release workflows produce exactly five artifacts: Android 16+ ML Kit and FOSS APKs, Android 13+ ML Kit and FOSS APKs, and an Android 15+ ML Kit AAB for Google Play. None may declare READ_MEDIA_IMAGES; CI fails if any does. CI installs the pinned NDK and inspects every archive before signing: the Vulkan library for all four ABIs and every effectâs SPIR-V pair must be present, ML Kit artifacts must not contain the U2NetP model or LiteRT native runtime, both FOSS APKs must contain them, and each ML Kit APK must remain smaller than its matching FOSS APK and below 10 MiB.
./gradlew assembleV33PlayRelease
./gradlew assembleV33FdroidRelease
./gradlew bundleV35PlayRelease
./gradlew assembleV36PlayRelease
./gradlew assembleV36FdroidRelease
Release signing keys are intentionally not stored in the repository. Configure your Play upload key locally before uploading either AAB; F-Droid builds and signs its own APK.
F-Droid should select both v33 and fdroid in its build metadata.
git clone https://github.com/saad-khan-rind/NOSAtmosphereEffect.git
Saad Ullah Khan đ Passau, Germany đ§ khansaad45678900@gmail.com đ LinkedIn đť GitHub đ Download Resume đ Portfolio
This project is open-source and available under the MIT License. Bundled third-party components retain their respective open-source licenses; see THIRD_PARTY_NOTICES.md.
The privacy policy is this.
âď¸ Feel free to fork, star, and use this code!