Setup
- Check your controller. Use the hardware guide to choose the right firmware profile. Chip type alone isn’t enough to identify the wiring.
- Install firmware over USB. Follow the installation guide and use the USB installer. Old firmware using password-based connections needs a USB update before it will work with current apps.
- Connect the app. Turn on Bluetooth, choose Find ears and follow the system picker. Android also has Scan directly. Confirm the OS pairing request, then release and click the headset button within 30 seconds.
The pairing guide covers the details. For app installation, see the Apple or Android guide; store download links aren’t available here yet.
Once connected, the controls guide covers effects, palettes, brightness and calibration.
Common problems
The app can’t find the headset
Check power and Bluetooth permissions. Wi-Fi mode disables Bluetooth in normal firmware. Switch back to Bluetooth and disconnect any other phone or Watch using the headset. See pairing for the button gesture for your board.
Pairing fails
The headset needs a fresh button click after you confirm the OS request. Holding a button from startup doesn’t count. There’s no fixed PIN.
If you reset accessory storage, forget the old system bond and pair again. Don’t erase storage as a routine reconnect fix.
No lights, or the wrong colours
Check power, brightness, LED counts, colour order and the firmware profile. Experimental v2 hardware can deliberately keep the LEDs off until its power limits are configured. Don’t raise current limits just to get light output.
Use LED diagnostics and the troubleshooting guide to narrow it down.
Motion looks wrong
Check that your hardware has a supported sensor. Keep the headset still during mounting calibration, and recalibrate after moving the controller. The phone simulation runs locally; it can’t tell you whether the headset’s sensor is working.
A firmware update failed
Follow updates and recovery before retrying. USB recovery may be needed. The troubleshooting guide also covers USB connections, Wi-Fi and settings that don’t save.
Bugs and questions
Open an issue on GitHub for bugs. For support questions or deletion requests, email espurr-support@neggles.dev.
Include the app and OS versions, controller type, firmware version, what happened and how to reproduce it. The app’s Support screen can prepare these details for you to review. It doesn’t send a support report automatically; logs and local reliability counts are separate options, off by default.
GitHub issues are public. Check logs and recordings before attaching them, and leave passwords and personal details out of reports. Sending email shares your sender address and any attachments with the support mailbox.
Support mail is handled through a Google Workspace Collaborative Inbox. Messages and attachments are kept until manually deleted. Email the support address to request deletion of correspondence you sent.
Privacy
Android, iPhone/iPad and Mac Catalyst offer optional Firebase analytics and crash reporting. It’s off until you allow it. Change Share analytics and crash reports in Settings or Support. Turning it off closes the Android app; reopen it to continue without Firebase. Apple apps stay open when you turn it off. Watch and widgets don’t include Firebase.
The privacy policy draft covers telemetry, local storage and support reports. It still has some publication details to resolve.