Unostot

Most recent activity

• Can no longer connect to my bangle.js 2

  in Bangle.js • 1 year, 7 months

  

  Hello Gordon,

  thanks for the reply.
  No, no improvement yet...more the other direction. I will try again the squeezing a bit later. But right now it did not connect or show up anywhere. When I wrote the post above there were some chances to get at least half a connection every now and then. Right now it was completely dead.

  But what you say with the squeezing matches with my obersavations back then. If there is a chance I can squeeze bluetooth on, this would explain why it worked so erratic.

  Can you explain a bit more how/where I should sqeeze to get better chances?

  As for the other question: It was one of a "2-watches", blue Kickstarter Bangles which got sent later to Germany because of the customs problem, and has also all 4 pins exposed (ok, mine right now with a bit partly removed nail polished on the center two :o) ).
  So I would say a rather early bangle js 2.

  Greetings,
  Georg

• Can no longer connect to my bangle.js 2

  in Bangle.js • 1 year, 8 months

  

  Hello,

  I have now a similar problem...
  right now i'm on vacation, so a bit time here and thereto play around and rule stuff out, but cornerpoints are:

  • Without noticable reason no bluetooth connection possible
    

  • booting into dfu/no code mode most of the tries does not help
    dfu mode and updatefrom 2.14 to 2.15 finally worked using the web ide, but was not visible in NRF toolbox/NRF DFU thingy

  • sometimes a factory reset helped, and sometimes gadgetbridge was at some time able to get a more or less long connection (noticable because time got synced)

  • i got it so far working that I could use the apploader to upload my apps (LCARS, android/messages quitemode and some others)
    it worked for a bit but is broken right now, not visible in any case/mode at the moment

  • will try tomorrow again with different phone which I used for succesful firmware upgrade

  • i'm away from home,so tomorrow I will disable any devices we have with us and have bluetooth, but if I understand right the only critical would be devices which were at some time paired to thewatch using BT oder gadget bridge...no "just have bluetooth enabled" devices...

  right now my only explanation for this erratic behaviour is a hardware error, but I'm willing to try a more systematic approach if you guys have ideas others than go in to DFU/no software mode...

  the watch of my wife currently is still working

  another point:successrate was better after reboot of the phone used for flashing, but also no consistent results using reboots to get a connection *sigh *

  so long greetings,
  Uno/Georg