-
-
I upgraded to 2v11.9 and now all buzzes are not stopping. Previously it was at random times. Anyone a similar experience?
If so, please attach a short info to https://github.com/espruino/Espruino/issues/2119 -
-
-
-
-
-
Looks great. BTW: My two Bangles had the strap "thing" mounted with the pin on different sides. And it makes a HUGE difference. The pin on the inner side does not keep the strap out of the way, the other one does. So a quick solution is to turn the pin to the inner on the outer side of the strap.
[I should make a picture :-)]
-
-
-
-
Shame it's not been released into the wild, I bet a lot of people would be interested in using something like that!
I'll put the Bangle 2 version on a Github repo. It's not in the Bangle app loader just because I feel that it violates some of the Bangle principles, for example it shows Gadgetbridge notifications smoothly integrated in the watch face and not via the notifications app. So you would have to uninstall some things and the widgets in the top is actually one widget, not four. But I'll make an adapted one next year.
-
Just a thought: I personally prefer touch to prolong the life of the button for a simple reason: when the button will die the watch is almost useless. I would not stress it with app use. I created a watch face with two start buttons for actions/apps (not in the store for some reasons). With additional left/right swipe I have four "actions" via touch in direct access (e.g. integrated music player, launcher, BT on/off, here: blue when BT is on) without stressing the physical button.
Maybe you can take the approach to have a single virtual button, which launches different apps depending on the number of touches?
-
Sorry Gordon that I have to come back with this.
if (x) clearTimeout(x);x = setTimeout(function() { x=undefined; ... },...)
This pattern leaves dangeling handles not only in theory, but also on the watch. clearTimeout is never called. If you have no timeout, then you create one. When the function is executed on time, you delete first your handle to this timer. But when the handle is lost the timeout never gets cleared, because there is no handle to it.
Just a note of removing chimeTimer=undefined - chimeTimer will still be set to the ID
of the timer that has now finished,Shouldn't this be done by clearTimeout? I feel that the problem is here.
I tried multiple alternative solutions for this. All end up in a sudden infinite buzzing after 10-15 hours and FIFO_FULL. The FIFO_FULL also appears with the Anton clock, which also uses this pattern. I'm a JS developer, but I'm really struggeling to develop a pattern which does work. Any logical correct solutions to the timer problem do not work. If you use apps this will never become visible, because everything is reset with app change.
The strange thing is: All was fine also on v1 until approx a year ago. Did you change the behaviour of timers in the past?
What should work should look like this:
function planChime() { if (chimeTimer) { clearTimeout(chimeTimer); } chimeTimer = setTimeout(function() { Bangle.buzz().then(() => { planChime(); }); }, 3600000 - (Date.now() % 3600000)); }
or at least
function planChime() { if (chimeTimer) { clearTimeout(chimeTimer); chimeTimer=undefined; } chimeTimer = setTimeout(function() { Bangle.buzz().then(() => { planChime(); }); }, 3600000 - (Date.now() % 3600000)); }
But it does not.
-
https://lospec.com/palette-list/3-bit-rgb
in code: g.setColor(r,g,b);
r,g, b = 0| 1(ok, I was too slow ...)
-
-
-
for IP67 meaning (as per kickstarter - "IP67 Waterproof" ) see https://en.wikipedia.org/wiki/IP_Code
6 = Dust-tight
7 = Immersion, up to 1 meter
To me that means I can drop it to bathtub by mistake or use it in rain, not to swim with it.You are right. The best you can expect from IP67 is that it works after washing hands and get accidentially a wet watch, getting a bit water during rain on it or in the very best case a short drop into water.
1 meter means the pressure of 1m water column. When the water has a higher pressure (e.g. moving arms in water, water stream) it's far beyond specification.
-
Was just curious if others had experienced battery life issues.
I don't think it's an issue to have 4-5 days, especially compared to other watches. It depends really on the use. If you lay it on the desk it will last virtually forever, if you are wearing it 7 days+, if you do things with it 4-5 days.
BTW: My Bangle 1 is on the desk (not moved) running for over a month now with a clock face updated every second.
-
-
Until now it works, but the buzz problems in the past had happend very randomly.