Frequent "locationd temporary error" and "Angle offset too high" on Comma 4

[Zaf9670]

Describe the bug

Opening GitHub issue per yassine's request from the Discord driving-feedback conversation. Unsure if this is car specific of my Comma 4.

Comma 4 + 2025 Honda CR-V Hybrid Sport Turing

This happens primarily after starting the car and the comma 4 (c4) comes up from a cold boot. If the c4 is on standby power it seems to have rarely if ever. If I reboot the c4, restart my car, or perform calibrations that seems to resolve some/most of the issues. As a side-note I also had this issue on the Honda/Acura sunnypilot fork of MVL (sp-honda-dev-202512).

Sometimes the angle offset or locationd errors will resolve after an unknown amount of time driving. I confirmed the mount is not loose in the discord thread with video.

Here are some of the drives I have uploaded with the issue.

https://connect.comma.ai/03384dacc4f21604/00000005--e9b359a2f1/19/138
https://connect.comma.ai/03384dacc4f21604/00000018--8b4c76e8b6 - locationd around 16:36 eastern time (roughly section 8)
https://connect.comma.ai/03384dacc4f21604/0000001a--fb14774344 - locationd prior to reboot resoling issues

Provide a route where the issue occurs

https://connect.comma.ai/03384dacc4f21604/00000005--e9b359a2f1/19/138

openpilot version

0.10.3

Additional info

No response

[Zaf9670]

Thread ID for reference 1453948512227164261

[Zaf9670]

Here are two more where even after a restart I could not get the locationd error to go away. Third is the remainder of the drive where I tried a few separate occasions but still had locationd errors.

I did not try a calibration. I just restarted the comma 4 after I got to my destination and it worked from then on.

03384dacc4f21604/00000026--18c542606b/0 - initial start
03384dacc4f21604/00000027--e282e63fbb/0 - after disable/enable openpilot, locationd persisted

03384dacc4f21604/00000028--50cbe84148/0 - remainder of drive where locationd persisted