You are reading a single comment by @Robin and its replies.
Click here to read the full conversation.
-
Update to the latest cutting-edge, as soon as you can, for example
setLCDOffset
used by the bootloader was introduced after that build. [You can browse the diff since your version on github].(https://github.com/espruino/Espruino/compare/5439331ac8f0e5dee87bf8319af08738c6718df9...master)
Sat 2019.12.28
Partial Success!! (okay took an hour instead)
The following is for the Beta prototype. It may/might apply for the final release product to be shipped in March.
The key to this solution was the insight provided in #7 post by @AkosLukacs. Although I had attempted a clean boot and removal of all apps and re-install using the web app library page, I had no success.
save()
before dis-connecting or do the above sequence twice ;-)Ignore these errors
and on second pass
Now, I can see what all the fuss was about!! The 'Settings' menu appears!! Now on to see if I am able to get a watch app installed!
EDIT:
Still an issue with software compatability. I am able to load any of the clocks, and am able to set the default with the 'Settings' menu. However, the 'Back' option just renders a blank screen, forcing a reboot. Interestingly, now loading the 'Bootloader' from the 'apps' page does allow the default clock to load first, but now back to where the 'Settings' menu won't render with BTN2.