Search results for:

The Bangle 2 broke at the strap connections on the case.

I might have finally fixed that with UHU Repair all putty
(https://www.gluemaxx.de/en/adhesives/2-component-adhesives/epoxy-putty/18/uhu-repair-all-powerkitt-60g)

The strap of the Bangle 1 ruptured in the "joint" that sits in the clasp when closed.
I tried fixing this one with ordinary super glue. Seems to work for now.

Same problem here.

I tried to "replace" the pieces that broke away with a two component glue, but the one I chose was too soft so the pin kept sliding out.
I'll have to look for something that is basically no more flexible than the original ABS once it has completely dried.

Also the strap of the Bangle 1 is falling apart.
I saw replacements in the store but when I wanted to finalize the order, the page told me they are out of stock (and I guess they are not coming back).
Are there alternatives for the B1 straps?
I would even buy a similar watch for a few EUR just to get the wrist band to not have to dump the B1.

I tried about 30-40 times during the last few days, also with different firmwares. Mostly with the edge builds, hoping that the package content would make a difference.

Just tried again and with the 2.12.28 release it worked.
I used an Android 10 phone and the nRF Toolbox app.

Happy to have the little bugger alive again :D

I tried from a Windows 10 PC and an Android 10 mobile.

I bricked my Bangle 2 but still hope there is a way to recover it.

After updating to 2.12.16 the message displaying didn't work for me so I tried to go back to an earlier version and might have had an update error there.

That didn't work out and I got an error. I tried down to version 2.10, all the same.
During the last three days I also tried to get the latest edge builds on in but to no avail.

I get into the DFU Start without problems and am presented with

DFU Start
BTN1 = REBOOT
CONNECT

I then start the flashing operation, wich goes up to 99% and then hangs, with the watch showing

DFU Start
BTN1 = REBOOT
CONNECT
ERROR

After about 30s the watch reboots by itself an the presents the following message

SW RESET
DFU2V12

CHECK STORAGE
NO NEW FW
BANK0 INVALID
BTN1 = REBOOT

Is there any way to get another working FW back onto the Bangle 2 or does it need recycling?

I tried uploading the FW with the IDE Flasher and the nRF Toolbox.

This has been solved by removing the Bangle2 from the "Paired Devices" list in the phone and disabling the Discovery and pairing -> Ignore connected devices (option names translated from German) option in Gadgetbridge.

Objection denied

My objection was denied by Geman customs on the grounds that the IOSS number was not included in the customs announcement(?) ( I guess that's where Royal Mail fucked it up). It's not enough to just have the number on the receipt and/or packaging slip.

They made it clear that the only way to handle this is to go through the seller/sender.

Pretty sad.

If you had to pay the additional VAT in Germany you can reclaim it from customs.

What you need is a "Abgabenbescheid" which you can get at
https://www.dhl.de/de/privatkunden/hilfe-kundenservice/formulare/abgabenbescheid-anfordern.html

Requested on 19-Nov-2021

Received on 23-Nov-2021

Then, since we are in Germany, you have to obey ... erm ... I mean follow the process:
https://www.zoll.de/DE/Fachthemen/Zoelle/Abgabenerhebung/Erlass-Erstattung/Verfahren/verfahren_node.html#doc298948bodyText2

Objection sent 23-Nov-2021

Still being handled by the customs office - haven't heard back 04-Dec-2021

With luck you can also get your 6EUR fee from DHL back using this link (once you have the "Abgabenbescheid").
https://www.dhl.de/nachentgelt

Important
The label on my package says that there is a one month deadline for this.
So be quick or be screwed (well not totally, since Gordon is so nice to reimburse you, but anyway).

I can't yet say if this works, since I've only gotten around step 1 before writing up this post.

Source: https://www.paketda.de/zoll/zoll-reklamieren.html

Objection denied on 17-Jan-2022 (see post below)

Updates
Action dates added

Hi all,

I have a problem connecting the Bangle 2 to Gadgetbridge on my Fairphone 3.

It looks like Gadgetbridge does not find the device, but that is apparently not the case as the log contains the following lines:

20:30:49.972 [main] WARN  n.f.g.i.GBDeviceCandidate - no cached services available for (unknown): 11:96:F1:C6:80:C0 (UNKNOWN)
20:30:50.013 [main] WARN  n.f.g.a.DiscoveryActivity - Bangle.js 14a7: 62
20:30:50.016 [main] DEBUG n.f.g.a.DiscoveryActivity - found device: Bangle.js 14a7, C8:1D:A7:B8:14:A7
20:30:50.016 [main] DEBUG n.f.g.a.DiscoveryActivity -   supports uuid: 6e400001-b5a3-f393-e0a9-e50e24dcca9e
20:30:51.374 [main] WARN  n.f.g.a.DiscoveryActivity - Bangle.js 14a7: 62
20:30:51.378 [main] DEBUG n.f.g.a.DiscoveryActivity - found device: Bangle.js 14a7, C8:1D:A7:B8:14:A7
20:30:51.378 [main] DEBUG n.f.g.a.DiscoveryActivity -   supports uuid: 6e400001-b5a3-f393-e0a9-e50e24dcca9e
20:30:52.505 [main] WARN  n.f.g.a.DiscoveryActivity - Bangle.js 14a7: 62
20:30:52.509 [main] DEBUG n.f.g.a.DiscoveryActivity - found device: Bangle.js 14a7, C8:1D:A7:B8:14:A7
20:30:52.510 [main] DEBUG n.f.g.a.DiscoveryActivity -   supports uuid: 6e400001-b5a3-f393-e0a9-e50e24dcca9e
20:30:52.886 [main] WARN  n.f.g.a.DiscoveryActivity - Bangle.js 14a7: 62
20:30:52.889 [main] DEBUG n.f.g.a.DiscoveryActivity - found device: Bangle.js 14a7, C8:1D:A7:B8:14:A7
20:30:52.890 [main] DEBUG n.f.g.a.DiscoveryActivity -   supports uuid: 6e400001-b5a3-f393-e0a9-e50e24dcca9e

So it looks as if only displaying the device in GB's list is problematic.

I already updated the watch to FW 2.10.223 but that didn't help.

Is that something that the FW can change or rather an issue that needs to be fixed in GB?

Cheers
MSD

Fixed by reinstalling from the production site. Was most likely connected to trying the install from the dev site on github.io

I just had to reset my Bangle and reinstall all apps due to putting something in the Flash that didn't belong there.

Being on the IDE page anyway I also updated to FW 2.10 before installing anything else.

Except Gadgetbridge 0.23 everything works fine.

I don't see the GB widget icon and when checking the settings I only get

Gadgetbridge:
Invalid settings!
Press BTN1 to return.

Downgrading to 2.09 fixes the issue.

Since there is nothing immediate in 2.10, that I need, that's OK as fix for now.

In case you can't decide which watch face is the nicest one you now have the chance to easily change them with a long press of BTN 3.

Once you have installed the Random Clock Loader widget (dev version at: https://msdeibel.github.io/BangleApps/index.html) it will change the clock setting of your Bangle each time the LCD turns off.

You can load the reload bclock with a long press of BTN 3 at any time and you might see a new watch face :)

I'm working on getting this to not require user interaction but it turns out that this is quite tricky without the widget doing bad things to other apps (namely Gadgetbridge).

Didn't get to work on it yet. Also looks like I won't be for another few weeks :(

I have finally found the time to put together some graphs from one week of running BatteryChart.

With BLE being more or less constantly active (and connected) during the day, while off at night, the watch lasts two days, with a few percent left.

The SoC device graph is only a rough estimation, since the widget only records values only every ten minutes and thus the LCD is naturally enabled more often than displayed there.

You will notice that the battery level seems to drop faster while the watch is not being used at night. However, you need to keep in mind that the percentage is calculated and takes the die temperature into account which also drops, which most likely explains the faster decline.

The espruino.json should be a good starting point. I'll try to look into it, the coming weekend.

Hi everyone,

Since I'm doing most of my development work for the Bangle in VS Code I would like to know if anyone has managed to integrate the Espruino libs into Code's intellisense. If yes, how did you do that?

Fix is implemented in version 0.09 of Battery Chart.

Until it is merged into the espruino master you can update from
https://msdeibel.github.io/BangleApps/

Hmm, seems to be my Battery Chart app or the widget.

I think it's rather the widget, because it happens even if the app is not running?

I'll have a closer look tomorrow.

UPDATE
Yeah seems to be the draw function for the widget icon. I removed the code in there and now it works. Will fix it tomorrow.

It seems I can no longer dismiss the notifications sent to the Bangle via Gadgetbridge (not limited to a phone app) using tap on the screen. Only option is a reload with button 3.

I'm on GB version 0.10 (Settings 0.16 and DefaultLauncher 0.02), but it might be that it already stopped working with 0.09 of GB.

GB version on the mobile is 0.43.2 from F-Droid.

Is anyone experiencing similar issues?

I found them but wasn't sure if I could work with them in case they don't fire.

I worked around with this code

Bangle.on('mag', (() => {
  console.log("mag received");
  compassEventReceived = true;
}));
    
Bangle.on('GPS', (() => {
  console.log("GPS received");
  gpsEventReceived = true;
}));

Bangle.on('HRM', (() => {
  console.log("HRM received");
  hrmEventReceived = true;
}));

// Wait two seconds, that should be enough for each of the events to get raised once
setTimeout(() => { 
  Bangle.on('mag', () => {});
  Bangle.on('GPS', () => {});
  Bangle.on('HRM', () => {});
}, 2000);

The only issue is removing the eventlisteners now. The code above fails to do that. I already posted another question for that, though ;)

How can I remove an event listener once I don't need it anymore?

I found that HTML elements normally provide a removeEventListener method, but how can I do that on the Espruino, especially on the Bangle?

Hi all,
currently we can easily check if the LCD is on with isLCDOn().

As far as I can see there are (for now) no corresponding functions for

• Compass
  
• GPS
  
• BLE
  
• and HRM
  
  

Is there another way of getting the status, e.g. by reading a pin status (which ones?) until we have convenience functions for this purpose?

@user110973 I just double checked and these are really the only ones that make sense. I overlooked that the other ones I had found with the filters are "feedback" piezos.

Here's what I implemented. I'll leave it here for further reference.
The full code can be found at https://github.com/msdeibel/BangleApps/blob/master/apps/batchart/widget.js

function logBatteryData() {
      const previousWriteLogName = "bcprvday";
      const previousWriteDay = require("Storage").read(previousWriteLogName);
      const currentWriteDay = new Date().getDay();

      const logFileName = "bclog" + currentWriteDay;

      // Change log target on day change
      if (previousWriteDay != currentWriteDay) {
        //Remove a log file containing data from a week ago
        require("Storage").erase(logFileName);
        require("Storage").write(previousWriteLogName, currentWriteDay);
      }

      var bcLogFileA = require("Storage").open(logFileName, "a");
      if (bcLogFileA) {
        console.log([getTime().toFixed(0), E.getBattery(), E.getTemperature(), getEnabledConsumersValue()].join(","));
        bcLogFileA.write([[getTime().toFixed(0), E.getBattery(), E.getTemperature(), getEnabledConsumersValue()].join(",")].join(",")+"\n");
      }
  }

Hello everyone,

I just started working on a data recorder widget/app for the Bangle and want to limit the file size to keep a maximum of one week worth of data. Which amounts to around 1000 lines in a text file (1 line/10 min).

Now that the storage size is limited and flash mem has a limited number of write cycles I was wondering what would be the best way to handle this.

In a simple solution I would

open the data file
read all lines into an array
append the new line to the array
write all lines, but the first, into the file

Since I'm quite new to developing for the Espruino I don't want to mess up the flash within a few days of the widget repeatedly writing to the flash.

Do you have any suggestions how the proposed solution could be improved?