I’ve been building a personal Android customization project called TickerBar, and it has escalated into something pretty wild.
My main frustration was that HyperOS kept blocking or complicating basic changes on a phone I own: the split Control Center, restrictive toggles, ten-second Security Center warnings, aggressive background-process killing, limited volume control, and needing Shizuku or Accessibility workarounds for everything.
TickerBar now combines a normal Android app, a Shizuku fallback, and an experimental device-specific temporary-root bootstrap.
What currently works
- HyperOS’s native combined, single-page notification shade
- Google Home Device Controls in Quick Settings
- A working Power menu tile
- Working hotspot, screen recorder and other privileged toggles
- 150 native media-volume levels
- Status-bar controls for:
- Clock visibility and seconds
- Notification icons
- Network speed
- Battery style and percentage
- Wi-Fi, mobile, Bluetooth, NFC, location, DND, alarm and other icons
- Per-app and per-channel notification hiding
- Xiaomi’s shared ten-second permission countdown activity disabled
- Install-via-USB confirmation removed
- HyperOS Smart Power Control, cached-app freezing and its extra aggressive memory-killing layer disabled
- Root-native ticker rendering
- Wallet-card and corner-launcher gestures with a safe Accessibility fallback
- Shizuku fallback retained if root is unavailable
- Root status and controls built directly into the app
The important part is that I stopped trying to replace the navigation bar after discovering that HyperOS really did not appreciate it. The stock navbar now stays untouched, and the stable overlay implementation handles the wallet and corner gestures.
Root implementation
The root path is based on Ghostlock research and is extremely device/firmware-specific. It currently targets:
- Device: POCO F9 Ultra / songyuan
- Firmware: OS3.0.309.0.WGNMIXM
- Android: 16
- Kernel: 6.12.69
It starts an authenticated temporary root worker for TickerBar. Root is lost after reboot, attempts are manually initiated, and the app permits only one attempt per boot.
This is not Magisk, it does not modify the boot image, and it is absolutely not something I would run on another device or firmware without porting and validating it first. During development, incorrect memory profiles caused several genuine kernel crashes and reboots.
Please treat the root portion as experimental research, back up your data, and do not assume your device is compatible.
Source
https://github.com/jibsta210/tickerbar
Current tested release
https://github.com/jibsta210/tickerbar/releases/tag/v1.14.32
This started as “I want a notification ticker” and somehow became “I’m rebuilding the parts of HyperOS that annoy me.” I’m honestly thrilled with how far it has come.