halemmerich

Most recent activity

• Lost charger cable for bangle.js2

  in Bangle.js • 3 hours, 36 minutes

  

  There is https://www.amazon.de/dp/B077RFZJ8Z/ref=­cm_sw_r_apan_glt_i_6ZH025Y98QRKS0HJK3A7 linked on https://www.espruino.com/Bangle.js2#char­ging.
  Probably there are other cables usable as well, but be sure to check the pin out (+/- on the correct pins) to not kill your Bangle.

• Where is this battery draining code from?

  in Bangle.js • 20 hours, 27 minutes

  

  I think battery falling like that can only be either a horribly wrong value for the battery calibration (and relatively low charge being shown as full) or GPS being active. There is just no hardware taking that much power besides full power backlight, but I suspect you would have seen that at some point. Do you have agpsdata configured for autoupdating? Maybe there is some bug not turning GPS off after the update.

• Pebble with distance and steps - Not updated on Bangle app store?

  in Bangle.js • 2 days, 6 hours

  

  There are two app loaders you can use (additional to several ways of running your own). One at https://banglejs.com/apps/. That one needs manual intervention by @Gordon to be updated and should contain more stable (older) apps. The other one is https://espruino.github.io/BangleApps/ and is automatically up to date with all accepted pull requests of the Github BangleApps development project. The pull request you mention (https://github.com/espruino/BangleApps/p­ull/2778 ) has been merged two days ago and is available since then on the development app loader.

• Navigation with Maps

  in Bangle.js • 1 week, 3 days

  

  I have used the OsmAnd Pebble Integration by just filtering normal notifications in GadgetBridge. Watch buzzes with a new message whenever Osmand would have done some voice output. That worked well enough for walking around in areas with street name signs and when I had at least an rough idea of my route it even worked fine for biking. Normal OsmAnd notifications on the Bangle are completely useless as they are updated much too often (a notification every few meters).

• Proposal for new Recorder features

  in Bangle.js • 1 week, 3 days

  

  Yes, default mode of BTHRM replaces internal HRM sensor and the events are usable in all apps without modifications.

• Ideas for stress testing GPS via GadgetBridge

  @halemmerich started

  • 8 comments
  • 400 views

  @Gordon replied
• Ideas for stress testing GPS via GadgetBridge

  in Bangle.js • 1 week, 5 days

  

  I think I found the issue:
  The location manager was not cleaned up when the Bangle was disconnected by connection loss. This pull request should fix that.
  https://codeberg.org/Freeyourgadget/Gadg­etbridge/pulls/3132

• Bangle.js 2 Cutting Edge - new heart rate algorithm

  in Bangle.js • 1 week, 5 days

  

  Either you managed to scratch the glass or the protector is still on. If I remember correctly it had no tab or something like that to pull it off. On my first Bangle I thought I had received a scratched one and only a few days later I discovered it to be a protector. It was a tiny bit "frosted". Without the protector you should have a mirror finish just like the display glass has.

  Edit: @adjtm hehe, you ninjaed my post very closely :D

• Ideas for stress testing GPS via GadgetBridge

  in Bangle.js • 1 week, 5 days

  

  I have tested a bit again with current stable firmware and GB (2v17 and 0.74) and the changes for android from https://github.com/espruino/BangleApps/p­ull/2534 since without them I can not get GBGPS to activate on GadgetBridge:

  • Connect watch to GB and start GPS Info to get GPS updates -> works fine
    
    • Battery level available in GB
      
    • Connected shown in GB
      
    • Sending notification works
      
    • characteristic write messages in logcat
      
  • Put watch into metal box
    
    • Battery level vanished from GB
      
    • Few ms of disconnected (grey) state, then connected state shown again
      
    • After "reconnect" still no battery level
      
    • GB still trying to send GPS, but not characteristic write messages
      
    • Debug notification does not work, just added to queue like GPS messages
      
  • Take watch out of box
    
    • nothing changes, stays fake connected without battery level
      
  • Reload watch (2 sec button press)
    
    • nothing changes again
      
  • Disconnect and reconnect watch with GB menu
    
    • Everything returns to normal
      
      

  It seems there is a problem in the GadgetBridge GPS handling code, not the GPS code on the watch. It is in the metal box when the problem starts, so no influence on GB at that point in time. Without triggering GBGPS on the watch the "fake" reconnect does not happen and the actual reconnect after the box is openend restores full functionality.
  Somehow some state in GB seems to be not cleared as it should be when the GPS service is active.

• Where is this battery draining code from?

  in Bangle.js • 1 week, 6 days

  

  Slightly off-topic, so I will keep it short:

  By making apps fast load that were never designed for it

  Apps do not need to be designed for being loaded without a reset, they need to be able to clean up if another app is loaded without reset. Fastload Utils just enables loading every app after one that is able to clean up. There is no (intended) way to fastload with the current version if the currently running app can not clean up. There should not be any stuff accumulating except for bugs in apps regarding clean up. Real reset is still done for leaving nearly every app but clocks and launchers.

  Edit: Nevertheless removing it as a possible source for errors is what I would do as well.