fifo_full / memory_busy

Well, the two errors are a bit different:

• FIFO_FULL means Gadgetbridge was trying to send a bunch of data to the watch and it was too busy to receive it - that shouldn't normally happen as Gadgetbridge should implement flow control, so I'm not sure what's up there. It'd be interesting if you get the error with the play store version?
  
• MEMORY_BUSY happens when something inside Bangle.js is trying to allocate variables while the Bangle is doing garbage collection. I have seen this when using the Pebble++ clock but I'm afraid I haven't been able to track it down (it'll be a firmware issue). If you or anyone has found a way to reproduce this I'd be extremely interested!