2013 Nissan 370Z — infotainment became glitchy after an OTA update

Intermittent stuff lies if you only catch it once. Write temp, speed, and in-gear vs coast when the 2013 Nissan 370Z does it — then decide on parts. That's the branch I'd chase this week. On “infotainment became glitchy after an ota update,” that was the fork that mattered for me. Do that first. Not interested in a five-hour wait for a shrug.

I wouldn't throw parts yet. Loaded-suspension checks on the 2013 Nissan 370Z catch play that a wheels-hanging inspection misses. That's the branch I'd chase this week. This is from a 2013 Nissan 370Z in Denver with 104,500 miles. Run the total, not the monthly, before you commit. Checking again after work.

Update: the cheap test changed the symptom, so I'm not throwing parts yet. Parking it somewhere I can hear it better next time.

I went back under the 2013 Nissan 370Z and it only happens after a heat soak, not on a cold start. If it repeats twice more I'll book time.

Log the conditions before you spend. A pressure test beats staring at a dry driveway if the 2013 Nissan 370Z is losing coolant with no puddle. That's the branch I'd chase this week. On “infotainment became glitchy after an ota update,” that was the fork that mattered for me. This is from a 2013 Nissan 370Z in Denver with 104,500 miles. Do that first. If the story changes I'll post the new data.