Repository navigation
device/husky, DEVICES: Bluetooth, haptics, the torch and the gauge on a third phone - #802
Conversation
|
Looks right to me, and thanks @gitColinX, this saves me doing it. What I can add from my unit, so it isn't one phone only for all of it: On 2026-11-14 on a local kernel ( For the Charging cell you left to me: on my unit charging stops at 92 %, the cause and the plan are in #761, so I'd keep that one at testing for now. I haven't checked these on the published kernel itself beyond the firmware loading and the devices being there, as I said on #741 (comment). |
|
Thank you, Colin, and thanks @Somnius for checking it against your unit. This is the kind of record the matrix needs: one phone named, the published kernel unchanged, the package version, who saw or felt each thing, and what wasn't tried (Handsfree, torch levels). I checked the kernel PRs each cell cites (#199, #200, #205, #163, #175: all merged) and the anchors. Bluetooth, Haptics and the Torch read right to me. One cell needs a change before I merge:
Two small ones while you're there:
With the Battery cell fixed I'll merge it. |
5422af8 to
76f688a
Compare
|
A correction to my own PR, before it's merged: the Battery cell was wrong. The published tree gives the gauge no battery model ("The fuel gauge has no battery model yet", at The new commit makes Battery partial and says that, and the NOTES entry says the same. The row now has 7 works and 2 partials (Wi-Fi, Battery). Bluetooth, Haptics and Torch are unchanged. Thanks @Somnius for your torch, haptics and gauge checks on your unit, and for keeping Charging at testing, which this PR leaves alone. |
… a third phone A NOTES entry for the third unit (Samsung 128 GB UFS 3.1) on merged omamobile at 82f31d3a7 with the firmware from extract-vendor-firmware (derekross#722): AirPods paired and played over A2DP, two rumble effects felt, the torch seen, and the gauge reading at boot with no overlay (the bus on by default since kernel derekross#205). The husky row's Bluetooth, Battery, Haptics and Torch cells move from testing to works and link it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The published tree gives the gauge no battery model ("The fuel gauge
has no battery model yet" at hsi2c_11), and on the third phone
charge_full_design reads 3000000 against the 4950 mAh pack. So the
Battery cell says partial and that the percentage is the gauge's
default, not works with Google's ATL model, which only a bring-up
overlay loads. The NOTES entry says the same and that its 100 % at
4.328 V isn't comparable with a modelled gauge (derekross#761).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
From the review on derekross#802: the NOTES entry says the 11-13 critical-battery suspend didn't come back, and names /sys/power/mem_sleep for "[s2idle] deep", since older notes quote "s2idle [deep]". From the review on derekross#724: the ROADMAP Suspend row says Lef's runs were on a local kernel. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
76f688a to
b1d56d4
Compare
|
@derekross, thank you. Our messages crossed: the Battery fix you asked for is the second commit ( The two small ones are in a third commit:
From your note on #724, the same commit adds "on a local kernel" to the ROADMAP Suspend row, next to Lef's eight runs. The DEVICES Suspend cell stays at "no" until H0b to H4 run on the published kernel. |
|
Thank you, Colin, and sorry our messages crossed. Your correction came two minutes after my comment. Battery now reads partial with the reason in the cell, and the Two tiny leftovers I'm not holding this for. The notes still call SUSPEND-PLAN a draft, but #724 merged. And ROADMAP's Suspend row says |
…ekross#243 and derekross#244 - NOTES no longer calls SUSPEND-PLAN a draft (derekross#802). - The ROADMAP Suspend row says mem_sleep read "s2idle [deep]" before kernel derekross#244 and reads "[s2idle] deep" on the published kernel (derekross#802). - The ROADMAP Time row no longer says "No RTC": the S2MPG14's RTC is rtc0 since kernel derekross#243 (asked for on that PR). - The 2026-11-15 NOTES entry records /proc/cmdline's mem_sleep_default=s2idle with mem_sleep (asked for on kernel derekross#244), and the RTC's probe lines, wakealarm and idle interrupt count (asked for on kernel derekross#243). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
…efore H2; NOTES and ROADMAP leftovers H0b (the Wi-Fi and PCIe unload and reload, no sleep) and H1 (`pm_test` freezer, devices and platform through `systemctl suspend`: three successes, no failures) ran attended on Colin's 8 Pro on the published `omamobile` at `82f31d3a7` with device-husky 0.1.13; touch, the display and a played haptic effect after H1 are carried into H2, and H2 to H4 have not run. The plan now says that the UFS `dme-set: attr-id 0x4021` line at resume is expected and not a stop, lists the four brcmfmac noise lines, names the maintainer's go-ahead per stage and device-husky 0.1.14 or later for H2 to H4, and records the sleep configuration in effect. NOTES and ROADMAP pick up the leftovers from #802 and the RTC and `mem_sleep_default=s2idle` facts from kernel #243 and #244. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
As agreed with @Somnius on #741: the notes and status cells for the 8 Pro rows Brett left, from my unit (the third one, Samsung 128 GB UFS 3.1), on merged
omamobileat82f31d3a7. Documentation only, on today'smainwith #741 in.What changes
device/husky/NOTES.md: a new 2026-11-15 entry for my unit. Kernel, firmware source and device package version are named in it. Everything listed was checked by a person at the phone:FF_RUMBLEeffects, both felt.docs/DEVICES.md, husky row: Bluetooth, Battery, Haptics and Torch go from testing to works. Each now says merged and links the entry.device/husky/ROADMAP.md, merge order item 1 (your note on device/husky: display, GPU, DVFS and Wi-Fi are merged; a boot of merged omamobile #741, @derekross): device-cheetah 0.1.34: prefer Wi-Fi over the USB gateway #205, Pixel 11 Pro XL (kodiak) — stock facts #199 and device-oriole: record native boot and RTC status finding #200 merged and device/husky: AOC-PLAN.md, the AoC and sound results so far, each with its date and uname -r #450 and husky sound: the AoC start with a hang marker, and the UCM2 and WirePlumber files #453 landed, so "Next" is only the sound kernel PRs, device-comet: stage the Pixel 9 Pro Fold descriptor and boot policy #203 and omamobile-shell 0.2.135: an optional device.lua after the shared phone rules #204.I left the Charging cell and the subsystem rows of the ROADMAP alone, since those are Lef's.
Limits
82f31d3a7, but he hasn't paired, felt, looked at the torch or checked charging there yet.tools/pr-check: all ok.@Somnius @greenbrettmichael for review, since these are your rows and your table.