-
@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/16223395/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.
-
Maybe @Gordon has some ideas, but I'd try a full reset:
https://www.espruino.com/Bangle.js2#deleting-all-codeFollowed by an update to the latest cutting edge firmware:
https://www.espruino.com/Bangle.js2#firmware-updates -
@Gordon I have no idea... Only discovered this setting myself a couple of days ago.
-
-
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#powering-off -
-
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).
-
-
-
-
The
jshFlashWrite...
message appears every time I lose connection due to Gadgetbridge crashing. And the address changes, the latest one read0x00052...
.It doesn't seem to make any difference if I pair the watch or not in Gadgetbridge. I just tried without pairing, and the app still crashes.
I'll install the 242 firmware in a moment and get back to you.
-
@Gordon The last couple of days I've seen that my Bangle.js 2 looses connection with my phone quite frequently. Haven't had much time for troubleshooting though (things like testing different versions of apps, both on watch and phone, etc), but today I noticed a way to trigger it.
When pressing play in a Netflix notification the Gadgetbridge app crashes and restarts, but the bluetooth connection is not resumed automatically.
I have debug messages active on the watch and when the crash occurs this is displayed on the watch:
jshFlashWrite SPI addr 0x00045
(Don't know if there's more to the message. That's all that fits on the screen and I can barely see the last 5 and most of the times only half the 4 is visible.)I'm also attaching an excerpt of a logcat I saved during the app crash. If needed I can send you the full thing too...
This was observed/logs saved on Bangle.js 2, firmware 2v10.240 with Android integration 0.04 and Messages 0.09 (but I'm seeing the same with 0.10 installed) installed on the watch and Gadgetbridge 0.63.0 on the phone.
This is probably not the only reason for Gadgetbridge crashing, since I've seen loss of connection without Netflix running on the phone as well, and I'd guess that it is Gadgetbridge crashing (for whatever reason) that is the cause of my issue.
Edit: forgot to add that I've tried this on a clean install of Gadgetbridge too, and with versions 0.61.0 and 0.62.0 as well.
-
-
-
That's not the cutting edge build though. You'll find that here (also linked in the firmware update instructions):
https://www.espruino.com/binaries/travis/master/ -
@Gordon Another manufacturer skipping components huh? Sucks... I have the the "something white" in there, so that feels good at least. Must say I absolutely love this watch!
-
-
I saw the same thing and did a full reset of the watch and everything started working after that.
There's an issue for this open on Github, and a few hours ago Gordon commited a fix that might take care of this. If you don't do anything else than update the firmware to 2v10.239 it would be interesting to see if that fixes things.
-
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...