Search results for:

The Bangle.js 2 already has a transflective display :)

This sounds different to the freezes I had. Do you use the default messaging ui app or one of the other ones? I had complete freezes (no reaction at all on the bangle), often remedied by disconnecting and reconnecting GadgetBridge.

I haven't seen it in while now and had this problem a lot before. I think there were some fixes regarding buzzes causing some buildup of intervals or timeouts and some other stuff regarding handling of messages fixed in current firmwares. Do you already use something newer than 2v18? I currently use 2v18.90.

It partly works, just the inital draw does not seem to happen. If you scroll up and down there are numbers drawn.

I had just enabled the Pebble-messages and disabled normal notifications for OsmAnd in the GadgetBridge notification filters. But at least for the current Bangle.JS GadgetBridge nightly installed from FDroid this seems to be no longer needed. With the default Message UI app the navigation messages seem to be handled correctly via some kind of native OsmAnd integration. At least I see arrows and symbols for things like roundabouts when using navigation with OsmAnd.

If the motivation is saving power this won't do much. AFAIK the display is still refreshed at about once a second. If no code is loaded the Bangle 2 runs for a really long time. I tried to record a discharge curve and lost about 20% of battery in 4 weeks before giving up. Maybe a 0 brightness setting would be more useful for very low power use.

It does not load another app, but it does not yet use the message events. It overrides the require call for the messages lib which is quite hacky. Boot order won't save that, only updating messages overlay to correctly using the messages event will help.
I wanted to have a go at updating messages overlay anyway since it does not work correctly with navigation messages. If you want to help out with that feel free to do so, otherwise I fear you will have to wait until I find some spare time :)

Nice, very useful. Was this the first opening of this particular watch? If so I need to get me a hotplate :) Mine fought back A LOT more using hot air.

Great :) The json you had posted seems to be valid, but if that indeed was the cause, there is a "Reset Settings" button in the "More..."-tab in the apploader that deletes the setting.json without using the IDE.

Maybe you can take the setting.info file from the backup and see if that one is valid? It also contains json.

Just delete the 4 setting* files and after a reload the settings app is gone. Do you have constant output on the left side of the IDE? If so maybe you can identify the app that is messing with your app update?

Yeah, copied the wrong link... https://www.espruino.com/Bangle.js2#resetting-without-loading-any-code

That can happen if some app does write to the console during the update. Just try again a few times. If it does not work, boot the Bangle without loading anything and perform install/removal then. There it should work. https://www.espruino.com/Bangle.js+Getting+Started#resetting-without-loading-any-code

That seems weird. Maybe the app info file that gets generated during install was somehow corrupted? In any case, reinstalling settings will probably help. Maybe perform a backup before using the app loader in case there is more corruption going on.

Yes, sure seems that way. This was sitting and snacking. So not completely without movement but close. Kickstarter version Bangle.

Do you maybe have .../index.html instead of .../android.html in your URL config for the apploader?

I've had good success for smart phone displays with something called B-7000. Did not yet try it but it should get soft with some heat if you need to open the watch again. I suspect silicon sealant would be pretty final :)

Filing down my 4*4mm Buttons gets me very close, but there is about 0.2mm left before I can completely close the watch. I found https://www.ebay.de/itm/134591795596, those seem to match the original footprint nicely. Lets see how long those take to get here :)

I'm sorry to report that the button mentioned in https://forum.espruino.com/comments/16686848/ has just now disintegrated completely. I have some tiny buttons that might just fit after filing them down a little bit. Are there currently replacements available for the button daughterboard?

Removed double post.

I have tried comparing the new algorithm with my BT belt during a few hours of hiking. There are still differences, but I think that is at least partly to be expected. It is a massive improvement over the old one which would show everything from 40 to 90 on similar levels of exertion. The y-axis does not start at 0 to show the differences a bit more clearly. So it looks worse than it is :)

There is https://www.amazon.de/dp/B077RFZJ8Z/ref=cm_sw_r_apan_glt_i_6ZH025Y98QRKS0HJK3A7 linked on https://www.espruino.com/Bangle.js2#charging.
Probably there are other cables usable as well, but be sure to check the pin out (+/- on the correct pins) to not kill your Bangle.

I think battery falling like that can only be either a horribly wrong value for the battery calibration (and relatively low charge being shown as full) or GPS being active. There is just no hardware taking that much power besides full power backlight, but I suspect you would have seen that at some point. Do you have agpsdata configured for autoupdating? Maybe there is some bug not turning GPS off after the update.

There are two app loaders you can use (additional to several ways of running your own). One at https://banglejs.com/apps/. That one needs manual intervention by @Gordon to be updated and should contain more stable (older) apps. The other one is https://espruino.github.io/BangleApps/ and is automatically up to date with all accepted pull requests of the Github BangleApps development project. The pull request you mention (https://github.com/espruino/BangleApps/pull/2778 ) has been merged two days ago and is available since then on the development app loader.

I have used the OsmAnd Pebble Integration by just filtering normal notifications in GadgetBridge. Watch buzzes with a new message whenever Osmand would have done some voice output. That worked well enough for walking around in areas with street name signs and when I had at least an rough idea of my route it even worked fine for biking. Normal OsmAnd notifications on the Bangle are completely useless as they are updated much too often (a notification every few meters).

Yes, default mode of BTHRM replaces internal HRM sensor and the events are usable in all apps without modifications.