Low power or screen lock: inspect saved segments before rerecording

Check saved material before deciding to record or compare again

Screen lock does not establish lost long notes. Existing UI says recording continues while locked and transcription runs with Yihu open. Long capture writes to disk and handles calls, resets and write errors. This is not zero-loss evidence for every power, shutdown, storage or accessory condition. Inspect saved material, pending transcription and actual gaps before rerecording; never fabricate missing words.

Different from foreground and route recovery

Foreground review checks lifecycle requests; route recovery checks engine events. Here whether a content gap exists and what a new capture should cover is the decision. No power setting, file cleanup, recording or recovery is performed.

Check Existing boundary Review Not established
Locked long notes UI describes recording continuation, foreground transcription Actual note/content state Uninterrupted under every battery/OS condition
Short speech Different cancellation path Prior request/result validity Long-note guarantees apply universally
No visible text Transcription differs from capture Saved audio/pending work No transcript means no capture
Written material Long capture retains prior writes Usable file and actual gap All unwritten buffers survive power loss
Call/service reset Interruption/saved-so-far notices Saved scope and errors Continuous audio or every file certified
Low power/write error No automatic downgrade promised here Power/storage/material state Automatic power-saving recapture/cloud restore
New capture Permission/safe conditions still apply Confirmed gap and manually labeled version Automatic merging/deduplication
Later handoff Original reservations/guards remain Prior effects and receipts Rerecording resets old attempts

Synthetic gap note

Known: sample segment A is usable. Unknown: whether B was saved. Pending transcription: lack of text cannot decide. Decision: inspect B before declaring complete loss or generating invented transition words.

No recording or low-power benchmark ran. Label recapture as a new version, not overwrite originals to imply continuity. Retain order/editorial notes separately. Uncertain prior handoffs require review, not repeated delivery.

FAQ

Does locking mean rerecord everything?

No. Long-note UI describes continued capture; inspect actual saved/pending state without generalizing to every path.

Does low-power mode automatically downsample safely?

No such feature/guarantee is asserted. Actual state/errors need review; no battery compatibility test is claimed.

Does no transcript mean no saved audio?

No. Saving and transcription differ; inspect material and foreground processing separately.

Does saved-so-far guarantee zero loss?

No. It does not establish all-buffer/every-condition recovery. Review actual usable scope.

Can a model fill missing meeting quotations?

Generated text is not recorded speech. Keep gaps and label any new recording/version.

Can recapture automatically deduplicate and resend?

No merging/deduplication/resend authority is added. Reservations and uncertainty rules remain.

Reading and source

Foreground state · Audio recovery · Segment review · One handoff · Start · Privacy

Lock/transcription UI · Disk writes/interruptions · Note state/handoff