Your Android phone and your Windows PC, working as one. Local-first, end-to-end encrypted, no account.
Bluetooth HFP & PC Call Audio Architecture (docs/research/hfp.md)
1. Why Android Blocks Software Wi-Fi Call Audio Capture
On stock Android (non-rooted devices without OEM system-signature privileges), cellular and PSTN voice call audio (AudioAttributes.USAGE_VOICE_COMMUNICATION / AudioSource.VOICE_CALL / AudioSource.VOICE_DOWNLINK / AudioSource.VOICE_UPLINK) is hardware-routed by the baseband/modem DSP and the Android audio HAL:
CAPTURE_AUDIO_OUTPUT&CONTROL_INCALL_EXPERIENCEare signature/privileged permissions: Third-party apps, even when grantedREAD_PHONE_STATE,ANSWER_PHONE_CALLS,CALL_PHONE, orInCallServicerole, cannot read the downlink voice stream or inject uplink microphone PCM into an active cellular call over Wi-Fi/LAN.AudioPlaybackCapture(MediaProjection) excludes voice calls: Android 10+'sAudioPlaybackCaptureConfigurationexplicitly blocks capturingUSAGE_VOICE_COMMUNICATIONandUSAGE_VOICE_COMMUNICATION_SIGNALLING.- ADB
appops/ shell Grade B cannot bypass HAL voice routing: UnlikePROJECT_MEDIAorREAD_CLIPBOARD_IN_BACKGROUND, the restriction onVOICE_CALLaudio capture is enforced inAudioPolicyManager(CAP_SYS_ADMIN/AID_AUDIOSERVER/ privileged partition check) and in hardware DSP routing on Qualcomm/Tensor/Exynos platforms.
Consequently, streaming two-way cellular call audio over a custom Wi-Fi/QUIC socket is impossible for any user-installed Android application.
2. Why Public Windows WinRT / Win32 APIs Cannot Route Two-Way HFP Call Audio for Unpackaged Apps
We evaluated three Windows Bluetooth APIs for using the PC's microphone and speakers as a Bluetooth Hands-Free Profile (HFP) Hands-Free (HF) unit during a cellular call:
Windows.Media.Audio.AudioPlaybackConnection(Windows 10 2004+) is A2DP Media Sink Only:AudioPlaybackConnectionactivates the inbox Bluetooth A2DP Sink (AvrcpTransport/ media playback) role so a paired phone can stream media audio to the PC.- It is not a bidirectional Bluetooth HFP Hands-Free unit or Audio Gateway API: it does not establish a Synchronous Connection-Oriented (SCO / eSCO) voice channel, does not route the PC's microphone back to the phone's cellular call uplink, and does not switch the phone's
InCallServiceaudio route to Bluetooth Hands-Free.
Windows.ApplicationModel.Calls.PhoneLineTransportDevice(Broken / Locked Down on Windows 11 22H2+):- Microsoft originally introduced
PhoneLineTransportDevicefor companion apps to bind tobthhfenum.sys(Microsoft Bluetooth Hands-Free Profile Handsfree role). - Starting in Windows 11 22H2,
PhoneLineTransportDevice::RequestAccessAsync()andConnect()are gated behind internal Windows inbox broker checks (YourPhone.exe/PhoneExperienceHostsystem identity and restrictedphoneCallTransport/phoneCallOrigincapabilities) and fail withE_ACCESSDENIEDfor third-party unpackaged and self-signed applications (see MyPhone#26).
- Microsoft originally introduced
- Kernel Profile Driver Requirement (
BTH_PROFILE_DRIVER_INTERFACE):- Without access to the inbox
PhoneExperienceHostbroker, opening an HFP RFCOMM service-level connection (AT command channel) plus an eSCO bidirectional voice channel on Windows requires a WHQL-signed kernel-mode Bluetooth profile driver (bthport.sys/ KMDF) paired with a custom audio miniport driver.
- Without access to the inbox
Conclusion: Routing two-way cellular call audio through the PC's microphone and speakers is not possible with public Windows user-mode APIs. NectarLink therefore supports incoming call alerts, caller ID, answer/decline/hangup, dialer, call log, and (with Elevated mode) mute/speakerphone/hold/DTMF keypad controls on the PC while call voice audio remains on the phone (or a Bluetooth headset paired directly to the phone).
3. Scope of desktop/app/src/win/bt_hfp.rs
desktop/app/src/win/bt_hfp.rsreports no call audio, so the Calls page shows no "PC call audio" panel on Windows. Call audio stays on the phone.- It used to report the Bluetooth link to a paired device, which read as call audio on the PC and could name a paired headset instead of the phone (#86).
- On Linux,
desktop/app/src/linux/bt_hfp.rsroutes call audio through BlueZ and PipeWire or PulseAudio, and the panel is shown there.