Hello! 👋

I just got my Bangle.js from NodeConf EU this morning and started playing around with it. Apparently, it's not possible to set non-integer time-zones on the thing (I'm currently in UTC+5:30 and it became quite evident that this hasn't been addressed yet).

I thought changing the step size from 1 to 0.5 here (https://github.com/espruino/BangleApps/blob/master/apps/setting/settings.js#L101) will work, but maybe there's more nuance to it than that.

Using kilometer cause unreadable menu entry because of too much chars.

kilometer: km
miles: mi

Doing properly would need changes to the Puck.js/UART lib, but we could just split up write commands for each file and use that to do a progress bar.

Currently settings creates a widget so it's now only loaded if widgets are (eg for clocks) - but let's move the code into the 'boot' app so they run in boot0 all the time

Display the Bangle.js pixel chooser, info about the watch and firmware versions, and maybe some credits

To display when Bangle.js first starts - explain what buttons do what, and how to add apps.

Would it make sense to have a folder per app, for better navigation in the source?
example:

• apps/animals/animals.js
• apps/animals/animals.json

Currently apps are unminified and no modules are loaded. We could use EspruinoTools to do the work for us?

The console was moved permanently onto Bluetooth, but I moved it back to 'auto' (so it goes to the screen if BT is disconnected) recently as it seemed good for debugging (so any errors get shown to the user).

But this means that BT connection state scrolls the screen and messes stuff up.

So we could:

• Add a 'debug' option that, when false (default) moves the console to Bluetooth. When true you get the scrolling, but as you're developing you put up with it :)
• Add an option to Espruino to disable the Connection State messages
• Change apps/widgets to clear their backgrounds all the time, so scrolling was less of a big deal
• Leave the console on Bluetooth permanently - but then you don't see app erros

I opened speedo in my car and saw 66 while I was almost going with ~110km/h.

I took a look and couldn't find something related in the code except that there is no "special" calculations in speedo.js but I can quickly multiply with 1.60934 (is 1km) If that's the case.

http://forum.espruino.com/comments/15082797/

We wanted to do this for Nodeconf and never got around to it.

A website where you connect via Web Bluetooth and then perform a bunch of gestures. They all get saved online and then you can use that information to train a tensorflow model - either for you or based on everyone's data.

There's some HTML in there to display tabs for filtering - we should display markers on each item based on 'tags' JSON and then allow filtering by those

and when you delete that app than it is deleted and removed from the Bangle app menu.

1.

The GPS Recorder App (its corresponding widget) modifies the color of the Watch Face.
Should the Watch Face App be corrected or should it be the GPS Recorder App?

2.

Despite the Watch Face showing the proper time, the date and time of the recorded track are wrong.

3.

The last character of the .gpsrc0 files is not displayed correctly in the App Loader (Windows 10).

4.

There are some minor tabulation issues in the .kml file.

I think it will help to have some versioning of the apps, maybe just date/timestamp would be enough. Just something that I'd know, if something changed and that I should upload new version of the app.
And with versions, also changelog would be helpful.

http://forum.espruino.com/comments/15084888/

We should just add a \n

As discussed here: http://forum.espruino.com/conversations/290058/#15120253

Add an app and code to handle output of time/distance/etc in a locale-sensitive way

Hi,

First, thanks for the Bangle.js!

Is there any reason why this min and max have been set? This leads me to not being able to set a Year higher than 1980 once my watch is restored to UNIX timestamp 😅 (01/01/1970).

I'd be glad to propose a PR if it is reasonable to change it.

They should be at the bottom of the screen and they end up halfway up!

The bootloader currently defines 'drawWidgets' and this means that if you just do a direct upload to the watch (or run something in the emulator) it's not there and causes an error. There may be more things in the future where this is an issue.

Maybe Bangle.js should just define those variables internally at boot time? That does obviously make stuff a bit less flexible though

Hi,

does https://banglejs.com/apps/ has the latest version?

Uncaught SyntaxError: Expecting a valid value, got ID
at line 1 col 110
...false,"clock":null,"12hour":galse,"distance":"kilometer"}
^

require('Storage').list()
=[
".boot0",
".bootcde",
"+boot",
"+launch",
"-launch",
"+miclock",
"-miclock",
"*miclock",
"+setting",
"-setting",
"@setting",
"*setting"
]
require('Storage').read("@setting")
="{"ble":true,"dev"" ... "nce":"kilometer"}"
console.log(require('Storage').read("@setting"))
{"ble":true,"dev":true,"timeout":10,"vibrate":true,"beep":true,"timezone":0,"HID":false,"clock":null,"12hour":galse,"distance":"kilometer"}
=undefined

Currently widgets set their size when they are loaded - but maybe it'd make sense to have it dynamic. Draw calls could return a width and drawWidgets could assign an X coordinate as it iterated along.

Might make sense for:

• Battery indicator - could expand to show 'charging' indicator
• GPS recording - could hide itself when not enabled/recording

Thoughts? It'd make sense to do this now before the final release.

Following on from... aca3ce8#commitcomment-36387513

I'm not happy about the current solution (of manually removing listeners from objects) at all - so yes, having a destructor would help, but there'd have to be one for the clock app too. I'm considering maybe just modifying the Bangle.js firmware to allow load(appname) which would tear down everything and start afresh with the supplied JS file from Storage?

That obviously means you then can't have widgets that stay running - but they'd get removed anyway every time you long-press BTN3.

What I could do is add a E.on('kill' event which gets fired just before everything is torn down, so widgets/apps could save their state. It might be a useful thing for Espruino in general.

just stumbled over special chars in the app name aclock.

require('Storage').list()
=[
".bootcde",
"+aclo\xEB\xEF%", <---- guess some hidden chars in app.json
"-aclock",
"*aclock",
"+sbat", ...
"+setting",
"-setting",
"=setting",
"@setting",
"*setting"
]

it lists them as a bunch of separate files.

I feel like maybe we could just remove this and use the Web IDE's version (which works correctly) rather than maintaining two.

Don't do MRF.sleep if bluetooth is set to off in settings and we're currently connected - it stops the app loader from uploading apps

Add the ability to whitelist certain Bluetooth devices for connections. When Bangle.js is set to programmable all the time (eg for Gadgetbridge) this is really needed for security.

http://forum.espruino.com/conversations/341437/#comment15029127

Should apps report which firmware version they need?

While we're still on 2v04.xyz firmwares I don't think this is sensible (especially as travis mis-numbers them) but when we move to version numbers I think it's fair to say requires 2v05/etc and check this against the current firmware.

reported in http://forum.espruino.com/comments/15092142/

http://forum.espruino.com/comments/15126827/

Bangle.js's RTC is only 24 bit, which means an offset is stored in RAM and gets lost on reboot.

To work around this we could attempt to grab the time from the GPS module (if it's got a time in it)

http://forum.espruino.com/comments/15082323/

Firmware download from site today along with latest code from BangleApps.

Similar issue with apps/firmware last Wednesday too. But I was also getting GPS time errors on main settings screen last week. And only satellite image showing on screen in app last week, not satellite count.

Looks like bootloader loads the clock app before loading widgets.

Output:

Uncaught ReferenceError: "widget" is not defined
at line 1 col 30
eval(require("Storage").read(widget))
^
in function called from line 127 col 103
...re("Storage").read(widget)));
`

Switching to menu and back does not cause errors and widgets are loaded properly.

Any hints how to fix it?

Is this the expected load order?

• setting
• widgets
• clock if available

Use https://banglejs.com/reference#l_E_kill to save current steps and reload it

As mentioned at #70

Should we add a global setting for the time format used in clock faces, and ask that all clock faces read the setting and change accordingly?

Or does it just make sense to have a different clock app for each time format?

Often when I click on Remove All Apps I get such an error message in Bangle.js loader (Windows 10):
App removal failed, Unable to decode "", got SyntaxError: Unexpected end of JSON input
However apps get deleted, and I can press on the button again in doubt.

Looks like the pedometer widget is causing a bit of battery drain. It managed to drain my BangleJS completely in about 12 hrs.
I noted a separate thing, the screen came on a LOT more easily when the pedometer widget was installed. I initially thought it was due to me resetting the watch and getting new versions of the apps. But after I uninstalled the pedometer widget the 'screen on' behaviour went back to it's old self.

I just noted this line of code and am wondering does this kick the screen back to on ?
https://github.com/espruino/BangleApps/blob/master/apps/wpedom/pedometer_widget.js#L44

In that case, maybe we should handle the lcdPower event and only call draw when the screen is turned on ?

P.S. I am going to start handling the step event in my app and report back if I notice similar drain. I only draw on screen when LCD power is on.

P.S.2 Firmware details

{
  VERSION: "2v04.294",
  GIT_COMMIT: "d0cfc724",
  BOARD: "BANGLEJS",
  FLASH: 524288, RAM: 65536,
  SERIAL: "a0cf0da6-xxxxxxxx",
  CONSOLE: "Bluetooth",
  MODULES: "Flash,Storage,hea" ... "ow,graphical_menu",
  EXPTR: 536883676 
}

Hi together,

I've pre-ordered a few days ago and wanted to tinker around in the webIDE.
However, apparently var file = app.storage.find(f=>f.name[0]=='-'); returns nothing,
thus applications can not get loaded into the webIDE any longer and index.js:307 No entrypoint found for mclockis logged out.

Cheers,

23Ro

I think this could improve readability if all files were formatted the same, for example just by using prettier.

On my watch I have noticed that if I set HID to ON under settings, I am unable to connect to the watch (after a reboot) using Web Bluetooth: I get the Connection Failed error message in the Web IDE (whereas I can connect to it in all other situations).

As title. Somehow the source for both clocks is the same making them both 12 hour clocks.

Personally I don't care about 12 hour clock as I think it's an abomination and leads to people saying things like 12 am and 12 pm (neither of which exist) but this current code is wrong in a different way.

A time of 1205 (5 past noon) will get rendered as 12:05 AM and a time of 0005 (5 past midnight) will get rendered as 12:05 PM which I don't think even 12 hour clock lovers would think is correct.

I've updated to 0.03 bootloader, and I'm not able to access menu (BTN2). When I uploaded initial bootloader, it's working fine.
Maybe something in 0.02 caused this.

Loaded app Settings and set "Time Zone " = 1
So now the app "Simple Clock" shows GMT+0001
Pressing BTN3 after loading another app, timezone is back to GMT+0000

Is there some startup code missing that loads settings?

From: http://forum.espruino.com/conversations/341899/#comment15032976

Basically just use the code from the bluetooth widget

On the main app view screen, but also on 'installed apps'

Observations:

• When setting Bangle.js time using the Bangle.js loader the time displays correctly at first.
• However, if pressing for a long time on BTN3 the time gets displayed with a time zone of 0.
• To correct this, the user has to enter the correct time zone in settings, as it is 0 by default, even after setting the time using the Bangle.js loader.
• Then, if accessing the clock by pressing on its app from the application menu, the correct time taking into account the set timezone gets displayed.
• However if accessing the time by pressing for a long time on BTN3, the time gets displayed with a time zone of 0 at fist, and one has to wait till it gets updated (the next second, or next minute depending on the clock) to see the correct time taking into account the set time zone.

We changed to starting the menu on button release (not press) - but that means that now the press of the button turns the LCD on, and the release opens the menu.

Previously it worked so that when in clock you could press any button to wake Bangle.js up (including the middle one) but it wouldn't go direct to settings. Now it's broken and you usually end up entering settings pretty often by accident