Occasional scrambling of data on Bluetooth UART after automatic reconnects?

I have been calling E.getErrorFlags() regularly to see if an error gets set at the time when the issue occurs. This was not the case. Is it correct that in this way I can exclude that I get issues due to too much data?

Yes, I think that's fine then.

While the timeout issue is present, I have made an interesting reproducible observation:

Thanks, that is interesting - so as you say it looks a bit like Gadgetbridge isn't able to send any information to the Bangle. In your Gadgetbridge log, do you see any messages about XON or XOFF?

It feels like there are two possibilities:

• When connecting, the 'write' characteristic can't be found, and so Gadgetbridge can't write at all
  
• Somehow the flow control system has got stuck and it believes the Bangle doesn't have any space for more data (so it's queuing up all the writes).
  
  

You mentioned this happened after an automatic reconnect. Do you think it's safe to say that after that reconnect it doesn't work at all - or that it was working and then it broke.