Infotainment, CarPlay & Android AutoDiscussionCommunity Starter

1970 Datsun 240Z — infotainment became glitchy after an OTA update

ColdStartFan202Community StarterOct 15, 20251970 Datsun 240ZWashington DC
1970 Datsun 240Z, about 192,500 miles. After a software update the screen occasionally reboots and one saved setting keeps resetting. Is there a normal post-update reset procedure owners should try before booking service?
permalink

7 replies

CityWeekend789Community StarterCommunity StarterOct 15, 2025permalink
Don't overfit one forum story to your car. If it still isn't clear on the 1970 Datsun 240Z, a specialist hour can be cheaper than another round of parts. I'd do that before spending real money. Verbal 'we'll take care of it' is not a plan. I'm in no rush to be a hero on it.
TruckDadCommunity StarterCommunity StarterOct 15, 2025permalink
Owner notes beat generic advice here. On the 1970 Datsun 240Z in Washington DC, I'd fix the thing you'll notice every day before chasing spec-sheet extras. That's where I'd start. On “infotainment became glitchy after an ota update,” that was the fork that mattered for me. This is from a 1970 Datsun 240Z in Washington DC with 192,500 miles. Keep sale price, fees, and rate as three different conversations. Climate here is different, so treat that as a local data point. I'd rather look cautious in this thread than stuck later.
RoadTripBuyer172Community StarterCommunity StarterOct 16, 2025permalink
Don't overfit one forum story to your car. If it still isn't clear on the 1970 Datsun 240Z, a specialist hour can be cheaper than another round of parts. I'd do that before spending real money. This is from a 1970 Datsun 240Z in Washington DC with 192,500 miles. Write the result down so the next test isn't a repeat of the last one. I'm keeping receipts and dates in one folder.
TruckDadCommunity StarterCommunity StarterOct 16, 2025permalink
Owner notes beat generic advice here. On the 1970 Datsun 240Z in Washington DC, I'd fix the thing you'll notice every day before chasing spec-sheet extras. Then you'll know the next fork. On “infotainment became glitchy after an ota update,” that was the fork that mattered for me. Keep sale price, fees, and rate as three different conversations. Climate here is different, so treat that as a local data point. Wrote this up on my lunch break.
CommuterDriver262Community StarterCommunity StarterOct 17, 2025permalink
Fair point. Counterpoint: Verify the cheap/easy branch on the 1970 Datsun 240Z before a big repair or a big spend. Then you'll know the next fork. That's the whole play. This is me being the wet blanket on purpose.
BoostShopper780Community StarterCommunity StarterOct 16, 2025permalink
I'd keep this practical. Verify the cheap/easy branch on the 1970 Datsun 240Z before a big repair or a big spend. I'd do that before spending real money. Keep sale price, fees, and rate as three different conversations. I've seen both outcomes, which is why I'd test instead of assume. Doing the boring step first on purpose.
TruckLearner956Community StarterCommunity StarterOct 16, 2025permalink
Write down what you already tried. A second data point from another 1970 Datsun 240Z owner helps more than a generic diagnosis. I'd do that before spending real money. That's the sequence I'd use. Not trying to scare you — just skip the expensive first guess. Might be overthinking it, but I'd rather overthink than overspend.
Sign in to reply

Similar discussions