Fixing Netflix-only Bluetooth lip-sync delay on Google TV Streamer

Short version

On one Google TV Streamer, Bluetooth headphones were roughly 200–250 ms late in Netflix while YouTube remained in sync. The usual sound settings did not fix it.

The evidence pointed to Netflix using Android's tunneled playback path over Bluetooth. On this device, that path used hardware A/V sync, and the observed behavior was consistent with the headphones' presentation delay not being compensated correctly. Adding Netflix's own platform capability below forced non-tunneled playback over Bluetooth:

"tunnelModeWithBTSetting": "disable"

After restarting Netflix, the video decoder reported INPUT_TUNNEL_MODE OFF, Netflix moved off the DIRECT | HW_AV_SYNC audio route, and lip sync was correct.

This is an unsupported workaround, not an official Google or Netflix fix. Back up the existing setting before changing it.

Tested environment

Google TV Streamer (kirkwood)
Android TV 14 / API 34
Google TV build UTTK.260317.003
Netflix 13.1.2 build 26051
Srhythm NC25 Bluetooth headphones, offering AAC and SBC
Symptom was application-specific: YouTube was synchronized; Netflix was not

The device names, network addresses, Bluetooth addresses, and account details have been omitted.

What was happening

The two applications used different playback paths:

Application	Observed path	Result
YouTube	Ordinary PCM/deep-buffer A2DP path	Video compensated for Bluetooth delay
Netflix	`DIRECT	HW_AV_SYNC`, with tunneled secure video

Other useful observations:

The headphones exposed AAC and SBC, but no aptX Low Latency, aptX Adaptive, LDAC, or Opus.
Android reported that Bluetooth variable-latency mode was enabled at the framework level, but the audio HAL did not support it.
A2DP hardware offload was disabled.
Spatial audio, dialogue enhancement, and volume leveling were already off.
Changing surround output to “Never” did not change the bad Netflix route.
Switching AAC to SBC reduced the delay somewhat, but did not eliminate it by itself. The controlled AAC retest below showed that the codec change was not the actual fix.

Inspection of the installed Netflix build revealed an explicit platform capability named tunnelModeWithBTSetting and code paths logging:

Tunnel mode with BT is enabled due to platform config
Tunnel mode with BT is disabled due to platform config

Accepted values are enable, disable, and default.

Workaround

1. Enable ADB temporarily

Install Android SDK Platform Tools and jq on the computer. On the Google TV device, enable Developer options by opening Settings → System → About and selecting Android TV OS build seven times. Then open Settings → System → Developer options → Wireless debugging.

For the first connection, choose Pair device with pairing code on the TV and use the pairing address shown there:

adb pair GOOGLE_TV_IP:PAIRING_PORT

Enter the six-digit code from the TV when prompted. Then use the separate IP address and port shown on the main Wireless debugging screen:

adb connect GOOGLE_TV_IP:ADB_PORT
adb devices

Wireless-debugging ports can vary. Use the IP address and port shown by the TV.

2. Back up and update Netflix's platform capability

The commands below preserve every existing field rather than replacing the whole JSON object. They also stop if the existing value is not a valid JSON object:

set -e

ORIGINAL=$(adb shell settings get global nrdp_platform_capabilities | tr -d '\r')

if [ -z "$ORIGINAL" ] || [ "$ORIGINAL" = "null" ]; then
  ORIGINAL='{}'
fi

printf '%s\n' "$ORIGINAL" > nrdp_platform_capabilities.backup.json

UPDATED=$(printf '%s' "$ORIGINAL" \
  | jq -e -c '
      if type == "object" then
        . + {"tunnelModeWithBTSetting":"disable"}
      else
        error("existing capability value is not a JSON object")
      end
    ')

PAYLOAD=$(printf '%s' "$UPDATED" | base64 | tr -d '\n')

adb shell "settings put global nrdp_platform_capabilities \
  \"\$(echo '$PAYLOAD' | base64 -d)\""

Verify the result:

adb shell settings get global nrdp_platform_capabilities

The output should retain the original fields and include:

"tunnelModeWithBTSetting":"disable"

3. Restart Netflix without clearing its data

adb shell am force-stop com.netflix.ninja
adb shell monkey -p com.netflix.ninja \
  -c android.intent.category.LEANBACK_LAUNCHER 1 >/dev/null

This force-stops and relaunches Netflix. It does not clear the application data or sign the user out.

4. Verify

Play a dialogue-heavy Netflix scene. On the tested MediaTek-based Streamer, the following command confirmed the changed video path:

adb shell logcat -d -v time \
  | grep 'set INPUT_TUNNEL_MODE' \
  | tail -1

Expected result:

set INPUT_TUNNEL_MODE OFF

The exact log tag is platform-specific, so its absence on another device does not prove the workaround failed. The practical test is whether dialogue remains synchronized.

AAC versus SBC result

SBC was tested first and made the original tunneled-path delay somewhat smaller, but Netflix still looked out of sync.

After disabling tunnel mode fixed the problem, the headphones were deliberately switched back to AAC while keeping every other relevant setting unchanged. Netflix was restarted and the same kind of dialogue-heavy content was tested again. The device reported all of the following:

AAC at 44.1 kHz, 16-bit stereo
INPUT_TUNNEL_MODE OFF
an active Netflix PCM/A2DP audio track with flags 0x000, rather than the previous direct/HW-A/V-sync route

Lip sync remained correct. This isolates tunnelModeWithBTSetting=disable as the effective workaround on this setup; SBC was not required. AAC was therefore left enabled.

If the delay returns

On the tested device, the delay returned three days later. The TV had not rebooted, the system build was unchanged, and Netflix had not updated. However, this command showed that tunnelModeWithBTSetting had disappeared:

adb shell settings get global nrdp_platform_capabilities

The capability object had been rewritten to its original fields. This suggests that a later platform or server-configuration refresh can silently remove the unsupported override.

If the delay returns, inspect the value above first:

If tunnelModeWithBTSetting is missing, repeat steps 2 and 3. Reapplying the field and restarting Netflix restored correct sync immediately on the tested device.
If the field is still set to disable, do not assume the same cause. Capture the current playback route and investigate it as a separate regression.

Wireless-debugging ports can also change. If a previously working address no longer connects, this command can reveal the currently advertised connection endpoint:

adb mdns services

Look for the Google TV device's _adb-tls-connect._tcp entry, then connect to the IP address and port shown there.

Revert

To restore the original Netflix capability object:

ORIGINAL=$(tr -d '\r\n' < nrdp_platform_capabilities.backup.json)
PAYLOAD=$(printf '%s' "$ORIGINAL" | base64 | tr -d '\n')

adb shell "settings put global nrdp_platform_capabilities \
  \"\$(echo '$PAYLOAD' | base64 -d)\""

adb shell am force-stop com.netflix.ninja
adb shell monkey -p com.netflix.ninja \
  -c android.intent.category.LEANBACK_LAUNCHER 1 >/dev/null

Notes and caveats

A Netflix or Google TV update may overwrite or stop honoring this setting.
A later platform or server-side configuration refresh can remove or supersede the value. This occurred once on the tested device without a reboot or application update.
Do not copy another person's complete nrdp_platform_capabilities JSON; merge only the one field so device-specific capabilities remain intact.
Clearing Netflix data and factory-resetting the Streamer were not required.
Turn Wireless debugging off after testing.

elitan/google-tv-netflix-bluetooth-sync-fix.md

Select an option

No results found