Repository navigation
omamobile-device-akita 0.1.1: the Trusty partitions for tools/nv-backup, and #456's notes - #509
Conversation
…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>
|
Thank you, @aninmucek. All five suggestions from #456 are in, and I checked each one. Here, on this head: About the two 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 Thanks again for another careful stage. |
…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>
Follows #456, with its five non-blocking suggestions.
NV_BACKUP_EXTRAis nowdevinfo 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, sotools/nv-backup --checkshows when Android has written Trusty's storage.sda8,sda9), and neither is onUFS_RW.trusty_persistchanged while stock ran;trusty_userdatadidn't.trusty_userdatatoo.ufs-probe.dtso: it now reads "If the board file's bootargs change".linux-omarchy-mobile#206's head.tools/phone-smokefrom 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 at025e6a2, 2026-07-26T12:13Z.Packages: none found
The two "new dmesg errors" are the
exynos-clkoutlines 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 lefttools/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.test/all: 16 ok.tests/nv-backuppasses, andtools/nv-backup -d akita --listaccepts the three extras.tests/device-overlayspasses.tools/pr-check: passes.🤖 Generated with Claude Code