Consumer Avenkin firmware typically enforces face blur at the system or camera API level so third‑party apps, saved files and streams show blurred faces. To capture raw faces you must secure a written enterprise/SDK commitment from Avenkin, use a paired phone or external recorder, or switch to a headset that does not blur.
Time needed about one hour at a demo unit plus follow-up time to export files
- Avenkin consumer builds usually apply face blur before apps receive camera frames.
- Verify enforcement on a live unit and an exported saved file before you buy.
- Do not attempt firmware hacks; request enterprise/SDK access or choose another device.
- Paired-phone capture or an external recorder are practical, legitimate workarounds.
- Collect dated, exportable evidence on the demo unit to support returns or enterprise requests.
- Your phone with the companion app installed and file‑browser access to exported files
- A consenting person to appear in the test recording for proof
- A USB cable or a method to export saved files to a laptop immediately
- A camera or second phone to record the live preview with a visible timestamp
- Access to the glasses’ Settings or About page to screenshot firmware and app versions
The steps
- Prepare test materialsOpen the companion app on your phone, launch a file browser or laptop file viewer, ready a second camera for a timestamped recording, and confirm the person in frame consents to being recorded.You should see: Phone companion app launches, file viewer open, and the secondary camera shows current date/time on screen.
- Show firmware and app versionOn the glasses open Settings → About or System and take a screenshot or photo showing the firmware string and companion app version.You should see: A clear image showing the firmware string and companion app version.
- Record a live preview clipStart the glasses’ camera app, begin recording while you watch the through‑lens live preview, and simultaneously record the live preview on your second camera so it has a visible timestamp.You should see: A 10–30 second clip recorded on the glasses and a timestamped external recording of the live preview.
- Export the saved file immediatelyUse the companion app or USB to export the saved clip from the glasses to your phone or laptop and open it in a standard video player.You should see: The exported video file appears in your file viewer and plays on your phone or laptop.
- Compare preview to saved filePlay the external timestamped preview video and the exported saved file side by side; check whether faces are blurred in the saved file.You should see: A clear side‑by‑side comparison showing whether the exported file contains blurred faces.
- Test a third-party app if availableInstall and run any allowed third‑party capture app on the glasses and repeat the record, export and compare steps to see whether alternate apps receive unblurred frames.You should see: Recorded files from the third‑party app appear and either match or differ from the vendor app results.
- Document and request written confirmationCollect screenshots, exported files, the timestamped preview video, and ask staff to provide a written statement of the unit’s firmware and any blur policy; email that to yourself.You should see: An email or paper statement from staff and a folder on your device containing all test evidence.
- Contact Avenkin support for enterprise optionsOpen a support ticket with Avenkin, attach your evidence, and ask explicitly for SDK access or a managed build that provides raw frames; request technical documentation or a trial build.You should see: A support ticket number and either written confirmation of enterprise options or a refusal.
avenkin face blur disable options are not available in consumer builds
Consumer Avenkin builds do not expose a user toggle to turn off face blur. The blur often runs in device firmware or the system camera API so third‑party apps and saved files receive already‑blurred frames. If blur runs at system level, switching camera apps will not produce raw faces.
This matters because it determines how you test in store, what evidence you collect, and whether you need enterprise access or a different device to capture unblurred footage.
How to test the claim on a demo unit or before buying
Bring your phone, a USB cable, and a second camera or phone for a timestamped recording. Record a live through‑the‑lens preview and the saved file on the glasses, then export the saved file immediately so you can compare the two on another device. Do not accept a preloaded demo loop.
Prepare a short script and one consenting person in frame so your clip shows identifiable actions and times you can match between preview and file.
- Ask staff where the blur is enforced: firmware, system API, the vendor camera app, or cloud processing.
- Record a 10–30 second clip with the glasses’ default camera app while you watch the live preview.
- Export the saved file to your phone or laptop immediately and open it in a standard video player to confirm whether faces are blurred in the saved file.
- If the store refuses export, record the live preview externally with visible timestamps and get a written staff statement.
What 'where the blur is enforced' means and why it changes your options
Enforcement can run in the vendor app, in device firmware or the system camera pipeline, or as cloud post‑processing. Each location changes your options: an app‑level blur can be bypassed by another app; a system/firmware blur cannot; cloud blur may leave on‑device files unblurred while playback is processed elsewhere.
To tell the difference, compare the through‑lens live preview, the saved file on the device, and what third‑party apps receive. If the preview is unblurred but the saved file is blurred, the blur runs at save or in the cloud; if all three are blurred, the blur is at system or firmware level.
Legal and privacy context you must check before recording faces
Blurred faces reduce some privacy risk but do not remove legal obligations. Obtain consent where required and check local rules about recording in public, workplaces or sensitive locations. Treat vendor blur as a technical measure you must verify, not a legal safeguard.
When you rely on vendor blur to anonymise bystanders, test its effectiveness for your use case and keep dated evidence of that test and any consent forms.
- Clarify who is responsible for consent on someone else’s site—the operator or you—and document that decision.
- Keep a dated consent form or an on‑camera verbal consent clip when you need unblurred capture for legitimate work.
Legitimate alternatives when you need unblurred footage
Don’t modify firmware to remove blur. Ask Avenkin for enterprise/SDK access, capture via a paired phone or external recorder, or switch to a headset that does not apply system‑level blur. Each option has different lead times and technical requirements.
Enterprise/SDK access suits organisations that can secure a written agreement and technical support. Paired‑phone or external capture is the fastest field workaround. Choosing a different device is the right call if you need regular raw capture without vendor restrictions.
- Request Avenkin enterprise SDK or camera API access and written confirmation that it provides raw frames.
- Test a paired‑phone workflow: some glasses proxy a camera feed to your phone where you can capture raw frames.
- Compare models and apps in our directory at /apps and device pages such as the XREAL Air 2 Ultra (/devices/xreal-air-2-ultra), Vuzix Shield (/devices/vuzix-shield) and Even Realities G1 (/devices/even-realities-g1).
- For one‑off shoots, use a dedicated action camera or pair a conventional camera with a wireless monitor instead of relying on the glasses’ camera.
How to check enforcement on Avenkin glasses you already own
Inspect firmware and app versions, record test clips in each available app, and export saved files for off‑device verification. Do not rely on a single playback on the glasses; collect the files and screenshots that show firmware and app versions alongside timestamped clips.
If you must contact support, attach your exported files, screenshots of firmware strings, and the timestamped preview recording so the vendor can reproduce the issue.
- Screenshot Settings → About or System showing the firmware string and companion app version.
- Record clips with the vendor camera app and any allowed third‑party app, then export both files for comparison.
Why this testing routine fails in practice and what to do about it
Tests commonly fail because staff refuse export, demo units run special firmware, or retail units play cached promotional clips. If you cannot get an exportable, timestamped clip from the unit you intend to buy, do not accept the sale without written confirmation.
Prevent wasted time and returns paperwork by collecting exportable, time‑stamped evidence before purchase and by asking for a consumer‑firmware unit to test.
- If staff only show a looped demo, record the live preview externally with a visible timestamp and get a paper confirmation of the unit’s firmware string.
- If online support is vague, escalate to enterprise sales and request specific SDK documentation or a trial build.
Your next step: run the quick decision checklist at the store or on your device
Run the checklist below at the demo or on your device and collect dated evidence. If Avenkin will not provide exportable proof or an enterprise SDK, return the device or pick a different headset that meets your capture needs.
The checklist tells you whether the blur is system‑wide, whether Avenkin will make an exception, and whether switching devices will save time.
- After you complete the checklist, compare suitable apps and alternative devices in our directory at /apps so you can pick a model that matches your workflow.
Where this usually goes wrong
- Live preview looks clear but exported saved file shows blurred facesBlur is applied at save or in a cloud processing step after previewCollect the timestamped preview video plus the exported file; request a written explanation from staff and Avenkin. If unresolved, do not keep the device.
- Both live preview and saved files are blurred across all appsSystem/firmware level enforcement provides only blurred frames to appsAsk Avenkin for enterprise/SDK access or switch to a device known not to enforce system‑level blur.
- Store staff show a polished promotional loop instead of live captureDemo units are configured to play marketing content rather than allow testingAsk for a live capture on a consumer unit, insist on file export, or test a different retailer unit.
- Companion app will not export files or lacks file accessRetail demo software restrictions or locked demo firmwareRequest staff to perform an export for you and hand you the file, or ask for a unit with export enabled.
The checklist
- Prepare test materials
- Show firmware and app version
- Record a live preview clip
- Export the saved file immediately
- Compare preview to saved file
- Test a third-party app if available
- Document and request written confirmation
- Contact Avenkin support for enterprise options
Frequently asked questions
Can Avenkin disable face blur for enterprise customers?
Possibly, but get a written technical commitment before you rely on it. Request the exact SDK/API documentation and a sample build or test plan that demonstrates raw frame output; do not accept verbal claims alone.
If the live preview looks unblurred, can I trust my saved files will be unblurred?
No. Live preview and saved files can differ if blur runs at save or in cloud processing. Always export the saved file and verify it on another device before you accept the device or leave the store.
Is it OK to try to remove the blur by modifying the device?
No. Modifying firmware or bypassing vendor restrictions can void warranties, break device security, and raise legal and ethical issues. Use vendor channels for enterprise needs or choose a different device.
What proof should I collect to support a return or an enterprise request?
Collect a timestamped clip of the live preview, the exported saved file, screenshots of firmware and app versions, and any written staff statements. Keep all files and timestamps together; vendors and retailers accept that as evidence.
Which alternative devices typically do not apply system-level face blur?
Behaviour varies by vendor and firmware; some headsets do not enforce mandatory system blur. Compare device pages and apps in our directory at /apps and check model pages such as the XREAL Air 2 Ultra (/devices/xreal-air-2-ultra), Vuzix Shield (/devices/vuzix-shield) and Even Realities G1 (/devices/even-realities-g1).
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.