Most recent activity
-
This works for me, assuming "maxZ" is defined somewhere:
try { function accelHandler(accel) { if (accel.z > maxZ) { maxZ = accel.z.toFixed(2); } drawHand(Math.round(maxZ)); //layout.render(); } Bangle.setPollInterval(80); Bangle.on('accel', accelHandler); } catch(e) { print(e.message); print("value exceeds limits"); drawHand(MIN); } -
Implementing this is beyond my skills, but it would make the watch far more useful for things like cycling, hiking, paragliding - basically all outdoor activities where you need constant location information. Constant onboard GPS usage shortens battery life from a few weeks to a few hours.
-
If you seriously want to save battery, you might look into BLE wheel and heart rate sensors. If you mount the watch to your bars, you could also power if with an external battery or a hub generator.
40min sounds very short, my watch easily lasts more than two hours with the tinyVario app, so there might be a problem with your code as well. (tinyVario used GPS and barometric sensor, no heart rate) -
If you have access to a 3D printer, you could try this.
-
- 5 comments
- 424 views
-
Will try, thanks!
-
2v14 stable, yes. It happened on 2v13 as well.
I just turn the barometer on when the app starts. It kind of works after the error, but there seems to be a pressure offset. As far as i know, the barometer chip has some calibration values that are being read at startup, maybe they are not read correctly? -
Sometimes i get the following error when powering up the baro sensor:
Uncaught Error: I2C Error: Arbitration (start) at line 1 col 43 Bangle.setBarometerPower(true, "tinyVario");It seems to be totally random, should i just use "try" and "catch" to repeatedly power up the sensor until i get no error? The sensor still works after this error, but pressure readings are way off.
Maybe enable it by default? I have no idea how many people just use their Bangle without developing for it, but most of those probably never read this forum and won´t change their app loader settings. I really don´t see a privacy problem with this.