Ge0rG on Nostr: nprofile1q…m32kp Yeah, the BTLE layer 2 protocol isn't very exciting, and the ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq9lt4284mghqxekzm6n5njxurnxrxhqhrva2leusdsuu5ja5jeycqxm32kp (nprofile…32kp)
Yeah, the BTLE layer 2 protocol isn't very exciting, and the fragmentation and indirection between UUIDs and handles doesn't make it easy to follow. You should also query the device with https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp to get a map of the UUIDs and which ones are read/write. Maybe googling the device ID will yield prior work as well.
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqxsn2ksmgnh3qkpkhrhxwpe6h3kfj40yjxvqq8kg4hvx0ld4v6xkqjmmqp2 (nprofile…mqp2)
Yeah, the BTLE layer 2 protocol isn't very exciting, and the fragmentation and indirection between UUIDs and handles doesn't make it easy to follow. You should also query the device with https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp to get a map of the UUIDs and which ones are read/write. Maybe googling the device ID will yield prior work as well.
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqxsn2ksmgnh3qkpkhrhxwpe6h3kfj40yjxvqq8kg4hvx0ld4v6xkqjmmqp2 (nprofile…mqp2)