Your Android phone and your Windows PC, working as one. Local-first, end-to-end encrypted, no account.
Known Limitations
NectarLink aims to be completely transparent about what works out of the box, what requires an optional setup step, and what is restricted by the Windows 11 or Android operating systems or device hardware.
Summary of Platform and Hardware Limitations
| Area | Limitation | Why It Happens | Workaround or Status |
|---|---|---|---|
| Calls: Two-way voice audio on PC | You can see caller ID, answer, decline, dial, and (with Elevated) mute, hold, toggle speakerphone, and press keypad tones from your PC, but call voice audio stays on the phone. |
Android routes cellular call audio (VOICE_CALL) in hardware DSP and blocks software capture. On Windows 11 22H2+, Microsoft's PhoneLineTransportDevice Bluetooth HFP API is locked to Microsoft's inbox system broker (E_ACCESSDENIED for third-party apps), and AudioPlaybackConnection is one-way A2DP media only (see docs/research/hfp.md). |
Use the Speaker button in NectarLink's call bar (with Elevated) or keep Bluetooth headphones paired to your phone via multipoint Bluetooth. |
| Clipboard: Automatic background phone-to-PC sync | At Standard and Assist, copying text on your phone does not send it to your PC automatically in the background. |
Android 10 and newer block background apps from reading the system clipboard unless they run as the foreground app, the active keyboard (IME), or the shell user (UID 2000). |
Enable the Elevated power level once (Wireless Debugging) for automatic background phone-to-PC clipboard sync, or tap the Send clipboard Quick Settings tile, share sheet target, or widget. |
| Notifications: Sensitive text & OTPs on Android 15+ | At Standard and Assist, Android 15 and newer may redact notification text containing two-factor authentication codes from third-party notification listeners. |
Android 15's Enhanced Confirmation Mode withholds sensitive notification content unless the listener holds the privileged RECEIVE_SENSITIVE_NOTIFICATIONS appop. |
Enable the Elevated power level once. NectarLink's shell helper automatically grants RECEIVE_SENSITIVE_NOTIFICATIONS to NectarLink. |
| Messages: Third-party chat app threads | Unified Conversations from WhatsApp, Signal, Telegram, and RCS show messages that arrive while connected and let you reply via RemoteInput, but cannot load older historical chat databases or start a brand-new thread with a contact who has not messaged you. |
Android sandboxes each third-party chat app's internal SQLite database and does not expose a public API for reading historical third-party messages or RCS databases. | Open the chat app directly on your PC in its own app window (Elevated on Android 11+) when you need to browse old chat history or start a new chat. |
Windows Integration: System Share sheet (Win+Share) |
File Explorer's right-click Send to menu, Explorer context menu, taskbar Jump List, drag-and-drop, and --share CLI work on all installs, but appearing in the Windows 11 Win+Share popup requires package identity. There's no Win+W Widgets board widget yet. |
Windows 11 requires the windows.shareTarget extension to belong to a package signed with a trusted code-signing certificate (or have Windows Developer Mode enabled). |
Use File Explorer's right-click Send to menu, drag files to the Shelf (Ctrl+Alt+S), or turn on Windows Developer Mode and run setup again. If NectarLink still isn't in the Share sheet, sparse-package.log in its install folder says why. |
Mirroring: FLAG_SECURE windows |
Banking apps, password managers, and DRM-protected streaming video apps render black when mirrored at Standard or Assist. |
Android's window compositor strips FLAG_SECURE layers from standard MediaProjection virtual displays to protect credentials and DRM video. |
Normal apps and the Android home screen render normally as soon as you leave the protected window. |
Mirroring: Elevated /dev/uhid and REMOTE_SUBMIX on some OEM ROMs |
On some non-AOSP OEM Android ROMs, virtual physical keyboard/gamepad registration (/dev/uhid) or internal audio capture for apps that block playback capture (REMOTE_SUBMIX) may be denied to shell (UID 2000). |
Custom OEM SELinux policies sometimes restrict /dev/uhid or AUDIO_SOURCE_REMOTE_SUBMIX to system (UID 1000) or root rather than shell (UID 2000). |
NectarLink detects the permission denial automatically and falls back cleanly to standard InputManager key/touch injection and standard Android 10+ AudioPlaybackCapture. |
| Webcam: 4K sensor support and 8-bit SDR color | 4K (2160p) webcam streaming requires a physical phone camera sensor and hardware encoder that support 3840x2160 at 30 fps. Video is streamed in 8-bit SDR (NV12 / RGB32), not 10-bit HDR. |
Emulators and some front-facing phone cameras max out at 1080p. Windows Media Foundation virtual cameras in video conferencing apps expect standard 8-bit SDR formats (NV12 / RGB32), so 10-bit HDR is omitted to avoid tone-mapping mismatches. |
Use 1080p or 720p if your phone's selected camera lens does not support 4K capture. |
| Wake-on-LAN & BLE Proximity Wake: Hardware dependencies | Waking a powered-off PC over Wi-Fi rarely works, and Companion Device BLE proximity wake requires a Bluetooth LE radio on both the PC and the phone. | Most PC motherboards cut power to Wi-Fi cards during shutdown (S5), supporting Wake-on-LAN only over wired Ethernet or from low-power standby (S0ix/S3). Android emulators lack a Bluetooth LE controller. |
Connect your desktop PC via Ethernet and enable Wake on LAN in Windows Device Manager and BIOS/UEFI for reliable Wake-on-LAN. |
Detailed Notes on Key Platform Boundaries
1. Bluetooth Hands-Free Profile (HFP) Call Audio on Windows 11
Many users ask why NectarLink does not route two-way phone call audio through the PC's speakers and microphone over Bluetooth like Microsoft's pre-installed Phone Link app.
Microsoft's inbox PhoneExperienceHost (YourPhone.exe) uses an internal Windows system broker interface to bthhfenum.sys (Windows.ApplicationModel.Calls.PhoneLineTransportDevice). Starting in Windows 11 22H2, calling PhoneLineTransportDevice::RequestAccessAsync() or Connect() from any unpackaged or third-party application returns E_ACCESSDENIED because Windows checks for Microsoft's internal system identity and restricted capabilities (phoneCallTransport / phoneCallOrigin). Meanwhile, the public Windows.Media.Audio.AudioPlaybackConnection API only activates the one-way Bluetooth A2DP Sink profile for media playback, not a bidirectional eSCO voice channel for cellular calls. Implementing a third-party HFP Hands-Free unit on Windows 11 without Microsoft's restricted broker would require installing a custom WHQL-signed kernel-mode Bluetooth profile driver. Rather than bundling invasive kernel drivers or showing a control that fails silently, NectarLink provides full call signaling, caller ID, dialer, and Elevated in-call controls (mute, speakerphone, hold, keypad) while keeping voice audio on the phone.
2. Android Background Clipboard Access Without Elevated
Starting in Android 10, ClipboardManager.getPrimaryClip() returns null whenever the calling app does not have window focus. There is no runtime permission a user can grant in standard Android Settings to override this for a regular app. NectarLink solves this cleanly at both ends of the spectrum:
- If you stay at
StandardorAssist, you can send your phone's clipboard with one tap from the Send clipboard Quick Settings tile (which briefly brings a transparent NectarLink activity to the front to read the clip and closes immediately), the Android share sheet, the home-screen widget, or the app. - If you enable
Elevatedvia Wireless Debugging, NectarLink's local shell helper (UID 2000) registers a system clipboard listener through Binder (IClipboard) so everything you copy on your phone arrives on your PC automatically in the background, while still honoring Android 13+'sEXTRA_IS_SENSITIVEflag to never copy passwords.
3. Windows Sparse Package Identity for Win+Share
Unpackaged Win32/Qt applications on Windows 11 can register File Explorer context menus, Send to shortcuts, taskbar Jump Lists, global hotkeys, Notification Center toasts, Cloud Files (cfapi) sync roots, and Media Foundation virtual cameras (MFCreateVirtualCamera). All of those work out of the box in NectarLink.
However, Windows 11 restricts the system Win+Share dialog (windows.shareTarget) to applications that carry an MSIX or sparse Appx package identity signed by a certificate in the machine's Trusted People / Trusted Root store (or registered while Windows Developer Mode is turned on). NectarLink ships the share target and its AppxManifest.xml, and on standard unsigned builds Send to and the Shelf are the primary sharing entry points. A Win+W Widgets board widget isn't built yet: it also needs the Windows App SDK.