Most recent activity
-
-
-
Looks like you did this already, but best to comment on the original post at http://forum.espruino.com/conversations/377121/ as we're trying to debug it on that
-
-
Can't you add an option to let the custom BangleApps show the official and current appdates.csv?
Maybe... but then your apps wouldn't appear in it - which maybe isn't what you want?
But actually, since you have your own branch, you could do this pretty easily yourself? The code is at https://github.com/espruino/EspruinoAppLoaderCore/blob/c46b4edd2052d0df37fea41f8839af8175a78ec9/js/index.js#L99-L118 so either you could change that, or you could just copy & paste the code into your local
loader.js
file with the different URL.Or if you wanted to do a PR to make it use a
Const.APPS_DATES_FILE
constant instead then you could easily add a one-liner to loader.js to get it from wherever you wantIt would be great if we could have the official BangleApps and a personal BangleApps available
This feels pretty niche... I mean you can always just go to banglejs.com/apps on your phone's web browser, see what's new, and then upload from Gadgetbridge? But if you wanted to send in a PR for a menu option in Gadgetbridge that could definitely be added.
-
It's possible it's to do with some configuration on the watch itself that's causing bluetooth to be disabled. Please can you try the steps here and see what happens?
https://www.espruino.com/Bangle.js2#resetting-without-loading-any-code
After that, you should hopefully be able to connect (it ensures it ignores any config that was previously on the watch). After that, maybe try upgrading the firmware via the 'firmware update' app.
If all that fails, you could also try uploading firmware using the NRF Toolbox app: https://www.espruino.com/Bangle.js2#android-ios-app but I'd say try that only as a last resort
-
Is this all connected (i.e. the same)?
In the menu, yes. It is possible to manually configure it with
https://www.espruino.com/Reference#l_Bangle_setOptions
and lockTimeout/lcdPowerTimeout/backlightTimeout thoughHowever it may not be such a good idea. The reason we 'lock' is twofold - to stop accidental presses but also because when the touchscreen is powered on it draws around 1.5mA (IIRC). It means that all by itself, the touchscreen would flatten the battery in around 5 days.
-
the default seems to be "off" and I wonder why that is
It's because at least initially it made it harder to connect sometimes - and for everyone that has a connection error that's one more person not having it work out of the box and asking for support :)
the combo minified module might be broken
You mean this? https://www.espruino.com/BLE+Keyboard#combination
If it is, can you let me know for sure and what's wrong/what error you get and I'll look into it?
I'm not sure what you can do about the icon - I think if you're just a keyboard it'll work ok? So it might just be a side-effect of it trying to do two things at once.
In terms of security, I'd have said that
NRF.setSecurity({passkey:"123456", mitm:1, display:1});
would be a good start, which should force the requirement for a secure connection. You'd probably also want to turn the UART service off completely -
As @fanoush says, maybe you (or an app that use it) had enabled HID (which makes window 'grab' the device as it thinks it's a keyboard/mouse/etc).
Otherwise maybe enabling passkey pairing or something like that did it?