Vibration stops working

[espruino-discuss2]

Posted at 2024-09-26 by lauzon

On a Bangle.js2, firmware 2v23 and just confirmed again on 2v24, the vibration stopped working (e.g. no longer vibrating when swiping to pick a number, no longer vibrating on alarms that pop up), most of the time. 😢
Vibration will work maybe once per day or less. It was working correctly on 2v23 until it started not working, so it probably has nothing to do with the firmware.

Everything else is working. Didn't soak the watch, didn't hit it anywhere as far as I can tell.

Any ideas?

[espruino-discuss2]

Posted at 2024-09-27 by @gfwilliams

Can you try connecting with the Web IDE (https://www.espruino.com/ide/) and then pasting Bangle.buzz() into the left-hand side (then hit enter) and see what happens?

Also while you're there, paste in require("Storage").readJSON("setting.json") and copy/paste the information it outputs into this thread.

The various alarms/message alerts can be configured to have different patterns/strengths of buzzes for different things, and it's possible that I guess your vibration motor has got somehow a bit 'sticky' and if things are configured to only use half strength.

Or your watch has got 'quiet mode' enabled, which will would disable the vibration motor (if the app is installed it'll do it at some times of day and not others)

---

Posted at 2024-09-27 by lauzon

Bangle.buzz() does nothing unfortunately. I also tried Bangle.buzz(10000, 1), maybe buzzing for a longer time would, I don't know, unstick things, but no, nothing either.

I don't have installed any App with "quiet" in the App name.

Here's the result for require("Storage").readJSON("setting.json"):

={ ble: true, blerepl: true, log: 0, timeout: 10,
  vibrate: true,
  beep: "vib",
  timezone: -4, HID: false,
  clock: "antonclk.app.js",
  "12hour": false, brightness: 1,
  options: { wakeOnBTN1: true, wakeOnBTN2: true, wakeOnBTN3: true, wakeOnFaceUp: false,
    wakeOnTouch: false, wakeOnTwist: false, twistThreshold: 819.2, twistMaxY: -800, twistTimeout: 1000 },
  theme: { fg: 65535, bg: 0, fg2: 65535, bg2: 8,
    fgH: 65535, bgH: 31, dark: true },
  clockHasWidgets: true,
  launcher: "dtlaunch.app.js",
  rotate: 0,
  touch: { x1: -4, y1: 32, x2: 196, y2: 177 }
 }

---

Posted at 2024-09-30 by @gfwilliams

Sorry to hear that - do you think you could reboot by long-pressing the button until you get to the recovery menu, then choose Clean Boot and try pasting in the Bangle.buzz() command again?

That should avoid loading any JS code onto the watch which should rule out any software being at fault.

After that you can just press for ~2sec to reload back to the clock.

But if that fails to buzz, I'm afraid it sounds like a hardware fault.

---

Posted at 2024-10-01 by lauzon

Still nothing 😭. Is there a picture of the watch's internal somewhere that would show which device is the buzzer? (maybe some cleanup would do)

---

Posted at 2024-10-02 by @gfwilliams

Yes - see https://www.espruino.com/Bangle.js2+Technical#pcb - it's the big circle in the middle of the PCB.

Getting into the watch is tricky though: https://www.espruino.com/Bangle.js2+Disassembly

---

Posted at 2024-10-02 by lauzon

Hmm, indeed. Thanks.