[blazinsmokey]

Interesting b/c that's how I have it set and since I set it like so there has been zero crashes. I think that is where our conversation was not being understood.

Before I couldn't watch for more than 30 minutes without crash back to kodi library screen. Now 3 movies total tested (~6 hours) and my wife just finished watching whatever she watches for about 3.5 hours and again zero crashes back to the menu.

[Martijn]

That should not be settable.

It can as they are independent of each other

[blazinsmokey]

It can as they are independent of each other

Hi Martijn, thank you for the clarification. So I am still getting HW acceleration right?

[fritsch]

As thought: It makes no sense: https://github.com/xbmc/xbmc/blob/master...c.cpp#L378

The meaning basically is: "Disable both" to Disable Mediacodec.

Should be something like:
Mediacodec: Enabled
Surface: Enabled

-> Use mediacodec surface

Mediacodec: Disabled
Surface not visible
-> No hw decoding

Mediacodec: Enabled
Surface disabled
-> GLES rendering.

[Koying]

"Plain" Mediacodec and "Surface" mediacodec are conceptually 2 different codecs (at least that's how I saw it) as their rendering path are completely different.
It works as you describe, besides label/settings.xml tweaks, which make sense, indeed.

[twferg]

Hola Amigos. I experienced this problem - "stream stalled" - on my Amazon Fire TV G2 running Kodi 17 RC3. Tried modifying cache settings in advancedsettings.xml with little improvement, and eventually went back to Kodi 16.1, which works great with both "plain" mediacodec and "surface" mediacodec enabled. This thread is the only place that I've seen the problem accurately described. Sadly, no activity here since 2017-01-12. Is this problem recognized as a bug that needs to be fixed in the ARM Kodi 17 release?

[blazinsmokey]

No solutions from my understanding. Android Dev's here don't seem to care much about Amazon devices. For me different things just started acting weird when I turned only the media codec off. I went back to Beta 7 which has worked fine for me with both options enabled. I'd try that version and see how it goes for you until we get a final release and then try that one out.

[twferg]

Gracias blazinsmokey. Tonight I had the same problem with Kodi 16.1, so I'm at a loss for a rational explaination. I'll try Beta 7 tomorrow with both settings enabled.

[X-Kent]

I am still having this issue in 17.1. It happens usually after couple of hours watching tv.

09:30:36.136 T:4114337728 NOTICE: Display resolution ADJUST : 1920x1080 @ 50.00 - Full Screen (21) (weight: 0.000)
09:38:29.134 T:3716486048 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
10:13:52.414 T:3702121376 NOTICE: CActiveAEStream::AddData - messy timestamps, increasing interval for measuring average error to 6000 ms
10:26:45.740 T:3702121376 NOTICE: Previous line repeats 1 times.
10:26:45.740 T:3702121376 NOTICE: CVideoPlayerAudio:rocess - stream stalled
10:26:48.110 T:3716486048 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
14:28:37.443 T:3702121376 WARNING: Previous line repeats 3 times.
14:28:37.444 T:3702121376 NOTICE: CVideoPlayerAudio:rocess - stream stalled
14:28:50.718 T:3716486048 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
14:29:41.216 T:3702121376 NOTICE: CVideoPlayerAudio:rocess - stream stalled
14:29:47.858 T:3716486048 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
14:34:47.699 T:3702121376 NOTICE: CVideoPlayerAudio:rocess - stream stalled
14:34:49.658 T:3716486048 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
16:01:46.364 T:3702121376 WARNING: Previous line repeats 1 times.
16:01:46.364 T:3702121376 NOTICE: CVideoPlayerAudio:rocess - stream stalled

I was not watching the TV all the time. When I arrived, the screen was frozen.

Any news regarding this issue ? Any workaround to at least "stop" instead of freezing the screen ?

I am running Kodi 17.1 on LibreELEC on S905x device.

[blazinsmokey]

I have not had this issue with Fire TV 2, different device than your S905, but seems to have went away with the final release of 17 and 17.1. I have not seen this issue since the betas. You might need to find users with the same device to see what's up. Clean install may fix it as well.

[grhhh]

Hi,

I have the same problem on a Lenovo tablet.

cpp:


21:12:06.425 T:548194337872  NOTICE: Starting Kodi (17.6 Git:20171119-ced5097). Platform: Android ARM 64-bit

21:12:06.425 T:548194337872  NOTICE: Using Release Kodi x64 build

21:12:06.425 T:548194337872  NOTICE: Kodi compiled Nov 19 2017 by GCC 4.9.0 for Android ARM 64-bit API level 21 (API level 21)

21:12:06.425 T:548194337872  NOTICE: Running on LENOVO Lenovo TB-X304F with Android 7.1.1 API level 25, kernel: Linux ARM 64-bit version 3.18.31-perf-g818d142

21:12:06.425 T:548194337872  NOTICE: FFmpeg version/source: ffmpeg-3.1-kodi

21:12:06.425 T:548194337872  NOTICE: Host CPU: AArch64 Processor rev 4 (aarch64), 4 cores available

21:12:06.425 T:548194337872  NOTICE: Product: LenovoTB-X304F, Device: X304F, Board: LenovoTB-X304F - Manufacturer: LENOVO, Brand: Lenovo, Model: Lenovo TB-X304F, Hardware: qcom



[...]



21:16:19.947 T:547662046288   DEBUG: CDVDVideoCodecAndroidMediaCodec::virtual void CDVDVideoCodecAndroidMediaCodec::SetCodecControl(int) 0->10000000

21:16:19.948 T:547662046288    INFO: CVideoPlayerVideo - Stillframe detected, switching to forced 23.976024 fps

21:16:19.953 T:547662046288   DEBUG: CPullupCorrection: pattern lost on diff 208541.666667, number of losses 1

21:16:20.096 T:548194337872   ERROR: CDVDMediaCodecInfo::ReleaseOutputBuffer ExceptionCheck index(8), render(1)

21:16:20.596 T:547662046288   ERROR: Previous line repeats 9 times.

21:16:20.596 T:547662046288   DEBUG: CDVDVideoCodecAndroidMediaCodec:ecode current state (4)

21:16:20.614 T:548194337872   ERROR: CDVDMediaCodecInfo::ReleaseOutputBuffer ExceptionCheck index(8), render(1)

[mancer]

...and I have the same issue on an Odroid device, so it's not limited to Android (posted it here). Unfortunately no solution though.