Skip to content

Behind the scenes

How AuraGlow Lights the Pixel HiLight Ring for Any App

By the llcloud team 6 min read

Quick answer

AuraGlow lights the Pixel 11 Pro HiLight ring for any app by pairing with the phone's own Wireless debugging and starting a small helper that runs with the developer tools' permissions, the only ones Android lets reach the ring. The app reads notifications and sends the helper colors and timings. It needs USB debugging left on to survive Wi-Fi changes and cannot run with debugging fully off.

The HiLight ring on the Pixel 11 Pro, Pro XL and Pro Fold is eight LEDs around the camera flash. Google uses it for favourite contacts and Gemini. AuraGlow lights it for any app you pick. People often ask how that is possible when Google's own settings stop where they do, and why the setup involves Developer options. Here is how it works, in plain terms, and where its limits are.

Why can't an ordinary app light the ring?

Android puts every light on the phone behind one permission, and only system apps and Android's own tools hold it. An app installed from a store cannot ask for it. It cannot be granted with a command either, which rules out the usual tricks.

That leaves one identity that can reach the ring: the "shell" user that Android's developer tools run as. It is the same identity a developer gets when they plug a phone into a computer and type commands. So the question for us was never how to hack the lights. It was how to borrow that identity safely, on the phone, without asking anyone to own a computer.

How does AuraGlow get there without a computer?

Wireless debugging lets Android's developer tools accept a connection over Wi-Fi. That connection can come from the phone itself. AuraGlow pairs with it once, the same way a computer would, using the six-digit code Settings shows.

Pairing had one awkward detail. Settings hides its pairing code the moment you leave the screen, so no screen inside our app could ever read it. The answer was a notification with a reply field. You type the code into AuraGlow's notification while the Settings screen stays open, and the pairing completes in the background. Our guide to setting up HiLight without a computer walks through it step by step.

Once paired, AuraGlow uses that connection for one thing: to start a small helper we call the renderer. The renderer is part of AuraGlow's own app package, launched as the shell user, so it holds the permission the app cannot. The app and the renderer talk over a private socket on the phone.

Who does what: the app or the renderer?

The split is deliberate. The app does everything that involves your data. The renderer does everything that touches the hardware, and nothing else.

The AuraGlow app The renderer
Reads your notifications ✓ ✗
Knows your apps, colors and contacts ✓ ✗
Talks to the lights hardware ✗ ✓
Receives Notifications from Android Colors and timings only
Network access Anonymous stats and crash reports ✗ None

When a message arrives, the app decides what should glow. It looks up the app's color, the person's color if you set one with Pro, the pattern and your rules like Do Not Disturb or face-down only. Then it sends the renderer a description of the light. The renderer never sees who wrote or what they said.

For the per-contact part, AuraGlow reads the sender from the notification itself and never asks for your contacts. How well that works depends on what each messaging app shares, which is why it is marked BETA. Our guide to HiLight colors per app and per contact explains the details.

How does the ring stay safe?

Every protection sits inside the renderer, below any screen or setting, so nothing in the app can switch it off. HiLight was designed for occasional glows. A notification light asks far more of it, so we set hard limits:

  • Any one alert is capped at 60 seconds. A light that is still waiting then carries on in its calmer standing pattern until the notification is cleared.
  • Once the ring has been lit for half of any ten-minute window, it rests.
  • Long, steady lights taper in brightness.
  • When the ring should be dark, the renderer hands it back to Android. That is also what lets Google's own call and Gemini glows keep working beside AuraGlow.

Android can play some light patterns itself, as hardware effects, so the renderer does not have to wake for every frame. We use that where a pattern fits, with one rule we never bend: no effect is open-ended. Each one is a lease of whole loops that ends by itself. Android stops the renderer routinely, on a Wi-Fi change or a restart, and an endless effect would leave the ring lit at full brightness with nobody left to stop it. With leases, the worst case is a light that ends on time.

We have also seen LEDs stay lit after Android reported them off. So turning the ring off is never a single write. The renderer writes black, waits, writes it again through fresh sessions, and only then lets go.

Why does the setup ask you to keep USB debugging on?

Because the renderer lives inside Android's developer tools, it lives and dies with them. Two Android behaviours matter here, and they are Android's, not ours.

First, Android switches Wireless debugging off whenever Wi-Fi changes and after every restart. Second, when both Wireless debugging and USB debugging are off, Android stops its developer tools entirely, and everything they started goes with them, the renderer included.

So USB debugging is the switch that keeps the tools alive through a Wi-Fi change. It needs no cable. It only has to stay on. We looked hard for another way and there is none: with debugging fully off, nothing outside the system can reach the ring.

What happens after a restart?

A restart always stops the renderer. AuraGlow handles the common case by itself. Each time it starts, the renderer grants the app permission to change secure settings, a grant Android allows its developer tools to give. From then on, after a reboot, AuraGlow can switch Wireless debugging back on and start a new renderer, usually before your first notification.

That power comes with strict rules. AuraGlow only does it on Wi-Fi, at most once per connection, never when Developer options look switched off, and never on a network where you turned Wireless debugging off yourself. If Android refuses the network, AuraGlow waits longer before each new try and posts a notification instead of raising Android's dialog again and again. When it cannot restart the light, it tells you, and one tap on Wireless debugging brings it back.

Root and Shizuku are optional ways to start the same renderer. With root, the light returns after every restart with nothing to pair. AuraGlow checks for root without running the root command, so a phone without root never sees a root prompt.

What can AuraGlow not do?

These limits are facts about Android and the hardware, and we state them plainly:

  • It cannot run with USB debugging and Wireless debugging both off.
  • It needs Wi-Fi to start the renderer. Mobile data is not enough for Wireless debugging.
  • It works on the Pixel 11 Pro, Pro XL and Pro Fold on Android 17 or later. The standard Pixel 11 has no ring.
  • Per-contact colors depend on what each messaging app puts in its notifications, so a sender can sometimes light in the app's color.
  • The ring rests on schedule. On a busy stretch, a gap in the light can be one of those rests.

If the light ever stops, our HiLight troubleshooting guide lists every cause we know of. For what HiLight is in the first place, read what Pixel HiLight is. To see the feature list and setup in one place, our Pixel 11 Pro HiLight guide has both, and AuraGlow vs Google's HiLight settings shows how the two work together. Other HiLight apps use the same developer-tools door in different ways, as AuraGlow vs HiLight Studio explains.

Sources

Questions

Why can't a normal app control the HiLight ring?

Android guards its lights hardware with a permission reserved for system apps, and it cannot be granted to an app from the Play Store, even with a command. Android's own developer tools run with an identity that can use it. AuraGlow reaches the ring through those tools, which is why setup goes through Developer options and Wireless debugging.

Does AuraGlow send my notifications anywhere?

No. AuraGlow reads notifications on the phone only to choose a color and a pattern. The helper that drives the ring has no network access and receives only colors and timings, never notification text. AuraGlow sends anonymous usage stats and crash reports to fix problems, and has no ads and no account.

Why does the light stop when I turn off USB debugging?

The helper lives inside Android's developer tools. Android switches Wireless debugging off on every Wi-Fi change, and if USB debugging is off too, Android stops those tools completely and the helper with them. With USB debugging on, the tools keep running and the light survives the Wi-Fi change. No cable is needed.

Can AuraGlow damage the HiLight LEDs?

AuraGlow's limits live in the helper itself, below any screen or setting. Any one alert is capped at 60 seconds, after which a light that is still waiting carries on in its calmer standing pattern, the ring rests once it has been lit for half of any ten-minute window, and long lights taper in brightness. Every effect AuraGlow hands the hardware runs on a short lease, so even a helper that dies cannot leave the ring lit.

Keep reading