Philips TVs playback problems

[Eigeplackter 90]

Hi,

having a strange problem with a friend of mine, using my emby remotely.

He owns 2 Philips PUS8505/12 (58&75") on both running the actual stable emby app.

1TV is connected via Powerlan, the other is wired to the router (as is my media server).

 

He reported several times that video playback stops at exactly 35:47 while audio continues w/o problems.

On both TVs this behaviour can be reproduced, while on his iPad all works flawless.

 

I cant reproduce this behaviour neither in webapp nor iOS (other remote user has iOS devices and no such problems).

Attached are 2 cutouts from todays emby.log.

1st occurence arround 13:04, 2nd around 21:32.

 

 

Snippet 1.txtSnippet 2.txt

 

 

[Luke 42078]

Hi.  Can you try sideloading our standard android app on the same device and see how that compares?

https://emby.media/emby-for-android.html

Thanks.

 

[GrimReaper 4740]

Also, when did your friend last update TV firmware, as Philips is fairly regular with pushing their updates? My main TV is Philips 77OLED806 and I have another 65OLED804, both running native AndroidTV app and the experience has always been practically flawless - and my household is somewhat heavy userbase. Considering PUS805 is relatively recent model, maybe an update would - or will - sort it out. 

[Eigeplackter 90]

I'll advice him in FW updae and otherwise I will try the sideloading thing.

Is there a HOWTO somewhere ? As Im not used to Android and he's not into such things.

 

[Eigeplackter 90]

FW has been updated but did not solve the 35:47 issue.

Will try sideloading, whatever it takes

 

[GrimReaper 4740]

Does that happen with a particular item or with any item played? Are those DirectPlay or Transcode sessions? Are there any ffmpeg logs created? If not, can your friend lower quality below item bitrate or select Playback Correction twice from AndroidTV app OSD Cog menu, as either will result in item being transcoded and logs generated (and at the same time see whether transcode session will carry past 35:47 if it was DirectPlaying previously). 

Edited February 20, 2023 by GrimReaper
Typo

[ebr 16179]

Are these mpeg4/divx items?  If so, the beta of the TV app should solve the issue.

[Eigeplackter 90]

1 hour ago, GrimReaper said:

Does that happen with a particular item or with any item played? Are those DirectPlay or Transcode sessions? Are there any ffmpeg logs created? If not, can your friend lower quality below item bitrate or select Playback Correction twice from AndroidTV app OSD Cog menu, as either will result in item being transcoded and logs generated (and at the same time see whether transcode session will carry past 35:47 if it was DirectPlaying previously). 

It happened with several items, not just a single one, all of em are *,avi files, as he's into older movies and tvshows.

Not happening with all files.

Should have been Directplay (have to test with him to be sure) , no ffmpeg logs for that user created.

 

@ebr All *.avi so far, will try with sideloading stable app, but may try beta if not sucessful.

 

 

Might be a while before I come back with news for all of you (maybe after next weekend, or later),

depends on us meeting.

 

[GrimReaper 4740]

1 minute ago, Eigeplackter said:

All *.avi so far, will try with sideloading stable app, but may try beta if not sucessful

Stable standard Android app apk you can download from the link provided above, beta AndroidTV app apk you can download from here:

 

[Eigeplackter 90]

1st update:

 

It's transcoding the media, and reporting playback errors-

 

Attached a short debug log with a succesful playback, start of a new playback and the transcode log for 1st playback.

 

 

ffmpeg-transcode-99edd5d3-2d21-4f3f-885f-8a0ac84434e4_1.txt embyserver-63812692209.txt

[GrimReaper 4740]

2.0.83 is not the latest beta (it's from 10 Oct 2022 actually, so quite old), download 2.0.87 from above link and sideload. 

[Eigeplackter 90]

Have not yet met him, have usb stick prepared, but need to drive by.

[Eigeplackter 90]

 

@ebr@GrimReaper @Luke
Thanks for the help guys.

 

Installation of AndroidTV beta 2.0.87g fixed the problem.

Tested with 3 separate Philips devices.

Edited February 26, 2023 by Eigeplackter