Search results for:

@Delta Gordon runs espruino.com... Since he said he'll swap it out for a new one I'm pretty sure the store will be able to replace it. :D

@Lixas What version of GB do you have installed? There was a bug along these lines that was fixed in v0.43.1.

I did see your PR for gbnotify, and did also look at your repo for the other parts. Can't wait to try it out.

I've been wondering about adding something to Gadgetbridge though - probably just the ability to run a webpage in the background on the phone and then push data from there.

Yes! I can picture several useful applications for that...

@DerGuteWolf There's already a spirit level app, so integrating this into the compass should be possible.
https://github.com/espruino/BangleApps/tree/master/apps/slevel

Hm... Looking at that there is also this:

t:"call", n:"ACCEPT/END/INCOMING/OUTGOING/REJECT/START/IGNORE"

What does START do? Will have to test...

The Phone call app wouldn't have a widget, but for rejecting and accepting a call I was also thinking of adding it to the existing GB widget. Once I get a hang of this I'm also planning on making my own forks so I can get things just the way I want them.

Had an idea last night that I have no idea if it is possible, so here's a shout-out for some input.

An app where you have a few phone numbers saved that you can select and start a call. Great if you're wearing a headset, you don't have to actually pick up your phone.

I'm still in the process of learning JavaScript and working with Gadgetbridge, BLE, etc, so before I even start looking closer into this:
Is it even possible to make that kind of action from the Bangle.js?

On another note, it would be cool to be able to also reject and accept calls from the watch... I see from the Gadgetbridge feature matrix that some watches have the former ability, but none have the latter.

Thoughts and ideas are welcome.

There are some really cool things you could do with magnets... That sounds like it could become really expensive, real quick though. :D

Works great!

Quick update.

As already expressed earlier in this thread, everything points to it being my phone that is causing this issue. As a test, I let the phone stay awake, with the screen on, for 2 hours, all the while having the watch connected and going about as usual (made sure to not get too far from the phone to avoid disconnecting caused by distance). After that I turned the phone screen off and let it stay like that for an additional 30 minutes.

During the first 2 hours (screen on) there where 2 instances of the watch and phone losing connection (reason 8 both times), but it was quickly reestablished (within a few seconds). In the last 30 minutes (screen off) there where 25 connection state changes, of which only 9 where successful connection attempts and the rest failed (8 reason 8 and 1 reason 34 from an active connection, and 7 reason 133 when trying to reconnect).

@Purple-Tentacle One observation: The buzz doesn't go off when the timer reaches zero, but rather one second after when END is displayed. In other words, a 10 second timer becomes an 11 second timer...

Edit: and maybe a reset option in the app? To set everything back to zero.

Confirmed fixed in v2.05.441.

Oh... I really liked that positioning of the widget. Would be sad if it doesn't work.

I only had the widgets load in after the LCD times out, no clock...

Yeah, that's what I figured as well. Couldn't see that in your code anywhere.

That error pops up regardless if the watch has just been cleared with "Install Default Apps" or if I've already set it up with my favourites.

Seems like the widget is triggering something, somewhere.

Oh yeah... Forgot to check that:

BLE Connected, queueing BLE restart for later
{"t":"status","bat":76}
Uncaught ReferenceError: "x" is not defined
 at line 2 col 102
...r.c)g.clearRect(0,h-24,w-1,x,h-1);for(wd of WIDGETS)wd.draw(...
                              ^
in function called from line 118 col 20
Bangle.drawWidgets();
                   ^
at line 36 col 16
  eval(clockApp);
               ^
> 

Weird...

@Purple-Tentacle Chrono Widget seems to break things on firmware v2.05.440. Tested it on a clean install of the default apps, and installing Chrono Widget just makes the screen go black. Any app showing the widgets seems to be affected.

Yup... Can't reproduce the Alarms issue on v2.05.440 anymore. Nice!

Yay! That's a fun little bug.

Yeah, I've been suspecting all along that it is my phone that's the culprit.

I did dig up an old Google Nexus 6 I had laying around and got that up and running yesterday, but it has the same issue with randomly dropping the connection. I'm gonna test with my wife's phone next...

@Gordon I've been doing some reading to try to understand more about how BLE works. Not quite there, but I did find some info about what you mentioned about the clock accuracy and BLE_HCI_CONNECTION_TIMEOUT, and that it possibly could be helped by increasing the PPM (example).

I have absolutely no idea if that is even relevant, but wanted to just air the idea and see if there may be something I could test in this regard.

I recreated the issue using the App Loader at banglejs.com/apps and here's the output below. Interestingly I couldn't recreate the issue when using the development App Loader.

>dumpStorage();
{ "addr": 1073741824,
  "name": ".boot0",
  "size": 1990, "flags": 0 }
{ "addr": 1073743848,
  "name": ".bootcde",
  "size": 1345, "flags": 0 }
{ "addr": 1073745228,
  "name": "boot.info",
  "size": 122, "flags": 0 }
{ "addr": 1073745384,
  "name": "launch.app.js",
  "size": 1825, "flags": 0 }
{ "addr": 1073747244,
  "name": "launch.info",
  "size": 140, "flags": 0 }
{ "addr": 1073747416,
  "name": "mclock.app.js",
  "size": 3715, "flags": 0 }
{ "addr": 1073751164,
  "name": "mclock.img",
  "size": 1155, "flags": 0 }
{ "addr": 1073752352,
  "name": "mclock.info",
  "size": 175, "flags": 0 }
{ "addr": 1073752560,
  "name": "setting.app.js",
  "size": 11628, "flags": 0 }
{ "addr": 1073764220,
  "name": "setting.boot.js",
  "size": 267, "flags": 0 }
{ "addr": 1073764520,
  "name": "",
  "size": 334, "flags": 0 }
{ "addr": 1073764888,
  "name": "setting.img",
  "size": 1155, "flags": 0 }
{ "addr": 1073766076,
  "name": "setting.info",
  "size": 189, "flags": 0 }
{ "addr": 1073766300,
  "name": "about.app.js",
  "size": 8818, "flags": 0 }
{ "addr": 1073775152,
  "name": "about.img",
  "size": 2308, "flags": 0 }
{ "addr": 1073777492,
  "name": "about.info",
  "size": 130, "flags": 0 }
{ "addr": 1073777656,
  "name": "alarm.app.js",
  "size": 2551, "flags": 0 }
{ "addr": 1073780240,
  "name": "alarm.boot.js",
  "size": 874, "flags": 0 }
{ "addr": 1073781148,
  "name": "alarm.js",
  "size": 1662, "flags": 0 }
{ "addr": 1073782844,
  "name": "",
  "size": 2, "flags": 0 }
{ "addr": 1073782880,
  "name": "alarm.img",
  "size": 1156, "flags": 0 }
{ "addr": 1073784068,
  "name": "alarm.wid.js",
  "size": 437, "flags": 0 }
{ "addr": 1073784540,
  "name": "alarm.info",
  "size": 178, "flags": 0 }
{ "addr": 1073784752,
  "name": "widbat.wid.js",
  "size": 1089, "flags": 0 }
{ "addr": 1073785876,
  "name": "widbat.info",
  "size": 114, "flags": 0 }
{ "addr": 1073786024,
  "name": "widbt.wid.js",
  "size": 478, "flags": 0 }
{ "addr": 1073786536,
  "name": "widbt.info",
  "size": 107, "flags": 0 }
{ "addr": 1073786676,
  "name": "widbatpc.settings.json",
  "size": 2, "flags": 0 }
{ "addr": 1073786712,
  "name": "",
  "size": 41, "flags": 0 }
{ "addr": 1073786788,
  "name": "alarm.json",
  "size": 40, "flags": 0 }
NEW PAGE 0x4000b000
{ "addr": 1073786880,
  "name": "welcome.boot.js",
  "size": 285, "flags": 0 }
{ "addr": 1073787200,
  "name": "welcome.app.js",
  "size": 9391, "flags": 0 }
{ "addr": 1073796624,
  "name": "welcome.settings.js",
  "size": 466, "flags": 0 }
{ "addr": 1073797124,
  "name": "welcome.img",
  "size": 2308, "flags": 0 }
{ "addr": 1073799464,
  "name": "welcome.info",
  "size": 213, "flags": 0 }
{ "addr": 1073799712,
  "name": "",
  "size": 334, "flags": 0 }
{ "addr": 1073800080,
  "name": "setting.json",
  "size": 350, "flags": 0 }
{ "addr": 1073800464,
  "name": "widbatpc.wid.js",
  "size": 3401, "flags": 0 }
{ "addr": 1073803900,
  "name": "widbatpc.settings.js",
  "size": 1582, "flags": 0 }
{ "addr": 1073805516,
  "name": "widbatpc.info",
  "size": 192, "flags": 0 }
{ "addr": 1073805740,
  "name": "",
  "size": 80, "flags": 0 }
{ "addr": 1073805852,
  "name": "",
  "size": 2, "flags": 0 }
{ "addr": 1073805888,
  "name": "alarm.json",
  "size": 2, "flags": 0 }
=undefined

I'm looking for a good solution for a custom made strap as well (as I'm sure there are many others that might be looking for ways to use the strap of their choice), so this is an interesting subject...

Don't know if @Gordon has any CAD or model files for you, but from what I understand we're using this hardware, so maybe you could find something for that if you look around (probably not though, but maybe worth a shot).

That's it! There are two alarm.json:

>print(require("Storage").list())
[
  ".boot0",
  ".bootcde",
  "boot.info",
  "launch.app.js",
  "launch.info",
  "mclock.app.js",
  "mclock.img",
  "mclock.info",
  "setting.app.js",
  "setting.boot.js",
  "setting.img",
  "about.info",
  "setting.info",
  "about.app.js",
  "about.img",
  "alarm.app.js",
  "alarm.boot.js",
  "alarm.js",
  "alarm.img",
  "alarm.wid.js",
  "alarm.info",
  "widbat.wid.js",
  "widbat.info",
  "widbt.wid.js",
  "widbt.info",
  "widbatpc.settings.json",
  "alarm.json",
  "welcome.boot.js",
  "welcome.app.js",
  "welcome.settings.js",
  "welcome.img",
  "welcome.info",
  "setting.json",
  "widbatpc.wid.js",
  "widbatpc.settings.js",
  "widbatpc.info",
  "alarm.json"
 ]
=undefined
> 

I leave both on, since I found it makes no difference for the outcome.

Leaving the old widget installed was just slightly faster when I was doing a bunch of testing, and the result was the same: can't write to alarm.json.