Skip to content

Notification light

How to Set Up HiLight for Every App Without a Computer or Root

By the llcloud team 6 min read

Quick answer

AuraGlow sets up HiLight for every app entirely on the Pixel 11 Pro, Pro XL or Pro Fold. You unlock Developer options, turn on Wireless debugging over Wi-Fi and type a six-digit pairing code into an AuraGlow notification. No PC, cable or root. Afterwards keep USB debugging on, with no cable plugged in, so a Wi-Fi change does not stop the light. It cannot run with debugging fully off.

The HiLight ring on the Pixel 11 Pro only lights for favourite contacts and Gemini out of the box. Most ways to unlock it for other apps assume you have a computer with ADB installed, or a rooted phone. AuraGlow needs neither. Here is the full setup on the phone, what each switch is for, and what can turn the light off later.

Why does HiLight need developer tools at all?

Android protects the lights hardware with a permission only system apps hold, so a normal app cannot touch the ring. Android's own developer tools can, and Wireless debugging lets those tools run on the phone itself. That is the one door Android leaves open, and every third-party HiLight app goes through it in some form.

The difference is who runs the tools. Some setups ask you to plug the phone into a computer and type commands. AuraGlow pairs with the phone's own Wireless debugging and starts the light by itself, so the phone is the only device involved. Our explainer on how AuraGlow lights the HiLight ring goes into the details.

What you need before you start

Requirement Why
Pixel 11 Pro, Pro XL or Pro Fold on Android 17 The only phones with the HiLight ring
Wi-Fi Wireless debugging does not run on mobile data
Notifications allowed for AuraGlow The pairing code is typed into an AuraGlow notification
Notification access AuraGlow lights the ring when a notification arrives
No computer, cable, root or Shizuku Optional routes only

The standard Pixel 11 has no ring. If that is your phone, see notification lights on any Android phone instead.

How do I set up HiLight on the phone, step by step?

AuraGlow's onboarding walks you through each switch and waits for it, so you always know what is left. The steps are below so you can see them in advance.

1. Grant notification access

Open AuraGlow and tap Grant on the notification access screen. Android asks you to confirm. Then pick the apps you want lit. You can change them any time.

2. Unlock Developer options

  1. Open Settings > About phone.
  2. Tap Build number seven times. Android counts down, then may ask for your PIN.
  3. Developer options now appear under Settings > System > Developer options.

3. Turn on Wireless debugging

  1. Connect to Wi-Fi.
  2. Open Settings > System > Developer options and turn on Wireless debugging.
  3. Android asks whether to allow wireless debugging on this network. Tick Always allow on this network and allow it. That lets AuraGlow restart the light by itself on this Wi-Fi later.

4. Pair AuraGlow with the code

  1. In AuraGlow, tap Pair. Settings opens.
  2. Tap Pair device with pairing code. A six-digit code appears.
  3. Without leaving that screen, pull down the AuraGlow notification, tap Enter code and type the six digits.

Why a notification? Settings hides its pairing code the moment you switch to another app, so no screen inside AuraGlow could ever see it. If you swipe the notification away, AuraGlow can bring it back. A wrong code just means opening the pairing screen again for a fresh one.

5. Watch the ring light up

Once paired, AuraGlow starts the light and its setup screen confirms the light is connected. From then on, each notification from an app you picked lights the ring in that app's color.

What do I need to leave switched on?

Leave Developer options and USB debugging on. That is what keeps the light running from day to day. You do not need a cable. The switch only has to stay on.

Turn on USB debugging

Open Settings > System > Developer options and turn on USB debugging. AuraGlow shows the same tip in its settings.

Here is why it matters. Android switches Wireless debugging off whenever your Wi-Fi changes, for example when you leave home. If USB debugging is also off, Android ends its developer tools completely, and the light goes with them. With USB debugging on, they keep running and a Wi-Fi change does not touch the light.

What turns the light off

What happens Does the light stop? What to do
Wi-Fi changes, USB debugging on No Nothing
Wi-Fi changes, USB debugging off Yes Turn USB debugging on, then Wireless debugging once
Phone restarts Yes, briefly AuraGlow usually restarts it by itself
Developer options switched off, sometimes by an update Yes Tap Build number seven times again
USB debugging and Wireless debugging both off Yes Turn them back on
Battery Saver or below your battery cutoff Paused on purpose Charge or change the cutoff

There is no way to keep the light running with debugging fully off. Google's own call, message and Gemini glows do not depend on any of this and keep working either way.

What happens after a restart?

A restart stops the light, because Android turns Wireless debugging off on every boot. AuraGlow usually switches Wireless debugging back on by itself on a Wi-Fi you allowed before, and starts the light again before the first notification arrives.

It only does this on Wi-Fi, at most once per connection, and never when it sees Developer options switched off. If you switched Wireless debugging off yourself on the current network, AuraGlow leaves it off. When it cannot restart the light, it posts a notification asking you to turn Wireless debugging on once. On a network Android has never allowed for debugging, the notification takes you to the Wireless debugging screen so you can allow it.

Root and Shizuku, if you already use them

AuraGlow offers two other routes during setup. If your phone is rooted, it can start the light through your root manager, with nothing to pair, and the light returns by itself after every restart. AuraGlow never asks for root on a phone without it. If you already run Shizuku, AuraGlow can connect through it, but Shizuku needs starting again after each restart.

Which HiLight setup is the easiest?

AuraGlow's on-phone pairing is the shortest path for a stock Pixel 11 Pro.

AuraGlow, on the phone ADB from a computer Root
Needs a computer ✗ ✓ Depends on the method
Needs a cable ✗ Often Depends on the method
Keeps your phone unrooted ✓ ✓ ✗
Lights any app in its own color ✓ Depends on the app Depends on the app
Back after a restart without a computer ✓ Usually by itself ✗ ✓
Needs USB debugging left on ✓ ✓ ✗

AuraGlow asks only for notification access and permission to post its own notifications. For the free and Pro features, read our Pixel 11 Pro HiLight guide, and to give each app or person a color, see HiLight colors per app and per contact. If something stops working, our HiLight troubleshooting guide covers every case. Weighing other ring apps? Compare AuraGlow vs HiLight Studio and AuraGlow vs HiLight Plus.

Sources

Questions

Can I set up HiLight for every app without a computer?

Yes. AuraGlow does the whole setup on the phone. Android only lets its own developer tools reach the HiLight ring, and Wireless debugging is one of those tools that runs on the phone itself. You pair AuraGlow with it by typing a six-digit code into a notification. Nothing is installed on a computer and no cable is needed.

Do I need root or Shizuku to control HiLight?

No. AuraGlow works on a stock, unrooted Pixel 11 Pro through Wireless debugging. Root and Shizuku are optional routes for people who already use them. With root there is nothing to pair and the light comes back by itself after every restart. Shizuku also works, but it needs starting again after each restart.

Why does AuraGlow need Wi-Fi?

Wireless debugging only runs on a Wi-Fi network, and mobile data is not enough. AuraGlow needs it during setup and whenever it has to start the light again, such as after a restart. Once the light is running and USB debugging is on, a Wi-Fi change or losing Wi-Fi does not stop it.

Can I turn off USB debugging after setup?

You can, but the light will stop the next time your Wi-Fi changes. Android switches Wireless debugging off on every Wi-Fi change, and with USB debugging also off, Android ends the developer tools AuraGlow runs through. Leave USB debugging on. It needs no cable, and with nothing plugged in it shows no notification.

Is it safe to leave Developer options and USB debugging on?

Developer options are a standard Android menu, and USB debugging only accepts a computer you approve on screen when a cable is connected. Keep your phone locked and decline any debugging prompt you did not expect. AuraGlow's part that drives the ring has no network access and receives only colors and timings.

Keep reading