You are reading a single comment by @Gordon and its replies. Click here to read the full conversation.
  • Hi - there was a recent issue with the 'FIFO_FULL' message appearing which got fixed yesterday, so that'd probably your issue. It was harmless though - just warning that some 'raw' NMEA GPS data got lost (but the app was never looking for the raw NMEA data so it didn't matter).

    The actual GPS coordinates are parsed in an IRQ so are never lost regardless of whether there's a FIFO_FULL or not.

    is every call to Bangle.setGPSPower(1) a cold start or a warm start of the ublox chipset?

    It's a warm start, so should acquire a lot faster. Although the time taken depends on how long it's been since the last fix. If it's a day or two it'll be slower than if it was only an hour ago.

    Maybe you could try again with a totally standard BangleRun and just leave it a bit longer to get a fix?

About

Avatar for Gordon @Gordon started