As you may have noticed, Google is planning to discontinue the Nearby Notifications. This means that the 1.2.12 firmware which currently ships with button-activated mode change into URL-mode will be obsolete.
As our user base has grown we have received some great feedback, now would be a great time to address the ideas for next software version.
- Should we bring the 2.X branch / GitHub master out of beta? So far I haven’t heard anyone saying that they’d gone back to RAWv1 or URL mode after starting to use the RAWv2 format.
On the other hand, a lot of users are perfectly happy with RAWv1 as it is, and update would probably break some existing applications.
- Battery measurement: Current battery voltage is not a great predictor of remaining runtime, especially in cold temperatures. It seems that we could get better results by synchronizing the ADC to radio transmissions.
- Button: Current process to enter bootloader by holding down button B while tapping R is a bit cumbersome. Maybe a long press on button “B” could trigger a reset and start tag on bootloader?
- Button: As the URL mode is no longer useful, what kind of action a short press should trigger? Switching between RAWv1 and RAWv2? Fast mode and long-life mode?
- GATT: So far the GATT profile which ships with 2.2.2 has caused more confusion than new use-cases. GATT-connectible devices show up on bluetooth scans for headphones etc which some users find annoying. There’s also a security concern on allowing DFU updates without physical access. Have you used the GATT profile for something, or should we disable it by default?
- NFC: Some kind of NFC event when the NFC field is weak can lead to a hangup in NFC driver and lead to increased current consumption. We’re investigating how to fix this issue.
Please let us know your thoughts on these matters as well as anything else you’d like to see