Troubleshooting ESEER Wallpapers
When a wallpaper behaves differently on a device, first check whether the cause is the project, motion input, rendering, memory or Android itself before rebuilding the scene.
Diagnose by layer: project, input, renderer, device
Avoid changing multiple controls at once. First identify whether the failure follows one project, one input mode, one renderer/editor, or the device as a whole.
| Observation | Most useful next comparison |
|---|---|
| Only one wallpaper fails | Open another wallpaper of the same type; compare asset size/effects/motion |
| All gyro scenes fail but Touch works | The issue is more likely related to motion input or the device sensor than to the scene |
| Editor preview works; installed wallpaper fails | Check what happens after locking/unlocking and after leaving/returning to the Home screen |
| Both preview and installed wallpaper are black | Test lighter assets/project and restart/reopen before re-exporting |
| Failure starts after adding one effect/layer | Disable/remove only that new component and retest |
Preview looks correct, installed wallpaper does not
Reopen the project
Confirm the editable state still renders correctly inside ESEER.
Reduce motion temporarily
Rule out edge exposure or extreme sensor response without changing layer structure.
Lock and unlock
Exercise wallpaper visibility/resume and any On Unlock layer behavior.
Apply another known-good wallpaper
Check whether the issue affects only this project or all wallpapers on the device.
Return to the failing project
If other wallpapers work correctly, inspect the layer, effect or setting that is different in this project.
Black or missing preview
- Allow a heavy live preview to finish preparing before repeatedly switching projects.
- Close and reopen the affected preview once before modifying the project.
- Compare with a project using smaller/fewer textures to check whether memory pressure is a factor.
- If a newly added image/effect correlates with the failure, remove only that component and retest.
- If both editor and installed wallpaper are black, restart ESEER/reapply the wallpaper before assuming the export itself is permanently corrupted.
Motion issues
| Symptom | Check first |
|---|---|
| Too much 3D camera movement | Advanced Camera Horizontal / Vertical or Extended Wallpaper Horizontal / Vertical strength |
| Edges visible | Edge safety/overscan or 3D layer scale/framing |
| Too jittery | Smoothing/response plus whether sensor input is the actual source |
| Pinned element drifts too much | Behavior → Pinned Horizontal / Vertical Motion, not camera FOV or layer Z |
| Pinned element changes size/position when reordering | Current Pinned behavior should use a stable reference; confirm the layer is actually Pinned and the app is up to date |
| Only Gyro behaves incorrectly | Compare Touch mode and device compatibility behavior |
For the actual motion controls, see Extended Wallpaper → Motion tuning, Advanced Camera → Motion, Camera Smoothing and Pinned Layers.
Gyroscope and device compatibility
Android vendors differ in sensor reporting, refresh behavior and background / power management. If motion behaves differently on one device, compare the editor preview with the installed wallpaper before changing the scene itself.
- Test motion again after locking and unlocking the device.
- Compare Gyro and Touch where both are available to separate sensor input from rendering or composition problems.
- Test a second, known-lightweight wallpaper when diagnosing a device-wide issue.
- If only one scene fails, inspect its edge coverage, depth / behavior and active effects before changing compatibility settings globally.
Import is blocked or fails
| Message / symptom | Meaning / next step |
|---|---|
| Only .es files are supported | Choose the original .es package rather than a renamed/other file type |
| Wallpaper already imported | The same package checksum is already registered locally |
| Created with a newer version of ESEER | Update ESEER before importing that package |
| Warning with Proceed / Cancel | The package is readable but resource risk was detected; proceed only if you accept the warning |
| Import blocked to prevent crashes | Do not retry unchanged; reduce heavy source assets and export again when possible |
| Failed to import .es wallpaper | Treat the package as invalid/malformed or unreadable and obtain/export a fresh copy |
See Import, Export and .es Files for the validation flow.
What to include in a useful report
| Information | Why it matters |
|---|---|
| Device model + Android version | Identifies vendor/OS-specific rendering and sensor differences |
| Wallpaper type | Separates Extended Wallpaper from 3D Scene rendering paths |
| Editor preview / installed wallpaper / both | Shows whether the issue is in the editor, installed wallpaper or both |
| Selected motion mode | Separates gyro/touch/input behavior |
| Steps immediately before the issue | Helps identify which recent action triggered the issue |
| Screen recording for visual issues | Shows timing, flicker, edge exposure and motion behavior |
| Crash/ANR trace when available | Provides the failing thread/call path instead of relying on visual symptoms |
Use the Support page or the ESEER community channels for app-specific reports.