Firmware 1.0.5 issues

[Nice Monkey]

It is not uncommon that with a major release some things get broken as side-effects requiring a bug-fix release on top of it. Not reporting all glitches is not uncommon either unfortunately. Most commercial products (and KODI) use Beta versions and next Release Candidates to find those glitches before a final release.

As long as Himedia brings out a bug-fix releases quick enough that is very acceptable from my point of view. Openly reporting all fixes included would highly be appreciated.

[futeko.com]

Ok so this is what I have done.

Tested by installing these version.  All installs via USB and button.

Installed 1.0.5 : going wrong
Installed 1.0.3 : fine
Installed 1.0.6 : fine.

Just to confirm I went back

Installed 1.0.5 : going wrong
Installed 1.0.6 : fine.

Seems there was more broken than they claim in release notes for 6 hence urgent fix.

OK. Possible. I'd have expected more feedback about it though.

Good that 1.0.6 has fixed it.

[PJDavis1970]

It is not uncommon that with a major release some things get broken as side-effects requiring a bug-fix release on top of it. Not reporting all glitches is not uncommon either unfortunately. Most commercial products (and KODI) use Beta versions and next Release Candidates to find those glitches before a final release.

As long as Himedia brings out a bug-fix releases quick enough that is very acceptable from my point of view. Openly reporting all fixes included would highly be appreciated.

Thats what QA regression testing is for

[PJDavis1970]

Ok so this is what I have done.

Tested by installing these version.  All installs via USB and button.

Installed 1.0.5 : going wrong
Installed 1.0.3 : fine
Installed 1.0.6 : fine.

Just to confirm I went back

Installed 1.0.5 : going wrong
Installed 1.0.6 : fine.

Seems there was more broken than they claim in release notes for 6 hence urgent fix.

OK. Possible. I'd have expected more feedback about it though.

Good that 1.0.6 has fixed it.

Yes it is good that its fixed.  However the ghosting issue has reappeared in 1.0.6.  I had this problem in the first 2 firmwares.  I appears when there are dark areas on the screen.  For example in a movie if someone has a black jacket on and they move you see like ghosting in those areas.

[DancesWithChickens]

not only an issue with 1.0.5, but i'll post it here anyway:

Internal HDD is shown as "sda1".
Connect external HDD via USB, it is shown as "sdb1".
Makes sense - the internal SATA connection should always be prioritized.

But:
Boot up Q10 Pro with internal HDD and external HDD:
Internal HDD is shown as "sdb1"
External HDD is shown as "sda1".

Not only does that not make sense, it is problematic, e.g. for KODI.
Sources/library paths do not work anymore, when updating library with paths changed, library items get deleted.

Fix this plz.

[Nice Monkey]

not only an issue with 1.0.5, but i'll post it here anyway:

Internal HDD is shown as "sda1".
Connect external HDD via USB, it is shown as "sdb1".
Makes sense - the internal SATA connection should always be prioritized.

But:
Boot up Q10 Pro with internal HDD and external HDD:
Internal HDD is shown as "sdb1"
External HDD is shown as "sda1".

Not only does that not make sense, it is problematic, e.g. for KODI.
Sources/library paths do not work anymore, when updating library with paths changed, library items get deleted.

Fix this plz.

This is an Android thing and reported before. It is not easy to get this fixed. Only OpenElec does not have the problem and even gives Volume Labels.
Android assigns interfaces on a first come bases. So your drives apparently activate at the same time. Also for multiple USB-drives "sdb1, sdb2 etc".

I am using a Docking Bay plus an Internal HDD myself. The Docking Bay is always the slowest and gets assigned to "sdb1" always.

[Mount81]

Quote PJDAvis:

Yes it is good that its fixed.  However the ghosting issue has reappeared in 1.0.6.  I had this problem in the first 2 firmwares.  I appears when there are dark areas on the screen.  For example in a movie if someone has a black jacket on and they move you see like ghosting in those areas.


I also have seen some ghosting in a couple of videos, also on darker areas/image. It also appears when the image is  mostly darker and some lighter object (like a face or white cloth or lightbulb) appears , and it pulls and leaves a ghost image as it moves. Has Himedia aknowledge from this yet?

[PJDavis1970]

Quote PJDAvis:

Yes it is good that its fixed.  However the ghosting issue has reappeared in 1.0.6.  I had this problem in the first 2 firmwares.  I appears when there are dark areas on the screen.  For example in a movie if someone has a black jacket on and they move you see like ghosting in those areas.


I also have seen some ghosting in a couple of videos, also on darker areas/image. It also appears when the image is  mostly darker and some lighter object (like a face or white cloth or lightbulb) appears , and it pulls and leaves a ghost image as it moves. Has Himedia aknowledge from this yet?

This was a problem I noticed when the Q10 was first release.  Firmware 1.0.3 fixed the issue for me however they have no reintroduced it.

[Nice Monkey]

This was a problem I noticed when the Q10 was first release.  Firmware 1.0.3 fixed the issue for me however they have no reintroduced it.

May I suggest you to make a FW 1.0.6 bug report for this specifically. That way you it will get the attentions it deserves. 
Would do it myself if had seen it and could reproduce to test.

[Tregobad]

My conclusion as of today with FW 1.06:
Setting of YCbCr420 10Bit ist possible (under 2160p / 60Hz)
But....with this setting I get no video signal  from the started Video, Audio is OK.
If  I switch to 1080p and  YCbCr420 10Bit it works. But this is not the capability I bought the Himedia for.

Therefore I`ve the choice to see the video signal on my Panasonic4K under 8Bit (means no HDR), or swichting to 10Bit (means HDR) but have no video signal.

To check the problem from the TV side, I`ve switched the Input signal at TV in a compatible mode (means without HDR capability). I see the Himedia video signal at once.
I guess the 10Bit signal sent from Himedia is not correct.

It looks like, Himedia get`s the setting to 10Bit working, but nothing behind it?
I have still the same problem > see next paragraph: In memory...   

Can anybody really confirm, that genuine 10Bit/HDR videos under 2160p/60hz will played and shown in HDR on his TV?


In memory my post concerning 10Bit/HDR Video signal with the first Firmware (Box delivery):
I`m wondering that I can`t set it to YCbCr420 10Bit but to 8 Bit.
If I try to change the settings to 10 Bit, the screen comes back in some seconds with the old setup, means 8 Bit.
My TV is the brandnew Panasonic DXW904 with UHD Premium certificate and HDR (HDMI cable is certified for 4K, HDR also). Therefore I should do it.
For my point of view I must set 10 Bit to see HDR.
Additional Infos:
Tested with the HDMI cable out of the box also, same result.
Checked the TV specs: (see enclosure) > should no problem at all.
At the box:
Changed the custom display format to 1080p (several Hz) > it works, 10 Bit possible
If I go back to 2160P > only 8 Bit possible

[Tregobad]

With FW 1.05 / 1.06 can anybody really confirm, that genuine 10Bit/HDR videos under 2160p/60hz will played and shown in HDR on his TV?

My conclusion as of today with FW 1.06:
Setting of YCbCr420 10Bit ist possible (under 2160p / 60Hz)
But....with this setting I get no video signal  from the started Video, Audio is OK.
If  I switch to 1080p and  YCbCr420 10Bit it works. But this is not the capability I bought the Himedia for.

Therefore I`ve the choice to see the video signal on my Panasonic4K under 8Bit (means no HDR), or swichting to 10Bit (means HDR) but have no video signal.

To check the problem from the TV side, I`ve switched the Input signal at TV in a compatible mode (means without HDR capability). I see the Himedia video signal at once.
I guess the 10Bit signal sent from Himedia is not correct.

It looks like, Himedia get`s the setting to 10Bit working, but nothing behind it?
I have still the same problem > see next paragraph: In memory...   

Can anybody really confirm, that genuine 10Bit/HDR videos under 2160p/60hz will played and shown in HDR on his TV?


In memory my post concerning 10Bit/HDR Video signal with the first Firmware (Box delivery):
I`m wondering that I can`t set it to YCbCr420 10Bit but to 8 Bit.
If I try to change the settings to 10 Bit, the screen comes back in some seconds with the old setup, means 8 Bit.
My TV is the brandnew Panasonic DXW904 with UHD Premium certificate and HDR (HDMI cable is certified for 4K, HDR also). Therefore I should do it.
For my point of view I must set 10 Bit to see HDR.
Additional Infos:
Tested with the HDMI cable out of the box also, same result.
Checked the TV specs: (see enclosure) > should no problem at all.
At the box:
Changed the custom display format to 1080p (several Hz) > it works, 10 Bit possible
If I go back to 2160P > only 8 Bit possible