HDR aspect ratio problem.

[Eriol]

Okay, that sounds good. SMB will certainly go too.

The PRoblem already exists forever and I do not think that himedia yet another update. Or are there signs?

I can not send it back unfortunately, I have the player for too long

It usually takes 3 months for HiMedia to publish a new firmware. So you need to wait about one more month to see if they fix anything. Till then I recommend you to read this guide:
http://www.futeko.com/newforum/index.php?topic=1566.0

[Tregobad]

HiMedia have said early/mid May for Kodi 17 passthrough and HDR unusual aspect ratio fix. Both are dependent on HiSilicon.

I have limited ability to influence timescale. It goes futeko >> HiMedia >> HiSilicon.

Dear Futeko,
May is gone some weeks ago, what are the status concerning the Update ?
And please, don?t answers like: "use MXplayer".
I bought an expensive 4K Mediaplayer and don?t like to fiddle around with the MX Pro.
In easy words: I would like to have, what I payed for. Bad enough that I have to wait for these core functionality till now.
Many thanks.

[netguru]

http://www.futeko.com/newforum/index.php?topic=711.msg16940#msg16940

[Tregobad]

http://www.futeko.com/newforum/index.php?topic=711.msg16940#msg16940

Thanks netguru for the fast reply.
We will see if the release dates AND Error corrections communicated comes true (became too often disapointed ).

[Lavalyte]

Did this ever get resolved? I am still seeing this issue.

[pcristi]

Did this ever get resolved? I am still seeing this issue.

Original HDR bug of double black bar(wrong position on screen) for crop 16:9 video and report on opening of that topic is fully solved on Android 7 2.0.4 or newest FW let us know about yours problem.

[Lavalyte]

Did this ever get resolved? I am still seeing this issue.

Original HDR bug of double black bar(wrong position on screen) for crop 16:9 video and report on opening of that topic is fully solved on Android 7 2.0.4 or newest FW let us know about yours problem.

I realised the problem.. I'm on 5.1.1. I assumed the auto updater would resolve this.
Right now I'm trying to get some information on if the upgrade to 7.2 still works as per the other thread.

[Mount81]

The problem is full resolved in the up from 2.0.4 as mentioned. Just follow the instructions precisely how to update up to some of the latest FW's.