Prevent accidental assistant wakes with four layers: apply a hardware mic mute or cover, revoke per-app microphone permissions, disable wake-word activation in system and companion app settings, and isolate units on a demo VLAN or airplane mode. Test every unit with a scripted wake sequence and a second recorder to prove a pass.
Time needed about two hours, roughly 10 minutes per unit
- One OS toggle rarely stops accidental wakes; combine hardware, app, assistant and network controls.
- Physical mic mutes or covers are the fastest, most reliable control during demos.
- Revoke microphone permission for non-essential apps and disable any in-app background listening.
- Isolate demo devices on a VLAN or use airplane mode to stop cloud assistant calls.
- Prove readiness with a scripted wake test and a second recorder; keep the audio and logs.
- Treat firmware and app updates as configuration changes and re-run checks after any update.
- Companion app installed and logged in for each device (admin account access preferred)
- Chargers and batteries topped up so devices do not enter low-power modes during test
- Access to a demo VLAN or Wi‑Fi and ability to isolate devices from the main network
- A second audio recorder (phone or recorder) to capture ambient audio during tests
- A scripted wake test file and a log template to record timestamps and pass/fail results
The steps
- Apply hardware mic mute or coverFlip the device’s hardware mic mute switch or place a removable microphone cover over the mic ports.You should see: Hardware mute shows muted position or cover sits flush; a quick spoken test elicits no assistant response or tone.
- Enable Do Not DisturbOpen system settings and enable Do Not Disturb (or the device equivalent) so notifications and assistant prompts are suppressed.You should see: Device or companion app displays a Do Not Disturb indicator.
- Check firmware version and batteryOpen the companion app or device settings and verify the firmware version you tested and that the battery is above your demo threshold.You should see: Companion app or device settings display the recorded firmware version and battery level above threshold.
- Revoke non-essential app microphone permissionsIn system Settings or the companion app, open each installed app and set Microphone permission to Deny for any app not required for the demo.You should see: System shows Microphone: Deny for those apps and companion app reflects changes where applicable.
- Disable wake-word activationIn system and companion app settings, turn off wake-word activation and set assistant activation to manual only.You should see: Settings show assistant voice activation off or set to manual; a wake-word attempt produces no assistant UI.
- Isolate device on demo VLAN or enable airplane modeConnect the device to the demo VLAN that blocks assistant servers or enable airplane mode if the demo runs offline.You should see: Network settings show connection to the demo VLAN or the airplane mode icon is visible.
- Run the scripted wake test with a second recorderPlace the second recorder beside the device, run the wake script (wake-word attempts, normal conversation, edge cases), and note timestamps in the log.You should see: Recorder audio shows ambient sound but no assistant activation; no assistant UI appears and network logs show no assistant API calls at those timestamps.
- Tag and log the device as demo-readyPlace a 'demo-ready' tag on the device with initials and date, and add an entry to the demo log with device serial, firmware, and test result.You should see: A physical tag is present and the demo log records a pass with timestamps and tester initials.
How to configure smart glasses to avoid accidental AI wakes
Use four layers: hardware mic control, per-app permission limits, assistant toggles, and network isolation. Apply a physical mute or cover first, then revoke microphone access for non-essential apps, disable wake-word activation where possible, and place devices on a demo VLAN or airplane mode. Test and record each unit.
- Layer 1: Hardware mic mute or cover.
- Layer 2: Per-app Microphone permission review.
- Layer 3: Disable wake-word activation in system and companion apps.
- Layer 4: Demo VLAN or airplane mode to block cloud services.
Quick repeatable checks you can run in ten minutes per pair
Run a short, ordered checklist on every demo unit. Start with physical controls, then apply software and network settings. Each step has an observable result you record so staff can verify demo readiness quickly before an event.
- Apply hardware mic switch or cover; verify no response to a spoken test.
- Enable Do Not Disturb and check the visual/system indicator.
- Confirm firmware version and battery level in the companion app.
- Revoke Microphone permission for non-essential apps.
- Turn off wake-word activation or set assistant to manual only.
- Move the device to the demo VLAN or enable airplane mode.
Where to check and change assistant, mic and permission settings on each model
Look in two places: the device system privacy pages and the companion app on the paired phone. Find a hardware mic switch or cover, the per-app Microphone permission page, and any assistant or voice-service toggle in system or companion app settings. Below are model-specific pointers and the expected result for each change.
Apple Vision Pro — where to turn listening down
Open Settings on the Vision Pro (or its paired iPhone companion) and disable Siri in Settings > Siri & Search. Then go to Settings > Privacy & Security > Microphone and remove access for non-essential apps. Confirm the system shows Siri disabled and revoked microphone entries in the Microphone list.
Ray‑Ban Meta — where the assistant and mic live
Open the Meta or Ray‑Ban companion app on the paired phone and look for voice, assistant or privacy settings. Disable any always-on assistant option and revoke microphone access for third-party apps in the phone’s app permission list. Expect the companion app to show voice features off and no assistant overlay during a wake-word test.
- See device details and companion app names here: /devices/ray-ban-meta
XREAL (Air/Ultra) — what to check in the Nebula or GlassesControl apps
Open Nebula or GlassesControl on the paired phone and disable voice assistant options. Then check the phone’s app permission screen for Microphone and set it to Deny or While Using as appropriate. Expected: voice features report disabled in the companion app and no assistant UI on wake-word attempts.
- See app-control links here: /devices/xreal-air-2-ultra
Even Realities G1 and teleprompter apps
Use the Even companion app and the device system settings to revoke microphone permission for non-essential apps. Check teleprompter or demo apps for built-in recording toggles and turn them off. Expected: the teleprompter app shows no active recording indicator when idle.
- Device details: /devices/even-realities-g1
Rokid and Vuzix — workplace controls to use first
Inspect the Rokid and Vuzix companion apps for voice and assistant settings and use hardware mute switches where available. Revoke microphone permissions in the companion app or system settings. Expected: companion app reports voice features disabled and the device shows a muted microphone state.
- Vuzix specifics: /devices/vuzix-shield
Android XR headsets — where to revoke background mic access
On Android XR, open Settings > Apps & notifications > See all apps > [app] > Permissions > Microphone and set to Deny. Then open the device assistant settings and disable voice activation. Expected: app permission shows Microphone denied and assistant voice activation shows off.
Which apps and assistant integrations still listen in the background
Inspect every installed app that has Microphone permission and any in-app assistants. Turning off the system assistant does not always stop third-party listeners. Open each app’s settings and disable background listening, or remove the app from demo devices if you cannot control it.
- Check app-level mic permissions under system Settings.
- Open AI or voice-enabled apps and disable background listening.
- Examples to inspect include meeting and recorder apps and cloud-linked assistants: /apps/meta-ai
How to test and prove a unit won’t accidentally wake during a demo
Run a scripted wake test with a second recorder beside the device. Include single wake-word attempts, normal conversation, and edge cases like laughter. Record timestamps, keep the audio file, and capture companion app network logs. A pass shows no assistant UI, no activation tone, and no assistant network requests during the test window.
- Test script: single wake-word, 30-second read-aloud, simulated demo dialogue, trigger phrases in different voices.
- Expected pass signals: no on-device assistant overlay, no activation chime, and no assistant API calls in logs.
- Run the test once on the demo VLAN and once in airplane mode if possible.
What to do on the day of the demo and how to recover if a unit wakes up
Before the event, show participants where the hardware mute is and announce that devices may record only with consent. Tag units as demo-ready. If a unit wakes during the demo, flip the hardware mute, isolate it from the demo network, and follow a short recovery sequence before returning it to service.
- Staff script: point out the mute and explain consent briefly.
- Recovery: mute the device, kill the companion app, disconnect from Wi‑Fi, rerun the scripted test.
- If the wake persists, factory-reset and reapply the checklist before reuse.
How this setup fails in practice and a simple maintenance policy
Failures repeat: app auto-updates re-enable mic access, firmware restores defaults, or staff restore backups that carry old permissions. Prevent regression with a lightweight policy: log updates, test a sample device after any change, and hold updated devices out of demos until they pass the checklist.
- Common failure: companion app auto-updates re-enable listening — check app auto-update settings.
- Common failure: staff restores a backup that re-enables permissions — require admin restores only.
- Maintenance: log firmware and app versions, re-run the 10-minute checklist, and re-tag the device when passed.
Where this usually goes wrong
- Device wakes during demo despite assistant toggle offA third-party app with microphone permission performs local wake-word detection or an in-app assistant remains active.Immediately flip the hardware mute, kill or uninstall the offending app, revoke its Microphone permission, and re-run the scripted test.
- Devices respond to wake words after a firmware updateFirmware or companion app update restored default permissions or re-enabled voice features.Rollback if possible or reapply the checklist on the updated firmware; record the firmware version and re-test before returning the device to demos.
- Outgoing assistant API calls appear in network logs while device seems idleA background service or cloud-connected app is sending buffered triggers or telemetry.Isolate the device from network, identify the source app via companion app logs, revoke that app’s permissions, and retest.
- Staff restores a backup that re-enables permissionsThe backup contains prior app and system settings that include microphone access.Prevent non-admin restores for demo devices; require any restore to be followed by the 10-minute checklist and re-tagging as demo-ready.
The checklist
- Apply hardware mic mute or cover
- Enable Do Not Disturb
- Check firmware version and battery
- Revoke non-essential app microphone permissions
- Disable wake-word activation
- Isolate device on demo VLAN or enable airplane mode
- Run the scripted wake test with a second recorder
- Tag and log the device as demo-ready
Frequently asked questions
Can I rely on airplane mode alone to stop accidental AI wakes?
No. Airplane mode blocks network calls but may not stop on-device wake processing or local recording. Use it with a hardware mute and per-app microphone permissions, then run the scripted wake test to confirm there is no local assistant response or recorded activation.
How do I capture proof that a device did not wake during a demo?
Record ambient audio with a second recorder, note timestamps, and save companion app network logs if available. A full proof set contains the recorder audio showing no activation, device screenshots showing mic and assistant disabled, and network logs showing no assistant requests during the timestamps.
What if a needed app requires the microphone for core functionality?
Limit microphone access to that app and set it to 'While Using' where possible. If the app still listens in the background, place the device on a demo VLAN that blocks assistant servers or use dedicated demo devices with only the required app installed.
Will firmware updates undo my settings?
They can. Firmware or companion app updates sometimes restore default permissions or re-enable assistants. Treat updates as configuration changes: test a sample device after any update, log the change, and have a revert or reconfiguration plan ready.
How should I tell participants about recording and consent at a public demo?
Verbally announce that devices have microphones and may listen if not muted, point out the hardware mute, and place clear signage at the demo area. For sensitive audiences, require explicit opt-in and keep devices muted and offline by default unless the participant consents.
Find apps that work on your glasses
Every app in the directory lists the glasses it runs on, how it works on each, and the official source that proves it.