FAQ

Lazulite needs permission to read your Android system's audio logs to show Bluetooth codec and audio path information. Android restricts access to these logs for privacy and security reasons, so you'll need to grant permission using one of three methods:

Option 1: Shizuku (Recommended for Most Users)

Best for: Most users, especially those who prefer to set up Lazulite directly on their phone

Shizuku lets Lazulite access the system information it needs without root. On Android 11 and newer, you can start Shizuku using Wireless debugging, without connecting your phone to a computer. After restarting your device, you'll need to start Shizuku again before opening Lazulite.

▶ Video guide: How to enable Shizuku

Option 2: ADB (For Users Familiar with ADB)

Best for: Users who already know how to use ADB from a computer

Install Android SDK Platform-Tools, enable USB debugging, connect and authorize your phone, then run:

adb shell pm grant com.pedronveloso.lazulite android.permission.DUMP

Option 3: Root Access

Best for: Power users with rooted devices

If your device is rooted, Lazulite can automatically request the necessary permissions. This is the most convenient option, but only if you're already comfortable with rooting Android devices.

First time using ADB? We recommend using Shizuku instead. The ADB option is intended for users who are already comfortable running commands from a computer.

If you want to continue with ADB, install Android SDK Platform-Tools, enable USB debugging, connect and authorize your phone, then run:

adb shell pm grant com.pedronveloso.lazulite android.permission.DUMP

Already granted permission but it's not working? Make sure:

• Your phone is connected via USB with USB debugging enabled
• You've authorized the computer on your phone when the "Allow USB debugging?" prompt appeared
• adb devices lists your phone as device, not unauthorized
• You ran the grant command exactly as shown above

Using Shizuku? Ensure Shizuku is running before launching Lazulite.

Lazulite can detect and display all Bluetooth audio codecs your device supports:

• LDAC, aptX, aptX HD, aptX Adaptive, aptX TWS, LC3, MIHC, Opus
• LHDC (see supported LHDC versions below)
• AAC, SBC
• SSC, SSC UHQ (Samsung devices only)

If your phone and Bluetooth audio device support it and agree to use it, Lazulite will show it.

Lazulite has been tested with LHDC V2, V3, and V5. In theory, it should support all current and future LHDC versions.

No. Lazulite works with Bluetooth audio devices, including headphones, earbuds, speakers, car audio systems, and Bluetooth audio receivers. Connect the device to your Android phone and play audio to inspect its Bluetooth codec and reported audio path. Available details depend on the phone and connected device.

Wired audio inspection is not supported. Lazulite shows the codec selected by your phone and Bluetooth audio device, along with the audio path reported by Android.

Wired connections bypass Bluetooth, so there is no Bluetooth codec data for Lazulite to inspect.

Many streaming apps claim "lossless" or "hi-fi" quality, but your device or headphones may force re-encoding to a lower-quality codec before audio ever reaches your ears.

Lazulite shows the actual codec used for Bluetooth transmission, not what the streaming app reports. If you are paying for hi-res audio but seeing AAC 256kbps in Lazulite, you now know what is actually happening.

Some Android devices can move Bluetooth audio encoding off the main processor and onto dedicated audio or Bluetooth hardware. That can reduce CPU work and power use during playback.

Lazulite detects when A2DP hardware offload is active and lists which codecs your device's hardware supports for it. A codec showing up in that list doesn't mean it's being offloaded right now: that depends on the codec in use, the connected device, your system settings, and how the manufacturer implemented it.

With "Look up destination vendor" enabled in Settings, Lazulite uses the connected Bluetooth audio device's MAC address prefix to look up the associated manufacturer, when available. This may identify the Bluetooth chipset manufacturer rather than the brand of your headphones, speaker, or other audio device. A result is not always available, for example when the address is randomized or the lookup has no matching record.

This is on by default when no preference has been saved; existing choices are preserved. You can turn it off in Settings. When enabled, Lazulite sends only the first three pairs of the destination MAC address to MACLookup to identify the vendor. No other part of the address is ever sent.

Lazulite performs all audio analysis locally on your device. No data leaves your phone unless you choose to share it.

Optional crash diagnostics: Lazulite does not collect app usage analytics. Crash diagnostics are off by default; if you enable them, crash reports and technical diagnostic logs may be sent to Google Firebase Crashlytics to help improve stability. Locally stored reports may upload after you opt in.

Optional vendor lookup: When "Look up destination vendor" is enabled in Settings, Lazulite sends the first three pairs of your connected device's MAC address to MACLookup to identify its manufacturer. No other part of the address is sent, and the setting is on by default when no preference has been saved. Existing choices are preserved, and you can turn it off in Settings.

Want to opt out? Go to Settings → Disable "Crash diagnostics" or "Look up destination vendor".

TL;DR: Nope, negligible impact.

Lazulite only reads existing system logs that your device generates anyway. It doesn't create additional processes or run in the background when you're not using it.

Note: Lazulite monitors your phone's logs, not your Bluetooth headphones. Your earbuds' battery is unaffected.