From f7ab67e6a924000c471b2f0b30bca818833c218f Mon Sep 17 00:00:00 2001 From: SusieeTheFemboy <96988330+SusieeTheLinuxUser@users.noreply.github.com> Date: Wed, 4 Nov 2026 16:47:05 +0100 Subject: [PATCH 1/3] Docs: record the Google backup test results A rejected backup with the switch off just means there was nothing to send, so test with it on. Also records the emulator setup and that v1.1.7 isn't released yet. Co-Authored-By: Claude Opus 5.5 --- AGENTS.md | 23 +++++++++++++++++------ 1 file changed, 17 insertions(+), 6 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index ef434d3..81b10aa 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -19,11 +19,22 @@ feature. Do not trade it away for elegance or convenience. ## Current state (2026-11-04) -v1.1.7 comes from PR #22. `1.1.5-debug` was seen working on the phone on 2026-11-04: the app -opens, folder backup ran, and the Google backup switch appears. 1.1.6 moves that switch to a -file Android doesn't back up, so it reads as off after updating until it's turned on again. No real Google backup has been -confirmed yet, so check it with `bmgr` (see "Android's Google backup" below) when the phone is -next on USB. +v1.1.7 was merged to `master` (PR #22) but has no `v1.1.7` tag or stable release yet: the +user may release it later. `1.1.7-debug` is on the phone, with the Google backup switch off. + +Google backup on a stock Android 16 emulator (2026-11-04), with a signed-in spare account: +switch on, `bmgr backupnow` succeeds, about 36 KB. **Switch off, it reports "Transport +rejected package because it wasn't able to process it at the time" (-1002). That is expected: +it is what an empty backup looks like, not a bug.** Google states no reason, but every empty +run was rejected and every run with data succeeded, across debug and release builds and +faked installers. An agent wrongly blamed `GoogleBackupAgent` for this after only testing +with the switch off, so **always test with the switch on**. Not done yet: a run with the +switch on on the real phone, and any restore. Why 1.1.5 showed "no data backed up" with the +switch on is unproven (the debug assets, now excluded, are the best guess). + +The emulator is the AVD `dosekeeper-test` (Play Store image), and it opens from T3 Code's +Device panel. It is the place for anything that uninstalls, since it holds only fake data. +Always aim adb at it with `-s emulator-5554`, so nothing can reach the phone. ## Earlier: reboot audit (2026-09-24, late) @@ -320,7 +331,7 @@ the user's phone. `master` is branch-protected — see "Git workflow" below. likely reason Android showed "no data backed up" on the debug-installed phone. It adds no network permission or account, since Android does the upload. It isn't a Drive folder of readable files: that would need sign-in and network access. Switch seen on hardware; **a real - backup through it hasn't been confirmed.** Check with `adb shell bmgr backupnow dev.susiee.dosekeeper`, switch on and off. + backup through it is confirmed on an emulator only** (see "Current state"). Check with `adb shell bmgr backupnow dev.susiee.dosekeeper`, with the switch on: off is rejected as empty. - **Backup & restore** (`BackupStore.kt`, `lib/services/backup_*.dart`, `lib/ui/backup_page.dart`, app-bar backup icon) — built after the 2026-09-24 wipe. From 8d6e7589e4ba3116c6809e6736e8fd4b903467cb Mon Sep 17 00:00:00 2001 From: SusieeTheFemboy <96988330+SusieeTheLinuxUser@users.noreply.github.com> Date: Wed, 4 Nov 2026 16:55:02 +0100 Subject: [PATCH 2/3] Docs: mark the empty-backup reading as an inference Android doesn't document -1002 as meaning empty, and adb's -s only picks the target for one command, so check the target before anything destructive. Co-Authored-By: Claude Opus 5.5 --- AGENTS.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 81b10aa..c444027 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -24,9 +24,10 @@ user may release it later. `1.1.7-debug` is on the phone, with the Google backup Google backup on a stock Android 16 emulator (2026-11-04), with a signed-in spare account: switch on, `bmgr backupnow` succeeds, about 36 KB. **Switch off, it reports "Transport -rejected package because it wasn't able to process it at the time" (-1002). That is expected: -it is what an empty backup looks like, not a bug.** Google states no reason, but every empty -run was rejected and every run with data succeeded, across debug and release builds and +rejected package because it wasn't able to process it at the time" (-1002). This repo reads +that as an empty backup, not a bug, but that's an inference:** Android doesn't document -1002 +as meaning empty, and Google states no reason. On this emulator every empty run was rejected +and every run with data succeeded, across debug and release builds and faked installers. An agent wrongly blamed `GoogleBackupAgent` for this after only testing with the switch off, so **always test with the switch on**. Not done yet: a run with the switch on on the real phone, and any restore. Why 1.1.5 showed "no data backed up" with the @@ -34,7 +35,8 @@ switch on is unproven (the debug assets, now excluded, are the best guess). The emulator is the AVD `dosekeeper-test` (Play Store image), and it opens from T3 Code's Device panel. It is the place for anything that uninstalls, since it holds only fake data. -Always aim adb at it with `-s emulator-5554`, so nothing can reach the phone. +Before anything destructive, run `adb devices -l` and confirm the target. Put +`-s emulator-5554` on every command: it only picks the target for that one command. ## Earlier: reboot audit (2026-09-24, late) @@ -331,7 +333,7 @@ the user's phone. `master` is branch-protected — see "Git workflow" below. likely reason Android showed "no data backed up" on the debug-installed phone. It adds no network permission or account, since Android does the upload. It isn't a Drive folder of readable files: that would need sign-in and network access. Switch seen on hardware; **a real - backup through it is confirmed on an emulator only** (see "Current state"). Check with `adb shell bmgr backupnow dev.susiee.dosekeeper`, with the switch on: off is rejected as empty. + backup through it is confirmed on an emulator only** (see "Current state"). Check with `adb shell bmgr backupnow dev.susiee.dosekeeper`, with the switch on: on the emulator, off was rejected with -1002, which we read as an empty backup. - **Backup & restore** (`BackupStore.kt`, `lib/services/backup_*.dart`, `lib/ui/backup_page.dart`, app-bar backup icon) — built after the 2026-09-24 wipe. From d9feb1554e6396e4489e59b57dbcf4402b44a700 Mon Sep 17 00:00:00 2001 From: SusieeTheFemboy <96988330+SusieeTheLinuxUser@users.noreply.github.com> Date: Wed, 4 Nov 2026 17:01:07 +0100 Subject: [PATCH 3/3] Docs: name the device in the backup check The check is still needed on the phone as well as the emulator, so it takes a serial. Co-Authored-By: Claude Opus 5.5 --- AGENTS.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index c444027..d89ae34 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -36,7 +36,8 @@ switch on is unproven (the debug assets, now excluded, are the best guess). The emulator is the AVD `dosekeeper-test` (Play Store image), and it opens from T3 Code's Device panel. It is the place for anything that uninstalls, since it holds only fake data. Before anything destructive, run `adb devices -l` and confirm the target. Put -`-s emulator-5554` on every command: it only picks the target for that one command. +`-s emulator-5554` on every command meant for it: it only picks the target for that one +command. The other adb examples in this file are for the phone, so they don't use it. ## Earlier: reboot audit (2026-09-24, late) @@ -333,7 +334,7 @@ the user's phone. `master` is branch-protected — see "Git workflow" below. likely reason Android showed "no data backed up" on the debug-installed phone. It adds no network permission or account, since Android does the upload. It isn't a Drive folder of readable files: that would need sign-in and network access. Switch seen on hardware; **a real - backup through it is confirmed on an emulator only** (see "Current state"). Check with `adb shell bmgr backupnow dev.susiee.dosekeeper`, with the switch on: on the emulator, off was rejected with -1002, which we read as an empty backup. + backup through it is confirmed on an emulator only** (see "Current state"). Check with `adb -s shell bmgr backupnow dev.susiee.dosekeeper`, with the switch on: on the emulator, off was rejected with -1002, which we read as an empty backup. - **Backup & restore** (`BackupStore.kt`, `lib/services/backup_*.dart`, `lib/ui/backup_page.dart`, app-bar backup icon) — built after the 2026-09-24 wipe.