Tom Fifield d201f6a1ed Guard bad time warning logs using GPS_DEBUG (#7897) ... In 2.7.7 / 2.7.8 we introduced some new checks for time accuracy. In combination, these result in a spamming of the logs when a bad time is found When the GPS is active, we're calling the GPS thread every 0.2secs. So this log could be printed 4,500 times in a no-lock scenario :) Reserve this experience for developers using GPS_DEBUG. Fixes https://github.com/meshtastic/firmware/issues/7896		2025-09-14 05:00:42 -05:00
..
cas.h	A second round of cleanup on GPS.h. (#5433)	2024-11-25 05:32:04 -06:00
GeoCoord.cpp	Clean up some inline functions (#5454)	2024-11-26 14:00:10 -06:00
GeoCoord.h	Clean up some inline functions (#5454)	2024-11-26 14:00:10 -06:00
GPS.cpp	Use char buffer for probeResponse (#7870)	2025-09-09 06:34:38 -05:00
GPS.h	Hold for 20s after GPS lock (#7801)	2025-09-02 06:06:06 -05:00
GPSUpdateScheduling.cpp	More reduction (#5256)	2024-11-04 19:15:59 -06:00
GPSUpdateScheduling.h	Revert "Sync Wio lr1110 refresh with master (#4288)"	2024-07-22 15:30:36 +02:00
NMEAWPL.cpp	Fixed NMEA sentence issue in CalTopo as well as bug with no printing all of the nodes (#5412)	2024-11-21 20:13:30 +08:00
NMEAWPL.h
RTC.cpp	Guard bad time warning logs using GPS_DEBUG (#7897)	2025-09-14 05:00:42 -05:00
RTC.h	Fix GPS that hard code 2080 as the start time. (#7803)	2025-09-02 06:41:26 -05:00
ubx.h	chore: update ubx.h (#6522)	2025-04-08 14:04:33 -05:00