Search results for:

I'm still having almost no problem getting a GPS fix with my Bangle.js 1. With the 2 I hadn't been able to get a fix until I took HughB's suggestion and laid the watch on something outdoors, keeping it still for about 5 minutes. Then I got a fix, wth 5 satellites.

@MaBe I assume that show color is only for Bangle.js 1. Nice displays.

@Andreas_Rozek The color wheel is a good addition, thanks. Is the entire area covered by a color tappable? Sometimes it seems like just the edge, to get the right answer and avoid getting black or white.

Could a future firmware upgrade for Bangle.js 2 improve color, or is there a limitation making that impossible? (Gordon's on a well-deserved holiday.)

On the bottom: 00F. On the top: 08F. Photos not great but you get the idea.

Thanks to both of you. Very helpful. I needed the "official" rainbow colors, which seem like F00, F80, FF0, 0F0, 00F, F0F. Because on a black background 00F is nearly unreadable, I'm using 08F. 0FF looks too green.

Those'll do, although they're not ideal. Even one more bit for color would've helped.

I missed the jest because I didn't see initially whom he was responding to.

Given the wacky things I've done in online clocks (including in some having the numerals move throughout the day, and in others using negative numbers), I tend to take any clock request seriously. I shouldn't.

If he goes back too far, there won't be any smart watches :-)

[Original post here deleted. See below for why.]

Maybe it's obvious—I got acceptable results using things like #FF8000 for orange (full red, half yellow). I'm not a fan of 3-bit colour, certainly in comparison with Bangle.js 1. Fortunately, I'm not drawing detailed pictures, and the number of users of my app won't likely exceed 10—in binary.

With my clock (Dozenal Time 2), I've found that drawing it continually may create a notable drain on the battery. (I'm testing it, and I realize the drain may result partly from the way the code works.) The version waiting to get into the public Bangle.js 2 app loader draws the clock for 15 seconds, within which the initial backlit time is determined by the LCD setting.

I first thought that that's enough. But I've run my Bangle.js 2 now with the backlight-off option (clock still running) for several days. It's better that way, more like the usual watch faces that don't disappear, and there's not often a need to activate the backlight, which there would be with the display off.

Buried up there is a question about the (simplest) way to stop a clock display from disappearing and keep it running. I've probably now solved that for this watch. Testing it.

Thanks to all those who commented.

A little late in the game, I've seen that 3-bit colour doesn't distinguish orange from yellow. With some flexibility (shades of the colours don't matter), I need the six rainbow colours for the only app I've produced, which works fine on bangle.js 1, with its better colour.

Using 0.5 for the colours instead of only 1 or 0 for RGB on bangle.js 2 with g.setBgColor seems to make a difference. Am I dreaming?

Currently the above watch screen goes blank 5 seconds after the lock icon comes on. Is there a way to write a line of code to keep the bangle.js 2 on (in screen lock mode) and, of course, the clock still running? I tried importing some code from the default Anton watch face (which stays on), without success so far, possibly because of the way my whole watch code is written.

But I have to disturb the code as little as possible, because its creator left the project, and I'm no coder.

Thanks for that. I removed the invalid button references before starting on bangle.js 2. I've not seen the NRF error. I did insert Gordon's code, which works fine, and tweaked all the sizes and positions. I don't see the LCDMode error on uploading to the watch from the computer, only in the emulator itself.

Next step will be to see if the watch uploads from one of the bangle.js app loaders. Not a great photo, and the colors remain a small issue, but it seems to work now:

I did solve my problem as Gordon suggested. The loop also affected BTN1, however. But it does seem I did something to cause the loop, which otherwise hasn't occurred.

The dozenal time watch, sometimes called Doztime. Sorry, I don't know where yourapp.boot.js is found… (or myapp.boot.js) — not finding much yet in documentation, although it seems .boot1 etc. are added to code by Espruino under most conditions.

What to do about that, I don't know.

I've discovered that I can actually send the code for my watch to bangle.js 2, and I've solved most of its problems. So are the above documented bugs affecting only the emulator?

Trying to convert an app for watch version 2, I get this set of errors:

Uncaught Error: setLCDMode is unsupported on this device
at line 5 col 13 in .boot1
global.BTN1=BTN3; global.BTN3=_;

at line 41 col 19 in .bootcde
Bangle.setLCDMode();

While I can get rid of the second instance at line 41, I don't know where .boot1 is and so can't see the correct line 5 or find that first error.

Any suggestion?

(Not about version 2)
Hmm. In 2v11 on Bangle.js 1, on trying to boot, the watch went into a loop. Holding BTN3 down, also a loop. I needed a clean restart…after doing who knows what to bring the foregoing about.

I removed all apps, etc., and then was good to go once again.

In Web IDE, it's necessary only to select the upper right settings icon, choose flasher on the left, and follow the instructions. I've installed 2v11 on both version 1 and version 2 of the watch.

Thanks. Process looks cumbersome. Web IDE worked.

Installing updated firmware using NRF Connect doesn't work on my iOS 14. Message is that the device (iPhone) doesn't support NRF Connect. Updating using the web IDE is easier.

(Often instructions assume serious coding ability, detailed knowledge of Bangle, and Android devices. I have none of those.)

I had my watch face on Pebble also, plus weather data that I can't bring in to Bangle because the required iOS connection is lacking. Some day…

Thank you. When you're available, let's communicate again.

I suppose I could put the two toggles into Settings. May be more complicated.

I've looked at the layout and the tutorial for Bangle.js version 2. The main thing I need is to convert two toggle switches that in version 1 were BTN4 and BTN5. The toggle functions aren't changing; just the new location of the switches needs to be specified. In version 1, it was only this:

setWatch(function(){ toggleTimeDigits(); }, BTN4, {repeat:true});
setWatch(function(){ toggleDateFormat(); }, BTN5, {repeat:true});

The watch was coded by someone who's left the project. Being a non-coder, I can't figure out the equivalent syntax for version 2. If anyone's interested in helping, I'll be grateful.

Is there a guide to converting an app from version 1 to version 2? Or is it just espruino.com/Bangle.js2#tutorials?
Is the old vector font available for the watch's version 2?
Thanks…

The text link pdfs are sized to keep them readable, rather than to have, for example, a very wide span of text. Two columns would have been useful also. I'm not sure if that answers your question!

I've been an amateur interested in this number base for several decades. What I've done is to take others' ideas that are mostly theoretical and realize them in ways that I think are useful. The clocks and the calendar were worked out with various collaborators. The dozenal clock (in one or more formats) and calendar are the only ones I use. There's an elaborate new metrology that includes time and is a whole additional story. The dozenal base also has a long history.

There are also solitaire card games, at https://games.dozenal.ca, the most unusual being in the shape of a hexagon.

I'm not sure that the watch hardware itself is the culprit. It may be, but a brief experiment with it suggested that the code has the problem. Because so few people use the watch, I haven't investigated further, partly because it would cost a fair amount to do so, partly because the original coder stopped working on the project.