hilight-studio

Download the signed APK from the latest GitHub prerelease, connect the Pixel with USB debugging enabled, then run: ```bash adb install -r HiLight-Studio-v1.0.10-experimental-signed.apk ``` If you have an older version installed, uninstall it first: ```bash adb uninstall com.hilight.studio adb install HiLight-Studio-v1.0.10-experimental-signed.apk ``` After installation, grant Notification access and Usage access in the system settings, then start the app.

The renderer enforces several limits to protect the LEDs: - Ambient effects stop after 30 seconds (configurable up to 5 minutes). - Notification effects are limited to 1 minute. - Privacy activity rules (microphone/camera) run only while the sensor is active, default 10 on/10 off with a 1 minute maximum per continuous use. - Sustained brightness tapers after 10 seconds of continuous light. - The array can be active for at most half of any 10‑minute window. - Battery Saver, low‑battery, quiet‑hours, screen‑state, and Do Not Disturb rules can pause output. These limits apply even if you edit app rules manually.

The app automatically detects root; if your device is rooted, open HiLight Studio and approve the one‑time root request – no further setup is needed. If not rooted, choose Shizuku or ADB: **Shizuku** 1. Install Shizuku v12+ and start it via Wireless debugging. 2. In HiLight Studio go to **Setup → Request access**, approve the prompt. 3. Restart Shizuku after each reboot and reopen the app. **ADB** 1. Enable Developer options → USB debugging on the phone. 2. Install HiLight Studio once to create its state files. 3. In **Setup → ADB**, copy the combined command for your shell (or run `./scripts/start-helper.sh` on macOS/Linux). 4. The helper starts in the background, runs a black‑only cleanup, and logs to `/data/local/tmp/hilight.log`. Verify with `adb shell cat /data/local/tmp/hilight.log` – you should see "connected: 8 HiLight LEDs". The renderer must be restarted after every reboot; the helper script handles this automatically.

To capture diagnostics: 1. In HiLight Studio go to **Setup → Copy LED diagnostics** – this copies a privacy‑safe report containing renderer identity, transport, session lifecycle, and cleanup outcome (no notification content, package names, or personal data). 2. If an LED remains lit after an animation, turn HiLight off, wait for the automatic three‑pass cleanup, then tap **Retry LED cleanup** (sends only black states). 3. Attach the copied diagnostics, the Pixel model, Android build, transport, pattern, and reproduction count to a bug report. 4. For a quick check of session ownership, run: ```bash adb shell dumpsys lights | grep -c "Session token=" ``` Expect `0` when dark and `1` while HiLight is visibly driving the LEDs. If ownership is wrong, re‑run the current ADB helper command from **Setup → ADB**.

Presets can be saved, exported as a JSON file, and imported later: - In the **Style** tab, tap the save icon to create a preset, then use **Export** / **Import** to move them between devices. Per‑app rules are set in the **Apps** tab: - Choose an app from the list, then enable **Foreground use** or **Notification** rules. - Select **Face‑down only** (global or per‑notification) and toggle the caution/liveness indicator. - For privacy activity rules, pick **Microphone** or **Camera** and assign any built‑in animation and colour, optionally limiting to a specific app or "any app". - Per‑contact rules let you assign a colour to a sender; the app reads the sender’s name from the notification (no contacts permission needed) and remembers chat names locally. All rules are stored on the device; no data is sent to external servers.

HiLight Studio supports English and Japanese. The language for each app can be selected independently from Android’s own Language settings (Settings → Apps → HiLight Studio → Language). The UI itself follows the system language unless you change it in the app’s **Setup → General** → **App language**.