B. Clay Miles

(posting this but see next post as I dug deeper) Nope, no change. running my script, unchanged from above except using 23 sets as recommended - and with debug turned...

After the results above, I ran gpsinit -f /etc/gpsinit_time.conf. I forgot to add the speed, and got the following output: ``` root@ B-NTPsec: /usr/local/src/mt3339-utils-1.2.1 # gpsinit -f /etc/gpsinit_time.conf /dev/gpsd0 Setting...

Dang. Battery pulled, waited a bit, battery restored, boot and get system sorted out with a reasonable time, gpsinit_reset, run update-epo script with 23 sets - same failure, same bad...

This issue is almost comical! Yeah, wouldn't surprise me if it's a faulty firmware update that leaves potentially corrupt data behind sometimes. It's interesting that your downloaded EPO doesn't work...

Just ran update, 22 sets, worked fine. Really makes me think maybe it's a problem with MTK's files...

In my case it's a ublox Neo M8T, on a HAT built by...some tiny drone company on ebay that I bought a couple from a few years ago, and which...