Per-OEM matrix
Two things a phone's maker can do to get in Zenith's way: kill it in the background — so comets (your notifications, drifting across the sky) stop and the quick ring bubble vanishes — and hide the switches that grant Zenith its permissions. The permissions are the same on every Android phone; only the menu names differ. This page lists what to grant, then where to look by brand.
Be honest with yourself about one thing: keeping an app alive in the background is your phone's job, not something Zenith can force. Where a step below names an exact menu, treat it as a well-known pointer — your phone's version may word it differently.
What every phone needs
Each of these is optional; Zenith runs without any of them. Turn on the ones whose features you want. Use the in-app buttons where they exist — they jump you straight to the right system screen.
| Goal | What to grant | Where you grant it |
|---|---|---|
| Zenith is your home screen | Default Home app = Zenith | Your phone's default-apps / home settings |
| Gesture actions (lock, notification shade, recents, quick tiles, screenshot, power menu) | The "Zenith actions" accessibility service | Your phone's accessibility screen — the "enable zenith actions →" button opens it |
| Comets (notifications on the sky) | Notification access for Zenith | Your phone's "notification access" screen — the "enable comet feed →" button opens it |
| The quick ring over other apps | "Display over other apps" | Your phone's overlay screen — the "✦ quick ring" toggle opens it when needed |
The three system screens above exist on every Android phone. What varies is the extra battery and autostart controls below, which can quietly undo those grants after a reboot.
By brand
For each brand: keep it running covers the background-kill fix; the permission grants are the standard screens in the table above unless noted.
Pixel (and stock / Android One)
Stock Android rarely kills the home app. If you use comets or the quick ring, set Zenith's battery use to unrestricted. The accessibility, notification-access, and "display over other apps" screens are all in the standard Settings; the in-app buttons take you there.
Samsung (One UI)
Samsung's "sleeping apps" and "deep sleeping apps" lists can suspend Zenith. Add Zenith to the never-sleeping list, keep it out of "put unused apps to sleep", and set its battery usage to unrestricted.
Xiaomi / Redmi / POCO (MIUI / HyperOS)
Among the most aggressive at killing background apps. Turn on "autostart" for Zenith in the Security app, and set its battery saver to no restrictions. On these phones the overlay and notification-access switches sometimes live inside the Security app as well as in the standard permission screens.
OnePlus / Oppo / Realme (OxygenOS / ColorOS / Realme UI)
Enable "auto-launch" (allow auto start) for Zenith, and turn off "sleep standby optimization" — or set Zenith's battery mode to don't-optimize / allow background activity.
Huawei / Honor (EMUI / MagicOS)
In the phone's battery "app launch" list, switch Zenith from automatic to manage manually, then allow auto-launch, secondary launch, and run in background. Huawei phones without Google services still expose the accessibility and notification-access screens.
Motorola
Close to stock. Set Zenith's battery to unrestricted, and check Moto's own background-limit setting if your model has one.
Others (Vivo/iQOO, Asus, Nothing, Sony, Tecno/Infinix, and more)
Look for a battery setting named background activity, autostart, or high background usage and allow Zenith; set battery optimization to don't-optimize. The three permission screens (accessibility, notification access, display over other apps) are standard Android — reach them fastest with the in-app buttons.
If it still gets killed
Re-check the grants after a reboot, then work through Zenith gets killed / notifications die after reboot.
See also. Zenith gets killed / notifications die after reboot · Set-default won't stick / getting back to default · The permissions gestures need, and why · Privacy & permissions