Search results for:

Yes, Oxygen OS is very aggressive when it comes to killing background processes. If you haven't already, make sure that Gadgetbridge is allowed to autostart and that it's removed from battery optimisation. And that all permissions are given to the app.

It seems unlikely that both watches would have some kind of fault that would cause those issues...

My gut reaction is that there's something about your setup that's the culprit (but of course, human intestines are notoriously bad at troubleshooting tech so I might be completely wrong)...

What is your setup? Firmware version (if you're not on the latest it might be a good idea to update), installed apps, phone, etc...

I've seen that when forgetting to close a row with a semicolon somewhere. Check if there are any warnings when you paste the code in the right side of the Web IDE.

I'm a little confused... Those are the exact steps described in the video you linked. And also what is described in the docs:
https://www.espruino.com/Bangle.js2#firm­ware-updates

Was something unclear about the instructions in the video (or in the docs, if you've seen those)?

You mean something like what's talked about here ?

Switch 9 and 10. First go into DFU mode on the watch and then pick the DFU device in the list of Bluetooth devices.

I took a shower with the watch attached to my wrist yesterday. Maybe this caused the button to have a malfunction?

It's been covered before, but worth repeating. IP67 is not "waterproof". Splash-proof/"accidentally and temporarily submerged in shallow water"-proof would be a better description...

A shower head can spray the watch with way higher pressure than what the watch is rated for, so I would not risk taking it into the shower.

Confirmed fixed in Gadgetbridge 0.63.1.

I've got the exact opposite experience. My Bangle.js 1 won't stay connected unless I keep my phone on me, while the Bangle.js 2 will stay connected two rooms away (AAC walls). The Bangle.js 2 should definitely have better range than what you're seeing...

Are you on the latest firmware?

I can confirm this behaviour. I've also added this info to your Github issue.

@ajkm That's taken care of on the phone side, and is already implemented in Gadgetbridge (the Android app). But, IIRC, you use an Iphone so maybe that option isn't available there...

@WizardStan If you install the GB debug app on your watch and have that open when a notification is received on the phone, what does it say (when the issue is active)?

It normally isn't...

Using the nRF tool to update isn't the most user friendly method, but the issues you experienced isn't normal and hopefully the issue should be fixed now that you've managed to update. Once Gordon gets the App loader firmware updater working it'll be a breeze...

@user137493 Looks great!

@Fteacher I ran the Lazy Clock through the Bangle 2 emulator and it looks fine... From what I can see after a quick look, it's just the button logic that needs an update. If no-one else does I might take a stab at it myself in the near future.

@Gordon Maybe a backers update about this would be good...

That's as good as it's going to get with a 3-bit display, meaning you have only 8 colours to work with. Any other colours are created by dithering. You can see an example of the palette here:
http://forum.espruino.com/comments/16223­395/

I think it looks great though.

Edit: the wave clock is just using the available colours properly, which prevents dithering from occurring.

@Gordon Might be that @Muldjord isn't seeing any results with the described method since it doesn't seem like the firmware updater in the App loader works. I just now tested updating to 2v10.244, and the fwupdater seems to get uploaded to the watch but when it reboots there's a quick "no new fw" before it boots up to 2v10.243 that I already had installed.

That could just be a bug fixed in 243.

Ref: http://forum.espruino.com/comments/16303­108/

Maybe @Gordon has some ideas, but I'd try a full reset:
https://www.espruino.com/Bangle.js2#dele­ting-all-code

Followed by an update to the latest cutting edge firmware:
https://www.espruino.com/Bangle.js2#firm­ware-updates

@Gordon I have no idea... Only discovered this setting myself a couple of days ago.

No worries... I also happened upon the Poweroff app in the App loader just now. Hadn't seen that one before and it will also do the trick.

It's in the Settings menu, at the bottom. And this kind of info, with much more, can be found here: https://www.espruino.com/Bangle.js2#powe­ring-off

Maybe Feedback instead of Notifications? Doesn't feel quite right though...

I don't get the FW anymore on 243, so you fixed that I guess...

As @Tx mentioned above, the issue seems to be found on Codeberg. And that fits kind of nicely with the message GB debug got just before the app crashed on my phone (see the attachment).