furiousmac/continuity

Apple Continuity Protocol Reverse Engineering and Dissector

continuity's Issues

TxPower on Nearby Info

It seems like TxPower in the Nearby Info advertisements is not really TxPower and is instead a device type.

Apple Watches always seem to be 26 (0x1a). Have you been able to make any rhyme or reason to what TxPower means?

AirPlay source message has a purpose.

From what I've observed the AirPlay source message causes an AirPlay target to(if supported) start it's AWDL interface. I'd suggest further testing and then adjusting the description.

nearby-info correct byte-type for Action-code?

Action-code is stated as uint8 (a full byte)?,
but deciphered only as 4-bit.

shouldnt it be type-marked as something like "uint4" ?

or clearly stated whats the high/low-part (from left to right/right to left?) of this divied byte?
maybe it could be clarified in clearly showing whats the low and high half-byte as nibbles?
https://en.wikipedia.org/wiki/Nibble#Low_and_high_nibbles

(the other half of the full byte (for the action-code) looks like as the 4-bit status-flags.)

Add message to the AirPods Pro 2 ?

With AirPods Pro 2, if you have engraving the case with Apple, the message is visible on the popup.

Is this a way to read the information ? Is there a specific protocol for that ?

Idk

Nearby-info structure different than in original paper

the document in the github here shows a different structure than in the original paper.
how come? what is the source of the github document here? some updates?

also the numbering 1-31 seems to be BITS, but the BT-Advertisment can not be longer than 31 BYTES?

https://petsymposium.org/2020/files/papers/issue1/popets-2020-0003.pdf

vs

https://github.com/furiousMAC/continuity/blob/master/messages/nearby_info.md

the 2019 Paper shows the byte for action code as nibbles , and here is one half location sharing, not status

https://petsymposium.org/2019/files/papers/issue4/popets-2019-0057.pdf