Which message are you getting? Fifo full or memory busy?
If you try the cutting edge builds, some changes went in since 2v14 to improve the memory_busy situation.
In terms of fifo_full it could likely be because I'm not sure if Gadgetbridge implements any flow control right now (I have it on a branch but the changes messed deeply with code that is common to other watches so it's not merged yet). If you just turn off the 'increased MTU' in Gadgetbridge settings it'll probably fix it though
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Which message are you getting? Fifo full or memory busy?
If you try the cutting edge builds, some changes went in since 2v14 to improve the memory_busy situation.
In terms of fifo_full it could likely be because I'm not sure if Gadgetbridge implements any flow control right now (I have it on a branch but the changes messed deeply with code that is common to other watches so it's not merged yet). If you just turn off the 'increased MTU' in Gadgetbridge settings it'll probably fix it though