Closed LoriLori closed 2 years ago
Are you able to connect to the watch and list its services using NRF Connect, or does the connection end immediately?
No connection using using NRF Connect. Connection attempt takes 14s and ends with 133, turned off/on phone and blue tooth. Opened watches so I can investigate.
Okay, thanks for the test. The LF clock calibration should work, but there might be an issue with the binaries on GitHub. I'll recompile from the new branch (a lot of refactoring is currently taking place in order to upstream P8 support into the official InfiniTime source code, see https://github.com/InfiniTimeOrg/InfiniTime/pulls?q=is%3Apr+author%3AStarGate01 ).
@LoriLori I published a new release at https://github.com/StarGate01/p8b-infinitime/releases/tag/v1.9.0.2 , which I tested on my development (unsealed) P8a, P8b, and PineTime. I also verified the firmware on a brand new stock P8b.
I've seen a similar problem with P8b FW on my P8(a) watch that HAS LF. @LoriLori you should use P8a FW if it works. Bootloader features should save you in case of the non-working FW.
Please note that on LF crystal builds, the recovery uses the LF crystal as well (if you flash the provided one). In theory, the LFRC builds should run on devices which have a crystal just as well, but I have seen the contention issues @ildar is describing.
I will be updating the device names to MOY-*, to hopefully reduce confusion on what firmware to use.
@ildar is correct, the bootloader will roll back if the new firmware turns out to be broken.
Sorry, I can't test. Opening a watch I caused damage. Thanks for your work!
Can't connect via nrf connect (two different phones) or linux getting gatt error 133 or [CHG] Device XX:XX:XX:XX:XX:XX Connected: yes Failed to connect: org.bluez.Error.Failed I think LFRC doesn't get calibrated properly.