WIP: road to pair my TicWatch

[deadYokai]

Just trying to make a pair with my watch, no more

Many parts of code is just stubs, or workarounds, needed proper implementation

After 465f5f0 requires merging PR microg/Wearable#3 and pushing to maven (not relevant after 63a77a0)

P.S. maybe needed code cleanup

[deadYokai]

now maybe fixes #2444 ,

at least my Mobvoi Health going to pair screen (after TOS)

but code in rough state for now

[deadYokai]

now, my device is trying to pair via Mobvoi Health

[deadYokai]

now need to implement openChannel method (wip)

for now only rfcomm client supported

ble, network, server is not implemented

[ale5000-git]

@deadYokai
Please look at the errors here: https://github.com/microg/GmsCore/actions/runs/20686657931?pr=3204

[deadYokai]

@ale5000-git as i mentioned before

After 465f5f0 requires merging PR microg/Wearable#3 and pushing to maven

[deadYokai]

or i can try to move https://github.com/microg/Wearable/ into GmsCore repo and get rid of dependence

https://mvnrepository.com/artifact/org.microg/wearable/0.1.1

[ale5000-git]

Sorry I missed that point, then we have to wait for @mar-v-in for the decision of this thing.
In the meanwhile go ahead with the other parts you are working, thanks.

[mar-v-in]

I'd suggest to entirely move the content of the microg/Wearable repo into play-services-wearable/core module in this repo and then we can archive the microg/Wearable repo entirely.

[deadYokai]

just sharing with good looking logs, in my opinion (logcat)

P.s. still not paired yet

[deadYokai]

i cannot pinpoint why connection closing when channel tries to open

can anybody help me? like some logs maybe logs from watch (i cannot capture from my)?

[teccheck]

Just looked at your code quickly, and you're the first who even got the Bluetooth UUID right. Looks very promising, keep it up. 👍

I'll try to test your code, as soon as I can with my Pixel Watch.

EDIT: If you need more information about the protocol, hit me up. I'm happy to help :)

[teccheck]

I've added 3 commits to my branch containing all of your changes unrelated to proto. Feel free to take a look. If you want to cleanly include them in your branch, you can do so via git reset --hard HEAD~3 and git pull [remote name of my repo] wearable. Cheers :D

[teccheck]

I just noticed, that I made a mistake with the ChannelControl Type in proto. They should be:

CHANNEL_CONTROL_OPEN = 1;
CHANNEL_CONTROL_OPEN_ACK = 2;
CHANNEL_CONTROL_CLOSE = 3;

This was correct in the constants in ChannelManager, but with your last two commits that changed.

[deadYokai]

I just noticed, that I made a mistake with the ChannelControl Type in proto. They should be:

CHANNEL_CONTROL_OPEN = 1;
CHANNEL_CONTROL_OPEN_ACK = 2;
CHANNEL_CONTROL_CLOSE = 3;

This was correct in the constants in ChannelManager, but with your last two commits that changed.

[deadYokai]

i has a dilema, to implement A2AEncryption i need somehow integrate ukey2 and i don't know how to do it

[teccheck]

i has a dilema, to implement A2AEncryption i need somehow integrate ukey2 and i don't know how to do it

I'm quite sure, you don't need A2AEncryption for pairing. All the traffic, I've seen wasn't encrypted.

[deadYokai]

i has a dilema, to implement A2AEncryption i need somehow integrate ukey2 and i don't know how to do it

I'm quite sure, you don't need A2AEncryption for pairing. All the traffic, I've seen wasn't encrypted.

i just trying implement what i can for now, and for future is good to implement A2A encryption

[teccheck]

i has a dilema, to implement A2AEncryption i need somehow integrate ukey2 and i don't know how to do it

I'm quite sure, you don't need A2AEncryption for pairing. All the traffic, I've seen wasn't encrypted.

i just trying implement what i can for now, and for future is good to implement A2A encryption

Sure, that makes sense. But if it's a blocker for you, it might be better to work on other parts first, and look at that later, once there's nothing else left.