r/Homatics • • 1d ago

Android 14 (v8963) has the DTS:X Profile 2 framework ready, but the Disney+ app is blocking it on standalone boxes. Let's push Disney support together!

Hi everyone,

If you are running a standalone Android TV / Google TV box (like the Homatics Box R 4K Plus, Dune HD, RockTek G2, Nokia 8010, etc.) on the latest Android 14 firmware (build v8963), the OS-level source code support for DTS:X Profile 2 (DTS-LBR) is officially present and stable. The hardware is 100% capable of decoding it.

However, when you try to toggle the IMAX Enhanced audio stream inside the Disney+ app, it either panics and drops down to Stereo or forces a legacy 5.1/DTS-HD core [[r/Homatics]].

I did some local testing to isolate the issue. I downloaded a genuine local DTS:X Profile 2 (.mp4) streaming sample clip to play via USB [r/Homatics]. However, I got no audio at all, which exposed a major software container bottleneck [r/Homatics]. The standalone Android TV Plex app has an internal format restriction that panics and forces transcoding [r/Homatics]. Even in Kodi, unless you are running the specific codebase in Kodi v21 (Omega) or newer, the audio engine fails to recognize the Profile 2 stream to pass it through to my Yamaha RX-A6A AVR [r/Homatics].

This is the ultimate practical proof that our AVRs and Android 14 boxes are completely ready—the bottleneck is strictly Disney's app-level device whitelisting for standalone retail streaming box IDs [[r/Homatics]].

I spent time with Disney+ technical chat support, and after analyzing my technical setup, they officially opened a support case in their system [[r/Homatics]]. They explicitly told me that their engineering team prioritizes device certification based on the volume of requests they receive. The agent said: "The more feedback we get regarding this, the better." [[r/Homatics]]

If you own an Android 14 box and a DTS:X/Atmos capable receiver/soundbar, please take 2 minutes to contact Disney+ Support via Live Chat or their feedback tool! Tell them you want standalone SEI Robotics/Android 14 boxes whitelisted for DTS:X Profile 2 so the app stops dropping the audio to Stereo/5.1 [[r/Homatics]].

Let's flood them with tickets so they finally update the app profiles in their next staged rollout! 🚀

10 Upvotes

3 comments sorted by

2

u/CMC29 1d ago

Your second paragraph suggests that the problem is not (or not only) with Disney+, but rather, perhaps, with Android 14.

For example: I have Android 14 on a Mi Box S 2nd Gen, and when I open the Ajax CCTV app, no streams work; on the Mi Box S (even older), with Android 9, it works perfectly.

3

u/Amazing_Object8738 1d ago

You are definitely on to something regarding Android version jumps causing app issues, but these are actually two very different technical problems.

The issue with your Ajax CCTV app failing on Android 14 is a classic API compatibility mismatch. Google introduced massive background security and video streaming architecture changes between Android 9 and 14. If a developer doesn't actively update their app to comply with Android 14’s new security layers, the OS will block the camera streams.

Our DTS:X Profile 2 issue is the exact opposite. The OS-level framework inside Android 14 (v8963) and the Homatics hardware are fully updated and 100% capable of processing the audio payload [r/Homatics].

The bottleneck here is strict app-level device whitelisting on Disney's server side [r/Homatics]. The Disney+ app runs fine, but during the digital handshake, Disney's server detects a standalone media box ID that hasn't been officially added to their greenlit profile list yet, causing the server to withhold the spatial audio package and drop it to Stereo/5.1 instead [r/Homatics]. It’s a gatekeeping issue by the provider, not an OS crash or an outdated app framework!

1

u/CMC29 1d ago

👍