docs(README): add ASUS Sonix IR hardware notes (proximity-sensor controlled emitter)#1110
Open
jatroconis wants to merge 1 commit into
Open
docs(README): add ASUS Sonix IR hardware notes (proximity-sensor controlled emitter)#1110jatroconis wants to merge 1 commit into
jatroconis wants to merge 1 commit into
Conversation
Document the empirically-validated finding that on ASUS laptops with a Sonix 3277:0018 IR module (Vivobook, ProArt, Zenbook), the IR emitter is controlled by the laptop's proximity sensor and only fires on motion in front of the camera. This: - Explains why 'howdy test' shows a black feed when no one is in front (expected — face entry triggers the LED) - Tells users not to run linux-enable-ir-emitter configure on these models (its brute-force step wedges the USB bus on Sonix chips per EmixamPP/linux-enable-ir-emitter#195) - Notes the common bezel layout where the IR LED is co-located with the RGB camera, so privacy-shutter behavior can be misleading References issue boltgolt#1109 for the empirical data and full investigation. Affected models reported across boltgolt#890 and related issues: ASUS Vivobook X1607C, ProArt PX13, ProArt H7606WX-DRSE011X, Zenbook S16 UM5606.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a small Hardware notes subsection under Troubleshooting in the README, documenting the proximity-sensor-controlled IR emitter behavior on ASUS laptops with the Sonix
3277:0018IR module (Vivobook, ProArt, Zenbook lines).This is a documentation-only change — no code touched.
Why
I just spent a long debug session getting Howdy working on a Vivobook X1607C and chased an IR feed that "worked for one frame and then went black" through several Howdy issues, several
linux-enable-ir-emitterissues, and two forced reboots before tracking down the actual cause. The root cause is hardware behavior, not a Howdy bug, and a small note in the README would save the next person the same debug session.The empirical investigation, including frame-by-frame brightness data with and without motion in front of the camera, is in #1109.
What the change says
howdy testshowing a black feed when nobody is in front is expected — face entry triggers the LED at auth time.linux-enable-ir-emitter configureon these models. Multiple users have reported the brute-force UVC step wedges the USB bus on Sonix3277:0018and requires a hard reboot (see EmixamPP/linux-enable-ir-emitter#195). It will not find a working sequence anyway because the LED is not chipset-controlled.Affected hardware (per cross-issue reports)
Test plan
I'm happy to move this to the wiki instead if that's the preferred home for hardware quirks. Also happy to expand the section with notes about other vendor IR modules if other contributors share their findings.