fifo_full / memory_busy

Posted on
Page
of 3
First Prev
/ 3
  • Do you plan to add flow control to the play store version as well?

    Yes - I talked about this in another thread but Google changed the Play Store rules to we had to change the 'API version' when uploading updates, and that potentially causes other issues with Gadgetbridge so it all needs to be checked out thoroughly - otherwise I risk breaking everything :)

  • Running latest Gadgetbridge 0.80.0-banglejs from F-Droid and latest Firmware 2v21 on my Bangle2. Since some weeks(?) I see these two annoying messages "FIFO_FULL" and "MEMORY_BUSY". My collection of apps is unchanged since a long time - so could be related to some recent updates ... Any advice?

  • 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!
  • Just a note that I may have finally fixed the remaining MEMORY_BUSY error on cutting edge builds (the fix will be in 2v22). It was related to the Health event that occurs every 10 minutes - it had to check daylight saving time to see if it was midnight or not, and it seems that caused the issue

  • Post a reply
    • Bold
    • Italics
    • Link
    • Image
    • List
    • Quote
    • code
    • Preview
About

fifo_full / memory_busy

Posted by Avatar for leiropi @leiropi

Actions