[axbmcuser]

Additional feedback after some hours of real-life usage testing of the fritschfiretv build from 01 oct. on the cube:

+++

- All around no crashes, freezes or stuff like that
- UI very snappy, even with large test libraries and displaying many movie posters at once (gui resolution 1080 on 1080p sdr output/display)
- Now also tested with 7.1 LPCM output with zero problems (can't test any passthrough on my setup) while using volume amplification
- All codecs: vc1, h264, hevc (hdr2sdr) up to 2160p 60hz all worked fine (only tested untouched material with high bitrates). seeking, skipping very very fast
- Framerate switching (on start/stop) worked with all tested titles (23, 60) without any problems noticed
- While using stable 5ghz wifi with ~290mbit behind a concrete wall i had zero(!) "re-buffering issues" even with highest bitrate untouched bd 2160p 60hz material (gemini man)

--- (maybe this is not build specific or can't really be changed/fixed because of reasons)

1) Zoom and vertical shift does not work (correctly) when using the (needed) hardware acceleration (MediaCodec enabled, MediaCodec (Surface) enabled).
2) All tests had to be performed with "<buffermode>0</buffermode>". Since i like use a network safety buffer on my other higher end windows setups i also tried using "<buffermode>1</buffermode>" with different config/sizes here on android, but it always ends up not working correctly. Maybe there just is no performance headroom for handling such additional buffering when using more demanding untouched files.
Since the CPU-usage indicator is not working, i couldn't really tell.
But:
since it seems to work flawless with "<buffermode>0</buffermode>" if you have stable wifi with 200-300mbit, it isn't really an issue for me.

So - all around it worked very stable and fast today