Most recent activity
-
I think I mentioned at https://forum.espruino.com/conversations/390481/#17137641 but if you use setUI({mode:"clock"}) it automatically sets up the middle button to go to the launcher - maybe you didn't have that?
That would be it. And now I remember why it's missing. I'd originally added that wen I first started creating the watch face in the emulator, and it generated the following error:
Uncaught ReferenceError: "setUI" is not defined at line 279 col 1 in app.js setUI({mode:"clock"});so I had to remove it again.
Can I offer a suggestion to add a
setUI()function to the emulator that does nothing. It would allow that line to be present, thus permitting developers to use the exact same code in the emulator as they are in production. -
Never Mind - I found the solution. Just can't delete this post.
-
I've managed to get my Bangle.JS into a bit of an unresponsive state. In the course of trying to save as much power as possible to extend battery life, I started by turning off BLE. That looked good, because the watch no longer appeared when I scanned with my cellphone.
"Great!" I thought to myself. "That works. Now I can go into settings, and turn it back on to finish developing my watch face." Except that now that it's running the first version of my watch face, the button does not enter the settings screen.
I specifically did not disable "Wake on BTN1" after a discussion in another thread about maintaining the default behaviour of the button. However, at the current time, the button does cause the light to come on, but it does not enter the settings screen.
So given this state, and the lack of BLE, what options do I have to get this thing back to normal operation. A long press on the button does eventually reboot the watch, but it returns to the above state. Is there some magic incantation I can cast to get it back to the factory default condition? While I'm at it, what could I have done that caused it to get into this state? I'd have thought that "Wake on BTN1" would have been enough, do I need to add something to the watch face itself?
The watch face can be found at https://github.com/dgnuff/BangleApps/tree/master/apps/travelwatch and it can be deployed from https://dgnuff.github.io/BangleApps - look for "TravelWatch". At the current time, there are two additional timezones hard coded to test that logic, they work right if you live in the "America/Los_Angeles" timezone, but other than that they will be wrong. I'll be working with https://www.espruino.com/Bangle.js+Custom to fix that, but for now, I need to fix these other problems first.
-- LATER --
Got it back from the grave, I found that by rapidly clicking the button after a reboot, I could get it into a "Reset" screen. From there a factory reboot did the trick. That said, this is still a concern, because it probably won't come as any kind of surprise when I say that I really don't want to do this again.
So what might have got it into that state? While I'm at it, how much of a drain is it to leave BLE enabled 24/7, just as long as I'm not actually communicating with the watch? I found the HRM in the watch, is setting "HRM Interval" to "Off" sufficient to keep the HRM disabled. And since I didn't see any references to GPS in the settings, does that just stay inactive unless something explicitly enables it?
-- EVEN LATER --
This is definitely a bug with the watch face. After doing the factory reset, I deployed the watch again, same behavior. This time it's far less of an issue, because I've left the "default" watchface as "AntonClock" that is baked into the firmware, and that one behaves correctly. So to get things back after starting my watch face, I can just reboot, it drops into AntonClock, and I can get to settings from there.
But I really would like to know what's wrong with my watch face so I can fix it.
-
Yeah. I got that when I tried it on the phone. The laptop never even got to the point of showing me the available versions to upload. So I'd guess that you're correct that BLE is broken. Which is kinda a surprise, since it's a builtin Bluetooth chip, not a USB dongle, which supposedly has BLE. At least it can see the watch and pair with it. it just can't actually talk once it's connected.
-
This is the app repo at https://banglejs.com/apps/ . I'm not yet to the point of connecting to the IDE. I need to get the firmware up to date on the watch before I'll even consider putting a custom watch face on it.
There's no issue with the computer Bluetooth. It's a laptop with wifi built in. Device manager shows all the necessary devices, all claim to be working correctly, and driver update tells me the best drivers are already installed.
And if you note in the last paragraph of my message
1) my phone can see both the computer and the Bangle.js when I have it scan for Bluetooth devices, proving that Bluetooth is working on the computer.
2) The computer does pair with and connect to the Bangle.js, becayuse the popup says "paired", and the button shows "Disconnect" which kinda implies we've got a connection.
It's just that the actual firmware upload fails.
-- LATER --
Doing a little research, it looks like BLE support on the laptop may be a bit dodgy. I tried browsing to the app loader on my smartphone and got a bit further. I got it connected, and the hamburger in the Firmware Update now reports I'm on 2.18, and that 2.19 is available.
Update is in progress now, we'll see how this goes. Thinking ahead, this seems to indicate that I'll have to use my phone to upload apps to the watch. This will be a bit of a pain vs direct upload from the IDE, but any port in a storm, I guess.
-- EVEN LATER --
Yeah, it definitely looks like BLE is pooched on the laptop. I tried it again on the laptop this time from within the IDE. Similar result to App Loader: it sees the Bangle.js claims it's paired, but then hangs at "Connecting".
-
I got my Bangle.js 2 today, and the first thing I did was to head to the app loader to do a firmware update, and set the time.
The Bluetooth connection seems to be very unreliable. I have the device paired, at least it shows that way in the app loader popup, and the button top right shows "Disconnect", implying it's got a connection.
However clicking on the hamburger to configure and upload either produces a popup warning me that this is only good on the Bangle.js 2, never mind that I already told the web page that I have a Bangle.js 2, or it just turns into a spinning icon that spins forever and does nothing.
I'm getting the same results in both Chrome and Edge, so it's not a browser issue.
Before you ask, Bluetooth is turned on and working on both the computer and the Bangle.js 2. I can see both my computer and the Bangle.js 2 advertising when I scan for devices on my phone. Plus the app loader page does show a "Disconnect" button, and the fact that it's paired with the watch, so everything should be working.
That's the problem. Emulator is happy. Deploying to production - watch this space for details.