Problems with the battery duration

Posted on
  • Hello there!

    This August got a bangle.js 2 and I'm pretty happy with it, is what I want from a smartwatch.

    The only problem I've got is the battery duration. I really think there is a problem with the consumption of the smartwatch and I have no idea how to diagnose it.

    The first time I used it only lasted for a week but that was normal, I installed like 50 apps ant tested every feature.

    The next battery charge (more than 12h charging) also lasted for a week and this time had a very casual use. After this, I decided to try to configure the watch for the maximun battery so I did a factory reset and used it for only the basics: default face and notifications from the phone. And there it was, the battery graph (see screenshot) had a slope that was pointing to 4 weeks of duration.

    The thing is that after the first week the connection between my phone and my bangle did something strange, had to reconnect and after that the slope went back to 1 or 2 weeks of battery. This happened again after a new factory reset (new screenshot).

    I have no idea of what is happening and not sure how to diagnose it. I'm using the cutting edge firmware and a small list of apps, I also tried the last stable firmware.

    How can I start to discern what is happening?

    Thanks for reading!


    2 Attachments

    • Screenshot_2024-09-14-22-57-19-845_com.espruino.gadgetbridge.banglejs.jpg
    • Screenshot_2024-10-11-20-16-51-406_com.espruino.gadgetbridge.banglejs.jpg
  • Hi - please can you check and make sure the LCD timeout is low, and only Wake on Button is set in the Bangle's settings?

    But as you say this could be related to the Bluetooth connection. Someone asked about this recently and there's a bit of background in https://forum.espruino.com/conversations/399937

    But basically when Bangle.js has a bluetooth connection, it goes into a low power low speed communications mode after 1 minute of inactivity, but when something is sent to it or it sends something, it enters the high power mode for 1 minute. If you've got something like a notification from the Android phone that keeps coming in every few minutes, that could kick it into the higher power mode?

    To track down you could enable write log in Gadgetbridge on your phone, then dump it out, and look to see how often UART TX/UART RX lines occur normally.

    Also in Gadgetbridge, make sure allow high MTU is enabled in the device's settings (I think it's the default) - if the Bangle can send/receive just one packet it won't put itself into the high power mode

    If this is the issue I guess it's something we could look at as a firmware update - making the Bangle less willing to put itself into the high power radio mode (like requiring more than 2 packets before it does it)

  • Hi - please can you check and make sure the LCD timeout is low, and only Wake on Tap is set in the Bangle's settings?

    Just checked: LCD timeout is 10 and only wakes on button is enabled not even wake on tap is on.

    I thought wake on tap was more taxing than wake on button. Should I change it to wake on tap?

    But basically when Bangle.js has a bluetooth connection, it goes into a low power low speed communications mode after 1 minute of inactivity, but when something is sent to it or it sends something, it enters the high power mode for 1 minute. If you've got something like a notification from the Android phone that keeps coming in every few minutes, that could kick it into the higher power mode?

    My phone have a few permanent notifications, one of them is home assistant but it never triggers a visible notification in the bangle. Can a permanent notification triggen the high power mode without seeing the notifacion in the bangle?

    I don't think that I recieved more notifications in the last weeks compared to the first week of the screenshots.

    To track down you could enable write log in Gadgetbridge on your phone, then dump it out, and look to see how often UART TX/UART RX lines occur normally.

    I'll do it for some time and report back. How do I dump the logs? Where to find them?

    Also in Gadgetbridge, make sure allow high MTU is enabled in the device's settings (I think it's the default) - if the Bangle can send/receive just one packet it won't put itself into the high power mode

    High MTU is enabled.

    If this is the issue I guess it's something we could look at as a firmware update - making the Bangle less willing to put itself into the high power radio mode (like requiring more than 2 packets before it does it)

    My gut says is the phone but is very strange that after a factory reset I get like a week of low power usage.

    I'll check the logs and post them here after a day. And I'll be around, If there is anything ellse I can test just tell me.

    Thanks for you answer!

  • Sorry - yes, Wake on button is best - I wrote the wrong thing.

    Can a permanent notification triggen the high power mode without seeing the notifacion in the bangle?

    No - it's just when data is sent to/from the Bangle.

    How do I dump the logs? Where to find them?

    https://gadgetbridge.org/internals/topics/logs/

    but is very strange that after a factory reset I get like a week of low power usage.

    What if you just factory reset and leave it not connected to a phone? What's the power usage then?

  • Sorry for the wait. Tough weeks in the job and Factorio Space Age at the same time (the factory must grow).

    I have more than a few logs stored but I reaaally have to sanitize them. I had no idea how much personal information there are on those logs. Any advice on how to do this efficiently? Any topics I should just remove from the docs?

  • The important stuff we need is the UART RX and TX lines - you can delete all the rest (but it might be handy if you can keep the original file just in case I need to look into something further)

    ... but obviously you'll want to sanitise the UART TX lines which will include message contents/phone numbers/etc. It's probably enough that I can just see the GB({"t":"messagetype part and the time, and not what's after.

    Someone posted up just yesterday that they'd been having poor battery life and they tracked it down to the messages widget (which by default flashes once a second when a message is unread). So you could try uninstalling that (you don't need it) and see if it helps at all?

  • Attached is a log file from today. I'm keeping the original.

    I just removed the messages widget. I'll be around!


    1 Attachment

  • Thanks! I could be wrong on this but looking at the log it seems like you receive messages which then may stay showing on your watch with a flashing messages widget for half an hour or more.

    There was another thread on this recently where @WizardStan tracked the battery use down to the messages widget: https://forum.espruino.com/conversations/398746/

    You could try uninstalling it (or disabling flashing in the messages settings page)? The widget isn't vital, but if it's flashing every second for several hours a day on average, that would definitely hit your battery life.

  • In these three days without the messages app the battery seems to be going down at a slower rate. I'll update in a week or so.

    Crazy that it was the flashing of the icons that did that. If after a week or so I the consumption rate seems ok I'll install the widget and disable flashing to see if there is any change.

  • Post a reply
    • Bold
    • Italics
    • Link
    • Image
    • List
    • Quote
    • code
    • Preview
About

Problems with the battery duration

Posted by Avatar for Fenixin @Fenixin

Actions