Skip to content

device/husky, DEVICES: Bluetooth, haptics, the torch and the gauge on a third phone - #802

Merged
derekross merged 3 commits into
derekross:mainfrom
gitColinX:husky-third-unit-status
Nov 16, 2026
Merged

derekross merged 3 commits into
derekross:mainfrom
gitColinX:husky-third-unit-status

Conversation

@gitColinX

@gitColinX gitColinX commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

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 omamobile at 82f31d3a7. Documentation only, on today's main with #741 in.

What changes

I left the Charging cell and the subsystem rows of the ROADMAP alone, since those are Lef's.

Limits

tools/pr-check: all ok.

@Somnius @greenbrettmichael for review, since these are your rows and your table.

@Somnius

Somnius commented Nov 15, 2026

Copy link
Copy Markdown
Contributor

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 (gbfe780ba73bf: published 82f31d3a7 plus the AoC sound port and the power-off change, so not the published build itself) I saw the torch LED light (brightness 2 of 17, by eye), felt two 500 ms FF_RUMBLE effects, and the Bluetooth radio powered up and a scan saw 12 devices. I didn't pair anything, so pairing and A2DP are yours alone. The gauge reads fine here too.

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).

@derekross

Copy link
Copy Markdown
Owner

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:

  1. Battery. The new cell says "the gauge with Google's ATL model … merged". The published zuma-husky.dts has no model. Its comment above the gauge says "The fuel gauge has no battery model yet…", and the fuel-gauge@36 node has no maxim,fg-model. The ATL model only exists in the bring-up overlay BATTERY-NOTES describes. Your own entry says the gauge was there "with no overlay", so your phone read it without a model. BATTERY-NOTES shows that matters: the right model moved the reported level by 10 points. In the legend's words that's partial, so something like: "partial (the gauge, temperature, MFD and pack EEPROM on by default, merged, kernel omamobile-modem 0.1.10: the modem profile starts once per boot #163, omamobile-shell 0.2.40: hide and show the keyboard from the home pill #175, the bus with device-cheetah 0.1.34: prefer Wi-Fi over the USB gateway #205; no battery model in the board file yet, Google's ATL model only through a bring-up overlay; verified on the third phone, notes; BATTERY-NOTES)". Please also add a clause to the NOTES bullet saying it ran without a model.

Two small ones while you're there:

  • "UPower acted on its level" cites the 11-13 critical-battery suspend, and that sleep never came back (SUSPEND-PLAN §4). Saying so in a few words keeps anyone from reading it as a good suspend.
  • [s2idle] deep is /sys/power/mem_sleep; naming the file helps, since older notes quote s2idle [deep] from earlier kernels.

With the Battery cell fixed I'll merge it.

@gitColinX
gitColinX force-pushed the husky-third-unit-status branch from 5422af8 to 76f688a Compare November 15, 2026 18:56
@gitColinX

gitColinX commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor Author

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 hsi2c_11 in zuma-husky.dts). On my unit charge_full_design reads 3000000 against the pack's 4950 mAh, so the percentage comes from the gauge's default model. Google's ATL model only arrives through Lef's bring-up overlay.

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.

gitColinX and others added 3 commits November 15, 2026 19:32
… 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>
@gitColinX
gitColinX force-pushed the husky-third-unit-status branch from 76f688a to b1d56d4 Compare November 16, 2026 02:32
@gitColinX

gitColinX commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor Author

@derekross, thank you. Our messages crossed: the Battery fix you asked for is the second commit (partial, no battery model in the board file, Google's ATL model only through the bring-up overlay, and the NOTES bullet saying the gauge ran without one). On my unit charge_full_design reads 3000000 against the pack's 4950 mAh, which fits.

The two small ones are in a third commit:

  • The NOTES bullet now says the 11-13 critical-battery suspend didn't come back.
  • "[s2idle] deep" now names /sys/power/mem_sleep.

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.

@derekross

Copy link
Copy Markdown
Owner

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 charge_full_design figure in the notes is a nice touch: it shows the gauge is on its default model. The suspend clause and the mem_sleep file are in too, and thanks for adding "on a local kernel" to the Suspend row.

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 mem_sleep selects deep "on the current kernels", while your boot on the published kernel reads [s2idle] deep. Whenever you next touch those files is fine. Merging now.

@derekross
derekross merged commit b010833 into derekross:main Nov 16, 2026
2 checks passed
gitColinX added a commit to gitColinX/omarchy-mobile that referenced this pull request Nov 16, 2026
…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>
derekross pushed a commit that referenced this pull request Nov 18, 2026
…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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants