-
I already implemented distance calculation on my dev repo. Only in km for now.
You can chose what to display in each line, steps or distance.But:
The widget takes too much memory now, it is not even possible to go to the settings app without running into memory problems. I will need someone to assist me with this.
I am going to open an issue now for that.Edit: there it is https://github.com/espruino/BangleApps/issues/296
-
-
-
-
-
Or did you write to flash?
Than you may have to reinstall the default apps:
https://www.espruino.com/Troubleshooting+Bangle.js#my-bangle-js-no-longer-boots-to-the-clock -
Hi,
I am using rather long variable names and a lot of long comments in my code. This is to make it as readable as possible.
Downside: The code gets very big and I run into memory problems too early.When uploading the code, I am using minifying to reduce the size.
Two questions:
- I experienced problems with the settings.js file when using minification. My guess is that is because variable names are not consistent anymore between files. Could that be?
- Does the app loader do some minification? I do not want to upload code without comments, but they really do not have to be on the watch. I do not think it does, because the comments are in the files on the watch. Can minifaction be enabled by some switch?
Thanks
ChristianThanks
- I experienced problems with the settings.js file when using minification. My guess is that is because variable names are not consistent anymore between files. Could that be?
-
For firmware update, see here: https://www.espruino.com/Bangle.js#firmware-updates
-
I created a pull request to the Bangle.js app loader: https://github.com/espruino/BangleApps/pull/290
-
-
Just provided a small update.
Readme shows changes made in new algorithm.Snippet:
Now every step is counted when in status 'active', if the time difference between two steps is not too short or too long.
To get in 'active' mode, you have to reach the step threshold before the active timer runs out.
When you reach the step threshold, the steps needed to reach the threshold are counted as well. -
-
-
-
-
As it is working pretty well for me, I would rule out:
- Bangle.js firmare
- GB widget on Bangle.js
- Gadgetbridge on phone (current version form F-Droid)
Which leaves us with:
- Phone settings (do not think so, as you made battery settings)
- Phone ROM
- Phone hardware
BTW, I am using a Pixel 4XL with current Android version.
- Bangle.js firmare
-
Still work in progress, but I want to get it out in the wild for you to test and to receive feedback.
I am still testing with the settings, but I am 90% satisfied.The goal was to filter out arm movement, but to still count real steps.
Please see the readme for details.Advantages:
- Good readability
- Arm movement filtering
- Step goal display
- 'Active' display
Disadvantages:
- Uses a lot of memory, but I am sure this can be improved by a real developer (so not me)
- Uses a lot of screen space, but this is needed for readability
- Good readability
-
I have my own, manual copy (not fork!) of the bangle.js github.
This is where I do all my crazy development stuff.
As soon as something is ready to be published, I copy the files over to my fork of the bangle.js github. Then I test if app installation is working as expected.
The I crate a pull request.This way I keep the crazyness and too many commits out of the fork and out of the bangle.js github.
No idea if there is a better way.
Example:
My bangle.js copy: https://github.com/Purple-Tentacle/BangleAppsDev
My bangle.js fork: https://github.com/Purple-Tentacle/BangleApps -
-
-
But that would only help for the unit (km/mi etc.) and not the calculation, right?