futeko.com FORUM
Product Support => HiMedia Q10 Pro, Q5 Pro => Topic started by: futeko.com on December 28, 2018, 07:28:58 AM
-
Download & Instructions
THIS FIRMWARE CAN ONLY BE INSTALLED ON A EUROPEAN Q10 PRO RUNNING ANDROID 7 FIRMWARE 2.0.4 OR LATER! Information on how to update from earlier firmware to Q10 Pro version 2.0.4 is here (http://www.futeko.com/newforum/index.php?topic=2096.0). Your current firmware version can be found at Settings - About - Device Info - Build number.
Download: http://www.mediafire.com/file/rkge581r713c6i5/Q10_PRO_FIRMWARE_2.1.1._INSTALL_ON_ANDROID_7_v2.0.4%252B_ONLY._FUTEKO._HMD-2.1.1_2018-12-24.zip/file
1. Extract update.zip (using an unzip program like 7zip, winzip etc) from the downloaded zip archive to the root of a FAT32 formatted USB pen drive. (the USB pen drive should contain a single file called 'update.zip'). Note, there is no need to rename anything!
2. Insert the USB pen drive into any USB port of Q10 Pro.
3. With Q10 Pro turned off, use a paper clip or pen to press and hold the the pinhole UPGRADE button on the back of Q10 Pro (next to the power port).
4. While keeping the UPGRADE button pressed, turn on the Q10 Pro.
5. Q10 Pro will showthe Android 7 coloured circle logo.
6. When you see the circle logo you can release the restore button.
7. A progress bar will indicate update progress. Do not turn box off or use the box/remote during update!
8. When update is complete the box will automatically reboot.
9. First boot will take 3-5 minutes. The box will reboot into new firmware. Allow boot to complete.
-
Q5 Pro version: http://www.futeko.com/newforum/index.php?topic=3995.0
-
9. Optimized the video player to solve the problem that some subtitles are flashing
->And again: what does that mean/suppose to refer? The so long awaited fix for the "sub-line skipping bug"? Or "something completely different" and useless "fake fix" again , that we users never ever even have heard about? Just hope that the previous...
-
+1 .
-
9. Optimized the video player to solve the problem that some subtitles are flashing
->And again: what does that mean/suppose to refer? The so long awaited fix for the "sub-line skipping bug"? Or "something completely different" and useless "fake fix" again , that we users never ever even have heard about? Just hope that the previous...
thats why i switched again to my old popcorn hour
-
Well Halleluiah, looks like Xmas has finally arrived for Q10 owners.
Just installed and did a quick test.
Finally, the skipping subtitles are working, I think most of us had given up on this ever being fixed.
Also looks like there has been improvements to Samba, although I previously could access my box using Samba, I needed to enter the device name in the address bar of File Explorer to access the box.
Now it is appearing under the network device list. This should help many that have had problems using Samba.
I have only had a quick look, but so far looking promising. :)
edit:->
Having spent more time looking at this version, I think I jumped the gun with Samba.
They may have fixed some naming issues, but still very temperamental, when going from the Q10 back to Windows (at least if you have password security).
If using Kodi, I have found no issues, entering a password and creating a link back to a Windows share.
However, when using the Q10/LAN to access windows, it has no problems finding the network name in its search, but when you try to access it and enter a username/password, it goes nowhere!
On the other hand, if you do the manual link, and enter all the details manually, it has no problems in creating a new short-cut.
The auto search seems flaky, maybe without any security it would create the short-cut.
-
Has anyone checked whether the problem of the aspect ratio pal 720x576 has been solved?
http://www.futeko.com/newforum/index.php?topic=2576.0
Thank you
-
Hi :)
NEW FIRMWARE HAS A VIRUS !!!!!
BitDefender Message is:
"The file C:\Users\Bobo\AppData\Local\Temp\Rar$DRa6880.41322\system\priv-app\InputDevices\InputDevices.apk is infected with Android.Trojan.Neucore.gTVQF and was moved to quarantine."
What is Android.Trojan.Neucore.gTVQF ?!
Should we install it or what?!
Best regards :)
-
Has anyone checked whether the problem of the aspect ratio pal 720x576 has been solved?
http://www.futeko.com/newforum/index.php?topic=2576.0
Thank you
i quote this.... its important to me !
Hi :)
NEW FIRMWARE HAS A VIRUS !!!!!
BitDefender Message is:
.........
what the fu*k ?!?!?!?!?!
is it real?
-
Could be a false positive, I ran these checks online.
When I uploaded the file to VirusTotal, 4 out of 30 scanners reported it had Android.Trojan.Neucore.GTVQF. All the others said it was clean.
FortiGuards Lab said it was clean.
Jotti's Malware Scan (4 out of 15 reported Android.Trojan.Neucore.GTVQF).
I managed to find one video pal 720x576 mpeg file, it did not display the aspect ratio correctly.
Edit:
My bad, the sample video file 720x576 I tested, had black bars encoded around the video. Thanks to Mount81 for pointing out this maybe the issue.
-
-
-
Hi
Install free (test version) Bit Defender 2019 and you will see the same message.
Before it, extract all files from install.zip to some place
Best regards
-
Okay, I just ran the same test with the previous firmware 2.1.0 on the VirusTotal web site and the results were almost the same (slightly worse).
Out of the 30 scanners 4 detected Android.Trojan.Neucore.GTVQF again, but 2 others reported Artemis and PUP.HighConfidence. The rest reported clean.
Looking more like a false positive to me.
-
Hmmm... This "Trojan thing is strange"....
Have anyone checked 2.0.9? It's just weird why HiMedia still don't have even 2.1.0 up on their support page...?
-
Hi :)
NEW FIRMWARE HAS A VIRUS !!!!!
BitDefender Message is:
"The file C:\Users\Bobo\AppData\Local\Temp\Rar$DRa6880.41322\system\priv-app\InputDevices\InputDevices.apk is infected with Android.Trojan.Neucore.gTVQF and was moved to quarantine."
What is Android.Trojan.Neucore.gTVQF ?!
Should we install it or what?!
Best regards :)
InputDevices.apk is a same in all HiMedia Android 7 firmware, need closer of 2 years to discover as false positive virus ;).
-
Please, could anybody test the .srt overlap subtitle issue to help confirm it is resolved on this firmware ?
-
pcristi is correct, I checked Checked 2.09 & 2.06, exactly the same results as 2.1.0.
6 out of 30 checkers failed, as opposed to 4 out of 30 for 2.1.1
I think we can put this one to bed.
-
@afss
For me .srt overlap subtitle still flashing(clipping) but not missing line similar to FW v2.0.6.
-
If someone of you has Kasperky, it should be good to check firmware with Kaspersky, too.
I use Bit Defender for years and I am shure that Bit Defender makes a very good job, it means: WE HAVE A VIRUS! :(
-
@bobo63
You are free to believe one of them
Kaspersky --> Clean
BitDefender --> Android.Trojan.Neucore.gTVQF
https://www.virustotal.com/#/file/ba0fd4073ec59c815e76aea1f48e0a6801a2625fabe9b8155c4a07457c27654f/detection
https://www.fortiguard.com/encyclopedia/virus/7895067/android-neucore-tvtp-tr
-
@afss
For me .srt overlap subtitle still flashing(clipping) but not missing line similar to FW v2.0.6.
Thank you !
-
I would be shocked if the firmware contained a virus, but will report the finding to HiMedia and pass on their reply here.
In the meantime I am leaving the firmware up as it is identical in respect to the 'virus' as previous firmwares.
-
9. Optimized the video player to solve the problem that some subtitles are flashing
->And again: what does that mean/suppose to refer? The so long awaited fix for the "sub-line skipping bug"? Or "something completely different" and useless "fake fix" again , that we users never ever even have heard about? Just hope that the previous...
Here, here. +1.
Maybe we are lucky, since Pcristi says this one does not SKIP lines, but only FLICKER.
Looking forward to further comments on Image and Color Quality improvements if any, that justifies upgrading from 2.0.6.
Cheers guys.
-
-
I would be shocked if the firmware contained a virus, but will report the finding to HiMedia and pass on their reply here.
Other Android 7.0 InputDevices.apk have a same positive report, for example SHIELD Tablet
ro.build.description=wx_na_wf-user 7.0 NRD90M 1928188_1065.2559 release-keys
ro.build.fingerprint=nvidia/wx_na_wf/shieldtablet:7.0/NRD90M/1928188_1065.2559:user/release-keys
SHA-256 41f675f38051f51d8fc0f387bd061978a81995726db4d75125df0f670ea42d8c
File name InputDevices.apk
File size 136.46 KB
Last analysis 2018-11-10 04:56:48 UTC
https://www.virustotal.com/#/file/41f675f38051f51d8fc0f387bd061978a81995726db4d75125df0f670ea42d8c/detection
-
Another improvement which isn't listed in the changelog is that (for me at least) the WiFi and Bluetooth settings remain OFF after a restart or switch off :) Can other confirm this?
-
I would be shocked if the firmware contained a virus, but will report the finding to HiMedia and pass on their reply here.
Other Android 7.0 InputDevices.apk have a same positive report, for example SHIELD Tablet
ro.build.description=wx_na_wf-user 7.0 NRD90M 1928188_1065.2559 release-keys
ro.build.fingerprint=nvidia/wx_na_wf/shieldtablet:7.0/NRD90M/1928188_1065.2559:user/release-keys
SHA-256 41f675f38051f51d8fc0f387bd061978a81995726db4d75125df0f670ea42d8c
File name InputDevices.apk
File size 136.46 KB
Last analysis 2018-11-10 04:56:48 UTC
https://www.virustotal.com/#/file/41f675f38051f51d8fc0f387bd061978a81995726db4d75125df0f670ea42d8c/detection
Thanks. I see that as conclusive proof that it isn't a virus.
-
So, I have checked
Q10 PRO FIRMWARE. ANDROID 7 v2.0.4+ TO v2.1.0. FUTEKO. HMD-2.1.0 2018-09-20.022650
with my Bit Defender :o
THIS VERSION IS CLEAN, so says Bit Defender.
It means, VIRUS belongs to new features ;)
>:( >:( >:(
-
Another improvement which isn't listed in the changelog is that (for me at least) the WiFi and Bluetooth settings remain OFF after a restart or switch off :) Can other confirm this?
For me is keep off, with clean install and not additional apps installed.
-
@afss
For me .srt overlap subtitle still flashing(clipping) but not missing line similar to FW v2.0.6.
Hi Cristi
If I understand correct the sub problem is fixed but not entirely? How it flash? :(
-
quick question. can you actually backup/save settings so I don't have to redo on the upgrade? I don't care about apps or kodi really since I only use the media player. I only see the link to backup kodi, but does that backup everything else too or just kodi stuff?
-
Can anyone test if if external .ass (PGS) subtitles work correctly? Here's a test sub: http://www.filedropper.com/assextensionpgssub-test (http://www.filedropper.com/assextensionpgssub-test)
Just rename it for a desired video, but keep the .ass file extension. It should display lines right after a couple of sec after the video starts.
Please report if specially formatted characters are still display correctly (little bit grayish, thin black border and shadow).
Thanks!
-
Another improvement which isn't listed in the changelog is that (for me at least) the WiFi and Bluetooth settings remain OFF after a restart or switch off :) Can other confirm this?
So if you have wifi ON and restart the player, the wifi is OFF? That's bad.
-
Another improvement which isn't listed in the changelog is that (for me at least) the WiFi and Bluetooth settings remain OFF after a restart or switch off :) Can other confirm this?
So if you have wifi ON and restart the player, the wifi is OFF? That's bad.
As long as you turn off the settings manually then reboot it will remain off rather than enabling itself again
-
Can anyone test if if external .ass (PGS) subtitles work correctly? Here's a test sub: http://www.filedropper.com/assextensionpgssub-test (http://www.filedropper.com/assextensionpgssub-test)
Worked for me, with Wrapper. But Kodi Player did not display them.
The special characters did display, with shadow using the Wrapper.
-
I have several apps that seem to think my Q10 Pro is "jailbroken", mainly apps that stream content. I had hoped the newest build might rectify it, but apparently not! Any way to rectify this without ACTUALLY rooting my box?
-
Another improvement which isn't listed in the changelog is that (for me at least) the WiFi and Bluetooth settings remain OFF after a restart or switch off :) Can other confirm this?
For me is keep off, with clean install and not additional apps installed.
Yes, I want them off, permanently. I have no use for WiFi or Bluetooth on my Q10.
-
@maelor
Try next:
- Do clean install with OFW/CFW v2.1.0/2.1.1 set WiFi/Bluetooth OFF.
- Test if after power OFF/ON and reboot is keep WiFi/Bluetooth OFF.
- Start install your application and never allow application to use location!
- For sure will get WiFi OFF a same like me.
- Location service will always trigger WiFi ON after power OFF/ON or reboot if is was activate.
-
I guess that bug still remained, when you can't actually delete any files from the internal HDD, and you must plug into a PC to run a chkdsk error fixing time-to-time to get back the "stuck" free space on the HDD. Some reported that file deletion doesn't even really work with the stock HiMedia File Manager.
This just makes the internal HDD option totally useless...
Any new found, simpler workarounds for this issue?
-----------------
Joker: Thanks for checking!
-
pcristi -
Everything has been working well since I installed 2.1.1. firmware last week!
I've tried several reboots and switch-offs and, every time, the new 2.1.1 firmware sets both the the WiFi and Bluetooth to OFF by default, which is exactly what I want :).
But HiMedia did not mention anything about this in the 2.1.1 changelog, so:
either - they fixed the problem but forgot to tell us :-\
or - the problem was caused by something else in the system and has now been cleared by the clean build when installing 2.1.1 firmware?
I see your point on 'Location Services'. It was ON, but still the WiFi/Bluetooth remained OFF ??? ?
But, anyway, I've just switched it OFF as I don't need it.
-
So, the Colorspace and Bitdepth options are missing again from the Settings menu. HiMedia doing this on purpose, but won't even send even a tiny bit of information to the customers from the reasons? That's just a so absolutely odd attitude and situation.
I hope the the code: 0 3 5 1 is still working to get them back. Anyone tested it yet?
-
I hope the the code: 0 3 5 1 is still working to get them back. Anyone tested it yet?
Yes, the "Video color space & HDMI deep cplor" cheat-code still works :). The options reappear in the Android menu and remain after a re-boot also.
-
I hope the the code: 0 3 5 1 is still working to get them back. Anyone tested it yet?
Yes, the "Video color space & HDMI deep cplor" cheat-code still works :). The options reappear in the Android menu and remain after a re-boot also.
Thanks for the feedback! And where it must be entered? I mean is there a specific Menu or Options screen where it should be entered (like in the Advanced Settings or at the Home Screen)? Or it's just totally all the same where?
-
Thanks for the feedback! And where it must be entered? I mean is there a specific Menu or Options screen where it should be entered (like in the Advanced Settings or at the Home Screen)? Or it's just totally all the same where?
I just went into the Android Settings > Advance Settings screen and then pressed 0 3 5 1 on the remote control.
-
And how about SD / .avi / Xvid / DivX video compatibility? These had some trouble ("Video problem" error) on some of the very previous FW's, so it will be good to know if they playback properly again...
If this feature will also get a "green pipe", I guess I will finally upgrade from 2.0.6... But I have may "oldies, but goldies" encoded in these SD formats, so any negative feedback would cancel this intention...
-
I hope the the code: 0 3 5 1 is still working to get them back. Anyone tested it yet?
Yes, the "Video color space & HDMI deep cplor" cheat-code still works :). The options reappear in the Android menu and remain after a re-boot also.
Good info. In 2.0.6 all other options (4:4:4 and 4:2:2) were NOT SUPPORTED, and coming back to 4:2:0 8bit.
Do these options now remain set, are compatible?
-
I managed to find one video pal 720x576 mpeg file, it did not display the aspect ratio correctly.
Was it a 16:9 or a 4:3 aspect ratio video?
I guess that the problem in the case of 16:9 / 720x576 pixel videos is that the Player doesn't detect correctly that it's anamorphic and that it should be displayed as 16:9, and rather stickily forces it into the 4:3 aspect ratio display. It should be communicated in details towards HiMedia to get acknowledge regarding the cause of the issue.
But I guess the "trick" to set the Aspect Ratio in the Settings to "Full Screen" still solves this problem, doesn't it?
-
Was it a 16:9 or a 4:3 aspect ratio video?
Good point, the sample file I used was 3742 kb/s, 720*576 (4:3), at 25.000 FPS, MPEG Video (PAL).
It displayed like a window in the middle of the screen, with black bands all around. And yes you can expand to full screen.
-
And how about SD / .avi / Xvid / DivX video compatibility? These had some trouble ("Video problem" error) on some of the very previous FW's, so it will be good to know if they playback properly again...
If this feature will also get a "green pipe", I guess I will finally upgrade from 2.0.6... But I have may "oldies, but goldies" encoded in these SD formats, so any negative feedback would cancel this intention...
someone con feedback this ,please?
im interested too....
-
Was it a 16:9 or a 4:3 aspect ratio video?
Good point, the sample file I used was 3742 kb/s, 720*576 (4:3), at 25.000 FPS, MPEG Video (PAL).
It displayed like a window in the middle of the screen, with black bands all around. And yes you can expand to full screen.
This is the usual problem that HiMedia does not want to solve, already discussed here:
http://www.futeko.com/newforum/index.php?topic=2576.0
-
Good point, the sample file I used was 3742 kb/s, 720*576 (4:3), at 25.000 FPS, MPEG Video (PAL).
It displayed like a window in the middle of the screen, with black bands all around. And yes you can expand to full screen.
[/quote]
The other option is to use Kodi VideoPlayer ("play using") as it seems to be able to handle older SD/DVD rips ok.
This can also be set up in "playercorefactory" settings so that "wrapper" handles all HD files 720p and above and Kodi handles lower resolutions. There were instructions provided in this forum in another thread, some time ago.
-
Was it a 16:9 or a 4:3 aspect ratio video?
Good point, the sample file I used was 3742 kb/s, 720*576 (4:3), at 25.000 FPS, MPEG Video (PAL).
It displayed like a window in the middle of the screen, with black bands all around. And yes you can expand to full screen.
If it was in 4:3 aspect ratio originally, than it may have been displayed correctly. This is how a 4:3 video should look like on a 16:9 display: http://www.taudio.com/tripod_images/graphics/aspectDiagram_2.jpg (http://www.taudio.com/tripod_images/graphics/aspectDiagram_2.jpg) -> If the black borders weren't any thicker or thinner, than it was correct. Was it like this?
And as far as I know, this issue only concerns the 16:9 aspect ratio 720x576 videos.
Edit: It displayed like a window in the middle of the screen, with black bands all around.
->You mean there were also black bars on the top and on the bottom? That's than also incorrect. It should have the bars only on the left and the right sides. (Except if the top-bottom black bars are originally encoded in the video.) :???
-
I hope the the code: 0 3 5 1 is still working to get them back. Anyone tested it yet?
Yes, the "Video color space & HDMI deep cplor" cheat-code still works :). The options reappear in the Android menu and remain after a re-boot also.
Good info. In 2.0.6 all other options (4:4:4 and 4:2:2) were NOT SUPPORTED, and coming back to 4:2:0 8bit.
Do these options now remain set, are compatible?
Any option that is available to me remains set. But most of the options were not available to me as they are dependent on the make/model of the television which the Q10 is connected to.
On my Samsung 4K televison, HDMI UHD is only available of HDMI1 and none of the other HDMI ports. I have my FreeSat box connected to HDMI1 and the Q10 box connected to HDMI2.
My Q10 is set to:
Colorspace - YCbCr444 8Bit (but YCbCr422 is also available)
TV HDR Mode: AUTO
I'm a great believer in leaving everything on AUTO and letting the system work things . Perhaps, in leaving the Colorspace option out of the latest firmware settings HiMedia agree with me?
-
I'm a great believer in leaving everything on AUTO and letting the system work things . Perhaps, in leaving the Colorspace option out of the latest firmware settings HiMedia agree with me?
If it would really work in "auto mode" for all users and for all the different displays they have, also switching every time for the best available Colorspace and bitdepth option for the videos in respect of the previously listed variables, I would agree.
Sadly it's appear to be a bit more complicated. At first, we don't even know yet in what Colorspace and bitdepth will the Player really switch during video playback (and after freque switching). 60 and 50Hz has different Colorspace "sweetpoints" than anything under 50HZ (like 23.976Hz). And there's a huge scatter how different type of TV's and Projectors will perform better PQ concerning the Bitdepth settings (difference that mostly visible in band toning and dithering). Some top-out at 10bit, some can do even better with 12bit and some still "prefer" more the 8bit input (and in many cases also regardless of the TV's bitdepth specification). That's why we need these settings and to be able to experiment with them, to find the best setting suitable for our display, mostly because the uncertainty regarding of the Players real operation described in the presumptions detailed under:
So there are no common "safe-to-say" settings that would result in the best possible PQ in every cases and for every one.
Presuming the "best case" : For every video under 50Hz the Player would switch either to 422 (to avoid 444 incompatibility with many displays not capable) and keep the bitdepth setting as it was.
In the lamer cases: It will switch to 420 and also change / reduce the bitdepth from what is originally configured in the settings.
-
Edit: It displayed like a window in the middle of the screen, with black bands all around.
->You mean there were also black bars on the top and on the bottom? That's than also incorrect. It should have the bars only on the left and the right sides. (Except if the top-bottom black bars are originally encoded in the video.) :???
Yes, there were black bars on the top and bottom & black bars on the left and right.
-
Edit: It displayed like a window in the middle of the screen, with black bands all around.
->You mean there were also black bars on the top and on the bottom? That's than also incorrect. It should have the bars only on the left and the right sides. (Except if the top-bottom black bars are originally encoded in the video.) :???
Yes, there were black bars on the top and bottom & black bars on the left and right.
Are you sure, that the bars were not encoded in the video? Than it appears to be a new bug again. So far it only concerned the 16:9 videos. On 2.0.6 at least the bug with 16:9 SD PAL video is already present, but with 4:3 aspect ratio videos it's still working fine. But still needs reassurance, so I will update later with some samples for anyone who would like to test it.
-
-
Here's a pack (https://ufile.io/dwedl), with 2 video samples included for testing the SD video compatibility and the 4:3 aspect ratio.
Thanks!
-
Here's a pack (https://ufile.io/dwedl), with 2 video samples included for testing the SD video compatibility and the 4:3 aspect ratio.
Thanks!
Yes both videos played correctly with black bars on the left & right, as you would expect in 4:3 aspect ratio. There is no difference between the Kodi player and the wrapper when displaying these videos.
If anyone has a sample 16:9 720x576 Video file I can test that also.
-
Okay, managed to find some sample 720*576 (16:9) at 25.000 FPS, MPEG Video (PAL).
In Kodi they played correctly with full screen video, with the wrapper they displayed in the 4:3 aspect ratio (black bands left & right).
-
[Any option that is available to me remains set. But most of the options were not available to me as they are dependent on the make/model of the television which the Q10 is connected to.
On my Samsung 4K televison, HDMI UHD is only available of HDMI1 and none of the other HDMI ports. I have my FreeSat box connected to HDMI1 and the Q10 box connected to HDMI2.
My Q10 is set to:
Colorspace - YCbCr444 8Bit (but YCbCr422 is also available)
TV HDR Mode: AUTO
I'm a great believer in leaving everything on AUTO and letting the system work things . Perhaps, in leaving the Colorspace option out of the latest firmware settings HiMedia agree with me?
Thank you for your answer. I think I managed to step a little further: under DISPLAY I setup playback at 2160p-30Hz (instead of 2160p-60Hz 4:2:0-8bit, as until now) and I could set colorspace at 4:4:4-8bit, which makes me happy. My TV set is a 4k panasonic TX-50DXU701 and all the HDR it can do is 8bit.
Any further advice, pat on the shoulder or light kick in the but is friendly appreciated.
Cheers everybody.
-
[Any option that is available to me remains set. But most of the options were not available to me as they are dependent on the make/model of the television which the Q10 is connected to.
On my Samsung 4K televison, HDMI UHD is only available of HDMI1 and none of the other HDMI ports. I have my FreeSat box connected to HDMI1 and the Q10 box connected to HDMI2.
My Q10 is set to:
Colorspace - YCbCr444 8Bit (but YCbCr422 is also available)
TV HDR Mode: AUTO
I'm a great believer in leaving everything on AUTO and letting the system work things . Perhaps, in leaving the Colorspace option out of the latest firmware settings HiMedia agree with me?
Thank you for your answer. I think I managed to step a little further: under DISPLAY I setup playback at 2160p-30Hz (instead of 2160p-60Hz 4:2:0-8bit, as until now) and I could set colorspace at 4:4:4-8bit, which makes me happy. My TV set is a 4k panasonic TX-50DXU701 and all the HDR it can do is 8bit.
Any further advice, pat on the shoulder or light kick in the but is friendly appreciated.
Cheers everybody.
I think if the TV is capable to accept HDR signal, than it's capable of 10bit also. Set back to 60Hz and check somehow (with your AVR's or TV's info button) that after you start a 23.976fps / 4K / HDR video, during playback what colorspace ond bitdepth input is proceeding.
As I've wrote before in the better case the Player will auto switch and you will get 422 and 10bit input as it is possible on 10bit for anything under 50Hz on 4K.
It's a very strange way and "workaround" to keep the GUI at 30Hz all the time, I wouldn't recommend it. The GUI supposed to set to 60Hz as it's far more natural and smooth for the eyes.
Also you can still report back here if you've got different result with the GUI set to 60Hz vs. 30Hz.
-
Somehow I think when one set the display as 2160P 60Hz, it is for all playback, not only the GUI (menu).
I had it so far set 2160P 60Hz, an averythign like 4:4:4: or 4:2:2: was "SELECTED IS NOT SUPPORTSET TO BACK"... that is YCbCr420 8bit.
If I set display like I said before at 2180P 30 HZ, I can select 4:4:4:-8bit, at 10 bit is agan "bla-bla-not support, reverting ti 420-8bit.
Not 10 bit for me, also the tv manual says only 8 bit HDR. NOT 10 bit HDR
So, I think that this setting has to do with MORE than just GUI/interface/menu...
I do not have means and other intermediary devices to esteblish colorspace during playback.
Just on png image that supposedly shows good color and written detail like it were for 4:4:4: 10 bit, but definitely it is not, according to tv's documentation.
Looking forward for more suggestions.
-
Check if your intend settings is fit HDMI 2.0a standard
(http://2ley7l42nt9s3jvzio2zneqa.wpengine.netdna-cdn.com/wp-content/uploads/2014/07/HDMI-org-chart.jpg)
-
Somehow I think when one set the display as 2160P 60Hz, it is for all playback, not only the GUI (menu).
I had it so far set 2160P 60Hz, an averythign like 4:4:4: or 4:2:2: was "SELECTED IS NOT SUPPORTSET TO BACK"... that is YCbCr420 8bit.
If I set display like I said before at 2180P 30 HZ, I can select 4:4:4:-8bit, at 10 bit is agan "bla-bla-not support, reverting ti 420-8bit.
Not 10 bit for me, also the tv manual says only 8 bit HDR. NOT 10 bit HDR
So, I think that this setting has to do with MORE than just GUI/interface/menu...
I do not have means and other intermediary devices to esteblish colorspace during playback.
Just on png image that supposedly shows good color and written detail like it were for 4:4:4: 10 bit, but definitely it is not, according to tv's documentation.
Looking forward for more suggestions.
No, the Player will auto switch the output frequency according to the video source, that's what "24p mode" supposed to do, when it's turned on in the Playback menu. So in the case of 23.976fps video it will auto switch from 60Hz to 23.976Hz and -presuming the best case- from 420 to a 422 colorspace during playback. That's why it would make the whole "set the GUI to 30Hz for higher colorspace" concept needless. So revise my suggestions and presumptions above according to this. It's a bit still strange you can't set 444 on 60Hz with 8bit, maybe it's also because fall-back compatibility regulation reasons (I've mentioned these above), as some displays won't support it. 422 on 60Hz just isn't on supported by HDMI 2.0 specifications (http://blog.toonormal.com/2014/01/10/4k-hdmi-and-deep-color/), so that would be impossible with any setup. But on 4K / 60Hz / 10bit there's definitely no other choice than 420.
Edit: and like I've mentioned before, we have no clarification yet, that to what colorspace and bitdepth variation will the Player auto-switch during the Playback from various previous GUI settings. It's what one must experiment on by their selfes. It's just a presumption that -also- the best case could happen, and the switching will always result in the highest possible settings variation. In your case, settings from the GUI's 60Hz / 420 / 8bit could also end up in e.g. 23.976Hz / 444 / 8bit during Playback. And even if you set 30Hz / 444 / 8bit for the GUI, it could switch back to 23.976Hz / 422 (or even 420) / 8bit during playback. That's what we still need to clear out, as there's still not so much relevant user info is published since.
Secondly: I still recommend the 10bit option -at least- to try out on whatever colorspace is it still accepted with your TV.
e.g. My TV is a 2014 FHD modell, and it's panel is also only 8bit, but it can accept and "convert" 10bit input. So I can set 1080p / 60Hz / 10bit too for the GUI. Maybe worth to check out on your's too (But still also keep under consideration my previous post regarding TV's bitdepth "favor" and find what's works with the best PQ results for you).
-
The new firmware is also present via OTA, because it is present on the official website.
(https://i.postimg.cc/kMRkXhYs/Ridimensiona-di-Screenshot-001.png)
http://www.himediatech.com/down.aspx?TypeId=11&FId=t14:11:4
-
So, is subtitles skipping problem fixed or not. Only one person said so far the problem is fixed , sort of. Anyone else can confirm further?
What about any other problems (apart from.those already mentioned)? Anyone else already updated can give feedback whether this is the recommended firmware.
-
A couple of other users reported on another Forum that the sub skipping bug is fixed and they didn't detected any other bugs so far.
-
Thanks for your help guyz.
1. The subtitle bug NOT present in 2.1.1 CFW after two days of watching. I will report back if I find otherwise.
2. HOW can I check what colorspace playback is my TV receiving during a movie? Is there any tool for that, the TV info button gives only resolution and frequency?
Cheers.
-
You can check colorspace and bitdepth output info with this tool linked in this post: Link (http://www.futeko.com/newforum/index.php?topic=3226.msg24223#msg24223)
Here's a descript to what mods must made in the .bat file to get out the info and under the values you need to check out: Link (http://www.futeko.com/newforum/index.php?topic=3226.msg24226#msg24226)
-
Ok, since this FW is given positive feedback, I intend to finally update from 2.08.
But I don't want to lose anything. Want to retain all my app without reinstalling. Is it ok for me to update from the settings update option instead of doing the pin method?
-
Is it ok for me to update from the settings update option instead of doing the pin method?
Yes, probably.
You won't cause any serious problems, possibly some instability in certain apps depending on what/how you have installed but if it so you can fix it with a clean install of 2.1.1.
-
Ok, since this FW is given positive feedback, I intend to finally update from 2.09.
But I don't want to lose anything. Want to retain all my app without reinstalling. Is it ok for me to update from the settings update option instead of doing the pin method?
updated with settings option, 2.1.0->2.1.1, like i usually do.
all is good, all is maintained.
haven't noticed any sub skipping so far.
-
The new firmware is also present via OTA, because it is present on the official website.
(https://i.postimg.cc/kMRkXhYs/Ridimensiona-di-Screenshot-001.png)
http://www.himediatech.com/down.aspx?TypeId=11&FId=t14:11:4
No OTA here?
-
Thanks to all of you who have answered my questions. I will update to this latest fw then.
-
You can check colorspace and bitdepth output info with this tool linked in this post: Link (http://www.futeko.com/newforum/index.php?topic=3226.msg24223#msg24223)
Here's a descript to what mods must made in the .bat file to get out the info and under the values you need to check out: Link (http://www.futeko.com/newforum/index.php?topic=3226.msg24226#msg24226)
THANK YOU,
I will give these a thorough read
My TV, the panasonic TX-xxDXU701, has ony 8bit HDR by manufacturing, but bright phosphors and good lighting plus processing engine which gives good HDR experience, at least acceptable. It was the tradeoff for the existing money. (if interested, a revies of the seris, comparable with mine: https://www.trustedreviews.com/reviews/panasonic-tx-50dx750 ).
As to Pcristi's post with the HDMI2.0 standards, I see only RGB settings in there, not YCbCr ones, and I do not understand them...
I will be back when I will know more.
Cheers.
-
Ok, since this FW is given positive feedback, I intend to finally update from 2.09.
But I don't want to lose anything. Want to retain all my app without reinstalling. Is it ok for me to update from the settings update option instead of doing the pin method?
updated with settings option, 2.1.0->2.1.1, like i usually do.
all is good, all is maintained.
Not for me!
Just upgraded and its wiped everything.
-
Furthermore, the update downloaded direct from the Himedia page says 2.1.1 but is actually 2.0.9.
So I have lost everything for nothing.
Thanks for nothing!
-
So, is subtitles skipping problem fixed or not. Only one person said so far the problem is fixed , sort of. Anyone else can confirm further?
So the subtitle bug with srt lines is NOT solved! All other subtitle formats as pgs or ass are skipping, srt (dvd embedded) does not!
I`m desperating :-\
-
I updated my Q10 to 2.0.6 successfully last year. I now tried updating to 2.1.1. and get the following error screen while booting:
https://1.bp.blogspot.com/-YYJHLWTkM64/UOOJ827PHwI/AAAAAAAAPvY/oyzPZeILHvk/s1600/Android+error+498.jpg
It indicates that the cache is full?! I checked the storage of the device and I only use about 700mb of 12gb. I tried applying the update with multiple different USB sticks. Can someone point me in the right direction so I can apply the update?
Thx in advance.
-
So, is subtitles skipping problem fixed or not. Only one person said so far the problem is fixed , sort of. Anyone else can confirm further?
So the subtitle bug with srt lines is NOT solved! All other subtitle formats as pgs or ass are skipping, srt (dvd embedded) does not!
I`m desperating :-\
I have just tested with all the above formats EXT and EMB and no skipping occurred at all.
Can you link the subs you tested?
-
Ok, since this FW is given positive feedback, I intend to finally update from 2.09.
But I don't want to lose anything. Want to retain all my app without reinstalling. Is it ok for me to update from the settings update option instead of doing the pin method?
updated with settings option, 2.1.0->2.1.1, like i usually do.
all is good, all is maintained.
Not for me!
Just upgraded and its wiped everything.
err... think u misunderstood.
i meant use settings option with usb local, firmware from futeko here.
not pin restore, not OTA download.
-
Ok, since this FW is given positive feedback, I intend to finally update from 2.09.
But I don't want to lose anything. Want to retain all my app without reinstalling. Is it ok for me to update from the settings update option instead of doing the pin method?
updated with settings option, 2.1.0->2.1.1, like i usually do.
all is good, all is maintained.
Not for me!
Just upgraded and its wiped everything.
I was the one who asked about updating from settings, so as not to lose any of my apps.
Since then (before your reply) I have already updated from settings and everything went smoothly, all my apps are intact.
The way I update is as follows:-
1. Download the FW 2.1.1
2. Unzip the file (you will get another file called update.zip)
3. Copy the file "update.zip" to the root of fat32 USB drive.
4. Insert the USB into Q10 pro and fresh boot (just to be sure)
5. Go to settings, choose the "upgrade" icon
6. Select "local upgrade"
7. It will take a few minutes to upgrade and reboot, so be patient.
8. The first time it reboot, it will take longer than usual to reach the main screen.
-
As I mentioned, I downloaded the file directly from the Himedia website, put the file on the root of a drive, chose "local upgrade", selected the file, update process completed and it wiped everything and was 2.0.9. I even re-downloaded the file and it was the same result. I have had to do a complete reset reinstall to get working again.
-
If you are using European model, you should download from Futeko website here, not Himedia website.
-
samba server doesn't work
-
samba server doesn't work
All HiMedia Android 7 FW has a same samba server version and for me working well. Probably your's problems is somewhere else then in HiMedia FW.
-
The new firmware is also present via OTA, because it is present on the official website.
(https://i.postimg.cc/kMRkXhYs/Ridimensiona-di-Screenshot-001.png)
http://www.himediatech.com/down.aspx?TypeId=11&FId=t14:11:4
No OTA here?
Can't see that option either
-
samba server doesn't work
All HiMedia Android 7 FW has a same samba server version and for me working well. Probably your's problems is somewhere else then in HiMedia FW.
Hi, may I know why Q10 Pro Media Center LAN can't acess another media player hard drives and files (connected wirelessly using Samba), even though I can see the drives sda1, sda2 etc. When I click on them I get error which says no such files or folders.
However when I use Q10 pro ES file explorer LAN , I can see the drives and open the files from the other media player.
-
Updated from 2.0.8 2018-04-03 to 2.1.1 2018-12-24
As a consequence App permissions is no longer accessible because it keeps saying: "package installer keeps stopping" and WiFi keeps getting reenabled after a restart (I never use it).
After downgrading the problems goes away.
I even tried a factory reset and downgrading to Android 5.1, and then upgrading again to Android 7 - 2.0.8 2018-04-03. It works fine. And then trying 2.1.1 2018-12-24 again - voila! - the "package installer keeps stopping", when trying to enter App permissions, reappears and nothing can be done except downgrading.
I put it to HiMedia that something is seriously wrong with this update. Anyone?
-
Is was popup by users on android-mediaplayer.de forum and reported to HiMedia.
As workaround copy update.zip/system/priv-app/PackageInstaller/PackageInstaller.apk from FW v2.0.8 via adb shell/ExplorerRoot to box running FW v2.1.1 or go to CFW.
-
-
-
-
I had been making a script in the same thread for the past few days. Just install it via ADB.
Here is a Batch Script (https://www.androidfilehost.com/?fid=11410963190603898084)
- Extract
- Start PI_Fix.bat
- Enter IP address
- and rejoice
-
-
-
-
I'm afraid you have a completely wrong thinking. If you choose an Android-based device, you should be willing to fix the bugs yourself. Even if it is based on the community. Because, an Android device never runs very well. Especially with the China Floundern here not much is tested. One sees again and again at the Firmwares which are published here by Himedia. The FWs grows with the customer. Unfortunately this is the case everywhere.
If you want a working system, never buy an Android device. Then you'd better go to Apple, they patch their mistakes quite promptly. At Himedia you sometimes have to wait several months or even years. Or forever.
See analogously the security status of January 2017!! Means, more or less we get the same FW-status since 2 years! Except for a few apps that will be recompiled, like the PackageInstaller last time. A lot has changed, I had taken them apart, but not tested them, see above.
-
If all companies that "build" mediaboxes don't wake up the new FireTV 4k will eat all of them.
-
There has always been a choice between more mainstream devices with their associated DRM and other restrictions and the media player products we have sold. This isn't going to change. AppleTV 4 will not 'eat' the products we sell because Apple don't want it to, they want AppleTV users to buy into and use exclusively Apple subscription content.
-
Apple TV costs X while FIRETV costs X-Y. :-)
-
-
The reason i only use mx player is simply because it gives me the least frustrations, i started like so many with the intention of using it fully.
if you are happy using the rather basic MX Player software, have you tried using the built-in high quality MediaCenter player?
If you just want to find a video or audio (or .iso) file and play it back, this should be fine for your purpose.
-
-
720x576 is aspect ratio(AR) 4:3 are play correct according that.
720x576 with AR 4:3 with screen aspect ratio(SAR) 16:9 are a problematic once.
HiMedia doesn't have any firmware witch handle correctly 720x576 AR 4:3 with SAR 16:9, a older FW is was just more convenient playing all 720x576 as output detect(set) 16:9/4:3.
Kodi with build in player(VideoPlayer) claim to do this according they settings.
-
-
Has anyone checked whether packageinstaller can be simply replaced with a "working" one in the 2.11 update?
Yes take from FW v2.0.8 and copy with RootExplorer if box is rooted or use batch file done by @hanspampel to do via adb shell.
http://www.futeko.com/newforum/index.php?topic=3994.msg27510#msg27510
-
Today I update to the latest firmware, OFFICIAL Q10 PRO 2.1.1
Is it no longer an option to do video depth settings (8 bits & 10 bit settings) in the advance option on firmware 2.1.1 ?.. there is only TV HDR Mode setting on the advance option.. is it only me who experiences this?
I do an update by pressing the reset button on the back of the box.
Thank you
-
-
Today I update to the latest firmware, OFFICIAL Q10 PRO 2.1.1
Is it no longer an option to do video depth settings (8 bits & 10 bit settings) in the advance option on firmware 2.1.1 ?.. there is only TV HDR Mode setting on the advance option.. is it only me who experiences this?
I do an update by pressing the reset button on the back of the box.
Thank you
Solution here: http://www.futeko.com/newforum/index.php?topic=3726.msg25949#msg25949
-
Solution here: http://www.futeko.com/newforum/index.php?topic=3726.msg25949#msg25949
Thank you Futeko
-
-
The fourcc for the .avi needs changing to xvid from divx. They are essentially the same but divx is a trademark and hence is not officially supported.
https://www.fourcc.org/changer/
https://www.tweaking4all.com/home-theatre/fourcc-changer/
-
The fourcc for the .avi needs changing to xvid from divx. They are essentially the same but divx is a trademark and hence is not officially supported.
https://www.fourcc.org/changer/
https://www.tweaking4all.com/home-theatre/fourcc-changer/
many thanks....ill try!
but ,futeko, before 2.0.6 everythings work well....also this files....! why?
-
When will the Q10 pro DTS-HD HRA be able to output in 7.1 correctly? Other players with the same setup can do that (like Dune 3d or Zappiti 4k HDR).
-
Is Kodi 18.1 can output 5.1 in True HD and DTS dolby digital with this firmware?
-
When will the Q10 pro DTS-HD HRA be able to output in 7.1 correctly? Other players with the same setup can do that (like Dune 3d or Zappiti 4k HDR).
I have tested DTS-MA and DTS-HD-HRA and they are both identified and play 7.1 channels correctly through my amp with the wrapper.
-
When will the Q10 pro DTS-HD HRA be able to output in 7.1 correctly? Other players with the same setup can do that (like Dune 3d or Zappiti 4k HDR).
DTS-HD HRA has worked fine with many firmware updates for a few years. It is likely an issue with your amplifier model (perhaps a Denon?) if you are unable to play correctly.
There have been previous mentions in other threads here with other amplifiers, including Yamaha and Marantz, where the audio passes through correctly and plays fine.
-
Hi Phil181,
i have a Denon AVR-X3300W and i know the discussion about Denon. But why is Himedia Q10 Pro the only one that have problems with my setup. Other players like Dune HD Base 3D, or Zappiti 4k One SE HDR bring the sound correctly to the amplifier. So i think it's not a Denon problem. It would be nice if something would happen there.
-
-
I have the Denon AVR-X 6200W and Have the most up-to-date FW and have zero problems with DTS-HDRA tracks.
-
Here -> https://thedigitaltheater.com/dts-trailers/ (https://thedigitaltheater.com/dts-trailers/) you can tested a many audio formats. all works fine with Q10 Pro, but only DTS-HD HR and DTS:X brings low noise with audio setup HBR to RAW 7.1. If i change HBR to 5.1 i got clear sound but only the DTS Core from audio stream.
-
Yes, they were some of the ones I tried. They all worked for me, have you applied the latest firmware. I believe they did release an update for your model, something about DTS:X update.
-
Installed the new firmware , and then somehow, google play store automatically upgraded Kodi to the new Kodi Leia.
Issue is , its not working with the Wrapper .
Do I need to again install the wrapper ?
Is it ok to run Kodi Leia on Q10 Pro ?
If I have to revert the earlier version of Kodi, then how to go about it and which is the best Kodi Version to use .
-
Installed the new firmware , and then somehow, google play store automatically upgraded Kodi to the new Kodi Leia.
Issue is , its not working with the Wrapper .
Do I need to again install the wrapper ?
Is it ok to run Kodi Leia on Q10 Pro ?
If I have to revert the earlier version of Kodi, then how to go about it and which is the best Kodi Version to use .
The newest KOID 18 version seems to be stable now to use it with Wrapper. You may need to reactivate the Wrapper (see FAQ thread).
-
Good morning
I ask if it is still valid with FW 2.1.1, restore old player (FW 2.0.4) for the 720x576 aspect ratio problem.
https://www.futeko.com/newforum/index.php?topic=2576.msg21706#msg21706
Bug never solved.
Thank you