View Single Post
Posts: 287 | Thanked: 862 times | Joined on Dec 2015
#226
Originally Posted by ruff View Post
Ok, then we need logs from watches to understand why it's nacking appmsg. The message is fairly simple - simple scalar value, nothing what could potentially be wrongly serialized.
I tried to switch the type of that first request for the token list to different types, but that didn't help. It could still be bad serialization, but there's only so many ways you can send a '1'.


Originally Posted by ruff View Post
Does anyone have annotated firmware disassembly accidentally? To look for possible reasons to nack.
Appmessages on the whole work fine, but I think it's the binary on the watch that decides whether to ack or nack in response. I found the source:

https://github.com/cpfair/pTOTP

I think the next step is to confirm that iOS and Android work with older watches on v3, then we can try to contact the author.

Last edited by abranson; 2016-04-08 at 07:22.
 

The Following 2 Users Say Thank You to abranson For This Useful Post: