Search results for:

I've only ever enabled HID once, first or second day of receiving the watch when testing stuff. Since then it's been off the whole time.

I'll take a closer look at troubleshooting this later in the week, and I might even install a stock ROM to see if that makes any difference... I only have this device as my daily driver though, so I rarely have an opportunity to do too much crazy stuff with it.

Searched a bit and it does seem like reason 8 is BLE_HCI_CONNECTION_TIMEOUT.

It's a Kickstarter Bangle.js for sure, unless you sent me something else. :D

I ran the same procedure (Resetting the watch with "Install Default Apps", installing the Battery widget with percent, setting and deleting alarms) and this time I ended up with an empty alarm.json that I couldn't save any new alarms to.

>alarms
=[  ]
>require("Storage").readJSON("alarm.json")
=[  ]
>require("Storage").write("alarm.json",JSON.stringify([
:  { on: true, hr: 12, last: 14, rp: true },
:  { on: true, hr: 13, last: 14, rp: true }
: ]));
=true
>require("Storage").readJSON("alarm.json")
=[  ]
>require("Storage").getFree()
=4130004

Here's what I got (hope I did it right):

>alarms
=[
  { on: true, hr: 13, last: 14, rp: true }
 ]
>require("Storage").readJSON("alarm.json")
=[
  { on: true, hr: 13, last: 14, rp: true }
 ]
>require("Storage").write("alarm.json",JSON.stringify([
:  { on: true, hr: 12, last: 14, rp: true },
:  { on: true, hr: 13, last: 14, rp: true }
: ]));
=true
>require("Storage").readJSON("alarm.json")
=[
  { on: true, hr: 13, last: 14, rp: true }
 ]
> 

As you can see, at this point I have an alarm at 13:00 that I cannot delete.

Awesome!

By the way, some explanation of the available settings in the readme might be a good idea as well.

Tested it for a quick walk (3.5k steps) right now and it seems to work pretty well.

How about an option to reset the steps?

Will for sure give it a try and let you know how it worked.

I'm going to let my face and palm get better acquainted for a moment... I had seen that setting but for some reason I just did not think about enabling it. Will do. Thanks.

The thinnest width of the strap (not counting the narrowing right at the end) is just over 24 mm (24.2), and (for completeness) right by the watch, at the base, it is 34 mm

There's no spring bar on the watch, but rather a solid pin holding the strap in place (two pins actually, one on each side, of course). It is 29 mm long and has a diameter of 1.5 mm.

The measurments between the two "taps" (I've actually no idea what to call them) on the watch where the strap attaches are as follows (see the disassembly video to see what I mean):
Outer edges - 23 mm
Inner edges - 12.7 mm

Edit: If you want to use a standard strap and have access to a 3D-printer you might want to try something like this: https://www.thingiverse.com/thing:4010651

Haven't seen any difference depending on what widget/clock that's being used. MarioClock might seem to be loosing connection more often since it buzzes on connect/disconnect, but I'm seeing the same kind of successful/failed connections in the logs no matter what...

ROM and hardware have been on the top of my list as well. Which is the main reason I'm switching ROM soon.

But, now that you mention it I have been using the MarioClock the past couple of days, which has its own GB implementation. I did see connectivity issues before that as well, but hadn't started investigating until after switching over to MarioClock. I'll test some more with the GB widget active.

I've been trying to troubleshoot the connection between the watch and my phone for the past few days. It is very flakey and can disconnect and reconnect several times in quick succession, or stay stable for several hours.

I'm using a OnePlus 3T with a custom Android 9 ROM. Gadgetbridge and all Bluetooth services are exempt from battery optimisation on the phone (and I even moved Gadgetbridge to /system/priv-app to see if that kept the connection more stable).

I've tried with the watch both paired and without pairing in Gadgetbridge.

I have no idea if it is caused by the phone, the ROM, Gadgetbridge or the watch... I'm going to switch to a different ROM in the near future, so then I'll at least have a second base of information there. Doesn't help right now though.

In an attempt to dig deeper I've saved a couple of logcats showing several successful and failed connections during about 15 minutes. One with the watch paired to the phone and one without pairing in Gadgetbridge. My skills with troubleshooting Bluetooth on this level are quite limited though, so I'm posting the files here hoping that someone might see something of use.

There are three files in each zip:

1. The full logcat (but filtered to remove some personal info)
   
2. A list showing all the separate successful and failed connections (for the time stamps)
   
3. An excerpt from the log showing the first failed connection
   
   

I've also noted that sometimes a reset of the watch (BTN1+BTN2) is necessary to be able to connect from my computer (and sometimes my phone). I believe I have read somewhere that Android doesn't actually let go of a BLE connection when you disconnect, so I was thinking this might be the reason for this little quirk. No biggie though, just a thought.

I guess this forum is a good place to discuss new apps...

There are ideas to make new apps (and more) visible in the App Loader being discussed on GitHub:
https://github.com/espruino/BangleApps/issues/249

Nice apps by the way.

There's another discussion open about this, where @Purple-Tentacle seems to be having some success when testing new code for this. Here:
http://forum.espruino.com/conversations/345358/

@Gordon I seem to have found a reliable and simple way of recreating the issue:

1. Reset watch
   
2. Install "Battery Level Widget with percentage"
   
3. Set alarm 1 (say 12:00)
   
4. Set alarm 2 (say 13:00)
   
5. Delete alarm 1 or alarm 2
   
   

Now it seems like alarm.json no longer can be edited (no errors showing in the Web IDE).

I do not know if this is specific to the battery widget or if other widgets/apps also may cause the issue. This is just the one I did find that reliably could show the problem (although I can confirm that the "Tiny Battery Widget" does not cause it).

Edit: steps 3 to 5 aren't the only way to reproduce, just what I found to be a quick way. The key seems to be to set and delete alarms at least three or four times, until there's no or only one alarm.

I'll keep testing.

@Gordon Had an opportunity to do some testing and have the following to report:

As already stated, following the steps of first clearing the device by first installing the Default apps then setting up an alarm works fine. But, as soon as I install my list of apps it is no longer possible to set any alarms. With one exception: It is possible to set an alarm once, but after that no longer.

The way that I set the clock up is to simply scroll from the top to the bottom of the App Loader and delete and install apps as I reach them in the list.

I started testing by deleting and installing one app at a time, each time attempting to set an alarm afterwards and it worked after every deletion/install. So, it's not a specific app that is causing it.

@Raik When it is possible to set an alarm the alarm.json file is present and contains the correct data, like in your screenshot. But, as I said above, after setting the clock up as described this only works once. After that the alarm.json stays empty (apart from the square brackets), no matter what alarm I try to set. It almost seems like the app can't write to the .json file anymore (no errors in the IDE though).

But, I can get things working by doing the same setup as described above, with one small change. Instead of deleting and install apps as I go, I install all the apps I want and only when they all are installed do I delete the ones I do not want. It does not matter in which order the apps are installed or in which order they are deleted, as long as the deletions happen last it seems.

Since I'm now out of time for today, I haven't tested if it's a certain number of installs/deletions that matter, if it has any impact as to what apps are installed/deleted, if setting an alarm before doing my setup changes the outcome, etc. That's for another day, if necessary.

Hope that helps in any way.

@Gordon Yes, I will sit down and narrow it down further later today. I did hook up to the Web IDE to see if I could catch anything when setting an alarm, but nothing...

@Gordon Ok... Following your steps I can set an alarm just fine. But, as soon as I have set the watch up with my prefered apps it stops working. I'm attaching a screenshot of the "My Apps" tab for reference.

I tested going back to Morph Clock and Default launcher, but it made no difference.

I can do a reset a bit later and just get the Default Apps on there, but currently doing theses steps:

1. BTN2 - launcher
   
2. Select Alarms and launch
   
3. Choose New Alarm
   
4. Choose Save
   
5. Choose Back
   
   

Nothing... No alarm icon in the top left and when going back to Alarms the alarm is gone. The alarm is shown in the list after step 4, but no icon and no alarm goes off (and isn't actually saved as seen when going back into the Alarms app).

I did get the icon and the alarm was actually saved one time (after several tests back and forth), but I've not been able to get it to do that again even though I'm following the same steps.

@Gordon Yes, even with Alarms App v0.06 it doesn't seem like the alarms are actually saved.

@Gordon How long is a while? I'm seeing this on the official App loader right now... I've done the Empty Cache and Hard Reload thing in Brave (and even opened the page on a completely fresh install of Chromium), but I can't see any of the updates done since yesterday (as an example, "Settings" is still on v0.09 even though it's a full day since v0.10 was commited).

Or am I misunderstanding how the App loader works contra the commits on GitHub?

While the Torch app solution was handy, it got really annoying to have it fire up when scrolling in menus.

Stunning! I wants it.

Well, the time zone can be set in half-hour increments in the "Locale" settings, so that's already taken care of.