You are reading a single comment by @fanoush and its replies. Click here to read the full conversation.
  • Hi there !
    I recently got a Kospet ROCK (C16) smartwatch, that I almost instantly turned into a near-useless Espruino-powered tinkering playground thanks to the instructions shared by @fanoush and @jeffmer.

    I don't have a lot of experience in embedded stuff apart from playing a bit with adafruit's circuitpython, but I'm looking forward to make my watch vaguely useful again with some code of my own.

    I don't have a precise idea yet of what I want to do with it, apart from restoring its time and fitness abilities.

    Code will be here :
    https://gitlab.com/ddelemeny/watchapps

    Any other projects on this watch I should know about ?

  • I don't have a precise idea yet of what I want to do with it, apart from restoring its time and fitness abilities.

    Not sure about the fitness part, not even sure @jeffmer got the heartrate sensor working.

    Any other projects on this watch I should know about ?

    There is also eucWatch made by @enaon
    https://github.com/enaon/eucWatch/tree/main
    https://enaon.github.io/eucWatch/

    I tend to use a lot of closures in my code, and I'm wondering if the overhead of that coding style is going to be significant enough to be a problem.

    closures are not an issue but low memory in general is

  • There is also eucWatch made by @enaon

    Thanks for the pointer !

    Not sure about the fitness part, not even sure @jeffmer got the heartrate sensor working.

    I'm currently looking into the existing HRS code, any particular reason it would be difficult to implement ?

    closures are not an issue but low memory in general is

    What are the available strategies to profile memory usage on Espruino ?

About

Avatar for fanoush @fanoush started