Search results for:

https://www.espruino.com/Bangle.js2+Disa­ssembly

I have a 3D-printer, so it was quite easy to control the temperature for softening the glue.

I'm officially putting this poor watch to rest. I must have broken something with all the testing and fiddling and no matter how I prod and squeeze I can't get Bluetooth connected anymore.

It was worth a shot though...

That last suggestion sounds like a great idea. I'll give that a go tonight.

Quick update...

This weekend I opened up the watch and tried fixing things. Not much luck though.

It seems like the sprung terminal has been making a dimple in the pad connected to the case and doesn't reach it anymore without some pressure on the top of the PCB. I tested various means of making sure it reaches (like putting a thin shim underneath the pad), and I can get it to function for a while but eventually connection is lost again and only pinching the watch makes it connect.

Could also be that the connector is loose on the PCB, but I saw no signs of that.

Apart from the above I also made sure everything was clean.

It's not looking good so far.

I do not have a hotplate (although it's on the shopping/diy list), but maybe this is a great excuse to finally get one (I could get an MHP30 for about the same price I would pay for a new Bangle including shipping and fees). But, since I just tested pinching the top right corner and the watch immediately connected to my phone it sounds like I won't need a hotplate.

I'm gonna open it up and see what I can do...

Seems like my Bangle.js 2 is giving up... It's an original Kickstarter watch and yesterday it suddenly wouldn't connect to my phone anymore.

Turns out that bluetooth is being very flaky... It will intermittently work for a short period but then it'll stop working again and no matter what I do I cannot get it connected again. Even tested on different devices.

Factory resetting the watch did not help, and even in DFU mode it'll refuse to connect or even show up most of the time. Even managed to semi-brick it even attempting to install the stable v21 release, since something went wrong during flashing and the watch got stuck looping with a bank0 error. Could get into DFU but nothing else. Eventually managed to get it flashed properly again, but no dice on Bluetooth.

Everything points to the hardware dying, but just figured I'd hop on here and see if there's anything else I can look at. Opening it up is well within my capabilities if that could help...

https://forum.espruino.com/conversations­/391261/

1. Make sure the watch isn't paired in the phone's Bluetooth settings.
   
2. Make sure the watch isn't connected to any other device.
   
3. Enable Passkey in Settings -> Bluetooth on the watch.
   
4. Connect the watch through Gadgetbridge and choose not to pair.
   
   

That's what seems to have worked on the other thread you replied to (for a GrapheneOS user).

Don't pair directly in the device's Bluetooth settings. If you have already, unpair it.

Use the "Connect" button in the App loader, or "Connect new device" in Gadgetbridge (and it might even be beneficial to choose the option not to pair there).

That's something to start with...

Current firmware updater shows DFU 2v20 as expected.

I'm seeing the same thing.

Updated the DFU first (through the app loader), and it ended up as unknown, CRC 2122305557.

After that I tried updating the firmware through the app loader, but that failed halfway and both firmware and DFU versions read unknown, even after a restart of the watch.

Updating manually worked fine though and I'm now on 2v20.5, but the DFU version is still unknown.

Trying to update the DFU again does nothing. The fwupdater starts on the watch but immediately exits back to the watch without doing anything.

Isn't SMA-Q3 the hardware that the Bangle.js 2 is based on? Where did you buy this, and was it advertised as a Bangle.js 2?

A couple of suggestions that might be solutions to your issues:

1. Check the in-watch settings for the Messages app and make sure "Repeat" is off.
   
2. A longer press (couple of seconds) will always bring you back to the watch face.
   
3. Same as 1. but change the vibration pattern to something that's longer or repeats in a pattern that's easier to detect.
   

I think there are a couple of apps available to manage quiet mode already. Check the App Manager.

@Alberich123
https://shop.espruino.com/accessories/ba­nglejs-parts/banglejs2-lcd

I captured a quick GB debug log and it shows this when receiving an SMS on the phone:

SENDING GB({t:"notify",id:1691570958,title:"",su­bject:"",body:"Testing",sender:"Me",tel:­"redacted"})

Dismissing the notification does not generate a "notify-" action, but I see these for other notifications I dismiss.

I can also add that I see the same behaviour as described by the OP when it comes to SMS: interacting with the messages UI on the watch doesn't do anything for the notification on the phone. Other apps can have the notification both dismissed and the app being opened depending on the watch interaction.

The messaging app I'm using is the AOSP Messaging app that comes with my installed Android ROM.

When I try using a different app for SMS it gets a little more interesting. I installed this one:
https://play.google.com/store/apps/detai­ls?id=com.simplemobiletools.smsmessenger­

The following then shows up in the logs:

SENDING GB({t:"notify",id:1691570974,title:"",su­bject:"",body:"Testing 6",sender:"Me",tel:"redacted"})

SENDING GB({t:"notify",id:1691570975,src:"SMS Messenger",title:"Me",subject:"",body:"T­esting 6",sender:""})

SENDING GB({t:"notify-",id:1691570975})

When dismissing this notification I'm moved to the messages list on the watch, and the first of the above received notifications is still there. With this app it is possible to dismiss the notification using the watch, but not to open the app.

SENDING GB({t:"notify",id:1691570980,title:"",su­bject:"",body:"Testing 9",sender:"Me",tel:"redacted"})

SENDING GB({t:"notify",id:1691570981,src:"SMS Messenger",title:"Me",subject:"",body:"T­esting 9",sender:""})

{"t":"notify","n":"OPEN","id":1691570981­}

{"t":"notify","n":"OPEN","id":1691570980­}

SENDING GB({t:"notify-",id:1691570981})

SENDING GB({t:"notify",id:1691570982,title:"",su­bject:"",body:"Testing 10",sender:"Me",tel:"redacted"})

SENDING GB({t:"notify",id:1691570983,src:"SMS Messenger",title:"Me",subject:"",body:"T­esting 10",sender:""})

{"t":"notify","n":"DISMISS","id":1691570­983}

SENDING GB({t:"notify-",id:1691570983})

Of course, when dismissing, one of the messages still remain in the messages list and needs to be removed manually.

All of this is on a custom Android 11 ROM. Firmware version of the watch and versions of the involved apps on the watch does not seem to matter since I've seen this behavior for some time.

Bangle firmware - 2v18.126
Android integration - v0.31
Messages - v0.60
Messages UI - v0.73
Gadgetbridge - 0.75.0b-banglejs (229)

@Gordon Regarding SMS, I've actually observed a different behaviour for those notifications compared to others (but haven't had an opportunity to dig any further).

Whenever I get an SMS and then clear the notification on my phone, the message persists on the Bangle and has to be deleted manually. This only happens with SMS.

Could of course be a particular thing with my setup, and I've been suspecting as much since I haven't seen anyone mentioning anything similar. But, since we're talking about SMS quirks here I figured I'd mention it.

I'll try to grab a log for this later today.

Before testing the new navigation mentioned in this thread I've had notifications off for my map app (Osmand+), since the constant updating of the navigation notification caused a constant number of notification events on the bangle.js. Must have been about a year since I tested that last though...

Looks like the button is stuck or that the device is otherwise constantly reporting the button being pressed (short, etc).

About the original issue (a clarification). Is this about SMS? I'm asking, because I've been seeing an issue with SMS notifications that might be related.

First, with all other notifications I'm not seeing any issues. Pressing the checkmark marks the message as read and keeps it in the messages app, while pressing the X dismisses it and removes it from the app (and sometimes also from the phone, depending on the app). But, with regular text messages (SMS) the message is never removed from the app on the watch. Not even when dismissing the notification from the phone. A manual delete is required...

I tested Message List just now and noticed that it has a bug with watch faces that doesn't use fast load: the app will open when a notification is received, but there will be no message. This was fixed in Message UI last week (not sure if it was 0.62 or 0.63 that fixed it).

Yes. The device you need to connect to though, in the nrf app, is dfu targ which is only available while you're on that screen.

An occasional splash from using the sink faucet was enough to make the device unresponsive and cause it to constantly reboot. This is surprising to me because IP67 rated devices are supposed to be protected from not just occasional splashes, but also water immersion of up to 1 meter for 30 minutes.

FYI: If it was just a splash it shouldn't be any worries, but if the watch ended up directly in the water stream underneath the faucet it could have been exposed to water pressure that would greatly exceed the pressure it would experience when just immersed to 1 meter.

Yeah... The main problem is that people do not understand what the IP-ratings for dust- and waterproofness actually mean. They see "IP67, waterproof to 1 meter for 30 minutes" and think: "Great, I can swim with that as long as I don't dive". When in reality you shouldn't even let a watch with that rating go under the tap while washing your hands (unless you have a really soft flowing tap)...

It is white down the hole when I check, so I guess my was one of those. How do we proceed?

White means that the membrane is in place and everything is as it should (apart from the dead watch, of course).