Skip to content

omamobile-device-akita 0.1.1: the Trusty partitions for tools/nv-backup, and #456's notes - #509

Merged
derekross merged 1 commit into
derekross:mainfrom
aninmucek:device-akita-m2-followup
Nov 8, 2026
Merged

derekross merged 1 commit into
derekross:mainfrom
aninmucek:device-akita-m2-followup

Conversation

@aninmucek

Copy link
Copy Markdown
Contributor

Follows #456, with its five non-blocking suggestions.

  • NV_BACKUP_EXTRA is now devinfo trusty_persist trusty_userdata, as in the Pixel 8 Pro's package since omamobile-device-husky 0.1.8: the radio partitions for tools/nv-backup #449, so tools/nv-backup --check shows when Android has written Trusty's storage.
    • Both partitions exist on the 8a (sda8, sda9), and neither is on UFS_RW.
    • Both are in M2.4's full backup. trusty_persist changed while stock ran; trusty_userdata didn't.
    • The package carries the descriptor, so it goes to 0.1.1.
    • NOTES' list and its provenance row name trusty_userdata too.
  • ufs-probe.dtso: it now reads "If the board file's bootargs change".
  • M2.7's "Watch for" now says not to use Suspend until the Pixel 8 Pro's U6.
  • Line 275 reads linux-omarchy-mobile#206's head.
  • tools/phone-smoke from the M2.6 root, 42 h into its boot, is test 18 in BRINGUP-M2. The required rows pass except the session, as expected without Omarchy's image.
The report

phone-smoke: akita

Kernel 7.3.0-rc6-omamobile-push1-g31d8b229d0d0, tools at 025e6a2, 2026-07-26T12:13Z.

Check Result Detail
boot (required) ok kernel 7.3.0-rc6-omamobile-push1-g31d8b229d0d0, slot b, up 152223s
storage guard (required) ok 62 partitions; only userdata and slot B's boot images writable
root (required) ok ext4 on userdata, 101G free
kernel health (required) ok no oops or BUG; 0 WARN, 4 error lines in dmesg (2 known, 2 new)
new dmesg errors not ok exynos-clkout exynos-clkout: probe with driver exynos-clkout failed with error N x1; exynos-clkout exynos-clkout: cannot match parent device x1
systemd units ok none failed
USB gadget (required) ok bound to 11210000.usb
display ok card0-Unknown-1 connected, 1080x2400
GPU not ok no render node
session (required) not ok Hyprland isn't running, the shell isn't running
lock not ok no /etc/pam.d/omarchy-lock-password: Omarchy's lock refuses to lock
touch not ok no multitouch input device
buttons skip no key input device found by name
Wi-Fi skip no wireless interface
Bluetooth skip no controller
battery skip no battery power supply
sound cards skip none
sensors skip no sensor proxy
cameras skip no libcamera tools

Packages: none found

The two "new dmesg errors" are the exynos-clkout lines that husky's log has too: the clkout driver can't match zuma's PMU ("cannot match parent device"). The tool's known list is the 7 Pro's. I can add them there with that reason if you'd like; I've left tools/ alone here. The report's date is the phone's clock (July), the same clock M2.7 has to set.

Checks:

  • tests/all: 466 ok, 0 not ok.
  • The package's test/all: 16 ok.
  • tests/nv-backup passes, and tools/nv-backup -d akita --list accepts the three extras.
  • tests/device-overlays passes.
  • tools/pr-check: passes.

🤖 Generated with Claude Code

…up, and derekross#456's notes

From the review of derekross#456:

- device.conf (and the package's copy): NV_BACKUP_EXTRA adds
  trusty_persist and trusty_userdata next to devinfo, as husky's
  package does since derekross#449, so tools/nv-backup --check shows when
  Android has written Trusty's storage.
- NOTES.md: trusty_userdata in the list of per-phone partitions, and
  the provenance row for the new value.
- BRINGUP-M2.md: don't use Suspend in M2.7 until husky's U6;
  linux-omarchy-mobile#206 spelled out; tools/phone-smoke's report from
  the M2.6 root (test 18).
- ufs-probe.dtso: "If the board file's bootargs change".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derekross

Copy link
Copy Markdown
Owner

Thank you, @aninmucek. All five suggestions from #456 are in, and I checked each one. NV_BACKUP_EXTRA now matches the Pixel 8 Pro's list exactly, in both the descriptor and the package's copy. The overlay comment, the Suspend warning in M2.7 and the kernel PR reference all read right. The smoke report from the M2.6 root is just what I hoped for: the guard, the root and USB all pass on your own kernel, and the session rows fail as expected until M2.7.

Here, on this head: tools/pr-check passes, the package test gives 16 ok, tests/nv-backup and tests/device-overlays pass, tools/nv-backup -d akita --list takes the three extras, and the initramfs config packs with UFS_RW unchanged. CI is green, and the branch merges cleanly onto today's main.

About the two exynos-clkout lines: yes, please, but as their own small tools/phone-smoke PR, with a comment saying which SoCs they come from. That keeps this one about the 8a.

I'll merge this as 0.1.1, then update the 8a's row in DEVICES.md myself, as I promised on #456. One heads-up that needs nothing from you: #459 (the reboot-to --help fix) changes the shared reboot-to.c, and your package's test checks that its copy matches. I'll add the 8a's copy, as 0.1.2, when I merge that one.

Thanks again for another careful stage.

@derekross
derekross merged commit e11b15e into derekross:main Nov 8, 2026
2 checks passed
robertzas pushed a commit to robertzas/omarchy-mobile that referenced this pull request Nov 14, 2026
…up, and derekross#456's notes (derekross#509)

From the review of derekross#456:

- device.conf (and the package's copy): NV_BACKUP_EXTRA adds
  trusty_persist and trusty_userdata next to devinfo, as husky's
  package does since derekross#449, so tools/nv-backup --check shows when
  Android has written Trusty's storage.
- NOTES.md: trusty_userdata in the list of per-phone partitions, and
  the provenance row for the new value.
- BRINGUP-M2.md: don't use Suspend in M2.7 until husky's U6;
  linux-omarchy-mobile#206 spelled out; tools/phone-smoke's report from
  the M2.6 root (test 18).
- ufs-probe.dtso: "If the board file's bootargs change".

Co-Authored-By: Claude Opus 5.5 <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.

2 participants