LG TV app 1.0.4.9

[A.n.d.r.e.w 1]

Is there any update on when the subtitle fix is going to be released for LG TVs?

My TV (65UH950V-ZA) is using 1.0.50 and the PC server is 4.9.3.0 and the fault is still there.

I've tried 3 random videos and they're all still putting subs in the top left corner.

[Luke 42102]

On 2/2/2026 at 2:51 PM, A.n.d.r.e.w said:

Is there any update on when the subtitle fix is going to be released for LG TVs?

My TV (65UH950V-ZA) is using 1.0.50 and the PC server is 4.9.3.0 and the fault is still there.

I've tried 3 random videos and they're all still putting subs in the top left corner.

Hi, we should have a server update out soon to resolve it, thanks.

[AndreiP 33]

Hi, all! 

Thank you for the update!  
Btw, could you please confirm me that the trailers work with the 1.0.50 version? 
A friend of mine told me that it happens that for somes shows or movies the trailers does not work on the LG TV, but plays in the Samsung cellphone. 

 

[Luke 42102]

50 minutes ago, AndreiP said:

Hi, all! 

Thank you for the update!  
Btw, could you please confirm me that the trailers work with the 1.0.50 version? 
A friend of mine told me that it happens that for somes shows or movies the trailers does not work on the LG TV, but plays in the Samsung cellphone. 

 

It is compatible with YouTube trailers now, yes.

[luca1970it 33]

Hi Luke,

I’ve been testing the latest version of the native Emby app for LG on my LG C3, paired with a Samsung HW-Q990D soundbar via eARC.

I've noticed a strange issue: the native app doesn't seem to passthrough Dolby Atmos (TrueHD). My soundbar only receives the Dolby Digital 5.1 core. However, DTS-HD Master Audio works perfectly fine through the app.

The interesting part is that if I use my Nvidia Shield TV Pro (connected directly to the TV's HDMI port), the LG C3 passes through the TrueHD/Atmos signal to the soundbar without any issues via eARC. This confirms the TV hardware and the eARC connection are working correctly.

Also, Atmos works fine on the LG native Netflix app (which uses Dolby Digital Plus), so the issue seems specific to how the Emby app handles TrueHD streams.

Is this a known limitation of the webOS player for native apps, or is there something that can be tweaked?

Thanks for the support!

@SamES

[SamES 1058]

There is a difference between Dolby Atmos TrueHD (lossless audio) vs Dolby Digital Plus which supports Atmos (lossy audio).

Netflix and other apps use Dolby Digital Plus (not TrueHD) and Emby also handles this format without problems.

With regards the the Shield, the TV will pass through lossless TrueHD via HDMI input and ARC output, but it does not support TrueHD from within an app.

So what you are experiencing is correct,, and it's an LG limitation. BTW, Samsung TV's have the same limitation, so it's not unique to LG.

I hope that explains it, but let me know if it doesn't.

This is an old article but it is still accurate and explains it well https://emby.media/support/articles/LG-Why-not-Atmos.html

[luca1970it 33]

On 2/17/2026 at 11:35 AM, SamES said:

There is a difference between Dolby Atmos TrueHD (lossless audio) vs Dolby Digital Plus which supports Atmos (lossy audio).

Netflix and other apps use Dolby Digital Plus (not TrueHD) and Emby also handles this format without problems.

With regards the the Shield, the TV will pass through lossless TrueHD via HDMI input and ARC output, but it does not support TrueHD from within an app.

So what you are experiencing is correct,, and it's an LG limitation. BTW, Samsung TV's have the same limitation, so it's not unique to LG.

I hope that explains it, but let me know if it doesn't.

This is an old article but it is still accurate and explains it well https://emby.media/support/articles/LG-Why-not-Atmos.html

Hi SamES,

I think there is a bit of a misunderstanding regarding how the Nvidia Shield TV Pro operates compared to native TV apps like those on LG (webOS) or Samsung (Tizen).

While it is true that native TV apps are often limited by the OS and hardware to lossy Dolby Digital Plus (DD+), the Nvidia Shield is a completely different beast. I have my Shield connected to an LG C3 OLED, which then passes the audio via eARC to my Samsung Q990D soundbar.

I can confirm that when using the Emby app on the Shield, it correctly performs passthrough for lossless TrueHD (Atmos). My soundbar explicitly displays 'Dolby Atmos' (TrueHD) and not just 'Dolby Digital'.

The limitation you mentioned applies to the native LG webOS app—which, in my experience, often struggles with licenses and even downgrades Atmos to basic Dolby Digital (not even Plus) during certain updates. However, claiming that the Shield has the same limitation within the app is incorrect; the Shield is specifically designed to handle these high-definition passthrough formats without conversion, provided the hardware chain (TV eARC and Soundbar) supports it, which mine does perfectly

 

 

Hi SamES,

In addition to everything described above, I would also like to add that, to further clarify, there is a massive performance gap between the Nvidia Shield TV Pro and the native LG webOS app that goes beyond just audio.

In my setup (Shield TV Pro -> LG C3 -> Samsung Q990D via eARC), the Shield handles lossless TrueHD (Atmos) perfectly. My soundbar explicitly displays 'Dolby Atmos' (TrueHD), proving that the bitstream passthrough is working exactly as intended. The Shield does NOT convert Atmos to basic Dolby Digital; it is designed specifically to avoid that limitation.

On the other hand, the native LG app is a complete disaster. Not only does it often fail to passthrough Atmos (downgrading it to basic Dolby Digital, not even Plus), but it also struggles with Dolby Vision metadata. I’ve noticed that when the LG app encounters certain audio tracks it can't handle, it seems to go into a 'protection mode' or forces a transcode that breaks the video layer. As a result, I often see the TV trigger HDR10 instead of Dolby Vision, which is absurd for a high-end OLED C3.

This inconsistency doesn't happen on the Shield. Because the Shield supports Direct Play for both TrueHD and various Dolby Vision profiles, the server doesn't need to touch the file. Everything stays intact. Claiming the Shield app has the same limitations as the LG or Samsung native apps is simply incorrect; the Shield is the only way to actually get the full quality out of a setup like mine.

Edited yesterday at 12:20 PM by luca1970it

[NakedPirate 16]

2 hours ago, luca1970it said:

On the other hand, the native LG app is a complete disaster.

Not the app, but the TV. 
Take the TV for what it is: a dumb monitor. Everything with and on the TV is a non-free locked-down walled garden. Don't settle for that crap - every China-stick for 20 bucks is light years ahead, you don't need the gold standard "Shield". TV'S and especially LG won't even manage to send multichannel PCM over EARC. I wrote about 50 E-Mails to all levels of support in the last years - they don't give a shit! If you need true HD, the Fire or Raspberry does it without problems.
 

Edited 21 hours ago by NakedPirate

[SamES 1058]

22 hours ago, luca1970it said:

I can confirm that when using the Emby app on the Shield, it correctly performs passthrough for lossless TrueHD (Atmos). My soundbar explicitly displays 'Dolby Atmos' (TrueHD) and not just 'Dolby Digital'.

The limitation you mentioned applies to the native LG webOS app—which, in my experience, often struggles with licenses and even downgrades Atmos to basic Dolby Digital (not even Plus) during certain updates. However, claiming that the Shield has the same limitation within the app is incorrect; the Shield is specifically designed to handle these high-definition passthrough formats without conversion, provided the hardware chain (TV eARC and Soundbar) supports it, which mine does perfectly

That's correct, and I think we are saying the same thing.  If a device (such as the shield) sends lossless audio into the TV via HDMI, then it can be passed out via HDMI/eARC without an issue, but an app on the TV cannot pass lossless audio out from the app on the TV via HDMI/eARC. Actually you will get nothing, the app/server must convert the audio to something compatible, which is generally AC3.

By app in this statement, I meant an app on the TV, not the Shield

On 17/02/2026 at 21:35, SamES said:

With regards the the Shield, the TV will pass through lossless TrueHD via HDMI input and ARC output, but it does not support TrueHD from within an app.

 

22 hours ago, luca1970it said:

I’ve noticed that when the LG app encounters certain audio tracks it can't handle, it seems to go into a 'protection mode' or forces a transcode that breaks the video layer. As a result, I often see the TV trigger HDR10 instead of Dolby Vision, which is absurd for a high-end OLED C3.

Again, you are correct. In some cases, the video may need to be transcoded as well as the audio which will break DV.  

Regardless, these are limitation of the TV with regards to not allowing apps on the TV to support lossless audio, and it is a limitation of the DV format that it does not survive a transcoding process. If you want TrueHD and DV support, then absolutely the Shield is the right device.