Avatar for johan_m_o

johan_m_o

Member since Sep 2021 • Last active May 2022
  • 2 conversations
  • 156 comments

Most recent activity

  • in Bangle.js
    Avatar for johan_m_o

    @Gordon I'm seeing a few issues with the new app.

    Sometimes I have trouble when connecting to the app store. It complains about an invalid json, and even when I manage to connect and update an app on the watch it shows an error about "t" not being defined in a json (or something along those lines). I'm thinking it's one of the apps I have installed, maybe... But I haven't seen this when connecting to the App Loader in a browser. Have done a completely clean install of the new GB app and also wiped my watch, but same thing. If I simply can't get the App Loader in Gadgetbridge to connect it has helped to force close the GB app and let it connect again.

    The app doesn't always release the Bluetooth connection to the watch. Even if I disconnect the BT widget shows it's connected and I can't reach it from other devices. In this case I have to kill the GB app for the watch to disconnect, even though GB itself shows that it's no longer connected to the watch. I have not seen this on previous installs of the regular Gadgetbridge app.

    The bitmap rendering of unknown characters and emojis is not working at all for me. The attached screenshot is me sending a test notification containing ♥️💪👁️. Been seeing the same in actual texts. And is the bitmap rendering supposed to take care of words containing special characters as well? If so it's not working for the Swedish å ä ö (small ä and ö renders properly by default, but not å or the capital letters).

    At one point when listing to music and starting a video on a web page (which automatically paused the music) there was a small toast informing me that the Gadgetbridge app isn't installed on my Bangle.js. Felt weird since it's deprecated...

    One really nice thing is that I finally can update the watch through the App Loader (ref later parts of: https://github.com/espruino/BangleApps/i­ssues/1069)! Might be the slowed down transfer speed that did it, so I'll try again with high MTU enabled later.

    Lastly a small feature request. It would be nice to be able to specify the development App Loader as the default.

    Love having a dedicated Bangle.js app though and not having to disconnect to use the App Loader.

    Edit: almost forgot... Incoming call notification doesn't work either, but maybe it's not supposed to since this is based on GB 0.66 (I didn't have time to compare the commit history).

  • in Bangle.js
    Avatar for johan_m_o

    Saw that with a bunch of apps in the last couple of weeks. I did a full reset and haven't seen it since. Suspecting a firmware update that did something...

  • in Bangle.js
    Avatar for johan_m_o

    @gfric You can turn off the low battery notification in the Android notification settings for Gadgetbridge. So you won't have to turn off Bluetooth...

    That suggestion sounds like a good idea though, but it might be on the radar already since I'm pretty sure I've seen this brought up before. Or maybe I'm misremembering.

  • in Bangle.js
    Avatar for johan_m_o

    On the top under the strap.

  • in Bangle.js
    Avatar for johan_m_o

    A shower nozzle can generate quite a high pressure (much higher than what you see at 1 meter deep water). I would not use the watch in the shower...

  • in Bangle.js
    Avatar for johan_m_o

    Have you checked the tutorials? You might find something there...
    https://www.espruino.com/Bangle.js2#tuto­rials

  • in Bangle.js
    Avatar for johan_m_o

    Sounds like you've taken the precaution of keeping the app working as default and made all your improvements optional. In that case I'd say it's just to go for it...

    Adding the @ for the original author to your commit message is a nice touch. That way they get a chance to review and possibly come up with suggestions on the implementation.

  • in Bangle.js
    Avatar for johan_m_o

    The watch did start off at 100% and I ran the code immediately after taking the watch off the charger. And looking at your graph, the battery percentage you've recorded pretty much exactly matches what I saw (with the plateau at 9-ish percent and then another plateau at 0).

    That blue line looks spot on though, so perhaps this is something we'll have to live with.

  • in Bangle.js
    Avatar for johan_m_o

    @Gordon The new battery monitor algorithm is working really well. I've been using my watch as regular for the past week and haven't charged it since my message above.

    The battery percentage has been much more "normal" without any sudden drops, but there is one quirk.

    For the first 5 days there was nothing special, although I did feel that the battery was depleting slightly faster than normal. By day 5 the level was down to 9% and usually I can get a week of battery life without issue. But, then the level stayed at 9% for more than 24 hours and have since started dropping very slowly. Now, almost exactly 7 days since taking the watch of the charger, and 48-ish hours since it hit 9% the level is down to 5%.

    Seems like the voltage levels in the algorithm needs a bit of tweaking...

Actions