Search results for:

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#rese­tting-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+Getti­ng+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/1668­6848/ 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#char­ging.
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/p­ull/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.

I think I found the issue:
The location manager was not cleaned up when the Bangle was disconnected by connection loss. This pull request should fix that.
https://codeberg.org/Freeyourgadget/Gadg­etbridge/pulls/3132

Either you managed to scratch the glass or the protector is still on. If I remember correctly it had no tab or something like that to pull it off. On my first Bangle I thought I had received a scratched one and only a few days later I discovered it to be a protector. It was a tiny bit "frosted". Without the protector you should have a mirror finish just like the display glass has.

Edit: @adjtm hehe, you ninjaed my post very closely :D

I have tested a bit again with current stable firmware and GB (2v17 and 0.74) and the changes for android from https://github.com/espruino/BangleApps/p­ull/2534 since without them I can not get GBGPS to activate on GadgetBridge:

• Connect watch to GB and start GPS Info to get GPS updates -> works fine
  
  • Battery level available in GB
    
  • Connected shown in GB
    
  • Sending notification works
    
  • characteristic write messages in logcat
    
• Put watch into metal box
  
  • Battery level vanished from GB
    
  • Few ms of disconnected (grey) state, then connected state shown again
    
  • After "reconnect" still no battery level
    
  • GB still trying to send GPS, but not characteristic write messages
    
  • Debug notification does not work, just added to queue like GPS messages
    
• Take watch out of box
  
  • nothing changes, stays fake connected without battery level
    
• Reload watch (2 sec button press)
  
  • nothing changes again
    
• Disconnect and reconnect watch with GB menu
  
  • Everything returns to normal
    
    

It seems there is a problem in the GadgetBridge GPS handling code, not the GPS code on the watch. It is in the metal box when the problem starts, so no influence on GB at that point in time. Without triggering GBGPS on the watch the "fake" reconnect does not happen and the actual reconnect after the box is openend restores full functionality.
Somehow some state in GB seems to be not cleared as it should be when the GPS service is active.

Slightly off-topic, so I will keep it short:

By making apps fast load that were never designed for it

Apps do not need to be designed for being loaded without a reset, they need to be able to clean up if another app is loaded without reset. Fastload Utils just enables loading every app after one that is able to clean up. There is no (intended) way to fastload with the current version if the currently running app can not clean up. There should not be any stuff accumulating except for bugs in apps regarding clean up. Real reset is still done for leaving nearly every app but clocks and launchers.

Edit: Nevertheless removing it as a possible source for errors is what I would do as well.

I've had similar problems (empty in a day) and have seen something in the trace logs. Do you have GPS via Gadgetbridge activated on your watch?
agpsdata turns on GPS for updates and I could not find it being turned off again in my log. I suspect this behaviour happens in combination with the workaround for Serial1-communication from the GadgetBridge GPS-handling code. So in the end the internal GPS gets switched on and only switched off if somehow a reload is triggered. This would explain why this happens only sometimes and not all the time. It would empty the Bangle if agpsdata pulls new data AND then no reload happens for long enough to eat a sizeable chunk of the battery.

Your problem with the buzzing code is a bit strange, but even if the CPU ran full tilt for the 6h it would consume under 30mAh or around 15% of the battery charge. Actual buzzing would probably need more power, but you said it wasn't actually buzzing a lot.

https://espruino.github.io/BangleApps/?i­d=gpstrek tries to do this using the barometer, but i needs some work on filtering. Currently the values for up and down are to high.

Yes, it only calibrates after 3 hours if it has seen a charging start and a charging stop event. Deliberately so to prevent setting the calibration too often. Maybe just starting a 3 hour timeout on charging start (event or even boot) would be better?
As for it being unlikely, I have seen it exactly once where I am sure that this has happened. The other times have been values much closer to correct ones. Those could have been caused by charging in cold environment or differing charger voltages or something like that.