Share your experience!
Hi all,
I’m running into a recurring HDMI/eARC issue that started after updating my Sony XR-55A80L to firmware version v6.8022. Hoping others can confirm or suggest a solution.
TV: Sony XR-55A80L (2023 OLED)
Amp: Sony TA-AN1000 (eARC capable)
Source devices: NVIDIA Shield Pro (fast boot), PS5
Connection: HDMI with eARC enabled
Bravia Sync: Enabled
Amp setting: Network Standby = ON, HDMI Standby Through = ON
TV Audio Output: Set to “Audio System”
eARC Mode: Auto
After the latest firmware update (v6.8022), I’ve been intermittently getting this message on boot:
“TV speakers active due to communication failure between the TV and audio system.”
The message appears at startup, particularly when using the Shield, which boots very quickly.
However, audio still routes to the amp correctly after a second or two.
The PS5 doesn’t trigger the issue, likely because it takes longer to boot and gives the amp time to complete the eARC handshake.
Double-checked Bravia Sync and eARC settings on both TV and amp
Ensured HDMI cables are high quality and fully eARC-capable
Amp and TV both have latest firmware
Network Standby and HDMI Standby Through are ON on the TA-AN1000
No HDMI splitters or ARC extenders in use
TV now starts up faster after the update — may be outpacing the amp’s readiness
It seems like the TV is trying to establish an eARC connection before the amp is fully ready, especially when the Shield boots quickly. This results in a temporary fallback to TV speakers before switching back to the amp. Since the PS5 takes longer to boot, it avoids the issue.
Is anyone else with an A80L or TA-AN1000 seeing the same issue after the v6.8022 update?
Could this be a firmware bug, or just a timing conflict due to faster TV startup?
Are there any recommended tweaks or CEC strategies that solved this for you?
Could this affect the TV or amp long-term, even if audio functions normally afterward?
Appreciate any advice or feedback!
Thanks in advance.
I'm having the exact same problem after updating to latest firmware on my A95K... I've got a Sonos Arc connected via the eARC (HDMI 3). Haven't had any problems with the setup until now. I get the message almost every time I turn on my TV now and sometimes the source doesn't change automatically anymore. I'm considering rolling back (if possible) to earlier firmware. Have you been in contact with Sony yet?
On a positive note, I do feel like the TV is turning on faster just as you describe so might be something related to that.
Hi,
Yes, I’ve contacted Sony and they provided me with a list of tests to go through to cover all possible scenarios. I recorded a video and sent it to them. After three weeks, they finally got back to me and confirmed that the issue has been escalated to their technical team, who are now working on a possible solution.
As you mentioned, the TV is indeed turning on much faster, and this is most likely what’s causing the issue.
That’s great to hear! Thanks for reply. I’ll wait and see if they come up with a fix then.
As soon as I hear back from them, I’ll post an update here to keep you informed. Hopefully, they manage to resolve the issue. I know it’s not exactly a fault, but it’s frustrating to see it happen every time I switch on the TV—especially considering the amount of money spent.
Nowadays, we have too many devices connected via CEC, and if something sends the signal too early or receives it too late, something is bound to fail in the process. As I mentioned in my first post, funnily enough, the PS5 works fine with every switch on—most likely because it has a slower boot time or simply syncs better with Sony's system. However, if I power on the TV directly instead of the Shield, I get the error again.
Just wanted to give an update on the Sony XR-55A80L issues some of us have been discussing. I received an email from Sony support today confirming that improvements will be implemented in the next software update.
Given that these types of issues often affect multiple models, it's highly likely this update will also bring fixes for other Sony TVs facing similar problems.
Good to know they're working on it! Fingers crossed it resolves things for us.
Thanks for the update as well. Will check it out once I arrive home from work.
Thanks again!