futeko.com FORUM
Product Support => HiMedia Q10 Pro, Q5 Pro => Topic started by: jeps on September 18, 2016, 08:19:00 AM
-
Hi.
I generally have my Q5 Pro switched on all the time.
The Q5 Pro is connected to a HDMI input on my 4K AV receiver, as are my TV box and my Chromecast.
Even though I have the output resolution fixed in the settings in my Q5 Pro it always change to to typically 1080i.
I then manually change the setting to 2160@60 and it stays at 2160 for the rest of time of using it.
I normally leave the Q5 Pro in the Kodi GUI.
The next time I switch my receiver to the Q5 Pro input the output is at 1080i again.
Has anybody got a cure for this quite annoying behaviour, please.
-
Same here! Old problem. Himedia= :-X
-
Same here, sometimes after longer Standby Q10pro restarts with 1080i
-
HiMedia are aware of this. It happens only in 2160p 60Hz mode and will be fixed.
-
It happens in 2160p 30hz mode too - only noticed it last week (I did update last week, so not sure if it's a 'new' issue with the last firmware released).
-
HiMedia are aware of this. It happens only in 2160p 60Hz mode and will be fixed.
NO! It happens with 2160p 24/25 hz too here ;)
-
It does and does not happen with 2160/24fps. Let me explain. I have a Yamaha 1079 and to this I have connected a UHD TV and a 1080p TV. If I have both video units connected through the 1079 (1+2 output on Yammy) the resolution of the HiMedia always shows 1080p, the lower resolution takes precedence. However, if I switch the Yammy to output 2 (the UHD TV) and set the resolution on the HiMedia to 2160/24fps and leave the Yammy setting on 2 it does not change resolution, Switch the Yammy back to 1+2 and the resolution changes to 1080p.
Ipso facto, the HiMedia Q5 Pro, in this case, is not at fault.
-
In that case not, but I have seen resolution switch to 1080i after reboot on a simpler setup with just a 4K capable AVR and a 4K TV. It is definitely a bug.
I had passed it onto HiMedia a while ago for 2160 60Hz, but thanks for the feedback about it also happening at other resolutions. So it's a 2160p bug. I presume Himedia will have figured this out themselves when establishing how to fix it.
-
Any news about this ?
I bought a 4K TV (LG E6) recently and this bug is driving me crazy :(
-
mine does this to, the other little annoying habit, is it will often not auto reconnect to wi fi, when switched on from stand by
-
I can confirm, that the bug is still present.
The only thing, that minimizes the resolution changes is to go as high as possible in colorspace setting.
But I am disappointed that himedia didn't fix this (most likely) pretty trivial bug.
-
I can confirm, that the bug is still present.
The only thing, that minimizes the resolution changes is to go as high as possible in colorspace setting.
But I am disappointed that himedia didn't fix this (most likely) pretty trivial bug.
7 beta or?
-
Still not fixed in "Q5 PRO FIRMWARE. ANDROID 7. 2.0.0-FUTEKO-EN. HMD-2.0.0 2016-11-18.175905"
Really disappointed :'(
-
Mine has stopped doing it for some reason - can't explain why.
-
Did some testing over the weekend, found a solution that works for me, hope it does for you too.
It's very simple:
When turning stuff on, start with your TV.
When turning stuff off, start with your HiMedia player.
If you never switch off your HiMedia, then always turn your receiver off first.
-
Pleased to say that this has been fixed (fingers crossed) in next firmware.
-
Pleased to say that this has been fixed (fingers crossed) in next firmware.
RGB bug? It is also fault.
-
q5pro (2.0.4) doesn't keep 2160p/60 resolution in settings, each time i turn off it (or my yamaha 581 receiverAV) turn back to 1080p/60 resolution.... very annoying.... ANY HELP?
-
Sorry I don't know the solution, but it's a well know issue since the beginning. The strange is that in that according to the newest 2.0.4 firmware changelog it should have been fixed by now. Some reported as they didn't experienced the resolution reset since they installed 2.0.4, but others did and still have this problem, just like before. It seams that it's not have been 100%-ly fixed and it can occur in some circumstances.
Maybe it has to do something with the AVR configurations or type, or maybe even the colourspace settings and switchings could affect that. Hope Futeko will report it to HiMedia, and would be also nice, to at least we could have some feedback from HiMedia from the -possible- causes of this long lasting issue.
Futeko?!
-
Also have this problem - never had this issue with 1.10 (Android 5).
-
Sorry I don't know the solution, but it's a well know issue since the beginning. The strange is that in that according to the newest 2.0.4 firmware changelog it should have been fixed by now. Some reported as they didn't experienced the resolution reset since they installed 2.0.4, but others did and still have this problem, just like before. It seams that it's not have been 100%-ly fixed and it can occur in some circumstances.
Maybe it has to do something with the AVR configurations or type, or maybe even the colourspace settings and switchings could affect that. Hope Futeko will report it to HiMedia, and would be also nice, to at least we could have some feedback from HiMedia from the -possible- causes of this long lasting issue.
Futeko?!
problem still persist http://www.futeko.com/newforum/index.php?topic=1232.0
"standard" user workaround it's not a big deal, but seems works....
i hope for a firmware-fix anyway
-
I have reported this to Himedia already as a bug on 2.0.4 affecting some users.
It doesn't happen to everyone though, so would be useful if cause could be isolated.
I will merge this thread with the other one for previous firmware. If you have this problem please post details of your setup (e.g. Q5/Q10 Pro > AVR model > HDMI switch > type of TV, and HDMI cable type).
-
I have reported this to Himedia already as a bug on 2.0.4 affecting some users.
It doesn't happen to everyone though, so would be useful if cause could be isolated.
I will merge this thread with the other one for previous firmware. If you have this problem please post details of your setup (e.g. Q5/Q10 Pro > AVR model > HDMI switch > type of TV, and HDMI cable type).
thanks
-
hello
i have the same problem.
with the frimware 2.01 ==> ok
with 2.03 ==>ok
with 2.04 it is not ok
-
In another local Himedia Forum (topic actually) we have gathered some information and speculations regarding the causes of the issue.
Possible concluded reasons, which -maybe- seams to be more than just simply guessing:
It may has to do something with the ARC function in the case of an Himedia-> AVR-> TV line. Or/and possibly with the source switching on the AVR's or/and the TV's. Some have reported that the resolution reset would appear all the time (could be reproduced) when Himedia Box is turned on (with 2160p@60Hz res), and one's switches the input of the TV to either USB or the TV Tuner source and begins to use the ARC on the AVR. And after switching back to the Himedia Box's source it is already resetted back to 1080i@60Hz.
But yea, further testing regarding this would be needed.
Hope this gives something to start with...
-
Problem was for me in 2.0.1 and still in 2.0.4 present (wasnt on 2.0.3). I thougt/hoped it would be fixed with newest fw. My devices are in my signature.
-
I have still this problem. Is there a solution or fix available?
My setup is:
LG 55bd7 TV
Yamaha RXV683 Receiver
Q5 pro with latest custom firmware.