Repository navigation
Conversation
The owner observed the rear LED turn on and off on the private integration kernel. Link the matrix to the hardware result and keep public enablement pending. Assisted-by: LLM
|
Thank you, @Gr-linkk. The entry says plainly that this was your private kernel with a helper supplying the node, and that the public package doesn't enable the torch. That is how I want these recorded. Two wording fixes and it goes in:
Three small additions to the entry, if you can: what the helper is (a module that registers the LED's I2C device, or an overlay), that this run is not a test of #242's strobe handling (its commit messages say that path hasn't run on hardware), and which shell ran (your notes say the phone has a local 0.2.12). On #242 itself, my three points from 11-11 are still open (the commit messages against the description, the binding text, |
Record the observation on the unpublished integration setup and identify the proposed board node and remaining enablement work. Assisted-by: LLM
The Pixel 6 torch cell says “no”. On November 10 the owner saw the rear LED turn on and off on the private integration kernel. The shell tile action also returned brightness to zero and the hardware enable line to low before its fallback fired. The notes identify the kernel and private setup.
Change only the torch cell to WIP. The public device package still leaves the torch disabled. Testing the public kernel and enable overlay is a separate step in derekross/linux-omarchy-mobile#242.
Checked the saved observation, shell tile and final-off records. Repository policy and whitespace checks pass. Documentation only.