From 11df0189485fcc3e2374bd4579e24f3fbad340ed Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Tue, 3 Nov 2026 09:02:04 -0647 Subject: [PATCH 1/3] omamobile-device-tegu 0.2.9, device/tegu: the radio partitions tools/nv-backup reads tools/nv-backup refused the 9a ("names no NV_PARTS"), so its NV check had to be done by hand. The 9a has the 7 Pro's partitions, the ones its hand-made backups have held since 2026-10-21. With them, --check against the 2026-10-28 backup reads every NV partition the same after days of the modem running. The package's copy of the descriptor follows it, as its test asks. --- device/tegu/device.conf | 11 +++++++++++ packages/omamobile-device-tegu/device.conf | 11 +++++++++++ packages/omamobile-device-tegu/version | 2 +- 3 files changed, 23 insertions(+), 1 deletion(-) diff --git a/device/tegu/device.conf b/device/tegu/device.conf index 80bc14ffc..6882d9767 100644 --- a/device/tegu/device.conf +++ b/device/tegu/device.conf @@ -33,3 +33,14 @@ INITRAMFS_INIT=/initramfs/init PANEL_SIZE=1080x2424 # No BRINGUP_PROBE or SIMPLEFB_TRIG_CON: those gs201 display accesses do # not apply here. The prototype's G4 trigger handling needs its own change. + +# --- Radio backup --- +# What tools/nv-backup copies, read-only, before any radio work (AGENTS.md +# section 1), found on the palmtop by PARTNAME: the same partitions as the +# Pixel 7 Pro's, and the ones its hand-made backups have held since +# 2026-10-21. NV_PARTS never change under Linux (the guard keeps them +# read-only and the modem profile works on RAM copies), so --check fails +# when one differs. NV_BACKUP_EXTRA is copied for a full way back but +# changes: devinfo holds the bootloader's slot flags. +NV_PARTS="efs efs_backup modem_userdata persist modem_a modem_b" +NV_BACKUP_EXTRA="devinfo" diff --git a/packages/omamobile-device-tegu/device.conf b/packages/omamobile-device-tegu/device.conf index 80bc14ffc..6882d9767 100644 --- a/packages/omamobile-device-tegu/device.conf +++ b/packages/omamobile-device-tegu/device.conf @@ -33,3 +33,14 @@ INITRAMFS_INIT=/initramfs/init PANEL_SIZE=1080x2424 # No BRINGUP_PROBE or SIMPLEFB_TRIG_CON: those gs201 display accesses do # not apply here. The prototype's G4 trigger handling needs its own change. + +# --- Radio backup --- +# What tools/nv-backup copies, read-only, before any radio work (AGENTS.md +# section 1), found on the palmtop by PARTNAME: the same partitions as the +# Pixel 7 Pro's, and the ones its hand-made backups have held since +# 2026-10-21. NV_PARTS never change under Linux (the guard keeps them +# read-only and the modem profile works on RAM copies), so --check fails +# when one differs. NV_BACKUP_EXTRA is copied for a full way back but +# changes: devinfo holds the bootloader's slot flags. +NV_PARTS="efs efs_backup modem_userdata persist modem_a modem_b" +NV_BACKUP_EXTRA="devinfo" diff --git a/packages/omamobile-device-tegu/version b/packages/omamobile-device-tegu/version index a45be4627..1866a362b 100644 --- a/packages/omamobile-device-tegu/version +++ b/packages/omamobile-device-tegu/version @@ -1 +1 @@ -0.2.8 +0.2.9 From aedf0b5d91cecdf0982b6c692e3aeabce583182f Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Tue, 3 Nov 2026 14:30:18 -0647 Subject: [PATCH 2/3] device/tegu: metadata in the radio backup's extras The hand-made backups of 10-26 and 10-28 held metadata too. It changes (the bootloader and stock write it), so it goes with devinfo in NV_BACKUP_EXTRA: copied for a full way back, not checked. --- device/tegu/device.conf | 5 +++-- packages/omamobile-device-tegu/device.conf | 5 +++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/device/tegu/device.conf b/device/tegu/device.conf index 6882d9767..563bc756c 100644 --- a/device/tegu/device.conf +++ b/device/tegu/device.conf @@ -41,6 +41,7 @@ PANEL_SIZE=1080x2424 # 2026-10-21. NV_PARTS never change under Linux (the guard keeps them # read-only and the modem profile works on RAM copies), so --check fails # when one differs. NV_BACKUP_EXTRA is copied for a full way back but -# changes: devinfo holds the bootloader's slot flags. +# changes: devinfo holds the bootloader's slot flags, and metadata (in the +# hand-made backups too) is written by the bootloader and by stock. NV_PARTS="efs efs_backup modem_userdata persist modem_a modem_b" -NV_BACKUP_EXTRA="devinfo" +NV_BACKUP_EXTRA="devinfo metadata" diff --git a/packages/omamobile-device-tegu/device.conf b/packages/omamobile-device-tegu/device.conf index 6882d9767..563bc756c 100644 --- a/packages/omamobile-device-tegu/device.conf +++ b/packages/omamobile-device-tegu/device.conf @@ -41,6 +41,7 @@ PANEL_SIZE=1080x2424 # 2026-10-21. NV_PARTS never change under Linux (the guard keeps them # read-only and the modem profile works on RAM copies), so --check fails # when one differs. NV_BACKUP_EXTRA is copied for a full way back but -# changes: devinfo holds the bootloader's slot flags. +# changes: devinfo holds the bootloader's slot flags, and metadata (in the +# hand-made backups too) is written by the bootloader and by stock. NV_PARTS="efs efs_backup modem_userdata persist modem_a modem_b" -NV_BACKUP_EXTRA="devinfo" +NV_BACKUP_EXTRA="devinfo metadata" From 52ad7ab9191f0ab5f685f5b14f27f2c2f2472e73 Mon Sep 17 00:00:00 2001 From: W4HO <87742609+W4HO-ham@users.noreply.github.com> Date: Tue, 3 Nov 2026 15:30:22 -0647 Subject: [PATCH 3/3] device/tegu NOTES: the radio backup check with tools/nv-backup Today's --check against the 2026-10-28 backup, after the day's reboots: every NV partition and metadata read the same, and devinfo differs as expected. --- device/tegu/NOTES.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/device/tegu/NOTES.md b/device/tegu/NOTES.md index 58fa7422a..2d9ae83cd 100644 --- a/device/tegu/NOTES.md +++ b/device/tegu/NOTES.md @@ -13,6 +13,16 @@ hash/build ID; this dirty release is not a published kernel package. `[V]` marks verified observations; `[I]` marks an inference still to test. Raw captures, recordings, backups and vendor files remain off repository. +## 2026-11-03: the radio backup check with tools/nv-backup + +- [V] **NV partitions unchanged (`7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty`):** + `tools/nv-backup -d tegu --check` against the 2026-10-28 read-only + backup, after the day's reboots (several with the modem ONLINE through + #372's boot unit, two sysrq reboots after dead-storage wakes, and two + kernel pushes): `efs`, `efs_backup`, `modem_userdata`, `persist`, + `modem_a`, `modem_b` and `metadata` read the same; `devinfo` differs, as + it does after any boot-success mark or fastboot write. + ## 2026-11-02, evening: calls, Phone and Messages, echo, a restart and MMS All on the daily kernel (`7.3.0-rc6-omamobile-tegu-s2mpg15-m1-g991042e2eff3-dirty`)