GB-M0-R5 — Market / OSS Reuse Gate

[PNHD]

Goal

Prevent GalaxyBridge from re-implementing functionality that already exists in usable commercial or open-source products.

Policy

For every subsystem, evaluate in this order:

1. existing commercial product behavior
2. public OSS implementation
3. license compatibility
4. code-quality / hardware evidence
5. reuse/fork/import if legally compatible
6. implement only the missing or inferior parts

Current reuse classifications

APPROVED_FOR_CODE_REUSE

• k97/WearBridge — MIT — ANCS/Wear OS/iOS companion baseline
• rajtiwariee/watchbridge — MIT — Galaxy Watch-oriented ANCS lifecycle reference/optional code reuse

For imported/substantially derived MIT code:

• preserve copyright/license notices
• record exact upstream repo + commit SHA
• maintain THIRD_PARTY_NOTICES.md
• refactor/package under GalaxyBridge architecture where appropriate

REFERENCE_ONLY

• timschneeb/GalaxyBudsClient — GPLv3. Do not copy implementation into the main GalaxyBridge codebase unless the PM intentionally accepts GPL obligations for the relevant distribution. Protocol facts/wire behavior may be independently implemented.
• GuiyeC/Aerlink-for-Android — no clear license verified; architecture/behavior reference only.
• Merge / Bridge / SyncWear commercial apps — benchmark UX/features/reliability only.

Required next audits

• pin upstream commits and license notices
• identify exact MIT modules worth importing for R2
• compare native Android GATT vs Nordic BLE library approach
• benchmark known reconnect/background/battery weaknesses
• audit Apple Media Service before building custom media transport
• keep R4 Buds work independent while its current Codex writer runs

Stop rule

Do not merge reuse code into feature/gb-m0-feasibility while another writer is active. Stage on an isolated branch and integrate after PM review.

[PNHD]

SOURCE REUSE AUDIT — PASS 2 (2026-08-11)

APPROVED_FOR_CODE_REUSE / DEPENDENCY

k97/WearBridge

• License: MIT
• Pinned snapshot: c9ff912b9e87bb679c63c863c6f7df6e97d06e52
• Reuse targets: ANCS constants, Notification Source parser, Control Point writer, fragmented Data Source assembler, call/Telecom behavior, filtering rules, unit-test semantics, documented Wear/Samsung gotchas.
• Improvement requirement: replace ad-hoc GATT timing with deterministic queued operations; bound buffers/timeouts; Galaxy Watch6 endurance/battery validation.

rajtiwariee/watchbridge

• License: MIT
• Current audited tree: eb489234673eb91dbbf25c9a976500e3929cd909
• Reuse targets: explicit connection state machine, first-pair advertising/bonding flow, reconnect/session-reset and foreground-service architecture.
• Do not inherit its Nordic 2.7.3; dependency is stale relative to current stable.

nordicsemi/Android-BLE-Library

• License: BSD-3-Clause
• Current main snapshot audited: 4a86e6c6b2631a29d7de6c5789b11326733f1503
• Current stable dependency audited: no.nordicsemi.android:ble-ktx:2.11.0
• Preferred for R2 generic Android GATT transport because it already supplies operation queues, retries, service discovery, bonding, Service Changed handling, long-packet splitting/merging, MTU/PHY/RSSI, timeouts, errors and coroutine/Flow support.
• Upstream Kotlin BLE v2 is still described as early-development/not recommended for production; do not use it in M0.

S-ResearchStack/app-sdk (Samsung Health Research Stack)

• License: Apache-2.0
• Pinned research snapshot: c489bb9da86b24fef1e340e877511d635f618175
• Reuse targets for R3: generic Samsung Health Tracker callbackFlow repository, HR+IBI, ECG, BIA, SpO2, raw PPG channels, accelerometer, sweat-loss mappings and matching tests.
• Import only wearable sensor acquisition pieces; do not pull the research backend/web/study stack.

coredevices/PebbleOS — AMS subsystem

• Relevant files carry Apache-2.0 SPDX headers.
• Pinned research snapshot: 3cb06ce9034bc650741c3b76fe98cb5cd33aef61
• Reuse/adapt test semantics for future Apple Media Service support: service discovery, Entity Update subscription/registration, rediscovery reset, resource retry, and remote-command mapping.
• Implement production Kotlin transport using current GalaxyBridge/Nordic stack rather than porting Pebble firmware architecture wholesale.

REFERENCE_ONLY

timschneeb/GalaxyBudsClient — GPLv3

• Use protocol/wire facts and behavior as interoperability research only. No implementation copy into main GalaxyBridge codebase unless GPL obligations are explicitly accepted later.

Freeyourgadget/Gadgetbridge — AGPLv3 (GitHub mirror archived; project moved to Codeberg)

• Independent cross-check source for Buds2 Pro behavior and feature coverage.
• Archived changelog confirms initial Galaxy Buds2 Pro support existed by v0.73 and later recognition fixes.
• No code copying into GalaxyBridge main codebase.

GuiyeC/Aerlink-for-Android — no clear license verified

• Reference-only for ANCS/AMS/BAS/CTS behavior.

KhaosT/AMS-Reference — no license detected

• Protocol/reference-only.

Merge / Bridge / SyncWear — proprietary/commercial

• Benchmark features/UX/reliability only.

DEFER / REJECT FOR M0

• Whole Android/Wear testing mega-frameworks that add unrelated DI/screenshot/test infrastructure.
• Full Samsung Research Stack backend/web portal.
• Nordic Kotlin BLE v2 while upstream still marks it early-development.
• Generic Flutter/React Native mobile frameworks; GalaxyBridge remains native Swift/Kotlin.

ARCHITECTURE CONSEQUENCE

1. R2 should be Nordic BLE 2.11 transport + adapted permissive ANCS implementation, not a greenfield GATT stack.
2. R3 should be adapted Samsung Research Stack sensor acquisition + native GalaxyBridge BLE + native HealthKit, not a custom Samsung sensor wrapper from zero.
3. Future media control should use Apple Media Service (AMS), not a custom media protocol.
4. R4 remains clean-room for Buds protocol implementation, cross-checking GPL/AGPL sources plus hardware evidence.

No application branch was modified by this audit; active R4 writer remains isolated.

[PNHD]

SOURCE REUSE AUDIT — PASS 3 (Buds2 Pro / spatial)

APPROVED_FOR_ADAPTATION

timschneeb/BudsPro-Headtracking

• License: MIT
• Pinned snapshot: 63b321aa0536fd28233eaaf3a05c4f3b3f8201fe
• Scope worth adapting only after base Buds management transport works:
  • BluetoothService.py: modern 0xFD / 0xDD frame shape, response/fragment bits, CRC16 packet construction
  • SpatialSensorManager.py: spatial enable/data/control IDs, attach/detach/keepalive lifecycle, quaternion extraction
• Do not port Python architecture literally; translate only the small protocol/state-machine semantics into the GalaxyBridge Kotlin transport layer and add proper bounds/timeouts/tests.
• Hardware caveat: repository issues show Buds2/Buds2 Pro can find/connect to a FACTORY RFCOMM service yet fail to produce stable spatial data or eventually disconnect/stutter. Thus source reuse is allowed, but compatibility is unproven.

REFERENCE_ONLY — NEW CROSS-CHECK DETAIL

Freeyourgadget/Gadgetbridge — AGPLv3

• Archived GitHub snapshot: a0948ee1cbc2a870f91d313f8e37df5f524465f7; project moved to Codeberg.
• Has a dedicated GalaxyBuds2ProDeviceCoordinator and Buds2 Pro settings matrix.
• Independently confirms case/left/right battery and controls for noise mode, voice detect, ambient customization, EQ, touch, double-tap edge, in-ear detection, seamless connection, one-earbud noise control, balance and game mode.
• Its protocol also independently exposes the same broad 0xFD ... CRC16 ... 0xDD message family and multiple command families.
• No code copying into GalaxyBridge due AGPL.

CRITICAL R4 TRANSPORT FINDING

There is a real upstream disagreement that must be settled by hardware, not assumption:

• current GalaxyBudsClient Buds2 Pro spec selects custom SppNew = 2e73a4ad-332d-41fc-90e2-16bef06523f2
• Gadgetbridge selects standard SPP UUID 00001101-0000-1000-8000-00805f9b34fb for Buds2 Pro
• MIT BudsPro-Headtracking enumerates standard UUID 00001101-0000-1000-8000-00805f9b34fb and filters service names GEARMANAGER / FACTORY

Therefore the product diagnostic should enumerate all actual SM-R510 SDP records and record UUID + service name + channel. A probe of only one UUID is insufficient evidence for RFCOMM_UNAVAILABLE.

CURRENT BUDS2 PRO FEATURE MATRIX FROM CROSS-SOURCE RESEARCH

Strongly corroborated / worth targeting after transport gate:

• case + left + right battery
• ANC / ambient / off noise controls
• voice detect + timeout
• ambient level/tone customization
• EQ preset
• touch lock / touch-and-hold behavior
• one-earbud noise-control option
• audio balance
• seamless connection option
• game/latency mode
• in-ear state/settings

Present in the broader GalaxyBudsClient capability matrix but requiring separate validation before product commitment:

• fit test
• charging state
• head tracking / spatial sensor
• auto-adjust sound
• rename
• SmartThings Find-related behavior
• Bixby-specific behavior
• firmware operations (remain out of scope/safety-restricted)

ARCHITECTURE CONSEQUENCE

Base R4 must prove safe simultaneous iPhone audio + Watch management first. After that, spatial/head tracking should be a separate spike based on the permissive MIT protocol source above rather than reverse-engineered from zero.

[PNHD]

SOURCE REUSE AUDIT — PASS 4 (iOS BLE test infrastructure)

APPROVED AS TEST-ONLY DEPENDENCY

nordicsemi/IOS-CoreBluetooth-Mock

• License: BSD-3-Clause
• Current stable audited release: 1.0.6 (published 2026-05-26)
• Purpose: simulator/unit/UI testing for CoreBluetooth-based code without pretending the simulator proves physical BLE behavior.
• Useful because it wraps/imitates CoreBluetooth types and can forward to native CoreBluetooth on physical iOS devices while supplying mock peripherals in simulator/tests.
• SPM-supported.

Recommended use in GalaxyBridge:

• protocol/state-machine tests
• service/characteristic discovery flows
• malformed/fragmented notification scenarios
• disconnect/reconnect state transitions
• UI diagnostic state tests

Do NOT let mock success satisfy any R1/R2/R4 hardware gate.

REJECT AS PRODUCTION BLE DEPENDENCY FOR NOW

RxBluetoothKit

• Apache-2.0 and historically mature, but latest public release surfaced in audit is from 2020 and it brings RxSwift abstraction that GalaxyBridge does not otherwise need.
• Native CoreBluetooth remains simpler for the iOS production side.

Bluejay / older CoreBluetooth wrappers

• useful historical design reference for serialized BLE operation queues/background restoration, but not preferred as a new production dependency for a 2026 Swift/iOS project without stronger current-maintenance evidence.

CONSEQUENCE

• Android/Wear production BLE: stable Nordic Android BLE Library 2.11.0.
• iOS production BLE: native CoreBluetooth, narrow GalaxyBridge adapter.
• iOS BLE tests: Nordic CoreBluetooth Mock 1.0.6 is approved if/when tests benefit from it.
• Physical hardware remains source of truth.