Got my F7X today and it was a step up from my F6X when it comes to the screen. My F6X must have had a «blueish backlight» that so many reported about, because my F7X was blackish. The funny thing is that my F6X screen was never as blue as the pics on…
Thanks Dave. I'll give it a go. That makes sense as the rest of the watch works fine so didn't think it would be a fault
Is this not something that could be handled with the Cryptography APIs? https://developer.garmin.com/connect-iq/api-docs/Toybox/Cryptography.html
I've had mine less than 12 hours, but I haven't noticed any connectivity issues any different from my 6X to my iPhone 13.
Same problem, also 11 speed cassette. My rear dropouts are fairly narrow (135mm) but can get it mounted with the 12x135 adaptor for the NDS, then have same issue you describe above. Looking at it the obvious thing to do is to move the cassette closer…
Still not fixed in 4.0.9
That was my impression. However, if the Garmin team was able to develop a cryptography library for CIQ, my understanding is that I would be able to create a secure connection by signing messages and sending raw bytes to the peripheral.
CIQ BLE only has basic stuff and no real security, See https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/adding-bluetooth-connectivity-to-your-connect-iq-projects
I am hoping to make an app that is able to interact with a BLE peripheral, and it needs to be able to create private keys and sign messages. Would it be possible to create a Monkey C library that can do this?
I am hoping to make an app that is able to interact with a BLE peripheral, and it needs to be able to serialize protobuf messages to be able to do this.
I have found chesapeaketechnology/BufMonkey on GitHub, but it does not appear to be fully functional…
