Hello.
Sorry to bother you. But you seem to know everything:)
I need help with my x4q pro and the sound problems it has. I have started a post in the forum you could read. Have you ever heard of that problem or know what i could do to solve it?
/Micke
Hi again. i have now upploaded log and all info
Could you share it one more time, please?
could you provide it once again? thanks
I was too slow My bad. Once again?
Hello,
I have now bought the Ugoos X4Q Extra and installed the CoreELEC-Amlogic-ng.arm-21.1.1-Omega-Generic.img.gz image on the micro SD card. Everything is actually running very well and I would like to say a big thank you for the great work!
I just noticed some oddity:
If the box was without power (individually switchable power strip), then I give it power and it starts, there are three problems:
- LAN/Ethernet doesnât work. In the CoreELEC settings, the slider for the LAN is deactivated. If I try to activate it, it jumps back straight away and it cannot be activated (WiFi I could activate, but I donât use this).
- If I then turn the box off, it restarts automatically! (By the way: Then the LAN works again too!) However, it only does this automatic restart, if it was previously without power. If I turn it off again, it stays off. I just canât take the power off, otherwise the game starts all over againâŚ
It doesnât matter how I turn the box off, I use two remote controls, the original one that I got to work with the remote.conf from the Ugoos UR-01. And then I have a USB Bluetooth remote control connected. Or I go to turn off via the CoreELEC menu (the power plug symbol). In all cases, it restarts when it is turned on for the first time after it was previously without power. - (Under Settings â System â CoreELEC â Use Player LED is deactivated (I had activated it before!). But then files with Dolby Vision are only output in RGB 8 bit, BT.709. I have to activate it again, then I have 12 bit, YUV422 and BT.2020nc.)
Edit: Okay, as I now think I know, deactivating âUse Player LEDâ is probably the better setting. Dolby Vision is complicated! So letâs ignore point 3 for now.
I donât know this behavior from other boxes (e.g. X96 max plus).
Previous workaround: leave the box plugged in as much as possible!
I used this as the device tree: sc2_s905x4_ugoos_x4.dtb
After I noticed these things, I reinstalled everything, but again with the same result.
One thing that I donât know, if it could play a role: The box initially had an Android with the firmware number 1.1.8 installed. And I didnât even bother with it at first, I wanted to have as little to do with Android as possible.
Only afterwards (after the second reinstallation of CoreELEC) did I check and update the firmware to the current 1.2.4.
The behavior described above has not changed. The only question is, can it play a role that I only updated the firmware AFTER the CoreELEC installation?
Another small thing on the side:
The LED on the box lights up white when in use. When you turn the box off, the LED still lights up white, just with a very slight green tint. But you have to look closely to see the difference. The easiest way to see that there is actually a slight color change is to watch the LED when it is turned off.
But the box can also light up green and red, which is what it shows when it is started up. It first lights up red briefly, then green, and then changes to white.
I think it would be clearer if it were to light up red when it is turned off (my LG TV also lights up red in standby). Or it would actually be even better if the LED were off completely. Also because it is quite intrusively bright.
If I turn it off completely from Android, the LED also goes off completely (but there you can also set the LED to how or whether it should light up in standby, for example).
Most of this translation was done using Google, so please forgive me if some things are not perfect!
Could anyone who has the Ugoos X4Q Extra check whether they have the same two problems?
Itâs actually quite easy to do: just unplug the device for a few seconds and see if there is an Ethernet connection afterwards (when starting it for the first time). Then shut down/turn off the device and see, if it reboots instead.
That would be nice, because then I would know whether itâs somehow related to my device (perhaps it played a role that I installed CoreELEC first and then updated the Android firmware, or the box is just broken) or whether itâs a general bug related to CoreELEC and the box.