You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Post there an exact error you are getting. If it is about failed signatures in other parts of the code, it well >might be that you subsequently trying to fetch things again and again without disconnecting the watch >and something is just stuck in a buffer that was not flushed. Disconnecting the watch before the new >attempt might help if that was an issue.
I'll post the exact error later, there is a way to read a dump bin file without the watch connected?
Because my watch battery is getting bad and I don't want to connect and disconnect the watch several times.
The text was updated successfully, but these errors were encountered:
The binary data saved are just whatever was requested and received from the watch. Sent commands are not stored. That is if no READ_SETTINGS was issued, then there would be no settings stored in a binary dump. Moreover if there was an incorrect number of bytes read, it would be stored that way in a dump. So it was mostly useful for me in initial stages. One idea would be to keep reading 1 byte at a time and flushing output indefinite number of times upon issuing READ_SETTINGS, then disconnecting the watch. Another option if you have an access to Windows machine, is to use proxy DLL (or maybe just Wireshark with USB packet capture) and record communication for original software.
I'll post the exact error later, there is a way to read a dump bin file without the watch connected?
Because my watch battery is getting bad and I don't want to connect and disconnect the watch several times.
The text was updated successfully, but these errors were encountered: