Most recent activity
-
@Serj thanks for your detailed reply, it's definitely good to hear first-hand experience from someone who's worn it day to day.
I noticed that many people have problems with the button and contact corrosion on the Bangle 2. Probably, relative to all users, these cases are not so many, but the first version of the Bangle did not have such problems, right?
Yeah that's a well documented issue with the B2. It wasn't an issue on the B1 because the SWD pins weren't exposed, you had to open it up to reprogram it.
It does seem like there is an argument to suggest that the B1 was sturdier, even if just from a design perspective than the actual hardware itself. @Gordon what was the reason for the B1 being discontinued? It does seem like there could be good use-cases for it with regards to using the watch in a 'tougher' environments.
-
Thanks Gordon, the use-case I'm thinking about is the watch not being handled with care (e.g. being chucked around). So was just wondering how much of a beating the screen / carcass could take before it would become compromised.
I wasn't aware of the cover so that would definitely help with regards to shock absorption! :)
-
Just from a visual perspective, the Bangle 1 encasing looked a bit more ruggedised than the Bangle 2, other than the IP rating being dropped from 68 > 67, is there any other factors that would suggest that the Bangle 2 wouldn't necessarily withstand the same physical wear and tear the Bangle 1 would?
For example, how tough are parts like the screen / casing / straps? And how do they compare to the Bangle 1, and to other industry standard devices like the Apple watch / Fitbit etc?
-
Perfect :) and yeah that is a challenge too. My plan for that was to return the custom UUID data in the
SCAN_RESPONSEpacket - I found this article, the array format forsetScanResponseis pretty horrible, I noticed you mentioned you'd log an issue for adding a nicer API, any updates on this?In the meantime, any tools or references I can look at to help me build a scan response payload? e.g. if I wanted to advertise a custom service UUID with some data
-
I see in the docs it mentions there is currently no support for custom UUIDs in
setAdvertising, any idea if or when you see this coming?Bit of a limitation for me at the moment as I would like to advertising some custom data without having to connect.
-
@Gordon worked a treat, thanks! I'm intrigued, how did you apply the fix without me having to update Espruino 🤔 When the tag is flashed are the libs downloaded in the fly?
Personally, I'm not sure I see the use-case for having a pressure sensor on the watch, it's certainly not worth sacrificing waterproofing for. However, I think people could see real value in a microphone / speaker, and that would be something I would see as a good trade-off with regards to waterproofing.
My wishlist would be:
Disclaimer - I was not one of those people who were complaining to you about there not being a microphone or speaker. I think you've done an amazing job with these, and not just from a hardware perspective but with the whole Bangle ecosystem (emulator, app loader, docs etc.). So only support & praise from me, keep up the great work!