-
YOOOOO!!! That fixed it, thank you so much!
OK, so it is one of those two features I disabled. If you want to test more, here are two more
https://github.com/fanoush/Espruino/commits/f-2.25-no-ext32khz/
this one has only the external low speed oscillator disabled and is forked from latest 2.25 release. To get the build you click the green checkmark on the latest commit, then 'Details' on the "Firmware build / build_dfu (BANGLEJS2) (push)", then expand the "upload BANGLEJS2 build artifact" and the link to zipped build artifact is https://github.com/fanoush/Espruino/actions/runs/12569157706/artifacts/2376029447
again you need to extract it to get the DFU zipHere https://github.com/fanoush/Espruino/commits/f-2.25-no-dcdc/ is the other one disabled
https://github.com/fanoush/Espruino/actions/runs/12569255154/artifacts/2376043065Beware that the zip inside both artifacts has same name as both is one commit on top of same version.
Does this mean that a normal version will always not work? And is the watch going to behave normally going forward using this version, or do you think it will still need to be replaced?
Yes, as long as normal version keeps it enabled you would need custom build. It is few clicks on github website to make your own build but still annoying. And you got faulty watch that passed QA by mistake with slightly worse battery life. It is up to you and @Gordon to sort this out. If you can easily get it replaced then I'd go for it. I heard people e.g. in Brazil(?) pay import taxes that makes that cost too high so it depends.
YOOOOO!!! That fixed it, thank you so much!
Does this mean that a normal version will always not work? And is the watch going to behave normally going forward using this version, or do you think it will still need to be replaced? Or did getting it to work normal once mean it will keep acting normal assuming something else doesn't happen?
Again thank you for the help & your patience with all my questions, this is my first foray into this kind of thing :)