Repository navigation
device/lynx: WIFI-PLAN after the fs_ready boot - #133
Merged
Merged
Conversation
The plan merged in derekross#88 as it stood before the fs_ready diagnostic boot (run 17, 2026-10-27, derekross#36). Record its result and what follows from it: - status line: the boot with Google's host stack, Google's own trigger and full Android's 5 s wait ran and stalled the same way, so that pair is ruled out and the variants are stopped; the cold stock read is the one measurement left; - section 7 item 1: the run as reported on derekross#36 (Google's kernel and vendor_dlkm modules, 68 modules, Bluetooth off, fs_ready at 10.8 s, IN_COLD_BOOT_CAL, the power-up 5 s later, BHI from 16.0 s, 0xfad00000 on every dump, -110 at 76.8 s), and the module count that matches it; - section 7 item 2: the module comparison as background, with the caveat about first-stage loads, and the CNSS profile's 16 modules on top of the USB profile's 52, in load order; - section 8: the ramoops console survives only a warm return, so the diagnostic's init writes warm to /sys/kernel/reboot/mode first; - section 5 and the pin table: gph2-5 reads output low at every Linux boot only on a kernel without the Bluetooth node (linux-omarchy-mobile derekross#98); with it a regulator owns the pin, so unbind the serdev first and record which kernel a run used. Assisted-by: LLM Signed-off-by: Jean-Paul Florencio <jpflorencio@version-tracker.app>
4 of 9 tasks
Owner
|
Thank you, @FlorencioJP, this is exactly the follow-up I asked for, and quickly too. I checked each of the five points against the thread on #36:
A few small things, none of them blocking:
@latentoperator, it's your plan, so please say if you'd like any of the wording changed. Otherwise I'll merge this as it is. |
derekross
added a commit
that referenced
this pull request
Oct 30, 2026
The matrix and the Wanted list against what has merged since #140, with each pull request's state checked on GitHub today: - Pixel 7 (panther): the GPU and haptics nodes (kernel #129, #130) were closed because they landed unchanged through kernel #134, merged with the touchscreen node and s2idle by default; device-panther 0.1.1 (#145) carries the GPU's always-on rule, the feedbackd rule and the sleep.conf drop-in. GPU and Haptics stay "testing" and now cite #134, #145 and the 2026-10-28 notes. Touch stays WIP: kernel #134's body records touches driving Hyprland and the PIN screen, but the driver fixes (kernel #133) and the kernel option with the touch notes (#149) are still in review. Suspend: "no" with the s2idle default named, since the notes say it hasn't run. - Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5 passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel #114, feedbackd's rule in device-raven 0.1.27 (#113). Display names its open kernel PR, #116. - Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (#133) records it scanning through its own UART; kernel #98 and #98 are in review. The Wanted line says so too. - Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained vbmeta_b needs (NOTES 2026-10-28 and 10-29, #104); Suspend describes the merged tier 1 auto-sleep (#64, off by default behind the omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old "until S8" text. Nothing from the open #171, #172, #174-#176. - Wanted: coral's #52 is merged, so its line no longer says "in review"; flame gets a line for its native install in review (#55, #56, #58, #59, split out of #17); the OnePlus 13 (dodge) is listed with #111 and kernel #115, both open. The Pixel 9a row and the Pixel 9 family line are left to #165. Every status word still parses with the website's parseCell. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
nesmeck
added a commit
to nesmeck/omarchy-mobile
that referenced
this pull request
Oct 31, 2026
Add panther's kernel.config with CONFIG_TOUCHSCREEN_FOCALTECH_FT3658=m, as derekross asked in linux-omarchy-mobile#109, for the touch node in review in linux-omarchy-mobile#134. NOTES records T6, one boot of that node with the driver's review fixes (derekross#133), suspend-to-idle and LDO25M at 1.8 V: the touch loads at boot, works across the panel and unlocks the PIN screen, and the GPU and the haptics keep working. TOUCH-PLAN's status and the Pixel 7 row's Touch cell say so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
nesmeck
added a commit
to nesmeck/omarchy-mobile
that referenced
this pull request
Oct 31, 2026
…ss#149's review points Move CONFIG_TOUCHSCREEN_FOCALTECH_FT3658=m to kernel/configs/omamobile.config, next to the other touchscreen options, and drop device/panther/kernel.config: that file is for options that would break another device, and the release kernel never reads it; the driver binds only to its own compatible. NOTES' T6 entry names its kernel release and how it relates to the PR heads (derekross#134 at ace1ba57fbe7, derekross#133 at fdc4f4403103: the build's local merge has the same tree), and that the option came from the shared fragment. The second stock fallback entry says where the changed bytes sit: the same areas as after boot 6. TOUCH-PLAN's status line carries T6's date, and BRINGUP-M1's status says the FT3658 never answered because of its supplies, pointing at TOUCH-PLAN's result. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
derekross
pushed a commit
that referenced
this pull request
Nov 1, 2026
…uch notes (#149) Panther's touchscreen: CONFIG_TOUCHSCREEN_FOCALTECH_FT3658=m in the shared fragment next to the Synaptics line (focaltech,ft3658 appears only in gs201-panther.dts, so it binds nowhere else), and BRINGUP-M1, NOTES and TOUCH-PLAN with T6's result on 7.3.0-rc6-omamobile-push1-g8d46192a301e (kernel #134 at ace1ba57fbe7, #133 at fdc4f4403103). device/panther/kernel.config is gone.
9 tasks done
derekross
added a commit
that referenced
this pull request
Nov 1, 2026
…s on the 7 Pro (#254) Kernel #153 (husky touch), #166 and #133 and omarchy-mobile #149 (panther touch) merged on 2026-10-31 and 11-01, and omamobile-audio 0.5.8 raised the 7 Pro's default speaker gains under verified protection. The website's device pages are built from this file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 1, 2026
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
The plan merged in derekross#88 as it stood before the fs_ready diagnostic boot (run 17, 2026-10-27, derekross#36). Record its result and what follows from it: - status line: the boot with Google's host stack, Google's own trigger and full Android's 5 s wait ran and stalled the same way, so that pair is ruled out and the variants are stopped; the cold stock read is the one measurement left; - section 7 item 1: the run as reported on derekross#36 (Google's kernel and vendor_dlkm modules, 68 modules, Bluetooth off, fs_ready at 10.8 s, IN_COLD_BOOT_CAL, the power-up 5 s later, BHI from 16.0 s, 0xfad00000 on every dump, -110 at 76.8 s), and the module count that matches it; - section 7 item 2: the module comparison as background, with the caveat about first-stage loads, and the CNSS profile's 16 modules on top of the USB profile's 52, in load order; - section 8: the ramoops console survives only a warm return, so the diagnostic's init writes warm to /sys/kernel/reboot/mode first; - section 5 and the pin table: gph2-5 reads output low at every Linux boot only on a kernel without the Bluetooth node (linux-omarchy-mobile derekross#98); with it a regulator owns the pin, so unbind the serdev first and record which kernel a run used. Assisted-by: LLM Signed-off-by: Jean-Paul Florencio <jpflorencio@version-tracker.app> Co-authored-by: Jean-Paul Florencio <jpflorencio@version-tracker.app>
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
The matrix and the Wanted list against what has merged since derekross#140, with each pull request's state checked on GitHub today: - Pixel 7 (panther): the GPU and haptics nodes (kernel derekross#129, derekross#130) were closed because they landed unchanged through kernel derekross#134, merged with the touchscreen node and s2idle by default; device-panther 0.1.1 (derekross#145) carries the GPU's always-on rule, the feedbackd rule and the sleep.conf drop-in. GPU and Haptics stay "testing" and now cite derekross#134, derekross#145 and the 2026-10-28 notes. Touch stays WIP: kernel derekross#134's body records touches driving Hyprland and the PIN screen, but the driver fixes (kernel derekross#133) and the kernel option with the touch notes (derekross#149) are still in review. Suspend: "no" with the s2idle default named, since the notes say it hasn't run. - Pixel 6 Pro (raven): Haptics "no" -> "works": HAPTICS-TORCH-PLAN H5 passed (2026-10-28/29), cs40l25-vibra and the node merged as kernel derekross#114, feedbackd's rule in device-raven 0.1.27 (derekross#113). Display names its open kernel PR, derekross#116. - Pixel 7a (lynx): Bluetooth "no" -> WIP: the merged WIFI-PLAN (derekross#133) records it scanning through its own UART; kernel derekross#98 and derekross#98 are in review. The Wanted line says so too. - Pixel 7 Pro (cheetah) detail: Boot names the AVB footers a chained vbmeta_b needs (NOTES 2026-10-28 and 10-29, derekross#104); Suspend describes the merged tier 1 auto-sleep (derekross#64, off by default behind the omamobile-sleep toggle, P0-P5 on 2026-10-26) in place of the old "until S8" text. Nothing from the open derekross#171, derekross#172, derekross#174-derekross#176. - Wanted: coral's derekross#52 is merged, so its line no longer says "in review"; flame gets a line for its native install in review (derekross#55, derekross#56, derekross#58, derekross#59, split out of derekross#17); the OnePlus 13 (dodge) is listed with derekross#111 and kernel derekross#115, both open. The Pixel 9a row and the Pixel 9 family line are left to derekross#165. Every status word still parses with the website's parseCell. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
…uch notes (derekross#149) Panther's touchscreen: CONFIG_TOUCHSCREEN_FOCALTECH_FT3658=m in the shared fragment next to the Synaptics line (focaltech,ft3658 appears only in gs201-panther.dts, so it binds nowhere else), and BRINGUP-M1, NOTES and TOUCH-PLAN with T6's result on 7.3.0-rc6-omamobile-push1-g8d46192a301e (kernel derekross#134 at ace1ba57fbe7, derekross#133 at fdc4f4403103). device/panther/kernel.config is gone.
robertzas
pushed a commit
to robertzas/omarchy-mobile
that referenced
this pull request
Nov 14, 2026
…s on the 7 Pro (derekross#254) Kernel derekross#153 (husky touch), derekross#166 and derekross#133 and omarchy-mobile derekross#149 (panther touch) merged on 2026-10-31 and 11-01, and omamobile-audio 0.5.8 raised the 7 Pro's default speaker gains under verified protection. The website's device pages are built from this file. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
The follow-up asked for on #36 (2026-10-28 20:14Z):
device/lynx/WIFI-PLAN.mdmerged in #88 as it stood before thefs_readydiagnostic boot, so it still named that boot as the next step. One file, five places:fs_readyboot ran on 2026-10-27 and stalled, so "Google's host stack and full Android's wait" is ruled out as the pair and the variants are stopped; the cold stock read (section 7, item 3) is the one measurement left, at latentoperator's call.vendor_dlkmmodules, 68 modules, Bluetooth off,fs_readyat 10.800 s,IN_COLD_BOOT_CAL, the power-up 5 s later, BHI from 16.001 s,0xfad00000on every dump, -110 at 76.772 s), and "52 modules" corrected to the 52 + 16 the run carried.warmto/sys/kernel/reboot/modefirst. Applies to both phones.gph2-5reads output low" holds only on a kernel without the Bluetooth node (linux-omarchy-mobile device-lynx: Bluetooth on the APM UART #98); with it a regulator owns the pin, so unbindserial0-0fromhci_uart_qcafirst and record which kernel a run used.Not in this PR: the "Bluetooth waits on the same question" and "
gpp16-2on PERIC1" lines in NOTES and section 2, which #98 corrects on its rebase, as agreed there. Facts only, no new boots.tools/pr-checkpasses. @latentoperator, the wording in sections 5 and 7 is yours to adjust.