True Tone Problem Since Update to 10.14.6

Same Issue here mbp13 2018. Updated and then got a true tone welcome message. Apple support told me to carry it in for service. It seems they aren't as aware of it being an issue.

I still have this issue across all my laptops. It's been introduced in 10.14.6 and never gone since then. Extremely annoying.

Could you please check that?

An the Screen flicker.

No, we can't as we are not Apple employees and have no contact with any of Apple's software engineers.

If you wish to make a suggestion to Apple, Send Feedback.

Same problem here, MBP 15 2018.

Regarding the support: they are always suggesting to reset something and usually that doesn't help. Once they gave me a list of things to try, like 5-7 items, I was spending my weekend time on slowly advancing through the list, after every item finished I was supposed to check did it help or not and that checking involved waiting for several hours. When I was at the middle of the list they released a new update which immediately fixed the issue. I wasted like 4-6 hours on that list in total.

Hey guys,

same for me here, MacBook Pro 15" 2019 with i9 and AMD 560X.

Especially arise when I am home on a bright day, it seems that True Tone does not know if he has to be on the cold (blue) or warmer side.

Resetting SMC and VRAM did not change a thing.

I think I identified a case when it happens always, or at least more : when the brightness of the screen is around the maximum and when there is a lot of luminosity around.

Did some of you observed the same ?

I have to say that the issue is most certainly happening more when brightness is high and the ambient light is less warm.

Today, in a different office, didn’t experience it at all! Tomorrow I will check again in the location where it originally happened.

I took it and they did the basic troubleshooting. Basically everything mentioned here. It didn't solve the issue. I needed my macbook so i didnt want to leave it there for them to carry further diagnostics especially when its almost certain a software issue with this update.

I'm having the same issue too. After the 10.14.6 update my late 2018 MacBook Pro started changing True Tone temperature from cool to warm and back abruptly.

The issue is intermittent but frequent. It is most visible when sitting against cool background (like a blue wall) and very annoying.

I tried rebooting the machine and resetting NVRAM / PRAM but that had no effect on the issue at all.

Exactly the same problem, but I have noticed that it happens especially in a place with a combination of cold and warm colors, for example: Macbook on a warm table, with a white wall behind. And at the beginning of the day, in the morning.

Maybe the new macOS Catalina will solve the problem??

Same problem.

I'm have been working with Apple support for this problem, even send information from my notebook to them, send videos showing the problem.

But at the end, they said this is related with software and closed the issue.

I'm currently waiting for Catalina, maybe that will fix the problem.

I agree that this is releated with software, but they are suggesting that this is releated with 3rd party software that I'm using. They didn't accept that this is releated with operating system. At least not to me.

My friend is using Catalina since early betas and don't have the issue so I have hope that update will fix the issue.

They are probably working hard to fix bugs in Catalina so they don't care about us much now.

The problem is that Upgrading to Catalina will cause a lot of problems to my work because most if the apps I use will not be compatible with Catalina.

they have to fix what they did in Mojave first. I’m so frustrated of how apple deal with this issue. I called many people from apple support and all they do is wasting my time and get me more frustrated. For this issue and more!

That's why I haven't bothered calling Apple. I don't want to reset no NVRAM/PRAM, no fresh installs of macOS either, not letting them waste my time with irrelevant troubleshooting walkthroughs. This clearly started happening right after the update to 10.14.6 and can't be coincidence that ambient light sensors decided to go bad at the same time for all of us.