Search results for:

Maybe offer it at a cheap 2nd hand / broken price. But the button is fairly key to using the watch.

Does it power on if you try to turn it on with the charge cable connected?

Usually takes a few days for a pull request to make it into the main app site. You could install it from your own cline of the repository.

I can't recall if a Rpi has web Bluetooth.
You might need a ble dongle and the right drivers installing.

location will be GPS lat/lon ? It will take you at least 20 seconds to power on the GPS and get a fix and that is assuming you have downloaded AGPS data - otherwise expect 12 minutes for the first fix.

That is good news. Interesting that it can take 12 hours to totally drain residual power from the accelerometer. One to bear in mind in the future.

BTW you dont need to use gadgetbridge to install apps. You can go straight to the AppLoader page through the standard browser on the phone.

https://banglejs.com/apps/

There is a debug setting in the Settings App. Utils / Debug / Log should capture something in log.txt. You would need to look at it through the IDE (after disconnecting with GadgetBridge).

I have also experienced randon clock freezes. I have seen them mostly on my Pastel and Lato clocks. Both use the Lato font. Its not frequent enough to narrow down. I saw it twice a couple of weeks back, but not now.

If you are using the health app check what you have set the heart rate monitor to. If it is on always I would expect you battery to run down in a few days.

Did you try factory reset via the Settings / Utils menu for a full wipe ?

You could always step sideways (sorry could not resist the image in my head).

Unless a flatten the battery reset fixes it, it looks like a broken accelerometer.
In order for the step counter to work it uses SQRT(X^2 + Y^2 + Z^2).

Step counters that only one axis tend to stop working in certain positions - eg one of the Garmin (£500) smartwatch wont count steps if you walk with sticks.

Just do a log of say 2 minutes normal walking or 500 steps.

https://banglejs.com/apps/?id=accellog

Your watch is not counting steps properly - it looks like something to do with the accelerometer.
It is possible record a few minutes of accelerometer data so we can look at what is going on.
We might have to try that next.

Yes the step counter works off the accelerometer data. So does the movement measurement.

Movement is something different. I have not looked at the code for movement - but I it will get triggered for any movement where as the step counter is looking for a regular sequence of cycles that match the normal pattern and timing of walking. Also the changes in g force back and forth have to be above a certain threshold. The threshold is quite sensitive but we seem to have it right as its been about 1-2 years since anyone had a problem with step counting.

I spent a lof of time testing the step counter to work out how to make it work so I'm probably an expert on it.

Suugest a couple of thing.

1) run Bangle.getHealthStatus("day").steps via the IDE and check what steps are reported.
If the step count looks close to your other fitness band then the problem is some config on your watch.

2) Try and setup a minimum sets of apps to start with. Say just the default ones that are present after a factory reset. Then update all they apps. Then install Lato Pedometer so you can see the step count.

See how that goes.

To use clock_info's you need to make a clock that supports the way they work.
I created the simplest example I could and produce the simplest++ clock.

https://github.com/espruino/BangleApps/tree/master/apps/simplestpp

There is also a clock_info wiki or tutorial somewhere as well.

You dont need to poll the clock_info they have their own timers, they emit a draw event that your code then reponds to.

I tried it out. My only thought would be to make the full screen version a settings option.
To implement sunrise and sunset take a look at the code in the sunrise / sunset clock_info app.

https://raw.githubusercontent.com/espruino/BangleApps/master/apps/clkinfosunrise/clkinfo.js

(function() {
  // get today's sunlight times for lat/lon
  var sunrise, sunset, date;
  var SunCalc = require("suncalc"); // from modules folder
  const locale = require("locale");

  function calculate() {
    var location = require("Storage").readJSON("mylocation.json",1)||{};
    location.lat = location.lat||51.5072;
    location.lon = location.lon||0.1276; // London
    date = new Date(Date.now());
    var times = SunCalc.getTimes(date, location.lat, location.lon);
    sunrise = times.sunrise;
    sunset = times.sunset;
    /* do we want to re-calculate this every day? Or we just assume
    that 'show' will get called once a day? */
  }

ok. Just been out and done 6000 steps, before getting back in the car.
Before I left I rebooted both watches to reset the step count to zero

First 2000 steps, watch 1 on left, watch 2 on right - both within 100 steps
The reset watch 2
Second 2000 steps, watch 1 on left, watch 2 on right upside down - both within 100 steps
Then reset watch 2
Third 2000 steps, watch 1 on left, watch 2 on left upside down - both within 200 steps

Which firmware are you using ? Install the firmware clock_info and you can see it via the Lato clock. There was an issue with some Bangles having a DC offset but this was fixed a while ago. Unless you are on realy old firmware you should not see that issue.

Are you saying you definitely only recorded 20 steps when looking at the step count in Lato (which uses the clock_info and reads direct from the step count Bangle.getHealthStatus("day").steps). I was a bit confused by the three ... after the numbers.

I would not expect the GadgetBridge step count to reflect total steps unless you have been carrying round your phone all the time. See
https://forum.espruino.com/conversations/385539/#comment16942663

Don't think battery will be a problem, the accelerometer is always on anyway.

Thats interesting, which Pedometer widget are you using?

It should work on either wrist. I will try a test with a Bangle on each wrist.

Sounds like all 3 would work.

Could you explain, option 2, motion value?

I built the daisy clock. To get a decent looking ring I did it with a series of fixed images. The resolution of the screen is too course to get non pixellated curves drawn. We really need a 360x360 screen.

Wow, I will settle for that!!!

I think everything is working fine. It is just that I had forgotten that when you connect through the IDE you get `> bluetooth' displayed on the screen regardless of the log setting and that whilst connected to the IDE the console.log output goes to the IDE and not to the log, this is why I was not seeing anything in the log when I viewed it through the IDE.

I'm wanting to use this to track down a hang I get in the Lato clock when I am using lots of clock_info's. The hang is rare. I suspect it mostly happens when I been using the sunrise clock_info, but I dont yet have a provable test case. A short button reset causing the clock to reload and everything is fine again. Its as if the clock timer does not get restarted. I'm now trying out with simplest++ as that is smallest clock code that supports clock_info's.

Yeah agree, lets keep menu labels as short as we can so that they are readable. LCD/Calibrate is enough in my view.

Good point. Default is programmability = True. My tests were done with that. I have not changed it. Will investigate further as the ability to log without display is a useful feature.