BLE_periph does not wake up

[enaon]

Hi , I had a problem with the magic3 since I moved to 2.27, I solved it by switching to s140-6.1.1 , but I can see the same problem on the bangle.js 2, so I thought I should report.

the problem is that after some time of inactivity, when connected to the ide, the BLE_periph drops to 25μΑ (according to E.getPowerUsage() ), and it nener wakes (well sometimes it wakes, but some times it does not) , I have to disconnected and connect again, otherwise the connection is very slow. This copy paste from the ide may make it easier to see. On 6.1.1, this problem is gone.

>E.getPowerUsage()
={
  device: { CPU: 291, PWM: 200, LED1: 8000, LCD_backlight: 14000,
    LCD_touch: 1600, BLE_periph: 665 },
  total: 24756 }
>E.getPowerUsage()
={
  device: { CPU: 3982, BLE_periph: 665 },
  total: 4647 }
>E.getPowerUsage()
={
  device: { CPU: 2105, BLE_periph: 665 },
  total: 2770 }
>E.getPowerUsage()
={
  device: { CPU: 181, BLE_periph: 665 },
  total: 846 }
>
>E.getPowerUsage()
={
  device: { CPU: 150, BLE_periph: 665 },
  total: 815 }
>E.getPowerUsage()
={
  device: { CPU: 781, PWM: 200, LED1: 8000, LCD_backlight: 14000,
    LCD_touch: 1600, BLE_periph: 665 },
  total: 25246 }
>E.getPowerUsage()
={
  device: { CPU: 809, PWM: 200, LED1: 8000, LCD_backlight: 14000,
    LCD_touch: 1600, BLE_periph: 665 },
  total: 25274 }
>E.getPowerUsage()
={
  device: { CPU: 806, PWM: 200, LED1: 8000, LCD_backlight: 14000,
    LCD_touch: 1600, BLE_periph: 665 },
  total: 25271 }
>E.getPowerUsage()
={
  device: { CPU: 1291, PWM: 200, LED1: 8000, LCD_backlight: 14000,
    LCD_touch: 1600, BLE_periph: 665 },
  total: 25756 }
>E.getPowerUsage()
={
  device: { CPU: 774, PWM: 200, LED1: 8000, LCD_backlight: 14000,
    LCD_touch: 1600, BLE_periph: 665 },
  total: 25239 }
>E.getPowerUsage()
={
  device: { CPU: 1141, PWM: 200, LED1: 8000, LCD_backlight: 14000,
    LCD_touch: 1600, BLE_periph: 665 },
  total: 25606 }
>E.getPowerUsage()
={
  device: { CPU: 3970, PWM: 200, LED1: 8000, LCD_backlight: 14000,
    LCD_touch: 1600, BLE_periph: 665 },
  total: 28435 }
>E.getPowerUsage()
={
  device: { CPU: 1319, PWM: 200, LED1: 8000, LCD_backlight: 14000,
    LCD_touch: 1600, BLE_periph: 665 },
  total: 25784 }
>E.getPowerUsage()
={
  device: { CPU: 779, PWM: 200, LED1: 8000, LCD_backlight: 14000,
    LCD_touch: 1600, BLE_periph: 665 },
  total: 25244 }
>E.getPowerUsage()
={
  device: { CPU: 801, PWM: 200, LED1: 8000, LCD_backlight: 14000,
    LCD_touch: 1600, BLE_periph: 665 },
  total: 25266 }
>E.getPowerUsage()
={
  device: { CPU: 1017, PWM: 200, LED1: 8000, LCD_backlight: 14000,
    LCD_touch: 1600, BLE_periph: 665 },
  total: 25482 }
>E.getPowerUsage()
={
  device: { CPU: 3982, BLE_periph: 665 },
  total: 4647 }
>E.getPowerUsage()
={
  device: { CPU: 3982, BLE_periph: 665 },
  total: 4647 }
>E.getPowerUsage()
={
  device: { CPU: 378, BLE_periph: 665 },
  total: 1043 }
>E.getPowerUsage()
={
  device: { CPU: 378, BLE_periph: 665 },
  total: 1043 }
>E.getPowerUsage()
={
  device: { CPU: 378, BLE_periph: 665 },
  total: 1043 }
>E.getPowerUsage()
={
  device: { CPU: 378, BLE_periph: 665 },
  total: 1043 }
>E.getPowerUsage()
={
  device: { CPU: 288, BLE_periph: 665 },
  total: 953 }
>E.getPowerUsage()
={
  device: { CPU: 288, BLE_periph: 665 },
  total: 953 }
>E.getPowerUsage()
={
  device: { CPU: 288, BLE_periph: 665 },
  total: 953 }
>E.getPowerUsage()
={
  device: { CPU: 288, BLE_periph: 665 },
  total: 953 }
>E.getPowerUsage()
={
  device: { CPU: 285, BLE_periph: 665 },
  total: 950 }
>E.getPowerUsage()
={
  device: { CPU: 285, BLE_periph: 665 },
  total: 950 }
>
{"t":"act","stp":0,"hrm":0,"mov":123,"act":"UNKNOWN"}
{"t":"status","bat":41,"chg":0}
{"t":"act","stp":0,"hrm":0,"mov":90,"act":"NOT_WORN"}
{"t":"status","bat":39,"chg":0}
{"t":"act","stp":0,"hrm":0,"mov":73,"act":"NOT_WORN"}
{"t":"status","bat":40,"chg":0}
{"t":"act","stp":0,"hrm":0,"mov":88,"act":"NOT_WORN"}
E.getPowerUsage()
={
  device: { CPU: 34, BLE_periph: 25 },
  total: 59 }
>E.getPowerUsage()
={
  device: { CPU: 67, BLE_periph: 25 },
  total: 92 }
>E.getPowerUsage()
={
  device: { CPU: 67, BLE_periph: 25 },
  total: 92 }
>E.getPowerUsage()
{"t":"status","bat":43,"chg":0}
={
  device: { CPU: 67, BLE_periph: 25 },
  total: 92 }
>Date()
=Date: Mon Jul 21 2025 22:04:33 GMT+0300
>E.getPowerUsage()
={
  device: { CPU: 67, BLE_periph: 25 },
  total: 92 }
>
>Date()
=Date: Mon Jul 21 2025 22:04:47 GMT+0300
>E.getPowerUsage()
={
  device: { CPU: 67, BLE_periph: 25 },
  total: 92 }
>E.getPowerUsage()
={
  device: { CPU: 1395, BLE_periph: 25 },
  total: 1420 }
>E.getPowerUsage()
={
  device: { CPU: 1395, BLE_periph: 25 },
  total: 1420 }
>E.getPowerUsage()
={
  device: { CPU: 1395, BLE_periph: 25 },
  total: 1420 }
>print("please wake up")
please wake up
=undefined
>E.getPowerUsage()
={
  device: { CPU: 35, BLE_periph: 25 },
  total: 60 }
>
{"t":"act","stp":0,"hrm":0,"mov":85,"act":"NOT_WORN"}
{"t":"status","bat":39,"chg":0}

[gfwilliams]

E.getPowerUsage() is only really a guess - this is how it works out values: https://github.com/espruino/Espruino/blob/master/libs/bluetooth/jswrap_bluetooth.c#L4957-L4973

So what you really mean is that the Connection Interval stays slow, when it should go into High Speed mode?

What if you do NRF.setConnectionInterval(7.5) - does that help?

Honestly, if that fails, it's probably the computer that is connecting to the device. I've seen this once or twice from my PC, and if I unplug the PC's Bluetooth dongle and re-plug it (or just restart the PC) it all works again - so it's a driver issue on the PC.

[enaon]

So what you really mean is that the Connection Interval stays slow, when it should go into High Speed mode?

Yes, I think this is it. I thought about the computer too, but it only happens on the magic, not the dsd6, (2.27 too, but nrf52832) or the nano (2.25 and nrf52840, but I do not know the softdevice version). Plus, it is solved on the magic now that I upgraded to 6.1.1.

If you feel this is a isolated case, then all is good, it is solved for me in any case now with 6.1.1 on th magic, but it was so frustrating that I had to look at what is happening. It was quite random too, some times it woke, some not, I never had this issues before, same pc as allways, internal intel bt/wifi combo card. But I do have a different BT keyboard/mouse, maybe this makes the problem appear on the magic/bangle (with softdevice 6.0.0 ), but it does not affect dsd6/nano for some reason.

What if you do NRF.setConnectionInterval(7.5) - does that help?

i will test that, out of curiosity :)

this is what I get on the magic with softdevice 6.1.1 now, consistently, it works as always I guess.

>E.getPowerUsage()
={
  device: { CPU: 53, BLE_periph: 25 },
  total: 78 }
>E.getPowerUsage()
={
  device: { CPU: 53, BLE_periph: 665 },
  total: 718 }
>E.getPowerUsage()
={
  device: { CPU: 66, BLE_periph: 665 },

[enaon]

What if you do NRF.setConnectionInterval(7.5) - does that help?

I just tested that on the bangle, it gave an error and the ide was still in jack daniels tenessy quiskey mode, very slow, so maybe it is the pc for some reason?

>E.getPowerUsage()
={
  device: { CPU: 44, BLE_periph: 25 },
  total: 69 }
>NRF.setConnectionInterval(7.5)
Uncaught Error: ERR 0x11 (BUSY) (:3758)
    at REPL (:1:30)

[gfwilliams]

Ok, interesting! So yes, I think the Bangle is busy trying to negotiate the faster MTU but your PC isn't responding. I bet if you connect with another PC to the same Bangle, you'll find it works just fine?