WearOS pairing and data bridging support - #3662
Conversation
c0bd156 to
bc37184
Compare
…dging, media controls, and channel data streams Signed-off-by: namdamdoi68-oss <namdamdoi68@gmail.com>
bc37184 to
446b3c2
Compare
|
Hi @marvinlsilva / @microg team, Just checking in on this PR. I've rebased and updated the branch with clean squashed commits, fixed the Bluetooth RFCOMM UUID implementation, and verified that unit tests pass cleanly. Please let me know if there's anything else needed from my side for review. Thanks! |
|
Hey, could you please share a video of you pairing a WearOS watch with your phone running MicroG with your patch? |
|
Hi @TobiPeterG, Thanks for checking in! During development and verification, I used the Android Studio Wear OS Emulator (Wear OS 3.5 / API 33) paired with an Android Phone Emulator (API 33) running the patched microG build via ADB Bluetooth port forwarding (adb forward tcp:5601 tcp:5601). Environment details: Phone: Android AVD - Pixel 6 (API 33) with patched microG GmsCore |
So you have no physical device to test it with? |
|
Please don't misunderstand me, having the emulator work is already great, someone will just need to verify that it works on an actual device |
Adds WearOS device pairing over Bluetooth RFCOMM, notification and call bridging, media controls, and Channel API data streams to play-services-wearable. Includes unit tests for the new bridge components.
Closes #2843.