Beginner seeking details

[ronaldheld]

I flashed backed to Infinitime, to try the procedure and test out 1.7.0.  
I presume that I need to set up an development environment running under windows?

[danielt]

I presume that I need to set up an development environment running under windows?

For wasp-os? A GNU/Linux distro is the best tested way to develop for wasp-os. I'm told you can run the simulator and build binaries on Windows using WSL2. This is enough but anything in the app guide that relies on wasptool cannot run on Windows (unless someone ports wasptool to Windows). Additionally although there's been talk of documenting how to configure Windows from time to time I've never managed to get anyone to add it to the documentation.

If your daily driver laptop is Windows-only then (again, I'm told that) a Raspberry Pi 4 can be a good option.

[ronaldheld]

I presume that I need to set up an development environment running under windows?

For wasp-os? A GNU/Linux distro is the best tested way to develop for wasp-os. I'm told you can run the simulator and build binaries on Windows using WSL2. This is enough but anything in the app guide that relies on wasptool cannot run on Windows (unless someone ports wasptool to Windows). Additionally although there's been talk of documenting how to configure Windows from time to time I've never managed to get anyone to add it to the documentation.

If your daily driver laptop is Windows-only then (again, I'm told that) a Raspberry Pi 4 can be a good option.

It sounds as if I will not be installing the development SW soon.
For right now, are there are Wasp-OS firmware from others I can flash? Also Gadgetbridge.is only side loaded and which version should I be using?

[danielt]

Latest Gadgetbridge is found here: https://f-droid.org/packages/nodomain.fr...getbridge/

[ronaldheld]

Latest Gadgetbridge is found here: https://f-droid.org/packages/nodomain.fr...getbridge/

I got the developer of the Star Trek firmware to create a file for me. When I flashed it, I got Init SPINOR FAILED. Do you know what that means, and can it be corrected?

[danielt]

Latest Gadgetbridge is found here: https://f-droid.org/packages/nodomain.fr...getbridge/

I got the developer of the Star Trek firmware to create a file for me.  When I flashed it, I got Init SPINOR FAILED.  Do you know what that means, and can it be corrected?

This is likely to be caused by building against an outdated version of https://github.com/daniel-thompson/micropython-eeprom (this gets checked out as a submodule and appears in wasp/drivers/flash ). The newer versions have code to wake the SPINOR from deep sleep.

It will probably also clear itself if you let the battery run down to completely flat (letting the battery run out has the effect of resetting the SPINOR which also releases it from deep sleep).

[ronaldheld]

Latest Gadgetbridge is found here: https://f-droid.org/packages/nodomain.fr...getbridge/

I got the developer of the Star Trek firmware to create a file for me.  When I flashed it, I got Init SPINOR FAILED.  Do you know what that means, and can it be corrected?

This is likely to be caused by building against an outdated version of https://github.com/daniel-thompson/micropython-eeprom (this gets checked out as a submodule and appears in wasp/drivers/flash ). The newer versions have code to wake the SPINOR from deep sleep.

It will probably also clear itself if you let the battery run down to completely flat (letting the battery run out has the effect of resetting the SPINOR which also releases it from deep sleep).

The only solution is to have the Star Trek code upgraded to Wasp-OS 0.4.1?

[danielt]

This is likely to be caused by building against an outdated version of https://github.com/daniel-thompson/micropython-eeprom (this gets checked out as a submodule and appears in wasp/drivers/flash ). The newer versions have code to wake the SPINOR from deep sleep.

It will probably also clear itself if you let the battery run down to completely flat (letting the battery run out has the effect of resetting the SPINOR which also releases it from deep sleep).

The only solution is to have the Star Trek code upgraded to Wasp-OS 0.4.1?

It's not really up to me!

However there are lots of ways to fix it: you could upgrade to latest wasp-os, you could upgrade just micropython-eeprom, you could write different code to wake the SPINOR from deep sleep or, as mentioned above, you could let the battery run flat.

[ronaldheld]

This is likely to be caused by building against an outdated version of https://github.com/daniel-thompson/micropython-eeprom (this gets checked out as a submodule and appears in wasp/drivers/flash ). The newer versions have code to wake the SPINOR from deep sleep.

It will probably also clear itself if you let the battery run down to completely flat (letting the battery run out has the effect of resetting the SPINOR which also releases it from deep sleep).

The only solution is to have the Star Trek code upgraded to Wasp-OS 0.4.1?

It's not really up to me!

However there are lots of ways to fix it: you could upgrade to latest wasp-os, you could upgrade just micropython-eeprom, you could write different code to wake the SPINOR from deep sleep or, as mentioned above, you could let the battery run flat.

I did let the battery drop to 0. After I charged it a short while I saw the pinecone then blank screen. It was charged to about a third, before I could get into the bootloader and reflash 0.4.1. until then the screen was blank.
I suppose the originator of the code needs to upgrade to 0.4.1 and create a new .zip file?

[danielt]

I suppose the originator of the code needs to upgrade to 0.4.1 and create a new .zip file?

That really is up to @graynada .

These days wasp-os has better support for alternative watch faces (https://wasp-os.readthedocs.io/en/latest...apps.faces ) so one option would be to add a themed watch face to the upstream wasp-os repos (although that will lead us to some hard choices because we have more or less run out of flash at the moment).