Near-field preference versus actual route: HFP allowance and capture policy

allowBluetoothHFP is permission to use a route, not proof it was selected or more accurate

Short-speech start reads the near-field preference. Enabled policy uses playAndRecord/voiceChat with mixWithOthers/allowBluetoothHFP; disabled policy uses record/default. Input graph policy branches too. These are implementation choices, not successful hardware activation, forced mic selection or measured accuracy. No noise-removal/mic-selection service is added.

Different from accessory suitability and recovery

Suitability checks environment; recovery checks capture events. Here stored preference, startup configuration, graph and actual route have separate evidence scopes. No setting or recording changes occur; long notes use another capture path.

Check Verified scope Manual review Not established
Preference Default true when absent Actual version/entry Default means system authorization
Enabled session playAndRecord/voiceChat Category/activation results Universal success or no echo
HFP allowBluetoothHFP permits Actual input route Paired headset mic forced
Mixing mixWithOthers policy Actual playback/output Unlimited web TTS/capture coexistence
Input graph Voice-processing policy etc. Actual configuration success Noise benchmark or speaker identification
Disabled record/default path Actual entry/state All accessories compatible
Startup snapshot Preference read at start This capture versus later settings Saved changes prove old capture rebound
Other capture Long notes separately implemented Actual entry/permission/format Every recording/page uses one policy

Synthetic policy review

Known: preference enabled. Unknown: selected HFP input and graph result. Report allowance only, not route selection or noise performance. Startup failures retain original handling rather than forcing mismatched pipelines.

voiceChat/voice processing names are not wind, distance, latency or accuracy SLAs. Actual route/safe environment need review without replacing device/OS acceptance or expanding service/target authority.

FAQ

Does true mean microphone permission granted?

No. Preference, system authorization and successful start differ.

Does HFP allowance force headset input?

No. Inspect the actual route, not pairing or options alone.

Does voiceChat guarantee cycling wind performance?

No benchmark/SLA is supplied; do not operate while driving/cycling.

Does mixWithOthers guarantee all page playback/capture coexistence?

No. Actual page/system/input/output boundaries still matter.

Do long notes use this exact policy?

Do not generalize short-speech configuration to the separate long-note path.

Does editing preferences prove old capture rebound?

No. Inspect startup, phase/route and original guards.

Reading and source

Accessory preflight · Route recovery · Permission/format · Start · Privacy

Policy/graph/start · Existing settings · Separate long-note path