Widget: Battery Meter

Please use this thread to report any issues or problems you are having with the widget.

Battery Meter: https://apps.garmin.com/en-US/apps/5...a-f8bea4ca47d7
Battery Meter v2: https://apps.garmin.com/en-US/apps/e54849a1-cc77-4c6d-a01f-99b68e7503f2

DESCRIPTION:

Simple battery meter widget that displays a graphic battery meter and text representation.

INSTRUCTIONS:

Battery Meter:
  • Fenix/D2/920XT: Change the color scheme by selecting "Start/Enter" button.
  • Vivoactive: Change the color scheme by tapping the screen.

Color scheme will be remembered between widget uses.

Battery Meter v2:

Settings for color scheme are managed in Garmin Connect Mobile.
  • Yes, I am running v2.7. When I press the right side enter button, it just takes me to the activities page. Perhaps there is something I am missing about adjusting the colors, I can find any way to do it.


    I don't have a Vivoactive so let me do a little research and get this ironed out. To confirm, it loads fine and looks correct, you are just unable to use the right hand select/enter button to cycle through the color schemes?
  • Former Member
    Former Member over 10 years ago
    That is correct. It looks exactly like the picture and tracks the battery accurately, but the color changing feature of the watch button does not work.
  • That is correct. It looks exactly like the picture and tracks the battery accurately, but the color changing feature of the watch button does not work.


    Turns out that the Vivoactive doesn't use the enter button the same as the fenix 3 and 920XT do. I have pushed an updated version. For the Vivoactive you can change the color scheme by tapping the screen. Please let me know if this works for you and everything is functioning correctly for you. Thanks for being patient and helping me work through this.
  • Former Member
    Former Member over 10 years ago
    That works now, thanks for fixing it!!
    If there is any way you can make the numbers a bit bigger, perhaps make the gauge a bit smaller, it would be perfect.
  • Former Member
    Former Member over 10 years ago
    The app indicates 97 or 98% even though the clock is 100% charged
  • [QUOTE=Lutz Balschuweit;700943]The app indicates 97 or 98% even though the clock is 100% charged

    I can't reproduce the issue you are describing. When I use the battery percentage shown at the top of the settings menu and the widget, they match. Where are you looking at the battery level to compare with it and what device are you using?
  • Former Member
    Former Member over 9 years ago
    FR235 v3.10

    When switching to the widget, it changes the color of the watch face. I currently have the color of my watch face set to use the color of my running activity profile (red). However when I switch to check the battery level and then go back to the watch face, the color is now a teal/blue color. I can get it back to red by selecting run mode and then going back to the watch face.

    Is there a way to fix this?

    Thanks,
    Henry
  • FR235 v3.10

    When switching to the widget, it changes the color of the watch face. I currently have the color of my watch face set to use the color of my running activity profile (red). However when I switch to check the battery level and then go back to the watch face, the color is now a teal/blue color. I can get it back to red by selecting run mode and then going back to the watch face.

    Is there a way to fix this?

    Thanks,
    Henry


    I don't think that the widgets work like this, which watch face are you using?
  • Former Member
    Former Member over 9 years ago
    I am using the default watch face for the 235. It is just a digital clock and the hour is set to the color of the last activity profile used. I like to have the red hour number which is the color of my running profile, but whenever i use the battery widget, and go back to the clock, it blue.
  • I have been unable to reproduce this on an internal build (v3.13). I'll try on 3.10 and see whether there's something that's been updated that may already fix this issue.