Recording Stopped After a Call or Headset Switch? | Yihu
Keep saved audio, check words around the interruption, then compare the phone mic. Try Yihu’s no-mic audio preview and review privacy before setup. Park before car-audio checks.
Preview privacy before you try
The linked preview uses preset material, needs no login or microphone, and keeps edits only in the open page. Reloading resets edits. Optional read-aloud uses the browser’s voice service; usage analytics require consent.
Keep private originals in approved tools. In the app, on-device recognition and the destination’s storage, sync and access rules are separate steps. Review the installed version before using a source-described workflow. Read the data-flow guide
US listing verified; availability depends on your storefront. No Mac or self-signing for store installation. Bring your workspace address and account; the optional speech model is about 950 MB.
A 10-second starting check
Choose a situation for a next step, or open the sample now. No login or installation needed.
Open the audio self-check preview →Local question guide and preset samples; no hardware diagnosis, recording or live AI. “10 seconds” is a starting goal, not a measured user result.
Replay saved audio, mark gaps, then check the phone input
In a safe stationary setting, inspect saved results and errors. Replay the retained passage and mark missing words, numbers and negation around the interruption. Make a separate short phone-mic comparison without overwriting the original. Inspect the existing destination draft before recording or handing off again; pause on uncertainty. Do not operate while driving.
Try this order
- Separate playback from input. Play existing audio to check output; hearing it does not establish that the headset microphone is selected.
- Keep what was saved. After a call or switch, inspect saved audio, transcription and error state, and mark incomplete wording.
- Make a short comparison. Use the phone microphone with a synthetic phrase such as “Check three items tomorrow; do not send.” Then inspect headset input and the app’s microphone permission.
- Inspect the existing draft. If earlier text already reached the workbench, review that draft. Pause when the result is unclear rather than handing it off again.
Choose your next check
| What you see | First action | Before continuing |
|---|---|---|
| Playback is silent too | Check volume and output, then play an existing sample | Restore playback before testing input separately |
| Playback works but the headset records nothing | Compare a phone-mic sample; inspect input and permission | Use the actual new sample, not just the connection icon |
| A call or device switch stopped recording | Keep saved passages and inspect interruption messages | Check the last sentence, numbers, negation and gaps |
| A note was saved only up to a point | Play back the retained portion and mark the join | Keep the original; make a separate supplement if needed |
| Audio exists but the workbench has no text | Next inspect speech models and the intended editor | Locate the text before recording or handing off again |
Why inspect short speech and recording notes separately?
Short speech and notes use different capture and saving paths. After an input change, the source attempts recovery when its conditions allow, but can also stop and report an interruption. Identify which entry point you used, then inspect actual audio, text and saved results. A reconnected headset cannot replace that check.
FAQ
Why can I hear the headset but not record through it?
Playback and recording input need separate checks. Compare the phone microphone first, then inspect available input choices and microphone permission in the actual app.
Should I immediately record everything again?
Keep and play back saved passages first. Mark gaps and make a separate short supplement if needed, without overwriting the original or duplicating a draft.
Will recording automatically resume after a call?
Inspect the actual recording entry point and state. A call can interrupt capture; ending it does not establish recovery or completeness.
What if a note says it was saved only up to that point?
Play back the saved part, identify its last sentence and gaps, then decide whether to record a separate supplement. Review joins before organizing action items.
Can recovered audio hand off the earlier draft again?
Inspect the destination draft first. Audio recovery does not establish that the earlier handoff failed; review existing text instead of inserting it automatically again.
What should I include in a report?
Start with version, device model, event category and synthetic-sample results. Keep unique device identifiers, real recordings and customer text out of public feedback.
Continue with your task
Audio input questions and preview · Notes to action items · Voice drafts · Daily sales brief · Setup · Privacy
Implementation reference: recovery conditions and stop messages
Short speech attempts recovery under conditions including unchanged input format; oldDeviceUnavailable/noSuitableRouteForCategory notifications can stop capture. The internal debounce grace is two seconds, not reconnection latency or a recovery guarantee. Notes attempt writer retargeting; failures still require inspection of what was saved. This page supplies no headset, call-interruption or physical-device acceptance results.
Evidence: short-speech events and format checks, notes and interruptions.
