Search results for:

A screen going blank doesn't necessarily signify a low or 0% battery. What happens if you press and hold the physical button?

@Gordon If you ever need characters to test or to "hard code," let me know. I can discuss the essential characters in all the European languages, including those in Cyrillic, although I'm guessing that would be going a bit beyond.

If your watch gains or loses time noticeably, I suggest installing the widget Adjust Clock by @malaire, which enables accurate timekeeping. Use of that would change Alessandro's statement slightly.

Text-based media may give odd results, including unwanted, undeserved remarks. @Gordon has enabled me to do things I've only dreamed of and deserves high credit and plaudits for his hard work and devotion, not to mention knowledge and skill.

That is unchangeable even if another boon would be easier workings with Apple's mobile phones. Apple doesn't make it easy, I know. Still, perhaps some day, even with Bangle 2.

Now with optional calendar date in two formats. Ordinal is shown, with dithered blue. (The colour #00f is too dark.) So as not to interfere with the time, the date appears briefly or not at all.

I've had a watch face in the app loader for a few years which may have no other user, and I'm about to produce a variant. Although Gordon may have a different answer, those interested in the topic the watches are allied to may be pleased to find them there.

In other words, it's research, and there seems to me no better place for the results.

As for colours, I don't need 64, but 8 are too few. I can get by, but 16 would be better by more than what the factor of 2 suggests. A little higher resolution would be good, also better accuracy if possible (although @malaire has taken care of that for this watch). I don't need more buttons, however.

All said, it's still a joy to work with this watch as it is and to see the results.

Thanks. I did reinstall the bootloader after you suggested that and before writing the above.

I feel much better, even if the watch may not :-) (The IDE still presents errors that aren't, occasionally.) Is a complete reset of all installations necessary?

And now for something completely different: dozenal time in imitation analog, with hands. Above is the explanation of the time reckoning, which is the same here. The four digits in the display immediately above are converted to hands, from left to right: red, yellow, green white. The white hand, which moves every 1.04167 second, may be shown or hidden.

Many thanks to @Andreas_Rozek for his model Bangle.js watch faces and his help with this project. Eventually this analog face should appear in the public app loader, along with the digital dozenal watch face already there.

(The time below is easily read as E3X.19 (E=eleven, X=ten). The equivalent on a traditional watch is 22:39:57.292.)

The problem continues but less often. Now the occasional error is only that a term is undefined, which it isn't. (Same term every time.) After that notification, reloading from RAM always works.

If I'm not doing something else wrong, is there possibly a bug in the IDE?

It says Flash. I assume it should be RAM, having now checked the Development page. Sorry for the very basic question.

"Send to Espruino."

In creating a new clock app, I find that occasionally loading it onto Bangle 2 fails and the IDE presents a lot of the code in many lines, then takes it away and presents:

echo(1)
undefined

Reloading almost always works, the above odd behavior occurring maybe 1 in 5 attempts, and only after I've changed a small detail (like color) in the code. Suggestions as to cause? Possibly a bug in the IDE?

I'm not a programmer/coder but am on my own for this glitch, which doesn't seem to occur on loading other code the same way.

Having used the beta of widadjust and the above-mentioned web page to check the time, I've probably come as close as I can to determining my watch's drift and fixing it. I'm still experimenting with a few details.

I'm surprised that others haven't commented on drift. It would be useful to know other estimates of that.

Thank you for that!

To others: I am testing this widget. It is working well.

I assume from the above multiple discussions of some weeks ago that the Bangle.js cannot use Apple's iOS time service in an efficient and reliable manner to regulate the watch's timekeeping via an iPhone. If that's incorrect, it would be helpful if someone would elaborate.

Meanwhile, other ways of regulation are being created (not by me).

No other reports of that, then? If not, I continue, not changing anything.

@Gordon
My watch "died" overnight. The standard battery indicator widget had indicated about 40%. I tried the technique you mentioned, and it worked. The display (only part of it) came back on with the battery still around 40%.

Is it possible that the watch kept running even though the screen was blank? I have reason to think that was happening. If it was, I don't know why the watch display shut off suddenly.

@Serj
Your help now takes on more importance. In view of malaire's solutions to regulate timing in a clock app, if restarting the watch becomes necessary only once every few days or longer, then doing it via the phone's connection seems to make the most sense.

Interesting! My first experiment with 210 ms/hr ended after 16 hours. The watch gained ⅓ to ½ a second, so about 600 ms/24 hrs. I don't know how linear that was. Success, regardless. While awaiting your further developments, I'll try a slightly high number, going towards your 0.68 figure. Then I may try halving it for every 30 minutes, although of course that gets close to 100 ms.

May there also be a good way to do this without setTime? One that would allow a smaller decrement. There's presumably a way to getMilliseconds.

I get it. I'll try 210 ms every hour.

Reply function not always working…reply is above.