Who Me Too'd this topic

profile.country.GB.title
micallefgilbert
Member

Sony XR-55A80L + TA-AN1000: “TV speakers active due to communication failure” after (v6.8022)

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.


📺 My setup:

  • 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


⚠️ The issue:

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.


🔍 What I’ve tried:

  • 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


🧠 My theory:

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.


Questions for the community:

  • 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.

Who Me Too'd this topic