Your Android phone and your Windows PC, working as one. Local-first, end-to-end encrypted, no account.
NectarLink: the brand's spelling, everywhere people read it
Beee2c46ca38352
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.ymlindex 191854a..2f03583 100644--- a/.github/ISSUE_TEMPLATE/bug_report.yml+++ b/.github/ISSUE_TEMPLATE/bug_report.yml@@ -5,7 +5,7 @@ body:- type: markdownattributes:value: |- Thanks for reporting. Nectarlink is in early development, so please check+ Thanks for reporting. NectarLink is in early development, so please checkthe open issues first. Security problems go through SECURITY.md instead.- type: textareaid: what-happened@@ -36,7 +36,7 @@ body:- type: inputid: versionsattributes:- label: Nectarlink versions+ label: NectarLink versionsdescription: Desktop app and Android app (commit hash if built from source).- type: textareaid: logsdiff --git a/.github/workflows/release.yml b/.github/workflows/release.ymlindex da1df60..2989edb 100644--- a/.github/workflows/release.yml+++ b/.github/workflows/release.yml@@ -133,7 +133,7 @@ jobs:run: |# The release's name, if Cargo.toml gives one ([workspace.metadata.release]).name=$(awk '/^\[workspace.metadata.release\]/{f=1;next} /^\[/{f=0} f && /^name = /{print $3}' source/Cargo.toml | tr -d '"')- title="Nectarlink ${GITHUB_REF_NAME#v}${name:+ $name}"+ title="NectarLink ${GITHUB_REF_NAME#v}${name:+ $name}"cd filessha256sum *.exe *.apk > SHA256SUMS.txtcat SHA256SUMS.txtdiff --git a/CHANGELOG.md b/CHANGELOG.mdindex cd2f57b..f425249 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -1,6 +1,6 @@# Changelog-All notable changes to Nectarlink. Versions follow+All notable changes to NectarLink. Versions follow[semantic versioning](https://semver.org); before 1.0, a minor version maychange things that need a step from you, and its notes say so.@@ -18,7 +18,7 @@ slow or unsteady connections and show how far they are.Both are listed with their SHA-256 hashes in [SHA256SUMS.txt](https://github.com/thtbee/nectarlink/releases/download/v0.1.3/SHA256SUMS.txt).Installed copies update themselves. If **Update** in 0.1.2 or earlier closes-Nectarlink and nothing happens, install this version from the link above+NectarLink and nothing happens, install this version from the link aboveonce; updates after it work from the app.### New@@ -41,13 +41,13 @@ once; updates after it work from the app.### Fixed-- **Updating the Windows app.** Clicking **Update** closed Nectarlink right+- **Updating the Windows app.** Clicking **Update** closed NectarLink rightaway, and the download that followed in the background could time out on aslow connection to GitHub's download server. The update then failed with no- sign of it, and Nectarlink reopened only minutes later. Now Nectarlink stays+ sign of it, and NectarLink reopened only minutes later. Now NectarLink staysopen while it downloads, shows the progress in **Settings › Connection &About**, resumes a download that was cut off, and closes only once the- update is downloaded and checked. If an update doesn't install, Nectarlink+ update is downloaded and checked. If an update doesn't install, NectarLinkreopens and says so.- Slow responses from GitHub no longer fail update checks or downloads: theWindows app waits longer and tries again.@@ -74,16 +74,16 @@ Installed copies update themselves.### Fixed- **The phone reconnects after an update or a restart.** Android closes an- app while it updates, and nothing brought Nectarlink's connection back until+ app while it updates, and nothing brought NectarLink's connection back untilthe app was opened again, so the PC showed the phone as gone. The connectionnow comes back on its own, after an update and after the phone restarts. Anotification says the update is done; tapping it opens the app.- **Check for updates in the phone's Settings shows what it found**: that- Nectarlink is up to date, or the update with its **Update** button and+ NectarLink is up to date, or the update with its **Update** button andprogress, or why it couldn't check. Before, the button greyed out and nothingappeared.- **Allowing installs continues the update.** When Android first asks to let- Nectarlink install updates, coming back from that screen now carries on with+ NectarLink install updates, coming back from that screen now carries on withthe update instead of staying on **Allow**.- **Phone downloads resume.** A dropped or changed connection no longer failsthe update: the download waits for the network and continues where it@@ -93,7 +93,7 @@ Installed copies update themselves.leaves the update ready to install instead of reporting an error.- **The PC app comes to the front after updating.** It reopened behind otherwindows; now it comes forward and a notification says it's updated. The same- fix brings the window forward when Nectarlink is opened while already+ fix brings the window forward when NectarLink is opened while alreadyrunning.## 0.1.1 (2026-10-15)@@ -113,7 +113,7 @@ Installed copies update themselves.### Changed-- **Sharing from the phone sends right away.** Choosing Nectarlink in the+- **Sharing from the phone sends right away.** Choosing NectarLink in theAndroid share sheet starts the transfer immediately, with no Flick to sendcard or Undo countdown. With more than one PC connected, you pick one first.Progress shows in a notification with a **Cancel** button, followed by a@@ -143,8 +143,8 @@ Installed copies update themselves.## 0.1.0 "Pollen" (2026-10-14)-The first public release of Nectarlink: the Windows app, the Android app and-the `nectarlink` command-line client. Nectarlink connects an Android phone and+The first public release of NectarLink: the Windows app, the Android app and+the `nectarlink` command-line client. NectarLink connects an Android phone anda Windows 11 PC directly over your network or a USB cable, end-to-endencrypted, with no account and no cloud service.@@ -166,7 +166,7 @@ info**, then **Run anyway**.- **Installer.** A setup window of its own, light or dark to match Windows.One click installs, with one administrator prompt. Setup adds the WindowsFirewall rule for local connections, Start menu and desktop shortcuts,- **Send to** in File Explorer and the update task, and starts Nectarlink+ **Send to** in File Explorer and the update task, and starts NectarLinkwith Windows. **What this installs** on thefirst screen lists all of it. The last screen shows a QR code that opens theAndroid app's download page.@@ -180,7 +180,7 @@ info**, then **Run anyway**.- **Features Guide** in both apps: every feature, whether it works with yourpaired phone right now, what would enable it, and a **Show me** button thatgoes to its control.-- **Pairing** by QR code (from the Nectarlink app or any camera app), by+- **Pairing** by QR code (from the NectarLink app or any camera app), bypicking a nearby device and comparing a 6-digit code, or automatically overa USB cable. Pairing links opened from other apps ask before pairing.- **Power levels** on Android:@@ -278,7 +278,7 @@ info**, then **Run anyway**.### Camera and sound-- **Phone as a webcam** through the Nectarlink Webcam virtual camera, in+- **Phone as a webcam** through the NectarLink Webcam virtual camera, inZoom, Teams, Meet, OBS and the Camera app, at up to 4K where the phonesupports it, with lens and zoom controls.- **Continuity Camera**: take a photo or scan a document with the phone, with@@ -337,7 +337,7 @@ testing. It builds on Windows and Linux.### Privacy and security- Local-first: devices connect directly over the local network or USB.- Nothing passes through a Nectarlink server, and there is no account.+ Nothing passes through a NectarLink server, and there is no account.- Every connection is QUIC with TLS 1.3, authenticated with Ed25519 devicekeys exchanged at pairing. Keys are protected by Windows DPAPI and theAndroid Keystore.diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex a037320..2098dfa 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -1,6 +1,6 @@-# Contributing to Nectarlink+# Contributing to NectarLink-Thank you for helping with Nectarlink. The project is young, so the codebase+Thank you for helping with NectarLink. The project is young, so the codebaseand these guidelines still change often.## Before you start@@ -13,7 +13,7 @@ and these guidelines still change often.## Sign your commits (DCO)-Nectarlink uses the [Developer Certificate of Origin](DCO.txt) instead of a+NectarLink uses the [Developer Certificate of Origin](DCO.txt) instead of aCLA. By signing off, you certify that you wrote the change or otherwise havethe right to submit it under the project's licenses.@@ -65,5 +65,5 @@ These come from the plan and will grow into a full style guide:## Reporting bugsOpen an issue with your Windows build, phone model, Android version, and the-Nectarlink versions on both sides. Security problems go through+NectarLink versions on both sides. Security problems go through[SECURITY.md](SECURITY.md) instead, never a public issue.diff --git a/Cargo.toml b/Cargo.tomlindex 2e44316..262c3e2 100644--- a/Cargo.toml+++ b/Cargo.toml@@ -16,7 +16,7 @@ members = [version = "0.1.3"edition = "2024"rust-version = "1.97"-authors = ["The Nectarlink contributors"]+authors = ["The NectarLink contributors"]repository = "https://github.com/thtbee/nectarlink"# Each release's name, from a bee's life (0.1 Pollen, …); the releasediff --git a/LICENSE b/LICENSEindex 57fc310..6c7bbe6 100644--- a/LICENSE+++ b/LICENSE@@ -1,4 +1,4 @@-Nectarlink is distributed under several licenses, depending on the part of the+NectarLink is distributed under several licenses, depending on the part of theproject. The full license texts are in the LICENSES/ directory.Part of the project License@@ -26,7 +26,7 @@ example:When a file's header and this table disagree, the file's header applies.-The Nectarlink name and logo are not licensed under any of the licenses above.+The NectarLink name and logo are not licensed under any of the licenses above.See TRADEMARKS.md.-Copyright (C) 2026 The Nectarlink contributors.+Copyright (C) 2026 The NectarLink contributors.diff --git a/LICENSES/APP-STORE-EXCEPTION.md b/LICENSES/APP-STORE-EXCEPTION.mdindex 4950734..4d4dc53 100644--- a/LICENSES/APP-STORE-EXCEPTION.md+++ b/LICENSES/APP-STORE-EXCEPTION.md@@ -1,13 +1,13 @@# Additional permission under GNU GPL version 3, section 7-This additional permission applies to every part of Nectarlink that is licensed+This additional permission applies to every part of NectarLink that is licensedunder the GNU General Public License version 3 or later ("the GPL"), as listedin the top-level `LICENSE` file.## PermissionAs an additional permission under section 7 of the GPL, the copyright holders-of Nectarlink give you permission to convey a covered work, or a work based on+of NectarLink give you permission to convey a covered work, or a work based onit, through an application store or similar distribution platform (for examplethe Apple App Store, the Mac App Store, the Microsoft Store or Google Play),even if that platform's terms of service or technical measures add@@ -33,7 +33,7 @@ This permission applies only if all of the following are true:This permission only relaxes the restrictions described above. It does notremove or reduce any right that the GPL grants to recipients. You may removethis additional permission from your own copies or modified versions, as-allowed by section 7 of the GPL. Contributions to Nectarlink are accepted under+allowed by section 7 of the GPL. Contributions to NectarLink are accepted underthe GPL together with this additional permission._Note: this text was drafted for the project and has not yet been reviewed by adiff --git a/README.md b/README.mdindex a6f08e7..76d0989 100644--- a/README.md+++ b/README.md@@ -2,7 +2,7 @@<img src="assets/brand/icon.svg" alt="" width="96" height="96">-# Nectarlink+# NectarLink**Your Android phone and your Windows PC, working as one.**@@ -10,7 +10,7 @@ Notifications, messages, calls, clipboard, files, photos, screen mirroring andphone apps in windows, between Android and Windows 11. Free and open source.Local-first, end-to-end encrypted, no account and no cloud.-Hi, I'm Bee, and yes, a bee built an app called Nectarlink. I build cool stuff+Hi, I'm Bee, and yes, a bee built an app called NectarLink. I build cool stuffin the open on [𝕏 @thtbee_](https://x.com/thtbee_), so come see what's next.Feedback, bugs or ideas? DM me directly.@@ -22,12 +22,12 @@ Feedback, bugs or ideas? DM me directly.</div><p align="center">- <img src="docs/screenshots/desktop-glass-home.png" alt="Nectarlink for Windows: Home with the phone's notifications and music playing, Glass theme" width="880">+ <img src="docs/screenshots/desktop-glass-home.png" alt="NectarLink for Windows: Home with the phone's notifications and music playing, Glass theme" width="880"></p>-## Why Nectarlink+## Why NectarLink-Nectarlink came out of my own frustration. I kept juggling Phone Link for+NectarLink came out of my own frustration. I kept juggling Phone Link fornotifications and messages, KDE Connect for the clipboard and LocalSend forfiles, and always wanted one app that did all of it. So I made one.@@ -38,8 +38,8 @@ of new features I wanted that I think you'll enjoy having too.| | Download | Needs ||---|---|---|-| **Windows** | [Installer (.exe)](https://github.com/thtbee/nectarlink/releases/latest) | Windows 11, 64-bit |-| **Android** | [App (.apk)](https://github.com/thtbee/nectarlink/releases/latest) | Android 8.0 or newer |+| **Windows** | [Installer (.exe)](https://github.com/thtbee/nectarlink/releases/download/v0.1.3/Nectarlink-0.1.3-x64-setup.exe) | Windows 11, 64-bit |+| **Android** | [App (.apk)](https://github.com/thtbee/nectarlink/releases/download/v0.1.3/Nectarlink-0.1.3-android.apk) | Android 8.0 or newer |Both apps update themselves from GitHub Releases and check every downloadagainst its SHA-256 sums.@@ -51,9 +51,9 @@ against its SHA-256 sums.## Get started-1. Install Nectarlink on your PC and on your phone.+1. Install NectarLink on your PC and on your phone.2. On the PC, the setup walkthrough shows a QR code. Scan it with the phone- (from the Nectarlink app or any camera app), or pick the PC from the phone's+ (from the NectarLink app or any camera app), or pick the PC from the phone'slist of nearby devices and compare a 6-digit code. A USB cable works too.3. Allow what you want to share. Every feature has its own switch per device,and the sensitive ones are off until you turn them on.@@ -262,5 +262,5 @@ open a public issue.- Core libraries: [MPL-2.0](LICENSES/MPL-2.0.txt)- Protocol specification and documentation: [CC BY 4.0](LICENSES/CC-BY-4.0.txt)-See [LICENSE](LICENSE) for which license applies where. The Nectarlink name and+See [LICENSE](LICENSE) for which license applies where. The NectarLink name andlogo are covered by the [trademark policy](TRADEMARKS.md).diff --git a/SECURITY.md b/SECURITY.mdindex 65ea135..4d184e8 100644--- a/SECURITY.md+++ b/SECURITY.md@@ -1,6 +1,6 @@# Security policy-Nectarlink handles sensitive data such as notifications, messages, one-time+NectarLink handles sensitive data such as notifications, messages, one-timecodes and files, so security reports are taken seriously.## Reporting a vulnerabilitydiff --git a/TRADEMARKS.md b/TRADEMARKS.mdindex bb7572f..2ad1ddc 100644--- a/TRADEMARKS.md+++ b/TRADEMARKS.md@@ -1,26 +1,26 @@# Trademark policy-The Nectarlink source code is open source, but the **Nectarlink name and+The NectarLink source code is open source, but the **NectarLink name andlogo** are not covered by the software licenses. This policy exists so that-people can trust that something called "Nectarlink" really comes from this+people can trust that something called "NectarLink" really comes from thisproject.## You're welcome to-- Use the name "Nectarlink" to refer to the project, for example in articles,+- Use the name "NectarLink" to refer to the project, for example in articles,reviews, tutorials and videos.-- Say that your software is "compatible with Nectarlink" or "based on- Nectarlink", as long as that's accurate.-- Redistribute unmodified official builds under the Nectarlink name.+- Say that your software is "compatible with NectarLink" or "based on+ NectarLink", as long as that's accurate.+- Redistribute unmodified official builds under the NectarLink name.## Please don't-- Distribute a **modified** version under the Nectarlink name or logo. Forks+- Distribute a **modified** version under the NectarLink name or logo. Forksare welcome, but they need their own name and logo.- Use the name or logo in a way that suggests the project endorses you, yourproduct or your service when it doesn't.- Use the name or a confusingly similar one in app store listings, domain names- or social media accounts for software that isn't the official Nectarlink.+ or social media accounts for software that isn't the official NectarLink.## Questionsdiff --git a/android/README.md b/android/README.mdindex dfc590d..771de6d 100644--- a/android/README.md+++ b/android/README.md@@ -1,4 +1,4 @@-# Nectarlink for Android+# NectarLink for AndroidKotlin + Jetpack Compose (Material 3) on top of the shared Rust core,called through UniFFI (`core/nectarlink-ffi`).diff --git a/android/app/src/main/AndroidManifest.xml b/android/app/src/main/AndroidManifest.xmlindex 4b65198..8a4c0b8 100644--- a/android/app/src/main/AndroidManifest.xml+++ b/android/app/src/main/AndroidManifest.xml@@ -28,7 +28,7 @@phone's sound while mirrored (playback capture, with the screen share's consent). --><uses-permission android:name="android.permission.RECORD_AUDIO" /><!-- Elevated: turning wireless debugging back on after a reboot or a new- Wi-Fi network. Not grantable to apps; Nectarlink grants it to itself+ Wi-Fi network. Not grantable to apps; NectarLink grants it to itselfthrough the shell once the user has paired it with wireless debugging. --><uses-permissionandroid:name="android.permission.WRITE_SECURE_SETTINGS"@@ -48,7 +48,7 @@<!-- Asking to run unrestricted in the background: phones such as Samsung'sotherwise freeze the app, and PCs can't reach it. --><uses-permission android:name="android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS" />- <!-- Companion Device Manager association: lets Android wake Nectarlink when+ <!-- Companion Device Manager association: lets Android wake NectarLink whena paired PC's BLE proximity beacon appears nearby. --><uses-featureandroid:name="android.software.companion_device_setup"@@ -61,7 +61,7 @@android:usesPermissionFlags="neverForLocation" /><!-- Installing its own updates from GitHub releases (the user allows it once). --><uses-permission android:name="android.permission.REQUEST_INSTALL_PACKAGES" />- <!-- Updates of Nectarlink itself without a prompt (Android 12+), when turned on in Settings. -->+ <!-- Updates of NectarLink itself without a prompt (Android 12+), when turned on in Settings. --><uses-permission android:name="android.permission.UPDATE_PACKAGES_WITHOUT_USER_ACTION" /><!-- Calls, shown on paired PCs, with the caller's number and contact(asked for in the app). The call itself stays on the phone. -->@@ -172,7 +172,7 @@<category android:name="android.intent.category.DEFAULT" /><data android:mimeType="*/*" /></intent-filter>- <!-- Map locations (geo: URIs) opened with Nectarlink go straight to the PC. -->+ <!-- Map locations (geo: URIs) opened with NectarLink go straight to the PC. --><intent-filter><action android:name="android.intent.action.VIEW" /><category android:name="android.intent.category.DEFAULT" />@@ -193,7 +193,7 @@android:name=".update.AppUpdater$InstallResult"android:exported="false" />- <!-- Reconnects after the phone restarts or Nectarlink updates. -->+ <!-- Reconnects after the phone restarts or NectarLink updates. --><receiverandroid:name=".service.StartupReceiver"android:exported="false">diff --git a/android/app/src/main/kotlin/app/nectarlink/android/calls/CallCompanion.kt b/android/app/src/main/kotlin/app/nectarlink/android/calls/CallCompanion.ktindex 0b082aa..d1189e6 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/calls/CallCompanion.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/calls/CallCompanion.kt@@ -12,8 +12,8 @@ import android.telecom.VideoProfileimport app.nectarlink.core.CallControls/**- * Nectarlink as a calling companion: Telecom binds this while there are- * calls, without Nectarlink being the phone app, so a PC can mute, switch to+ * NectarLink as a calling companion: Telecom binds this while there are+ * calls, without NectarLink being the phone app, so a PC can mute, switch to* the speaker, hold, and press keys on the call in progress. It shows* nothing on the phone. Telecom binds companions that hold* MANAGE_ONGOING_CALLS (Android 12+), an app-op Elevated's shell grants.diff --git a/android/app/src/main/kotlin/app/nectarlink/android/clipboard/PhoneClipboard.kt b/android/app/src/main/kotlin/app/nectarlink/android/clipboard/PhoneClipboard.ktindex 13026ef..d7985eb 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/clipboard/PhoneClipboard.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/clipboard/PhoneClipboard.kt@@ -57,7 +57,7 @@ object PhoneClipboard {data object Unreadable : ImageResult}- /** True when `(text, html)` was written to the phone clipboard by Nectarlink itself within the last few seconds. */+ /** True when `(text, html)` was written to the phone clipboard by NectarLink itself within the last few seconds. */fun isRecentEcho(text: String, html: String? = null): Boolean {val last = lastWrittenText ?: return falseif (normalizeClipText(last) != normalizeClipText(text)) return false@@ -66,7 +66,7 @@ object PhoneClipboard {return true}- /** True when `uri` was placed on the phone clipboard by Nectarlink itself within the last few seconds. */+ /** True when `uri` was placed on the phone clipboard by NectarLink itself within the last few seconds. */fun isRecentUriEcho(uri: Uri): Boolean {val last = lastWrittenUri ?: return falseif (last != uri) return false@@ -205,14 +205,14 @@ object PhoneClipboard {* immediately paste it into chat or email apps, while recording the URI to suppress* clipboard echo back to the PC.*/- fun setFileUri(context: Context, uri: Uri, label: String = "Nectarlink file"): Boolean = runCatching {+ fun setFileUri(context: Context, uri: Uri, label: String = "NectarLink file"): Boolean = runCatching {appContext = context.applicationContextlastWrittenUri = urilastWrittenText = uri.toString()lastWrittenHtml = nulllastWrittenAtMs = android.os.SystemClock.elapsedRealtime()val mgr = manager(context) ?: return false- val clip = ClipData.newUri(context.contentResolver, label.ifBlank { "Nectarlink file" }, uri)+ val clip = ClipData.newUri(context.contentResolver, label.ifBlank { "NectarLink file" }, uri)mgr.setPrimaryClip(clip)true}.getOrElse {@@ -221,7 +221,7 @@ object PhoneClipboard {}/** Overload using the cached application [Context] when available. */- fun setFileUri(uri: Uri, label: String = "Nectarlink file"): Boolean {+ fun setFileUri(uri: Uri, label: String = "NectarLink file"): Boolean {val ctx = appContext ?: return falsereturn setFileUri(ctx, uri, label)}diff --git a/android/app/src/main/kotlin/app/nectarlink/android/companion/PcCompanion.kt b/android/app/src/main/kotlin/app/nectarlink/android/companion/PcCompanion.ktindex 8880a08..383ef9b 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/companion/PcCompanion.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/companion/PcCompanion.kt@@ -13,7 +13,7 @@ import android.os.Buildimport java.util.concurrent.Executor/**- * Companion Device Manager (CDM) integration for waking Nectarlink when a+ * Companion Device Manager (CDM) integration for waking NectarLink when a* paired PC's BLE proximity beacon (`NCTR\x01` + 8-byte device ID prefix) is* nearby, and granting OS-level background execution / foreground-service start* exemptions while associated.@@ -56,7 +56,7 @@ object PcCompanion {/*** Builds the scan filter mask matching [buildBeaconPayload]: 13 `0xFF`* bytes when a specific 8-byte device ID prefix is present, or 5 `0xFF`- * bytes to match any Nectarlink PC beacon.+ * bytes to match any NectarLink PC beacon.*/fun buildBeaconMask(hasDeviceId: Boolean): ByteArray =ByteArray(if (hasDeviceId) 13 else 5) { 0xFF.toByte() }diff --git a/android/app/src/main/kotlin/app/nectarlink/android/core/BackgroundAccess.kt b/android/app/src/main/kotlin/app/nectarlink/android/core/BackgroundAccess.ktindex 159b971..0a003fd 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/core/BackgroundAccess.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/core/BackgroundAccess.kt@@ -41,14 +41,14 @@ enum class OemBrand {/*** Running unrestricted in the background. Without it, battery savers (and- * OEM background app killers in particular) pause Nectarlink between events,+ * OEM background app killers in particular) pause NectarLink between events,* so a PC's requests (replies, dismissals, find my phone) time out.*/object BackgroundAccess {fun isUnrestricted(context: Context): Boolean =context.getSystemService(PowerManager::class.java)?.isIgnoringBatteryOptimizations(context.packageName) ?: true- /** Android's prompt to let Nectarlink run unrestricted. */+ /** Android's prompt to let NectarLink run unrestricted. */@SuppressLint("BatteryLife") // A companion that must stay reachable is the case this exists for.fun requestIntent(context: Context): Intent =Intent(Settings.ACTION_REQUEST_IGNORE_BATTERY_OPTIMIZATIONS, "package:${context.packageName}".toUri())@@ -169,7 +169,7 @@ object BackgroundAccess {/*** Returns the first OEM battery/autostart settings intent that resolves on- * this phone, or falls back to Nectarlink's App info screen (`ACTION_APPLICATION_DETAILS_SETTINGS`).+ * this phone, or falls back to NectarLink's App info screen (`ACTION_APPLICATION_DETAILS_SETTINGS`).*/fun oemSettingsIntent(context: Context, oem: OemBrand = detectOem()): Intent {val pm = context.packageManager@@ -189,7 +189,7 @@ object BackgroundAccess {.addFlags(Intent.FLAG_ACTIVITY_NEW_TASK)/**- * Whether Nectarlink was installed other than by an app store (from a+ * Whether NectarLink was installed other than by an app store (from a* file, a browser download, or another installer). Android 13 and newer* may then hold back some settings ("restricted settings") until the user* allows them from App info. There is no public way to read that statediff --git a/android/app/src/main/kotlin/app/nectarlink/android/core/CoreState.kt b/android/app/src/main/kotlin/app/nectarlink/android/core/CoreState.ktindex 092511b..9b4eaf3 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/core/CoreState.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/core/CoreState.kt@@ -181,9 +181,9 @@ data class CoreState(val pairing: PairingState = PairingState.Idle,/** Name of the device making this phone ring, or null. */val ringingFrom: String? = null,- /** Whether the user let Nectarlink read notifications (to mirror them). */+ /** Whether the user let NectarLink read notifications (to mirror them). */val notificationAccess: Boolean = false,- /** Whether Android lets Nectarlink reach the local network (Android 17). */+ /** Whether Android lets NectarLink reach the local network (Android 17). */val localNetwork: Boolean = true,/** Whether the Elevated helper runs (wireless debugging). */val elevated: Boolean = false,@@ -191,17 +191,17 @@ data class CoreState(val inputAccess: Boolean = false,/** Whether a paired PC tried to inject mouse/keyboard input while input access is off. */val remoteInputRequested: Boolean = false,- /** Whether the user let Nectarlink read and send texts (for PCs). */+ /** Whether the user let NectarLink read and send texts (for PCs). */val smsAccess: Boolean = false,- /** Whether the user let Nectarlink follow and answer calls (to show them on PCs). */+ /** Whether the user let NectarLink follow and answer calls (to show them on PCs). */val callAccess: Boolean = false,- /** Whether the user let Nectarlink read contacts (for PCs). */+ /** Whether the user let NectarLink read contacts (for PCs). */val contactsAccess: Boolean = false,- /** Whether the user let Nectarlink see the phone's photos (to show them on PCs). */+ /** Whether the user let NectarLink see the phone's photos (to show them on PCs). */val photoAccess: Boolean = false,/** Whether Android 14+ "Select photos and videos" partial access is active. */val photoPartialAccess: Boolean = false,- /** Whether Android lets Nectarlink run unrestricted in the background. */+ /** Whether Android lets NectarLink run unrestricted in the background. */val backgroundUnrestricted: Boolean = true,/** Whether Companion Device Manager association is active for waking when a PC BLE beacon is nearby. */val companionAssociated: Boolean = false,diff --git a/android/app/src/main/kotlin/app/nectarlink/android/core/SystemMonitors.kt b/android/app/src/main/kotlin/app/nectarlink/android/core/SystemMonitors.ktindex 85b78f6..dfcc890 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/core/SystemMonitors.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/core/SystemMonitors.kt@@ -76,7 +76,7 @@ private fun parseSecureOverlaySeed(context: Context): UInt? = runCatching {/*** Reads the phone's active theme seed color (`0xFFRRGGBB` ARGB):* 1. If the user selected "Media artwork color" or a preset seed ("honey",- * "lavender", "ocean", "sage") in the Nectarlink Android app's Appearance+ * "lavender", "ocean", "sage") in the NectarLink Android app's Appearance* settings, uses that seed so "My phone's colors" on the PC matches the* phone app's chosen theme.* 2. When Dynamic Color is enabled on Android 12+ (`API 31+`), reads the@@ -739,7 +739,7 @@ class NetworkMonitor(context: Context, private val onChange: () -> Unit) {}/**- * Listens for Nectarlink appearance preference changes, media artwork color+ * Listens for NectarLink appearance preference changes, media artwork color* changes, and Material You wallpaper/configuration color changes without polling.*/class AccentMonitor(private val context: Context, private val onChange: (UInt?) -> Unit) {diff --git a/android/app/src/main/kotlin/app/nectarlink/android/elevated/InputServer.kt b/android/app/src/main/kotlin/app/nectarlink/android/elevated/InputServer.ktindex e9c390a..7150864 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/elevated/InputServer.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/elevated/InputServer.kt@@ -886,7 +886,7 @@ object InputServer {val usage = androidKeyCodeToHidUsage(androidKeyCode) ?: return falseif (!keyboardAttempted) {keyboardAttempted = true- keyboardFd = openDevice("Nectarlink Virtual Keyboard", 0x4EE7, KEYBOARD_RD)+ keyboardFd = openDevice("NectarLink Virtual Keyboard", 0x4EE7, KEYBOARD_RD)}val fd = keyboardFd ?: return falseval down = ByteArray(8).apply { this[2] = usage.toByte() }@@ -898,7 +898,7 @@ object InputServer {fun sendGamepadReport(buttons: Int, lx: Int, ly: Int, rx: Int, ry: Int, lt: Int, rt: Int): Boolean {if (!gamepadAttempted) {gamepadAttempted = true- gamepadFd = openDevice("Nectarlink Virtual Gamepad", 0x4EE8, GAMEPAD_RD)+ gamepadFd = openDevice("NectarLink Virtual Gamepad", 0x4EE8, GAMEPAD_RD)}val fd = gamepadFd ?: return falseval report = java.nio.ByteBuffer.allocate(12).order(java.nio.ByteOrder.LITTLE_ENDIAN).apply {diff --git a/android/app/src/main/kotlin/app/nectarlink/android/links/LinkNotifications.kt b/android/app/src/main/kotlin/app/nectarlink/android/links/LinkNotifications.ktindex 9cae2a3..daaf2dd 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/links/LinkNotifications.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/links/LinkNotifications.kt@@ -55,7 +55,7 @@ object LinkNotifications {} else {Intent(Intent.ACTION_VIEW, url.toUri()).addFlags(Intent.FLAG_ACTIVITY_NEW_TASK)}- // When Nectarlink is in the foreground, Android allows opening the target right away.+ // When NectarLink is in the foreground, Android allows opening the target right away.runCatching { context.startActivity(viewIntent) }val open = PendingIntent.getActivity(diff --git a/android/app/src/main/kotlin/app/nectarlink/android/media/PcMedia.kt b/android/app/src/main/kotlin/app/nectarlink/android/media/PcMedia.ktindex 791a3bf..ea2e397 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/media/PcMedia.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/media/PcMedia.kt@@ -117,7 +117,7 @@ class PcMedia(if (first == null) return hide()val (pc, player) = firstshown = first- val session = session ?: MediaSession(context, "Nectarlink PC media").also {+ val session = session ?: MediaSession(context, "NectarLink PC media").also {it.setCallback(callback, main)it.setSessionActivity(openApp())session = itdiff --git a/android/app/src/main/kotlin/app/nectarlink/android/media/PhoneMedia.kt b/android/app/src/main/kotlin/app/nectarlink/android/media/PhoneMedia.ktindex f58deba..ba3a80e 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/media/PhoneMedia.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/media/PhoneMedia.kt@@ -23,7 +23,7 @@ import java.io.ByteArrayOutputStream* apps' media sessions, read with notification access, and the PCs'* commands for them.*- * Runs on the main thread. Nectarlink's own session (a PC's media, see+ * Runs on the main thread. NectarLink's own session (a PC's media, see* [PcMedia]) is left out, so a PC never gets its own music back.*/class PhoneMedia(context: Context, private val onChange: (List<MediaPlayer>) -> Unit) {diff --git a/android/app/src/main/kotlin/app/nectarlink/android/notifications/NotificationListener.kt b/android/app/src/main/kotlin/app/nectarlink/android/notifications/NotificationListener.ktindex bf42b28..ee70116 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/notifications/NotificationListener.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/notifications/NotificationListener.kt@@ -171,7 +171,7 @@ class NotificationListener : NotificationListenerService() {fun component(context: Context) = ComponentName(context, NotificationListener::class.java)- /** Android's notification access screen, on Nectarlink's own switch where possible. */+ /** Android's notification access screen, on NectarLink's own switch where possible. */fun settingsIntent(context: Context): Intent =if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.R) {Intent(Settings.ACTION_NOTIFICATION_LISTENER_DETAIL_SETTINGS).putExtra(diff --git a/android/app/src/main/kotlin/app/nectarlink/android/notifications/NotificationReader.kt b/android/app/src/main/kotlin/app/nectarlink/android/notifications/NotificationReader.ktindex 5414d7b..e2d3ce8 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/notifications/NotificationReader.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/notifications/NotificationReader.kt@@ -29,7 +29,7 @@ import app.nectarlink.core.NotificationConversationimport app.nectarlink.core.NotificationLive/**- * Turns Android notifications into what Nectarlink mirrors, and decides+ * Turns Android notifications into what NectarLink mirrors, and decides* which ones are worth mirroring at all.*/internal class NotificationReader(private val context: Context) {diff --git a/android/app/src/main/kotlin/app/nectarlink/android/service/StartupReceiver.kt b/android/app/src/main/kotlin/app/nectarlink/android/service/StartupReceiver.ktindex 81a99b5..6f7b71b 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/service/StartupReceiver.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/service/StartupReceiver.kt@@ -13,7 +13,7 @@ import kotlinx.coroutines.launchimport kotlinx.coroutines.withTimeoutOrNull/**- * Brings the connection back after the phone restarts or Nectarlink is+ * Brings the connection back after the phone restarts or NectarLink is* updated, without waiting for the app to be opened. Starting the core starts* the connection service when a PC is paired (Core.start). After an update,* the new version also says so in a notification.diff --git a/android/app/src/main/kotlin/app/nectarlink/android/storage/PhoneStorage.kt b/android/app/src/main/kotlin/app/nectarlink/android/storage/PhoneStorage.ktindex d1fe368..b6e336b 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/storage/PhoneStorage.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/storage/PhoneStorage.kt@@ -34,7 +34,7 @@ import java.nio.file.Files* Security invariants:* - Paths are relative to the shared root; `..`, `.`, leading/trailing `/`,* `\`, NUL, and control characters are rejected.- * - Never exposes `/data`, `Android/data`, `Android/obb`, or Nectarlink's own+ * - Never exposes `/data`, `Android/data`, `Android/obb`, or NectarLink's own* private directories.* - Symlinks resolving outside the canonical storage root (or into a blocked* directory) are rejected.@@ -551,7 +551,7 @@ class PhoneStorage(fun capabilities(context: Context): List<String> =if (hasAnyAccess(context)) listOf("storage.read", "storage.write") else emptyList()- /** Intent to open Android's "All files access" settings screen for Nectarlink. */+ /** Intent to open Android's "All files access" settings screen for NectarLink. */fun allFilesAccessIntent(context: Context): Intent {if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.R) {val perApp = Intent(diff --git a/android/app/src/main/kotlin/app/nectarlink/android/ui/guide/FeaturesGuideData.kt b/android/app/src/main/kotlin/app/nectarlink/android/ui/guide/FeaturesGuideData.ktindex b420f20..9e94d5f 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/ui/guide/FeaturesGuideData.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/ui/guide/FeaturesGuideData.kt@@ -117,7 +117,7 @@ data class FeatureGuideEntry()/**- * Full catalog of Nectarlink features for the Android Features Guide.+ * Full catalog of NectarLink features for the Android Features Guide.*/object FeaturesGuideCatalog {val entries: List<FeatureGuideEntry> = listOf(diff --git a/android/app/src/main/kotlin/app/nectarlink/android/ui/home/HomeScreen.kt b/android/app/src/main/kotlin/app/nectarlink/android/ui/home/HomeScreen.ktindex 30c717d..0c871e9 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/ui/home/HomeScreen.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/ui/home/HomeScreen.kt@@ -747,7 +747,7 @@ private fun WhatsNewFeaturesGuideCard(color = MaterialTheme.colorScheme.onSecondaryContainer,)Text(- text = "Explore every Nectarlink feature, check live permissions, or tap Show me to jump straight to any control.",+ text = "Explore every NectarLink feature, check live permissions, or tap Show me to jump straight to any control.",style = MaterialTheme.typography.bodySmall,color = MaterialTheme.colorScheme.onSecondaryContainer,)@@ -851,7 +851,7 @@ private fun NoPairedPcCard(color = MaterialTheme.colorScheme.onPrimaryContainer,)Text(- text = "Open Nectarlink on your Windows or Linux PC to pair by QR code or local discovery, or reopen the setup walkthrough.",+ text = "Open NectarLink on your Windows or Linux PC to pair by QR code or local discovery, or reopen the setup walkthrough.",style = MaterialTheme.typography.bodyMedium,color = MaterialTheme.colorScheme.onPrimaryContainer,)diff --git a/android/app/src/main/kotlin/app/nectarlink/android/ui/pairing/QrScanner.kt b/android/app/src/main/kotlin/app/nectarlink/android/ui/pairing/QrScanner.ktindex dfbfb73..33d1da6 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/ui/pairing/QrScanner.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/ui/pairing/QrScanner.kt@@ -50,7 +50,7 @@ import java.util.concurrent.atomic.AtomicBooleanprivate const val LINK_PREFIX = "nectarlink://pair?"/**- * A camera preview that reports the first Nectarlink pairing link it sees.+ * A camera preview that reports the first NectarLink pairing link it sees.* Asks for the camera permission if needed.*/@Composablediff --git a/android/app/src/main/kotlin/app/nectarlink/android/ui/settings/SettingsScreen.kt b/android/app/src/main/kotlin/app/nectarlink/android/ui/settings/SettingsScreen.ktindex 8fb1b51..47dbcfc 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/ui/settings/SettingsScreen.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/ui/settings/SettingsScreen.kt@@ -1145,7 +1145,7 @@ private fun WriteSettingsAccess(granted: Boolean) {}}-/** Control from the PC: Nectarlink's accessibility service, turned on in Android's settings. */+/** Control from the PC: NectarLink's accessibility service, turned on in Android's settings. */@Composableprivate fun ControlAccess(on: Boolean) {val context = LocalContext.currentdiff --git a/android/app/src/main/kotlin/app/nectarlink/android/update/AppUpdater.kt b/android/app/src/main/kotlin/app/nectarlink/android/update/AppUpdater.ktindex 78af91c..d66ffeb 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/update/AppUpdater.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/update/AppUpdater.kt@@ -73,7 +73,7 @@ class AppUpdater(context: Context) {data object UpToDate : Statedata class Available(val update: Update) : State- /** Waiting for the user to let Nectarlink install apps; continues when they have. */+ /** Waiting for the user to let NectarLink install apps; continues when they have. */data class NeedsPermission(val update: Update) : State/** `total` is 0 until the size is known. */@@ -104,7 +104,7 @@ class AppUpdater(context: Context) {/*** For the background: checks when due and, with automatic updates on, installs a newer- * release. Android 12 and later install it without asking once Nectarlink has installed+ * release. Android 12 and later install it without asking once NectarLink has installed* itself before; otherwise a notification asks for one tap.*/suspend fun updateIfDue() {@@ -179,7 +179,7 @@ class AppUpdater(context: Context) {/** Whether this app may install apps (the user allows it once, in Settings). */fun canInstall(): Boolean = context.packageManager.canRequestPackageInstalls()- /** Android's screen where the user lets Nectarlink install updates. */+ /** Android's screen where the user lets NectarLink install updates. */fun allowInstallsIntent(): Intent =Intent(Settings.ACTION_MANAGE_UNKNOWN_APP_SOURCES, "package:${context.packageName}".toUri()).addFlags(Intent.FLAG_ACTIVITY_NEW_TASK)@@ -421,7 +421,7 @@ class AppUpdater(context: Context) {Build.VERSION.SDK_INT < Build.VERSION_CODES.TIRAMISU ||ContextCompat.checkSelfPermission(context, Manifest.permission.POST_NOTIFICATIONS) == PackageManager.PERMISSION_GRANTED- /** "Nectarlink 0.2.0 is ready", opening Android's install prompt when tapped. */+ /** "NectarLink 0.2.0 is ready", opening Android's install prompt when tapped. */internal fun notifyReady(confirm: Intent) {if (!mayNotify()) returnval manager = context.getSystemService(NotificationManager::class.java)diff --git a/android/app/src/main/kotlin/app/nectarlink/android/update/UpdateCard.kt b/android/app/src/main/kotlin/app/nectarlink/android/update/UpdateCard.ktindex 80e3655..29dcd6c 100644--- a/android/app/src/main/kotlin/app/nectarlink/android/update/UpdateCard.kt+++ b/android/app/src/main/kotlin/app/nectarlink/android/update/UpdateCard.kt@@ -42,7 +42,7 @@ private val AppUpdater.State.update: AppUpdater.Update?else -> null}-/** "Nectarlink 0.2.0 is available" on Home, while there's an update to talk about. */+/** "NectarLink 0.2.0 is available" on Home, while there's an update to talk about. */@Composablefun UpdateCard(updater: AppUpdater, modifier: Modifier = Modifier) {val state by updater.state.collectAsStateWithLifecycle()diff --git a/android/app/src/main/res/drawable/ic_notification.xml b/android/app/src/main/res/drawable/ic_notification.xmlindex 76600d7..ab62ab1 100644--- a/android/app/src/main/res/drawable/ic_notification.xml+++ b/android/app/src/main/res/drawable/ic_notification.xml@@ -1,6 +1,6 @@<?xml version="1.0" encoding="utf-8"?><!-- SPDX-License-Identifier: GPL-3.0-or-later -->-<!-- The Nectarlink mark for notifications: flat white, inside the 20dp live area. -->+<!-- The NectarLink mark for notifications: flat white, inside the 20dp live area. --><vector xmlns:android="http://schemas.android.com/apk/res/android"android:width="24dp" android:height="24dp" android:viewportWidth="100" android:viewportHeight="100"><group android:pivotX="50" android:pivotY="50" android:scaleX="0.96" android:scaleY="0.96" android:rotation="-25">diff --git a/android/app/src/main/res/values/strings.xml b/android/app/src/main/res/values/strings.xmlindex 8692b93..fb7c698 100644--- a/android/app/src/main/res/values/strings.xml+++ b/android/app/src/main/res/values/strings.xml@@ -1,13 +1,13 @@<?xml version="1.0" encoding="utf-8"?><!-- SPDX-License-Identifier: GPL-3.0-or-later --><resources>- <string name="app_name">Nectarlink</string>+ <string name="app_name">NectarLink</string><!-- Pairing --><string name="pair_title">Pair with your PC</string>- <string name="pair_scan_hint">On your PC, open Nectarlink. Point the camera at the code it shows.</string>+ <string name="pair_scan_hint">On your PC, open NectarLink. Point the camera at the code it shows.</string><string name="pair_nearby_title">Pair nearby</string>- <string name="pair_nearby_hint">On your PC, open Nectarlink and keep its pairing screen open. It shows up here.</string>+ <string name="pair_nearby_hint">On your PC, open NectarLink and keep its pairing screen open. It shows up here.</string><string name="pair_looking">Looking for PCs…</string><string name="pair_joining">Pairing…</string><string name="pair_connecting">Connecting to %1$s…</string>@@ -21,9 +21,9 @@<string name="pair_failed_declined">Pairing was declined on one of the devices.</string><string name="pair_failed_expired">The code expired. Show a new one on your PC.</string><string name="pair_failed_unreachable">Couldn\'t reach the PC. Make sure both are on the same network.</string>- <string name="pair_failed_other">That isn\'t a Nectarlink pairing code, or something went wrong.</string>+ <string name="pair_failed_other">That isn\'t a NectarLink pairing code, or something went wrong.</string><string name="your_pc">your PC</string>- <string name="camera_permission_needed">Nectarlink needs the camera to scan the pairing code. Nothing is recorded.</string>+ <string name="camera_permission_needed">NectarLink needs the camera to scan the pairing code. Nothing is recorded.</string><!-- Home --><string name="home_title">Home</string>@@ -55,7 +55,7 @@<string name="settings_notifications">Notifications</string><string name="notifications_title">Show notifications on your PC</string><string name="notifications_on">On. Notifications appear on your paired PCs, where you can reply to and dismiss them.</string>- <string name="notifications_off">Nectarlink needs notification access to show this phone’s notifications on your PC.</string>+ <string name="notifications_off">NectarLink needs notification access to show this phone’s notifications on your PC.</string><string name="notifications_restricted">Switch greyed out? Open App info, tap ⋮, choose “Allow restricted settings”, then try again.</string><string name="action_allow">Allow</string><string name="clip_share_label">Send to PC</string>@@ -69,12 +69,12 @@<string name="media_previous">Previous</string><string name="action_send_files">Send files</string><string name="action_send_folder">Send a folder</string>- <string name="input_service_label">Nectarlink: control from your PC</string>+ <string name="input_service_label">NectarLink: control from your PC</string><string name="input_service_description">Lets your PC\'s mouse and keyboard tap, swipe and type on this phone while you share its screen with a paired PC. It reads nothing else.</string><string name="settings_control">Control from your PC</string><string name="control_title">Use your PC\'s mouse and keyboard</string><string name="control_on">On: while your screen is shown on your PC, you can tap, swipe and type from there.</string>- <string name="control_off">Tap, swipe and type from your PC while it shows this screen. Turn on Nectarlink in Accessibility.</string>+ <string name="control_off">Tap, swipe and type from your PC while it shows this screen. Turn on NectarLink in Accessibility.</string><string name="dnd_access_title">Do Not Disturb and silent mode</string><string name="dnd_access_on">On: your PC can turn Do Not Disturb on or off and set the ringer to silent.</string><string name="dnd_access_off">Let your PC turn Do Not Disturb on or off and set the ringer to silent.</string>@@ -82,7 +82,7 @@<string name="write_settings_on">On: your PC can adjust this phone\'s screen brightness.</string><string name="write_settings_off">Let your PC adjust this phone\'s screen brightness.</string><string name="local_network_title">Reach your PC on this network</string>- <string name="local_network_text">Android asks before an app talks to devices on your network. Nectarlink needs it to reach your PC.</string>+ <string name="local_network_text">Android asks before an app talks to devices on your network. NectarLink needs it to reach your PC.</string><string name="channel_elevated">Wireless debugging setup</string><string name="elevated_title">Real touch and keys (Wireless debugging)</string><string name="elevated_not_set_up">Real-time touch, every key, and mute, hold and keypad on calls from your PC. Uses Android\'s own Wireless debugging.</string>@@ -90,14 +90,14 @@<string name="elevated_starting">Starting…</string><string name="elevated_running">On: your PC\'s mouse and keyboard work like a real touchscreen and keyboard.</string><string name="elevated_failed">Couldn\'t start it. Check that Wireless debugging is on, then try again.</string>- <string name="elevated_not_paired">The phone forgot Nectarlink\'s pairing. Set it up again.</string>+ <string name="elevated_not_paired">The phone forgot NectarLink\'s pairing. Set it up again.</string><string name="elevated_set_up">Set up</string><string name="elevated_turn_off">Turn off</string><string name="elevated_try_again">Try again</string><string name="elevated_steps_title">Set up Wireless debugging</string>- <string name="elevated_steps">One-time codes in notifications Android hides as sensitive also reach your PC.\n\n1. Turn on Developer options: in Settings › About phone, tap Build number 7 times.\n2. In Developer options, turn on Wireless debugging (on Wi-Fi), open it and tap Pair device with pairing code.\n3. Type the 6-digit code into Nectarlink\'s notification, without closing the code.</string>+ <string name="elevated_steps">One-time codes in notifications Android hides as sensitive also reach your PC.\n\n1. Turn on Developer options: in Settings › About phone, tap Build number 7 times.\n2. In Developer options, turn on Wireless debugging (on Wi-Fi), open it and tap Pair device with pairing code.\n3. Type the 6-digit code into NectarLink\'s notification, without closing the code.</string><string name="elevated_open_developer">Open Developer options</string>- <string name="elevated_pair_title">Pair Nectarlink with Wireless debugging</string>+ <string name="elevated_pair_title">Pair NectarLink with Wireless debugging</string><string name="elevated_pair_text">In Wireless debugging, tap Pair device with pairing code, then type the code here.</string><string name="elevated_pair_action">Enter code</string><string name="elevated_pair_hint">6-digit pairing code</string>@@ -161,7 +161,7 @@<string name="clip_empty">There’s no text or image on the clipboard.</string><string name="clip_image_too_large">That image is too large to send.</string><string name="clip_image_unreadable">That image can’t be read.</string>- <string name="clip_image_unsupported">Update Nectarlink on %1$s to send it images.</string>+ <string name="clip_image_unsupported">Update NectarLink on %1$s to send it images.</string><string name="clip_nothing_shared">There’s no text to send.</string><string name="clipboard_history_title">Clipboard history</string><string name="clipboard_history_subtitle">Your last 50 clips with your PCs, kept encrypted on this phone.</string>@@ -192,16 +192,16 @@<string name="clip_action_track">Track</string><string name="clip_action_email">Email</string><string name="background_title">Stay reachable in the background</string>- <string name="background_text">Android is pausing Nectarlink to save battery, so your PC can\'t reach it. Let it run in the background.</string>+ <string name="background_text">Android is pausing NectarLink to save battery, so your PC can\'t reach it. Let it run in the background.</string><string name="background_on">Allowed to stay connected in the background</string><string name="settings_background_title">Background & battery</string><string name="battery_open_oem_settings">Battery settings</string>- <string name="battery_guide_samsung">On Samsung: open App info › Battery › select Unrestricted, and in Device care › Battery › Background usage limits make sure Nectarlink is never put to sleep.</string>- <string name="battery_guide_xiaomi">On Xiaomi / HyperOS / MIUI: turn on Autostart for Nectarlink, and in App info › Battery saver select No restrictions.</string>+ <string name="battery_guide_samsung">On Samsung: open App info › Battery › select Unrestricted, and in Device care › Battery › Background usage limits make sure NectarLink is never put to sleep.</string>+ <string name="battery_guide_xiaomi">On Xiaomi / HyperOS / MIUI: turn on Autostart for NectarLink, and in App info › Battery saver select No restrictions.</string><string name="battery_guide_oneplus">On OnePlus / OxygenOS: open App info › Battery usage › turn on Allow background activity and Allow auto-launch.</string><string name="battery_guide_oppo_realme">On Oppo / Realme: open App info › Battery usage › turn on Allow background activity and Allow auto-launch.</string><string name="battery_guide_vivo">On Vivo / Funtouch / OriginOS: open App info › Battery › select Unrestricted (High background power usage) and allow Autostart.</string>- <string name="battery_guide_huawei">On Huawei / Honor: open App launch (Phone Manager) › turn off Manage automatically for Nectarlink and keep Auto-launch, Secondary launch, and Run in background on.</string>+ <string name="battery_guide_huawei">On Huawei / Honor: open App launch (Phone Manager) › turn off Manage automatically for NectarLink and keep Auto-launch, Secondary launch, and Run in background on.</string><string name="battery_guide_pixel">On Pixel: open App info › App battery usage › tap Allow background usage and select Unrestricted.</string><string name="action_manage">Manage</string><string name="action_app_info">App info</string>@@ -217,10 +217,10 @@<string name="mode_system">System</string><string name="mode_light">Light</string><string name="mode_dark">Dark</string>- <string name="about_version">Nectarlink %1$s</string>+ <string name="about_version">NectarLink %1$s</string><string name="unpair_title">Unpair %1$s?</string><string name="unpair_text">Both devices forget each other. You can pair them again any time.</string>- <string name="core_failed">Nectarlink couldn\'t start: %1$s</string>+ <string name="core_failed">NectarLink couldn\'t start: %1$s</string><!-- Actions --><string name="action_pair">Pair</string>@@ -237,21 +237,21 @@<string name="action_pair_new">Pair another PC</string><string name="action_refresh">Refresh</string><string name="action_update">Update</string>- <string name="update_title">Nectarlink %1$s is available</string>+ <string name="update_title">NectarLink %1$s is available</string><string name="update_text">Get the latest improvements and fixes.</string><string name="update_downloading">Downloading…</string><string name="update_downloading_progress">Downloading · %1$s of %2$s</string><string name="update_waiting_network">Waiting for a connection. The download continues where it stopped.</string><string name="update_installing">Installing. Android may ask you to confirm.</string>- <string name="update_not_allowed">Allow Nectarlink to install its updates. The update continues when you come back.</string>+ <string name="update_not_allowed">Allow NectarLink to install its updates. The update continues when you come back.</string><string name="update_damaged">The download was damaged, so it wasn’t installed. Try again.</string><string name="update_offline">The update couldn’t be downloaded. Try again when you’re online.</string><string name="update_install_failed">Android didn’t install the update. Try again.</string><string name="update_whats_new">What’s new</string><string name="update_check">Check for updates</string><string name="update_checking">Checking for updates…</string>- <string name="update_up_to_date_version">Nectarlink %1$s is up to date.</string>- <string name="update_current_version">You have Nectarlink %1$s.</string>+ <string name="update_up_to_date_version">NectarLink %1$s is up to date.</string>+ <string name="update_current_version">You have NectarLink %1$s.</string><string name="update_check_failed">Couldn’t check for updates. Check your internet connection.</string><string name="action_lock_pc">Lock PC</string><string name="action_sleep_pc">Sleep</string>@@ -322,11 +322,11 @@<string name="remote_dictate_no_recognizer">This phone doesn\'t have speech recognition installed.</string><string name="remote_dictate_no_speech">Didn\'t catch anything. Tap or hold Dictate to try again.</string><string name="remote_dictate_error">Speech recognition couldn\'t finish. Tap or hold Dictate to try again.</string>- <string name="remote_dictate_permission_needed">Nectarlink needs microphone access to dictate into %1$s.</string>+ <string name="remote_dictate_permission_needed">NectarLink needs microphone access to dictate into %1$s.</string><string name="remote_denied_title">Allow control on %1$s</string>- <string name="remote_denied_text">On %1$s, allow control from this phone in Nectarlink\'s prompt or in Settings › Devices.</string>+ <string name="remote_denied_text">On %1$s, allow control from this phone in NectarLink\'s prompt or in Settings › Devices.</string><string name="remote_offline_text">%1$s isn\'t connected right now.</string>- <string name="remote_unsupported_text">Update Nectarlink on %1$s to control it from this phone.</string>+ <string name="remote_unsupported_text">Update NectarLink on %1$s to control it from this phone.</string><string name="remote_slide_next">Next slide</string><string name="remote_slide_prev">Previous</string><string name="remote_slide_start">Start show</string>@@ -356,7 +356,7 @@<string name="recorder_notification_recording">Recording for %1$s</string><string name="recorder_notification_paused">Recording paused (%1$s)</string><string name="recorder_permission_title">Allow microphone access</string>- <string name="recorder_permission_text">Nectarlink uses the microphone only while you record a voice note to send to %1$s.</string>+ <string name="recorder_permission_text">NectarLink uses the microphone only while you record a voice note to send to %1$s.</string><string name="recorder_allow_mic">Allow microphone</string><string name="recorder_offline_hint">Recordings are saved on this phone and sent automatically when %1$s connects.</string><string name="recorder_status_ready">Ready to record for %1$s</string>@@ -390,9 +390,9 @@<string name="deck_live">Live</string><string name="deck_volume_percent">%1$d%%</string><string name="deck_waiting">Loading %1$s\'s Deck…</string>- <string name="deck_empty_page">No tiles on this page yet. Add tiles in Nectarlink on %1$s.</string>+ <string name="deck_empty_page">No tiles on this page yet. Add tiles in NectarLink on %1$s.</string><string name="deck_commands_denied_title">Allow commands on %1$s</string>- <string name="deck_commands_denied_text">To run shell commands from this phone, turn on “Run Deck commands” for this phone in Nectarlink › Settings › Devices on %1$s.</string>+ <string name="deck_commands_denied_text">To run shell commands from this phone, turn on “Run Deck commands” for this phone in NectarLink › Settings › Devices on %1$s.</string><string name="deck_hint">Customize tiles in Deck on %1$s</string><string name="pc_audio_title">PC audio</string><string name="pc_audio_volume">Volume</string>@@ -431,7 +431,7 @@<string name="webcam_request_title">%1$s wants to use your camera</string><string name="webcam_request_text">Tap to open the webcam controls and start streaming.</string><string name="webcam_permission_title">Allow camera access</string>- <string name="webcam_permission_text">Nectarlink uses the camera only while you stream video to %1$s as a webcam.</string>+ <string name="webcam_permission_text">NectarLink uses the camera only while you stream video to %1$s as a webcam.</string><string name="webcam_allow_camera">Allow camera</string><string name="webcam_status_streaming">Streaming %1$d × %2$d to %3$s</string><string name="webcam_status_connecting">Connecting camera to %1$s…</string>@@ -632,7 +632,7 @@<string name="widget_pc_title">PC quick actions</string><string name="widget_pc_description">Connection status, Send clipboard, Ring PC, Lock PC, and Wake for your paired PC.</string><string name="widget_pc_no_pc">No PC paired</string>- <string name="widget_pc_tap_to_pair">Tap to open Nectarlink and pair a PC</string>+ <string name="widget_pc_tap_to_pair">Tap to open NectarLink and pair a PC</string><string name="widget_pc_connected">Connected</string><string name="widget_pc_offline">Offline</string><string name="widget_pc_waking">Waking…</string>@@ -645,8 +645,8 @@<!-- Companion Device Manager proximity wake --><string name="companion_wake_title">Wake when PC is nearby (Companion Device)</string>- <string name="companion_wake_on">Associated · Android wakes Nectarlink when your PC is nearby</string>- <string name="companion_wake_off">Associate your PC so Android wakes Nectarlink when its BLE beacon is in range</string>+ <string name="companion_wake_on">Associated · Android wakes NectarLink when your PC is nearby</string>+ <string name="companion_wake_off">Associate your PC so Android wakes NectarLink when its BLE beacon is in range</string><string name="companion_wake_associate">Associate</string><!-- Flick to Send sheet -->@@ -674,7 +674,7 @@<string name="mirror_allow_pc_control">Allow PC mouse control</string><string name="action_open_controls">Controls</string><string name="remote_input_requested_title">Your PC tried to control this phone</string>- <string name="remote_input_requested_text">Turn on “Nectarlink: control from your PC” in Accessibility to use your PC\'s mouse and keyboard on this phone.</string>+ <string name="remote_input_requested_text">Turn on “NectarLink: control from your PC” in Accessibility to use your PC\'s mouse and keyboard on this phone.</string><string name="permissions_setup_title">Permissions & setup (%1$d remaining)</string><string name="permissions_setup_subtitle">Notifications, calls, texts, photos and background access</string><string name="clipboard_preview_hidden">••••••••••••</string>@@ -764,10 +764,10 @@<string name="walkthrough_perm_access_title">Assist</string><string name="walkthrough_perm_access_does">Control your mirrored phone screen from your PC with mouse and keyboard.</string>- <string name="walkthrough_perm_access_requires">Android requires the Nectarlink Accessibility service or Elevated.</string>+ <string name="walkthrough_perm_access_requires">Android requires the NectarLink Accessibility service or Elevated.</string><string name="walkthrough_pair_title">Pair with your PC</string>- <string name="walkthrough_pair_subtitle">Open Nectarlink on your Windows 11 PC. Scan its QR code or pick your PC below.</string>+ <string name="walkthrough_pair_subtitle">Open NectarLink on your Windows 11 PC. Scan its QR code or pick your PC below.</string><string name="walkthrough_pair_ready_title">Paired PC</string><string name="walkthrough_pair_badge_paired">Paired</string><string name="walkthrough_pair_device_online">%1$s · Connected</string>@@ -806,7 +806,7 @@<string name="walkthrough_power_elevated_step3">3. Turn on Wireless debugging, tap Pair device with pairing code, and enter the 6-digit code in the notification.</string><string name="walkthrough_done_title">Setup complete</string>- <string name="walkthrough_done_subtitle">Nectarlink is ready. Reopen this walkthrough anytime from Settings › About.</string>+ <string name="walkthrough_done_subtitle">NectarLink is ready. Reopen this walkthrough anytime from Settings › About.</string><string name="walkthrough_done_summary_heading">Your setup</string><string name="walkthrough_done_paired_label">Paired PC</string><string name="walkthrough_done_no_pc">None yet · pair anytime on Home</string>@@ -818,7 +818,7 @@<string name="walkthrough_done_no_permissions">None granted yet</string><string name="walkthrough_done_try_heading">Try first</string><string name="walkthrough_done_try_1">1. Copy text and tap the Send clipboard tile to paste on your PC.</string>- <string name="walkthrough_done_try_2">2. Share any file or link to Nectarlink from Android Share.</string>+ <string name="walkthrough_done_try_2">2. Share any file or link to NectarLink from Android Share.</string><!-- Features Guide Chrome --><string name="guide_back">Back</string>@@ -880,12 +880,12 @@<string name="guide_notif_summary">See phone notifications on your PC, dismiss them, or reply inline.</string><string name="guide_notif_where">Settings › Permissions › Notifications</string><string name="guide_notif_needs">Notification access, Notifications toggle on for the PC</string>- <string name="guide_notif_need_1">Android Notification Access enabled for Nectarlink.</string>+ <string name="guide_notif_need_1">Android Notification Access enabled for NectarLink.</string><string name="guide_notif_need_2">On Android 13+, Allow restricted settings enabled in App info if sideloaded.</string><string name="guide_notif_need_3">Windows 11 PC paired and online.</string><string name="guide_notif_phone_1">Open Settings › Permissions › Notifications and tap Allow.</string>- <string name="guide_notif_phone_2">Turn on Nectarlink in Android Notification Access.</string>- <string name="guide_notif_pc_1">View phone notifications in the PC notification center or Nectarlink window.</string>+ <string name="guide_notif_phone_2">Turn on NectarLink in Android Notification Access.</string>+ <string name="guide_notif_pc_1">View phone notifications in the PC notification center or NectarLink window.</string><string name="guide_notif_pc_2">Type a reply on the card and press Send, or dismiss to clear on both devices.</string><string name="guide_notif_opt_1">Allow / Manage: Opens Android Notification Access settings.</string><string name="guide_notif_opt_2">Per-PC Notifications toggle: Controls whether a paired PC receives notifications.</string>@@ -944,7 +944,7 @@<string name="guide_clip_needs">Paired PC; Elevated for automatic background phone-to-PC sync</string><string name="guide_clip_need_1">PC-to-phone clipboard sync and the Send clipboard tile work out of the box.</string><string name="guide_clip_need_2">Elevated adds automatic phone-to-PC clipboard sync.</string>- <string name="guide_clip_phone_1">Copy text or an image on your phone, then open Nectarlink or tap the Send clipboard tile.</string>+ <string name="guide_clip_phone_1">Copy text or an image on your phone, then open NectarLink or tap the Send clipboard tile.</string><string name="guide_clip_phone_2">Tap Clipboard history on Home to view, pin, copy, or delete recent clips.</string><string name="guide_clip_pc_1">Copy text or an image on your PC to send it to your phone clipboard.</string><string name="guide_clip_opt_1">Show / Hide: Masks or reveals the latest clip preview on Home.</string>@@ -976,7 +976,7 @@<string name="guide_files_need_1">Paired Windows 11 PC (offline files wait in Send queue for up to 7 days).</string><string name="guide_files_phone_1">On Home, tap Send files or Send a folder on your paired PC card.</string><string name="guide_files_phone_2">Pause, resume, or cancel active transfers in the Transfers card on Home.</string>- <string name="guide_files_pc_1">Drag files onto the Nectarlink window or top-edge island on your PC.</string>+ <string name="guide_files_pc_1">Drag files onto the NectarLink window or top-edge island on your PC.</string><string name="guide_files_opt_1">Send files / Send a folder: Transfers individual files or full folder trees.</string><string name="guide_files_opt_2">Pause / Resume: Resumes interrupted transfers without re-sending completed bytes.</string><string name="guide_files_privacy">Files stream over QUIC TLS 1.3 with BLAKE3 integrity verification into Download/Nectarlink.</string>@@ -1001,7 +1001,7 @@<string name="guide_share_where">Android Share sheet › Send to PC</string><string name="guide_share_needs">Paired PC</string><string name="guide_share_ext_1">1. Tap Share in any browser, gallery, or document app on your phone.</string>- <string name="guide_share_ext_2">2. Select Nectarlink (Send to PC or Open on PC).</string>+ <string name="guide_share_ext_2">2. Select NectarLink (Send to PC or Open on PC).</string><string name="guide_share_need_1">At least one paired PC.</string><string name="guide_share_phone_1">Share any link or file from Android Share and pick your target PC.</string><string name="guide_share_pc_1">Links open in your default PC browser; files save to Downloads.</string>@@ -1018,7 +1018,7 @@<string name="guide_storage_need_2">Browse this phone\'s storage in File Explorer enabled for the PC in Settings › Devices.</string><string name="guide_storage_phone_1">Grant All files access or pick folders in Settings › Permissions › Photos and videos.</string><string name="guide_storage_phone_2">Turn on the storage switch for your PC in Settings › Devices.</string>- <string name="guide_storage_pc_1">Open your phone storage from Nectarlink or Windows File Explorer on your PC.</string>+ <string name="guide_storage_pc_1">Open your phone storage from NectarLink or Windows File Explorer on your PC.</string><string name="guide_storage_opt_1">All files access / Selected folders only: Share full storage or only picked SAF folders.</string><string name="guide_storage_privacy">Storage browsing is off by default for every PC until you turn it on.</string><string name="guide_storage_limits">Android blocks access to private app directories in /Android/data.</string>@@ -1030,7 +1030,7 @@<string name="guide_pc_files_needs">Online paired PC with storage sharing enabled</string><string name="guide_pc_files_need_1">Online paired PC with storage access enabled for this phone.</string><string name="guide_pc_files_phone_1">On Home, tap Browse PC files on your paired PC card and tap any file to download.</string>- <string name="guide_pc_files_pc_1">Allow storage access for this phone in Nectarlink on your PC.</string>+ <string name="guide_pc_files_pc_1">Allow storage access for this phone in NectarLink on your PC.</string><string name="guide_pc_files_opt_1">Browse PC files sheet: Navigate PC folders and download files into Downloads.</string><string name="guide_pc_files_privacy">Downloaded files save locally in your phone Downloads folder.</string><string name="guide_pc_files_limits">Requires the paired PC to be online.</string>@@ -1105,7 +1105,7 @@<string name="guide_webcam_needs">Camera permission, online paired PC</string><string name="guide_webcam_need_1">Camera permission on Android and an online paired PC.</string><string name="guide_webcam_phone_1">On Home, tap Webcam on your paired PC card, choose resolution and lens, and tap Start webcam.</string>- <string name="guide_webcam_pc_1">View or record the live camera stream in Nectarlink on your PC.</string>+ <string name="guide_webcam_pc_1">View or record the live camera stream in NectarLink on your PC.</string><string name="guide_webcam_opt_1">Flip camera / Torch / Zoom / Resolution (720p, 1080p, 4K): Live camera controls.</string><string name="guide_webcam_privacy">Never starts silently; shows an ongoing notification while streaming.</string><string name="guide_webcam_limits">1080p 60 fps and 4K require hardware encoder support and fast Wi-Fi or USB.</string>@@ -1117,7 +1117,7 @@<string name="guide_continuity_needs">Camera permission, online paired PC</string><string name="guide_continuity_need_1">Camera permission on Android and an online paired PC.</string><string name="guide_continuity_phone_1">Tap the request notification or banner, take a photo or adjust document corners, and tap Send.</string>- <string name="guide_continuity_pc_1">Trigger Take photo or Scan document from Nectarlink on your PC.</string>+ <string name="guide_continuity_pc_1">Trigger Take photo or Scan document from NectarLink on your PC.</string><string name="guide_continuity_opt_1">Adjust corners / Enhance document: Perspective crop and contrast enhancement for scans.</string><string name="guide_continuity_privacy">Captures are sent only when you tap Use photo or Send scan.</string><string name="guide_continuity_limits">Camera requests expire after 2 minutes if not answered.</string>@@ -1153,7 +1153,7 @@<string name="guide_assist_summary">Let your PC mouse and keyboard tap, swipe, and type on this phone using the Accessibility service.</string><string name="guide_assist_where">Settings › Permissions › Control from your PC › Use your PC\'s mouse and keyboard</string><string name="guide_assist_needs">Accessibility service enabled</string>- <string name="guide_assist_need_1">Nectarlink Accessibility service enabled in Android Settings.</string>+ <string name="guide_assist_need_1">NectarLink Accessibility service enabled in Android Settings.</string><string name="guide_assist_phone_1">Open Settings › Permissions › Control from your PC and tap Allow under Use your PC\'s mouse and keyboard.</string><string name="guide_assist_pc_1">Click, drag, scroll, and type inside the phone mirror window on your PC.</string><string name="guide_assist_opt_1">Stop typing: Ends remote PC keyboard typing from the Home banner.</string>@@ -1180,7 +1180,7 @@<string name="guide_deck_needs">Online paired PC</string><string name="guide_deck_need_1">Online paired Windows 11 PC.</string><string name="guide_deck_phone_1">On Home, tap Deck on your paired PC card and tap any tile to trigger its action.</string>- <string name="guide_deck_pc_1">Customize Deck pages and tiles in Nectarlink on your PC.</string>+ <string name="guide_deck_pc_1">Customize Deck pages and tiles in NectarLink on your PC.</string><string name="guide_deck_opt_1">Full screen: Expands the Deck grid across your phone screen.</string><string name="guide_deck_privacy">Deck layouts and system stats stay between your phone and paired PC.</string><string name="guide_deck_limits">Shell command tiles require Run Deck commands enabled for this phone on your PC.</string>@@ -1202,7 +1202,7 @@<string name="guide_wake_summary">Wake a sleeping paired PC over your local network using Wake-on-LAN.</string><string name="guide_wake_where">Home › Paired PC card › Wake</string><string name="guide_wake_needs">Paired PC with Wake-on-LAN enabled in BIOS and network adapter</string>- <string name="guide_wake_need_1">Paired PC connected over LAN at least once so Nectarlink learns its MAC address.</string>+ <string name="guide_wake_need_1">Paired PC connected over LAN at least once so NectarLink learns its MAC address.</string><string name="guide_wake_need_2">Wake-on-LAN enabled in Windows network adapter settings and BIOS/UEFI.</string><string name="guide_wake_phone_1">When your paired PC is offline on Home, tap Wake on its card.</string><string name="guide_wake_pc_1">Enable Wake-on-LAN packet wake in Device Manager › Network adapters › Power Management.</string>@@ -1219,7 +1219,7 @@<string name="guide_quick_need_2">Do Not Disturb and silent mode require Do Not Disturb access.</string><string name="guide_quick_need_3">Phone brightness control requires Screen brightness permission or Elevated.</string><string name="guide_quick_phone_1">Use Ring PC, Lock PC, and Sleep on your paired PC card on Home or add the PC quick actions widget.</string>- <string name="guide_quick_pc_1">Toggle phone DND, ringer, flashlight, volume, and brightness from Nectarlink on your PC.</string>+ <string name="guide_quick_pc_1">Toggle phone DND, ringer, flashlight, volume, and brightness from NectarLink on your PC.</string><string name="guide_quick_opt_1">Do Not Disturb / Screen brightness: Grant in Settings › Permissions › Control from your PC.</string><string name="guide_quick_privacy">Commands are authenticated per device over TLS 1.3.</string><string name="guide_quick_limits">Locking and sleeping the PC can be toggled per phone in PC Settings › Devices.</string>@@ -1247,7 +1247,7 @@<string name="guide_doctor_phone_1">Open Settings › Permissions › Background & battery and allow unrestricted battery usage.</string><string name="guide_doctor_phone_2">Follow the OEM battery guide if your phone vendor restricts background apps.</string><string name="guide_doctor_pc_1">Open Connection Doctor on your PC to inspect transport latency, ports, and link health.</string>- <string name="guide_doctor_opt_1">Wake when PC is nearby: Associates your PC so Android wakes Nectarlink when in BLE range.</string>+ <string name="guide_doctor_opt_1">Wake when PC is nearby: Associates your PC so Android wakes NectarLink when in BLE range.</string><string name="guide_doctor_privacy">Diagnostics run locally between your phone and paired PC.</string><string name="guide_doctor_limits">Some phone makers\' battery savers must be set to Unrestricted.</string><string name="pair_link_title">Pair with %1$s?</string>@@ -1257,9 +1257,9 @@<string name="pair_link_unknown_pc">this PC</string><string name="data_clear_failed">Some history couldn\'t be cleared. Try again.</string><string name="channel_updates">Updates</string>- <string name="update_ready_title">Nectarlink %1$s is ready</string>+ <string name="update_ready_title">NectarLink %1$s is ready</string><string name="update_ready_text">Tap to install the update.</string>- <string name="update_done_title">Nectarlink is updated to %1$s</string>+ <string name="update_done_title">NectarLink is updated to %1$s</string><string name="update_done_text">Tap to open it. Your PCs reconnect on their own.</string><string name="update_auto_title">Install updates automatically</string><string name="update_auto_text">New versions from GitHub install in the background.</string>diff --git a/android/app/src/test/kotlin/app/nectarlink/android/ui/remote/RemoteMathTest.kt b/android/app/src/test/kotlin/app/nectarlink/android/ui/remote/RemoteMathTest.ktindex 2a3788a..0265afd 100644--- a/android/app/src/test/kotlin/app/nectarlink/android/ui/remote/RemoteMathTest.kt+++ b/android/app/src/test/kotlin/app/nectarlink/android/ui/remote/RemoteMathTest.kt@@ -80,7 +80,7 @@ class RemoteMathTest {assertTrue(joiner.hasTypedUtterance)// Subsequent utterances get a single leading space.- assertEquals("This is Nectarlink.", joiner.next("This is Nectarlink.").removePrefix(" ").also {+ assertEquals("This is NectarLink.", joiner.next("This is NectarLink.").removePrefix(" ").also {// Verify the actual returned string had the single leading space:})val third = joiner.next("How are you?")diff --git a/assets/brand/README.md b/assets/brand/README.mdindex 2a0c827..88631a9 100644--- a/assets/brand/README.md+++ b/assets/brand/README.md@@ -1,4 +1,4 @@-# The Nectarlink mark+# The NectarLink markThe Waggle Dance: two loops, the phone and the PC, around a drop of nectar,tilted like the run of a honeybee's waggle dance, which is how bees tell eachdiff --git a/core/nectarlink-adb/Cargo.toml b/core/nectarlink-adb/Cargo.tomlindex 2c9ac81..717f5b6 100644--- a/core/nectarlink-adb/Cargo.toml+++ b/core/nectarlink-adb/Cargo.toml@@ -1,6 +1,6 @@[package]name = "nectarlink-adb"-description = "Pure-Rust ADB server client for Nectarlink USB transport"+description = "Pure-Rust ADB server client for NectarLink USB transport"license = "MPL-2.0"version.workspace = trueedition.workspace = truediff --git a/core/nectarlink-adb/src/lib.rs b/core/nectarlink-adb/src/lib.rsindex 3a8216b..48c4a3f 100644--- a/core/nectarlink-adb/src/lib.rs+++ b/core/nectarlink-adb/src/lib.rs@@ -1,6 +1,6 @@// SPDX-License-Identifier: MPL-2.0//! Pure-Rust client for the local ADB server (`127.0.0.1:5037`) used to detect-//! USB-attached Android devices and set up TCP port forwarding for Nectarlink's+//! USB-attached Android devices and set up TCP port forwarding for NectarLink's//! USB QUIC tunnel.use std::net::{Ipv4Addr, SocketAddr, SocketAddrV4};diff --git a/core/nectarlink-cli/Cargo.toml b/core/nectarlink-cli/Cargo.tomlindex 81aef4d..fc5c976 100644--- a/core/nectarlink-cli/Cargo.toml+++ b/core/nectarlink-cli/Cargo.toml@@ -1,6 +1,6 @@[package]name = "nectarlink-cli"-description = "Nectarlink command-line client for development and scripting"+description = "NectarLink command-line client for development and scripting"license = "GPL-3.0-or-later"version.workspace = trueedition.workspace = truediff --git a/core/nectarlink-cli/src/main.rs b/core/nectarlink-cli/src/main.rsindex f8c6f02..deadb8b 100644--- a/core/nectarlink-cli/src/main.rs+++ b/core/nectarlink-cli/src/main.rs@@ -20,7 +20,7 @@ use nectarlink_core::{use tokio::sync::broadcast::error::RecvError;#[derive(Parser, Debug)]-#[command(name = "nectarlink", version, about = "Nectarlink command-line client")]+#[command(name = "nectarlink", version, about = "NectarLink command-line client")]struct Cli {/// Where this client keeps its identity and paired devices.#[arg(long, global = true, env = "NECTARLINK_DATA_DIR")]@@ -1715,11 +1715,11 @@ fn sample_storage_tree(root: &std::path::Path) {("Documents/notes.txt", b"Shopping list:\n- Coffee beans\n- Oats\n- Sparkling water\n"),("Documents/project-plan.md",- b"# Nectarlink Storage\n\nBrowse phone files directly in File Explorer.\n",+ b"# NectarLink Storage\n\nBrowse phone files directly in File Explorer.\n",),("Download/guide.txt",- b"Welcome to Nectarlink Phone Storage.\nOpen any file to stream it on demand.\n",+ b"Welcome to NectarLink Phone Storage.\nOpen any file to stream it on demand.\n",),("DCIM/Camera/IMG_20260406_184210.jpg",@@ -2452,7 +2452,7 @@ async fn start_node(cli: &Cli) -> Result<Node> {None => dirs::data_local_dir().context("no local data directory")?.join("Nectarlink").join("cli"),};let name = cli.name.clone().unwrap_or_else(|| {- hostname::get().ok().and_then(|h| h.into_string().ok()).unwrap_or_else(|| "Nectarlink CLI".into())+ hostname::get().ok().and_then(|h| h.into_string().ok()).unwrap_or_else(|| "NectarLink CLI".into())});let (kind, os, os_ver) = if cli.as_phone {(DeviceKind::Phone, "android".into(), "16".into())@@ -3966,7 +3966,7 @@ async fn pair(node: &Node) -> Result<()> {let link = node.pairing_start_qr().await?;let uri = link.to_uri();print_qr(&uri);- println!("\nScan this code in the Nectarlink app, or run on another machine:");+ println!("\nScan this code in the NectarLink app, or run on another machine:");println!(" nectarlink join \"{uri}\"\n");println!("Waiting for a device (pairing mode ends in 5 minutes)…");loop {@@ -4344,7 +4344,7 @@ async fn play(app: app.into(),title: Some(if track == 1 { title.to_owned() } else { format!("{title} ({track})") }),artist: Some(artist.into()),- album: Some("Nectarlink Test Album".into()),+ album: Some("NectarLink Test Album".into()),playing,duration: Some(length),position: Some(position),@@ -4891,7 +4891,7 @@ fn resolve(node: &Node, query: &str) -> Result<DeviceId> {}}-/// Resolves a target for `send`: a paired Nectarlink device, a discovered+/// Resolves a target for `send`: a paired NectarLink device, a discovered/// LocalSend peer, or a `host[:port]` LocalSend address.async fn resolve_send_target(node: &Node, query: &str, default_port: u16) -> Result<(DeviceId, bool)> {if let Ok(id) = resolve(node, query)diff --git a/core/nectarlink-core/Cargo.toml b/core/nectarlink-core/Cargo.tomlindex 5314c4d..16036d2 100644--- a/core/nectarlink-core/Cargo.toml+++ b/core/nectarlink-core/Cargo.toml@@ -1,6 +1,6 @@[package]name = "nectarlink-core"-description = "Nectarlink engine: identity, pairing, sessions and storage"+description = "NectarLink engine: identity, pairing, sessions and storage"license = "MPL-2.0"version.workspace = trueedition.workspace = truediff --git a/core/nectarlink-core/src/identity.rs b/core/nectarlink-core/src/identity.rsindex 1dcc0f2..a2ef195 100644--- a/core/nectarlink-core/src/identity.rs+++ b/core/nectarlink-core/src/identity.rs@@ -162,7 +162,7 @@ mod dpapi {unsafe {CryptProtectData(&input,- windows::core::w!("Nectarlink device key"),+ windows::core::w!("NectarLink device key"),Some(&entropy),None,None,@@ -201,7 +201,7 @@ mod dpapi {/// The install ID a device reports to its peers ([`DeviceInfo::install_id`]): a salted/// BLAKE3 hash of a platform ID that survives app reinstalls (Android's `ANDROID_ID`,/// Windows' `MachineGuid`). The raw ID never leaves the device; the salt keeps the hash-/// specific to Nectarlink, so it can't be matched against other apps' identifiers.+/// specific to NectarLink, so it can't be matched against other apps' identifiers.////// [`DeviceInfo::install_id`]: nectarlink_protocol::messages::DeviceInfo::install_idpub fn install_id_from(platform_id: &str) -> Option<String> {diff --git a/core/nectarlink-core/src/lib.rs b/core/nectarlink-core/src/lib.rsindex 1524ade..52c767e 100644--- a/core/nectarlink-core/src/lib.rs+++ b/core/nectarlink-core/src/lib.rs@@ -1,5 +1,5 @@// SPDX-License-Identifier: MPL-2.0-//! The Nectarlink engine: device identity, pairing, sessions with paired+//! The NectarLink engine: device identity, pairing, sessions with paired//! devices, and storage. Shared by the Windows and Android apps.//!//! The entry point is [`Node`]. Commands are async methods; everything thatdiff --git a/core/nectarlink-core/src/localsend.rs b/core/nectarlink-core/src/localsend.rsindex cabd8a6..24e26f8 100644--- a/core/nectarlink-core/src/localsend.rs+++ b/core/nectarlink-core/src/localsend.rs@@ -7,7 +7,7 @@//! - Listens on UDP multicast `224.0.0.167:53317` (with `SO_REUSEADDR`) and TCP//! port `53317` (configurable via `NodeConfig::localsend_port`).//! - If TCP port `53317` is already taken by the standalone LocalSend app on the-//! same PC, Nectarlink logs a notice, leaves receiving to LocalSend, and still+//! same PC, NectarLink logs a notice, leaves receiving to LocalSend, and still//! discovers and sends files to LocalSend peers on the network.use std::{@@ -92,7 +92,7 @@ pub struct LocalSendPeer {pub protocol: String,}-/// Derives a deterministic Nectarlink [`DeviceId`] for a LocalSend peer from its+/// Derives a deterministic NectarLink [`DeviceId`] for a LocalSend peer from its/// certificate fingerprint (or `ip:port` when encryption is off).pub fn peer_device_id(fingerprint: &str, ip: &str, port: u16) -> DeviceId {let mut hasher = Sha256::new();@@ -430,7 +430,7 @@ impl LocalSendState {tracing::info!(port = configured_port,error = %e,- "LocalSend TCP port is in use by another app; Nectarlink will still discover and send to LocalSend peers"+ "LocalSend TCP port is in use by another app; NectarLink will still discover and send to LocalSend peers");None}@@ -557,7 +557,7 @@ fn build_our_multicast_dto(shared: &Shared, port: u16, announce: bool) -> MulticMulticastDto {alias: device.name,version: LOCALSEND_PROTOCOL_VERSION.into(),- device_model: device.model.or_else(|| Some("Nectarlink".into())),+ device_model: device.model.or_else(|| Some("NectarLink".into())),device_type: Some(device_kind_str(device.kind).into()),fingerprint: shared.localsend.identity.fingerprint.clone(),port,@@ -574,7 +574,7 @@ fn build_our_info_dto(shared: &Shared) -> InfoDto {InfoDto {alias: device.name,version: LOCALSEND_PROTOCOL_VERSION.into(),- device_model: device.model.or_else(|| Some("Nectarlink".into())),+ device_model: device.model.or_else(|| Some("NectarLink".into())),device_type: Some(device_kind_str(device.kind).into()),fingerprint: shared.localsend.identity.fingerprint.clone(),port: Some(port),diff --git a/core/nectarlink-core/src/node.rs b/core/nectarlink-core/src/node.rsindex c23fb2c..48effa2 100644--- a/core/nectarlink-core/src/node.rs+++ b/core/nectarlink-core/src/node.rs@@ -1298,7 +1298,7 @@ impl ProtocolHandler for PairProtocol {}}-/// The Nectarlink engine. One per app.+/// The NectarLink engine. One per app.////// Commands are async methods; everything that changes is reported through/// [`Node::events`]. Cheap to clone.diff --git a/core/nectarlink-core/src/otp.rs b/core/nectarlink-core/src/otp.rsindex 285fc69..66e434c 100644--- a/core/nectarlink-core/src/otp.rs+++ b/core/nectarlink-core/src/otp.rs@@ -700,7 +700,7 @@ mod tests {("Use PIN 7391 to sign in to your workspace.", "7391"),("Sign in with one-time code 582019", "582019"),("Your 2FA code for GitHub is 394821.", "394821"),- ("Enter 601928 to log in to Nectarlink.", "601928"),+ ("Enter 601928 to log in to NectarLink.", "601928"),// Prefixed & hyphenated formats("G-482193 is your Google verification code.", "482193"),("G-123456 is your Google verification code", "123456"),diff --git a/core/nectarlink-core/src/store.rs b/core/nectarlink-core/src/store.rsindex 08b9cf4..b81b057 100644--- a/core/nectarlink-core/src/store.rs+++ b/core/nectarlink-core/src/store.rs@@ -2383,7 +2383,7 @@ fn migrate(conn: &Connection) -> Result<()> {let current = usize::try_from(current).unwrap_or(usize::MAX);if current > MIGRATIONS.len() {return Err(Error::Storage(format!(- "the database was created by a newer Nectarlink (schema {current}); please update"+ "the database was created by a newer NectarLink (schema {current}); please update")));}for (index, sql) in MIGRATIONS.iter().enumerate().skip(current) {diff --git a/core/nectarlink-core/tests/two_devices.rs b/core/nectarlink-core/tests/two_devices.rsindex 63d3a82..5273693 100644--- a/core/nectarlink-core/tests/two_devices.rs+++ b/core/nectarlink-core/tests/two_devices.rs@@ -2466,7 +2466,7 @@ async fn remote_input_needs_toggle_and_delivers_motion_keys_and_slides() {RemoteInput::Button { button: MouseButton::Left, action: ButtonAction::Down },RemoteInput::Button { button: MouseButton::Left, action: ButtonAction::Up },RemoteInput::Scroll { dx: 0.0, dy: -3.0 },- RemoteInput::Text { text: "Hello Nectarlink 🐝".into() },+ RemoteInput::Text { text: "Hello NectarLink 🐝".into() },RemoteInput::Key { key: remote_keys::ENTER.into(), mods: vec![] },RemoteInput::Key { key: "c".into(), mods: vec![KeyMod::Ctrl] },RemoteInput::Key { key: remote_keys::COPY.into(), mods: vec![] },@@ -4253,7 +4253,7 @@ async fn localsend_coexists_when_port_is_already_bound() {assert!(dev.node.localsend_enabled());assert!(!dev.node.localsend_receiving(),- "when port is occupied by standalone LocalSend, Nectarlink must leave receiving to it without failing"+ "when port is occupied by standalone LocalSend, NectarLink must leave receiving to it without failing");dev.node.shutdown().await;diff --git a/core/nectarlink-ffi/src/lib.rs b/core/nectarlink-ffi/src/lib.rsindex 3777c77..f2eaa9b 100644--- a/core/nectarlink-ffi/src/lib.rs+++ b/core/nectarlink-ffi/src/lib.rs@@ -3119,7 +3119,7 @@ pub struct NodeOptions {pub usb_port: Option<u16>,}-/// The Nectarlink engine. One per app process.+/// The NectarLink engine. One per app process.#[derive(uniffi::Object)]pub struct NectarlinkNode {runtime: Runtime,diff --git a/core/nectarlink-protocol/Cargo.toml b/core/nectarlink-protocol/Cargo.tomlindex d374acd..18a2a66 100644--- a/core/nectarlink-protocol/Cargo.toml+++ b/core/nectarlink-protocol/Cargo.toml@@ -1,6 +1,6 @@[package]name = "nectarlink-protocol"-description = "Nectarlink wire protocol: message types, framing and pairing primitives"+description = "NectarLink wire protocol: message types, framing and pairing primitives"license = "MPL-2.0"version.workspace = trueedition.workspace = truediff --git a/core/nectarlink-protocol/src/lib.rs b/core/nectarlink-protocol/src/lib.rsindex d0adfe6..69d63cf 100644--- a/core/nectarlink-protocol/src/lib.rs+++ b/core/nectarlink-protocol/src/lib.rs@@ -1,5 +1,5 @@// SPDX-License-Identifier: MPL-2.0-//! The Nectarlink wire protocol (version 0).+//! The NectarLink wire protocol (version 0).//!//! This crate is pure protocol logic with no networking: device IDs, message//! types, the CBOR envelope, length-prefixed framing and the pairingdiff --git a/core/nectarlink-protocol/src/pairing.rs b/core/nectarlink-protocol/src/pairing.rsindex ad76fb0..a0eaf08 100644--- a/core/nectarlink-protocol/src/pairing.rs+++ b/core/nectarlink-protocol/src/pairing.rs@@ -32,9 +32,9 @@ pub struct PairingUri {#[derive(Debug, thiserror::Error, PartialEq, Eq)]pub enum PairingUriError {- #[error("not a Nectarlink pairing link")]+ #[error("not a NectarLink pairing link")]NotPairing,- #[error("pairing link version {0} is not supported; please update Nectarlink")]+ #[error("pairing link version {0} is not supported; please update NectarLink")]UnsupportedVersion(String),#[error("pairing link is missing {0}")]Missing(&'static str),diff --git a/desktop/app/Cargo.toml b/desktop/app/Cargo.tomlindex 2178897..e744f09 100644--- a/desktop/app/Cargo.toml+++ b/desktop/app/Cargo.toml@@ -1,6 +1,6 @@[package]name = "nectarlink-desktop"-description = "Nectarlink for Windows: the desktop app"+description = "NectarLink for Windows: the desktop app"version.workspace = trueedition.workspace = true# Above the workspace minimum: material-colors needs Rust 1.97.diff --git a/desktop/app/build.rs b/desktop/app/build.rsindex e69e59f..8aab16e 100644--- a/desktop/app/build.rs+++ b/desktop/app/build.rs@@ -212,13 +212,13 @@ BEGINBEGINBLOCK "040904B0"BEGIN- VALUE "CompanyName", "The Nectarlink contributors"- VALUE "FileDescription", "Nectarlink"+ VALUE "CompanyName", "The NectarLink contributors"+ VALUE "FileDescription", "NectarLink"VALUE "FileVersion", "{version}"VALUE "InternalName", "nectarlink-desktop"VALUE "LegalCopyright", "GPL-3.0-or-later"VALUE "OriginalFilename", "nectarlink-desktop.exe"- VALUE "ProductName", "Nectarlink"+ VALUE "ProductName", "NectarLink"VALUE "ProductVersion", "{version}"ENDENDdiff --git a/desktop/app/qml/App.qml b/desktop/app/qml/App.qmlindex 0436f08..4dbfb81 100644--- a/desktop/app/qml/App.qml+++ b/desktop/app/qml/App.qml@@ -5,7 +5,7 @@ import QtQml.Modelsimport app.nectarlink// Application root. The main window exists only while it's open: closing it-// destroys it (freeing its GPU resources) and Nectarlink keeps running in+// destroys it (freeing its GPU resources) and NectarLink keeps running in// the tray. A tray click, a second launch or a ringing request reopens it.QtObject {id: appdiff --git a/desktop/app/qml/IslandWindow.qml b/desktop/app/qml/IslandWindow.qmlindex 368daca..9b45a1e 100644--- a/desktop/app/qml/IslandWindow.qml+++ b/desktop/app/qml/IslandWindow.qml@@ -255,7 +255,7 @@ Window {: base}if (mode === "notification")- return qsTr("Click to view in Nectarlink")+ return qsTr("Click to view in NectarLink")if (mode === "waiting") {return DeviceList.count > 0? qsTr("Will send when %1 is back").arg(DeviceList.deviceNameAt(0))diff --git a/desktop/app/qml/MainWindow.qml b/desktop/app/qml/MainWindow.qmlindex b7ccb53..4ef2065 100644--- a/desktop/app/qml/MainWindow.qml+++ b/desktop/app/qml/MainWindow.qml@@ -112,7 +112,7 @@ NativeWindow {height: 740minimumWidth: Theme.layout.minWindow[0]minimumHeight: Theme.layout.minWindow[1]- title: "Nectarlink"+ title: "NectarLink"property bool resizing: resizeSettleTimer.runningTimer {diff --git a/desktop/app/qml/MirrorWindow.qml b/desktop/app/qml/MirrorWindow.qmlindex f1965a9..7e105b6 100644--- a/desktop/app/qml/MirrorWindow.qml+++ b/desktop/app/qml/MirrorWindow.qml@@ -22,7 +22,7 @@ Window {visible: truetitle: info.app ? qsTr("%1 · %2").arg(info.title).arg(deviceName)- : deviceName.length > 0 ? qsTr("%1 · Nectarlink").arg(deviceName) : qsTr("Phone screen · Nectarlink")+ : deviceName.length > 0 ? qsTr("%1 · NectarLink").arg(deviceName) : qsTr("Phone screen · NectarLink")color: "black"minimumWidth: 240minimumHeight: 240@@ -448,7 +448,7 @@ Window {wrapMode: Text.WordWraprole: "bodySmall"color: "white"- text: qsTr("To control the phone, turn on Control from your PC in Nectarlink's settings on the phone.")+ text: qsTr("To control the phone, turn on Control from your PC in NectarLink's settings on the phone.")}Button {id: notifyPhoneBtndiff --git a/desktop/app/qml/ShelfWindow.qml b/desktop/app/qml/ShelfWindow.qmlindex cab8393..7c7fdbe 100644--- a/desktop/app/qml/ShelfWindow.qml+++ b/desktop/app/qml/ShelfWindow.qml@@ -13,7 +13,7 @@ import app.nectarlinkWindow {id: shelfWin- title: "Nectarlink Shelf"+ title: "NectarLink Shelf"flags: Qt.Tool | Qt.FramelessWindowHint | Qt.WindowStaysOnTopHint | Qt.WindowDoesNotAcceptFocuscolor: "transparent"visible: truediff --git a/desktop/app/qml/components/LockChip.qml b/desktop/app/qml/components/LockChip.qmlindex 1629229..6490242 100644--- a/desktop/app/qml/components/LockChip.qml+++ b/desktop/app/qml/components/LockChip.qml@@ -43,21 +43,21 @@ Rectangle {const s = feature || {}switch (lockKind) {case "assist":- return qsTr("On your phone, open Nectarlink › Settings › Control from your PC and turn on the Accessibility service.")+ return qsTr("On your phone, open NectarLink › Settings › Control from your PC and turn on the Accessibility service.")case "elevated":return qsTr("Needs Elevated: set up Wireless debugging or connect over USB.")case "role":- return qsTr("On your phone, set Nectarlink as the default SMS/Caller ID app when prompted.")+ return qsTr("On your phone, set NectarLink as the default SMS/Caller ID app when prompted.")case "permission":if (s.target === "notification_access")- return qsTr("On your phone, open Nectarlink and allow Notification access.")+ return qsTr("On your phone, open NectarLink and allow Notification access.")if (s.target === "dnd_access")- return qsTr("On your phone, open Nectarlink and allow Do Not Disturb access.")+ return qsTr("On your phone, open NectarLink and allow Do Not Disturb access.")if (s.target === "write_settings")- return qsTr("On your phone, open Nectarlink and allow Modify system settings.")- return qsTr("Open Nectarlink on your phone and grant this permission in Settings.")+ return qsTr("On your phone, open NectarLink and allow Modify system settings.")+ return qsTr("Open NectarLink on your phone and grant this permission in Settings.")case "enableAddon":- return qsTr("Open Settings › Camera & Audio to set up the Nectarlink virtual camera add-on.")+ return qsTr("Open Settings › Camera & Audio to set up the NectarLink virtual camera add-on.")case "enablePath":return qsTr("Open Settings › Connection & About and turn on Connect over mobile data.")case "enableToggle":diff --git a/desktop/app/qml/pages/AppsPage.qml b/desktop/app/qml/pages/AppsPage.qmlindex 60823aa..0aac3d7 100644--- a/desktop/app/qml/pages/AppsPage.qml+++ b/desktop/app/qml/pages/AppsPage.qml@@ -87,7 +87,7 @@ Item {muted: truetext: page.deviceId.length === 0? qsTr("Pair your phone to open its apps in windows on this PC.")- : (page.feature.reason || qsTr("Set up Wireless debugging in Nectarlink on the phone to open its apps here."))+ : (page.feature.reason || qsTr("Set up Wireless debugging in NectarLink on the phone to open its apps here."))}LockChip {anchors.horizontalCenter: parent.horizontalCenterdiff --git a/desktop/app/qml/pages/FeaturesGuidePage.qml b/desktop/app/qml/pages/FeaturesGuidePage.qmlindex 54ba6ab..b03ff68 100644--- a/desktop/app/qml/pages/FeaturesGuidePage.qml+++ b/desktop/app/qml/pages/FeaturesGuidePage.qml@@ -4,7 +4,7 @@ import QtQuick.Layoutsimport app.nectarlink// In-app Features Guide page: searchable and filterable reference to every-// Nectarlink feature, live capability status when a phone is connected,+// NectarLink feature, live capability status when a phone is connected,// "Show me" navigation, and "Learn more" reader sheet with handbook tabs.Item {id: guide@@ -249,7 +249,7 @@ Item {area: "camera_audio",capKey: "webcam",toggleKey: "",- summary: "Use your phone camera as the Nectarlink Virtual Camera in Zoom, Teams, Meet, and OBS.",+ summary: "Use your phone camera as the NectarLink Virtual Camera in Zoom, Teams, Meet, and OBS.",whereLabel: "Home › Phone as webcam",needsLabel: "Camera permission on phone and Virtual Camera registered on PC",targetId: "settings:camera_audio:webcam",@@ -569,7 +569,7 @@ Item {Txt {Layout.fillWidth: true- text: "Every feature in Nectarlink, what it needs, and where to find it."+ text: "Every feature in NectarLink, what it needs, and where to find it."role: "body"color: Theme.surfaceContentVariantwrapMode: Text.WordWrapdiff --git a/desktop/app/qml/pages/PairingPanel.qml b/desktop/app/qml/pages/PairingPanel.qmlindex 86a00a9..1f2fa1b 100644--- a/desktop/app/qml/pages/PairingPanel.qml+++ b/desktop/app/qml/pages/PairingPanel.qml@@ -96,7 +96,7 @@ Item {anchors.horizontalCenter: parent.horizontalCenterspacing: 14Repeater {- model: [qsTr("Install Nectarlink"), qsTr("Tap “Pair with PC”"), qsTr("Scan this code")]+ model: [qsTr("Install NectarLink"), qsTr("Tap “Pair with PC”"), qsTr("Scan this code")]delegate: Row {required property int indexrequired property string modelData@@ -169,7 +169,7 @@ Item {width: parent.widthspacing: 6Repeater {- model: [qsTr("Open Nectarlink on your phone"), qsTr("Tap “Pair with PC”"), qsTr("Scan this QR code")]+ model: [qsTr("Open NectarLink on your phone"), qsTr("Tap “Pair with PC”"), qsTr("Scan this QR code")]delegate: Row {required property int indexrequired property string modelData@@ -217,7 +217,7 @@ Item {wrapMode: Text.WordWraprole: "body"muted: true- text: qsTr("On your phone, open Nectarlink and choose “Pair nearby”. It shows up here.")+ text: qsTr("On your phone, open NectarLink and choose “Pair nearby”. It shows up here.")}Repeater {model: Pairing.nearbydiff --git a/desktop/app/qml/pages/SettingsPage.qml b/desktop/app/qml/pages/SettingsPage.qmlindex 0017fd4..0d4aeb3 100644--- a/desktop/app/qml/pages/SettingsPage.qml+++ b/desktop/app/qml/pages/SettingsPage.qml@@ -2982,7 +2982,7 @@ Item {ListRow {width: parent.widthiconPath: Icons.desktop- title: qsTr("Nectarlink %1").arg(AppController.version)+ title: qsTr("NectarLink %1").arg(AppController.version)description: AppController.updateStatus.length > 0? AppController.updateStatus: qsTr("This PC: %1").arg(AppController.deviceName)diff --git a/desktop/app/qml/pages/WalkthroughPage.qml b/desktop/app/qml/pages/WalkthroughPage.qmlindex 2011386..ee8c420 100644--- a/desktop/app/qml/pages/WalkthroughPage.qml+++ b/desktop/app/qml/pages/WalkthroughPage.qml@@ -95,9 +95,9 @@ FocusScope {]readonly property var stepTitles: [- "Welcome to Nectarlink",+ "Welcome to NectarLink","Your data stays on your devices",- "Install Nectarlink on your phone",+ "Install NectarLink on your phone","Pair your phone and PC","Choose what to share","Optional setup",@@ -108,7 +108,7 @@ FocusScope {"Your Android phone and Windows PC, working together on your local network.","No accounts, no cloud servers, and no telemetry.","Get the Android app from GitHub Releases or install the APK over USB.",- "Scan the QR code from the Nectarlink Android app, or pick your phone from nearby devices.",+ "Scan the QR code from the NectarLink Android app, or pick your phone from nearby devices.","Safe features are on by default. Higher-trust access stays off until you turn it on.","Three quick checks so notifications and discovery work reliably in Windows.","Reopen it from Settings or the Command Palette."@@ -918,7 +918,7 @@ FocusScope {}}- // STEP 2: Install Nectarlink on your phone+ // STEP 2: Install NectarLink on your phoneColumnLayout {Layout.fillWidth: truespacing: 12@@ -1468,7 +1468,7 @@ FocusScope {Layout.fillWidth: truetext: AppController.toastsEnabled? "Enabled in Windows Settings."- : "Notifications are off for Nectarlink in Windows Settings."+ : "Notifications are off for NectarLink in Windows Settings."role: "caption"color: Theme.surfaceContentVariantwrapMode: Text.WordWrap@@ -1544,7 +1544,7 @@ FocusScope {Txt {Layout.fillWidth: true- text: "Keep Nectarlink ready in the system tray when you sign in."+ text: "Keep NectarLink ready in the system tray when you sign in."role: "caption"color: Theme.surfaceContentVariantwrapMode: Text.WordWrap@@ -1647,7 +1647,7 @@ FocusScope {: "Pair a phone anytime from Home",body: walkthrough.hasPairedDevice? "Your phone is linked and ready on your local network."- : "Open the Nectarlink Android app whenever you are ready to scan the QR code."+ : "Open the NectarLink Android app whenever you are ready to scan the QR code."},{icon: Icons.search,@@ -1657,7 +1657,7 @@ FocusScope {{icon: Icons.book,title: "Features guide",- body: "Browse every feature in Nectarlink, see what permissions it needs, and jump straight to it."+ body: "Browse every feature in NectarLink, see what permissions it needs, and jump straight to it."}]diff --git a/desktop/app/qml/pages/WelcomePage.qml b/desktop/app/qml/pages/WelcomePage.qmlindex 7e3fa3f..108ff18 100644--- a/desktop/app/qml/pages/WelcomePage.qml+++ b/desktop/app/qml/pages/WelcomePage.qml@@ -33,7 +33,7 @@ Item {Txt {width: parent.widthhorizontalAlignment: Text.AlignHCenter- text: qsTr("Welcome to Nectarlink")+ text: qsTr("Welcome to NectarLink")role: "displaySmall"}Txt {@@ -43,7 +43,7 @@ Item {role: "body"muted: truetext: page.status === "failed"- ? qsTr("Nectarlink couldn't start.")+ ? qsTr("NectarLink couldn't start."): qsTr("Your phone and this PC, together. Pair once and they find each other from then on.")}}diff --git a/desktop/app/qml/setup/SetupWindow.qml b/desktop/app/qml/setup/SetupWindow.qmlindex 1660136..4e699b2 100644--- a/desktop/app/qml/setup/SetupWindow.qml+++ b/desktop/app/qml/setup/SetupWindow.qml@@ -41,7 +41,7 @@ NativeWindow {minimumHeight: heightmaximumHeight: heightvisible: true- title: removing ? qsTr("Uninstall Nectarlink") : qsTr("Nectarlink Setup")+ title: removing ? qsTr("Uninstall NectarLink") : qsTr("NectarLink Setup")color: bgbackdrop: falsedarkFrame: dark@@ -155,7 +155,7 @@ NativeWindow {mipmap: truescale: 1 + emblem.breath * 0.04Accessible.role: Accessible.Graphic- Accessible.name: qsTr("Nectarlink")+ Accessible.name: qsTr("NectarLink")}SadBee {anchors.centerIn: parent@@ -184,13 +184,13 @@ NativeWindow {font.weight: Font.DemiBoldcolor: window.inktext: window.phase === "failed"- ? (window.removing ? qsTr("Couldn't uninstall Nectarlink") : qsTr("Setup couldn't finish"))+ ? (window.removing ? qsTr("Couldn't uninstall NectarLink") : qsTr("Setup couldn't finish")): window.phase === "working"- ? (window.action === "remove" ? qsTr("Uninstalling Nectarlink")- : window.action === "update" ? qsTr("Updating Nectarlink")- : qsTr("Installing Nectarlink"))- : window.removing ? qsTr("Uninstall Nectarlink?")- : "Nectarlink"+ ? (window.action === "remove" ? qsTr("Uninstalling NectarLink")+ : window.action === "update" ? qsTr("Updating NectarLink")+ : qsTr("Installing NectarLink"))+ : window.removing ? qsTr("Uninstall NectarLink?")+ : "NectarLink"}Item { width: 1; height: 10 }Text {@@ -204,7 +204,7 @@ NativeWindow {text: window.phase === "failed" ? Setup.message: window.phase === "working" ? Setup.step: window.removing- ? qsTr("Sorry to see you go. This uninstalls Nectarlink and deletes its settings and pairings on this PC. Files you received stay in Downloads\\Nectarlink.")+ ? qsTr("Sorry to see you go. This uninstalls NectarLink and deletes its settings and pairings on this PC. Files you received stay in Downloads\\Nectarlink."): Setup.kind === "update"? qsTr("Update from %1 to %2. Your settings and pairings stay as they are.").arg(Setup.installedVersion).arg(Setup.version): Setup.kind === "reinstall"@@ -266,7 +266,7 @@ NativeWindow {SetupButton {visible: window.removing || window.phase === "failed"filled: false- text: window.removing && window.phase !== "failed" ? qsTr("Keep Nectarlink") : qsTr("Close")+ text: window.removing && window.phase !== "failed" ? qsTr("Keep NectarLink") : qsTr("Close")ink: window.inkfocusColor: window.honeyonClicked: window.close()@@ -314,7 +314,7 @@ NativeWindow {font.pixelSize: 28font.weight: Font.DemiBoldcolor: window.ink- text: window.removing ? qsTr("Nectarlink is uninstalled") : qsTr("Nectarlink is ready")+ text: window.removing ? qsTr("NectarLink is uninstalled") : qsTr("NectarLink is ready")}Item { width: 1; height: 8 }Text {@@ -376,7 +376,7 @@ NativeWindow {anchors.horizontalCenter: parent.horizontalCenterspacing: 12SetupButton {- text: window.removing ? qsTr("Close") : qsTr("Open Nectarlink")+ text: window.removing ? qsTr("Close") : qsTr("Open NectarLink")fill: window.removing ? window.ink : window.honeyink: window.removing ? window.bg : window.onHoneyfocusColor: window.honey@@ -436,7 +436,7 @@ NativeWindow {font.pixelSize: 14color: window.mutedtextFormat: Text.StyledText- text: qsTr("Nectarlink goes into Program Files for everyone on this PC. Setup also:")+ text: qsTr("NectarLink goes into Program Files for everyone on this PC. Setup also:")+ "<br>• " + qsTr("allows it through Windows Firewall on private networks, so your phone can connect")+ "<br>• " + qsTr("adds a task that installs updates without an administrator prompt")+ "<br>• " + qsTr("adds Start menu and desktop shortcuts, and starts it with Windows (turn this off in Settings)")diff --git a/desktop/app/src/automations.rs b/desktop/app/src/automations.rsindex 62097d1..8d2bb45 100644--- a/desktop/app/src/automations.rs+++ b/desktop/app/src/automations.rs@@ -75,7 +75,7 @@ fn execute_rule(rule: &AutomationRule) {tracing::warn!(rule = %rule.name, trigger = %rule.trigger, error = %e, "automation action failed");} else {let _ = crate::pc_notifications::forward_to_phones(- "Nectarlink Automations",+ "NectarLink Automations",&rule.name,&format!("Triggered by {}", rule.trigger),);diff --git a/desktop/app/src/battery.rs b/desktop/app/src/battery.rsindex 9be14cd..1faf19f 100644--- a/desktop/app/src/battery.rs+++ b/desktop/app/src/battery.rs@@ -92,7 +92,7 @@ pub fn on_event(event: &NodeEvent) {key: device.to_string(),title,body,- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: None,image: None,actions: Vec::new(),diff --git a/desktop/app/src/bridge/app.rs b/desktop/app/src/bridge/app.rsindex abba1b4..cc92100 100644--- a/desktop/app/src/bridge/app.rs+++ b/desktop/app/src/bridge/app.rs@@ -529,7 +529,7 @@ pub fn install_update_in_background() {object.as_mut().set_update_progress(-1.0);object.as_mut()- .set_update_status(QString::from("Installing. Nectarlink reopens by itself."));+ .set_update_status(QString::from("Installing. NectarLink reopens by itself."));}Err(message) => {object.as_mut().set_update_busy(false);@@ -802,16 +802,16 @@ impl cxx_qt::Initialize for qobject::AppController {);let labels = tray::MenuLabels {- open: "Open Nectarlink".into(),+ open: "Open NectarLink".into(),command_palette: "Command palette".into(),shelf: "Toggle Shelf".into(),take_photo: "Take photo with phone".into(),scan_document: "Scan document with phone".into(),find_phone: "Find my phone".into(),open_link: "Open copied link on phone".into(),- quit: "Quit Nectarlink".into(),+ quit: "Quit NectarLink".into(),};- match tray::Tray::create("Nectarlink", labels, move |event| on_tray_event(&qt, event)) {+ match tray::Tray::create("NectarLink", labels, move |event| on_tray_event(&qt, event)) {Ok(tray) => self.rust_mut().tray = Some(tray),Err(e) => tracing::warn!(error = %e, "no tray icon"),}@@ -1247,13 +1247,13 @@ impl qobject::AppController {self.as_mut().set_phone_toggles_revision(toggles_version as i32);let mut tooltip = match (devices, online) {- (0, _) => "Nectarlink · no devices paired".to_owned(),- (_, 0) => "Nectarlink · not connected".to_owned(),+ (0, _) => "NectarLink · no devices paired".to_owned(),+ (_, 0) => "NectarLink · not connected".to_owned(),(_, 1) => battery.map_or_else(- || "Nectarlink · 1 device connected".to_owned(),- |b| format!("Nectarlink · {b}"),+ || "NectarLink · 1 device connected".to_owned(),+ |b| format!("NectarLink · {b}"),),- (_, n) => format!("Nectarlink · {n} devices connected"),+ (_, n) => format!("NectarLink · {n} devices connected"),};if waiting_count > 0 {tooltip.push_str(&format!(" · {waiting_count} waiting"));@@ -1835,7 +1835,7 @@ impl qobject::AppController {let json = compute_shelf_items_json(idx);self.as_mut().set_shelf_items(QString::from(&json));self.as_mut().set_shelf_open(true);- win::tray::apply_no_activate_style_by_title("Nectarlink Shelf");+ win::tray::apply_no_activate_style_by_title("NectarLink Shelf");}}@@ -1857,7 +1857,7 @@ impl qobject::AppController {}pub fn style_shelf_window(&self) {- win::tray::apply_no_activate_style_by_title("Nectarlink Shelf");+ win::tray::apply_no_activate_style_by_title("NectarLink Shelf");win::tray::apply_no_activate_style_by_title("Nectar Island");}@@ -2142,7 +2142,7 @@ fn find_guide_file_on_disk(file_stem: &str) -> Option<String> {fn load_guide_doc_content(raw_key: &str) -> (String, String) {let key = raw_key.trim().trim_end_matches(".md").to_ascii_lowercase();let top_level_title = match key.as_str() {- "overview" => Some("Nectarlink overview"),+ "overview" => Some("NectarLink overview"),"setup" => Some("Install and first-time setup"),"features" => Some("Features reference"),"permissions" => Some("Android permissions and why each is optional"),@@ -2159,8 +2159,8 @@ fn load_guide_doc_content(raw_key: &str) -> (String, String) {let (title, body) = match key.as_str() {"overview" => (- "Nectarlink overview",- "Nectarlink links your Android phone and your Windows 11 PC directly on your local network or over a USB cable.\n\n\+ "NectarLink overview",+ "NectarLink links your Android phone and your Windows 11 PC directly on your local network or over a USB cable.\n\n\How it works\n\- Devices discover each other over local Wi-Fi (mDNS) or USB (ADB reverse tunnel) and connect over QUIC (TLS 1.3).\n\- Every connection is mutually authenticated using Ed25519 device keys generated on each device.\n\@@ -2172,15 +2172,15 @@ fn load_guide_doc_content(raw_key: &str) -> (String, String) {),"setup" => ("Install and first-time setup",- "1. Install Nectarlink on your Windows 11 PC and your Android phone (Android 8.0 or newer).\n\+ "1. Install NectarLink on your Windows 11 PC and your Android phone (Android 8.0 or newer).\n\2. Connect both devices to the same Wi-Fi network, or plug your phone into your PC with a USB cable.\n\3. Open the Pair step in the setup walkthrough, or click + (Pair a new device) at the bottom of the left rail.\n\- 4. Scan the QR code from the Nectarlink Android app, or select your phone from the nearby devices list and confirm that the 6-digit code matches on both screens.\n\+ 4. Scan the QR code from the NectarLink Android app, or select your phone from the nearby devices list and confirm that the 6-digit code matches on both screens.\n\5. Choose which features to share for that phone and grant only the Android permissions you want to use.",),"permissions" => ("Android permissions and why each is optional",- "Nectarlink never asks for every permission up front. Each feature works independently:\n\n\+ "NectarLink never asks for every permission up front. Each feature works independently:\n\n\- Notification Access: Required only if you want phone notifications, inline replies, and notification-backed chat threads on your PC.\n\- SMS and Contacts: Required only if you want to read and send SMS/MMS messages or look up contact names on your PC.\n\- Phone and Call Log: Required only if you want incoming call alerts, call history, or dialing from your PC.\n\@@ -2189,22 +2189,22 @@ fn load_guide_doc_content(raw_key: &str) -> (String, String) {),"elevated" => ("Elevated and Assist modes",- "Most Nectarlink features work in Standard mode with regular Android permissions. Two optional modes unlock deeper system integration:\n\n\+ "Most NectarLink features work in Standard mode with regular Android permissions. Two optional modes unlock deeper system integration:\n\n\Elevated mode (Wireless debugging or root)\n\- Captures the phone screen without showing the Android cast confirmation prompt every time.\n\- Streams individual phone apps in separate desktop windows (virtual displays).\n\- Controls additional system quick toggles.\n\n\Assist mode (Android Accessibility Service)\n\- Injects mouse clicks, scrolling, and touch gestures when you control your phone from your PC.\n\- - Nectarlink never reads screen text or logs keystrokes through the Accessibility service.",+ - NectarLink never reads screen text or logs keystrokes through the Accessibility service.",),"troubleshooting" => ("Troubleshooting and Connection Doctor","If your phone and PC do not see each other:\n\n\1. Open Connection Doctor from Settings › Connection & About or the Command Palette.\n\- 2. Check that your Wi-Fi network profile in Windows is set to Private rather than Public, or click Fix in Connection Doctor to allow Nectarlink through Windows Firewall.\n\+ 2. Check that your Wi-Fi network profile in Windows is set to Private rather than Public, or click Fix in Connection Doctor to allow NectarLink through Windows Firewall.\n\3. Verify that both devices are on the same subnet and that guest Wi-Fi client isolation is turned off on your router.\n\- 4. You can also connect over a USB cable with USB debugging enabled; Nectarlink automatically sets up a local tunnel.",+ 4. You can also connect over a USB cable with USB debugging enabled; NectarLink automatically sets up a local tunnel.",),"privacy" => ("Privacy and security",@@ -2224,7 +2224,7 @@ fn load_guide_doc_content(raw_key: &str) -> (String, String) {- Settings › Notifications for per-app rules (Show, Silent, or Hidden) and Do Not Disturb sync.\n\- Settings › General › Copy one-time codes.\n\n\What it needs\n\- - Notification Access permission enabled for Nectarlink on your Android phone.\n\+ - Notification Access permission enabled for NectarLink on your Android phone.\n\- The per-device Notifications toggle enabled on your PC.",),"messages" => (@@ -2258,12 +2258,12 @@ fn load_guide_doc_content(raw_key: &str) -> (String, String) {- Settings › General › Sync clipboard to phone.\n\n\What it needs\n\- Automatic PC-to-phone clipboard send works whenever your phone is connected.\n\- - Background phone-to-PC clipboard sync on Android 10+ uses notifications, the Nectarlink quick tile, or Elevated mode.",+ - Background phone-to-PC clipboard sync on Android 10+ uses notifications, the NectarLink quick tile, or Elevated mode.",),"transfers" => ("Send files","What it does\n\- Sends files, folders, links, and text between your phone and PC at local network speed. If your phone is offline when you send, Nectarlink places the item in the Waiting to send queue and delivers it automatically as soon as your phone reconnects.\n\n\+ Sends files, folders, links, and text between your phone and PC at local network speed. If your phone is offline when you send, NectarLink places the item in the Waiting to send queue and delivers it automatically as soon as your phone reconnects.\n\n\Where to find it\n\- Home › Send files button, drag-and-drop anywhere on the window, Waiting to send card, and Transfers list.\n\- Windows File Explorer › right-click › Send to.\n\n\@@ -2297,7 +2297,7 @@ fn load_guide_doc_content(raw_key: &str) -> (String, String) {"What it does\n\Streams your Windows PC monitor to your phone so you can view your desktop from across the room and use your phone as a trackpad or laser pointer.\n\n\Where to find it\n\- - Started from the Nectarlink app on your phone.\n\+ - Started from the NectarLink app on your phone.\n\- Settings › Devices › Share PC screen to phone.\n\n\What it needs\n\- The per-device Share PC screen to phone switch on your PC, or one-time approval when your phone requests to view your screen.",@@ -2305,7 +2305,7 @@ fn load_guide_doc_content(raw_key: &str) -> (String, String) {"webcam" => ("Phone as webcam","What it does\n\- Streams your phone camera into the Nectarlink Virtual Camera on Windows so Zoom, Teams, Meet, Discord, and OBS can use your phone's rear or front camera at up to 4K.\n\n\+ Streams your phone camera into the NectarLink Virtual Camera on Windows so Zoom, Teams, Meet, Discord, and OBS can use your phone's rear or front camera at up to 4K.\n\n\Where to find it\n\- Home › Phone as webcam.\n\- Settings › Camera & Audio › Start webcam.\n\n\@@ -2370,7 +2370,7 @@ fn load_guide_doc_content(raw_key: &str) -> (String, String) {- Home › Type on phone.\n\- Command Palette › Type on phone with PC keyboard.\n\n\What it needs\n\- - Assist mode (Accessibility service), the Nectarlink input method, or Elevated mode on your phone.",+ - Assist mode (Accessibility service), the NectarLink input method, or Elevated mode on your phone.",),"phone-controls" => ("Phone controls",@@ -2417,7 +2417,7 @@ fn load_guide_doc_content(raw_key: &str) -> (String, String) {"What it does\n\Opens a keyboard-first search bar over actions, contacts, message threads, mirrorable apps, phone quick toggles, clipboard history, and navigation pages.\n\n\Where to find it\n\- - Global hotkey Ctrl+Alt+Space (or Ctrl+K inside the Nectarlink window).\n\+ - Global hotkey Ctrl+Alt+Space (or Ctrl+K inside the NectarLink window).\n\- Commands in the top bar.\n\n\What it needs\n\- Works at any time with zero background memory cost when closed.",@@ -2473,7 +2473,7 @@ fn load_guide_doc_content(raw_key: &str) -> (String, String) {"local-api" => ("Local HTTP API","What it does\n\- Exposes an opt-in localhost HTTP/JSON and Server-Sent Events API on 127.0.0.1 (default port 53320) protected by a bearer token so scripts, CLI tools, and Stream Deck plugins can trigger Nectarlink actions.\n\n\+ Exposes an opt-in localhost HTTP/JSON and Server-Sent Events API on 127.0.0.1 (default port 53320) protected by a bearer token so scripts, CLI tools, and Stream Deck plugins can trigger NectarLink actions.\n\n\Where to find it\n\- Settings › Connection & About › Local automation API.\n\n\What it needs\n\diff --git a/desktop/app/src/bridge/setup.rs b/desktop/app/src/bridge/setup.rsindex c825c51..ee1b47a 100644--- a/desktop/app/src/bridge/setup.rs+++ b/desktop/app/src/bridge/setup.rs@@ -80,7 +80,7 @@ pub struct SetupRust {}static MODE: OnceLock<Mode> = OnceLock::new();-/// Where the app ended up, for Open Nectarlink.+/// Where the app ended up, for Open NectarLink.static INSTALLED_DIR: Mutex<Option<PathBuf>> = Mutex::new(None);/// Sets what the window is for, before QML loads.@@ -208,7 +208,7 @@ impl qobject::Setup {if let Some(dir) = dir&& let Err(e) = setup::open_app(&dir){- tracing::warn!(error = %e, "can't open Nectarlink");+ tracing::warn!(error = %e, "can't open NectarLink");}}diff --git a/desktop/app/src/calls.rs b/desktop/app/src/calls.rsindex 49d3d66..13efe44 100644--- a/desktop/app/src/calls.rs+++ b/desktop/app/src/calls.rs@@ -308,7 +308,7 @@ fn show_ringing(device: DeviceId, call: &CallState, silenced: bool) {key: key(device, &call.id),title: caller(call),body,- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: call.photo.as_deref().and_then(|photo| save_photo(device, &call.id, photo)),image: None,actions,@@ -342,7 +342,7 @@ fn show_in_progress(device: DeviceId, call: &CallState) {key: format!("{ACTIVE}{}", key(device, &call.id)),title: format!("On a call with {}", caller(call)),body: format!("On {}", phone_name(device)),- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: None,image: None,actions,@@ -371,7 +371,7 @@ fn show_missed(device: DeviceId, call: &CallState) {key: format!("missed {}", key(device, &call.id)),title: format!("Missed call from {}", caller(call)),body: format!("On {}", phone_name(device)),- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: None,image: None,actions: Vec::new(),@@ -800,7 +800,7 @@ pub fn dial_problem(error: &Error) -> &'static str {match error {Error::Denied => "Calls are turned off for this phone.",Error::Unsupported => {- "The phone doesn't place calls for this PC. Allow it in the Nectarlink app on the phone."+ "The phone doesn't place calls for this PC. Allow it in the NectarLink app on the phone."}Error::Offline | Error::NotPaired | Error::Timeout => "The phone isn't connected.",_ => "The phone couldn't place that call.",diff --git a/desktop/app/src/clipboard.rs b/desktop/app/src/clipboard.rsindex 0b869f4..31302a4 100644--- a/desktop/app/src/clipboard.rs+++ b/desktop/app/src/clipboard.rs@@ -308,7 +308,7 @@ pub fn send_now(device: DeviceId) {Err(Error::TooLarge) if image => show_message("That image is too large to send."),Err(Error::TooLarge) => show_message("That's too much text to send at once."),Err(Error::Unsupported) if image => {- show_message(format!("Update Nectarlink on {name} to send it images."))+ show_message(format!("Update NectarLink on {name} to send it images."))}Err(Error::Denied) => show_message(format!("The clipboard is turned off for {name}.")),Err(e) => show_message(describe(&e)),diff --git a/desktop/app/src/command_palette.rs b/desktop/app/src/command_palette.rsindex 61eb905..1f851f4 100644--- a/desktop/app/src/command_palette.rs+++ b/desktop/app/src/command_palette.rs@@ -396,7 +396,7 @@ fn open_voice_recordings(device: DeviceId) {let phone_name =core_host::host().hub.read(|s| s.name_of(&device)).unwrap_or_else(|| "your phone".into());show_message(format!(- "Opened Recordings folder. Start a voice note in Nectarlink on {phone_name} to send it here."+ "Opened Recordings folder. Start a voice note in NectarLink on {phone_name} to send it here."));}@@ -664,7 +664,7 @@ fn build_candidates() -> Vec<PaletteCandidate> {out.push(PaletteCandidate {id: format!("action:webcam:{dev_id}"),title: if webcam_streaming { "Stop phone webcam".into() } else { "Use phone as webcam".into() },- subtitle: format!("Stream {dev_name}'s camera into the Nectarlink virtual webcam"),+ subtitle: format!("Stream {dev_name}'s camera into the NectarLink virtual webcam"),category: "Actions".into(),icon: "video".into(),badge: dev_name.clone(),diff --git a/desktop/app/src/continuity_camera.rs b/desktop/app/src/continuity_camera.rsindex 3ab2c0d..5e24814 100644--- a/desktop/app/src/continuity_camera.rs+++ b/desktop/app/src/continuity_camera.rs@@ -1,7 +1,7 @@// SPDX-License-Identifier: GPL-3.0-or-later//! Continuity Camera coordinator for Windows: initiates "Take photo with phone"//! and "Scan document with phone" from the tray menu, global hotkeys, or the-//! Nectarlink UI, remembers the external foreground window (`HWND`) that was+//! NectarLink UI, remembers the external foreground window (`HWND`) that was//! active when the request started, places the captured image onto the Windows//! clipboard on arrival, and either restores focus + synthesizes `Ctrl+V` into//! the original target window or prompts the user if that window was closed.@@ -65,7 +65,7 @@ enum DeliveryDecision {AutoPaste { hwnd: isize, toast: String },/// A target window was remembered when the request started, but is no longer/// alive/visible when the capture arrived. Do not blindly paste elsewhere;- /// ask the user in Nectarlink.+ /// ask the user in NectarLink.PromptMissingTarget { title: String, body: String, target_name: String },/// No external target window was remembered when the request started.ClipboardOnly { toast: String },@@ -96,7 +96,7 @@ fn decide_delivery_action(return DeliveryDecision::PromptMissingTarget {title: format!("{item_cap} ready on clipboard"),body: format!(- "“{target_name}” is no longer open, so Nectarlink didn’t paste automatically. Switch to the window where you want your {item_lower} from {device_name} and click Paste into active window, or press Ctrl+V anywhere."+ "“{target_name}” is no longer open, so NectarLink didn’t paste automatically. Switch to the window where you want your {item_lower} from {device_name} and click Paste into active window, or press Ctrl+V anywhere."),target_name,};diff --git a/desktop/app/src/deck.rs b/desktop/app/src/deck.rsindex e9a7f1d..e45ac47 100644--- a/desktop/app/src/deck.rs+++ b/desktop/app/src/deck.rs@@ -48,7 +48,7 @@ fn sample_live_state() -> DeckState {if crate::pc_audio_stream::is_enabled() {output_devices.push(nectarlink_core::AudioOutputDevice {id: "nectarlink:phone_speaker".to_owned(),- name: "Phone speaker (Nectarlink)".to_owned(),+ name: "Phone speaker (NectarLink)".to_owned(),is_default: false,});}diff --git a/desktop/app/src/doctor.rs b/desktop/app/src/doctor.rsindex 1c30d30..8b422b9 100644--- a/desktop/app/src/doctor.rs+++ b/desktop/app/src/doctor.rs@@ -110,43 +110,43 @@ fn match_oem(raw: &str) -> Option<(&'static str, &'static str)> {if lower.contains("samsung") || lower.contains("galaxy") || lower.contains("sm-") {Some(("Samsung",- "On Samsung: open Settings → Apps → Nectarlink → Battery and choose Unrestricted, then in \- Device care → Battery → Background usage limits make sure Nectarlink is never put to sleep.",+ "On Samsung: open Settings → Apps → NectarLink → Battery and choose Unrestricted, then in \+ Device care → Battery → Background usage limits make sure NectarLink is never put to sleep.",))} else if lower.contains("xiaomi") || lower.contains("redmi") || lower.contains("poco") {Some(("Xiaomi",- "On Xiaomi / HyperOS / MIUI: open Settings → Apps → Manage apps → Nectarlink, turn on \+ "On Xiaomi / HyperOS / MIUI: open Settings → Apps → Manage apps → NectarLink, turn on \Autostart, and set Battery saver to No restrictions.",))} else if lower.contains("oneplus") {Some(("OnePlus",- "On OnePlus / OxygenOS: open Settings → Apps → App management → Nectarlink → Battery usage and \+ "On OnePlus / OxygenOS: open Settings → Apps → App management → NectarLink → Battery usage and \turn on Allow background activity and Allow auto-launch.",))} else if lower.contains("oppo") || lower.contains("realme") || lower.contains("rmx") {Some(("Oppo / Realme",- "On Oppo / Realme: open Settings → Apps → App management → Nectarlink → Battery usage and turn \+ "On Oppo / Realme: open Settings → Apps → App management → NectarLink → Battery usage and turn \on Allow background activity and Allow auto-launch.",))} else if lower.contains("vivo") || lower.contains("iqoo") {Some(("Vivo","On Vivo / OriginOS / Funtouch: open Settings → Battery → Background power consumption \- management → Nectarlink and choose Unrestricted, and allow Autostart.",+ management → NectarLink and choose Unrestricted, and allow Autostart.",))} else if lower.contains("huawei") || lower.contains("honor") {Some(("Huawei","On Huawei / Honor: open Settings → Battery → App launch, turn off Manage automatically for \- Nectarlink, and keep Auto-launch, Secondary launch, and Run in background on.",+ NectarLink, and keep Auto-launch, Secondary launch, and Run in background on.",))} else if lower.contains("pixel") || lower.contains("google") {Some(("Pixel",- "On Pixel: open Settings → Apps → See all apps → Nectarlink → App battery usage, tap Allow \+ "On Pixel: open Settings → Apps → See all apps → NectarLink → App battery usage, tap Allow \background usage, and choose Unrestricted.",))} else {@@ -199,14 +199,14 @@ pub fn diagnose(facts: &Facts, now_secs: i64) -> Vec<Check> {Some(f) if f.blocked => checks.push(check("firewall",Outcome::Fail,- "Windows Firewall blocks Nectarlink",+ "Windows Firewall blocks NectarLink","Someone chose not to allow it when Windows asked. Allow it, and your phone can connect.",Some("firewall"),)),Some(f) if !f.allowed => checks.push(check("firewall",Outcome::Warn,- "Nectarlink isn't allowed through Windows Firewall",+ "NectarLink isn't allowed through Windows Firewall","Your phone may not be able to connect. Allow it once here.",Some("firewall"),)),@@ -278,7 +278,7 @@ pub fn diagnose(facts: &Facts, now_secs: i64) -> Vec<Check> {Outcome::Warn,format!("{name} isn't connected"),format!(- "{seen} Open Nectarlink on the phone and keep both on the same network. If the phone \+ "{seen} Open NectarLink on the phone and keep both on the same network. If the phone \asks to run in the background, allow it."),Some("reconnect"),diff --git a/desktop/app/src/folder_sync.rs b/desktop/app/src/folder_sync.rsindex 0ad1c8b..d328b08 100644--- a/desktop/app/src/folder_sync.rs+++ b/desktop/app/src/folder_sync.rs@@ -1,6 +1,6 @@// SPDX-License-Identifier: GPL-3.0-or-later//! Folder Sync (§3.6 P2): one-way (Phone → PC) and two-way folder-//! synchronization over the Nectarlink storage service (`storage.list`,+//! synchronization over the NectarLink storage service (`storage.list`,//! `storage.read`, `storage.write`), with conflict-safe renaming so neither//! side's edits are ever lost.diff --git a/desktop/app/src/launch.rs b/desktop/app/src/launch.rsindex 6861eb5..29a5234 100644--- a/desktop/app/src/launch.rs+++ b/desktop/app/src/launch.rs@@ -1,5 +1,5 @@// SPDX-License-Identifier: GPL-3.0-or-later-//! What another launch of Nectarlink asks the running one to do: show its+//! What another launch of NectarLink asks the running one to do: show its//! window (Start menu, shortcuts), send files (Explorer's "Send to") or//! quit (the installer, before replacing or removing the app).//!diff --git a/desktop/app/src/links.rs b/desktop/app/src/links.rsindex 4ddbce9..a1d03b0 100644--- a/desktop/app/src/links.rs+++ b/desktop/app/src/links.rs@@ -103,7 +103,7 @@ fn notice(title: &str, body: &str) {key: "notice".into(),title: title.into(),body: body.into(),- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: None,image: None,actions: Vec::new(),@@ -187,7 +187,7 @@ fn send(phone: DeviceId, name: String, handoff: HandoffLink) {notice(&format!("Sent to {name}"), &body);}}- Err(Error::Unsupported) => notice("Couldn't send it", &format!("Update Nectarlink on {name}.")),+ Err(Error::Unsupported) => notice("Couldn't send it", &format!("Update NectarLink on {name}.")),Err(e) => notice("Couldn't send it", &describe(&e)),}});diff --git a/desktop/app/src/local_api.rs b/desktop/app/src/local_api.rsindex 795a538..de2c245 100644--- a/desktop/app/src/local_api.rs+++ b/desktop/app/src/local_api.rs@@ -1,6 +1,6 @@// SPDX-License-Identifier: GPL-3.0-or-later//! Local authenticated HTTP/JSON automation API (`127.0.0.1:<port>`, default-//! `53320`, off by default): lets local tools (such as the Nectarlink PowerToys+//! `53320`, off by default): lets local tools (such as the NectarLink PowerToys//! Command Palette / Run extension, Raycast scripts, AutoHotkey, or CLI scripts)//! list paired phones, send files/links/clipboard text, trigger Continuity//! Camera, ring a phone, or read recent timeline and clipboard items.diff --git a/desktop/app/src/main.rs b/desktop/app/src/main.rsindex 45a351f..f67f5ec 100644--- a/desktop/app/src/main.rs+++ b/desktop/app/src/main.rs@@ -1,5 +1,5 @@// SPDX-License-Identifier: GPL-3.0-or-later-//! Nectarlink for Windows.+//! NectarLink for Windows.//!//! One process: Rust runs the core (`nectarlink-core`) and OS integration,//! Qt Quick draws the UI. Windows are created when opened and destroyed when@@ -355,7 +355,7 @@ fn watch_network() {});}-/// Phone notifications as Windows toasts, sent by "Nectarlink" with the+/// Phone notifications as Windows toasts, sent by "NectarLink" with the/// app's icon (written as a PNG, which Windows needs as a file).fn start_toasts() {let icon = core_host::host().data_dir.join("cache").join("nectarlink.png");@@ -401,7 +401,7 @@ fn run_setup_window(mode: setup::Mode) -> ExitCode {bridge::native::ffi::prepare_qt_without_log();let mut app = QGuiApplication::new();if let Some(mut app) = app.as_mut() {- app.as_mut().set_application_name(&QString::from("Nectarlink Setup"));+ app.as_mut().set_application_name(&QString::from("NectarLink Setup"));app.as_mut().set_application_version(&QString::from(env!("CARGO_PKG_VERSION")));}bridge::native::ffi::load_bundled_fonts();diff --git a/desktop/app/src/mark.rs b/desktop/app/src/mark.rsindex f3b945b..d168b50 100644--- a/desktop/app/src/mark.rs+++ b/desktop/app/src/mark.rs@@ -1,5 +1,5 @@// SPDX-License-Identifier: GPL-3.0-or-later-//! The Nectarlink mark, the Waggle Dance (`assets/brand/icon.svg`): two loops,+//! The NectarLink mark, the Waggle Dance (`assets/brand/icon.svg`): two loops,//! the phone and the PC, around a drop of nectar, tilted like a bee's waggle//! run, on an espresso tile with a warm glow. Drawn in code at any pixel//! size: the tray, window and toast icons at runtime, and the executable'sdiff --git a/desktop/app/src/messages.rs b/desktop/app/src/messages.rsindex 5bf94b1..e526422 100644--- a/desktop/app/src/messages.rs+++ b/desktop/app/src/messages.rs@@ -1067,7 +1067,7 @@ pub fn send_problem(error: &Error) -> &'static str {match error {Error::Denied => "Messages are turned off for this phone.",Error::Unsupported => {- "The phone doesn't send texts for this PC. Allow it in the Nectarlink app on the phone."+ "The phone doesn't send texts for this PC. Allow it in the NectarLink app on the phone."}Error::Offline | Error::NotPaired | Error::Timeout => "The phone isn't connected.",Error::TooLarge => "That attachment or message is too large (MMS supports up to 900 KB).",diff --git a/desktop/app/src/mirror.rs b/desktop/app/src/mirror.rsindex 3b02192..35ab8eb 100644--- a/desktop/app/src/mirror.rs+++ b/desktop/app/src/mirror.rs@@ -461,7 +461,7 @@ pub fn screenshot_file(window: Window) {key: path.to_string_lossy().into_owned(),title: file_name.clone(),body: format!("Screenshot from {device_name}, saved in Downloads\\Nectarlink"),- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: None,image: Some(path),actions: vec![(ACTION_OPEN.into(), "Open".into()), (ACTION_SHOW.into(), "Show in folder".into())],@@ -603,7 +603,7 @@ pub fn stop_recording(window: Window) {key: path.to_string_lossy().into_owned(),title: file_name.clone(),body: format!("Recording from {device_name}, saved in Downloads\\Nectarlink"),- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: None,image: None,actions: vec![@@ -896,10 +896,10 @@ fn request(window: Window, options: MirrorStart) {let reason = match e {Error::Denied => "Mirroring is turned off for this phone.".to_owned(),Error::Unsupported if app => {- "Set up Wireless debugging in Nectarlink on the phone to open its apps here.".into()+ "Set up Wireless debugging in NectarLink on the phone to open its apps here.".into()}Error::Unsupported => {- "This phone's app doesn't share its screen yet. Update Nectarlink on the phone.".into()+ "This phone's app doesn't share its screen yet. Update NectarLink on the phone.".into()}Error::Offline | Error::NotPaired => "The phone isn't connected.".into(),e => describe(&e),@@ -918,7 +918,7 @@ fn request(window: Window, options: MirrorStart) {set_phase(window,Phase::Ended(Some(- "The app didn't open on the phone. Try again, or open Nectarlink on the phone to check Wireless debugging."+ "The app didn't open on the phone. Try again, or open NectarLink on the phone to check Wireless debugging.".into(),)),);@@ -1048,7 +1048,7 @@ pub fn load_apps(device: DeviceId) {Apps::Ready(apps)}Err(Error::Unsupported) => Apps::Failed(- "Set up Wireless debugging in Nectarlink on the phone to open its apps here.".into(),+ "Set up Wireless debugging in NectarLink on the phone to open its apps here.".into(),),Err(e) => Apps::Failed(describe(&e)),};@@ -1217,7 +1217,7 @@ pub fn drop_files(raw_urls: &[String]) {/// Requests remote input control from the phone for `key` and shows a guidance banner.pub fn request_control(key: &str) {let Some(window) = Window::parse(key) else { return };- set_notice(window, "On your phone, tap Allow / turn on Control from your PC in Nectarlink");+ set_notice(window, "On your phone, tap Allow / turn on Control from your PC in NectarLink");input(window,nectarlink_core::MirrorInput::Touch { action: nectarlink_core::TouchAction::Up, x: 0.5, y: 0.5 },diff --git a/desktop/app/src/pc_audio_stream.rs b/desktop/app/src/pc_audio_stream.rsindex c5147c7..96f685f 100644--- a/desktop/app/src/pc_audio_stream.rs+++ b/desktop/app/src/pc_audio_stream.rs@@ -2,7 +2,7 @@//! Phone as Speaker / Headphones for PC Audio (§3.8 P2): captures Windows//! system audio via WASAPI loopback (`AUDCLNT_STREAMFLAGS_LOOPBACK`), converts//! 32-bit float stereo samples to 16-bit signed little-endian PCM, and streams-//! them to connected phones over Nectarlink's low-latency audio stream.+//! them to connected phones over NectarLink's low-latency audio stream.#![allow(unsafe_code)]diff --git a/desktop/app/src/pc_storage.rs b/desktop/app/src/pc_storage.rsindex b7b7279..29fa78c 100644--- a/desktop/app/src/pc_storage.rs+++ b/desktop/app/src/pc_storage.rs@@ -1,7 +1,7 @@// SPDX-License-Identifier: GPL-3.0-or-later//! Your PC in Your Pocket (§3.11 P2): exposes the PC's `Downloads`,//! `Documents`, `Desktop`, and `Pictures` folders to paired phones over the-//! Nectarlink storage service when `share_pc_storage` is enabled in Settings.+//! NectarLink storage service when `share_pc_storage` is enabled in Settings.use std::{path::{Path, PathBuf},diff --git a/desktop/app/src/photos.rs b/desktop/app/src/photos.rsindex 00f411b..55f4b1d 100644--- a/desktop/app/src/photos.rs+++ b/desktop/app/src/photos.rs@@ -154,7 +154,7 @@ fn show(device: DeviceId, photo: &Photo) {key: format!("{device} {}", photo.id),title: if photo.screenshot { "New screenshot".into() } else { "New photo".into() },body: format!("From {name}"),- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: None,image: preview,actions: vec![(ACTION_SAVE.into(), "Save".into()), (ACTION_COPY.into(), "Copy".into())],diff --git a/desktop/app/src/recordings.rs b/desktop/app/src/recordings.rsindex 336511c..a7cf603 100644--- a/desktop/app/src/recordings.rs+++ b/desktop/app/src/recordings.rs@@ -522,7 +522,7 @@ pub fn on_done(transfer: Transfer) {key: final_path.to_string_lossy().into_owned(),title: format!("Recording from {device} saved"),body,- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: None,image: None,actions: vec![(ACTION_OPEN.into(), "Open".into()), (ACTION_SHOW.into(), "Show in folder".into())],diff --git a/desktop/app/src/send_to.rs b/desktop/app/src/send_to.rsindex abcf032..f1bc4d4 100644--- a/desktop/app/src/send_to.rs+++ b/desktop/app/src/send_to.rs@@ -1,6 +1,6 @@// SPDX-License-Identifier: GPL-3.0-or-later//! Explorer's "Send to" menu: a shortcut per paired phone, which starts-//! Nectarlink with `--send-to <device> <files…>`. The running app sends the+//! NectarLink with `--send-to <device> <files…>`. The running app sends the//! files and follows the transfer in a Windows notification with a progress//! bar, so nothing else needs to open.@@ -148,8 +148,8 @@ fn reconcile(dir: &Path, desired: &[(DeviceId, String)], exe: &Path) -> io::Resu.any(|(p, _)| p.file_name().is_some_and(|n| n.to_string_lossy().to_lowercase() == lower))};let candidate = std::iter::once(base.clone())- .chain(std::iter::once(format!("{base} (Nectarlink)")))- .chain((2..).map(|n| format!("{base} (Nectarlink {n})")))+ .chain(std::iter::once(format!("{base} (NectarLink)")))+ .chain((2..).map(|n| format!("{base} (NectarLink {n})"))).find(|c| !taken(c)).unwrap_or(base);planned.push((@@ -157,7 +157,7 @@ fn reconcile(dir: &Path, desired: &[(DeviceId, String)], exe: &Path) -> io::ResuShortcut {target: exe.to_owned(),arguments: format!("{ARG} {id}"),- description: format!("Send to {name} with Nectarlink"),+ description: format!("Send to {name} with NectarLink"),},));}@@ -238,7 +238,7 @@ fn share(files: Vec<PathBuf>, url: Option<String>, text: Option<String>) {request_activation();}let Some((device_id, device_name)) = target else {- failed("No phone paired", "Pair your phone in Nectarlink to share with it.");+ failed("No phone paired", "Pair your phone in NectarLink to share with it.");return;};if !files.is_empty() {@@ -260,7 +260,7 @@ fn share(files: Vec<PathBuf>, url: Option<String>, text: Option<String>) {key: "share-text".into(),title: format!("Sent to {device_name}"),body: "Copied to your phone's clipboard.".into(),- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: None,image: None,actions: Vec::new(),@@ -357,7 +357,7 @@ fn send(device: String, paths: Vec<PathBuf>) {}Err(Error::Denied) => failed(&format!("Couldn't send to {name}"),- "Files are turned off for this device. Turn them on in Nectarlink.",+ "Files are turned off for this device. Turn them on in NectarLink.",),Err(e) => failed(&format!("Couldn't send to {name}"), &describe(&e)),}@@ -370,7 +370,7 @@ fn failed(title: &str, body: &str) {key: format!("failed-{title}"),title: title.into(),body: body.into(),- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: None,image: None,actions: Vec::new(),@@ -399,7 +399,7 @@ fn track(id: String, device_name: String) {key: id,title,body: format!("{device_name} is offline. Will send when it's back."),- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: None,image: None,actions: vec![(ACTION_CANCEL.into(), "Cancel".into())],@@ -429,7 +429,7 @@ fn update(map: &mut HashMap<String, Tracked>, transfer: &Transfer) {key: transfer.id.clone(),title,body,- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: None,image: None,actions: Vec::new(),@@ -556,11 +556,11 @@ mod tests {reconcile(dir.path(), &[(a, "Pixel".into()), (b, "Tab".into()), (c, "Pixel".into())], &exe).unwrap();assert_eq!(names(dir.path()),- ["Pixel (Nectarlink).lnk", "Pixel.lnk", "Tab (Nectarlink).lnk", "Tab.lnk"]+ ["Pixel (NectarLink).lnk", "Pixel.lnk", "Tab (NectarLink).lnk", "Tab.lnk"]);assert_eq!(shortcut::arguments(&dir.path().join("Pixel.lnk")).unwrap(), format!("{ARG} {a}"));assert_eq!(- shortcut::arguments(&dir.path().join("Pixel (Nectarlink).lnk")).unwrap(),+ shortcut::arguments(&dir.path().join("Pixel (NectarLink).lnk")).unwrap(),format!("{ARG} {c}"));diff --git a/desktop/app/src/settings.rs b/desktop/app/src/settings.rsindex a7051a0..1778505 100644--- a/desktop/app/src/settings.rs+++ b/desktop/app/src/settings.rs@@ -272,7 +272,7 @@ pub struct Settings {/// reduced motion or battery saver whatever this says).#[serde(default = "default_true", alias = "comb_motion")]pub comb_motion: bool,- /// Closing the window keeps Nectarlink running in the tray.+ /// Closing the window keeps NectarLink running in the tray.#[serde(alias = "close_to_tray")]pub close_to_tray: bool,/// Send what's copied on this PC to connected phones.diff --git a/desktop/app/src/setup.rs b/desktop/app/src/setup.rsindex c4074f8..e9f8771 100644--- a/desktop/app/src/setup.rs+++ b/desktop/app/src/setup.rs@@ -12,7 +12,7 @@//! A program can't delete its own folder, so it first copies itself to a//! temporary folder (as `Nectarlink Uninstall.exe`) and carries on from//! there, then runs `uninstall.exe /S /PROGRESS=<file>` with administrator-//! rights, and finally removes this user's Nectarlink data. Files received+//! rights, and finally removes this user's NectarLink data. Files received//! from phones (`Downloads\Nectarlink`), voice recordings and synced folders//! belong to the user and are kept.//!@@ -106,7 +106,7 @@ impl Step {/// What the window says while this step runs.pub fn label(self) -> &'static str {match self {- Step::Closing => "Closing Nectarlink",+ Step::Closing => "Closing NectarLink",Step::Files => "Copying files",Step::Firewall => "Allowing through Windows Firewall",Step::Updates => "Setting up updates",@@ -170,7 +170,7 @@ pub fn remove(installed: &Path, mut on_event: impl FnMut(Event)) -> Outcome {let uninstaller = installed.join("uninstall.exe");if !uninstaller.is_file() {return Outcome::Failed(- "The uninstaller is missing. Reinstall Nectarlink, then uninstall it.".into(),+ "The uninstaller is missing. Reinstall NectarLink, then uninstall it.".into(),);}let progress = progress_file("remove");@@ -192,7 +192,7 @@ pub fn remove_user_data() {if let Err(e) = std::fs::remove_dir_all(&data)&& e.kind() != std::io::ErrorKind::NotFound{- tracing::warn!(error = %e, "can't remove all of Nectarlink's data");+ tracing::warn!(error = %e, "can't remove all of NectarLink's data");}}diff --git a/desktop/app/src/storage.rs b/desktop/app/src/storage.rsindex 22ae3a7..229fb53 100644--- a/desktop/app/src/storage.rs+++ b/desktop/app/src/storage.rs@@ -74,7 +74,7 @@ use crate::{win,};-/// Provider prefix for sync root IDs (`Nectarlink!<device_id>`).+/// Provider prefix for sync root IDs (`NectarLink!<device_id>`).const PROVIDER_PREFIX: &str = "Nectarlink!";/// Difference between Windows FILETIME epoch (1601-01-01) and Unix epoch@@ -210,7 +210,7 @@ pub fn shutdown() {}}-/// Unregisters all `Nectarlink!*` sync roots from Windows (`--uninstall`).+/// Unregisters all `NectarLink!*` sync roots from Windows (`--uninstall`).pub fn unregister_all() {shutdown();win::with_com(|| {diff --git a/desktop/app/src/transfers.rs b/desktop/app/src/transfers.rsindex 7e15d0f..72f5676 100644--- a/desktop/app/src/transfers.rs+++ b/desktop/app/src/transfers.rs@@ -252,7 +252,7 @@ pub fn on_event(event: &NodeEvent) {device: TOAST_GROUP.into(),key: format!("req:{}", t.id),title: format!("{device} wants to send {}", title(t)),- body: "Accept in Nectarlink to save to Downloads\\Nectarlink".into(),+ body: "Accept in NectarLink to save to Downloads\\Nectarlink".into(),attribution: "LocalSend".into(),icon: None,image: None,@@ -298,7 +298,7 @@ pub fn on_event(event: &NodeEvent) {} else {format!("From {device}, saved in Downloads\\Nectarlink")},- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: None,image: None,actions: vec![(ACTION_OPEN.into(), "Open".into()), (ACTION_SHOW.into(), "Show in folder".into())],diff --git a/desktop/app/src/updater.rs b/desktop/app/src/updater.rsindex 4112b29..fd276fd 100644--- a/desktop/app/src/updater.rs+++ b/desktop/app/src/updater.rs@@ -155,9 +155,9 @@ pub fn check_now(told: bool) -> Option<String> {if new {announce(&update);}- Some(format!("Nectarlink {} is available.", update.version))+ Some(format!("NectarLink {} is available.", update.version))}- Ok(None) => told.then(|| "Nectarlink is up to date.".to_owned()),+ Ok(None) => told.then(|| "NectarLink is up to date.".to_owned()),Err(e) => {tracing::info!(error = %e, "couldn't check for updates");told.then(|| "Couldn't check for updates. Check your internet connection.".to_owned())@@ -169,9 +169,9 @@ fn announce(update: &Update) {toast::show(toast::Toast {device: TOAST_GROUP.into(),key: update.version.clone(),- title: format!("Nectarlink {} is available", update.version),+ title: format!("NectarLink {} is available", update.version),body: "Update now, or later from Settings.".into(),- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: None,image: None,actions: vec![(ACTION_UPDATE.into(), "Update".into())],@@ -684,7 +684,7 @@ pub fn announce_update(previous: String, shown: bool) {tracing::info!(from = previous, to = current, "updated");after_start(shown,- format!("Nectarlink is updated to {current}"),+ format!("NectarLink is updated to {current}"),"Your phone reconnects on its own.".into(),);}@@ -696,7 +696,7 @@ pub fn announce_update_failed(shown: bool) {after_start(shown,"The update didn't install".into(),- "Nectarlink is still on the version you had. Try again from Settings.".into(),+ "NectarLink is still on the version you had. Try again from Settings.".into(),);}@@ -712,7 +712,7 @@ fn after_start(shown: bool, title: String, body: String) {key: "updated".into(),title,body,- attribution: "Nectarlink".into(),+ attribution: "NectarLink".into(),icon: None,image: None,actions: Vec::new(),diff --git a/desktop/app/src/webcam.rs b/desktop/app/src/webcam.rsindex ff2df7a..a257e54 100644--- a/desktop/app/src/webcam.rs+++ b/desktop/app/src/webcam.rs@@ -468,7 +468,7 @@ pub fn start(device: Option<DeviceId>) {let reason = match e {Error::Denied => "Webcam is turned off for this phone.".to_owned(),Error::Unsupported => {- "This phone's app doesn't support Webcam yet. Update Nectarlink on the phone.".into()+ "This phone's app doesn't support Webcam yet. Update NectarLink on the phone.".into()}Error::Offline | Error::NotPaired => "The phone isn't connected.".into(),e => describe(&e),diff --git a/desktop/app/src/win/autostart.rs b/desktop/app/src/win/autostart.rsindex 288a3ad..9d26a5c 100644--- a/desktop/app/src/win/autostart.rs+++ b/desktop/app/src/win/autostart.rs@@ -1,5 +1,5 @@// SPDX-License-Identifier: GPL-3.0-or-later-//! Starting Nectarlink when the user signs in, so phones can reach this PC+//! Starting NectarLink when the user signs in, so phones can reach this PC//! without opening it first: a value under the user's `Run` key that starts//! it in the tray.diff --git a/desktop/app/src/win/ble_beacon.rs b/desktop/app/src/win/ble_beacon.rsindex 9e78415..4fafcc1 100644--- a/desktop/app/src/win/ble_beacon.rs+++ b/desktop/app/src/win/ble_beacon.rs@@ -21,7 +21,7 @@ use windows::{Storage::Streams::{DataReader, DataWriter},};-/// Bluetooth SIG test/internal company identifier used for Nectarlink proximity frames.+/// Bluetooth SIG test/internal company identifier used for NectarLink proximity frames.pub const COMPANY_ID: u16 = 0xFFFF;/// 5-byte magic header (`"NCTR"` + protocol version `0x01`).@@ -98,7 +98,7 @@ pub fn build_manufacturer_payload(device_id: &DeviceId) -> [u8; 13] {out}-/// Starts advertising the Nectarlink BLE proximity beacon for `device_id` and+/// Starts advertising the NectarLink BLE proximity beacon for `device_id` and/// watching for paired phone BLE proximity frames for RSSI walk-away ranging.pub fn start(device_id: DeviceId) {if let Err(e) = try_start(&device_id) {diff --git a/desktop/app/src/win/clipboard.rs b/desktop/app/src/win/clipboard.rsindex 2c5274d..f209337 100644--- a/desktop/app/src/win/clipboard.rs+++ b/desktop/app/src/win/clipboard.rs@@ -3,7 +3,7 @@//! and writing what a phone sent (docs/protocol/clipboard.md).//!//! A hidden message-only window on its own thread listens for clipboard-//! changes and owns what Nectarlink writes, so text that came from a phone+//! changes and owns what NectarLink writes, so text that came from a phone//! is never sent back. Content that password managers mark as private is//! never read for sending. Images are read as PNG when the app offers it,//! or else as a bitmap (converted to PNG off the clipboard thread), and@@ -110,7 +110,7 @@ static ON_COPY: OnceLock<OnCopy> = OnceLock::new();/// A fingerprint of the last content reported, so one copy reported several/// times (apps often write the clipboard in steps) is sent once.static LAST_REPORTED: Mutex<Option<u64>> = Mutex::new(None);-/// The last rich-text clip written by Nectarlink, so if a host-clipboard bridge+/// The last rich-text clip written by NectarLink, so if a host-clipboard bridge/// (such as the Android emulator's QEMU clipboard pipe) immediately echoes the/// same plain text without rich formats, we preserve the rich formats.static LAST_WRITTEN_RICH: Mutex<Option<WrittenRich>> = Mutex::new(None);@@ -126,7 +126,7 @@ fn fingerprint(clip: &Clip) -> Option<u64> {}/// Starts watching the clipboard; `on_copy` gets each newly copied text or-/// image that isn't private and didn't come from Nectarlink, on the watcher+/// image that isn't private and didn't come from NectarLink, on the watcher/// thread.pub fn start(on_copy: impl Fn(Clip) + Send + Sync + 'static) {if ON_COPY.set(Box::new(on_copy)).is_err() {@@ -158,7 +158,7 @@ fn run() -> windows::core::Result<()> {CreateWindowExW(WINDOW_EX_STYLE(0),w!("Nectarlink.Clipboard"),- w!("Nectarlink clipboard"),+ w!("NectarLink clipboard"),WINDOW_STYLE(0),0,0,@@ -193,7 +193,7 @@ unsafe extern "system" fn window_proc(hwnd: HWND, msg: u32, wparam: WPARAM, lpar}fn on_clipboard_changed(hwnd: HWND) {- // What Nectarlink wrote (a phone's text) isn't sent back.+ // What NectarLink wrote (a phone's text) isn't sent back.// SAFETY: GetClipboardOwner has no preconditions.if unsafe { GetClipboardOwner() }.is_ok_and(|owner| owner == hwnd) {return;@@ -725,7 +725,7 @@ mod tests {#[test]fn cf_html_and_rtf_round_trip() {- let frag = "<p><b>Hello</b> <i>Nectarlink</i> 🐝</p>";+ let frag = "<p><b>Hello</b> <i>NectarLink</i> 🐝</p>";let encoded = encode_cf_html(frag);assert_eq!(decode_cf_html(&encoded).as_deref(), Some(frag));diff --git a/desktop/app/src/win/doctor.rs b/desktop/app/src/win/doctor.rsindex a3f583d..d67ada7 100644--- a/desktop/app/src/win/doctor.rs+++ b/desktop/app/src/win/doctor.rs@@ -257,7 +257,7 @@ pub fn fix_firewall(exe: &Path) -> windows::core::Result<bool> {}/// Opens Windows Defender Firewall's Control Panel / settings page so the user-/// can inspect or toggle Nectarlink directly.+/// can inspect or toggle NectarLink directly.pub fn open_firewall_settings() -> bool {let mut info = SHELLEXECUTEINFOW {cbSize: std::mem::size_of::<SHELLEXECUTEINFOW>() as u32,diff --git a/desktop/app/src/win/jumplist.rs b/desktop/app/src/win/jumplist.rsindex 9f20bc5..31071a9 100644--- a/desktop/app/src/win/jumplist.rs+++ b/desktop/app/src/win/jumplist.rs@@ -1,6 +1,6 @@// SPDX-License-Identifier: GPL-3.0-or-later//! Windows Taskbar Jump List: quick user tasks when right-clicking the-//! Nectarlink icon on the taskbar or Start menu (`ICustomDestinationList`).+//! NectarLink icon on the taskbar or Start menu (`ICustomDestinationList`).use std::path::Path;@@ -20,7 +20,7 @@ use windows::{use super::with_com;-/// The command-line flag Jump List tasks pass back to Nectarlink.+/// The command-line flag Jump List tasks pass back to NectarLink.pub const ARG: &str = "--task";/// The 5 user tasks shown in the Windows Taskbar Jump List: `(action, title, description)`.diff --git a/desktop/app/src/win/media_sessions.rs b/desktop/app/src/win/media_sessions.rsindex 28ca264..7206ede 100644--- a/desktop/app/src/win/media_sessions.rs+++ b/desktop/app/src/win/media_sessions.rs@@ -3,7 +3,7 @@//! sessions apps report to Windows (Global System Media Transport//! Controls), and commands from a phone sent to them.//!-//! Nectarlink's own session (a phone's media in the flyout) is left out, so+//! NectarLink's own session (a phone's media in the flyout) is left out, so//! a phone never gets its own music back.use std::{@@ -180,7 +180,7 @@ fn watch(Ok(())}-/// Every session but Nectarlink's own, the one Windows considers current+/// Every session but NectarLink's own, the one Windows considers current/// first.fn snapshot(manager: &GlobalSystemMediaTransportControlsSessionManager,@@ -620,7 +620,7 @@ pub fn command(player: &str, action: MediaAction, position: Option<u64>) -> Resu}/// Tracks which PC media sessions were actively playing when a phone call-/// started and were paused by Nectarlink, so only those sessions are resumed+/// started and were paused by NectarLink, so only those sessions are resumed/// when the call ends.#[derive(Debug, Default)]pub(crate) struct PausedForCall {@@ -660,8 +660,8 @@ fn paused_for_call<T>(f: impl FnOnce(&mut PausedForCall) -> T) -> T {}/// Pauses any PC media sessions that are currently playing (excluding-/// Nectarlink's own SMTC session) and remembers them so [`resume_after_call`]-/// can resume only what Nectarlink paused.+/// NectarLink's own SMTC session) and remembers them so [`resume_after_call`]+/// can resume only what NectarLink paused.pub fn pause_for_call() {let Some(manager) = MANAGER.get().cloned() else { return };std::thread::spawn(move || {diff --git a/desktop/app/src/win/mod.rs b/desktop/app/src/win/mod.rsindex ff2678e..0aab4ea 100644--- a/desktop/app/src/win/mod.rs+++ b/desktop/app/src/win/mod.rs@@ -71,7 +71,7 @@ fn reg_dword(root: HKEY, key: &str, value: &str) -> Option<u32> {}/// Windows' per-installation machine GUID. It stays the same across app reinstalls, so a-/// hash of it lets phones recognise this PC after Nectarlink is reinstalled.+/// hash of it lets phones recognise this PC after NectarLink is reinstalled.pub fn machine_guid() -> Option<String> {reg_string(HKEY_LOCAL_MACHINE, r"SOFTWARE\Microsoft\Cryptography", "MachineGuid")}@@ -204,6 +204,6 @@ mod tests {let version = os_version();let parts: Vec<&str> = version.split('.').collect();assert_eq!(parts.len(), 3, "{version}");- assert!(parts[2].parse::<u32>().unwrap() >= 22000, "Nectarlink targets Windows 11: {version}");+ assert!(parts[2].parse::<u32>().unwrap() >= 22000, "NectarLink targets Windows 11: {version}");}}diff --git a/desktop/app/src/win/single_instance.rs b/desktop/app/src/win/single_instance.rsindex 982a4e2..884c98d 100644--- a/desktop/app/src/win/single_instance.rs+++ b/desktop/app/src/win/single_instance.rs@@ -1,5 +1,5 @@// SPDX-License-Identifier: GPL-3.0-or-later-//! One Nectarlink per user session and data folder. A second launch (from+//! One NectarLink per user session and data folder. A second launch (from//! the Start menu, a shortcut or Explorer's "Send to") leaves its request//! (`crate::launch`), wakes the running one with [`wake`] and exits.diff --git a/desktop/app/src/win/smtc.rs b/desktop/app/src/win/smtc.rsindex 125ca57..9c5deb7 100644--- a/desktop/app/src/win/smtc.rs+++ b/desktop/app/src/win/smtc.rs@@ -125,7 +125,7 @@ fn run(updates: mpsc::Receiver<Option<Shown>>) -> windows::core::Result<()> {CreateWindowExW(WINDOW_EX_STYLE(0),w!("Nectarlink.Media"),- w!("Nectarlink media"),+ w!("NectarLink media"),WS_OVERLAPPED,0,0,diff --git a/desktop/app/src/win/toast.rs b/desktop/app/src/win/toast.rsindex 96a9fa8..66fb4a8 100644--- a/desktop/app/src/win/toast.rs+++ b/desktop/app/src/win/toast.rs@@ -2,7 +2,7 @@//! Phone notifications as Windows toasts, with the app's icon, its actions//! and an inline reply field.//!-//! Nectarlink isn't a packaged app, so it registers an AppUserModelID under+//! NectarLink isn't a packaged app, so it registers an AppUserModelID under//! HKCU (display name and icon) and gives the process that ID. Toasts are//! driven from one thread with COM initialized; clicks, replies and//! dismissals come back through per-toast handlers while the app runs.@@ -217,7 +217,7 @@ fn register(icon: &Path) -> windows::core::Result<()> {}.ok()};- let result = set("DisplayName", "Nectarlink").and_then(|()| set("IconUri", &icon.to_string_lossy()));+ let result = set("DisplayName", "NectarLink").and_then(|()| set("IconUri", &icon.to_string_lossy()));// SAFETY: the key was opened above.unsafe {let _ = RegCloseKey(key);diff --git a/desktop/app/src/win/tray.rs b/desktop/app/src/win/tray.rsindex 63f2fa4..0faec73 100644--- a/desktop/app/src/win/tray.rs+++ b/desktop/app/src/win/tray.rs@@ -202,7 +202,7 @@ unsafe fn find_top_external_window(self_pid: u32) -> Option<(isize, String, bool}/// Records the current foreground window if it belongs to an external-/// user-facing application (not Nectarlink itself and not the Windows shell tray).+/// user-facing application (not NectarLink itself and not the Windows shell tray).pub fn record_foreground_window() {// SAFETY: Standard Win32 queries on the foreground and Z-order HWNDs.unsafe {diff --git a/desktop/app/src/win/vcam.rs b/desktop/app/src/win/vcam.rsindex 830b64c..42a39c0 100644--- a/desktop/app/src/win/vcam.rs+++ b/desktop/app/src/win/vcam.rs@@ -1,6 +1,6 @@// SPDX-License-Identifier: GPL-3.0-or-later//! Windows 11 Virtual Camera (`MFCreateVirtualCamera`) registration and-//! session management for `"Nectarlink Webcam"`.+//! session management for `"NectarLink Webcam"`.use std::path::{Path, PathBuf};@@ -31,7 +31,7 @@ use windows::{};pub const CLSID_STR: &str = "{8E6C3B74-5D4A-4B9E-9A12-7C8F1E2D3A40}";-pub const FRIENDLY_NAME: &str = "Nectarlink Webcam";+pub const FRIENDLY_NAME: &str = "NectarLink Webcam";pub const REGISTER_ARG: &str = "--register-vcam";pub const UNREGISTER_ARG: &str = "--unregister-vcam";@@ -137,7 +137,7 @@ pub fn register_under(let inproc_key = format!(r"{clsid_key}\InprocServer32");let fs_key = format!(r"{frameserver_prefix}\{CLSID_STR}");- create_and_set(root, &clsid_key, &[(None, "Nectarlink Virtual Camera Media Source")])?;+ create_and_set(root, &clsid_key, &[(None, "NectarLink Virtual Camera Media Source")])?;create_and_set(root, &inproc_key, &[(None, dll_str.as_ref()), (Some("ThreadingModel"), "Both")])?;create_and_set(root, &fs_key, &[(Some("FriendlyName"), FRIENDLY_NAME)])?;Ok(())@@ -215,7 +215,7 @@ impl std::fmt::Debug for VirtualCameraHandle {}impl VirtualCameraHandle {- /// Creates and starts the `"Nectarlink Webcam"` session-lifetime virtual camera.+ /// Creates and starts the `"NectarLink Webcam"` session-lifetime virtual camera./// Succeeds when `nectarlink_vcam.dll` is registered in `HKLM`.pub fn start() -> Result<Self, String> {unsafe {diff --git a/desktop/app/src/win/widget.rs b/desktop/app/src/win/widget.rsindex 68e38d1..57cc7d6 100644--- a/desktop/app/src/win/widget.rs+++ b/desktop/app/src/win/widget.rs@@ -3,7 +3,7 @@//! Adaptive Card v1.5 snapshot of the primary paired phone (connection status,//! battery level, latest clipboard preview, and quick actions) and dispatches//! `Action.Execute` verbs (`ring`, `send_clipboard`, `take_photo`, `open_app`)-//! to the running Nectarlink instance.+//! to the running NectarLink instance.#![allow(unsafe_code, dead_code)]@@ -37,7 +37,7 @@ pub const ARG: &str = "--widget-provider";/// Widget definition ID declared in `desktop/installer/AppxManifest.xml`.pub const WIDGET_ID: &str = "NectarlinkPhoneStatus";-/// COM `CLSID` for the Nectarlink Windows Widgets provider+/// COM `CLSID` for the NectarLink Windows Widgets provider/// (`{9C4E1A22-8F3B-4D09-A6E2-1D8F5C3B9E04}`).pub const CLSID: GUID = GUID::from_u128(0x9C4E1A22_8F3B_4D09_A6E2_1D8F5C3B9E04);@@ -217,7 +217,7 @@ pub fn render_adaptive_card(state: &WidgetState) -> String {},{"type": "Action.Execute",- "title": "Open Nectarlink",+ "title": "Open NectarLink","verb": "open_app"}]@@ -228,7 +228,7 @@ pub fn render_adaptive_card(state: &WidgetState) -> String {/// Maps an Adaptive Card `Action.Execute` verb (`"ring"`, `"send_clipboard"`,/// `"take_photo"`, `"open_app"`) to a [`Request`] and queues it for the primary-/// Nectarlink instance when `data_dir` is provided.+/// NectarLink instance when `data_dir` is provided.pub fn handle_action_verb(verb: &str, data_dir: Option<&Path>) -> Result<(), String> {let request = match verb.trim() {"ring" => Request::Task { action: "find-phone".into() },diff --git a/desktop/installer/nectarlink.nsi b/desktop/installer/nectarlink.nsiindex e7e0fb0..edd47e2 100644--- a/desktop/installer/nectarlink.nsi+++ b/desktop/installer/nectarlink.nsi@@ -1,12 +1,12 @@; SPDX-License-Identifier: GPL-3.0-or-later;-; The Nectarlink installer for Windows (built by scripts/package.ps1).+; The NectarLink installer for Windows (built by scripts/package.ps1).;; Two ways to run it:;; - Opened by the user: no NSIS pages. It unpacks the app to a temporary; folder and runs it there, as "Nectarlink Setup.exe" with --setup, which-; draws Nectarlink's own setup window (desktop/app/src/setup.rs). That+; draws NectarLink's own setup window (desktop/app/src/setup.rs). That; window runs this installer again, elevated, as below.; - With /S (that window, or the app's updater): installs into Program Files; for every user of the PC, without a window. /PROGRESS=<file> writes each@@ -32,13 +32,16 @@ SetCompressor /SOLID zlib!include "LogicLib.nsh"!include "FileFunc.nsh"+; APP names the install folder, registry keys and the firewall rule; DISPLAY is+; the name people see.!define APP "Nectarlink"+!define DISPLAY "NectarLink"!define EXE "nectarlink-desktop.exe"!define SETUP_EXE "Nectarlink Setup.exe"!define UNINSTALL_KEY "Software\Microsoft\Windows\CurrentVersion\Uninstall\${APP}"!define FIREWALL_RULE "Nectarlink"-Name "${APP}"+Name "${DISPLAY}"OutFile "${OUTFILE}"; Elevates itself only when it installs (see .onInit).RequestExecutionLevel user@@ -51,14 +54,14 @@ ShowInstDetails nevershowShowUninstDetails nevershowVIProductVersion "${VERSION}.0"-VIAddVersionKey "ProductName" "${APP}"-VIAddVersionKey "FileDescription" "${APP} Setup"-VIAddVersionKey "CompanyName" "The Nectarlink contributors"+VIAddVersionKey "ProductName" "${DISPLAY}"+VIAddVersionKey "FileDescription" "${DISPLAY} Setup"+VIAddVersionKey "CompanyName" "The NectarLink contributors"VIAddVersionKey "LegalCopyright" "GPL-3.0-or-later"VIAddVersionKey "FileVersion" "${VERSION}"VIAddVersionKey "ProductVersion" "${DISPLAY_VERSION}"-; 1: show Nectarlink's own setup window. 0: install now (/S).+; 1: show NectarLink's own setup window. 0: install now (/S).Var Interactive; Where each step is written, for the setup window (/PROGRESS=<file>).Var ProgressFile@@ -76,12 +79,12 @@ Var AppDir!macro ArchCheck${If} "${ARCH}" == "x64"${IfNot} ${IsNativeAMD64}- MessageBox MB_ICONSTOP "This copy of ${APP} is for x64 PCs. Download the ARM64 version for this PC." /SD IDOK+ MessageBox MB_ICONSTOP "This copy of ${DISPLAY} is for x64 PCs. Download the ARM64 version for this PC." /SD IDOKAbort${EndIf}${ElseIf} "${ARCH}" == "arm64"${IfNot} ${IsNativeARM64}- MessageBox MB_ICONSTOP "This copy of ${APP} is for ARM64 PCs. Download the x64 version for this PC." /SD IDOK+ MessageBox MB_ICONSTOP "This copy of ${DISPLAY} is for ARM64 PCs. Download the x64 version for this PC." /SD IDOKAbort${EndIf}${EndIf}@@ -111,7 +114,7 @@ Function .onInit${EndIf}${Else}StrCpy $Interactive 1- ; No NSIS window: the window is Nectarlink's own.+ ; No NSIS window: the window is NectarLink's own.SetSilent silent${EndIf}FunctionEnd@@ -189,7 +192,7 @@ Section "Install"; Phones reach this PC over UDP (QUIC) and find it with mDNS.!insertmacro Progress "step firewall"nsExec::Exec 'netsh advfirewall firewall delete rule name="${FIREWALL_RULE}"'- nsExec::Exec 'netsh advfirewall firewall add rule name="${FIREWALL_RULE}" dir=in action=allow program="$INSTDIR\${EXE}" enable=yes profile=private,domain description="Lets paired phones connect to Nectarlink."'+ nsExec::Exec 'netsh advfirewall firewall add rule name="${FIREWALL_RULE}" dir=in action=allow program="$INSTDIR\${EXE}" enable=yes profile=private,domain description="Lets paired phones connect to NectarLink."'; Updates without an administrator prompt: a task that runs this app as; SYSTEM to install a newer release, which signed-in users may start but@@ -200,20 +203,20 @@ Section "Install"nsExec::Exec 'powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -File "$PLUGINSDIR\update-task.ps1" -Exe "$INSTDIR\${EXE}"'!insertmacro Progress "step shortcuts"- CreateShortCut "$SMPROGRAMS\${APP}.lnk" "$INSTDIR\${EXE}" "" "$INSTDIR\${EXE}" 0 "" "" "Your phone, on your PC"- CreateShortCut "$DESKTOP\${APP}.lnk" "$INSTDIR\${EXE}" "" "$INSTDIR\${EXE}" 0 "" "" "Your phone, on your PC"+ CreateShortCut "$SMPROGRAMS\${DISPLAY}.lnk" "$INSTDIR\${EXE}" "" "$INSTDIR\${EXE}" 0 "" "" "Your phone, on your PC"+ CreateShortCut "$DESKTOP\${DISPLAY}.lnk" "$INSTDIR\${EXE}" "" "$INSTDIR\${EXE}" 0 "" "" "Your phone, on your PC"; Best-effort Sparse Package registration for the Windows Share sheet target.nsExec::Exec 'powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Command "try { Add-AppxPackage -Register \"$INSTDIR\AppxManifest.xml\" -ExternalLocation \"$INSTDIR\" -ErrorAction SilentlyContinue } catch {}"'WriteRegStr HKLM "Software\${APP}" "InstallDir" "$INSTDIR"- WriteRegStr HKLM "${UNINSTALL_KEY}" "DisplayName" "${APP}"+ WriteRegStr HKLM "${UNINSTALL_KEY}" "DisplayName" "${DISPLAY}"WriteRegStr HKLM "${UNINSTALL_KEY}" "DisplayVersion" "${DISPLAY_VERSION}"- WriteRegStr HKLM "${UNINSTALL_KEY}" "Publisher" "The Nectarlink contributors"+ WriteRegStr HKLM "${UNINSTALL_KEY}" "Publisher" "The NectarLink contributors"WriteRegStr HKLM "${UNINSTALL_KEY}" "DisplayIcon" "$INSTDIR\${EXE}"WriteRegStr HKLM "${UNINSTALL_KEY}" "InstallLocation" "$INSTDIR"WriteRegStr HKLM "${UNINSTALL_KEY}" "URLInfoAbout" "https://github.com/thtbee/nectarlink"- ; Windows Settings > Apps opens Nectarlink's own uninstall window.+ ; Windows Settings > Apps opens NectarLink's own uninstall window.WriteRegStr HKLM "${UNINSTALL_KEY}" "UninstallString" '"$INSTDIR\${EXE}" --remove'WriteRegStr HKLM "${UNINSTALL_KEY}" "QuietUninstallString" '"$INSTDIR\uninstall.exe" /S'WriteRegDWORD HKLM "${UNINSTALL_KEY}" "NoModify" 1@@ -245,8 +248,8 @@ Section "Uninstall"nsExec::Exec 'powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Command "try { Get-AppxPackage -Name \"Nectarlink.Desktop\" -ErrorAction SilentlyContinue | Remove-AppxPackage -ErrorAction SilentlyContinue } catch {}"'nsExec::Exec 'netsh advfirewall firewall delete rule name="${FIREWALL_RULE}"'nsExec::Exec 'schtasks /Delete /TN "Nectarlink Update" /F'- Delete "$SMPROGRAMS\${APP}.lnk"- Delete "$DESKTOP\${APP}.lnk"+ Delete "$SMPROGRAMS\${DISPLAY}.lnk"+ Delete "$DESKTOP\${DISPLAY}.lnk"; Only ever a folder of our own (a silent install can be pointed; anywhere with /D): never everything in, say, C:\.${GetFileName} "$INSTDIR" $0diff --git a/desktop/installer/update-task.ps1 b/desktop/installer/update-task.ps1index c6ed771..d5a75d1 100644--- a/desktop/installer/update-task.ps1+++ b/desktop/installer/update-task.ps1@@ -17,7 +17,7 @@ $principal = New-ScheduledTaskPrincipal -UserId 'S-1-5-18' -LogonType ServiceAcc$settings = New-ScheduledTaskSettingsSet -AllowStartIfOnBatteries -DontStopIfGoingOnBatteries `-MultipleInstances IgnoreNew -ExecutionTimeLimit (New-TimeSpan -Minutes 30)Register-ScheduledTask -TaskName $name -Action $action -Principal $principal -Settings $settings `- -Description 'Installs new versions of Nectarlink from its GitHub releases.' -Force | Out-Null+ -Description 'Installs new versions of NectarLink from its GitHub releases.' -Force | Out-Null# SYSTEM and administrators: full control. Authenticated users: read and run.$service = New-Object -ComObject Schedule.Servicediff --git a/desktop/vcam/Cargo.toml b/desktop/vcam/Cargo.tomlindex d81a89c..508dc1a 100644--- a/desktop/vcam/Cargo.toml+++ b/desktop/vcam/Cargo.toml@@ -1,6 +1,6 @@[package]name = "nectarlink-vcam"-description = "Nectarlink virtual camera Media Foundation media source (Windows 11)"+description = "NectarLink virtual camera Media Foundation media source (Windows 11)"version.workspace = trueedition.workspace = truerust-version.workspace = truediff --git a/desktop/vcam/build.rs b/desktop/vcam/build.rsindex bb01a62..da916dc 100644--- a/desktop/vcam/build.rs+++ b/desktop/vcam/build.rs@@ -23,13 +23,13 @@ BEGINBEGINBLOCK "040904B0"BEGIN- VALUE "CompanyName", "The Nectarlink contributors"- VALUE "FileDescription", "Nectarlink virtual camera"+ VALUE "CompanyName", "The NectarLink contributors"+ VALUE "FileDescription", "NectarLink virtual camera"VALUE "FileVersion", "{version}"VALUE "InternalName", "nectarlink_vcam"VALUE "LegalCopyright", "GPL-3.0-or-later"VALUE "OriginalFilename", "nectarlink_vcam.dll"- VALUE "ProductName", "Nectarlink"+ VALUE "ProductName", "NectarLink"VALUE "ProductVersion", "{version}"ENDENDdiff --git a/desktop/vcam/src/lib.rs b/desktop/vcam/src/lib.rsindex 323daa7..50552d9 100644--- a/desktop/vcam/src/lib.rs+++ b/desktop/vcam/src/lib.rs@@ -24,7 +24,7 @@ pub use shm::{};pub use source::{SAMPLE_DURATION_100NS, VcamClassFactory, VcamMediaSource, VcamMediaStream};-/// CLSID of the Nectarlink Virtual Camera Media Foundation media source:+/// CLSID of the NectarLink Virtual Camera Media Foundation media source:/// `{8E6C3B74-5D4A-4B9E-9A12-7C8F1E2D3A40}`.pub const CLSID_NECTARLINK_VCAM: GUID = GUID::from_u128(0x8e6c3b74_5d4a_4b9e_9a12_7c8f1e2d3a40);diff --git a/desktop/vcam/src/shm.rs b/desktop/vcam/src/shm.rsindex 7e02c0b..af215df 100644--- a/desktop/vcam/src/shm.rs+++ b/desktop/vcam/src/shm.rs@@ -441,7 +441,7 @@ pub fn bgrx_to_nv12(bgrx: &[u8], width: u32, height: u32, nv12: &mut [u8]) {const FIGTREE_TTF: &[u8] = include_bytes!("../../../assets/fonts/Figtree.ttf");-/// Honey primary (`docs/design/tokens.json`) and white ink for the Nectarlink mark.+/// Honey primary (`docs/design/tokens.json`) and white ink for the NectarLink mark.const MARK_BG_BGR: [u8; 3] = [0x00, 0x51, 0x8A];const MARK_INK_BGR: [u8; 3] = [0xFF, 0xFF, 0xFF];const MARK_HEXAGON: [(f32, f32); 6] =@@ -461,7 +461,7 @@ struct CachedPlaceholderCard {static PLACEHOLDER_CACHE: std::sync::Mutex<Option<CachedPlaceholderCard>> = std::sync::Mutex::new(None);-/// Renders a clean, calm placeholder frame with the Nectarlink mark and+/// Renders a clean, calm placeholder frame with the NectarLink mark and/// `"Start the webcam on <phone>"` in anti-aliased Figtree into `bgrx` (`width * height * 4`).pub fn render_placeholder_bgrx(bgrx: &mut [u8], width: u32, height: u32, phone_name: &str) {let w = width as usize;@@ -513,7 +513,7 @@ fn build_placeholder_card(width: u32, height: u32, phone_name: &str) -> CachedPl} else {format!("Start the webcam on {phone_name}")};- let caption = "Nectarlink Camera";+ let caption = "NectarLink Camera";let font = TrueTypeFont::parse(FIGTREE_TTF);let head_px = (22.0 * scale).clamp(12.0, 38.0);@@ -787,7 +787,7 @@ mod tests {.0.iter().any(|px| px[0] == 0x00 && px[1] == 0x51 && px[2] == 0x8A && px[3] == 0xFF);- assert!(has_honey_mark, "placeholder should include the Nectarlink honey mark");+ assert!(has_honey_mark, "placeholder should include the NectarLink honey mark");let has_text_ink =frame.as_chunks::<4>().0.iter().any(|px| px[0] > 0xD0 && px[1] > 0xD0 && px[2] > 0xD0);assert!(has_text_ink, "placeholder should include bright headline text ink");diff --git a/desktop/vcam/src/source.rs b/desktop/vcam/src/source.rsindex 736d717..35674de 100644--- a/desktop/vcam/src/source.rs+++ b/desktop/vcam/src/source.rs@@ -1,6 +1,6 @@// SPDX-License-Identifier: GPL-3.0-or-later//! Media Foundation custom media source (`IMFMediaSourceEx`, `IMFMediaStream2`,-//! `IMFMediaEventGenerator`, `IMFGetService`, `IClassFactory`) for the Nectarlink+//! `IMFMediaEventGenerator`, `IMFGetService`, `IClassFactory`) for the NectarLink//! virtual camera.#![allow(unsafe_code, clippy::not_unsafe_ptr_arg_deref)]diff --git a/docs/PERFORMANCE.md b/docs/PERFORMANCE.mdindex 61b3713..60ac6c2 100644--- a/docs/PERFORMANCE.md+++ b/docs/PERFORMANCE.md@@ -1,4 +1,4 @@-# Nectarlink Performance Budgets & Measurements+# NectarLink Performance Budgets & MeasurementsThis document records the release performance budgets, root-cause regression audits, and measured BEFORE/AFTER results across the Windows Desktop app (`nectarlink-desktop`), the Rust core engine (`nectarlink-core`), and the Android companion app (`app.nectarlink.android`).diff --git a/docs/PLAN.md b/docs/PLAN.mdindex 4318e24..ba21cac 100644--- a/docs/PLAN.md+++ b/docs/PLAN.md@@ -1,7 +1,7 @@-# Nectarlink: Product & Engineering Plan+# NectarLink: Product & Engineering Plan-> **Nectarlink** connects Android phones and Windows PCs. It's one open-source app that replaces Phone Link, KDE Connect, scrcpy, LocalSend and Intel Unison.-> *Bees carry nectar back to the hive. Nectarlink carries everything between your phone and your PC.*+> **NectarLink** connects Android phones and Windows PCs. It's one open-source app that replaces Phone Link, KDE Connect, scrcpy, LocalSend and Intel Unison.+> *Bees carry nectar back to the hive. NectarLink carries everything between your phone and your PC.*> Status: **in active development (Qt Quick + Rust on Windows 11, Kotlin + Jetpack Compose on Android, shared Rust core).** Phase 1 and most of Phases 2 to 3 work end to end; see §3 for per-feature status. Last updated 2026-10-09.---@@ -10,14 +10,14 @@| Question | Decision | One-line reason ||---|---|---|-| Name | **Nectarlink** (done) | Clean name (no conflicts found), warm, on the bee theme, says "connection". See §10.1 |+| Name | **NectarLink** (done) | Clean name (no conflicts found), warm, on the bee theme, says "connection". See §10.1 || Shared engine | **Rust core** (`nectarlink-core`) used by both apps | Both ends run the same protocol code, which avoids the cross-implementation bugs KDE Connect has || Transport | **iroh 1.x** (QUIC, devices dialed by public key) | E2E-encrypted by default, LAN discovery, hole punching, relay fallback and multipath in one library (1.0 June 2026, now 1.3) || Wire format | **CBOR (serde)** over QUIC streams, plus a versioned spec in `docs/protocol` | Self-describing and forward-compatible, with no codegen toolchain. Third parties can still implement it || Windows app | **Qt Quick (QML) for the UI + Rust for everything else** (bridged by cxx-qt), `windows-rs` for OS integration, mirrored video drawn inside the UI with no copies. **No WebView, no web stack** (done) | Visual ceiling equal to web (real blur, shaders, Caelestia-level motion) at a fraction of the RAM, best fit for video and always-on overlays. Gated by a Phase 0 "Qt + Rust proof" (§5.1) || Android app | **Kotlin + Jetpack Compose + Material 3 Expressive**, core via **UniFFI** | Deep OS integration needs native Kotlin, and Compose/M3 Expressive is the best-looking, smoothest Android UI stack || Mirroring | **Two engines:** *Elevated* (scrcpy-server, Apache-2.0) and *Standard* (MediaProjection). PC side decodes in hardware with Media Foundation and renders with D3D11 | Best quality and features when privileged access exists, and it still works when it doesn't |-| Superpowers without root | **Power Levels** (Basic → Assist → Elevated). A Root level is parked for later. Elevated mode runs Nectarlink's *own* code as the `shell` user, so there's **no extra app to install**. Several setup paths, and the UI greys out features by level | Unlocks background clipboard, sensitive notifications, consent-free mirroring, app windows and toggles on **any** Android phone |+| Superpowers without root | **Power Levels** (Basic → Assist → Elevated). A Root level is parked for later. Elevated mode runs NectarLink's *own* code as the `shell` user, so there's **no extra app to install**. Several setup paths, and the UI greys out features by level | Unlocks background clipboard, sensitive notifications, consent-free mirroring, app windows and toggles on **any** Android phone || Accounts / cloud | **None.** Local-first. Optional "away from home" mode via relays (self-hostable) | Privacy is the #1 reason people leave Phone Link || Platforms | **Windows 11 only** (x64 + native ARM64). Android 8+. **macOS desktop = future scope** (Qt Quick, the Rust core and the `Platform`/`VideoSink` layers make it a port, not a rewrite). iPhone = later | Win11-only frees us to use Mica, the virtual camera API and the Win11 context menu || Distribution | **GitHub-first**: GitHub Releases + winget (Windows), GitHub Releases + Obtainium + later IzzyOnDroid (Android). No Play account for now | Free, fast to ship, no Play policy limits on SMS/Accessibility/files |@@ -58,8 +58,8 @@| Constraint | Impact | Our answer ||---|---|---|-| Android 10+: no background clipboard read | Auto clipboard sync phone→PC is impossible for normal apps | Elevated mode reads the clipboard. Fallbacks: QS tile, share target, notification button, optional Nectarlink keyboard (IME) |-| Android 15+: sensitive notifications redacted for untrusted listeners | OTPs and 2FA vanish | Elevated mode grants Nectarlink `RECEIVE_SENSITIVE_NOTIFICATIONS` via appops (one time, persists). Explained clearly in onboarding |+| Android 10+: no background clipboard read | Auto clipboard sync phone→PC is impossible for normal apps | Elevated mode reads the clipboard. Fallbacks: QS tile, share target, notification button, optional NectarLink keyboard (IME) |+| Android 15+: sensitive notifications redacted for untrusted listeners | OTPs and 2FA vanish | Elevated mode grants NectarLink `RECEIVE_SENSITIVE_NOTIFICATIONS` via appops (one time, persists). Explained clearly in onboarding || Android 14+: MediaProjection needs consent **every session** | Standard mirroring shows a dialog each time | Elevated engine (scrcpy-server as shell) has no prompts || Android 13+: "restricted settings" for sideloaded apps | Notification-listener and accessibility toggles are greyed out for non-store installs | Onboarding detects it and walks through "Allow restricted settings". Obtainium installs reduce the friction || Android developer verification (enforced from 30 Sep 2026 in BR/ID/SG/TH, global 2027) | Unverified sideloads get blocked, and that includes GitHub APKs | Register for verification (non-Play path) before global enforcement. One signing key for every channel from day one |@@ -71,7 +71,7 @@### 1.4 What we take from KDE Connect (inspiration only, no connection to it)-Nectarlink does **not** pair with or talk to KDE Connect. We study what it does well and build our own version:+NectarLink does **not** pair with or talk to KDE Connect. We study what it does well and build our own version:- **Per-device plugin toggles**: every feature can be switched on/off per paired device. This becomes our per-device feature permissions.- **Run commands**: user-defined PC commands triggered from the phone. Our custom commands / Deck actions, off by default.- **Presentation remote**: slide control plus a pointer. Our presentation remote with laser pointer.@@ -164,7 +164,7 @@ current Android.| Fast, resumable, multi-stream transfers with progress, pause/resume, and integrity hashing (done) (single QUIC stream per transfer with 16 MiB stream window and 8 × 1 MiB read-ahead saturates the shared QUIC congestion window; BLAKE3 integrity hashing and manual pause/resume from either side) | P0 || **Flick to send**: flick a photo/file upward on the phone and it lands on the PC. Drag a file to the screen edge on the PC and it flies to the phone. Physics-based animation on both ends (done) | P1 || **LocalSend protocol interop**: send to and receive from any LocalSend device (iOS, Mac, Linux). We implement its open protocol in Rust; we don't reuse its (Dart) code (done) | P1 |-| **Coexistence**: runs side by side with KDE Connect (ports 1714 to 1764) and LocalSend (53317) on the same PC without conflicts. If LocalSend's port is taken, Nectarlink still sends but leaves receiving to the LocalSend app (done) | P0 |+| **Coexistence**: runs side by side with KDE Connect (ports 1714 to 1764) and LocalSend (53317) on the same PC without conflicts. If LocalSend's port is taken, NectarLink still sends but leaves receiving to the LocalSend app (done) | P0 || **Phone storage in Explorer** (Cloud Files API: placeholders, on-demand download, native sync icons) (done) | P1 || **Photos**: gallery with thumbnails, recent screenshots/photos pop up on PC, drag out to the desktop (done) | P0 (recent), P1 (gallery) || Folder sync (Syncthing-style two-way folders, e.g. Camera → PC) (done) | P2 |@@ -210,7 +210,7 @@ current Android.| Wake-on-LAN (done) | P1 || **Unlock PC with phone fingerprint**: the PC lock screen offers "Unlock with phone" → the phone shows a biometric prompt → a signed challenge unlocks Windows. Built as a Windows credential provider. Keys live in Android Keystore (StrongBox where available) and are bound to biometrics. Works only when paired and nearby (BLE proximity + LAN). Rate-limited, revocable, and **external security review before release**: deferred (dedicated post-1.0 workstream requiring a system-wide `Winlogon` `ICredentialProvider` DLL and external security review) | P2 (dedicated workstream) |-### 3.11 Ambient & signature experiences (what makes Nectarlink special)+### 3.11 Ambient & signature experiences (what makes NectarLink special)| Feature | Tier ||---|---|| **Nectar Island** (optional extra, off by default (`nectar_island: false`), with per-trigger toggles when enabled): a small, animated pill at the top of the PC screen showing live phone activity (call, timer, music, transfer, Live Update, OTP, voice recording). Expands on hover. A nice touch, not a pillar (done) | P2 |@@ -220,7 +220,7 @@ current Android.| **Handoff**: send a link, map location, document or YouTube timestamp to open on the other device (done) | P0 (links), P1 (rich) || **"Ping me when it's done"**: `nectarlink notify-when <pid \| -- command...>` watches a running process or command on the PC, shows a live chronometer notification on the phone while it runs, and alerts the phone when it finishes or fails (done) | P1 || **Timeline**: one searchable history of everything that moved between devices (files, clips, links, photos, recordings), with "send again" (done) | P1 |-| **Your PC in your pocket**: from anywhere (Away mode), browse and grab PC files, see what the PC is doing (Ping-me tasks, downloads), wake it (relayed Wake-on-LAN through another Nectarlink device left at home), and later view/control the PC screen (reverse mirroring) (done) (PC file browsing, Ping-me status, relayed Wake-on-LAN, and reverse PC-to-phone screen mirroring implemented; reverse mirroring is off by default (`pc_mirror` toggle), prompts the PC user for consent on every session with a persistent stop banner, and requires `remote_input` for mouse/keyboard control) | P2 (files/status in P1 if Away mode lands early) |+| **Your PC in your pocket**: from anywhere (Away mode), browse and grab PC files, see what the PC is doing (Ping-me tasks, downloads), wake it (relayed Wake-on-LAN through another NectarLink device left at home), and later view/control the PC screen (reverse mirroring) (done) (PC file browsing, Ping-me status, relayed Wake-on-LAN, and reverse PC-to-phone screen mirroring implemented; reverse mirroring is off by default (`pc_mirror` toggle), prompts the PC user for consent on every session with a persistent stop banner, and requires `remote_input` for mouse/keyboard control) | P2 (files/status in P1 if Away mode lands early) || **Proximity lock**: lock the PC when the phone walks away (BLE RSSI): deferred (requires continuous BLE RSSI hardware ranging; Android emulator lacks a BLE radio) | P2 || **Automations**: triggers (connected, battery low, call started) → actions (done) | P2 || Find my phone (ring even on silent), battery & signal in tray, low-battery alerts, measured phone screen preview & Home summary (done) | P0 |@@ -253,7 +253,7 @@ current Android.```┌──────────────────────── Windows PC (one native process) ──┐ ┌───────────────────────── Android phone ─────────────────────────┐-│ Qt Quick UI (QML screens, Nectarlink design system) │ │ Compose UI (Material 3 Expressive) │+│ Qt Quick UI (QML screens, NectarLink design system) │ │ Compose UI (Material 3 Expressive) ││ main window · Island · Shelf · Deck editor · palette │ │ home · devices · onboarding · Deck · tiles · widgets ││ mirror/app windows: decoded D3D11 video inside the UI │ │ ▲ Kotlin facades (Flows) ││ ▲ cxx-qt bridge (view-models, in-process) │ │ ┌─────┴───────────────────────────────────────────────────┐ │@@ -266,7 +266,7 @@ current Android.│ └─────┬──────────────────────────────────────────────┘ │ QUIC │ │ nectarlink-core (same crate, compiled for arm64/x86_64) │ ││ ┌─────┴──────────────────────────────────────────────┐ │◄──────►│ └─────────────────────────────────────────────────────────┘ ││ │ nectarlink-core (Rust, shared) │ │ iroh │ ┌─────────────────────────────────────────────────────────┐ │-│ │ identity · pairing · sessions · capabilities │ │ │ │ Elevated mode (Nectarlink's own code as shell uid) │ │+│ │ identity · pairing · sessions · capabilities │ │ │ │ Elevated mode (NectarLink's own code as shell uid) │ ││ │ services · transfer engine · store (SQLite) │ │ │ │ clipboard · appops · screen capture · input injection │ ││ └────────────────────────────────────────────────────┘ │ │ │ virtual displays · toggles · scrcpy-server engine │ ││ nectarlink-adb (built-in ADB client) ─ USB / wireless dbg ───┼────────┼─►│ │ │@@ -289,7 +289,7 @@ nectarlink/app/ one crate (cxx-qt builds the QML module, bridge and binary together):src/ Rust host: startup, tray, window lifecycle, wiring to coresrc/bridge/ the ONLY Rust↔Qt bridge: cxx-qt view-models exposed to QML- qml/ Nectarlink design system (tokens, ~30 components) + screens. Presentation only+ qml/ NectarLink design system (tokens, ~30 components) + screens. Presentation onlyplatform/ `Platform` trait: nectarlink-win (windows-rs) now, nectarlink-mac latervideo/ `VideoSink`: MF decode + D3D11 texture → Qt Quick scene-graph item (small C++)now; VideoToolbox + Metal later@@ -339,23 +339,23 @@ Order of attempts (iroh races paths and keeps the best one; multipath lets two p- **Transfers:** chunked, content-hashed (BLAKE3), resumable by offset, parallel streams for many small files, zero-copy reads where possible.### 4.6 Power Levels (one APK, no extra apps)-Everything ships inside the single Nectarlink APK. "Elevated" is **not a separate app**: it's a mode where Nectarlink launches a copy of its *own* code (via `app_process`) with `shell`-user privileges. That process talks back to the app over a local socket with strict caller checks (our UID + signing certificate). Shizuku is only **one optional path** for people who already have it.+Everything ships inside the single NectarLink APK. "Elevated" is **not a separate app**: it's a mode where NectarLink launches a copy of its *own* code (via `app_process`) with `shell`-user privileges. That process talks back to the app over a local socket with strict caller checks (our UID + signing certificate). Shizuku is only **one optional path** for people who already have it.| Level | How you get it | Effort | Lasts | Adds (on top of the level above) ||---|---|---|---|---|| **Basic Basic** | Install + grant normal permissions | ~1 min | Forever | Notifications (non-sensitive), SMS/MMS, calls, contacts, files, photos, media both ways, PC→phone clipboard, webcam, Continuity Camera, voice recorder, voice typing, touchpad/air mouse/Deck, standard mirroring (consent prompt each session, view-only) |-| **Assist Assist** | Turn on Nectarlink's Accessibility service (one toggle, plus the "restricted settings" step for sideloaded installs) | ~1 min | Forever | Control the phone during standard mirroring, global actions (back/home/recents/lock) |+| **Assist Assist** | Turn on NectarLink's Accessibility service (one toggle, plus the "restricted settings" step for sideloaded installs) | ~1 min | Forever | Control the phone during standard mirroring, global actions (back/home/recents/lock) || **Elevated Elevated** | Any one of the setup paths below | 1 to 3 min | Until phone reboot (auto re-arms) | **Auto** phone→PC clipboard, OTP/sensitive notifications, prompt-free mirroring with full control, phone audio to PC, **app windows**, type into the phone with the PC keyboard, Wi-Fi/BT/DND toggles from PC, install APKs from PC, self-whitelist from battery killers |-**Setup paths to Elevated** (Nectarlink recommends the best one by detecting Android version, USB state and Shizuku):+**Setup paths to Elevated** (NectarLink recommends the best one by detecting Android version, USB state and Shizuku):1. **USB cable:** guided "enable USB debugging" (animated, per-OEM steps), then plug in. The PC app has a **built-in ADB client**, so there's nothing else to install. This also turns on the USB connection path.2. **Wireless, using the PC's QR** (Android 11+): the PC shows an ADB-pairing QR, and the phone scans it in *Developer options → Wireless debugging → Pair with QR code*. No cable.-3. **Phone only** (Android 11+): Nectarlink opens Wireless debugging, the user types the pairing code into a Nectarlink notification, and Nectarlink pairs with itself. No PC needed.+3. **Phone only** (Android 11+): NectarLink opens Wireless debugging, the user types the pairing code into a NectarLink notification, and NectarLink pairs with itself. No PC needed.4. **Shizuku / Sui:** one tap if already installed. Never required.**Re-arming after a reboot (keeping it painless):**- If the PC is paired for wireless debugging, the PC silently re-arms the phone the next time both are on the same network.-- On Android 13+, Nectarlink grants itself `WRITE_SECURE_SETTINGS` during the first Elevated session. After that it can switch wireless debugging back on by itself on trusted Wi-Fi, on devices where the OEM allows it.+- On Android 13+, NectarLink grants itself `WRITE_SECURE_SETTINGS` during the first Elevated session. After that it can switch wireless debugging back on by itself on trusted Wi-Fi, on devices where the OEM allows it.- Otherwise it shows a single quiet notification: "Tap to restore superpowers".**Capability-driven UI** (the same rules on both apps):@@ -443,7 +443,7 @@ What we optimize for, in order:**Decision: Qt Quick (QML) for the UI, Rust for everything else.** Fallback: web UI (Tauri) with native Rust video windows.-#### Final three, scored (1 to 5, weighted for Nectarlink; RAM/size/start figures are estimates to verify in Phase 0)+#### Final three, scored (1 to 5, weighted for NectarLink; RAM/size/start figures are estimates to verify in Phase 0)| Criterion | Weight | A. Web (Tauri 2 + React) | **B. Qt Quick + Rust** (done) | C. Slint ||---|---|---|---|---|| Visual ceiling (blur, glass, effects, type) | 15 | 5 | **5** (real blur, shaders, particles) | 3 (no in-app blur/shaders yet) |@@ -462,7 +462,7 @@ What we optimize for, in order:| Mac later | 2 | 4 | **4** | 4 || **Weighted total / 100** | | **≈ 78** | **≈ 81** | **≈ 74** |-**Why B wins (narrowly):** Nectarlink is *always running*, *video-heavy* (mirroring plus one window per phone app) and has *always-on overlays* (Island, Shelf). Those are exactly the web stack's weakest points and Qt's strongest, and Qt gives up nothing on looks. If development speed were weighted above ~20 %, web would win, which is why it is the fallback.+**Why B wins (narrowly):** NectarLink is *always running*, *video-heavy* (mirroring plus one window per phone app) and has *always-on overlays* (Island, Shelf). Those are exactly the web stack's weakest points and Qt's strongest, and Qt gives up nothing on looks. If development speed were weighted above ~20 %, web would win, which is why it is the fallback.**Rejected outright:** Flutter (maintainer's call; multi-window still experimental), Electron (RAM), WinUI 3 (Windows-only), Compose Multiplatform (JVM RAM), Avalonia (C# bridge), GPUI (development slowed in 2026), iced/egui (not built for this).@@ -477,7 +477,7 @@ What we optimize for, in order:| Startup cost of QML | Pre-compile QML to bytecode at build time (`qmlcachegen`, LGPL) || Mica on a Qt window | Direct DWM calls on the native window handle, plus a transparent QML root || **Qt licensing pitfalls** | Use only LGPL modules (Core, Gui, Qml, Quick, Quick Controls, Quick Effects/MultiEffect, Quick Shapes, Svg, Multimedia). **Avoid GPL-only modules:** Qt Qml Compiler (`qmlsc`), Lottie, Quick Timeline, Graphs, Quick 3D, Virtual Keyboard, Canvas Painter. They'd conflict with the future app-store exception. Dynamic linking satisfies LGPL relinking |-| Qt LTS patch releases become **commercial-only** after their first period | Track the **latest Qt 6 minor release** (currently 6.12), pinned per Nectarlink release, instead of relying on LTS patches |+| Qt LTS patch releases become **commercial-only** after their first period | Track the **latest Qt 6 minor release** (currently 6.12), pinned per NectarLink release, instead of relying on LTS patches || Qt's long-term openness | Guaranteed by the KDE Free Qt Foundation agreement: if open-source releases ever stop, Qt becomes BSD-licensed |#### Risk gate (Phase 0): "Qt + Rust proof"@@ -529,7 +529,7 @@ Build Home, a notification card, the Deck grid, one hero transition and a live m**Shared language across both apps**- Same iconography, the same names for features, and the same power-level badges (mapped to the theme's own palette, no traffic-light colors).-- **Dynamic color:** default warm honey/amber accent (on brand for Nectarlink). Once paired, both apps can adopt the phone's Material You palette.+- **Dynamic color:** default warm honey/amber accent (on brand for NectarLink). Once paired, both apps can adopt the phone's Material You palette.- Motion: spring-based (no linear easing), choreographed transitions (a notification card grows into the conversation view), honoring reduced motion.**Desktop (Qt Quick)**@@ -652,7 +652,7 @@ Each phase ends with a usable, releasable product. Phase sizes are relative; act| # | Feature | Target & Constraints | Architecture & Implementation Spec ||---|---|---|---|| **2.1** | **Proximity Lock (BLE RSSI Ranging)** (§3.11) | Lock Windows automatically when the paired phone walks away. | Continuous BLE advertisement RSSI smoothing (EMA filter + hysteresis threshold, e.g. `< -82 dBm` for `> 12 s` or link loss while on battery) in `desktop/app/src/win/ble_beacon.rs` + Android BLE scanner, triggering `LockWorkStation()` when enabled in Settings. |-| **2.2** | **Unlock PC with Phone Fingerprint (`desktop/credprov`)** (§3.10) | Unlock Windows lock screen via phone `BiometricPrompt`. | Isolated Windows `ICredentialProvider` DLL (`desktop/credprov`) communicating over a local named pipe with the Nectarlink service, issuing a 256-bit nonce signed by an Android Keystore `StrongBox` Ed25519/ECDSA key bound to `BiometricPrompt`. Requires external security review before enabling by default. |+| **2.2** | **Unlock PC with Phone Fingerprint (`desktop/credprov`)** (§3.10) | Unlock Windows lock screen via phone `BiometricPrompt`. | Isolated Windows `ICredentialProvider` DLL (`desktop/credprov`) communicating over a local named pipe with the NectarLink service, issuing a 256-bit nonce signed by an Android Keystore `StrongBox` Ed25519/ECDSA key bound to `BiometricPrompt`. Requires external security review before enabling by default. || **2.3** | **Bluetooth RFCOMM Fallback Link** (§3.1) | Keep notifications, SMS, and call alerts alive when no Wi-Fi/LAN or USB is available. | Classic Bluetooth RFCOMM socket transport (`Windows.Devices.Bluetooth.Rfcomm` ↔ Android `BluetoothAdapter.listenUsingRfcommWithServiceRecord`) multiplexed into `nectarlink-core` as a low-bandwidth control path. || **2.4** | **Tablet / Phone as Second Monitor (`IddCx`)** (§3.12) | Extend the Windows desktop onto an Android tablet/phone as a virtual display. | Pair an open-source signed UMDF2 `IddCx` indirect display driver on Windows with the Reverse Mirroring pipeline (§1.2) capturing the virtual display output at 60 to 120 fps. || **2.5** | **Phone as Live PC Microphone** (§3.8) | Route the phone's microphone into Windows apps (Discord, Zoom, OBS). | Stream low-latency 48 kHz mono/stereo PCM from the phone's `AudioRecord` (with `NoiseSuppressor`) to the PC (`audio.pcm` bidirectional stream) and play into a virtual audio endpoint or default communications loopback. |@@ -694,7 +694,7 @@ Each phase ends with a usable, releasable product. Phase sizes are relative; act## 10. Decisions & open questions-### 10.1 Name: **Nectarlink** (done)+### 10.1 Name: **NectarLink** (done)- Repo: `github.com/thtbee/nectarlink` (private until most things work locally; no pushing before that).- Checks done: no conflicting products found on the web; `nectarlink.app`, `nectarlink.dev`, `getnectarlink.com` and the GitHub name were free (2026-10-05).- **Still to do before any announcement:** official trademark searches (USPTO, TMview, IP India), register the domain, X handle, and reserve `nectar-link` as a redirect.@@ -715,7 +715,7 @@ Each phase ends with a usable, releasable product. Phase sizes are relative; act**Windows 11 only**, x64 + ARM64.### 10.5 Crash reporting (done) (opt-in)-- Nothing is sent unless you say yes. After a crash, Nectarlink asks once and shows the exact redacted report (no notification text, message content, file names or keys).+- Nothing is sent unless you say yes. After a crash, NectarLink asks once and shows the exact redacted report (no notification text, message content, file names or keys).- **v1 uses no server at all:** "Report on GitHub" opens a prefilled issue, and you attach the redacted bundle yourself.- If volume grows: an opt-in, self-hosted GlitchTip (Sentry-compatible) server.- Tooling: Rust minidumps (`crash-handler`) on desktop, ACRA with a consent dialog on Android.@@ -757,8 +757,8 @@ Each phase ends with a usable, releasable product. Phase sizes are relative; act## 11. Pre-flight checklist### Must resolve before writing code-1. **Name clearance.** Trademark search for "Nectarlink" in software classes (9 and 42) in the US, EU and India, then secure the domain, GitHub org and X handle. Do this *before* teasing the name to the X audience, because renaming after a public announcement is costly.-2. **Signing-key custody.** The Android signing key is Nectarlink's permanent identity: lose it and every user has to uninstall to update, and developer verification is tied to it. Generate it once, keep two offline backups, and store it as a CI secret. The same applies to the auto-update signing key.+1. **Name clearance.** Trademark search for "NectarLink" in software classes (9 and 42) in the US, EU and India, then secure the domain, GitHub org and X handle. Do this *before* teasing the name to the X audience, because renaming after a public announcement is costly.+2. **Signing-key custody.** The Android signing key is NectarLink's permanent identity: lose it and every user has to uninstall to update, and developer verification is tied to it. Generate it once, keep two offline backups, and store it as a CI secret. The same applies to the auto-update signing key.3. **Dev environment (done) (done 2026-10-04)**:- Installed: Qt 6.12.0 (MSVC x64 + ARM64) in `C:\Qt`, Android NDK 30.0.16248370 + CMake 4.1.2, Android command-line tools, Rust targets (Android ×4, Windows ARM64), `cargo-ndk` 4.1.2.- Already present: Android platform 37, build-tools 36, platform-tools, Rust 1.99, MSVC Build Tools 2022, Node 24, Python 3.14.@@ -793,7 +793,7 @@ Each phase ends with a usable, releasable product. Phase sizes are relative; act| # | Step | Owner | Output ||---|---|---|---|-| 1 | Name clearance + grab domain, GitHub org, X handle | Maintainer | "Nectarlink" cleared by official searches |+| 1 | Name clearance + grab domain, GitHub org, X handle | Maintainer | "NectarLink" cleared by official searches || 2 | Phase 0 detailed spec: protocol v0 (Hello, pairing, capabilities), `nectarlink-core` public API, capability-matrix schema, repo scaffolding plan, ADRs, spike test plans with pass criteria | Claude | `docs/` specs || 3 | Design foundations + 2 to 3 visual directions (both apps) | Claude → maintainer picks | Chosen direction, then hi-fi mockups || 4 | Dev environment setup (Qt 6.12, JDK, Android SDK/NDK, Rust targets) | Together | One-command build prerequisites |diff --git a/docs/SECURITY-REVIEW.md b/docs/SECURITY-REVIEW.mdindex f3aa33b..1587702 100644--- a/docs/SECURITY-REVIEW.md+++ b/docs/SECURITY-REVIEW.md@@ -1,13 +1,13 @@-# Nectarlink Security Review+# NectarLink Security Review**Review Date:** 2026-10-10-**Scope:** End-to-end audit of every network, local IPC, elevated privilege, shared-memory, and filesystem surface in Nectarlink (`nectarlink-protocol`, `nectarlink-core`, `nectarlink-adb`, `nectarlink-desktop`, `nectarlink-vcam`, Android app, and `nectarlink-shell` helper).+**Scope:** End-to-end audit of every network, local IPC, elevated privilege, shared-memory, and filesystem surface in NectarLink (`nectarlink-protocol`, `nectarlink-core`, `nectarlink-adb`, `nectarlink-desktop`, `nectarlink-vcam`, Android app, and `nectarlink-shell` helper).---## Executive Summary-Nectarlink follows a strict **zero-trust, local-first security architecture**:+NectarLink follows a strict **zero-trust, local-first security architecture**:1. **Mutual Ed25519 + TLS 1.3 / QUIC Authentication:** Every peer has a persistent 256-bit Ed25519 identity key (`iroh::SecretKey`). Post-pairing sessions (`ALPN = "nectarlink/0"`) enforce mutual certificate verification and immediately drop any connection whose remote `EndpointId` is not present in the local SQLite `peers` table (`store.is_paired(&peer)`).2. **Out-of-Band / Mutual-Consent Pairing:** Pairing (`ALPN = "nectarlink/pair/0"`) requires either scanning a QR code containing a one-time 128-bit cryptographic token (`tok`) with a 5-minute TTL, or explicit user confirmation of a 6-digit Short Authentication String (SAS) derived via BLAKE3 from the TLS exporter key (`EXPORTER-nectarlink-pair-v0`) and both peers' Ed25519 public keys (`derive_sas` in `core/nectarlink-protocol/src/sas.rs`).3. **Strict Wire & Filesystem Boundaries:** Every incoming CBOR/JSON envelope is size-capped BEFORE allocation (`MAX_FRAME_LEN = 1 MiB`), validated via `.is_valid()` and `.sanitized()`, and gated by per-peer feature permissions (`PeerPermissions`). All incoming file and storage paths reject `..`, root prefixes, drive letters, and NUL bytes.@@ -120,7 +120,7 @@ Nectarlink follows a strict **zero-trust, local-first security architecture**:- `desktop/app/src/main.rs`### Threat Model-- **Cross-Session / Multi-User Local Spoofing:** On a multi-user Windows machine, another logged-in user attempts to signal Nectarlink's Win32 event or write a malicious `Request` into the launch queue.+- **Cross-Session / Multi-User Local Spoofing:** On a multi-user Windows machine, another logged-in user attempts to signal NectarLink's Win32 event or write a malicious `Request` into the launch queue.- **Malformed / Oversized Launch Queue File:** Corrupted or adversarial JSON in `<data_dir>/launch/` attempts to crash the running tray process.### Security Controls in Place@@ -268,7 +268,7 @@ Nectarlink follows a strict **zero-trust, local-first security architecture**:3. **PC Audio Streaming to Phone (`desktop/app/src/pc_audio_stream.rs`):**- Off by default (`Settings::pc_audio_to_phone = false`). Audio loopback capture (`WASAPI`) can only be enabled locally from the PC's Settings UI (`Camera & Audio -> Stream PC audio to phone`) and only streams to connected phones that have the `media` toggle enabled.4. **PC Storage Provider (`desktop/app/src/pc_storage.rs`, `core/nectarlink-core/src/storage.rs`):**- - Gated by the `storage` toggle (`false` by default), plus `remote_files` (`false` by default) when connected over a non-LAN `ConnectionPath::Relay` path. Sandboxed to the user's non-sensitive `Nectarlink Shared` folder via `FolderStorage` (which rejects `..`, absolute paths, and symlink escapes).+ - Gated by the `storage` toggle (`false` by default), plus `remote_files` (`false` by default) when connected over a non-LAN `ConnectionPath::Relay` path. Sandboxed to the user's non-sensitive `NectarLink Shared` folder via `FolderStorage` (which rejects `..`, absolute paths, and symlink escapes).5. **PC Notifications to Phone (`desktop/app/src/pc_notifications.rs`):**- Off by default (`Settings::forward_pc_notifications = false`). Only forwards when explicitly enabled by the PC user in Settings AND Windows `UserNotificationListener` access is granted AND the per-device `notifications` toggle is on.diff --git a/docs/api.md b/docs/api.mdindex 21ea9ca..3a042f9 100644--- a/docs/api.md+++ b/docs/api.md@@ -1,6 +1,6 @@-# Nectarlink Local Authenticated Automation API (`docs/api.md`)+# NectarLink Local Authenticated Automation API (`docs/api.md`)-Nectarlink for Windows includes an opt-in, loopback-only HTTP/JSON API (`127.0.0.1:<port>`, default port `53320`) designed for local desktop automation tools:+NectarLink for Windows includes an opt-in, loopback-only HTTP/JSON API (`127.0.0.1:<port>`, default port `53320`) designed for local desktop automation tools:- **PowerToys Command Palette / PowerToys Run** (`tools/powertoys-extension`)- **AutoHotkey / Raycast for Windows / Flow Launcher**@@ -12,7 +12,7 @@ Nectarlink for Windows includes an opt-in, loopback-only HTTP/JSON API (`127.0.0The Local API is **off by default**. Enable it in **Settings → Local automation API** (or set `"localApiEnabled": true` in `%LOCALAPPDATA%\Nectarlink\desktop-settings.json`).-When enabled, Nectarlink binds strictly to `127.0.0.1:<localApiPort>` (default `53320`) and writes `<data-dir>\api-token.json` (`%LOCALAPPDATA%\Nectarlink\api-token.json`):+When enabled, NectarLink binds strictly to `127.0.0.1:<localApiPort>` (default `53320`) and writes `<data-dir>\api-token.json` (`%LOCALAPPDATA%\Nectarlink\api-token.json`):```json{diff --git a/docs/design/assets/nl.css b/docs/design/assets/nl.cssindex eb9ca9a..8b1c56e 100644--- a/docs/design/assets/nl.css+++ b/docs/design/assets/nl.css@@ -1,4 +1,4 @@-/* Nectarlink design preview stylesheet. Mirrors docs/design/tokens.json. */+/* NectarLink design preview stylesheet. Mirrors docs/design/tokens.json. */:root{--sans:"Figtree","Segoe UI Variable Text","Segoe UI",system-ui,sans-serif;--serif:"Instrument Serif",Georgia,serif;diff --git a/docs/design/assets/nl.js b/docs/design/assets/nl.jsindex 54c9a8e..9588284 100644--- a/docs/design/assets/nl.js+++ b/docs/design/assets/nl.js@@ -1,4 +1,4 @@-// Nectarlink design preview helpers: icons, Material You seeds, theme switcher.+// NectarLink design preview helpers: icons, Material You seeds, theme switcher.const ICON = {home:'<path d="M3 11l9-7 9 7"/><path d="M5 10v10h14V10"/>',msg:'<path d="M21 12a8 8 0 0 1-11.6 7.1L4 20l1-4.6A8 8 0 1 1 21 12z"/>',diff --git a/docs/design/mockups/index.html b/docs/design/mockups/index.htmlindex e2e4094..b8d9e98 100644--- a/docs/design/mockups/index.html+++ b/docs/design/mockups/index.html@@ -3,7 +3,7 @@<head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1">-<title>Nectarlink Mockups</title>+<title>NectarLink Mockups</title><!-- Preview only: the apps bundle these OFL fonts locally. --><link rel="preconnect" href="https://fonts.googleapis.com"><link rel="preconnect" href="https://fonts.gstatic.com" crossorigin><link href="https://fonts.googleapis.com/css2?family=Figtree:wght@400;500;600;700&family=Instrument+Serif&family=Space+Mono:wght@400;700&family=Caveat:wght@500&display=swap" rel="stylesheet">@@ -153,7 +153,7 @@</head><body data-theme="bloom-light"><div class="bar">- <div class="brand">Nectarlink <span>· Mockups</span></div>+ <div class="brand">NectarLink <span>· Mockups</span></div><div class="seg" id="themes"><button data-t="bloom-light" class="on">Bloom Light</button><button data-t="bloom-dark">Bloom Dark</button><button data-t="graphite-paper">Graphite Paper</button><button data-t="graphite-slate">Graphite Slate</button>@@ -187,12 +187,12 @@ document.getElementById('screens').innerHTML =set('pair','1 · First run','Pair in under a minute','The PC shows a QR code; the phone scans it and both sides are paired and authenticated, with no codes to type. Nearby pairing (6-digit code check) and USB pairing are one click away.',`<div class="win sm"><div class="main">- <header class="top"><h3>Welcome to Nectarlink</h3><span class="grow"></span><span class="cap">Step 1 of 2</span></header>+ <header class="top"><h3>Welcome to NectarLink</h3><span class="grow"></span><span class="cap">Step 1 of 2</span></header><div class="pair"><div class="crop"><i></i><i></i><i></i><i></i><div class="qrbox">${qrSVG()}</div></div><span class="G cap">Fig. 00 // Pairing code</span><h2>Scan with your phone</h2>- <div class="steps"><span><b>1</b>Install Nectarlink</span><span><b>2</b>Tap “Pair with PC”</span><span><b>3</b>Scan this code</span></div>+ <div class="steps"><span><b>1</b>Install NectarLink</span><span><b>2</b>Tap “Pair with PC”</span><span><b>3</b>Scan this code</span></div><div class="alt"><button class="btn tonal sm">${i('wifi')}Pair nearby instead</button><button class="btn out sm">${i('usb')}Use a USB cable</button></div><span class="timer">Code refreshes in 4:12 · Only works on this network</span></div></div></div>@@ -210,7 +210,7 @@ set('pair','1 · First run','Pair in under a minute',set('onboard','2 · Phone setup','One live checklist','Every permission shows its real state, why it is needed, and one tap to grant it. Nothing is buried in settings, and the list updates the moment a permission is granted.',`<div>${phone(`<div class="ph-title" style="margin-top:6px">Almost there</div>- <p class="ph-sub">Give Nectarlink what it needs. You can change any of this later.</p>+ <p class="ph-sub">Give NectarLink what it needs. You can change any of this later.</p><div class="progress"><i></i></div><div class="check done"><span class="st">${i('check')}</span><div class="tx"><b>Notifications</b><small>Show your phone's alerts on your PC</small></div></div><div class="check done"><span class="st">${i('check')}</span><div class="tx"><b>Messages & calls</b><small>Texts, call alerts and contacts</small></div></div>@@ -219,7 +219,7 @@ set('onboard','2 · Phone setup','One live checklist',<div class="check"><span class="st">${i('bell')}</span><div class="tx"><b>Restricted settings</b><small>Needed because the app came from GitHub</small></div><button class="btn tonal sm">Show me</button></div><button class="btn fill wide" style="margin-top:auto">Continue</button>`)}<p class="caption"><b>Checklist.</b> States are live; sideloaded installs get a guided “Allow restricted settings” step.</p></div>- <div>${phone(`<div style="display:flex;justify-content:space-between;align-items:center;margin-top:6px"><span class="ph-title">Nectarlink</span><span class="av p">B</span></div>+ <div>${phone(`<div style="display:flex;justify-content:space-between;align-items:center;margin-top:6px"><span class="ph-title">NectarLink</span><span class="av p">B</span></div><div class="card" style="background:var(--hero-bg);color:var(--hero-ink);border-radius:var(--r-xl)"><span class="G cap">Fig. 02 // Linked to</span><div class="ph-title" style="font-size:21px">Bee's Desktop</div><div class="hint" style="color:inherit;opacity:.8">Connected · Wi-Fi · 12 ms</div><div style="display:flex;gap:6px;margin-top:10px"><span class="chip">Laptop 64%</span><span class="chip">Basic</span></div></div><div class="card" style="display:flex;gap:12px;align-items:center"><span class="av p">${i('bolt')}</span><div style="flex:1"><b style="font-size:13px">Unlock more</b><div class="hint">Auto clipboard, OTP codes, app windows</div></div>${i('chev')}</div>@@ -227,7 +227,7 @@ set('onboard','2 · Phone setup','One live checklist',<div class="tabbar"><span class="on">${i('home')}</span><span>${i('send')}</span><span>${i('deck')}</span><span>${i('gear')}</span></div>`)}<p class="caption"><b>Home.</b> A gentle “Unlock more” card instead of nagging. It disappears once you choose.</p></div>`) +-set('power','3 · Choose your power','Pick how much Nectarlink can do',+set('power','3 · Choose your power','Pick how much NectarLink can do','Three clear levels, each showing what it unlocks, what it needs, how long it takes and how to undo it. A smart default is pre-selected; “Decide later” is always available.',`<div>${phone(`<div class="ph-title" style="margin-top:4px">Choose your power</div><p class="ph-sub">Everything works at Basic. More access unlocks more.</p>@@ -245,7 +245,7 @@ set('power','3 · Choose your power','Pick how much Nectarlink can do',<div class="path"><span class="ic">${i('usb')}</span><div class="tx"><b>Plug into your PC</b><small>USB debugging · 1 min</small></div>${i('chev')}</div><div class="path"><span class="ic">${i('handset')}</span><div class="tx"><b>On this phone only</b><small>No PC needed · Android 11+</small></div>${i('chev')}</div><div class="path"><span class="ic">${i('shield')}</span><div class="tx"><b>Use Shizuku</b><small>Already installed · 1 tap</small></div>${i('chev')}</div>- <p class="hint" style="margin-top:auto">Nectarlink starts a helper with developer access, built into this app. It never leaves your phone and you can revoke it in Settings.</p>`)}+ <p class="hint" style="margin-top:auto">NectarLink starts a helper with developer access, built into this app. It never leaves your phone and you can revoke it in Settings.</p>`)}<p class="caption"><b>Setup paths.</b> Recommended path chosen from what's detected (Android version, USB, Shizuku).</p></div>`) +set('notif','4 · Notifications','Your phone’s alerts, organized',@@ -268,8 +268,8 @@ set('notif','4 · Notifications','Your phone’s alerts, organized',<div class="composer">Reply to Mom…<span class="grow"></span><span class="send">${i('send')}</span></div><div class="via">Replies are sent through WhatsApp on your phone</div></div></div></div></div><div style="display:flex;flex-direction:column;gap:14px">- <div class="toast"><div class="t"><i></i>Nectarlink · Pixel 9<span class="grow"></span>now</div><h5>Mom · WhatsApp</h5><p>Dinner at 8? Bring the charger you borrowed.</p><div class="reply"><span>Type a reply</span><b>Send</b></div></div>- <div class="toast"><div class="t"><i></i>Nectarlink · Pixel 9<span class="grow"></span>now</div><h5>Google</h5><p>Your sign-in code is 482 913</p><div class="reply"><b style="flex:1">Copy code</b><b>Dismiss</b></div></div>+ <div class="toast"><div class="t"><i></i>NectarLink · Pixel 9<span class="grow"></span>now</div><h5>Mom · WhatsApp</h5><p>Dinner at 8? Bring the charger you borrowed.</p><div class="reply"><span>Type a reply</span><b>Send</b></div></div>+ <div class="toast"><div class="t"><i></i>NectarLink · Pixel 9<span class="grow"></span>now</div><h5>Google</h5><p>Your sign-in code is 482 913</p><div class="reply"><b style="flex:1">Copy code</b><b>Dismiss</b></div></div><p class="caption" style="max-width:364px"><b>Toasts.</b> Native Windows style for system consistency; only the small app badge picks up the theme accent.</p></div>`) +diff --git a/docs/design/themes/index.html b/docs/design/themes/index.htmlindex 18d8f70..a22d6a6 100644--- a/docs/design/themes/index.html+++ b/docs/design/themes/index.html@@ -3,7 +3,7 @@<head><meta charset="utf-8"><meta name="viewport" content="width=device-width, initial-scale=1">-<title>Nectarlink Themes</title>+<title>NectarLink Themes</title><!-- Preview only: the apps bundle these OFL fonts locally and never load them from the web. --><link rel="preconnect" href="https://fonts.googleapis.com"><link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>@@ -259,7 +259,7 @@ svg{width:19px;height:19px;stroke:currentColor;fill:none;stroke-width:1.8;stroke<body data-theme="bloom-light"><div class="bar">- <div class="brand">Nectarlink <span>· Themes</span></div>+ <div class="brand">NectarLink <span>· Themes</span></div><div class="seg" id="themes"><button data-t="bloom-light" class="on">Bloom Light</button><button data-t="bloom-dark">Bloom Dark</button>@@ -378,7 +378,7 @@ document.getElementById('stage').innerHTML=`</div><div class="phone"><div class="screen"><div class="cam"></div><div class="sb"><span>9:41</span><span>82%</span></div>- <div class="ph-top"><h3>Nectarlink</h3><div class="avatar">B</div></div>+ <div class="ph-top"><h3>NectarLink</h3><div class="avatar">B</div></div><div class="pc"><div class="fig">Fig. 02 // This phone is linked to</div><h4>Bee's Desktop</h4><p>Connected · Wi-Fi · 12 ms</p><div class="pills"><span class="pill">Laptop 64%</span><span class="pill">Elevated</span></div></div><div class="tiles">diff --git a/docs/design/tokens.json b/docs/design/tokens.jsonindex 9f4f112..f207e19 100644--- a/docs/design/tokens.json+++ b/docs/design/tokens.json@@ -1,6 +1,6 @@{"$schema": "nectarlink-design-tokens/v1",- "$description": "Single source of truth for Nectarlink design tokens. QML (desktop) and Compose (Android) themes are generated from this file. Bloom colors follow Material You tonal roles; at runtime the Android app derives them from the wallpaper and sends the seed to the PC (hello.device.accent). The palettes here are the fallbacks and brand presets.",+ "$description": "Single source of truth for NectarLink design tokens. QML (desktop) and Compose (Android) themes are generated from this file. Bloom colors follow Material You tonal roles; at runtime the Android app derives them from the wallpaper and sends the seed to the PC (hello.device.accent). The palettes here are the fallbacks and brand presets.","themes": {"hive": {"description": "Honey on charcoal (Comb, dark) and on warm wax (Wax, light), with a living honeycomb behind the app that grows from the logo, breathes and pulses. Colors are fixed: no wallpaper, artwork or phone colors.",diff --git a/docs/guide/README.md b/docs/guide/README.mdindex 1eb3c20..76451ab 100644--- a/docs/guide/README.md+++ b/docs/guide/README.md@@ -1,14 +1,14 @@-# Nectarlink User Guide+# NectarLink User Guide-Nectarlink connects your Android phone and your Windows 11 PC directly over your local network. It handles notifications, messages, calls, clipboard sharing, file transfers, photo browsing, screen mirroring, camera streaming, audio routing, and cross-device input in one open-source application.+NectarLink connects your Android phone and your Windows 11 PC directly over your local network. It handles notifications, messages, calls, clipboard sharing, file transfers, photo browsing, screen mirroring, camera streaming, audio routing, and cross-device input in one open-source application.<p align="center">- <img src="images/home-bloom.png" alt="Nectarlink for Windows home screen in the Bloom theme" width="760">+ <img src="images/home-bloom.png" alt="NectarLink for Windows home screen in the Bloom theme" width="760"></p>## Why This Guide Is Organized This Way-Documentation for Nectarlink is split into two parts so you can find answers quickly:+Documentation for NectarLink is split into two parts so you can find answers quickly:1. **User Guide (`docs/guide/`)**: Organized by everyday tasks and feature areas. Each page explains what a feature does, why it is useful, what permissions or settings it requires, how to use it step by step, where your data is stored, and what platform limits apply. This layout matches the navigation inside the Windows and Android apps and can be rendered directly on GitHub or published as a static documentation site.2. **Technical Reference ([`docs/technical/`](../technical/README.md))**: Written for developers, security auditors, and contributors. It covers internal crate architecture, the wire protocol, FFI bridges, database schemas, performance budgets, and build instructions.@@ -33,7 +33,7 @@ Separating task-oriented workflows from implementation internals keeps everyday### Screen, Camera, Audio, and Input- [Mirroring and App Windows](mirroring.md): Mirroring your phone screen at up to 60 fps (H.264, H.265, AV1), forwarding phone audio, taking screenshots and MP4 recordings, keeping the phone awake or turning its physical screen off, remote touch and keyboard input (`Assist` and `Elevated`), opening individual phone apps in their own `app window`, DeX desktop mode, and reverse mirroring your PC screen to your phone.-- [Cameras and Audio](cameras-and-audio.md): Using your phone as a Windows webcam (`Nectarlink Webcam` virtual camera add-on), lens and zoom controls, Continuity Camera for capturing photos and scanning documents with corner crop and black-and-white enhancement, using your phone as a low-latency wireless speaker for PC audio, and recording voice notes with timestamped markers.+- [Cameras and Audio](cameras-and-audio.md): Using your phone as a Windows webcam (`NectarLink Webcam` virtual camera add-on), lens and zoom controls, Continuity Camera for capturing photos and scanning documents with corner crop and black-and-white enhancement, using your phone as a low-latency wireless speaker for PC audio, and recording voice notes with timestamped markers.- [Input and Control](input-and-control.md): Controlling your PC from your phone (touchpad, gyroscope air mouse, keyboard with modifier bar, voice dictation, presentation remote with laser pointer), typing on your phone from your PC keyboard, the `Deck` macro pad, phone system controls on PC Home, Desk Mode stand display, and Lock, Sleep, and Wake-on-LAN actions.- [Desktop Surfaces and Automation](desktop-surfaces.md): The slide-out `Shelf` edge panel, Flick to send gestures, `Nectar Island` top-of-screen activity pill, the searchable cross-device `Timeline`, the global `Command Palette` (`Ctrl+Alt+Space`), rich `Handoff` for links, maps, videos, and documents, `notify-when` task completion alerts, trigger-action automations, the local HTTP API, and the command-line client.@@ -47,14 +47,14 @@ Separating task-oriented workflows from implementation internals keeps everyday## Glossary-Nectarlink uses consistent terms across the Windows app, the Android app, and this guide:+NectarLink uses consistent terms across the Windows app, the Android app, and this guide:| Term | Definition || :--- | :--- || `pair` | The one-time cryptographic ceremony that links a phone and a PC. Pairing exchanges Ed25519 public keys and verifies a shared secret via a QR code token or a 6-digit confirmation code. |-| `paired device` | A phone or PC that has completed pairing and is stored in your local trust store. Only a `paired device` can open an encrypted Nectarlink session with your device. |+| `paired device` | A phone or PC that has completed pairing and is stored in your local trust store. Only a `paired device` can open an encrypted NectarLink session with your device. || `Standard` | The default Android power level. It uses ordinary Android runtime permissions and notification listener access, requiring no accessibility service and no developer options. |-| `Assist` | The second Android power level. It adds Nectarlink's Android Accessibility Service (**Use your PC's mouse and keyboard** under **Control from your PC**) so your PC mouse and keyboard can tap, swipe, scroll, and type during screen mirroring without developer setup. |+| `Assist` | The second Android power level. It adds NectarLink's Android Accessibility Service (**Use your PC's mouse and keyboard** under **Control from your PC**) so your PC mouse and keyboard can tap, swipe, scroll, and type during screen mirroring without developer setup. || `Elevated` | The third Android power level (**Real touch and keys (Wireless debugging)** under **Control from your PC**). It uses Android's built-in Wireless Debugging (or USB `adb`) to run a local shell helper (`UID 2000`, no root). It enables real-time touch dragging, UHID physical keyboard and gamepad input, `app window` streaming, automatic background phone-to-PC clipboard sync, sensitive notification OTP detection on Android 15+, Wi-Fi and Bluetooth toggles, and in-call mute/hold/speaker controls. || `mirror` | A live video and audio stream of your phone's primary screen inside a dedicated window on your PC (or, with **Share PC screen to phone**, your PC's screen on your phone). || `app window` | A single Android application streamed to its own independent window on your PC using an Android virtual display (`Elevated` on Android 11+), running alongside whatever is on the phone's physical screen. |@@ -63,7 +63,7 @@ Nectarlink uses consistent terms across the Windows app, the Android app, and th| `Timeline` | A searchable local history of everything shared between your devices, including files, clipboard items, links, saved photos, voice recordings, and mirroring or webcam sessions. || `island` (**Nectar Island**) | An optional compact pill at the top center of your PC monitor that displays live phone calls, file transfer progress, media playback, timers, and alerts. || `Waiting to send` | A persistent queue panel on Home (both PC and Android) that holds files, clipboard items, links, and task alerts sent while the target device was offline, delivering them automatically in order as soon as the device reconnects. |-| `Command Palette` | A keyboard-driven launcher on your PC (`Ctrl+Alt+Space`) for running any Nectarlink action, sending text or files, starting mirroring, or jumping to settings from any application. |+| `Command Palette` | A keyboard-driven launcher on your PC (`Ctrl+Alt+Space`) for running any NectarLink action, sending text or files, starting mirroring, or jumping to settings from any application. || `Connection Doctor` | A diagnostic tool in the Windows app (**Settings › Connection & About › Connection Doctor**) and Android app that checks firewall rules, network profile type, VPN routing, Wi-Fi AP isolation, and Android background battery restrictions. || **Connect over mobile data** | An opt-in setting (**Settings › Connection & About › Connect over mobile data** on the PC and **Settings › Devices › Connect over mobile data** on Android, off by default on both) that allows paired devices to stay connected across different networks (such as LTE/5G and home broadband) using end-to-end encrypted relay packets when a direct LAN path is unavailable. || `Handoff` | Sending an active web link, map location (`geo:` URI), video link with its current playback timestamp, or document to a paired device so it opens immediately in the default application on the receiving side. |diff --git a/docs/guide/calls.md b/docs/guide/calls.mdindex 6f99db0..ae1c1cd 100644--- a/docs/guide/calls.md+++ b/docs/guide/calls.md@@ -19,7 +19,7 @@ The **Calls** page on your PC lets you see incoming phone calls with caller ID,### Handling Incoming Calls on Your PC-1. When your phone rings, Nectarlink displays an incoming call banner on your PC (and expands `Nectar Island` if enabled) showing the caller's name, phone number, and contact photo.+1. When your phone rings, NectarLink displays an incoming call banner on your PC (and expands `Nectar Island` if enabled) showing the caller's name, phone number, and contact photo.2. If **Pause media during calls** is enabled in **Settings › Camera & Audio**, any music or video playing on your PC pauses automatically while the phone is ringing or in a call, and resumes when the call ends.3. From the incoming call banner on your PC, you can:- Click **Answer** to pick up the call on your phone.@@ -49,14 +49,14 @@ The **Calls** page groups your phone's recent incoming, outgoing, and missed cal## Why Call Voice Audio Stays on Your Phone-When you answer or place a call from your PC, Nectarlink controls the call on your phone while the voice audio itself remains on your phone's earpiece, speakerphone, or Bluetooth headset paired directly to your phone.+When you answer or place a call from your PC, NectarLink controls the call on your phone while the voice audio itself remains on your phone's earpiece, speakerphone, or Bluetooth headset paired directly to your phone.This is due to two operating system restrictions (documented in detail in [`docs/research/hfp.md`](../research/hfp.md)):1. **Android hardware voice routing**: On non-rooted Android devices, cellular call audio (`VOICE_CALL`, `VOICE_DOWNLINK`, `VOICE_UPLINK`) is routed by the modem DSP and blocked from software capture (`AudioPlaybackCapture` explicitly excludes voice communication, even at the `Elevated` shell level).2. **Windows 11 Bluetooth HFP restrictions**: Windows' `AudioPlaybackConnection` API only supports one-way A2DP media playback (not two-way Hands-Free Profile voice channels), and Microsoft's `PhoneLineTransportDevice` HFP broker on Windows 11 22H2 and newer rejects third-party applications with `E_ACCESSDENIED` unless they run with Microsoft's internal inbox system identity or a WHQL-signed kernel driver.-For hands-free calling at your desk, click **Speaker** in Nectarlink's call bar (with `Elevated`) or keep your wireless headphones paired to your phone via multipoint Bluetooth.+For hands-free calling at your desk, click **Speaker** in NectarLink's call bar (with `Elevated`) or keep your wireless headphones paired to your phone via multipoint Bluetooth.## What the Options Do@@ -68,7 +68,7 @@ For hands-free calling at your desk, click **Speaker** in Nectarlink's call bar## Data and Privacy- **Where data travels**: Call state changes, caller ID metadata, recent call log entries, and contact records travel directly between your phone and PC over your end-to-end encrypted QUIC connection.-- **Where data stays**: Recent call logs and contacts are read live from your phone and held in memory on the PC during your session. Nectarlink never records call audio.+- **Where data stays**: Recent call logs and contacts are read live from your phone and held in memory on the PC during your session. NectarLink never records call audio.## Limitsdiff --git a/docs/guide/cameras-and-audio.md b/docs/guide/cameras-and-audio.mdindex 1a81900..66de090 100644--- a/docs/guide/cameras-and-audio.md+++ b/docs/guide/cameras-and-audio.md@@ -1,6 +1,6 @@# Cameras and Audio-Nectarlink lets your PC use your phone's cameras and audio hardware in four ways: streaming your phone's camera as a Windows webcam (`Nectarlink Webcam`), snapping photos or scanning documents straight into your PC clipboard (**Continuity Camera**), playing your PC's system audio through your phone (**Phone as speaker**), and recording voice notes on your phone that land automatically on your PC (**Voice recorder**).+NectarLink lets your PC use your phone's cameras and audio hardware in four ways: streaming your phone's camera as a Windows webcam (`NectarLink Webcam`), snapping photos or scanning documents straight into your PC clipboard (**Continuity Camera**), playing your PC's system audio through your phone (**Phone as speaker**), and recording voice notes on your phone that land automatically on your PC (**Voice recorder**).<p align="center"><img src="images/webcam-live.png" alt="Camera and Audio settings on Windows showing a live webcam preview from the phone" width="760">@@ -23,11 +23,11 @@ Your phone's main camera sensor offers much better optics and low-light quality#### One-Time Virtual Camera Add-On Setup-You can preview your phone's camera inside Nectarlink's **Settings › Camera & Audio** immediately with zero setup. To make **Nectarlink Webcam** appear as a selectable camera inside Zoom, Microsoft Teams, Google Meet, Discord, OBS Studio, and the Windows Camera app:+You can preview your phone's camera inside NectarLink's **Settings › Camera & Audio** immediately with zero setup. To make **NectarLink Webcam** appear as a selectable camera inside Zoom, Microsoft Teams, Google Meet, Discord, OBS Studio, and the Windows Camera app:1. On your PC, open **Settings › Camera & Audio**.2. Next to **Virtual camera add-on**, click **Set up** and approve the Windows User Account Control (UAC) administrator prompt.-3. Nectarlink registers `nectarlink_vcam.dll` with Windows 11's Media Foundation `MFCreateVirtualCamera` service. Once registered, the status indicator shows **Ready** (and you can unregister it at any time by clicking **Remove**).+3. NectarLink registers `nectarlink_vcam.dll` with Windows 11's Media Foundation `MFCreateVirtualCamera` service. Once registered, the status indicator shows **Ready** (and you can unregister it at any time by clicking **Remove**).#### Starting and Controlling the Webcam Stream@@ -40,7 +40,7 @@ You can preview your phone's camera inside Nectarlink's **Settings › Camera &- **Zoom**: Tap `1x` or `2x` presets or drag the continuous zoom slider on your phone.- **Flashlight (Torch)**: Toggle the rear LED flash on or off for fill lighting.- **Mirror image**: Horizontally flip the video feed in PC **Settings › Camera & Audio**.-3. Open your video conferencing app on Windows and select **Nectarlink Webcam** as your camera.+3. Open your video conferencing app on Windows and select **NectarLink Webcam** as your camera.### 2. Continuity Camera: Take a Photo or Scan a Document@@ -54,7 +54,7 @@ When you need to insert a photo of a physical object, whiteboard, or multi-corne3. **In Photo mode**: Frame your shot, tap **Capture photo**, inspect the preview, and tap **Use photo** (or **Retake**).4. **In Scan mode**:- Capture the page or receipt.- - Drag the four corner handles (**Adjust corners**) to match the edges of the document. Nectarlink corrects the perspective geometry into a flat rectangle.+ - Drag the four corner handles (**Adjust corners**) to match the edges of the document. NectarLink corrects the perspective geometry into a flat rectangle.- Toggle **Enhance document** to apply high-contrast black-and-white document enhancement for crisp, readable text.- Tap **Send scan**.5. The captured photo or enhanced scan arrives on your PC in `Downloads\Nectarlink` and is automatically placed onto your Windows clipboard so you can press `Ctrl+V` straight into Word, Notion, Slack, email, or any image editor.@@ -84,14 +84,14 @@ Use your phone's microphone to record voice notes, interviews, or meeting memos4. When you finish and tap **Send**:- If your PC is online, the recording transfers immediately and lands in your chosen recordings folder (`Downloads\Nectarlink` or `Documents\Nectarlink Recordings` by default).- If you chose **MP3**, **WAV**, or **FLAC** in PC **Settings › Files & Sync › Voice recordings** (instead of the default **M4A**), your PC automatically converts the audio file upon arrival.- - If you added markers during the recording, Nectarlink writes a companion `<filename>.markers.txt` file right beside the audio file listing every marker's timestamp and label.+ - If you added markers during the recording, NectarLink writes a companion `<filename>.markers.txt` file right beside the audio file listing every marker's timestamp and label.- If your PC is offline when you finish recording, the voice note stays saved on your phone and is sent automatically as soon as your PC reconnects.## What the Options Do- **Stream PC audio to phone** (`Settings › Camera & Audio` on PC, default: **Off**): Streams real-time Windows system audio to your connected phone.- **Pause media during calls** (`Settings › Camera & Audio` on PC, default: **On**): Auto-pauses PC media playback when your phone rings or is in a call.-- **Virtual camera add-on** (`Settings › Camera & Audio` on PC): Registers or removes the Windows 11 `Nectarlink Webcam` Media Foundation virtual camera.+- **Virtual camera add-on** (`Settings › Camera & Audio` on PC): Registers or removes the Windows 11 `NectarLink Webcam` Media Foundation virtual camera.- **Phone** (`Settings › Camera & Audio` on PC, shown when multiple phones are paired): Selects which paired phone is used for the webcam.- **Camera** (`Settings › Camera & Audio` on PC, default: **Back**): Selects the **Back** or **Front** phone lens.- **Mirror image** (`Settings › Camera & Audio` on PC, default: **Off**): Flips the webcam video horizontally.@@ -101,7 +101,7 @@ Use your phone's microphone to record voice notes, interviews, or meeting memos## Data and Privacy-- **Explicit camera consent on the phone**: A paired PC can never open your phone's camera silently. Whenever you click **Start webcam** or trigger **Continuity Camera** from the PC, your phone displays a notification requiring a physical tap on the phone before the camera opens. While streaming, Android's green camera privacy indicator and Nectarlink's persistent **Streaming camera to `<PC>`** notification remain visible on your phone with a one-tap **Stop** button.+- **Explicit camera consent on the phone**: A paired PC can never open your phone's camera silently. Whenever you click **Start webcam** or trigger **Continuity Camera** from the PC, your phone displays a notification requiring a physical tap on the phone before the camera opens. While streaming, Android's green camera privacy indicator and NectarLink's persistent **Streaming camera to `<PC>`** notification remain visible on your phone with a one-tap **Stop** button.- **Shared memory isolation**: On Windows, decoded webcam frames are passed to the Media Foundation virtual camera DLL through a logon-session-scoped shared memory ring buffer (`Local\NectarlinkVirtualCamera_v2`) with strict atomic bounds checking (`MAX_WIDTH = 3840`, `MAX_HEIGHT = 2160`) so other Windows user accounts cannot read the feed.- **Temporary camera cache**: Temporary Continuity Camera captures on the phone are stored in the app's private cache and deleted automatically within 24 hours (or immediately via **Settings › Features & Data › Data & storage › Photo thumbnails & camera cache › Clear**).@@ -109,5 +109,5 @@ Use your phone's microphone to record voice notes, interviews, or meeting memos- **4K Webcam Hardware Support**: 4K (`3840 x 2160`) webcam streaming requires a phone camera sensor and hardware encoder that support 4K 30 fps output, plus sufficient Wi-Fi or USB bandwidth. If a phone camera only supports up to 1080p, it streams at its highest supported resolution.- **8-Bit SDR Webcam Pipeline**: The webcam pipeline uses 8-bit SDR color (`NV12` / `RGB32` Media Foundation media types) for broad compatibility across Zoom, Teams, Meet, Chrome, and OBS; 10-bit HDR video is not used.-- **Administrator Prompt for Virtual Camera Registration**: Registering or removing a system-wide Media Foundation virtual camera on Windows 11 (**Virtual camera add-on › Set up**) requires a one-time Administrator (UAC) approval. Previewing the webcam inside Nectarlink's own window works without Administrator privileges.+- **Administrator Prompt for Virtual Camera Registration**: Registering or removing a system-wide Media Foundation virtual camera on Windows 11 (**Virtual camera add-on › Set up**) requires a one-time Administrator (UAC) approval. Previewing the webcam inside NectarLink's own window works without Administrator privileges.- **Continuity Camera Request Expiry**: If you trigger **Take photo** or **Scan document** while your phone is offline, the queued request expires after **2 minutes** so your phone does not unexpectedly prompt for a photo hours later.diff --git a/docs/guide/clipboard.md b/docs/guide/clipboard.mdindex a8e7883..3732fa5 100644--- a/docs/guide/clipboard.md+++ b/docs/guide/clipboard.md@@ -1,9 +1,9 @@# Clipboard-Nectarlink shares your clipboard between your Windows 11 PC and your Android phone. Copy plain text, rich HTML text, an image, or a file on one device and paste it on the other, with smart action chips for links and addresses, an optional encrypted 50-item clipboard history, and automatic filtering for passwords and one-time verification codes.+NectarLink shares your clipboard between your Windows 11 PC and your Android phone. Copy plain text, rich HTML text, an image, or a file on one device and paste it on the other, with smart action chips for links and addresses, an optional encrypted 50-item clipboard history, and automatic filtering for passwords and one-time verification codes.<p align="center">- <img src="images/clipboard-autopaste.png" alt="Clipboard sync and smart context chips in Nectarlink" width="760">+ <img src="images/clipboard-autopaste.png" alt="Clipboard sync and smart context chips in NectarLink" width="760"></p>## What You Need@@ -20,37 +20,37 @@ Nectarlink shares your clipboard between your Windows 11 PC and your Android pho### Copying on Your PC to Paste on Your Phone1. On your PC, copy any plain text, formatted HTML text, or image (`Ctrl+C`, right-click **Copy**, or `Win+Shift+S` screen snip).-2. With **Sync clipboard to phone** turned on in **Settings › General** (the default), Nectarlink sends the copied content to your connected phone automatically in the background.+2. With **Sync clipboard to phone** turned on in **Settings › General** (the default), NectarLink sends the copied content to your connected phone automatically in the background.3. On your phone, tap **Paste** in any text field or image editor.4. You can also send your current PC clipboard manually at any time by clicking **Send clipboard** on the PC Home screen or running **Send clipboard to phone** in the `Command Palette` (`Ctrl+Alt+Space`).### Copying on Your Phone to Paste on Your PC-Android 10 and newer block background apps from reading the system clipboard unless they run with shell privileges. Nectarlink gives you two ways to send your phone's clipboard to your PC:+Android 10 and newer block background apps from reading the system clipboard unless they run with shell privileges. NectarLink gives you two ways to send your phone's clipboard to your PC:-- **Automatic in the background (with `Elevated`)**: Once you enable `Elevated` (via Wireless Debugging in **Settings › Permissions › Control from your PC** or **Settings › Features & Data › Clipboard › Background clipboard access**), Nectarlink's local shell helper listens for clipboard changes and sends copied text and images to your PC automatically as soon as you tap **Copy** in any app.+- **Automatic in the background (with `Elevated`)**: Once you enable `Elevated` (via Wireless Debugging in **Settings › Permissions › Control from your PC** or **Settings › Features & Data › Clipboard › Background clipboard access**), NectarLink's local shell helper listens for clipboard changes and sends copied text and images to your PC automatically as soon as you tap **Copy** in any app.- **One-tap manual send (at `Standard` or `Assist`)**: Without `Elevated`, you can send what you copied on your phone using any of four quick surfaces:1. **Quick Settings tile**: Pull down your phone's notification shade and tap the **Send clipboard** tile.2. **Android share sheet**: Select text or an image in any app, tap **Share**, and choose **Send to PC** (or tap your PC's Direct Share icon).- 3. **Home screen widget**: Tap **Send clip** on the Nectarlink **PC quick actions** widget on your Android home screen.- 4. **Inside the Nectarlink app**: Tap **Send clipboard** on the Android Home screen (or in the persistent connection notification).+ 3. **Home screen widget**: Tap **Send clip** on the NectarLink **PC quick actions** widget on your Android home screen.+ 4. **Inside the NectarLink app**: Tap **Send clipboard** on the Android Home screen (or in the persistent connection notification).### Copying and Pasting Files (`Ctrl+C` / `Ctrl+V`)-Nectarlink bridges Windows file clipboard drops (`CF_HDROP`) with file transfers:+NectarLink bridges Windows file clipboard drops (`CF_HDROP`) with file transfers:-- **PC to phone**: If you copy one or more files in Windows File Explorer (`Ctrl+C`) and click **Send clipboard** in Nectarlink, those files are transferred straight to your phone.+- **PC to phone**: If you copy one or more files in Windows File Explorer (`Ctrl+C`) and click **Send clipboard** in NectarLink, those files are transferred straight to your phone.- **Phone to PC**: When **Copy received files** is enabled in **Settings › General** (the default), small files and photos you send from your phone to your PC are saved to `Downloads\Nectarlink` and automatically placed onto your Windows clipboard as file drops so you can press `Ctrl+V` straight into an email, chat window, document, or folder.### Smart Context Chips-When a text clip arrives from a paired device and matches a recognizable pattern, Nectarlink displays a context chip on the confirmation banner so you can act on it with one click or tap:+When a text clip arrives from a paired device and matches a recognizable pattern, NectarLink displays a context chip on the confirmation banner so you can act on it with one click or tap:| Detected Content | Context Chip Action || :--- | :--- || **Web URL (`https://...`)** | **Open**: Opens the link in your default web browser. || **Street Address or Coordinates** | **Open in Maps**: Opens the address in your default maps app. |-| **Phone Number** | **Call**: Opens the number in the Nectarlink dialer (on PC) or phone dialer (on Android). |+| **Phone Number** | **Call**: Opens the number in the NectarLink dialer (on PC) or phone dialer (on Android). || **Parcel Tracking Number** (UPS, FedEx, USPS, DHL) | **Track**: Opens the carrier tracking page for that package. || **Email Address** | **Email**: Starts a new email to that address in your default mail client. |diff --git a/docs/guide/desktop-surfaces.md b/docs/guide/desktop-surfaces.mdindex aae9198..14f1c00 100644--- a/docs/guide/desktop-surfaces.md+++ b/docs/guide/desktop-surfaces.md@@ -1,9 +1,9 @@# Desktop Surfaces and Automation-Beyond the main window, Nectarlink integrates into Windows 11 with fast, low-overhead desktop surfaces and automation tools: the slide-out **`Shelf`** edge panel, **`Nectar Island`** at the top of your screen, the searchable cross-device **`Timeline`**, the global **`Command Palette`** (`Ctrl+Alt+Space`), rich **`Handoff`** for links, maps, videos, and documents, **`notify-when`** process completion alerts, a trigger-action **Rules Engine**, a local authenticated **HTTP API**, a **PowerToys Command Palette** extension, and the `nectarlink` command-line client.+Beyond the main window, NectarLink integrates into Windows 11 with fast, low-overhead desktop surfaces and automation tools: the slide-out **`Shelf`** edge panel, **`Nectar Island`** at the top of your screen, the searchable cross-device **`Timeline`**, the global **`Command Palette`** (`Ctrl+Alt+Space`), rich **`Handoff`** for links, maps, videos, and documents, **`notify-when`** process completion alerts, a trigger-action **Rules Engine**, a local authenticated **HTTP API**, a **PowerToys Command Palette** extension, and the `nectarlink` command-line client.<p align="center">- <img src="images/command-palette.png" alt="Global Command Palette open over the Nectarlink window on Windows 11" width="760">+ <img src="images/command-palette.png" alt="Global Command Palette open over the NectarLink window on Windows 11" width="760"></p>## What You Need@@ -72,7 +72,7 @@ The `Timeline` gives you one searchable local log of everything that has moved b### 4. Global `Command Palette` (`Ctrl+Alt+Space`)-Press **`Ctrl+Alt+Space`** from anywhere in Windows to open Nectarlink's `Command Palette` over your current window:+Press **`Ctrl+Alt+Space`** from anywhere in Windows to open NectarLink's `Command Palette` over your current window:1. Start typing to fuzzy-search every action, paired device, recent file, or setting:- **Mirror phone screen**@@ -93,8 +93,8 @@ Press **`Ctrl+Alt+Space`** from anywhere in Windows to open Nectarlink's `Comman- **Web links**: Share any URL from your phone's browser to your PC via the Android share sheet (or send a URL from your PC via the `Command Palette` or `nectarlink send <url>`). The link opens immediately in the default browser on the receiving device.- **Maps and street addresses**: Share a Google Maps link or `geo:` location URI between devices to open that location directly in Maps.-- **Video links with playback timestamp**: When you share a YouTube, Vimeo, or Twitch link (or run `nectarlink send <url> --at-seconds 142`), Nectarlink attaches the current playback position so the receiving device offers a **Continue watching** action that resumes the video at the exact second you left off.-- **Documents (`--open` / `Shift+Drop`)**: Hold **`Shift`** while dropping a document onto Nectarlink (or run `nectarlink send report.pdf --open`) to transfer the file and open it automatically in the default viewer on the receiving device as soon as the transfer finishes.+- **Video links with playback timestamp**: When you share a YouTube, Vimeo, or Twitch link (or run `nectarlink send <url> --at-seconds 142`), NectarLink attaches the current playback position so the receiving device offers a **Continue watching** action that resumes the video at the exact second you left off.+- **Documents (`--open` / `Shift+Drop`)**: Hold **`Shift`** while dropping a document onto NectarLink (or run `nectarlink send report.pdf --open`) to transfer the file and open it automatically in the default viewer on the receiving device as soon as the transfer finishes.### 6. Task Completion Alerts (`nectarlink notify-when`)@@ -123,10 +123,10 @@ You can automate routine actions between your phone and PC without writing scrip### 8. Local Authenticated HTTP API and PowerToys Extension-For power users who use **PowerToys Command Palette**, **AutoHotkey**, **Raycast**, **Flow Launcher**, or custom PowerShell/Python scripts, Nectarlink includes an opt-in local HTTP/JSON API:+For power users who use **PowerToys Command Palette**, **AutoHotkey**, **Raycast**, **Flow Launcher**, or custom PowerShell/Python scripts, NectarLink includes an opt-in local HTTP/JSON API:1. Open PC **Settings › Connection & About** and turn on **Local automation API** (default port `53320`).-2. Nectarlink binds strictly to loopback (`127.0.0.1:53320`, never exposed on LAN) and writes a random 256-bit Bearer token to `%LOCALAPPDATA%\Nectarlink\api-token.json`.+2. NectarLink binds strictly to loopback (`127.0.0.1:53320`, never exposed on LAN) and writes a random 256-bit Bearer token to `%LOCALAPPDATA%\Nectarlink\api-token.json`.3. Every request must include `Authorization: Bearer <token>`, and any request carrying a browser `Origin` header is rejected with `403 Forbidden` to prevent cross-site browser attacks.4. Available endpoints (see [`docs/api.md`](../api.md) for full request/response schemas and PowerShell/`curl` examples):- `GET /v1/devices`: List paired devices, connection status, and battery level.@@ -136,7 +136,7 @@ For power users who use **PowerToys Command Palette**, **AutoHotkey**, **Raycast- `POST /v1/ring`: Trigger Find my phone.- `POST /v1/camera`: Trigger Continuity Camera (`"photo"` or `"scan"`).- `GET /v1/timeline`: Query recent cross-device `Timeline` entries.-5. A companion **PowerToys Command Palette** extension in `tools/powertoys-cmdpal/` connects to this API so you can invoke Nectarlink actions directly from PowerToys.+5. A companion **PowerToys Command Palette** extension in `tools/powertoys-cmdpal/` connects to this API so you can invoke NectarLink actions directly from PowerToys.## What the Options Do@@ -154,4 +154,4 @@ For power users who use **PowerToys Command Palette**, **AutoHotkey**, **Raycast## Limits- **Global Hotkey Conflicts**: If another Windows application has already registered `Ctrl+Alt+Space`, `Ctrl+Alt+S`, `Ctrl+Alt+C`, or `Ctrl+Alt+D` as a system-wide hotkey, you can assign any non-conflicting `Ctrl`/`Alt`/`Shift`/`Win` key combination in **Settings › Shortcuts & Rules**.-- **Windows Widgets Board Provider (`NectarlinkPhoneStatus`)**: Nectarlink includes a Windows App SDK Widget Provider (`desktop/app/src/win/widget.rs`), plus the taskbar **Jump List** that works on all installs. Appearing inside the Windows 11 `Win+W` Widgets board requires the app's sparse package manifest to be registered with a trusted code-signing certificate or Windows Developer Mode enabled. On Android, the **PC quick actions** home-screen widget works on all devices out of the box.+- **Windows Widgets Board Provider (`NectarlinkPhoneStatus`)**: NectarLink includes a Windows App SDK Widget Provider (`desktop/app/src/win/widget.rs`), plus the taskbar **Jump List** that works on all installs. Appearing inside the Windows 11 `Win+W` Widgets board requires the app's sparse package manifest to be registered with a trusted code-signing certificate or Windows Developer Mode enabled. On Android, the **PC quick actions** home-screen widget works on all devices out of the box.diff --git a/docs/guide/faq.md b/docs/guide/faq.mdindex 01a815a..b7e4851 100644--- a/docs/guide/faq.md+++ b/docs/guide/faq.md@@ -2,35 +2,35 @@## General and Accounts-### Do I need to create an account or sign in to use Nectarlink?+### Do I need to create an account or sign in to use NectarLink?-No. Nectarlink has no user accounts, no sign-in screens, and no cloud servers. Each device generates its own cryptographic Ed25519 identity key locally on first launch, and you link your devices directly by scanning a QR code or comparing a 6-digit code.+No. NectarLink has no user accounts, no sign-in screens, and no cloud servers. Each device generates its own cryptographic Ed25519 identity key locally on first launch, and you link your devices directly by scanning a QR code or comparing a 6-digit code.-### Is Nectarlink free and open source?+### Is NectarLink free and open source?Yes. The Windows and Android applications and the CLI are licensed under [GPL-3.0-or-later](../../LICENSES/GPL-3.0-or-later.txt) (with an app-store distribution exception), the shared Rust core crates are licensed under [MPL-2.0](../../LICENSES/MPL-2.0.txt), and the protocol specifications and documentation are licensed under [CC BY 4.0](../../LICENSES/CC-BY-4.0.txt). There are no paid tiers, subscriptions, or advertisements.-### Does Nectarlink only work with Samsung or Pixel phones?+### Does NectarLink only work with Samsung or Pixel phones?-No. Nectarlink works with any Android phone or tablet running Android 8.0 (API 26) or newer, regardless of manufacturer (Samsung, Google Pixel, Xiaomi, OnePlus, Motorola, Sony, Nothing, Asus, Oppo, Realme, Vivo, Huawei, and others).+No. NectarLink works with any Android phone or tablet running Android 8.0 (API 26) or newer, regardless of manufacturer (Samsung, Google Pixel, Xiaomi, OnePlus, Motorola, Sony, Nothing, Asus, Oppo, Realme, Vivo, Huawei, and others).## Networking and Connectivity### Do my phone and PC have to be on the same Wi-Fi network?-By default, yes: Nectarlink connects directly over your local network (Wi-Fi or Ethernet) or over a USB data cable (`On USB`). If you want your phone and PC to stay connected when you leave home on mobile data (LTE/5G) or use a separate Wi-Fi network, turn on **Connect over mobile data** in **Settings › Connection & About** on your PC and **Settings › Devices** on your phone.+By default, yes: NectarLink connects directly over your local network (Wi-Fi or Ethernet) or over a USB data cable (`On USB`). If you want your phone and PC to stay connected when you leave home on mobile data (LTE/5G) or use a separate Wi-Fi network, turn on **Connect over mobile data** in **Settings › Connection & About** on your PC and **Settings › Devices** on your phone.### Does my data pass through a server when I use **Connect over mobile data**?-When **Connect over mobile data** is turned on and a direct peer-to-peer UDP path cannot be established between your networks, encrypted QUIC packets are forwarded through an `iroh` relay. Because the TLS 1.3 session is encrypted end to end between your phone's key and your PC's key, the relay only forwards opaque encrypted packets and can never read your notifications, messages, clipboard, or files. When your devices are on the same local network or connected by USB, all device-to-device traffic goes straight between them without leaving your local network (the only internet request Nectarlink makes by default on installed copies is a periodic HTTPS check to GitHub Releases for app updates, which can be turned off on the PC in **Settings › Connection & About › Automatic updates**).+When **Connect over mobile data** is turned on and a direct peer-to-peer UDP path cannot be established between your networks, encrypted QUIC packets are forwarded through an `iroh` relay. Because the TLS 1.3 session is encrypted end to end between your phone's key and your PC's key, the relay only forwards opaque encrypted packets and can never read your notifications, messages, clipboard, or files. When your devices are on the same local network or connected by USB, all device-to-device traffic goes straight between them without leaving your local network (the only internet request NectarLink makes by default on installed copies is a periodic HTTPS check to GitHub Releases for app updates, which can be turned off on the PC in **Settings › Connection & About › Automatic updates**).-### Can I use Nectarlink without Wi-Fi at all, using only a USB cable?+### Can I use NectarLink without Wi-Fi at all, using only a USB cable?-Yes. Enable **USB debugging** in your phone's Developer options and plug your phone into your PC with a USB data cable. Nectarlink automatically detects the USB connection, lets you pair with a 6-digit confirmation code, and runs your entire encrypted session (`On USB`) over the cable.+Yes. Enable **USB debugging** in your phone's Developer options and plug your phone into your PC with a USB data cable. NectarLink automatically detects the USB connection, lets you pair with a 6-digit confirmation code, and runs your entire encrypted session (`On USB`) over the cable.### What happens if I send a file or copy a link while my other device is asleep or offline?-It is not lost. Nectarlink places files, folders, clipboard sends, `Handoff` links, and `notify-when` task alerts into a persistent `Waiting to send` queue stored in SQLite. You can see and cancel queued items on the Home screen of either app, and they are delivered automatically in order as soon as the other device reconnects.+It is not lost. NectarLink places files, folders, clipboard sends, `Handoff` links, and `notify-when` task alerts into a persistent `Waiting to send` queue stored in SQLite. You can see and cancel queued items on the Home screen of either app, and they are delivered automatically in order as soon as the other device reconnects.### Can I pair multiple phones with one PC, or one phone with multiple PCs?@@ -38,37 +38,37 @@ Yes. You can pair two or more phones (for example, a personal phone and a work p## Power Levels and Permissions-### Do I need to root my phone to use Nectarlink?+### Do I need to root my phone to use NectarLink?-No. Nothing in Nectarlink uses or requires root access. Every everyday feature works at the default `Standard` power level using normal Android permissions, and advanced features (`Elevated`) use Android's official built-in Wireless Debugging (`UID 2000` shell user).+No. Nothing in NectarLink uses or requires root access. Every everyday feature works at the default `Standard` power level using normal Android permissions, and advanced features (`Elevated`) use Android's official built-in Wireless Debugging (`UID 2000` shell user).### Why does Android 13+ gray out the Notification access or Accessibility switch ("Restricted settings")?-Android 13 and newer block sideloaded APKs (apps installed outside an app store) from turning on Notification Listener or Accessibility services until you confirm in **App info**. Open **Android Settings › Apps › Nectarlink**, tap the three-dot menu in the top-right corner, tap **Allow restricted settings**, verify with your fingerprint or PIN, and then return to Nectarlink to turn the switch on.+Android 13 and newer block sideloaded APKs (apps installed outside an app store) from turning on Notification Listener or Accessibility services until you confirm in **App info**. Open **Android Settings › Apps › NectarLink**, tap the three-dot menu in the top-right corner, tap **Allow restricted settings**, verify with your fingerprint or PIN, and then return to NectarLink to turn the switch on.### Do I have to re-pair Wireless Debugging (`Elevated`) every time I reboot my phone?-No. You only enter the 6-digit Wireless Debugging pairing code once during initial setup. After that, whenever your phone reboots or reconnects to Wi-Fi, Nectarlink automatically turns Wireless Debugging back on and starts the `Elevated` helper in the background by itself.+No. You only enter the 6-digit Wireless Debugging pairing code once during initial setup. After that, whenever your phone reboots or reconnects to Wi-Fi, NectarLink automatically turns Wireless Debugging back on and starts the `Elevated` helper in the background by itself.-### Can I use Nectarlink if I do not want to grant SMS, Call, or Photo permissions?+### Can I use NectarLink if I do not want to grant SMS, Call, or Photo permissions?-Yes. Every Android permission is optional, and Nectarlink's capability matrix adapts the user interface to show only what you have enabled. For example, if you only want clipboard sync, file transfers, and screen mirroring, you can skip SMS, Calls, Contacts, and Photos permissions completely.+Yes. Every Android permission is optional, and NectarLink's capability matrix adapts the user interface to show only what you have enabled. For example, if you only want clipboard sync, file transfers, and screen mirroring, you can skip SMS, Calls, Contacts, and Photos permissions completely.## Battery, Memory, and Performance-### How much battery does Nectarlink use on my phone?+### How much battery does NectarLink use on my phone?-When connected and idle in the background, Nectarlink maintains a single lightweight QUIC connection with event-driven wakeups and zero polling loops, using less than 1 percent battery per hour in continuous connected soak tests. High-power features such as screen mirroring (`mirror`) and camera streaming (**Phone as webcam**) use hardware video encoders only while actively streaming and stop immediately when you close the window.+When connected and idle in the background, NectarLink maintains a single lightweight QUIC connection with event-driven wakeups and zero polling loops, using less than 1 percent battery per hour in continuous connected soak tests. High-power features such as screen mirroring (`mirror`) and camera streaming (**Phone as webcam**) use hardware video encoders only while actively streaming and stop immediately when you close the window.### How much RAM and CPU does the Windows app use in the background?-When started minimized in the Windows system tray, Nectarlink uses approximately **27 MB** of private commit memory (~5 to 10 MB active working set) and **0.0 percent** idle CPU. When you close the main window (`Stay in system tray`), Nectarlink unloads the QML window tree and image caches to keep background memory usage minimal while staying ready to pop up notifications or open the `Shelf` and `Command Palette` in under 50 milliseconds.+When started minimized in the Windows system tray, NectarLink uses approximately **27 MB** of private commit memory (~5 to 10 MB active working set) and **0.0 percent** idle CPU. When you close the main window (`Stay in system tray`), NectarLink unloads the QML window tree and image caches to keep background memory usage minimal while staying ready to pop up notifications or open the `Shelf` and `Command Palette` in under 50 milliseconds.## Privacy and Data Management-### Does Nectarlink send my clipboard when I copy a password from my password manager?+### Does NectarLink send my clipboard when I copy a password from my password manager?-No. Password managers on both Windows (such as 1Password, Bitwarden, and KeePassXC) and Android 13+ mark copied passwords with system privacy flags (`ExcludeClipboardContentFromMonitorProcessing` on Windows and `ClipDescription.EXTRA_IS_SENSITIVE` on Android). Nectarlink checks those flags before reading or sending the clipboard and skips any sensitive item. One-time verification codes (OTPs) are also excluded from clipboard history and `Timeline`.+No. Password managers on both Windows (such as 1Password, Bitwarden, and KeePassXC) and Android 13+ mark copied passwords with system privacy flags (`ExcludeClipboardContentFromMonitorProcessing` on Windows and `ClipDescription.EXTRA_IS_SENSITIVE` on Android). NectarLink checks those flags before reading or sending the clipboard and skips any sensitive item. One-time verification codes (OTPs) are also excluded from clipboard history and `Timeline`.### How do I delete my local history or unpair a device?diff --git a/docs/guide/files-and-transfers.md b/docs/guide/files-and-transfers.mdindex 19ab2fb..d1c1421 100644--- a/docs/guide/files-and-transfers.md+++ b/docs/guide/files-and-transfers.md@@ -1,9 +1,9 @@# Files and Transfers-Nectarlink transfers files and folders between your phone and PC at full local Wi-Fi or USB speed. Every transfer supports manual pause and resume, automatic recovery after a dropped connection, end-to-end BLAKE3 integrity verification, and an offline `Waiting to send` queue so nothing is lost when the other device is asleep or out of reach. You can also mount your phone's storage directly inside Windows File Explorer, browse your PC's folders from your phone, set up automatic folder sync, and share files with nearby LocalSend devices.+NectarLink transfers files and folders between your phone and PC at full local Wi-Fi or USB speed. Every transfer supports manual pause and resume, automatic recovery after a dropped connection, end-to-end BLAKE3 integrity verification, and an offline `Waiting to send` queue so nothing is lost when the other device is asleep or out of reach. You can also mount your phone's storage directly inside Windows File Explorer, browse your PC's folders from your phone, set up automatic folder sync, and share files with nearby LocalSend devices.<p align="center">- <img src="images/files-localsend.png" alt="File transfers and LocalSend in Nectarlink for Windows" width="760">+ <img src="images/files-localsend.png" alt="File transfers and LocalSend in NectarLink for Windows" width="760"></p>## What You Need@@ -22,7 +22,7 @@ Nectarlink transfers files and folders between your phone and PC at full local WYou can send files or entire folders from your PC using any of these entry points:-1. **Drag and drop**: Drag files or folders onto the Nectarlink main window, onto the slide-out `Shelf` edge panel (`Ctrl+Alt+S`), or onto an open `mirror` window.+1. **Drag and drop**: Drag files or folders onto the NectarLink main window, onto the slide-out `Shelf` edge panel (`Ctrl+Alt+S`), or onto an open `mirror` window.2. **Flick to send**: Drag a file toward the screen edge where your `Shelf` sits with a quick flick gesture. A 3-second **Undo** toast appears before the transfer begins.3. **Home screen button**: Click **Send files** on the PC Home screen and pick files or folders.4. **File Explorer `Send to` menu**: Right-click any file or folder in Windows File Explorer, choose **Send to**, and click your phone's name.@@ -32,25 +32,25 @@ Received files on your phone are saved to `Download/Nectarlink` (preserving subf### Sending Files and Folders from Phone to PC-1. **From any Android app**: Tap **Share**, then tap your PC's Direct Share target at the top of the Android share sheet (or tap **Nectarlink**). The transfer starts right away; with more than one PC connected, you pick one first. Its progress shows in a notification with a **Cancel** button, followed by a **Sent to** confirmation.-2. **From the Nectarlink app**: Open Nectarlink on your phone and tap **Send files** or **Send a folder** under **Quick Transfer & Clipboard**.+1. **From any Android app**: Tap **Share**, then tap your PC's Direct Share target at the top of the Android share sheet (or tap **NectarLink**). The transfer starts right away; with more than one PC connected, you pick one first. Its progress shows in a notification with a **Cancel** button, followed by a **Sent to** confirmation.+2. **From the NectarLink app**: Open NectarLink on your phone and tap **Send files** or **Send a folder** under **Quick Transfer & Clipboard**.Received files on your PC are saved to `Downloads\Nectarlink` (avoiding overwrites by adding a numeric suffix if a file with the same name already exists). If **Copy received files** is enabled in **Settings › General**, small received files are also placed on your Windows clipboard so you can paste them anywhere with `Ctrl+V`.### Pausing, Resuming, and Verifying Transfers- **Manual Pause and Resume**: While a large file is transferring, click **Pause** in the **Transfers** card on either the PC or the phone to pause the stream at the current byte offset, and click **Resume** whenever you are ready to continue.-- **Automatic Resume on Reconnect**: Incoming files are written to a staging `.part` file. If your Wi-Fi drops or you unplug a USB cable mid-transfer, Nectarlink keeps the partial bytes and automatically resumes from the exact byte offset when the connection returns.+- **Automatic Resume on Reconnect**: Incoming files are written to a staging `.part` file. If your Wi-Fi drops or you unplug a USB cable mid-transfer, NectarLink keeps the partial bytes and automatically resumes from the exact byte offset when the connection returns.- **BLAKE3 Integrity Check**: Every file transfer computes a full-file cryptographic **BLAKE3** hash. The receiver verifies the hash before moving the completed `.part` file to its final destination. If a single byte fails verification, the file is never committed as complete.### Offline Queue and the `Waiting to send` Panel-When you send files, folders, clipboard items, links, `Handoff` documents, or `notify-when` alerts while your other device is offline, Nectarlink does not fail the action. Instead, it queues the item reliably:+When you send files, folders, clipboard items, links, `Handoff` documents, or `notify-when` alerts while your other device is offline, NectarLink does not fail the action. Instead, it queues the item reliably:1. A confirmation toast lets you know the target device is offline and that your item will be sent automatically when it reconnects, with an **Undo** button.2. On Home (both PC and Android), a compact **`Waiting to send`** panel appears whenever items are queued, showing the total count and each item's icon, name, target device, size, and status (`Waiting`, `Sending` with live progress, `Failed` with reason, or `Expired`). The system tray tooltip and `Nectar Island` also quietly note how many items are waiting.3. The queue is stored in SQLite (`send_queue` table) and **survives app restarts and system reboots** on both platforms, holding up to 200 items or 10 GiB of pending files.-4. Queued files are referenced by path and checked before sending (`mtime` and byte size). If a queued file was modified or deleted on disk while waiting, Nectarlink stops that item with a clear reason rather than sending unexpected content, and lets you retry or remove it.+4. Queued files are referenced by path and checked before sending (`mtime` and byte size). If a queued file was modified or deleted on disk while waiting, NectarLink stops that item with a clear reason rather than sending unexpected content, and lets you retry or remove it.5. **Automatic Expiry**: To prevent stale actions from running days later, queued items expire by type:- Continuity Camera requests: **2 minutes**- Links, clipboard items, and task alerts: **24 hours**@@ -72,7 +72,7 @@ You can browse your phone's internal storage or selected folders directly inside1. On your PC, open **Settings › Files & Sync** and turn on **Your PC in your pocket**, and make sure **File Explorer integration** (`storage`) is enabled for your phone in **Settings › Devices**.2. If you want to browse PC files while away from home over mobile data (**Connect over mobile data**), also turn on **Remote PC file access** (`remote_files`) for that phone in **Settings › Devices**.-3. On your phone, tap **PC files** on the Home screen to browse your PC's shared folders (`Downloads`, `Documents`, `Desktop`, `Pictures`, and `Nectarlink Shared`), download files to your phone on demand, or upload files from your phone to a PC folder.+3. On your phone, tap **PC files** on the Home screen to browse your PC's shared folders (`Downloads`, `Documents`, `Desktop`, `Pictures`, and `NectarLink Shared`), download files to your phone on demand, or upload files from your phone to a PC folder.### Automatic Folder Sync@@ -81,15 +81,15 @@ To keep a phone folder (such as `DCIM/Camera` or a notes directory) synchronized1. On your PC, open **Settings › Files & Sync** and scroll to the **Synced folders** card.2. Click **Add DCIM to Pictures** (or configure a custom phone folder and PC folder pair) and choose between:- **One-way (phone to PC)**: Mirrors new and updated files from the phone folder (and subfolders up to 3 levels deep) into the PC folder without pushing PC changes back to the phone.- - **Two-way sync**: Synchronizes additions and updates in both directions. If the same file is modified on both devices between syncs, Nectarlink preserves both versions by saving a conflict copy rather than overwriting your work.+ - **Two-way sync**: Synchronizes additions and updates in both directions. If the same file is modified on both devices between syncs, NectarLink preserves both versions by saving a conflict copy rather than overwriting your work.3. Every synced file streams to a temporary `.nectarlink.part` file and verifies its byte length and **BLAKE3** hash before replacing the destination file. Click **Sync now** to run all enabled rules immediately, or toggle individual rules on and off.### LocalSend Compatibility-Nectarlink includes a built-in LocalSend v2.1 client and server so you can exchange files with any nearby phone, tablet, Mac, Linux machine, or Windows PC running the LocalSend app without pairing:+NectarLink includes a built-in LocalSend v2.1 client and server so you can exchange files with any nearby phone, tablet, Mac, Linux machine, or Windows PC running the LocalSend app without pairing:1. Turn on **LocalSend on local network** in **Settings › Files & Sync** on your PC or **Settings › Features & Data › LocalSend** on your phone.-2. Nearby LocalSend devices on the same Wi-Fi network (UDP multicast `224.0.0.167:53317` and TCP port `53317`) appear automatically in Nectarlink's LocalSend list, and your device appears in theirs.+2. Nearby LocalSend devices on the same Wi-Fi network (UDP multicast `224.0.0.167:53317` and TCP port `53317`) appear automatically in NectarLink's LocalSend list, and your device appears in theirs.3. Because LocalSend is an unauthenticated LAN protocol, **every incoming LocalSend transfer requires your explicit approval** (`Accept` or `Decline`) before a single byte is written to disk.## What the Options Do@@ -104,11 +104,11 @@ Nectarlink includes a built-in LocalSend v2.1 client and server so you can excha## Data and Privacy- **Where data travels**: All transfers between paired devices use end-to-end encrypted QUIC streams. LocalSend transfers use HTTPS on your local Wi-Fi network.-- **Path sandboxing**: Both Nectarlink's paired storage provider and the LocalSend receiver strictly sanitize all file paths and filenames, rejecting `..` parent traversal, drive prefixes, reserved Windows device names (`CON`, `NUL`, `COM1`), and symlink escapes outside the shared root.+- **Path sandboxing**: Both NectarLink's paired storage provider and the LocalSend receiver strictly sanitize all file paths and filenames, rejecting `..` parent traversal, drive prefixes, reserved Windows device names (`CON`, `NUL`, `COM1`), and symlink escapes outside the shared root.- **Where data stays**: Received files stay in `Downloads\Nectarlink` on Windows and `Download/Nectarlink` on Android. Clearing **Transfer history** or **Timeline** only removes the log entries; your downloaded files on disk are never touched.## Limits-- **Windows Share Sheet Target (`windows.shareTarget`)**: Sending files via drag-and-drop, File Explorer's right-click **Send to** menu, the Explorer context menu, the `Shelf`, and `nectarlink --share` works on all standard Windows installs. Appearances inside the system-wide Windows 11 `Win+Share` popup sheet require Nectarlink's sparse package manifest to be registered with a trusted code-signing certificate or Windows Developer Mode enabled.+- **Windows Share Sheet Target (`windows.shareTarget`)**: Sending files via drag-and-drop, File Explorer's right-click **Send to** menu, the Explorer context menu, the `Shelf`, and `nectarlink --share` works on all standard Windows installs. Appearances inside the system-wide Windows 11 `Win+Share` popup sheet require NectarLink's sparse package manifest to be registered with a trusted code-signing certificate or Windows Developer Mode enabled.- **Queue Bounds**: The offline `Waiting to send` queue holds up to **200 items** or **10 GiB** of pending files per device. Live interactive features (screen mirroring, webcam, remote input, and ringing a device) are never queued because they only make sense while the device is online.- **Folder Sync Depth**: Recursive folder sync traverses up to 3 levels of subdirectories inside each configured folder pair.diff --git a/docs/guide/getting-started.md b/docs/guide/getting-started.mdindex 2467b06..ccb30b4 100644--- a/docs/guide/getting-started.md+++ b/docs/guide/getting-started.md@@ -1,6 +1,6 @@# Getting Started-This guide walks you through installing Nectarlink on Windows 11 and Android, completing the first-run setup walkthrough, pairing your devices, and choosing the Android power level that fits how you work.+This guide walks you through installing NectarLink on Windows 11 and Android, completing the first-run setup walkthrough, pairing your devices, and choosing the Android power level that fits how you work.## System Requirements@@ -10,29 +10,29 @@ This guide walks you through installing Nectarlink on Windows 11 and Android, co| **Android Phone or Tablet** | Android 8.0 (API 26) or newer | Android 10+ required for internal audio capture during mirroring; Android 11+ required for on-device Wireless Debugging (`Elevated`) and `app window` streaming; Android 12+ required for `Elevated` in-call mute/hold/speaker controls. || **Network** | Shared Wi-Fi / LAN, USB cable, or **Connect over mobile data** | By default, all device-to-device traffic travels directly over your local network or a USB data cable without leaving your LAN (installed copies only contact GitHub Releases over HTTPS to check for app updates; see [Privacy and Security](privacy-and-security.md)). |-## Installing Nectarlink+## Installing NectarLink### On Windows 111. Download the latest Windows installer (`Nectarlink-<version>-x64-setup.exe`) from the project's GitHub Releases page.2. Run the installer. The installer isn't code-signed yet, so Windows SmartScreen may show **Windows protected your PC**: choose **More info**, then **Run anyway**.-3. Click **Install** and allow the administrator prompt. Setup installs Nectarlink, registers the required Windows Firewall rule for local QUIC discovery and connections, adds Start Menu and desktop shortcuts, and sets Nectarlink to start in the system tray when you sign in (turn this off with **Start with Windows** in **Settings › General**). **What this installs** on the first screen lists everything it adds.-4. The last screen shows a QR code for the Android app's download page. Scan it with your phone's camera, then click **Open Nectarlink**.+3. Click **Install** and allow the administrator prompt. Setup installs NectarLink, registers the required Windows Firewall rule for local QUIC discovery and connections, adds Start Menu and desktop shortcuts, and sets NectarLink to start in the system tray when you sign in (turn this off with **Start with Windows** in **Settings › General**). **What this installs** on the first screen lists everything it adds.+4. The last screen shows a QR code for the Android app's download page. Scan it with your phone's camera, then click **Open NectarLink**.### On Android1. Download `Nectarlink-<version>-android.apk` from the GitHub Releases page (or scan the QR code shown when Windows setup finishes, or in the PC walkthrough).-2. Open the downloaded APK and allow installation if Android prompts you. Because Nectarlink supports full SMS/MMS messaging, call logs, and optional `All files access` for mounting phone storage in File Explorer (permissions that Google Play restricts), the full app is distributed directly as a signed APK with built-in SHA-256 verified updates.-3. Open **Nectarlink** on your phone.+2. Open the downloaded APK and allow installation if Android prompts you. Because NectarLink supports full SMS/MMS messaging, call logs, and optional `All files access` for mounting phone storage in File Explorer (permissions that Google Play restricts), the full app is distributed directly as a signed APK with built-in SHA-256 verified updates.+3. Open **NectarLink** on your phone.### Uninstalling-- **Windows:** open **Settings › Apps › Installed apps**, choose **Nectarlink**, then **Uninstall**. This removes the app, its firewall rule, update task, shortcuts and Share sheet entry, and deletes its settings and pairings on this PC. Files you received and voice recordings stay where they were saved.+- **Windows:** open **Settings › Apps › Installed apps**, choose **NectarLink**, then **Uninstall**. This removes the app, its firewall rule, update task, shortcuts and Share sheet entry, and deletes its settings and pairings on this PC. Files you received and voice recordings stay where they were saved.- **Android:** uninstall it like any other app.## First-Run Setup Walkthrough-When you open Nectarlink for the first time on a new installation, a guided walkthrough sets up your device in a few short steps. You can go back or skip any optional step, and if you close the app midway, it resumes where you left off. You can also reopen the walkthrough at any time from **Settings › Connection & About** on Windows or **Settings › Features & Data › About** on Android.+When you open NectarLink for the first time on a new installation, a guided walkthrough sets up your device in a few short steps. You can go back or skip any optional step, and if you close the app midway, it resumes where you left off. You can also reopen the walkthrough at any time from **Settings › Connection & About** on Windows or **Settings › Features & Data › About** on Android.### PC Walkthrough Steps@@ -40,8 +40,8 @@ When you open Nectarlink for the first time on a new installation, a guided walk<img src="images/walkthrough-pc.png" alt="First-run setup walkthrough on Windows" width="760"></p>-1. **Welcome**: Introduces Nectarlink and how your phone and PC work together.-2. **Privacy Promise**: Summarizes Nectarlink's local-first design: direct connections on your network, end-to-end encryption with device keys, and no user account or cloud server.+1. **Welcome**: Introduces NectarLink and how your phone and PC work together.+2. **Privacy Promise**: Summarizes NectarLink's local-first design: direct connections on your network, end-to-end encryption with device keys, and no user account or cloud server.3. **Install the Phone App**: Shows a scannable QR code linking directly to the Android APK if you do not have it installed yet.4. **Pair**: Displays your PC's live pairing QR code and listens for nearby phones or USB connections.5. **Choose What to Share**: Lets you review the main per-device feature toggles (Notifications, Messages, Calls, Clipboard, Files, Photos, Screen mirroring, Webcam) before your first session begins.@@ -61,22 +61,22 @@ When you open Nectarlink for the first time on a new installation, a guided walk1. **Welcome**: Introduces the companion app.2. **Permissions**: Requests only the permissions you want to use, one at a time, with a plain explanation of why each is needed:- - **Notifications**: Lets Nectarlink mirror phone notifications to your PC and run inline replies or actions.+ - **Notifications**: Lets NectarLink mirror phone notifications to your PC and run inline replies or actions.- **SMS and MMS**: Lets you read conversations and send texts from your PC.- **Calls and Call Log**: Shows caller ID, recent calls, and call controls on your PC.- **Contacts**: Matches phone numbers to names and photos in Calls and Messages on your PC.- **Photos and Videos**: Displays your camera roll and new screenshots on your PC.- - **Stay Reachable in the Background**: Exempts Nectarlink from Android's aggressive background battery killer so your PC can always reach your phone.+ - **Stay Reachable in the Background**: Exempts NectarLink from Android's aggressive background battery killer so your PC can always reach your phone.- **Local Network**: Allows discovery and direct QUIC connections to your PC.3. **Pair**: Scans the QR code shown on your PC or connects using a 6-digit nearby code.4. **Choose a Power Level**: Explains `Standard`, `Assist`, and `Elevated` so you can pick the level of integration you prefer.5. **Done**: Takes you to the Home screen and links to the in-app **Features Guide**.-> **Note on Android 13 and newer ("Restricted settings")**: When you install an APK outside an app store on Android 13 or newer, Android initially grays out the **Notification access** and **Accessibility** switches as a security precaution. If a switch is grayed out, tap **App info** inside Nectarlink's prompt (or open Android's **Settings › Apps › Nectarlink**), tap the three-dot menu in the top-right corner, tap **Allow restricted settings**, verify with your screen lock, and return to Nectarlink.+> **Note on Android 13 and newer ("Restricted settings")**: When you install an APK outside an app store on Android 13 or newer, Android initially grays out the **Notification access** and **Accessibility** switches as a security precaution. If a switch is grayed out, tap **App info** inside NectarLink's prompt (or open Android's **Settings › Apps › NectarLink**), tap the three-dot menu in the top-right corner, tap **Allow restricted settings**, verify with your screen lock, and return to NectarLink.## Pairing Your Phone and PC-Nectarlink supports three ways to `pair` your phone and PC. All three methods establish the same mutual Ed25519 cryptographic trust and end-to-end encrypted QUIC session.+NectarLink supports three ways to `pair` your phone and PC. All three methods establish the same mutual Ed25519 cryptographic trust and end-to-end encrypted QUIC session.<p align="center"><img src="images/pairing.png" alt="Pairing a phone by scanning the QR code shown on the PC" width="760">@@ -84,40 +84,40 @@ Nectarlink supports three ways to `pair` your phone and PC. All three methods es### Method 1: Scan the QR Code (Fastest on Wi-Fi)-1. On your PC, open Nectarlink. If no phone is paired yet, the pairing screen opens automatically. Otherwise, go to **Settings › Devices** and click **Pair a new device**.-2. On your phone, open Nectarlink and tap **Scan code** (or point your phone's built-in camera app at the QR code on the PC screen).+1. On your PC, open NectarLink. If no phone is paired yet, the pairing screen opens automatically. Otherwise, go to **Settings › Devices** and click **Pair a new device**.+2. On your phone, open NectarLink and tap **Scan code** (or point your phone's built-in camera app at the QR code on the PC screen).3. The QR code contains your PC's public key, local IP addresses, and a one-time 128-bit cryptographic secret (`s`) that expires after 5 minutes. Both devices verify the HMAC-SHA256 proof and complete pairing immediately.### Method 2: 6-Digit Nearby Code (No Camera Needed)1. Make sure both your phone and PC are on the same Wi-Fi or local network.-2. Open the pairing screen in Nectarlink on your PC.+2. Open the pairing screen in NectarLink on your PC.3. On your phone, tap **Pair nearby instead** and select your PC's name from the discovered list.4. Both screens display a 6-digit verification code derived via HMAC-SHA256 from both devices' committed random nonces and Ed25519 public keys over the TLS 1.3 pairing session.5. Verify that the 6 digits match on both screens, then click **Codes match** on the PC and tap **Codes match** on the phone. If the numbers do not match, tap **They don't match** to abort the connection.### Method 3: Plug in a USB Cable (Auto-Pair)-If you have USB debugging (`adb`) enabled on your phone, Nectarlink detects the phone as soon as you plug it into your PC with a USB cable.+If you have USB debugging (`adb`) enabled on your phone, NectarLink detects the phone as soon as you plug it into your PC with a USB cable.<p align="center"><img src="images/usb-autopair.png" alt="USB auto-pair confirmation with 6-digit verification code on PC" width="760"></p>1. Connect your phone to your PC with a USB data cable and approve the Android **Allow USB debugging** prompt on your phone if asked.-2. Nectarlink sets up a local loopback tunnel over USB and automatically opens the 6-digit confirmation prompt on both the PC and the phone.+2. NectarLink sets up a local loopback tunnel over USB and automatically opens the 6-digit confirmation prompt on both the PC and the phone.3. Confirm that the 6-digit code matches on both screens and accept on both devices.-4. Once paired, Nectarlink uses the high-speed USB connection (`On USB`) whenever the cable is plugged in and switches to Wi-Fi automatically when you unplug it.+4. Once paired, NectarLink uses the high-speed USB connection (`On USB`) whenever the cable is plugged in and switches to Wi-Fi automatically when you unplug it.## Choosing an Android Power Level-Android groups app capabilities into tiers of system access. Nectarlink is designed so that everyday features work out of the box at the `Standard` level, while power users can opt into `Assist` or `Elevated` without rooting their phone.+Android groups app capabilities into tiers of system access. NectarLink is designed so that everyday features work out of the box at the `Standard` level, while power users can opt into `Assist` or `Elevated` without rooting their phone.### Comparison of Power Levels| Feature or Capability | `Standard` (Default) | `Assist` (Accessibility) | `Elevated` (Wireless Debugging / ADB) || :--- | :--- | :--- | :--- |-| **Setup required** | Ordinary Android permissions | Turn on Nectarlink in Android Accessibility | One-time Wireless Debugging pairing on phone (or USB `adb`) |+| **Setup required** | Ordinary Android permissions | Turn on NectarLink in Android Accessibility | One-time Wireless Debugging pairing on phone (or USB `adb`) || **Notifications, inline reply, actions, dismiss sync** | Yes | Yes | Yes || **Sensitive notification text & OTPs on Android 15+** | Hidden by Android OS | Hidden by Android OS | **Enabled** (`RECEIVE_SENSITIVE_NOTIFICATIONS`) || **SMS, MMS, Unified Conversations, Calls, Contacts, Photos** | Yes | Yes | Yes |@@ -133,26 +133,26 @@ Android groups app capabilities into tiers of system access. Nectarlink is desig### Trade-Offs to Know-- **`Standard`** requires the least setup and grants Nectarlink zero input-injection or shell capabilities. Its only limits come from Android OS rules: background apps cannot read the clipboard automatically, Android shows a confirmation dialog each time screen mirroring starts, and mirroring is view-only.-- **`Assist`** takes about 30 seconds to turn on in **Android Settings › Accessibility › Nectarlink: control from your PC**. It lets your PC mouse and keyboard tap, swipe, and type on the mirrored screen. Because Android's Accessibility gesture API dispatches completed strokes rather than live pointer streams, dragging (such as long-press drag-and-drop) is discrete rather than continuous.-- **`Elevated`** runs a small, open-source companion process (`app.nectarlink.android.elevated.InputServer`) inside Android's `shell` user (`UID 2000`) via Android's built-in Wireless Debugging. It gives Nectarlink the same capabilities as desktop `scrcpy`, plus background clipboard sync and `app window` streaming, without needing a PC cable or root. Only Nectarlink's own app process (presenting the one-time 192-bit session token over loopback) can talk to the helper.+- **`Standard`** requires the least setup and grants NectarLink zero input-injection or shell capabilities. Its only limits come from Android OS rules: background apps cannot read the clipboard automatically, Android shows a confirmation dialog each time screen mirroring starts, and mirroring is view-only.+- **`Assist`** takes about 30 seconds to turn on in **Android Settings › Accessibility › NectarLink: control from your PC**. It lets your PC mouse and keyboard tap, swipe, and type on the mirrored screen. Because Android's Accessibility gesture API dispatches completed strokes rather than live pointer streams, dragging (such as long-press drag-and-drop) is discrete rather than continuous.+- **`Elevated`** runs a small, open-source companion process (`app.nectarlink.android.elevated.InputServer`) inside Android's `shell` user (`UID 2000`) via Android's built-in Wireless Debugging. It gives NectarLink the same capabilities as desktop `scrcpy`, plus background clipboard sync and `app window` streaming, without needing a PC cable or root. Only NectarLink's own app process (presenting the one-time 192-bit session token over loopback) can talk to the helper.### How to Enable `Elevated` on Your Phone (Wireless Debugging)You can set up `Elevated` directly on your phone in about two minutes on Android 11 or newer:<p align="center">- <img src="images/wireless-debugging.png" alt="Setting up Elevated mode via Wireless Debugging in Nectarlink for Android" width="760">+ <img src="images/wireless-debugging.png" alt="Setting up Elevated mode via Wireless Debugging in NectarLink for Android" width="760"></p>-1. Open **Nectarlink** on your phone and go to **Settings › Permissions › Control from your PC**.+1. Open **NectarLink** on your phone and go to **Settings › Permissions › Control from your PC**.2. Next to **Real touch and keys (Wireless debugging)**, tap **Set up**.3. If **Developer options** is not enabled on your phone yet, open Android's **Settings › About phone** and tap **Build number** 7 times until Android confirms you are a developer.-4. Tap **Open Developer options** in Nectarlink. Scroll down to **Wireless debugging**, turn the switch **On**, and tap the words **Wireless debugging** to open its sub-screen.+4. Tap **Open Developer options** in NectarLink. Scroll down to **Wireless debugging**, turn the switch **On**, and tap the words **Wireless debugging** to open its sub-screen.5. Tap **Pair device with pairing code**. A dialog appears showing a 6-digit Wi-Fi pairing code.-6. Do not close that dialog. Pull down the notification shade at the top of your screen, find Nectarlink's **Pair Nectarlink with Wireless debugging** notification, tap **Enter code**, type the 6-digit code, and send it.-7. Nectarlink pairs with Wireless Debugging and starts the `Elevated` helper immediately. After this one-time pairing, Nectarlink automatically restarts `Elevated` in the background whenever you reconnect to Wi-Fi or reboot your phone.+6. Do not close that dialog. Pull down the notification shade at the top of your screen, find NectarLink's **Pair NectarLink with Wireless debugging** notification, tap **Enter code**, type the 6-digit code, and send it.+7. NectarLink pairs with Wireless Debugging and starts the `Elevated` helper immediately. After this one-time pairing, NectarLink automatically restarts `Elevated` in the background whenever you reconnect to Wi-Fi or reboot your phone.### Alternative: Automatic `Elevated` via USB Cable-If you connect your phone to your PC with a USB cable and have **USB debugging** enabled in Developer options, Nectarlink on your PC can start the `Elevated` helper on your phone over `adb` automatically without needing the Wi-Fi pairing code step.+If you connect your phone to your PC with a USB cable and have **USB debugging** enabled in Developer options, NectarLink on your PC can start the `Elevated` helper on your phone over `adb` automatically without needing the Wi-Fi pairing code step.diff --git a/docs/guide/input-and-control.md b/docs/guide/input-and-control.mdindex 1ba0d1f..31d2f19 100644--- a/docs/guide/input-and-control.md+++ b/docs/guide/input-and-control.md@@ -1,6 +1,6 @@# Input and Control-Nectarlink lets you control your PC from your phone and control your phone from your PC. Use your phone as a multi-touch trackpad, gyroscope air mouse, remote keyboard, voice dictation mic, presentation clicker with a laser pointer, `Deck` macro pad, or bedside `Desk clock` display. Going the other way, type on your phone from your PC keyboard without screen mirroring, move your PC mouse cursor across the screen edge onto your phone (**Flow**), toggle phone system settings from PC Home, or lock, sleep, and wake your PC remotely.+NectarLink lets you control your PC from your phone and control your phone from your PC. Use your phone as a multi-touch trackpad, gyroscope air mouse, remote keyboard, voice dictation mic, presentation clicker with a laser pointer, `Deck` macro pad, or bedside `Desk clock` display. Going the other way, type on your phone from your PC keyboard without screen mirroring, move your PC mouse cursor across the screen edge onto your phone (**Flow**), toggle phone system settings from PC Home, or lock, sleep, and wake your PC remotely.<p align="center"><img src="images/type-on-phone.png" alt="Typing on the phone from the PC keyboard and controlling phone settings on Home" width="760">@@ -33,13 +33,13 @@ Tap **Control PC** on the Android Home screen. The first time you open it, click#### Air Mouse Mode-- Hold your thumb on the center pad and tilt your phone in the air. Nectarlink reads your phone's gyroscope with hand-tremor filtering to move the PC cursor accurately where you point.-- Tap the pad while holding to left-click, and release the pad to park the cursor. (If your phone does not have a gyroscope sensor, Nectarlink lets you know and suggests Touchpad mode.)+- Hold your thumb on the center pad and tilt your phone in the air. NectarLink reads your phone's gyroscope with hand-tremor filtering to move the PC cursor accurately where you point.+- Tap the pad while holding to left-click, and release the pad to park the cursor. (If your phone does not have a gyroscope sensor, NectarLink lets you know and suggests Touchpad mode.)#### Keyboard and Voice Dictation- **Remote Keyboard**: Tap **Keyboard** to open your phone's soft keyboard and type straight into the focused window on your PC. Above the keyboard sits a scrollable bar of PC modifier and special keys: **`Ctrl`**, **`Alt`**, **`Shift`**, **`Win`**, **`Esc`**, **`Tab`**, **Arrow keys**, **`Home`**, **`End`**, **`PgUp`**, **`PgDn`**, **`Del`**, **`Copy`**, and **`Paste`**. Tap a modifier key (`Ctrl`, `Alt`, `Shift`, `Win`) to latch it for the next keystroke.-- **Voice Dictation**: Tap or hold **Dictate** and speak. Nectarlink uses your phone's speech recognizer (on-device recognition where available) to stream live partial transcripts and type the finished sentence directly into the active text field on your PC.+- **Voice Dictation**: Tap or hold **Dictate** and speak. NectarLink uses your phone's speech recognizer (on-device recognition where available) to stream live partial transcripts and type the finished sentence directly into the active text field on your PC.#### Presentation Remote and Laser Pointer@@ -91,7 +91,7 @@ When your phone is resting on a charger or desk stand, tap **Desk clock** on the- **Lock or Sleep PC**: Tap **Lock PC** or **Sleep** on your phone (or on the Android **PC quick actions** widget) to lock your Windows session or put the PC to sleep when you walk away.- **Wake PC (Wake-on-LAN)**: When your PC is asleep or powered off, tap **Wake** on your phone (or on the Android home-screen widget).- On the local network, your phone sends Wake-on-LAN UDP packets to every MAC and broadcast address stored for your PC during prior connections.- - If you have another Nectarlink device online on your home LAN while you are on mobile data (**Connect over mobile data**), Nectarlink can also relay the wake request through your online home device.+ - If you have another NectarLink device online on your home LAN while you are on mobile data (**Connect over mobile data**), NectarLink can also relay the wake request through your online home device.- Check **Settings › Connection & About › Wake from your phone** on your PC to verify whether your Windows network adapter has Wake on LAN enabled in Device Manager.## What the Options Dodiff --git a/docs/guide/known-limitations.md b/docs/guide/known-limitations.mdindex 078d59c..99a3837 100644--- a/docs/guide/known-limitations.md+++ b/docs/guide/known-limitations.md@@ -1,18 +1,18 @@# 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.+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`](../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. |+| **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`](../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. |+| **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`) & Widgets board (`Win+W`)** | 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 and `Win+W` Widgets board requires package identity. | Windows 11 requires `windows.shareTarget` and `com.microsoft.windows.widgets` COM extensions 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 enable Windows Developer Mode if registering the sparse package locally. || **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`. |+| **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. |@@ -20,19 +20,19 @@ Nectarlink aims to be completely transparent about what works out of the box, wh### 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.+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.+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:+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 `Standard` or `Assist`, 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 `Elevated` via 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+'s `EXTRA_IS_SENSITIVE` flag to never copy passwords.+- If you stay at `Standard` or `Assist`, 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 `Elevated` via 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+'s `EXTRA_IS_SENSITIVE` flag to never copy passwords.### 3. Windows Sparse Package Identity for `Win+Share` and `Win+W` Widgets-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.+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 two shell extension points (`windows.shareTarget` in the system `Win+Share` dialog and `com.microsoft.windows.widgets` in the `Win+W` Widgets board) 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 complete implementation and `AppxManifest.xml` for both extensions, and documents this requirement honestly so users on standard unsigned builds know why `Send to` and the `Shelf` are the primary sharing entry points.+However, Windows 11 restricts two shell extension points (`windows.shareTarget` in the system `Win+Share` dialog and `com.microsoft.windows.widgets` in the `Win+W` Widgets board) 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 complete implementation and `AppxManifest.xml` for both extensions, and documents this requirement honestly so users on standard unsigned builds know why `Send to` and the `Shelf` are the primary sharing entry points.diff --git a/docs/guide/messages.md b/docs/guide/messages.mdindex a8e40b8..3dada5e 100644--- a/docs/guide/messages.md+++ b/docs/guide/messages.md@@ -22,7 +22,7 @@ The **Messages** page on your PC brings together your phone's SMS and MMS text t1. Click **Messages** in the left navigation bar on your PC.2. The left pane lists your conversations ordered by most recent activity:- **SMS and MMS threads** are synced directly from your phone's system telephony database, including group MMS conversations and inline picture attachments.- - **Unified Conversations** capture incoming messages from chat apps that use Android's `MessagingStyle` notification format (such as Google Messages RCS, WhatsApp, Telegram, Signal, Discord, and Slack). Each thread badge shows which app it belongs to. Nectarlink automatically deduplicates SMS notifications against the system SMS provider so texts never appear twice.+ - **Unified Conversations** capture incoming messages from chat apps that use Android's `MessagingStyle` notification format (such as Google Messages RCS, WhatsApp, Telegram, Signal, Discord, and Slack). Each thread badge shows which app it belongs to. NectarLink automatically deduplicates SMS notifications against the system SMS provider so texts never appear twice.3. When chat apps are present, chips at the top of the list filter conversations by app. The search box filters threads by contact name, phone number, app, or message text.### Sending Texts and Replying to Chat Apps@@ -48,12 +48,12 @@ You can attach images to any SMS/MMS conversation in three ways:### Starting a New Conversation1. Click the **New message** button at the top of the conversation list.-2. Type a contact's name or phone number in the **To:** field. Nectarlink searches your phone's synced contacts as you type, showing matching names, phone numbers, and contact avatars.+2. Type a contact's name or phone number in the **To:** field. NectarLink searches your phone's synced contacts as you type, showing matching names, phone numbers, and contact avatars.3. Click a contact (or finish typing a phone number), write your message in the composer, and press **Enter**.### One-Time Codes-When an SMS or chat message contains a verification code, Nectarlink displays a **Copy code** button right inside the message bubble (and copies it automatically if **Copy one-time codes** is turned on in **Settings › General**).+When an SMS or chat message contains a verification code, NectarLink displays a **Copy code** button right inside the message bubble (and copies it automatically if **Copy one-time codes** is turned on in **Settings › General**).## What the Options Dodiff --git a/docs/guide/mirroring.md b/docs/guide/mirroring.mdindex 0ed1ecc..68ad67c 100644--- a/docs/guide/mirroring.md+++ b/docs/guide/mirroring.md@@ -1,6 +1,6 @@# Mirroring and App Windows-Nectarlink streams your phone's screen to your Windows 11 PC in a dedicated window at up to 60 frames per second with hardware video encoding (H.264, H.265, or AV1) and live audio forwarding. Depending on your Android power level, you can view your screen, control it with your PC mouse and keyboard, open individual Android apps in their own desktop windows (`app window`), launch a full desktop layout (DeX mode), or reverse-mirror your PC's screen to your phone.+NectarLink streams your phone's screen to your Windows 11 PC in a dedicated window at up to 60 frames per second with hardware video encoding (H.264, H.265, or AV1) and live audio forwarding. Depending on your Android power level, you can view your screen, control it with your PC mouse and keyboard, open individual Android apps in their own desktop windows (`app window`), launch a full desktop layout (DeX mode), or reverse-mirror your PC's screen to your phone.<p align="center"><img src="images/mirroring-window.png" alt="Phone screen mirrored in a window on Windows 11" width="760">@@ -10,7 +10,7 @@ Nectarlink streams your phone's screen to your Windows 11 PC in a dedicated wind| Feature | Requirements || :--- | :--- |-| **View phone screen and audio on PC (`mirror`)** | `Standard` power level. **Screen mirroring** toggle enabled in PC **Settings › Devices** (on by default). At `Standard` or `Assist`, Android displays a system **Start recording or casting** prompt on your phone each time mirroring starts. With `Elevated`, Nectarlink grants `PROJECT_MEDIA` automatically so mirroring starts without a phone prompt. |+| **View phone screen and audio on PC (`mirror`)** | `Standard` power level. **Screen mirroring** toggle enabled in PC **Settings › Devices** (on by default). At `Standard` or `Assist`, Android displays a system **Start recording or casting** prompt on your phone each time mirroring starts. With `Elevated`, NectarLink grants `PROJECT_MEDIA` automatically so mirroring starts without a phone prompt. || **Tap, swipe, scroll, and type from PC** | `Assist` (Android Accessibility Service enabled in **Settings › Permissions › Control from your PC**) or `Elevated` (Wireless Debugging). `Elevated` adds real-time touch dragging, UHID physical keyboard layouts, XInput gamepad passthrough, and stylus pressure/tilt. || **Turn off physical phone screen while mirroring** | `Elevated` power level. || **Phone apps in individual PC windows (`app window`)** | `Elevated` power level on Android 11 or newer. |@@ -22,7 +22,7 @@ Nectarlink streams your phone's screen to your Windows 11 PC in a dedicated wind1. On your PC, click **Mirror screen** on the **Home** screen (or press `Ctrl+Alt+Space` and choose **Mirror phone screen**). You can also start mirroring from your phone by tapping **Mirror to PC** on the Android Home screen.2. If your phone is at `Standard` or `Assist`, tap the notification on your phone and approve Android's screen-sharing dialog. If your phone is at `Elevated`, the `mirror` window opens immediately on your PC without a prompt on the phone.-3. Your phone's screen streams at up to 1920 pixels on the long edge and 60 fps. Nectarlink automatically negotiates the best hardware codec supported by both devices (**AV1**, **H.265/HEVC**, or **H.264/AVC**) and adapts when you rotate your phone between portrait and landscape.+3. Your phone's screen streams at up to 1920 pixels on the long edge and 60 fps. NectarLink automatically negotiates the best hardware codec supported by both devices (**AV1**, **H.265/HEVC**, or **H.264/AVC**) and adapts when you rotate your phone between portrait and landscape.4. On Android 10 and newer, your phone's media and game audio plays through your PC's speakers automatically during mirroring. Click the speaker icon in the `mirror` window toolbar at any time to mute or unmute the phone's audio on your PC.### Controlling Your Phone from the Mirror Window@@ -33,7 +33,7 @@ Once `Assist` or `Elevated` is enabled on your phone:- **Mouse wheel / two-finger trackpad scroll**: Scrolls vertically or horizontally under the cursor.- **Right-click**: Triggers Android **Back**.- **Middle-click**: Triggers Android **Home**.-- **Keyboard typing and shortcuts**: Type directly into any focused Android field. At `Elevated` (when `/dev/uhid` is permitted by your phone's kernel/SELinux policy), Nectarlink registers a virtual physical HID keyboard and gamepad so non-US keyboard layouts, key combinations, and connected Xbox/XInput controllers work natively inside Android apps and games.+- **Keyboard typing and shortcuts**: Type directly into any focused Android field. At `Elevated` (when `/dev/uhid` is permitted by your phone's kernel/SELinux policy), NectarLink registers a virtual physical HID keyboard and gamepad so non-US keyboard layouts, key combinations, and connected Xbox/XInput controllers work natively inside Android apps and games.- **Clipboard and file drop inside the mirror**: Pressing `Ctrl+C` or `Ctrl+V` while the `mirror` window is focused syncs your clipboard, and dragging files from Windows File Explorer onto the `mirror` window sends them straight to `Download/Nectarlink` on your phone.- **Stylus / Pen**: Windows Ink pen pressure, tilt, and barrel buttons are forwarded to the phone screen at `Elevated`.@@ -65,9 +65,9 @@ With `Elevated` on Android 11 or newer, you can run individual phone apps in sep<img src="images/apps-page.png" alt="The Apps page on the PC listing the phone's apps" width="760"></p>-3. Click any app. Nectarlink creates an isolated virtual display on your phone and opens that app on your PC in its own `app window` with its own Windows taskbar icon.+3. Click any app. NectarLink creates an isolated virtual display on your phone and opens that app on your PC in its own `app window` with its own Windows taskbar icon.4. The app runs independently beside whatever is shown on your phone's physical screen, and typing from your PC does not pop up the on-screen soft keyboard on your phone.-5. Resize the `app window` on your PC and the Android app dynamically re-lays out to match the new aspect ratio. Nectarlink remembers each app's window size and screen position for the next time you open it. You can open multiple `app window` instances side by side in tabs or separate windows.+5. Resize the `app window` on your PC and the Android app dynamically re-lays out to match the new aspect ratio. NectarLink remembers each app's window size and screen position for the next time you open it. You can open multiple `app window` instances side by side in tabs or separate windows.### Desktop Display Mode (DeX / Desktop Mode)@@ -77,7 +77,7 @@ On phones that support a desktop launcher layout on secondary displays (such asYou can also view (and optionally control) your PC's desktop from your phone:-1. On your phone, open **Nectarlink** and tap **View PC screen** under **Screen, Camera & Input** (or open the **Control PC** screen and switch to the screen view).+1. On your phone, open **NectarLink** and tap **View PC screen** under **Screen, Camera & Input** (or open the **Control PC** screen and switch to the screen view).2. **Explicit PC Consent**: Because a PC screen is sensitive, reverse mirroring is **off by default** (**Share PC screen to phone** in **Settings › Devices**). If it is not already enabled for your phone, your PC displays a modal consent prompt asking whether to **Not now**, **Allow** (for this session only, cleared automatically on disconnect), or **Allow for this device** (enables **Share PC screen to phone** for that phone).3. **Sharing indicator**: Throughout any active reverse-mirroring session, the PC window's title bar shows a live pill (**Sharing screen with `<Phone>`**) with a **Stop** button.4. **Input Gating**: Viewing the PC screen from your phone is read-only unless you have also enabled **Remote mouse, keyboard & Deck** (`remote_input`) for that phone on your PC.@@ -101,5 +101,5 @@ You can also view (and optionally control) your PC's desktop from your phone:## Limits- **`FLAG_SECURE` Protected Content**: Android apps that set the `FLAG_SECURE` window flag (such as banking apps, password managers, and DRM-protected video streaming apps like Netflix) render black inside `Standard` and `Assist` `MediaProjection` streams by Android OS design.-- **Audio Capture Rules and `REMOTE_SUBMIX`**: Standard Android 10+ `AudioPlaybackCapture` captures apps that allow playback capture (`USAGE_MEDIA`, `USAGE_GAME`). Apps that opt out of playback capture in their manifest cannot be captured at `Standard` or `Assist`. At `Elevated`, Nectarlink attempts internal audio capture via `REMOTE_SUBMIX` (`UID 2000`), which works on AOSP/Pixel builds but may be blocked by custom SELinux policies on some OEM ROMs (falling back automatically to standard playback capture).-- **UHID Kernel/SELinux Access**: Virtual physical keyboard (`--uhid-key`) and gamepad (`--uhid-gamepad`) injection at `Elevated` open `/dev/uhid` as `shell` (`UID 2000`). On OEM ROMs whose SELinux policy denies `shell` access to `/dev/uhid`, Nectarlink falls back automatically to standard Android `InputManager` key and motion injection.+- **Audio Capture Rules and `REMOTE_SUBMIX`**: Standard Android 10+ `AudioPlaybackCapture` captures apps that allow playback capture (`USAGE_MEDIA`, `USAGE_GAME`). Apps that opt out of playback capture in their manifest cannot be captured at `Standard` or `Assist`. At `Elevated`, NectarLink attempts internal audio capture via `REMOTE_SUBMIX` (`UID 2000`), which works on AOSP/Pixel builds but may be blocked by custom SELinux policies on some OEM ROMs (falling back automatically to standard playback capture).+- **UHID Kernel/SELinux Access**: Virtual physical keyboard (`--uhid-key`) and gamepad (`--uhid-gamepad`) injection at `Elevated` open `/dev/uhid` as `shell` (`UID 2000`). On OEM ROMs whose SELinux policy denies `shell` access to `/dev/uhid`, NectarLink falls back automatically to standard Android `InputManager` key and motion injection.diff --git a/docs/guide/notifications.md b/docs/guide/notifications.mdindex 08713e1..ff650d9 100644--- a/docs/guide/notifications.md+++ b/docs/guide/notifications.md@@ -1,6 +1,6 @@# Notifications-Nectarlink mirrors your phone's notifications to your Windows 11 PC in real time. You can read alerts, reply inline to messages, trigger notification action buttons, track live delivery or timer progress, copy one-time verification codes with one click, and dismiss notifications on both devices at once.+NectarLink mirrors your phone's notifications to your Windows 11 PC in real time. You can read alerts, reply inline to messages, trigger notification action buttons, track live delivery or timer progress, copy one-time verification codes with one click, and dismiss notifications on both devices at once.<p align="center"><img src="images/notifications-grouped.png" alt="Phone notifications grouped by app on the PC Home screen" width="760">@@ -19,8 +19,8 @@ Nectarlink mirrors your phone's notifications to your Windows 11 PC in real time### Reading, Grouping, and Dismissing Notifications-1. Open **Nectarlink** on your PC and stay on **Home**. Active notifications from your connected phone appear in the **Notifications** card, displaying each app's icon, title, body text, timestamp, and any attached photo or big picture.-2. When an app posts multiple notifications, Nectarlink groups them under a collapsible app header showing the count. Click the header to expand or collapse that app's alerts, or click **Clear group** (`x`) to dismiss all notifications from that app at once.+1. Open **NectarLink** on your PC and stay on **Home**. Active notifications from your connected phone appear in the **Notifications** card, displaying each app's icon, title, body text, timestamp, and any attached photo or big picture.+2. When an app posts multiple notifications, NectarLink groups them under a collapsible app header showing the count. Click the header to expand or collapse that app's alerts, or click **Clear group** (`x`) to dismiss all notifications from that app at once.3. Click the `x` button on any individual notification card (or dismiss the Windows popup) to clear it. Dismissals synchronize both ways: clearing a notification on your PC removes it from your phone's notification shade, and swiping it away on your phone removes it from your PC. After you dismiss a notification or group on the PC, a brief **Undo** bar lets you restore it locally if you clicked by mistake.4. Click a notification card on your PC while `Elevated` is active (on Android 11+) to open that phone app directly on your PC in its own `app window`.@@ -28,7 +28,7 @@ Nectarlink mirrors your phone's notifications to your Windows 11 PC in real time1. When a notification supports direct reply (such as a chat message or email), click **Reply** on the notification card in the app or type directly into the Windows notification popup.2. Type your response and press **Enter** or click **Send**. Your phone sends the reply through the original app's `RemoteInput` handler immediately.-3. Action buttons attached to the notification on your phone (such as **Mark as read**, **Archive**, **Remind me**, or **Snooze**) appear as buttons on both the Windows popup and the card in Nectarlink. Click any action button to run it on the phone.+3. Action buttons attached to the notification on your phone (such as **Mark as read**, **Archive**, **Remind me**, or **Snooze**) appear as buttons on both the Windows popup and the card in NectarLink. Click any action button to run it on the phone.### Live Updates, Progress Bars, and Timers@@ -46,8 +46,8 @@ When an incoming notification or SMS contains a 4-to-8-digit one-time verificati<img src="images/notifications-otp.png" alt="One-time verification code detected with a Copy code button" width="760"></p>-1. Nectarlink extracts the verification code locally on your device and adds a prominent **Copy code (`123456`)** button to both the Windows notification popup and the notification card on Home.-2. If you turn on **Copy one-time codes** in **Settings › General**, Nectarlink copies the verification code to your PC clipboard automatically as soon as it arrives and shows a brief confirmation banner so you can press `Ctrl+V` straight into your browser.+1. NectarLink extracts the verification code locally on your device and adds a prominent **Copy code (`123456`)** button to both the Windows notification popup and the notification card on Home.+2. If you turn on **Copy one-time codes** in **Settings › General**, NectarLink copies the verification code to your PC clipboard automatically as soon as it arrives and shows a brief confirmation banner so you can press `Ctrl+V` straight into your browser.3. One-time verification codes are never written to your clipboard history or `Timeline`, and copying an OTP on your PC never loops it back to the phone.### Viewing Dismissed Notification History@@ -55,7 +55,7 @@ When an incoming notification or SMS contains a 4-to-8-digit one-time verificatiIf you accidentally swipe away an alert on your phone or want to check a notification from earlier in the day:1. In the **Notifications** card on PC Home, switch the filter from **Active** to **History**.-2. Nectarlink displays dismissed notifications from the last 24 hours (up to 300 items), complete with search filtering by app name or text.+2. NectarLink displays dismissed notifications from the last 24 hours (up to 300 items), complete with search filtering by app name or text.3. You can clear the history at any time or turn 24-hour retention off in **Settings › Storage & Privacy › Notification history**.### Forwarding PC Notifications to Your Phone (Optional)@@ -70,13 +70,13 @@ If you step away from your desk and want your PC's alerts (such as calendar remiAll notification settings live in **Settings › Notifications** (and **Settings › General** / **Settings › Storage & Privacy**) on the PC:-- **Follow phone Do not disturb** (`Settings › Notifications`, default: **Off**): When turned on, your PC silences popup toasts whenever your phone is in Do Not Disturb mode. Notifications still arrive quietly in the Nectarlink feed so you can read them when you want.+- **Follow phone Do not disturb** (`Settings › Notifications`, default: **Off**): When turned on, your PC silences popup toasts whenever your phone is in Do Not Disturb mode. Notifications still arrive quietly in the NectarLink feed so you can read them when you want.- **Notification profile on Home**: From the Phone Controls card on PC Home, you can switch your phone's notification profile between **All**, **Priority only** (Do Not Disturb), and **Silent**.- **Forward PC notifications** (`Settings › Notifications`, default: **Off**): Mirrors Windows desktop notifications to your connected phone.- **Quiet hours** (`Settings › Notifications`): Opens Windows **System › Notifications** settings so you can configure automatic Focus / Do Not Disturb schedules on Windows 11.- **Per-app notification rules** (`Settings › Notifications`): Every phone app that has sent at least one notification appears in an alphabetical list with its icon and a three-way selector:- - **Show** (default): Shows a Windows popup toast and lists the alert in the Nectarlink feed.- - **No pop-ups**: Suppresses Windows popup toasts for that app while keeping its notifications visible inside the Nectarlink feed.+ - **Show** (default): Shows a Windows popup toast and lists the alert in the NectarLink feed.+ - **No pop-ups**: Suppresses Windows popup toasts for that app while keeping its notifications visible inside the NectarLink feed.- **Hide**: Completely blocks notifications from that app on your PC.- **Copy one-time codes** (`Settings › General`, default: **Off**): Automatically copies detected verification codes from incoming notifications and SMS messages to the PC clipboard.- **Notification history** (`Settings › Storage & Privacy`, default: **On**): Keeps dismissed phone notifications on the PC for 24 hours (up to 300 alerts). Includes a one-click **Clear** button.@@ -89,6 +89,6 @@ All notification settings live in **Settings › Notifications** (and **Settings## Limits-- **Android 15+ Enhanced Confirmation Mode (`RECEIVE_SENSITIVE_NOTIFICATIONS`)**: Starting in Android 15, the operating system redacts the text of notifications that appear to contain two-factor authentication codes from untrusted notification listeners. To receive sensitive notification text and OTPs on Android 15 and newer, enable the `Elevated` power level once; Nectarlink's shell helper automatically grants `RECEIVE_SENSITIVE_NOTIFICATIONS` to Nectarlink.-- **OEM Background Restrictions**: If your phone manufacturer puts Nectarlink to sleep in the background, notifications may be delayed until you wake the phone screen. Follow the per-OEM steps in [Troubleshooting](troubleshooting.md) to set Nectarlink's battery usage to **Unrestricted**.+- **Android 15+ Enhanced Confirmation Mode (`RECEIVE_SENSITIVE_NOTIFICATIONS`)**: Starting in Android 15, the operating system redacts the text of notifications that appear to contain two-factor authentication codes from untrusted notification listeners. To receive sensitive notification text and OTPs on Android 15 and newer, enable the `Elevated` power level once; NectarLink's shell helper automatically grants `RECEIVE_SENSITIVE_NOTIFICATIONS` to NectarLink.+- **OEM Background Restrictions**: If your phone manufacturer puts NectarLink to sleep in the background, notifications may be delayed until you wake the phone screen. Follow the per-OEM steps in [Troubleshooting](troubleshooting.md) to set NectarLink's battery usage to **Unrestricted**.- **Chat App History**: Notification mirroring captures alerts that arrive while your phone and PC are connected (or recently active in the phone's shade). Full historical message databases for third-party encrypted chat apps (such as Signal or WhatsApp) are sandboxed by Android and cannot be read retroactively.diff --git a/docs/guide/photos.md b/docs/guide/photos.mdindex b0fb3a0..ae18a12 100644--- a/docs/guide/photos.md+++ b/docs/guide/photos.md@@ -21,13 +21,13 @@ The **Photos** page on your PC gives you instant access to your phone's camera r1. Click **Photos** in the left navigation bar on your PC.2. Use the album filter pills at the top (**All**, **Camera**, **Screenshots**, or any custom album from your phone's `MediaStore`) to narrow the grid.-3. Photos are grouped chronologically by day. As you scroll, Nectarlink streams lightweight thumbnails from your phone and caches them locally so scrolling stays responsive even across galleries with 10,000+ photos.+3. Photos are grouped chronologically by day. As you scroll, NectarLink streams lightweight thumbnails from your phone and caches them locally so scrolling stays responsive even across galleries with 10,000+ photos.4. Additionally, the **Home** screen and the slide-out `Shelf` edge panel (`Ctrl+Alt+S`) always show quick cards for your phone's **Latest photo** and **Latest screenshot**.### Viewing Full-Resolution Photos-1. Click any thumbnail in the **Photos** grid to open the full-resolution viewer inside Nectarlink.-2. Nectarlink streams the original, uncompressed image file from your phone on demand.+1. Click any thumbnail in the **Photos** grid to open the full-resolution viewer inside NectarLink.+2. NectarLink streams the original, uncompressed image file from your phone on demand.3. Use the **Left** and **Right** arrow keys on your keyboard to step through your gallery, or press **Escape** to return to the grid.4. From the viewer toolbar, you can:- Click **Copy** (`Ctrl+C`) to copy the full-resolution image onto your Windows clipboard so you can paste it into any document, chat app, or image editor.@@ -40,7 +40,7 @@ You do not need to click Save before using a photo in another Windows program:1. Point at any photo tile on the **Photos** page, on the **Home** screen, or inside the slide-out `Shelf`.2. Click and drag the photo directly onto your Windows Desktop, into a File Explorer folder, or into an open app (such as PowerPoint, Photoshop, Figma, Slack, or your web browser).-3. Nectarlink stages the full-resolution file with its original sanitized filename (for example, `IMG_20261012_091500.jpg`) so the receiving app gets the real file immediately.+3. NectarLink stages the full-resolution file with its original sanitized filename (for example, `IMG_20261012_091500.jpg`) so the receiving app gets the real file immediately.### Selecting and Saving Multiple Photos@@ -62,10 +62,10 @@ Whenever you take a new photo or capture a screenshot on your phone while connec## Data and Privacy-- **On-demand reading**: Nectarlink never bulk-uploads your photo library in the background. Your phone reads photo metadata and thumbnails directly from Android's `MediaStore` only when you open the **Photos** page (or for the single latest photo/screenshot on Home), and full-resolution originals are transferred only when you view, copy, drag, or save a specific photo.+- **On-demand reading**: NectarLink never bulk-uploads your photo library in the background. Your phone reads photo metadata and thumbnails directly from Android's `MediaStore` only when you open the **Photos** page (or for the single latest photo/screenshot on Home), and full-resolution originals are transferred only when you view, copy, drag, or save a specific photo.- **Local cache retention**: Thumbnail previews downloaded to your PC are stored in `%LOCALAPPDATA%\Nectarlink\cache\photos\` and automatically purged after **30 days**. Drag-and-drop staging files in `%LOCALAPPDATA%\Nectarlink\cache\photos\drag\` are cleaned up automatically. Clicking **Clear** next to **Photo thumbnails** in **Settings › Storage & Privacy** wipes all cached thumbnails on your PC without affecting any photos on your phone or any files you saved to `Downloads`.## Limits-- **Android 14+ Partial Photo Access**: If you choose **Select photos** instead of **Allow all** when Android prompts for media access, Android only reveals the specific photos you picked to Nectarlink. Nectarlink displays an inline notice in Android Settings (**Some of your photos and videos aren't available on your PC**) with an **Allow all** button so you can expand access whenever you want.-- **Cloud-Only Backed-Up Photos**: Nectarlink reads photos stored locally on your phone's storage (`MediaStore`). Older photos that have been deleted from your phone's local storage by a cloud backup service (such as Google Photos "Free up space") are not on the device and will not appear unless downloaded back to the phone.+- **Android 14+ Partial Photo Access**: If you choose **Select photos** instead of **Allow all** when Android prompts for media access, Android only reveals the specific photos you picked to NectarLink. NectarLink displays an inline notice in Android Settings (**Some of your photos and videos aren't available on your PC**) with an **Allow all** button so you can expand access whenever you want.+- **Cloud-Only Backed-Up Photos**: NectarLink reads photos stored locally on your phone's storage (`MediaStore`). Older photos that have been deleted from your phone's local storage by a cloud backup service (such as Google Photos "Free up space") are not on the device and will not appear unless downloaded back to the phone.diff --git a/docs/guide/privacy-and-security.md b/docs/guide/privacy-and-security.mdindex 0ee2141..55e0316 100644--- a/docs/guide/privacy-and-security.md+++ b/docs/guide/privacy-and-security.md@@ -1,12 +1,12 @@# Privacy and Security-Nectarlink is built so that your personal data stays on your own devices under your direct control. There is no user account, no cloud database, no analytics or telemetry, and no advertising SDK. Every connection between your phone and your PC is mutually authenticated and encrypted end to end.+NectarLink is built so that your personal data stays on your own devices under your direct control. There is no user account, no cloud database, no analytics or telemetry, and no advertising SDK. Every connection between your phone and your PC is mutually authenticated and encrypted end to end.For a line-by-line engineering audit of every network, IPC, shared-memory, and filesystem boundary, see [`docs/SECURITY-REVIEW.md`](../SECURITY-REVIEW.md).## 1. Device Identity Keys-When Nectarlink starts for the first time on your Windows PC or Android phone, it generates a persistent 256-bit **Ed25519** cryptographic identity keypair:+When NectarLink starts for the first time on your Windows PC or Android phone, it generates a persistent 256-bit **Ed25519** cryptographic identity keypair:- **How devices are identified**: Every device is addressed by its 32-byte Ed25519 public key (`DeviceId`), never by an IP address, hostname, or email address.- **How your private key is protected at rest**:@@ -17,7 +17,7 @@ When Nectarlink starts for the first time on your Windows PC or Android phone, iAn unknown device on your Wi-Fi network can never read your notifications, clipboard, or files. Devices only communicate after completing a mutual pairing ceremony (`ALPN = "nectarlink-pair/0"`):-- **QR Code Pairing**: When you display a pairing QR code on your PC, Nectarlink generates a one-time 128-bit random secret (`s`, encoded in URL-safe base64) that expires after 5 minutes and is invalidated after use or after 5 failed attempts. Scanning that QR code proves your phone observed the secret out of band by computing `HMAC-SHA256(s, "nectarlink-pair-v0" || idA || idB)` over both devices' Ed25519 public keys (`idA` for the initiator and `idB` for the responder).+- **QR Code Pairing**: When you display a pairing QR code on your PC, NectarLink generates a one-time 128-bit random secret (`s`, encoded in URL-safe base64) that expires after 5 minutes and is invalidated after use or after 5 failed attempts. Scanning that QR code proves your phone observed the secret out of band by computing `HMAC-SHA256(s, "nectarlink-pair-v0" || idA || idB)` over both devices' Ed25519 public keys (`idA` for the initiator and `idB` for the responder).- **Nearby and USB 6-Digit Code Pairing**: When you pair without a camera (via **Pair nearby** or **USB auto-pair**), both devices establish a TLS 1.3 session, exchange SHA-256 commitments to 128-bit random nonces (`nA` and `nB`), and derive a 6-digit Short Authentication String (**SAS**) using **HMAC-SHA256** (`uint32_be(HMAC-SHA256(nA || nB, "nectarlink-sas-v0" || idA || idB)[0..4]) mod 1,000,000`). If an attacker on an untrusted Wi-Fi network attempted a man-in-the-middle attack, the public keys in the SAS calculation would not match on both sides. Nothing is paired until you confirm **Codes match** on both devices.- **Pairing links opened from outside the app**: A `nectarlink://pair` link that reaches the phone from a web page, another app, or the system camera never pairs on its own. The phone asks first, naming the PC, and pairs only after you tap **Pair**.@@ -35,30 +35,30 @@ Once paired, each device saves the peer's Ed25519 public key in its local SQLiteEvery post-pairing session (`ALPN = "nectarlink/0"`) runs over **QUIC** (via `iroh`) with **TLS 1.3** mutual authentication:- **Mutual verification**: Both the phone and the PC verify the peer's Ed25519 signature during the TLS 1.3 handshake and immediately drop any connection whose public key is not in the local `peers` table.-- **USB tunnel encryption**: Even when connected over a USB cable (`On USB`), Nectarlink runs the exact same TLS 1.3 end-to-end encrypted QUIC protocol over the local loopback bridge.+- **USB tunnel encryption**: Even when connected over a USB cable (`On USB`), NectarLink runs the exact same TLS 1.3 end-to-end encrypted QUIC protocol over the local loopback bridge.- **Strict wire bounds**: Every protocol message is length-prefixed CBOR capped at 1 MiB before memory allocation (`MAX_FRAME_LEN`), preventing malformed frames from exhausting memory.## 4. Network Connections and Automatic Update Checks### Local-First Device Communication-- **Local network by default**: By default, Nectarlink discovers your paired devices on the local network using mDNS and connects directly over LAN IPv4/IPv6 or a USB cable (`127.0.0.1:53319` over `adb forward`). No device-to-device data leaves your local network unless you turn on **Connect over mobile data**.-- **Opt-in **Connect over mobile data** (`away_mode`, off by default on both PC and Android)**: If you turn on **Connect over mobile data** in **Settings › Connection & About** on the PC and **Settings › Devices** on Android, Nectarlink maintains your connection when your phone is on LTE/5G or a different Wi-Fi network.+- **Local network by default**: By default, NectarLink discovers your paired devices on the local network using mDNS and connects directly over LAN IPv4/IPv6 or a USB cable (`127.0.0.1:53319` over `adb forward`). No device-to-device data leaves your local network unless you turn on **Connect over mobile data**.+- **Opt-in **Connect over mobile data** (`away_mode`, off by default on both PC and Android)**: If you turn on **Connect over mobile data** in **Settings › Connection & About** on the PC and **Settings › Devices** on Android, NectarLink maintains your connection when your phone is on LTE/5G or a different Wi-Fi network.- **End-to-end encryption over relays**: When a direct UDP hole-punch cannot be established while **Connect over mobile data** is enabled, encrypted QUIC packets are forwarded through an `iroh` relay. Because TLS 1.3 terminates exclusively inside your phone and your PC using your paired Ed25519 keys, a relay only sees opaque encrypted UDP datagrams and can never decrypt your messages, notifications, clipboard, or files.-- **Extra protection for remote storage**: Even if you have enabled **File Explorer integration** (`storage`) on your home Wi-Fi, Nectarlink blocks storage browsing over a relay connection unless you also explicitly enable **Remote PC file access** (`remote_files`, off by default) in **Settings › Devices**.+- **Extra protection for remote storage**: Even if you have enabled **File Explorer integration** (`storage`) on your home Wi-Fi, NectarLink blocks storage browsing over a relay connection unless you also explicitly enable **Remote PC file access** (`remote_files`, off by default) in **Settings › Devices**.### Automatic Update Checks (`api.github.com`)To keep your installation current without an app store, installed copies check GitHub Releases over HTTPS:-- **On Windows (`desktop/app/src/updater.rs`, `win/http.rs`)**: On installed copies, **Check for updates** is **On** by default. Nectarlink sends an HTTPS `GET` request via `WinHTTP` to `https://api.github.com/repos/thtbee/nectarlink/releases/latest` 30 seconds after startup and once every 24 hours (with `User-Agent: Nectarlink/<version> (Windows)`). It sends no personal or device information. When a newer release exists, its `SHA256SUMS.txt` and installer (`Nectarlink-<version>-x64-setup.exe`) are downloaded, the installer is checked against the sums, and it runs silently: by itself at a quiet moment when **Install updates automatically** is on (the default), or when you click **Update**. The installer registers a Windows task, **Nectarlink Update**, that runs the update as SYSTEM so no administrator prompt is needed. It takes no input from whoever starts it, only installs a newer published release, and writes what it did to `update.log` in the install folder. Turn either setting off in **Settings › Connection & About**.-- **On Android (`AppUpdater.kt`)**: Release builds check `https://api.github.com/repos/thtbee/nectarlink/releases/latest` over HTTPS at most once every 24 hours, in the background and when the app comes to the front (`User-Agent: Nectarlink/<version> (Android)`), and when you tap **Check for updates**. With **Install updates automatically** on (the default), a newer APK is downloaded, checked against `SHA256SUMS.txt`, and installed. Android only installs it over Nectarlink if it carries the same signature, so only official release builds can update the app.+- **On Windows (`desktop/app/src/updater.rs`, `win/http.rs`)**: On installed copies, **Check for updates** is **On** by default. NectarLink sends an HTTPS `GET` request via `WinHTTP` to `https://api.github.com/repos/thtbee/nectarlink/releases/latest` 30 seconds after startup and once every 24 hours (with `User-Agent: Nectarlink/<version> (Windows)`). It sends no personal or device information. When a newer release exists, its `SHA256SUMS.txt` and installer (`Nectarlink-<version>-x64-setup.exe`) are downloaded, the installer is checked against the sums, and it runs silently: by itself at a quiet moment when **Install updates automatically** is on (the default), or when you click **Update**. The installer registers a Windows task, **Nectarlink Update**, that runs the update as SYSTEM so no administrator prompt is needed. It takes no input from whoever starts it, only installs a newer published release, and writes what it did to `update.log` in the install folder. Turn either setting off in **Settings › Connection & About**.+- **On Android (`AppUpdater.kt`)**: Release builds check `https://api.github.com/repos/thtbee/nectarlink/releases/latest` over HTTPS at most once every 24 hours, in the background and when the app comes to the front (`User-Agent: Nectarlink/<version> (Android)`), and when you tap **Check for updates**. With **Install updates automatically** on (the default), a newer APK is downloaded, checked against `SHA256SUMS.txt`, and installed. Android only installs it over NectarLink if it carries the same signature, so only official release builds can update the app.-### Network Connections Nectarlink Makes+### Network Connections NectarLink Makes| Connection / Activity | Protocol & Destination | Default State | How to Control or Disable || :--- | :--- | :--- | :--- |-| **Paired device discovery & session** | mDNS (`_nectarlink._udp.local`) and direct QUIC + TLS 1.3 UDP on your local LAN | **On** (LAN only) | Unpair devices in **Settings › Devices** or quit Nectarlink |+| **Paired device discovery & session** | mDNS (`_nectarlink._udp.local`) and direct QUIC + TLS 1.3 UDP on your local LAN | **On** (LAN only) | Unpair devices in **Settings › Devices** or quit NectarLink || **USB wired transport (`On USB`)** | QUIC + TLS 1.3 over loopback TCP (`127.0.0.1:5037` ADB host to `127.0.0.1:53319` on device) | **On** when USB debugging is active | Unplug the USB cable or turn off USB debugging on the phone || **Automatic update check (Windows)** | HTTPS `GET` to `https://api.github.com/repos/thtbee/nectarlink/releases/latest` (30s after launch and every 24h; downloads `SHA256SUMS.txt` and the setup `.exe` when a newer release exists) | **On** on installed copies | Turn off **Settings › Connection & About › Automatic updates** || **Automatic / manual update check (Android)** | HTTPS `GET` to `https://api.github.com/repos/thtbee/nectarlink/releases/latest` (at most once per 24h in release builds; downloads `SHA256SUMS.txt` and the `.apk` when a newer release exists) | **On** in release builds | Controlled by foreground checks or manual **Settings › Features & Data › About › Check for updates** |@@ -84,11 +84,11 @@ Pairing a device does not give it unrestricted access to everything. You control## 6. How the `Elevated` Shell Helper Is Secured-If you choose to enable the `Elevated` power level on Android, Nectarlink starts its companion helper (`app.nectarlink.android.elevated.InputServer` via `app_process`) running as Android's `shell` user (`UID 2000`) through Wireless Debugging or USB `adb`.+If you choose to enable the `Elevated` power level on Android, NectarLink starts its companion helper (`app.nectarlink.android.elevated.InputServer` via `app_process`) running as Android's `shell` user (`UID 2000`) through Wireless Debugging or USB `adb`.To ensure no other app on your phone can abuse this helper:-1. **Loopback Binding and 192-Bit Per-Session Token Authentication**: Because Android SELinux blocks regular apps from connecting to `shell`-owned Unix domain sockets, `InputServer` binds exclusively to a loopback TCP socket (`127.0.0.1:<ephemeral_port>`) and requires a 24-byte (48-hex-character) `SecureRandom` secret token on the first line of every connection. The token is generated fresh by the Nectarlink app when launching the helper and verified in constant time (`MessageDigest.isEqual`); any unauthenticated connection is closed immediately before reading a command.+1. **Loopback Binding and 192-Bit Per-Session Token Authentication**: Because Android SELinux blocks regular apps from connecting to `shell`-owned Unix domain sockets, `InputServer` binds exclusively to a loopback TCP socket (`127.0.0.1:<ephemeral_port>`) and requires a 24-byte (48-hex-character) `SecureRandom` secret token on the first line of every connection. The token is generated fresh by the NectarLink app when launching the helper and verified in constant time (`MessageDigest.isEqual`); any unauthenticated connection is closed immediately before reading a command.2. **Fixed Verb Dispatch and Strict Command Allowlist**: Commands sent over the socket are parsed as fixed single-letter verbs (`D`, `M`, `U`, `C`, `S`, `W`, `K`, `T`, `P`, `A`, `V`, `E`, `H`, `G`, `B`) dispatched directly to Android Binder APIs (`IInputManager`, `IClipboard`, `IActivityTaskManager`, `/dev/uhid`), and the `C` verb is restricted to an explicit allowlist of system toggle commands (notification shade expand, Wi-Fi, Bluetooth, hotspot, and screen brightness `0..255`). Arbitrary shell commands are rejected.## 7. Local Data Storage, Encryption, and Retentiondiff --git a/docs/guide/settings.md b/docs/guide/settings.mdindex e0a9758..41ac478 100644--- a/docs/guide/settings.md+++ b/docs/guide/settings.md@@ -3,7 +3,7 @@This page explains every setting in the Windows 11 app and the Android app one by one, including its exact in-app label, default value, and what changing it does.<p align="center">- <img src="images/settings-appearance.png" alt="Categorized two-pane Settings screen in Nectarlink for Windows" width="760">+ <img src="images/settings-appearance.png" alt="Categorized two-pane Settings screen in NectarLink for Windows" width="760"></p>## Windows 11 App Settings@@ -19,7 +19,7 @@ Controls the visual theme, light/dark mode, accent palette, OLED black surfaces,| Setting | Options / Default | What It Does || :--- | :--- | :--- || **Theme** | `Hive`, `Bloom` (default), `Glass`, `Graphite` | Selects the visual style. **Hive** is honey on charcoal (dark) or warm wax (light), with a living honeycomb behind the whole window that grows from the logo, breathes, and sends soft pulses of light; its colors are fixed, so the color options below are hidden. **Bloom** uses soft, tinted Material You surfaces. **Glass** renders translucent cards over the Windows backdrop, each with a lit glass rim: a specular edge from the top left, a softer reflection at the bottom right, and a faint inner glow. **Graphite** uses high-contrast monochrome ink-on-paper surfaces. |-| **Mode** | `System` (default), `Light`, `Dark` | Follows Windows 11's system light/dark mode or locks Nectarlink to Light or Dark. |+| **Mode** | `System` (default), `Light`, `Dark` | Follows Windows 11's system light/dark mode or locks NectarLink to Light or Dark. || **Color** *(shown in Bloom and Glass)* | **Wallpaper** (default), **Honey**, **Lavender**, **Ocean**, **Sage**, **Black**, **Media artwork**, or **Phone color pills** | Picks the accent seed color. **Wallpaper** extracts colors from your desktop wallpaper. **Media artwork** dynamically adapts the app's palette to the album art of whatever song is currently playing. **Phone color pills** sync live with each paired phone's Material You wallpaper palette. || **Pure black (AMOLED)** | **Off** (default) | Shown inline as an **AMOLED** pill when the **Black** color swatch is selected in Bloom/Glass, or as a dedicated row in **Graphite Dark**. Replaces dark gray backgrounds with pure `#000000` black for OLED monitors. || **Animated comb** *(Hive)* | **On** (default) | Lets Hive's honeycomb breathe and pulse. It also holds still while animations are off in Windows, while energy saver is on, and while the window isn't in front. Shown in place of **Mica backdrop**, which Hive doesn't use. |@@ -33,8 +33,8 @@ Controls startup behavior, the system tray, `Nectar Island`, battery notificatio| Setting | Default | What It Does || :--- | :--- | :--- |-| **Start with Windows** | **On** for installed copies | Launches Nectarlink quietly in the Windows system tray when you sign in to your PC. |-| **Stay in system tray** | **On** | Keeps Nectarlink running in the system tray (unloading the UI window to ~5 to 10 MB working set) when you close the main window, so your phone stays connected. When turned off, closing the window quits the app completely. |+| **Start with Windows** | **On** for installed copies | Launches NectarLink quietly in the Windows system tray when you sign in to your PC. |+| **Stay in system tray** | **On** | Keeps NectarLink running in the system tray (unloading the UI window to ~5 to 10 MB working set) when you close the main window, so your phone stays connected. When turned off, closing the window quits the app completely. || **Nectar Island** | **Off** | Shows a compact pill at the top center of your primary monitor during active phone events. Automatically hides during full-screen games/videos or Windows Do Not Disturb. || **Island triggers** *(shown when Nectar Island is On)* | **Calls**: On, **Transfers**: On, **Media**: On, **Alerts**: Off | Toggles which phone events expand `Nectar Island`: incoming/active **Calls**, active file **Transfers**, now-playing **Media**, and phone notification **Alerts** (including OTPs, timers, and recordings). || **Battery alerts** | **On** | Shows a desktop notification when a connected phone's battery drops low or reaches a full charge. |@@ -91,13 +91,13 @@ Lists your paired phones (with a device selector pill bar at the top when more t### 4. Camera & Audio-Configures **Phone as speaker**, call media pausing, the **Nectarlink Webcam** virtual camera add-on, and live camera stream settings.+Configures **Phone as speaker**, call media pausing, the **NectarLink Webcam** virtual camera add-on, and live camera stream settings.| Setting | Options / Default | What It Does || :--- | :--- | :--- || **Stream PC audio to phone** | **Off** (default) | Streams real-time Windows system audio (uncompressed 16-bit stereo) to your connected phone so you can listen through your phone's speakers or headphones. || **Pause media during calls** | **On** (default) | Automatically pauses media playing on this PC when your phone rings or is in an active call, and resumes when the call ends. |-| **Virtual camera add-on** | **Set up** / **Remove** | Registers or unregisters `nectarlink_vcam.dll` with Windows 11 Media Foundation (requires a one-time Administrator prompt) so **Nectarlink Webcam** appears in Zoom, Teams, Meet, and OBS. |+| **Virtual camera add-on** | **Set up** / **Remove** | Registers or unregisters `nectarlink_vcam.dll` with Windows 11 Media Foundation (requires a one-time Administrator prompt) so **NectarLink Webcam** appears in Zoom, Teams, Meet, and OBS. || **Phone** *(shown when more than one phone is paired)* | First paired phone | Picks which paired phone provides the webcam video feed. || **Camera** | `Back` (default), `Front` | Selects the phone's rear or front camera lens. || **Mirror image** | **Off** (default) | Flips the webcam video horizontally. |@@ -112,10 +112,10 @@ Configures Do Not Disturb synchronization, PC-to-phone notification forwarding,| Setting | Options / Default | What It Does || :--- | :--- | :--- |-| **Follow phone Do not disturb** | **Off** (default) | Mutes Windows notification popups on this PC whenever your phone is in Do Not Disturb mode (notifications still wait quietly in the Nectarlink feed). |+| **Follow phone Do not disturb** | **Off** (default) | Mutes Windows notification popups on this PC whenever your phone is in Do Not Disturb mode (notifications still wait quietly in the NectarLink feed). || **Forward PC notifications** | **Off** (default) | Forwards Windows desktop notifications to your connected phone while you are away from your desk. || **Quiet hours** | **Set a schedule** button | Opens Windows 11 **System › Notifications** settings to configure automatic Focus / Do Not Disturb schedules. |-| **Per-app notification rules** | `Show` (default), `No pop-ups`, `Hide` | For every phone app that has posted a notification: **Show** displays both Windows popups and feed cards; **No pop-ups** keeps alerts in the Nectarlink feed without desktop popups; **Hide** blocks that app's notifications completely. |+| **Per-app notification rules** | `Show` (default), `No pop-ups`, `Hide` | For every phone app that has posted a notification: **Show** displays both Windows popups and feed cards; **No pop-ups** keeps alerts in the NectarLink feed without desktop popups; **Hide** blocks that app's notifications completely. |---@@ -126,7 +126,7 @@ Configures File Explorer integration, PC folder sharing, LocalSend, voice record| Setting | Options / Default | What It Does || :--- | :--- | :--- || **File Explorer Send to** | **On** (default) | Adds your paired phones to the right-click **Send to** menu in Windows File Explorer. |-| **Your PC in your pocket** | **Off** (default) | Shares your PC's `Downloads`, `Documents`, `Desktop`, `Pictures`, and `Nectarlink Shared` folders with paired phones that have **File Explorer integration** enabled. |+| **Your PC in your pocket** | **Off** (default) | Shares your PC's `Downloads`, `Documents`, `Desktop`, `Pictures`, and `NectarLink Shared` folders with paired phones that have **File Explorer integration** enabled. || **LocalSend on local network** | **Off** (default) | Enables the built-in LocalSend v2.1 client and server (UDP/TCP port `53317`) to send and receive files with nearby LocalSend devices on your Wi-Fi network without pairing. || **Open files shared from the phone** | **Off** (default) | When you share a single photo or document from the phone, opens it in its default Windows app as soon as it arrives. When off, the file is saved to `Downloads\Nectarlink` without opening anything. || **Voice recordings** | Format: `M4A` (default), `MP3`, `WAV`, `FLAC`; Folder: **Choose folder** / **Reset** | Sets where incoming voice notes from your phone are saved (`Documents\Nectarlink Recordings` or `Downloads\Nectarlink` by default) and automatically converts them to MP3, WAV, or FLAC if selected. |@@ -187,7 +187,7 @@ Provides network diagnostics, **Connect over mobile data**, Wake-on-LAN readines| **Connect over mobile data** | **Off** | Allows this PC and paired phones to stay connected over LTE/5G or across separate networks via end-to-end encrypted relay packets when direct LAN/USB is unavailable. || **Wake from your phone** | Read-only status indicator (`Ready`, `Off in Windows`, `Check settings`, `No adapter`) | Inspects your active Windows network adapter and tells you whether Wake on LAN is enabled in Device Manager so your phone can wake this PC from sleep. || **Local automation API** | **Off** (default port `53320`) | Starts the loopback-only HTTP/JSON server (`127.0.0.1:<port>`) for PowerToys, AutoHotkey, and scripts, and writes the 256-bit Bearer token to `%LOCALAPPDATA%\Nectarlink\api-token.json`. |-| **Nectarlink `<version>`** | **Check for updates** and **Open logs** buttons | Shows the app version and this PC's device name, checks GitHub Releases for SHA-256 verified updates, or opens the local diagnostic logs folder. |+| **NectarLink `<version>`** | **Check for updates** and **Open logs** buttons | Shows the app version and this PC's device name, checks GitHub Releases for SHA-256 verified updates, or opens the local diagnostic logs folder. || **Check for updates** | **On** (shown on installed copies) | Checks GitHub Releases over HTTPS (`https://api.github.com/repos/thtbee/nectarlink/releases/latest`) 30 seconds after startup and every 24 hours. || **Install updates automatically** | **On** | Installs a newer release by itself when nobody has used the PC for 10 minutes and nothing is in progress (no mirroring, app window, transfer, call, screen sharing or webcam). No administrator prompt: the installer sets up a task that does it. Turn it off to install from the notification or **Check for updates** when you choose. || **Setup walkthrough & Features guide** | Action buttons / Command Palette entries | Reopens the first-run setup walkthrough or the interactive in-app Features Guide at any time. |@@ -199,7 +199,7 @@ Provides network diagnostics, **Connect over mobile data**, Wake-on-LAN readinesOn Android, tap **Settings** in the floating bottom dock. You can view all settings at once (**All**) or filter by category chip at the top (**Appearance**, **Devices**, **Permissions**, **Features & Data**).<p align="center">- <img src="images/android-settings.png" alt="Settings screen in Nectarlink for Android" width="760">+ <img src="images/android-settings.png" alt="Settings screen in NectarLink for Android" width="760"></p>### 1. Appearance@@ -211,7 +211,7 @@ On Android, tap **Settings** in the floating bottom dock. You can view all setti| **Animated comb** *(Hive)* | **On** (default) | Lets Hive's honeycomb breathe and pulse. It holds still with **Remove animations** or battery saver on, and while the app isn't in front. || **Pure black (AMOLED)** | **Off** (default) | Shown in Graphite Dark or as an inline **AMOLED** pill when the **Black** seed swatch is selected. Uses true `#000000` black surfaces for OLED phone screens. || **Media artwork color** *(Bloom and Glass)* | **Off** (default) | Tints the app to match the artwork of what is playing on the phone or a paired PC. Applies only while this is on. With nothing playing, the app uses the wallpaper or preset colors. |-| **Colors from wallpaper** *(Android 12+)* | **On** (default) | Uses your wallpaper's colors and updates when the wallpaper changes. On Samsung phones with One UI's **Color palette** off, Nectarlink reads the colors from the wallpaper itself. Paired PCs that select **My phone's colors** use the same seed. |+| **Colors from wallpaper** *(Android 12+)* | **On** (default) | Uses your wallpaper's colors and updates when the wallpaper changes. On Samsung phones with One UI's **Color palette** off, NectarLink reads the colors from the wallpaper itself. Paired PCs that select **My phone's colors** use the same seed. || **Color swatches** | **Honey**, **Lavender**, **Ocean**, **Sage**, **Black** | Selects a preset accent color when **Media artwork color** and **Colors from wallpaper** are off. |### 2. PCs (`Devices`)@@ -230,12 +230,12 @@ Each permission row shows its live state (**On** / **Allowed** vs **Off**) and a| Section & Setting | Power Level / Purpose || :--- | :--- || **Notifications › Show notifications on your PC** | Grants Android Notification Listener access so phone notifications, inline replies, and actions work on your PC. Includes an **App info** helper on Android 13+ if **Allow restricted settings** is needed. |-| **Control from your PC › Use your PC's mouse and keyboard** | Enables Nectarlink's Android Accessibility Service (`Assist` power level) so you can tap, swipe, and type on your phone from your PC during screen mirroring or via **Type on phone**. |+| **Control from your PC › Use your PC's mouse and keyboard** | Enables NectarLink's Android Accessibility Service (`Assist` power level) so you can tap, swipe, and type on your phone from your PC during screen mirroring or via **Type on phone**. || **Control from your PC › Real touch and keys (Wireless debugging)** | Sets up or manages the `Elevated` power level via Android's built-in Wireless Debugging (real-time touch dragging, UHID keyboard/gamepad, `app window` streaming, background clipboard sync, Android 15+ sensitive OTPs, in-call mute/hold/speaker, and Wi-Fi/Bluetooth toggles). || **Control from your PC › Do Not Disturb and silent mode** | Grants Notification Policy Access so your PC can toggle Do Not Disturb and set the ringer to silent. || **Control from your PC › Screen brightness** | Grants Modify system settings (`WRITE_SETTINGS`) so your PC can adjust your phone's screen brightness slider. || **Background & battery › Stay reachable in the background** | Requests Android's unrestricted battery usage exemption (`REQUEST_IGNORE_BATTERY_OPTIMIZATIONS`) and displays step-by-step instructions tailored to your phone's manufacturer (Samsung, Xiaomi, OnePlus, Oppo/Realme, Vivo, Huawei, Pixel) with a **Battery settings** button. |-| **Background & battery › Wake when PC is nearby (Companion Device)** | Associates your paired PC with Android's `CompanionDeviceManager` so Android wakes Nectarlink automatically when your PC's Bluetooth LE beacon is in range. |+| **Background & battery › Wake when PC is nearby (Companion Device)** | Associates your paired PC with Android's `CompanionDeviceManager` so Android wakes NectarLink automatically when your PC's Bluetooth LE beacon is in range. || **Calls, contacts and messages › Calls on your PC** | Grants phone state, call log, and call control permissions. || **Calls, contacts and messages › Contacts on your PC** | Grants contact read access so names and avatars appear in Calls and Messages on your PC. || **Calls, contacts and messages › Text from your PC** | Grants SMS permissions to read and send texts on your PC. |@@ -257,8 +257,8 @@ Each permission row shows its live state (**On** / **Allowed** vs **Off**) and a| **Data & storage › Photo thumbnails & camera cache** | **Clear** button | Clears temporary Continuity Camera captures (automatically cleaned up after 24 hours). || **Data & storage › Received-file history** | **Clear** button | Clears the transfer log without deleting any saved files in `Download/Nectarlink`. || **Data & storage › Clear everything...** | Confirmation dialog | Deletes all clipboard history, `Timeline`, transfer records, and temporary caches on this phone while keeping your paired PCs and settings. |-| **About › Nectarlink `<version>` & Check for updates** | **Check for updates** button | Shows the installed version and checks GitHub Releases (`https://api.github.com/repos/thtbee/nectarlink/releases/latest`) for SHA-256 verified APK updates. |-| **About › Install updates automatically** | **On** | Checks once a day in the background and installs a newer release by itself. Android 12 and later install it without asking once Nectarlink has installed an update before; otherwise a notification asks for one tap. Needs **Install unknown apps** allowed for Nectarlink. |+| **About › NectarLink `<version>` & Check for updates** | **Check for updates** button | Shows the installed version and checks GitHub Releases (`https://api.github.com/repos/thtbee/nectarlink/releases/latest`) for SHA-256 verified APK updates. |+| **About › Install updates automatically** | **On** | Checks once a day in the background and installs a newer release by itself. Android 12 and later install it without asking once NectarLink has installed an update before; otherwise a notification asks for one tap. Needs **Install unknown apps** allowed for NectarLink. |<p align="center"><img src="images/android-update.png" alt="About in the Android app with Install updates automatically" width="360">diff --git a/docs/guide/troubleshooting.md b/docs/guide/troubleshooting.mdindex 2e260d7..c828bf8 100644--- a/docs/guide/troubleshooting.md+++ b/docs/guide/troubleshooting.md@@ -4,7 +4,7 @@ If your phone and PC cannot find each other, disconnect when your phone screen t## 1. Run the `Connection Doctor` First-Nectarlink includes a built-in diagnostic tool on Windows that automatically detects the most common network blockers and fixes what it can.+NectarLink includes a built-in diagnostic tool on Windows that automatically detects the most common network blockers and fixes what it can.1. On your PC, open **Settings › Connection & About**.2. Next to **Connection Doctor**, click **Check**.@@ -16,48 +16,48 @@ Nectarlink includes a built-in diagnostic tool on Windows that automatically det## 2. Phone Disconnects When Its Screen Is Off (Per-OEM Battery Guides)-If Nectarlink stays connected while the Android app is open on screen, but drops its connection a few minutes after you lock your phone (causing inline replies, notifications, or file transfers from your PC to wait or time out), Android or your phone manufacturer's battery manager is putting Nectarlink to sleep.+If NectarLink stays connected while the Android app is open on screen, but drops its connection a few minutes after you lock your phone (causing inline replies, notifications, or file transfers from your PC to wait or time out), Android or your phone manufacturer's battery manager is putting NectarLink to sleep.### Step 1: Allow Standard Android Background Access-1. On your phone, open **Nectarlink › Settings › Permissions › Background & battery**.-2. Next to **Stay reachable in the background**, tap **Allow** and confirm Android's prompt to let Nectarlink run without battery restrictions (`Unrestricted`).+1. On your phone, open **NectarLink › Settings › Permissions › Background & battery**.+2. Next to **Stay reachable in the background**, tap **Allow** and confirm Android's prompt to let NectarLink run without battery restrictions (`Unrestricted`).### Step 2: Apply Your Phone Brand's Extra Battery Setting-Several Android manufacturers add their own proprietary background task killers on top of standard Android. Nectarlink detects your phone's manufacturer and shows the matching guide right inside **Settings › Permissions › Background & battery** (tap **Battery settings** there to jump directly to the system screen):+Several Android manufacturers add their own proprietary background task killers on top of standard Android. NectarLink detects your phone's manufacturer and shows the matching guide right inside **Settings › Permissions › Background & battery** (tap **Battery settings** there to jump directly to the system screen):| Phone Brand | Required Settings || :--- | :--- |-| **Samsung (One UI)** | 1. Open **Android Settings › Apps › Nectarlink › Battery** and select **Unrestricted**.<br>2. Open **Android Settings › Device care › Battery › Background usage limits** and make sure Nectarlink is not in **Sleeping apps** or **Deep sleeping apps** (add it to **Never auto sleeping apps**). |-| **Google Pixel** | Open **Android Settings › Apps › Nectarlink › App battery usage**, tap **Allow background usage** (the row text itself, not just the toggle), and select **Unrestricted**. |-| **Xiaomi / Redmi / POCO (HyperOS / MIUI)** | 1. Open **Android Settings › Apps › Manage apps › Nectarlink** and turn **Autostart** (or **Background autostart**) **On**.<br>2. Tap **Battery saver** and select **No restrictions**. |-| **OnePlus (OxygenOS)** | Open **Android Settings › Apps › App management › Nectarlink › Battery usage** and turn on both **Allow background activity** and **Allow auto-launch**. |-| **Oppo / Realme (ColorOS / Realme UI)** | Open **Android Settings › Apps › App management › Nectarlink › Battery usage** and turn on both **Allow background activity** and **Allow auto-launch**. |-| **Vivo / iQOO (Funtouch OS / OriginOS)** | Open **Android Settings › Apps › Nectarlink › Battery**, select **Unrestricted** (or **High background power usage**), and enable **Autostart** in Background power consumption management. |-| **Huawei / Honor (EMUI)** | Open **Phone Manager (or System Optimizer) › App launch**, turn **Off** **Manage automatically** for Nectarlink, and keep all three toggles (**Auto-launch**, **Secondary launch**, and **Run in background**) turned **On**. |+| **Samsung (One UI)** | 1. Open **Android Settings › Apps › NectarLink › Battery** and select **Unrestricted**.<br>2. Open **Android Settings › Device care › Battery › Background usage limits** and make sure NectarLink is not in **Sleeping apps** or **Deep sleeping apps** (add it to **Never auto sleeping apps**). |+| **Google Pixel** | Open **Android Settings › Apps › NectarLink › App battery usage**, tap **Allow background usage** (the row text itself, not just the toggle), and select **Unrestricted**. |+| **Xiaomi / Redmi / POCO (HyperOS / MIUI)** | 1. Open **Android Settings › Apps › Manage apps › NectarLink** and turn **Autostart** (or **Background autostart**) **On**.<br>2. Tap **Battery saver** and select **No restrictions**. |+| **OnePlus (OxygenOS)** | Open **Android Settings › Apps › App management › NectarLink › Battery usage** and turn on both **Allow background activity** and **Allow auto-launch**. |+| **Oppo / Realme (ColorOS / Realme UI)** | Open **Android Settings › Apps › App management › NectarLink › Battery usage** and turn on both **Allow background activity** and **Allow auto-launch**. |+| **Vivo / iQOO (Funtouch OS / OriginOS)** | Open **Android Settings › Apps › NectarLink › Battery**, select **Unrestricted** (or **High background power usage**), and enable **Autostart** in Background power consumption management. |+| **Huawei / Honor (EMUI)** | Open **Phone Manager (or System Optimizer) › App launch**, turn **Off** **Manage automatically** for NectarLink, and keep all three toggles (**Auto-launch**, **Secondary launch**, and **Run in background**) turned **On**. |## 3. Android 13+ "Restricted Settings" (Grayed-Out Notification or Accessibility Switch)On Android 13 and newer, if you install an APK downloaded from a browser or GitHub Releases, Android disables the **Notification access** and **Accessibility** switches until you explicitly allow restricted settings for that app:-1. Tap **Allow** on the **Show notifications on your PC** or **Use your PC's mouse and keyboard** row in Nectarlink so Android sees that you tried to turn it on once.-2. Return to Nectarlink's **Settings › Permissions** and tap **App info** (or open **Android Settings › Apps › Nectarlink**).+1. Tap **Allow** on the **Show notifications on your PC** or **Use your PC's mouse and keyboard** row in NectarLink so Android sees that you tried to turn it on once.+2. Return to NectarLink's **Settings › Permissions** and tap **App info** (or open **Android Settings › Apps › NectarLink**).3. Tap the **three-dot menu** in the top-right corner of the App info screen and tap **Allow restricted settings**.4. Authenticate with your fingerprint, face, or PIN.-5. Go back to Nectarlink and tap **Allow** again. The switch can now be turned on normally.+5. Go back to NectarLink and tap **Allow** again. The switch can now be turned on normally.## 4. Troubleshooting `Elevated` (Wireless Debugging)### The 6-Digit Pairing Code Notification Does Not Appear or Fails-- **Keep the code dialog open on screen**: Android invalidates the 6-digit Wireless Debugging pairing code the moment you navigate away from the **Pair device with pairing code** dialog. Keep that dialog visible on screen, pull down your notification shade over it, tap **Enter code** on Nectarlink's notification, and type the 6 digits there.+- **Keep the code dialog open on screen**: Android invalidates the 6-digit Wireless Debugging pairing code the moment you navigate away from the **Pair device with pairing code** dialog. Keep that dialog visible on screen, pull down your notification shade over it, tap **Enter code** on NectarLink's notification, and type the 6 digits there.- **Make sure Wi-Fi is connected**: Android's built-in Wireless Debugging only runs while connected to a Wi-Fi network.-- **If the phone says "The phone forgot Nectarlink's pairing"**: If you tapped **Forget all** under Paired devices in Android's Wireless Debugging settings, open Nectarlink's **Settings › Permissions › Control from your PC** and tap **Set up** to pair Wireless Debugging again.+- **If the phone says "The phone forgot NectarLink's pairing"**: If you tapped **Forget all** under Paired devices in Android's Wireless Debugging settings, open NectarLink's **Settings › Permissions › Control from your PC** and tap **Set up** to pair Wireless Debugging again.### `Elevated` Stops After Turning Developer Options Off-- If you turn the master **Developer options** switch off in Android Settings, Android stops Wireless Debugging and terminates the `Elevated` shell helper. Keep **Developer options** turned on if you use `Elevated` features. (When you reboot your phone or reconnect to Wi-Fi with Developer options on, Nectarlink automatically re-enables Wireless Debugging and restarts `Elevated` by itself.)+- If you turn the master **Developer options** switch off in Android Settings, Android stops Wireless Debugging and terminates the `Elevated` shell helper. Keep **Developer options** turned on if you use `Elevated` features. (When you reboot your phone or reconnect to Wi-Fi with Developer options on, NectarLink automatically re-enables Wireless Debugging and restarts `Elevated` by itself.)## 5. Troubleshooting USB Auto-Pair and `On USB` Transport@@ -83,18 +83,18 @@ If plugging your phone into your PC with a USB cable does not trigger USB auto-p- Check that the speaker icon in the `mirror` window toolbar on your PC is not muted, and that your phone's media volume is turned up.- Note that some Android apps explicitly block third-party `AudioPlaybackCapture` in their manifest (see [Known Limitations](known-limitations.md)).-## 7. Troubleshooting Phone as Webcam (`Nectarlink Webcam`)+## 7. Troubleshooting Phone as Webcam (`NectarLink Webcam`)-### `Nectarlink Webcam` Does Not Appear in Zoom, Teams, Meet, or OBS+### `NectarLink Webcam` Does Not Appear in Zoom, Teams, Meet, or OBS-1. Open Nectarlink on your PC and go to **Settings › Camera & Audio**.+1. Open NectarLink on your PC and go to **Settings › Camera & Audio**.2. Check the **Virtual camera add-on** row. If it shows **Set up** instead of **Ready**, click **Set up** and approve the Windows Administrator prompt.3. Restart Zoom, Teams, your web browser, or OBS so the application refreshes its list of Windows Media Foundation video capture devices.### Clicking "Start Webcam" on the PC Waits on "Asking..."-- By design, a PC cannot turn on your phone's camera silently. Look at your phone and tap the **`<PC>` wants to use your camera** notification (or open Nectarlink on your phone and tap **Webcam › Start webcam**).+- By design, a PC cannot turn on your phone's camera silently. Look at your phone and tap the **`<PC>` wants to use your camera** notification (or open NectarLink on your phone and tap **Webcam › Start webcam**).## 8. Inspecting Diagnostic Logs-If you need to report a bug, open **Settings › Connection & About** on your PC and click **Open logs** (next to the Nectarlink version row) to open the local log directory in File Explorer. Nectarlink never logs notification text, SMS message bodies, or clipboard contents to its log files.+If you need to report a bug, open **Settings › Connection & About** on your PC and click **Open logs** (next to the NectarLink version row) to open the local log directory in File Explorer. NectarLink never logs notification text, SMS message bodies, or clipboard contents to its log files.diff --git a/docs/protocol/calls.md b/docs/protocol/calls.mdindex 51698b8..94e9a11 100644--- a/docs/protocol/calls.md+++ b/docs/protocol/calls.md@@ -137,16 +137,16 @@ the call.calls. `call.log` needs the call log permission. `call.dial` uses`CALL_PHONE` to place the call directly, or opens the dialer when`CALL_PHONE` isn't granted. `call.incall` needs Android 12 or later and-the `MANAGE_ONGOING_CALLS` app-op, which lets Telecom bind Nectarlink's+the `MANAGE_ONGOING_CALLS` app-op, which lets Telecom bind NectarLink'sin-call service as a calling companion without it being the phone app.-Apps can't grant that app-op to themselves; Nectarlink's Elevated mode+Apps can't grant that app-op to themselves; NectarLink's Elevated mode(Wireless debugging) grants it through the shell when it starts.Not in this service:- **Recording calls.** Android doesn't let apps other than the phone'sown record call audio (capturing the voice call stream needs a- privileged permission), so Nectarlink doesn't offer it.+ privileged permission), so NectarLink doesn't offer it.- **Talking through the PC.** Carrying the call's audio to the PC'smicrophone and speakers is planned as a Bluetooth hands-free (HFP)link from the PC to the phone, as for a headset; it isn't part of thisdiff --git a/docs/protocol/v0.md b/docs/protocol/v0.mdindex 36d2b1c..9f00c10 100644--- a/docs/protocol/v0.md+++ b/docs/protocol/v0.md@@ -1,9 +1,9 @@-# Nectarlink Protocol, version 0 (draft)+# NectarLink Protocol, version 0 (draft)> Status: **draft for Phase 0.** Breaking changes are allowed until v1.> License: CC BY 4.0. Anyone may implement this protocol.-This document specifies how two Nectarlink devices find each other, pair,+This document specifies how two NectarLink devices find each other, pair,connect and exchange messages. Version 0 covers the Phase 0 scope: identity,pairing, the session handshake, capabilities, heartbeat and the first events(device info, battery, ping). Feature services are specified in separate@@ -20,7 +20,7 @@ Key words **MUST**, **SHOULD** and **MAY** are used as in RFC 2119.| Term | Meaning ||---|---|-| **Device** | One installation of Nectarlink (a phone, a PC). |+| **Device** | One installation of NectarLink (a phone, a PC). || **Device key** | An Ed25519 key pair generated on first launch. Never leaves the device. || **Device ID** | The Ed25519 public key (32 bytes). Equal to the iroh `EndpointId`. Displayed as lowercase z-base-32. || **Pairing** | A one-time ceremony after which each device stores the other's Device ID as trusted. |@@ -401,7 +401,7 @@ When the user accepts the captured photo or scanned document on the phone:## 13. LocalSend v2.1 Interoperability (Optional LAN Interop)-In addition to Nectarlink's native QUIC/iroh protocol, any Nectarlink node can+In addition to NectarLink's native QUIC/iroh protocol, any NectarLink node canoptionally enable **LocalSend v2.1** interoperability (off by default, stored inthe local settings table as `localsend.enabled`) to send files to and receivefiles from unpaired LocalSend devices (iOS, macOS, Linux, Windows, Android) on@@ -416,15 +416,15 @@ the local network.peeks at the first byte of each incoming connection (`0x16` = TLS ClientHello)to serve both HTTPS and plain HTTP on the same socket.- **Coexistence:** If TCP port `53317` is already bound by a standalone- LocalSend app on the same machine, Nectarlink logs a warning, sets+ LocalSend app on the same machine, NectarLink logs a warning, sets`localsend_receiving() = false` (leaving incoming transfers to the standaloneLocalSend app), and still joins UDP multicast discovery and supports outgoingtransfers to discovered LocalSend peers.-- **Identity & TLS:** Nectarlink generates a deterministic self-signed X.509 v3+- **Identity & TLS:** NectarLink generates a deterministic self-signed X.509 v3certificate (Ed25519) from the node's device key and advertises its uppercasehex SHA-256 DER digest as the LocalSend `fingerprint`. If a peer's fingerprint- matches a paired Nectarlink `DeviceId`, it is de-duplicated in favor of the- native Nectarlink session; otherwise a deterministic synthetic `DeviceId` is+ matches a paired NectarLink `DeviceId`, it is de-duplicated in favor of the+ native NectarLink session; otherwise a deterministic synthetic `DeviceId` isderived from `BLAKE3("nectarlink-localsend-peer-v1:" || fingerprint_or_addr)`.### 13.2 REST Endpoints (`/api/localsend/v2/...`)diff --git a/docs/protocol/webcam.md b/docs/protocol/webcam.mdindex 4d9842c..00cf5de 100644--- a/docs/protocol/webcam.md+++ b/docs/protocol/webcam.md@@ -10,7 +10,7 @@ travel on a dedicated bidirectional QUIC stream (`{ svc: "webcam", op: "video",|---|---|---|| `camera.stream` | Phone | Streams a camera for webcam use (when `CAMERA` permission is granted) || `camera.virtual` | PC | Receives and decodes a phone's webcam stream |-| `addon.vcam` | PC | The Windows virtual camera COM add-on is registered in `HKLM`, so apps (Teams, Meet, Zoom, Windows Camera) see `"Nectarlink - <Phone name>"` |+| `addon.vcam` | PC | The Windows virtual camera COM add-on is registered in `HKLM`, so apps (Teams, Meet, Zoom, Windows Camera) see `"NectarLink - <Phone name>"` |Both devices have a `webcam` per-device toggle (on by default). When turned offfor a peer, `webcam.start` is refused with `denied` (`4`), incoming `webcam`diff --git a/docs/research/hfp.md b/docs/research/hfp.mdindex 9a1965a..2ac3626 100644--- a/docs/research/hfp.md+++ b/docs/research/hfp.md@@ -25,7 +25,7 @@ We evaluated three Windows Bluetooth APIs for using the PC's microphone and spea3. **Kernel Profile Driver Requirement (`BTH_PROFILE_DRIVER_INTERFACE`)**:- Without access to the inbox `PhoneExperienceHost` broker, 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.-**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).+**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).---diff --git a/docs/technical/README.md b/docs/technical/README.mdindex 17b7f9f..cba1572 100644--- a/docs/technical/README.md+++ b/docs/technical/README.md@@ -1,6 +1,6 @@-# Nectarlink Technical Documentation+# NectarLink Technical Documentation-This directory contains engineering documentation for contributors, security reviewers, and systems engineers working on Nectarlink. It covers the multi-crate Rust workspace, the Windows Qt 6 + `cxx-qt` desktop application, the Android Jetpack Compose + UniFFI client, the QUIC + TLS 1.3 protocol, the SQLite persistence layer, and the performance verification suite.+This directory contains engineering documentation for contributors, security reviewers, and systems engineers working on NectarLink. It covers the multi-crate Rust workspace, the Windows Qt 6 + `cxx-qt` desktop application, the Android Jetpack Compose + UniFFI client, the QUIC + TLS 1.3 protocol, the SQLite persistence layer, and the performance verification suite.For end-user setup and feature guides, see [docs/guide/README.md](../guide/README.md).diff --git a/docs/technical/architecture.md b/docs/technical/architecture.mdindex 623419d..d514565 100644--- a/docs/technical/architecture.md+++ b/docs/technical/architecture.md@@ -1,6 +1,6 @@# Architecture-Nectarlink is built around a shared Rust core library (`nectarlink-core`) that implements peer discovery, cryptographic identity, QUIC session management, capability negotiation, persistent storage, and media/file framing. Native platform shells on Windows (`desktop/app`) and Android (`android/app`) bind directly to this core and provide OS integration and UI rendering.+NectarLink is built around a shared Rust core library (`nectarlink-core`) that implements peer discovery, cryptographic identity, QUIC session management, capability negotiation, persistent storage, and media/file framing. Native platform shells on Windows (`desktop/app`) and Android (`android/app`) bind directly to this core and provide OS integration and UI rendering.## System Topology@@ -99,7 +99,7 @@ The Windows desktop client combining a Rust service host with a Qt 6.12 Quick/QM- `media.rs`: Windows `GlobalSystemMediaTransportControlsSessionManager` (SMTC) integration for bidirectional Now Playing metadata and transport controls.- `ble_proximity.rs`: Windows WinRT BLE watcher and GATT advertisement reader for RSSI-smoothed proximity presence and auto-lock.- `local_api.rs`: Opt-in localhost HTTP/SSE server (`127.0.0.1:53320`) for CLI, PowerToys, Raycast, and Stream Deck integrations.- - `share_target.rs` and `shell_integration.rs`: Windows Share Target activation and Explorer context-menu verb registration (`Send to Phone with Nectarlink`).+ - `share_target.rs` and `shell_integration.rs`: Windows Share Target activation and Explorer context-menu verb registration (`Send to Phone with NectarLink`).- `setup.rs` (with `bridge/setup.rs` and `qml/setup/`): The installer's and uninstaller's window. The NSIS installer (`desktop/installer/nectarlink.nsi`) unpacks the app and starts it with `--setup`; the uninstall entry starts the installed app with `--remove`. The window runs the NSIS installer or uninstaller silently with administrator rights and shows its progress.- `updater.rs`: Automatic release update checker (`https://api.github.com/repos/thtbee/nectarlink/releases/latest`) and SHA-256 verified silent NSIS installer runner on installed desktop copies.@@ -121,7 +121,7 @@ The Android application written in Kotlin with Jetpack Compose (`compileSdk = 37## Discovery and Transport Architecture-Nectarlink uses `iroh` (`1.3`) to run a single QUIC + TLS 1.3 endpoint per device. Every paired connection is classified into one of three `ConnectionPath` variants (`core/nectarlink-core/src/node.rs`):+NectarLink uses `iroh` (`1.3`) to run a single QUIC + TLS 1.3 endpoint per device. Every paired connection is classified into one of three `ConnectionPath` variants (`core/nectarlink-core/src/node.rs`):| Path | Discovery Mechanism | Transport Path | Latency & Bandwidth Profile ||---|---|---|---|diff --git a/docs/technical/building-and-testing.md b/docs/technical/building-and-testing.mdindex 21d021e..dbc9aae 100644--- a/docs/technical/building-and-testing.md+++ b/docs/technical/building-and-testing.md@@ -1,6 +1,6 @@# Building and Testing-This document covers the pinned toolchain versions, environment variables, build commands, and test suites required to build and verify Nectarlink on Windows and Android.+This document covers the pinned toolchain versions, environment variables, build commands, and test suites required to build and verify NectarLink on Windows and Android.## Pinned Toolchainsdiff --git a/docs/technical/contributing.md b/docs/technical/contributing.mdindex 0b424c0..67ff6c5 100644--- a/docs/technical/contributing.md+++ b/docs/technical/contributing.md@@ -1,10 +1,10 @@# Contributing-This guide summarizes the repository conventions, module header requirements, protocol change rules, and pre-submission checks for contributing to Nectarlink. See also the root [`CONTRIBUTING.md`](../../CONTRIBUTING.md) and [`LICENSE`](../../LICENSE).+This guide summarizes the repository conventions, module header requirements, protocol change rules, and pre-submission checks for contributing to NectarLink. See also the root [`CONTRIBUTING.md`](../../CONTRIBUTING.md) and [`LICENSE`](../../LICENSE).## License-Nectarlink uses three licenses across the repository (see [`LICENSE`](../../LICENSE)):+NectarLink uses three licenses across the repository (see [`LICENSE`](../../LICENSE)):- **Core libraries** (`core/nectarlink-protocol`, `core/nectarlink-core`, `core/nectarlink-ffi`): [`MPL-2.0`](../../LICENSES/MPL-2.0.txt)- **Applications and CLI** (`desktop/app`, `desktop/vcam`, `android`, `cli`): [`GPL-3.0-or-later`](../../LICENSES/GPL-3.0-or-later.txt) with an [`app-store exception`](../../LICENSES/APP-STORE-EXCEPTION.md)- **Protocol specification and documentation** (`docs/`): [`CC BY 4.0`](../../LICENSES/CC-BY-4.0.txt)diff --git a/docs/technical/performance-budgets.md b/docs/technical/performance-budgets.mdindex dd5ff35..3d1f4fb 100644--- a/docs/technical/performance-budgets.md+++ b/docs/technical/performance-budgets.md@@ -1,6 +1,6 @@# Performance Budgets-Nectarlink treats startup latency, idle resource consumption, UI frame pacing, and bulk transfer throughput as regression-tested engineering budgets. Every metric below is taken from [`docs/PERFORMANCE.md`](../PERFORMANCE.md) and verified on hardware (`Windows 11 desktop + Samsung SM-S908E Android 14`).+NectarLink treats startup latency, idle resource consumption, UI frame pacing, and bulk transfer throughput as regression-tested engineering budgets. Every metric below is taken from [`docs/PERFORMANCE.md`](../PERFORMANCE.md) and verified on hardware (`Windows 11 desktop + Samsung SM-S908E Android 14`).## Target Budgets vs Measured Resultsdiff --git a/docs/technical/protocol-overview.md b/docs/technical/protocol-overview.mdindex 6163c49..a3c54b0 100644--- a/docs/technical/protocol-overview.md+++ b/docs/technical/protocol-overview.md@@ -1,6 +1,6 @@# Protocol Overview-The Nectarlink wire protocol (`nectarlink/0`) runs over a single mutually authenticated QUIC + TLS 1.3 connection per peer (`iroh` `1.3`). It multiplexes control messages, request/response RPCs, bulk file streams, real-time media streams, and unreliable low-latency datagrams without head-of-line blocking between independent features.+The NectarLink wire protocol (`nectarlink/0`) runs over a single mutually authenticated QUIC + TLS 1.3 connection per peer (`iroh` `1.3`). It multiplexes control messages, request/response RPCs, bulk file streams, real-time media streams, and unreliable low-latency datagrams without head-of-line blocking between independent features.## Specification Index (`docs/protocol/`)diff --git a/docs/technical/releasing.md b/docs/technical/releasing.mdindex 6d68783..8ff65ef 100644--- a/docs/technical/releasing.md+++ b/docs/technical/releasing.md@@ -1,6 +1,6 @@# Releasing-How a version of Nectarlink gets from `main` to people's devices, and how the+How a version of NectarLink gets from `main` to people's devices, and how theapps update themselves afterwards.## What a release is@@ -22,7 +22,9 @@ Both apps' updaters need all three: they only accept an installer thatplace it's set: the Windows app, the installer and the Android app(`versionName`, and `versionCode` derived from it) all read it. Use`MAJOR.MINOR.PATCH`; a pre-release such as `0.2.0-beta.1` is allowed, and- `[workspace.metadata.release] name` gives the release a name.+ `[workspace.metadata.release] name` gives the release a name. The+ README's download table links straight to the files, so change the+ version in its two links too.2. **Checks.** `./scripts/check.ps1 -Android` locally, and a green CI run onthe commit to release.3. **Tag and push.** `git tag v<version>` on that commit and push the tag.@@ -67,7 +69,7 @@ Signing. Either plugs in after `package.ps1` builds the installer, before[security model](security-model.md#automatic-updates-and-release-verification).- **Android** (`update/AppUpdater.kt`): checks daily from the connectionservice and when the app opens, and installs through `PackageInstaller`.- Android 12 and later skip the confirmation once Nectarlink installed the+ Android 12 and later skip the confirmation once NectarLink installed therunning version itself; the first update after a manual install asks once.## Testing an update before publishingdiff --git a/docs/technical/security-model.md b/docs/technical/security-model.mdindex 565490c..eb050ec 100644--- a/docs/technical/security-model.md+++ b/docs/technical/security-model.md@@ -1,6 +1,6 @@# Security Model-Nectarlink uses an end-to-end encrypted, mutually authenticated peer-to-peer security model with no central user accounts and no cloud storage. Every connection is authenticated at the transport layer by static Ed25519 device identities and authorized at the application layer by per-device capability toggles and interactive runtime consent gates.+NectarLink uses an end-to-end encrypted, mutually authenticated peer-to-peer security model with no central user accounts and no cloud storage. Every connection is authenticated at the transport layer by static Ed25519 device identities and authorized at the application layer by per-device capability toggles and interactive runtime consent gates.For the full audit record and vulnerability remediation history, see [`docs/SECURITY-REVIEW.md`](../SECURITY-REVIEW.md).@@ -123,7 +123,7 @@ Implemented in `desktop/app/src/updater.rs` (`win/http.rs`), `desktop/installer/- **What is accepted**: a published release (not a draft or pre-release) whose version is newer than the running one, with an installer named `Nectarlink-*-x64-setup.exe` (Windows, a plain file name) or `*-android.apk`, and a `SHA256SUMS.txt` that lists it. The download is rejected unless its SHA-256 matches. Android additionally refuses an APK not signed with the app's own key.- **Windows, installing without a prompt**: the app is installed per machine, so installing needs administrator rights. The installer registers the scheduled task **Nectarlink Update**, which runs `nectarlink-desktop.exe --update-service` as SYSTEM. Its security descriptor gives SYSTEM and Administrators full control and authenticated users read and execute only, so a signed-in user can start it but not change what it runs. The task takes no arguments or input from the user: it fetches the latest release itself and applies the checks above. When the user clicks **Update**, the app first downloads the installer itself (resumable, with progress) into `%ProgramData%\Nectarlink\updates` and checks it against the sums. The task copies that file into a new randomly named folder in `C:\Windows\SystemTemp` (writable only by SYSTEM and administrators) and checks the copy against the sums it fetched itself, so a file planted in the shared folder can only ever be the official installer. When there is no matching file, it downloads the installer into that folder itself. It then runs the installer with `/S` and logs to `update.log` in the install folder. The worst a user can do by starting it is install the latest official release early.- **Windows, when**: with **Install updates automatically** on, the app starts the task once nobody has used the PC for 10 minutes and nothing would be interrupted (mirroring, an app window, a transfer, a call, screen sharing, the webcam). It first starts a hidden relauncher, which reopens the app once the new version's `DisplayVersion` is in the uninstall key and the installer has exited, then quits. Without the task (copies installed before it existed) **Update** runs the installer with the usual UAC prompt.-- **Android**: with **Install updates automatically** on, the connection service checks in the background at most once a day and installs through `PackageInstaller` with `USER_ACTION_NOT_REQUIRED` (Android 12+, `UPDATE_PACKAGES_WITHOUT_USER_ACTION`). Android skips the prompt only when Nectarlink installed the current version itself; otherwise the user confirms from a notification.+- **Android**: with **Install updates automatically** on, the connection service checks in the background at most once a day and installs through `PackageInstaller` with `USER_ACTION_NOT_REQUIRED` (Android 12+, `UPDATE_PACKAGES_WITHOUT_USER_ACTION`). Android skips the prompt only when NectarLink installed the current version itself; otherwise the user confirms from a notification.- **Opt-out**: **Check for updates** and **Install updates automatically** in Settings on both apps. With checks off, nothing is fetched.- **Not yet**: release binaries are not code-signed (Authenticode) yet, so trust rests on HTTPS to GitHub and the release's checksums.diff --git a/docs/technical/storage-and-retention.md b/docs/technical/storage-and-retention.mdindex 2a257fe..6b887be 100644--- a/docs/technical/storage-and-retention.md+++ b/docs/technical/storage-and-retention.md@@ -1,6 +1,6 @@# Storage and Retention-Nectarlink persists all relational state in an embedded SQLite database (`nectarlink.db`) managed by `core/nectarlink-core/src/store.rs`, supplemented by a `KeyProtector`-encrypted clipboard vault (`core/nectarlink-core/src/clipboard_history.rs`) and bounded desktop notification state files (`desktop/app/src/notification_store.rs`).+NectarLink persists all relational state in an embedded SQLite database (`nectarlink.db`) managed by `core/nectarlink-core/src/store.rs`, supplemented by a `KeyProtector`-encrypted clipboard vault (`core/nectarlink-core/src/clipboard_history.rs`) and bounded desktop notification state files (`desktop/app/src/notification_store.rs`).## Data Directory Layout@@ -63,7 +63,7 @@ In addition to SQLite conversation threads, the desktop app maintains fast JSON-Implemented across `core/nectarlink-core/src/store.rs`, `core/nectarlink-core/src/node.rs`, and `core/nectarlink-core/src/transfer.rs`.-Whenever a user sends files, folders, links, clipboard payloads, voice recordings, handoff documents, task alerts, or camera requests while the target device is offline (or when the connection drops mid-operation), Nectarlink enqueues the action into `send_queue` and delivers it automatically when a session is established.+Whenever a user sends files, folders, links, clipboard payloads, voice recordings, handoff documents, task alerts, or camera requests while the target device is offline (or when the connection drops mid-operation), NectarLink enqueues the action into `send_queue` and delivers it automatically when a session is established.### Queue Item Kinds and Default TTLs (`QueueKind`)diff --git a/spikes/s1-qt-rust/qml/Main.qml b/spikes/s1-qt-rust/qml/Main.qmlindex d722364..576ac01 100644--- a/spikes/s1-qt-rust/qml/Main.qml+++ b/spikes/s1-qt-rust/qml/Main.qml@@ -11,7 +11,7 @@ Window {minimumWidth: 980minimumHeight: 640visible: true- title: "Nectarlink · S1 proof"+ title: "NectarLink · S1 proof"color: mica ? "transparent" : Theme.surface// The frame and the Mica tint follow the app theme, not the system one.diff --git a/spikes/s1-qt-rust/src/main.rs b/spikes/s1-qt-rust/src/main.rsindex 0a974a5..b5b1c53 100644--- a/spikes/s1-qt-rust/src/main.rs+++ b/spikes/s1-qt-rust/src/main.rs@@ -1,5 +1,5 @@// SPDX-License-Identifier: GPL-3.0-or-later-//! Spike S1: can Qt Quick + Rust deliver the Nectarlink design within the+//! Spike S1: can Qt Quick + Rust deliver the NectarLink design within the//! performance budgets? See README.md for what is measured and the results.mod bridge;@@ -19,7 +19,7 @@ fn main() {let mut app = QGuiApplication::new();let mut engine = QQmlApplicationEngine::new();if let Some(app) = app.as_mut() {- app.set_application_name(&QString::from("Nectarlink S1"));+ app.set_application_name(&QString::from("NectarLink S1"));}// The tray test closes the main window and keeps running, like tray mode.if std::env::args().any(|a| a == "--tray-test") {diff --git a/tools/powertoys-extension/Cargo.toml b/tools/powertoys-extension/Cargo.tomlindex ba4f2f7..f8fae97 100644--- a/tools/powertoys-extension/Cargo.toml+++ b/tools/powertoys-extension/Cargo.toml@@ -1,6 +1,6 @@[package]name = "nectarlink-ptrun"-description = "PowerToys Run & Command Palette extension helper for Nectarlink"+description = "PowerToys Run & Command Palette extension helper for NectarLink"version = "0.0.1"edition = "2024"license = "GPL-3.0-or-later"diff --git a/tools/powertoys-extension/README.md b/tools/powertoys-extension/README.mdindex 7784d03..a086257 100644--- a/tools/powertoys-extension/README.md+++ b/tools/powertoys-extension/README.md@@ -1,6 +1,6 @@-# Nectarlink PowerToys Command Palette / PowerToys Run Extension (`nectarlink-ptrun`)+# NectarLink PowerToys Command Palette / PowerToys Run Extension (`nectarlink-ptrun`)-`nectarlink-ptrun` is a standalone, zero-dependency Rust helper that connects Windows launcher tools (PowerToys Command Palette, PowerToys Run, Flow Launcher, Raycast for Windows) to Nectarlink's [Local Authenticated API](../../docs/api.md).+`nectarlink-ptrun` is a standalone, zero-dependency Rust helper that connects Windows launcher tools (PowerToys Command Palette, PowerToys Run, Flow Launcher, Raycast for Windows) to NectarLink's [Local Authenticated API](../../docs/api.md).## Building@@ -10,8 +10,8 @@ cargo build --release --manifest-path tools/powertoys-extension/Cargo.toml## Prerequisites-1. Open **Nectarlink → Settings → Local automation API** and turn on **Enable local automation API**.-2. Nectarlink writes `%LOCALAPPDATA%\Nectarlink\api-token.json` containing the loopback port (`53320`) and a 256-bit Bearer token.+1. Open **NectarLink → Settings → Local automation API** and turn on **Enable local automation API**.+2. NectarLink writes `%LOCALAPPDATA%\Nectarlink\api-token.json` containing the loopback port (`53320`) and a 256-bit Bearer token.## Usagediff --git a/tools/powertoys-extension/src/main.rs b/tools/powertoys-extension/src/main.rsindex f1dd42c..72031d0 100644--- a/tools/powertoys-extension/src/main.rs+++ b/tools/powertoys-extension/src/main.rs@@ -1,6 +1,6 @@// SPDX-License-Identifier: GPL-3.0-or-later//! `nectarlink-ptrun`: PowerToys Command Palette / PowerToys Run bridge for-//! Nectarlink's Local Authenticated API (`docs/api.md`).+//! NectarLink's Local Authenticated API (`docs/api.md`).//!//! Usage://! - `nectarlink-ptrun [--data-dir <dir>] query "<search>"`@@ -86,7 +86,7 @@ pub fn read_token_file(data_dir: &Path) -> Result<ApiTokenFile, String> {let path = data_dir.join("api-token.json");let raw = fs::read_to_string(&path).map_err(|e| {format!(- "can't read {} ({e}); enable the Local automation API in Nectarlink Settings",+ "can't read {} ({e}); enable the Local automation API in NectarLink Settings",path.display())})?;@@ -135,7 +135,7 @@ pub fn build_query_items(search: &str, timeline_items: &[Value]) -> Vec<PaletteIPaletteItem {id: "send-url".into(),title: format!("Open URL on phone: {q}"),- subtitle: "Send link to your phone via Nectarlink".into(),+ subtitle: "Send link to your phone via NectarLink".into(),action: "send-url".into(),arg: q.to_owned(),},@@ -190,7 +190,7 @@ fn api_request() -> Result<Value, String> {let addr = SocketAddr::from(([127, 0, 0, 1], cfg.port));let mut stream = TcpStream::connect_timeout(&addr, Duration::from_secs(2))- .map_err(|e| format!("can't connect to Nectarlink Local API at {addr}: {e}"))?;+ .map_err(|e| format!("can't connect to NectarLink Local API at {addr}: {e}"))?;let _ = stream.set_read_timeout(Some(Duration::from_secs(3)));let _ = stream.set_write_timeout(Some(Duration::from_secs(3)));@@ -211,7 +211,7 @@ fn api_request(stream.read_to_string(&mut resp).map_err(|e| e.to_string())?;let (_, json_body) = resp.split_once("\r\n\r\n")- .ok_or_else(|| "malformed HTTP response from Nectarlink Local API".to_owned())?;+ .ok_or_else(|| "malformed HTTP response from NectarLink Local API".to_owned())?;serde_json::from_str(json_body).map_err(|e| format!("invalid JSON from Local API: {e}"))}@@ -269,7 +269,7 @@ fn main() -> ExitCode {api_request(&cfg, "POST", "/v1/send", Some(&json!({ "paths": [path] })))}"notify" => {- let title = arg.unwrap_or_else(|| "Nectarlink".into());+ let title = arg.unwrap_or_else(|| "NectarLink".into());api_request(&cfg, "POST", "/v1/notify", Some(&json!({ "title": title })))}other => Err(format!("unknown action: {other}")),diff --git a/tools/xtask/src/notices.rs b/tools/xtask/src/notices.rsindex 05cbf14..55f7038 100644--- a/tools/xtask/src/notices.rs+++ b/tools/xtask/src/notices.rs@@ -51,11 +51,11 @@ pub fn run(args: &[&str]) -> Result<()> {let crates = shipped_crates(&metadata)?;let mut text = String::new();- writeln!(text, "Nectarlink for Windows: third-party notices")?;+ writeln!(text, "NectarLink for Windows: third-party notices")?;writeln!(text, "{}", "=".repeat(43))?;writeln!(text,- "\nNectarlink is free software under the GNU General Public License, version 3\n\+ "\nNectarLink is free software under the GNU General Public License, version 3\n\or later (LICENSE.txt). It includes the software below, under these terms.\n")?;write_qt(&mut text, &root)?;@@ -84,7 +84,7 @@ fn env_cargo() -> String {}/// The crates in the app's normal dependency graph, workspace crates left-/// out (they're Nectarlink's own).+/// out (they're NectarLink's own).fn shipped_crates(metadata: &Value) -> Result<Vec<Crate>> {let packages: BTreeMap<&str, &Value> = metadata["packages"].as_array()