Search results for:

I did not constantly monitor the screen but just noted that after 2-3mins it was ok again. I did not do anything on the watch in that few minutes (no screen touch or button press).

My assumption is that because of the low power something did not correctly work/communicate anymore, probably as you said "just" the communication to the screen.
And when the backlight was off and the battery could recover for a short time again, maybe it just raised the power enough to pull off a full redraw again.
Yes, this has never happened to me before but usually I also don't allow the battery charge to go below 10%. Just this time I completely forgot.

Unfortunately I did not make a picture of the screen. It was definitely not connected to temperature as I was inside the whole time and the temperature-value (displayed as part of my LCARS watchface) always showed 30-33°.

But I can describe my actions and what I observed:

• start at normal LCARS watchface, locked. no visible distortion.
  
• press button. lock widged disappears
  
• press button. "loading" box appears for a bit then the upper ~1/4 of the screen looks like the Settings/Launcher menu but with small quirks here and there. Below that a part of the "loading" box remains a bit distorted and on the remaining screen there are partly color spots/leftovers from the LCARS watch and partly stripes/dots that look like from the Settings/Launcher menu.
  
• press button for 2s. In the middle of the screen some movement and 1 or both vertical lines for the "loading" box appear, but only part of the content.
  
• no matter what clicking or touching the screen I did it stayed corrupted.
  
• after ~2-3mins the screen recovered and showed the LCARS watchface again properly.
  
  
  

Firstly thanks for the effort in the previous months to reduce the power consumption of the watch. When I bought it in February it ran a full week on a single charge and I expected that to go down over time when I added more apps/watchfaces.
Instead in the previous run it managed to not bother me for two weeks straight 🙀

Maybe that's a reason that yesterday I forgot to charge the watch and unfortunately it ran flat. What surprised me is that it apparently did not shut itself down in time and I also could not turn it off anymore when I realized I was on 0% (but still living).

When I tried to get into the Launcher menu the screen just garbaged up and I couldn't do anything besides reloading which then corrupted the screen a bit differently again.
My assumption is that the power was so low that either the CPU or the screen drawing did not have enough power anymore to redraw the full screen and in that state I could not reach the "Turn off" menu anymore.

I would have assumed that the watch turns itself off before it reached such a low state but either it wasn't there yet (but already pretty much unusable).
Or does this self-shutoff maybe not exist at all (or is broken?)?
If the power runs out (or goes super low) while the watch is still alive, is there a risk that it corrupts its settings or other storage?

Is there another way to shut down the clock without the settings-menu? I understand that different timings of pressing the button are just different stages of "resets" but I didn't want to reset just shut down the watch safely.

I had the exactly same issue as sachinm had after updating to the latest cutting edge firmware version.

Using the reset procedure as halemmerich suggested without loading code I could connect again and reset to the stable 2v14 firmware.
With that version everything works again.

Thanks for the hint!

I had the same experience.
I flashed back to the stable version and then upgraded again to 2v13.123 and on the second try the notifications work again.

Thank you for that nice app :-)

I'd like to bring in some small suggestions. Of course, since those are just from my personal usage patterns, they may not match to others.

• for me, configuring seconds in a timer is an exceptional rarity. Maybe in the settings it would be possible to add a config, that enables/disables seconds for timers?
  
• initially you had that "Time Now:" text. While I think that in the context of a timer that info may not be too helpful, for me it would be useful if it were to display a "Ends at: hh:mm:ss" (or "Ending: ", "Until: ", ...?) time instead. If the fonts size is larger or the same size you had that line initially would not be so important for me :-)
  

Was there not a flashing envelope symbol in the top left? That's usually shown as well

Whoops, you are right, I completely overlooked that, sorry for that.

Thanks for the link to the Github issue, wasn't aware that I'm bringing up something that's already in progress.
I will try to check the Github too in the future before I post in the forums here.

Yes, I meant only the main message list.

Thank you very much for the explanation, I'll be patient and wait for the change :-)

Ah, that makes sense. Thanks for the instructions.

What puzzled me was, that there was no apparent display of any notification as I was navigating the Settings and still the buzzer was vibrating.

The behavior feels a bit off (as it seems different on the Clock app than in another app) and I tried to come up with an improvement suggestion. eg. if the button is pressed or the watch is unlocked and the display is touched stop the vibration. But the settings allow to leave the watch unlocked I realized that it's maybe not so easy to come up with something that not only fits my usage patterns but also other peoples' :-/

Would it maybe make sense to also allow for a limited number of "repetitions", eg. off/3/5/10/unlimited times?

Just curious, in almost all applications pressing the button has the semantic meaning of a "back" action.
("back" meaning back to the previous level, with the top node being the launcher).

This is the case in almost all apps, except the "Messages" app, where to get out of it one has to tap the "back" icon on the screen which (at least for me) feels like a UI inconsistency.

Was there a special reason why in the Messages app the back functionality was not put on the button but on a visual icon instead?

Hi, one odd thing I have recognized a few times now.

When on my Bangle2 I'm in not directly at the Clock app but eg. in the launcher or the Settings menu and then a notification comes in from the phone (eg. a WhatsApp or email) then the vibro motor buzzes as expected.
But unexpectedly it continues to buzz every few seconds until I long-press the button and return to the Clock.

My current Bangle.js2 firmware version: 2v12.107.

Updates after a few days of trying. What did I change in the meantime:

• updated Gadgedbridge to 0.66
  
• updated Bangle firmware to 2v12.107
  
• enabled "Connect to Gadgetbridge device when Bluetooth is turned on"
  
  

As of now there are still the "blackouts" each night, but in the morning it now seems to automatically reconnect without requiring a manual action.
I tend to suspect something on the phone somehow hibernating GadgetBridge anyway, even if I excluded it from power saving options.

At least for now it is working for me when I use it, thank you for your hints :-)

I have upgraded Gadgetbridge today to 0.66 and finally the battery history just fixed there.
With that I could confirm my feeling, that the charge level display seems a bit "flaky".
Could this be somehow in connection with the algorithm change that was discussed above?

Firmware on my Bangle2 is 2v12.93.

In the global Gadgedbridge settings "Reconnect automatically" is enabled, also "Start automatically."
"Connect to Gadgetbridge device when Bluetooth is turned on" is disabled though, I think I disabled that one because of a hint somewhere that it would drain battery.
I will try to turn that on for a day or two and see if/what changes.

Hi. Yes, I have to manually reconnect in the morning each day. I tried now removing the Bangle2 from Gadgetbridge and adding it one time with pairing and one time without.

Unfortunately with both attempts it did not change the behavior and still every night it disconnects :-/

My bangle.js 2 seems to be loosing the BT connection pretty reliably over night when I'm asleep.
It stays connected properly all day and until I fall asleep, but when I wake up it's always disconnected in Gadgetbridge.

I have installed the latest Gadgetbridge APK available from FDroid, updated to cutting-edge 2.12 firmware and excluded Gadgetbridge from energy saving options on my Android Phone (OnePlus Nord). But it's still disconnecting.

An indication can be seen in the Gadgetbridge screenshot attached showing the recorded heartrate. Every day looks pretty similar to this.

PS.: is it normal that it doesn't detect any sleep at all? Do I need a special app installed for that?

I like the new menu system system very much :-)

Today I have recognized a small drawing issue with multi-line menu entries when they are scrolled into the widget area just a bit and back.
When hitting exactly the right spot before scrolling back, it seems that some horizontal lines are not re-drawn completely.

I could reproduce it in the System->LCD menu with scrolling up&down repeatedly for different lengths and then suddenly especially horizontal lines (like in F and T) disappear. See the screenshot attached.