Search results for:

By the way: With other music apps it does not crash, with Amazon Music this can be reproduced.

When pressing play in a Netflix notification the Gadgetbridge app
crashes and restarts, but the bluetooth connection is not resumed
automatically.

I can confirm this, but with Amazon music. I opened https://codeberg.org/Freeyourgadget/Gadgetbridge/issues/2485
but I don't have the time to add the required logs right now. Maybe you can do it ...?

I'm still struggeling on this.
Edit: Post deleted - I had another idea, still testing ..

BTW: If your code has runtime errors and is executed after boot (e.g. a watch face), you may just replace it by working code to get everything back in place.

Maybe saved to somewhere else than "Storage"?

@Gordon: That's exactly the issue I encountered before. I included at the moment as workaround in the watch face

Bluetooth.setConsole(true);

otherwise the whole console is written to the screen.

Yes and it is the case - my next idea is:

function planChime() {
  chimeTimer = setTimeout(function() {
    Bangle.buzz().then(() => {
      setTimeout(()=>{
    clearTimeout(chimeTimer);
   chimeTimer = undefined;
         planChime();
      }, 2000);
      });
  }, 3600000 - (Date.now() % 3600000));
}

Additionally, is the "Time Zone" setting just a way to quickly offset the watch when you change timezones? I don't see any reason to actually set this to my UTC offset, since I'm just setting the time manually anyway?

It might be neccessary when using time sync like Gadgetbride or GPS time.

Sadly, Navstar satellites are synchronised, so the number of channels are irrelevant for downloading ephemeris and almanac data.

Yes and no. The data is the same, but the TTFB of the data can be massivly reduced. Multi channel is used as a method for shortening the time to 30 s to 3 min. The mathematicians at the chip designers do the rest of the improvement.

If the GPS is starting from fresh, it needs to download the almanac and ephemeris data. This takes a minimum 12.5 minutes, assuming no errors

AT6558 has 56 channels.
TTFF is possible with 45s +
(=cold start without time and data)

Ah, ok. But it makes a real sound without a vibration.

Yes, I also thought this. But I tried it today and it makes a noise. Maybe it is generated by a slight buzzer movement but I dont feel any vibration.

Because it can't do that, there is no speaker.

Bangle v2 is able to make a beep, v1 only some devices. On Both devices nearly inaudible in normal environments.

Bangle.beep();

In IDE works.

Yes. Above is another solution, based on what Gordon wrote.

... ok - next solution:

function planChime() {
  if (chimeTimer) {
    clearTimeout(chimeTimer);
   chimeTimer = undefined;
  }
  chimeTimer = setTimeout(function() {
    Bangle.buzz().then(() => {
      setTimeout(function(){
         planChime();
      }, 2000);
      });
  }, 3600000 - (Date.now() % 3600000));
}

It's working if it is changed to:

function planChime() {
  if (chimeTimer) {
    clearTimeout(chimeTimer);
  }
  chimeTimer = setTimeout(function() {
    Bangle.buzz().then(() => {
      setTimeout(function(){
         planChime();
      }, 2000);
      });
  }, 3600000 - (Date.now() % 3600000));
}

To be exact: The shown code is derived from the Anton clock approach to time updates.

Jep, you're right. Thank you. That's not correct. The undefined would lead to one buzz in the first, two buzzes in the second hour and so on. But this does not explain why this leads to infinite buzzes in the first hour - due to the 2s delay.

I developed an hour chime function (buzz) two years ago for v1 which worked very well. After some firmware upgrades on v1, the chime had sometimes complete runaways and did not stop chiming. I had several attempts with completely different approaches to get rid of it and secured the buzz() in a way that it can only be executed once at a time. Now I tried the event triggered solution below on v2 - and there it is again. Works, works not. Does somebody see my error in the code? From my point of view it should be impossible that the buzz code is executed twice.

function planChime() {
  if (chimeTimer) {
    clearTimeout(chimeTimer);
  }
  chimeTimer = setTimeout(function() {
    chimeTimer = undefined;
    Bangle.buzz().then(() => {
      setTimeout(function(){
         planChime();
      }, 2000);
      });
  }, 3600000 - (Date.now() % 3600000));
}

after a buzzer runaway:

Uncaught Storage Updated!
Interpreter error: [
  "FIFO_FULL"
 ]
New interpreter error: FIFO_FULL
>

I saw that at least the health tracking app requires firmware 2v11
Is this the problem with all HRM apps? On the website (and travis master) there is only 2v10. Bit confused now...

In the log sometimes appears:

HEALTH ERR: Already written!

I tried some other things, but as far as I can check it, the sensor is not working.

It says true, but no light

Bangle.setHRMPower(1)

no, it does not light up although:

>Bangle.setHRMPower(1);
=true
> Bangle.isHRMOn()
=true
{"t":"act","stp":0,"hrm":-1}

The HRM app has no console messages, but gets stuck with "Please wait ... 1".
Is it ok that reset() gets only the Bangle startup screen?

Maybe the device is already whitelisted?
I tried passkey with Android and it does nor work for me. It seems that 6 digits are not expected.

Just saw that there is a small plastic foil covering the sensor. But removing it does not change anything.

Hi,
all HRM apps do not work on my Bangle 2. The Heart Rate Monitor (v0.06) counts down to 1 and gets stuck and also the Health Tracking App stops working when I enable HRM. The firmware was udpated yesterday.
Any idea on this?
TX