Hey everyone,
If you use custom Watch Face Format (WFF) watch faces on the Xiaomi Watch 5, you might have run into a frustrating issue: built-in complications (steps, calories, heart rate, etc.) work for a few minutes after launching the watch face, and then completely freeze.
I've seen this mentioned a few times here and there but haven't seen a fix—so I eventually let Antigravity to pull out all kinds of logs from my watch, pulled the MiWatchFace app from my watch and let multiple AI models analyze all that.
After digging deep into the system logs and MiWatchFace app decompile, (A)I figured out why it happens and built a lightweight companion app that seems to have solves it. At least so far. No root is needed, no manual steps and there is almost zero battery impact.
The Root Cause (Why it happens)
- Xiaomi's complication data sources are declared with an update period of
0, meaning they rely entirely on push events rather than platform polling.
- That push pipeline runs through a private binder to
MiHealthService.
- When a third-party WFF watch face is active, Android's cached-app freezer (
am_freeze) and standby buckets treat the MiWatchFace process as disposable cache because it has no active foreground component. Once frozen, the background updates die, and your watch face gets stuck showing stale numbers forever.
- Temporary fixes (like re-entering the watch-face editor or running ADB shell scripts) only temporarily wake up the process or grant short-lived allow-lists—they don't fix the underlying lifecycle decay.
The Solution: Mi Complication Bridge
Temporary manual fixes aren't helpful, and even though I also made myself a separate complications app for steps and calories etc. I was not able to replicate all of the MiWatchface complications. For example, movement minutes. So now I built Mi Complication Bridge.
It runs a minimal foreground service that maintains a persistent binder connection to TransmitRXService. Because a non-frozen process holds an active binding to the provider, Android's freezer refuses to freeze it, keeping the MiHealthService topic pushes flowing continuously.
- No ADB / No Root required after initial sideload.
- Self-healing watchdog: Automatically re-binds on disconnect and boots cleanly from direct boot (
LOCKED_BOOT_COMPLETED).
- Ultra-low power footprint: Event-driven architecture with virtually zero battery consumption.
Looking for Testers!
I've been running this locally on my Xiaomi Watch 5 for the past few days, and my complications have stayed live without a single freeze or manual re-selection. But I can't be 100% sure that there are some edge cases this app does not cover so if there are others who have the same issue - please feel free to test it out and report back the issues the app might not cover.
You can grab the APK and check out the source code and the initial analyze report that found the issue and potential fix on GitHub here.
Feedback and testing reports are very appreciated!