Any issues with instrument cluster programming?

Has anyone here taken it to the dealer for this?

 

Good idea to get the process rolling. Going to roll into scheduled service.

 

My 24 Pro will not memorize TPMS either!

 

Same here, tried to put tire pressure in place of pitch/roll and it stuck for about a week before it magically turned into trip a/b

 

Seems like all but 1 of us is having this problem. Hope they come up with a fix mind you now that I have done it 100 times it only takes about 5 seconds to fix it and go back to my main screen

 

I wish there was more than 3 pages of gauges . There's enough to have like 6!

 

You’ll need more than 6. If you have a TRD or TH there are at least 1350 permutations for the 12.3” display.

(15 on the LH side) x (6 in the center) x (15 on the RH side) = 1350.

Or is my math off?

 

You guys have jinxed me! Now I'm losing it (changes to Trip B). However, there was a change that occurred. I got the privacy policy change notice and declined to have my location sent. So all of the connected services were disabled. I've turned them back on to see if that helps. Will let you know.

 

The TPMS lack of permanence also affects some (maybe all?) other Toyota models with the digital-dash, in my personal experience. Some sort of software bug.

 

Wouldn't need as many pages if we could put any gauge in the center. All gauges should be able to go in any of the 3 positions. There's also small stuff that could be permanent elsewhere in the empty real estate.

I find what works best is round tach in the center, this way, oil pressure and temp is on the lower left, and alternator and fuel gauge on the lower right. So no need to add those in another precious spot.

 

Yes since it's all digital there should be more options. Even sweet retro bar graph one would be cool!

 

With all of the connected services enabled I no longer lose the TPMS display.
I'm going comet chasing for the next few days but after that I'll try disabling individual services to see if I can determine if there is a specific one that is causing the problem.

 

This is interesting. I can replicate this as well.

 

It would be super interesting, and not surprising, if TPMS data was making a round trip through Toyota servers between the ECU and the dash.

 

I think it's more that your custom settings are tied in with your account profile and getting reset if your profile is not available. Should be able to save settings locally though. Still have to consider this a bug in my opinion. Odd that I've never noticed it happening when I'm somewhere with no cellular service. Will have to play with it some more later. Going comet chasing again. Came up with clouds last week.

PS: it's not just the TPMS display that changed for me when I disabled communication, all 3 displays reverted to their default settings (I have customized all of them).

 

The only service I didn't have selected was the reporting to insurance companies. When enabled, TPMS is now sticky.

 

this is what I think as well, mine worked fine until i cancelled all the Toyota app stuff

 

I also have all of the "Connected Services" nonsense disabled and experience the same TPMS widget issue. Would a software update fixing the problem be installable at home over the air, or is that a take-it-to-the-dealer-and-have-the-system-flashed thing? (I haven't owned a car with updatable software before.)

 

Where/how are connected services enabled/disabled? App or multimedia screen?

 

It's probably not, since it's a function that needs to work out in the wilderness where there's no cellular signal. That and it does function with the connected services turned off. The display just doesn't stick.

I'm sure it's just a glitch that wasn't particularly well tested because it really sounds like an edge case. I'm a professional software QA engineer and have been for quite a few years. It probably wouldn't have occurred to me to test the persistence of the display setting in connection with the connected services setting. What the heck would they have to do with one another?

Regardless, the way software glitches get fixed is by users that experience them reporting them and providing whatever information they can surrounding the circumstances of when the glitch happened. The developers need data to be able to reproduce the problem so they can identify the root cause, fix it, and QA can make sure it's really corrected. Keep telling them everything you know when you experience it.