[Feature Request] Allow deleting individual activity / steps records the way vitals can be deleted

[Albabit]

Following on from #60, which landed the READINGS section under each vital with a delete button per entry. That works well and I use it.

Activity / steps, doesn't have the equivalent. There's no way to see the individual step records behind a day's total, and no way to remove one.

Why it comes up :

The ring logs activity in 30 minute blocks, so a day's total is built from a couple of dozen records rather than one figure. Anything that inflates one of those blocks is stuck in the total for good.
Taking the ring off and carrying it, a car journey on a rough road, that kind of thing.

My original request on #60 said "heart rate, SpO2, etc.", so this is arguably the rest of that rather than something new.
I only noticed the gap once the vitals side was in and I went looking for the same thing under Activity.

Scope :

Same as #60. Deletion only, not editing, and ideally with the same confirmation step and the same persistence across re-syncs, since activity records come back from the ring on every sync exactly like history readings do.

Not urgent, and behind #66 in my own order of preference. Happy to test whenever.

[foureight84]

@Albabit — this is in a test build: v2.9.0+52-rc1 (PR #71). Prerelease, so the in-app updater won't push it to anyone else — install the universal APK over your current build.

You were right that this is the rest of #60 rather than something new, and it's built the same way: Activity → the RECORDS card under today's totals, one row per block, a delete button per row, a confirmation step, and a tombstone so a re-sync can't put it back.

Two things the code review on this PR turned up that are worth knowing before you test.

Deleting from today needed more than a tombstone. The tombstone stops the history path from writing the block back, which is the whole story for a past day. But the ring also pushes a live cumulative step count for today — seconds apart, and again on every reconnect — and the app ratchets the day up against it so today's count doesn't visibly drop every time the ring reconnects. That counter still contains the block you deleted, so the restated total went straight back up. It would have read to you as the delete silently failing, which is exactly the shape of thing you'd have reported. The day now remembers how much it removed and subtracts it from every later reading of the ring's counter. It's also why the feature is only offered on today: it's the only day whose counter is still moving.

Calories are dropped rather than corrected. A block carries steps and distance and no calorie field, so there's nothing to subtract from the ring's own daily calorie figure — and that figure did count the block you removed. Rather than invent a correction, the day falls back to the app's own calorie estimate, recomputed from the blocks that remain. So expect the calorie number on a day you've deleted from to shift, and to stop agreeing with the ring's. That's deliberate, but tell me if it reads wrong in practice.

What would confirm it:

• Delete a block from today, then wait for a live update or force a reconnect — the total must stay down. This is the one I'd most like a second pair of eyes on.
• Then force a full re-sync of that day and check it's still down.
• And that a day you haven't touched still counts up normally, since that live ratchet is load-bearing for everything else.

#66 is in the same build, since you'd said it sat ahead of this one in your own order — the HR and SpO₂ buttons are separate now, with the blood-pressure and HRV legs moved to a control of their own rather than riding along behind a single "Measure".

[Albabit]

@foureight84 ,
rc1 tested, including the one you wanted a second pair of eyes on. It holds.

I was on 2952 steps today. Deleted the last block, 213 steps, and the total dropped to 2739 as expected.

Then I tried to make it come back : disconnected the ring from the app's settings, turned Bluetooth off on the phone, turned it back on, restarted the app, reconnected the ring, and forced a full re-sync : Still 2739 ! 👍
The live cumulative counter didn't ratchet it back up.

The RECORDS card itself reads well, one row per block under today's totals, and the confirmation step is there.

I haven't yet had a day where I deleted something and then watched an untouched day alongside it over a longer stretch, so I can't speak to the ratchet still being load-bearing for everything else beyond this session.
Happy to keep an eye on it over the next few days and say if anything drifts.