Ugoos X4Q Extra: No Ethernet connection after starting after it was without power and then shutting down = reboot

Help & Support Ugoos
1

Although the CoreELEC otherwise runs great, my Ugoos X4Q Extra unfortunately has a few small errors, reproducible. But I don’t know, if that could be due to my box or if it is due to CoreELEC.

The box was previously updated to the latest Android 1.2.4. (But it was also tried with the original Android version 1.1.8, with the same result. So it can’t be due to an “incorrect” installation of Android.)

I tried it with two micro SD cards:

Installation 1:
Sandisk, A1, Class10, 16 GB: CoreELEC-Amlogic-ng.arm-21.1.1-Omega_nightly_20241206-Generic.img.gz + subsequent update in the device via the update function to Omega 21.2

Installation 2:
Sandisk, A1, Class10, 64 GB (purchased brand new): CoreELEC-Amlogic-ng.arm-21.2-Omega-Generic.img.gz

The flashing was triggered using the toothpick method.

Device tree used: sc2_s905x4_ugoos_x4.dtb → renamed to dtb.img and copied to the root directory of coreeelec.

Installation 2 in particular is a pure test installation in which I have not changed anything.
I simply approved the few queries at the beginning (system language, SAMBA, etc.) and then switched on logging and then shut down the system.

By the way: Immediately after installation (the box was previously without power and was then flashed using a toothpick and switching on the power) the network connection was there and activated!).

Error description:

  1. Error:
    After the first boot, AFTER THE BOX HAS BEEN DISCONNECTED FROM THE POWER, the Ethernet connection is deactivated and cannot be activated. Only after another reboot (without disconnecting it from the power) is the Ethernet connection there and activated.
  2. Error:
    After the first boot, AFTER THE BOX HAS BEEN DISCONNECTED FROM THE POWER, it won’t shut down, but instead reboots. It doesn’t matter whether I turn the box off with the corresponding button on a USB Bluetooth remote control or the original remote control or via the menu (-> Shut down).
  3. Error:
    The LED light on the box remains white after shutting down. If you look closely, you can see that the white has a very slight green tint, but you have to look closely, ideally watching the transition when it’s turned off. If you don’t have a direct before/after comparison, it just looks white and you think the box is still on!
    When you start the box, however, you can see how the LED briefly turns red, then green (real green!) and then white. The LED can therefore display both a real red and a real green.
    On Android, it also turns red in standby and goes out completely when shutting down. Couldn’t you set it up like that under CoreELEC? Either red or, best of all, just off completely when you shut down the box.

I activated debug logging during installation 2, as described here:

Then I shut down the system and unplugged the box for a few seconds. Then plugged it back in.

Now I wanted to upload the debug log (Settings > CoreELEC > System > Submit Log > Upload latest Kodi log).

But not entirely surprisingly, an error message came up:

Failed to paste log files, try again.

As described, the box had no Ethernet connection after power was turned off!

Now I shut down the box to generate the second error (reboot instead of shutdown).
As expected, this reboot actually happened (although I actually just wanted to turn the box off) and then I tried uploading the debug log again and this time it worked:

https://paste.coreelec.org/RalphPickle

I wonder if the error with the missing Ethernet connection before the last reboot can still be seen in this log?

But I also found two log files in storage/.kodi/temp (or something similar) that I will also try to attach here (I am not shown whether the upload was successful or whether it is attached.).

One of them is called kodi.old.log, which could possibly be the first log file when I had no Ethernet after the first reboot (after power off).

kodi.log (104,6 KB)
kodi.old.log (121,9 KB)

2

In CoreELEC HDMI CeC is enabled by default

Disable this in CoreELEC and your TV settings

See if results are different

3

This I have in installation 1 (which I use) completely deactivated everything in the TV and in the CoreELEC settings, but the behavior mentioned remains.

4

Ok
I reread your post again ,couple of times

Last year i seriously considered this Box for its Dolby Vision capabilities, in the End went with the Kinhank g1 .

Losing the ethernet connection after/sleep/reboot/powerdown/shutdown seems odd .
When you have success with boot
Go to system/settings /CoreELEC settings/Connection
Does it show wired connected?
And below wifi is idle?
Or shows wifi ready?
If shows wifi ready,then click on and disable
This will stabilizes the ethernet connection.
Not sure if will solve issue after power down

Log shows you are testing 21.2 NG 4.9 kernel

Switch to / test the NE 5.4.210 kernel
Also NO 5.15.119 kernel

Compare results

5

No, not if it is the first boot after it has been powerless.
If I try to set the slider for Ethernet to Active, it immediately jumps back.
The next time I reboot (without powering off in between), Ethernet is shown immediately active again (and it works). It is always active after booting, just not the first time I boot after it has been powerless.

By the way: The WiFi entry is located first above the Ethernet entry.
WiFi is apparently not affected by this power outage!

If WiFi was previously set to active, it will be active again immediately after a restart (after power outage).

But in my installation 1 I have deactivated WiFi in general, but unfortunately that doesn’t help either.

But I read here:

The s905x4 needs to be running CE-NG to use this dovi.ko for DV FEL playback. DV FEL is NOT supported in CE-NE.

So maybe this is not such a good idea?

PS: Thanks for your effort!

6

Testing NG is only if you want/ need FEL Profile 7 playback.

NE kernel you will have Dolby Vision Support, just not FEL profile 7

Same with NO kernel when you add the dovi.ko file.
Just not FEL profile 7

Something else was thinking
Maybe there is no dedicated DTB for the Extra
Just Ugoos X4Q DTB

Try using generic DTB Sc2 s905x4 4g
Instead of the Ugoos X4Q DTB

Originally this Box was to be used on NE 5.4.210 kernel

It was/is added bonus you can test NG kernel for FEL profile 7

So go ahead and test the other branches/kernels
Can not hurt anything

7

What do you mean by wifi on top?
Ethernet on the Bottom?
Slider for wifi?

You are in Android Settings?

I posted about Settings in CoreELEC System
CoreELEC settings
Move down to
Connections
There you will see
Online/Ready/idle

Network Connection

There is no slider
You click on and Select Action
Like Disconnect

8

Sorry, I was in the wrong place!

I read it a bit too superficially, because I thought I knew which place you meant…

There is nothing under Connections, the field is just completely empty (assuming WiFi is deactivated, otherwise there are a number of WiFi networks there).

I was under System/CoreELEC/Network.
The first entry at the top is: Wireless Networks, Active (<- is always there, even if it is inactive!)
The second is: Wired Networks, Active (<- ditto)
Behind both there is a small slider that you can use to activate/deactivate the network.
The slider for Wired Networks is set to deactivated (after restarting, if there was no power beforehand). When I try to activate it, it immediately jumps back again.
And that also matches the empty window for Connections, because if all networks are deactivated, there is nothing there.

Tried with other device-tree:
I was already thinking about trying the sc2_s905x4_4g_1gbit.dtb device tree. But I had read somewhere that USB wouldn’t work with it.
I can now confirm this after trying it.
So I couldn’t operate the device after restarting, because the USB remote control didn’t work and I hadn’t placed a remote.conf for the original remote control. And because I didn’t have a network connection, I obviously couldn’t connect via SAMBA.
But I could still see that the error that there was no Ethernet connection after the first start without power also existed with this device tree. I noticed this because a completely wrong time was displayed in Kodi and I could see in my router that the box wasn’t connected.
I couldn’t check whether the second error (forced reboot instead of poweroff after restarting without power) had also occurred, because I couldn’t shut down the device, because I didn’t have a remote control.

Then I tried it with the CoreELEC-Amlogic-ne.aarch64-21.2-Omega-Generic.img.gz and device-tree sc2_s905x4_ugoos_x4.dtb:

Errors no. 1 and 2 do not exist there!

The box starts after it has been disconnected from the power supply and has direct Ethernet. And then you can simply switch it off cleanly without it doing a forced reboot.

But:
When I start the box with the NE image, I always get this message first:

Android Dolby Vision kernel module is not compatible
No dolby vision media playback possible!

Please upgrade Android firmware of your device to minimum Linux kernel version 5.4.210.
Dolby Vision will be displayed in HDR instead Dolby Vision until the firmware will fulfill the minimum requirements.

I have Android 1.2.4 on the box, which according to the information in Android uses a Linux kernel 5.4.125, a newer version is not offered to me when searching for updates. (Originally 1.1.8 was installed and I was then able to download several updates one after the other until I got to 1.2.4.)
I put the dovi.ko in the root directory of the coreELEC partition again, as before.

That doesn’t make any sense to me either, since I bought the Ugoos specifically because of the Dolby Vision support.
But I don’t really know much about DV and don’t know whether my files (which I don’t want to comment on here!) even have this Profile 7 (FEL 7).
But it seems that DV doesn’t work at all, only HDR(10).

Then I tried the image CoreELEC-Amlogic-no.aarch64-22.0-Piers_nightly_20250124-Generic.img.gz, with the same result:

  • The above error message due to Dolby Vision
  • Errors 1 and 2 do not exist.
  • I also noticed that the LED on the device with the NO image always lights up green, regardless of whether the device is on or off.
9

Ok
You are progress/success

Navigation

I have Logitech K400+ wireless keyboard with usb dongle that i use.
Try to find/use something similar
Wireless Mouse
Even an old wired mouse
Then after can add remote config/pair Blutooth control etc…

Network slider

There is no reason to touch anything there
Just leave as default settings
Both Enabled

Moving forward stay with NO kernel 5.15.137
It is the Future!!!

Dovi.ko

NG Branch is a different. ko
Than NO Branch .ko

So make sure you have the correct dovi.ko fo NEW ORDER 22 Piers

After success than can go back and Test NG Branch on a separate/SD Card USB Drive etc.
You also can Test NE Branch ,it is also EOL and is there you have issues with Android Kernel
So just ignore NE

10

But that’s no use, if the USB interface is dead.
But that was only the case with the “general” S905X4 device tree.
Otherwise I would also have a small USB keyboard here, but that didn’t work well for me.
I would prefer a remote control.
But I think, that’s not the problem in this case.
(In general, I’m already looking for a decent USB remote control, but that’s another story…)

No, you misunderstood that. My English is bad too, maybe it got lost in the translation somehow, what I meant! The “default setting” after starting, after it has been without power, is, that the slider is set to DISABLED for Wired Networks.
But that’s wrong. It’s supposed to be activated. So I tried to switch it to Activated, but that doesn’t work.
After another reboot (without it having been without power in between), Wired Networks is activated again (and of course I’ll leave it like that!).

I only had a quick look, but I really liked the colors of the OSD!

I didn’t know, that there are different dovi.ko for the different CoreELEC versions (ng, ne, no).
Where can I find them, e.g. for no (and the Ugoos X4Q Extra)?
I only know the link that is included here in the explanations for the NG image:

And then I would still have the problem, that I can’t play Dolby Vision Profile 7 (FEL 7) with the NO image (if my files even support it)? Or would it work with the right dovi.ko?

11

No FEL in any -no images.

12

Network slider

I dont know why you are changing settings in Network???

As posted before i never touch/change anything in Network
I leave both active
All other settings as default

The idea is to get your Box up n running on NO kernel 5.15.137 with Dolby Vision Working

Then with separate media
Go back to NG kernel to test

13

Counter question: What would you do, if you didn’t have an Ethernet connection and then saw under System/CoreELEC/Network/Wired Networks, that the slider was set to Deactivated?

Wouldn’t you also think, ‘okay, that’s wrong’ and then try to activate it?

(Assuming you were using wired network at all and not wireless.)

But then it can’t be activated anyway. So you could also say: I didn’t change anything. I just looked and found that the wired network is deactivated there AFTER BOOTING AFTER THE DEVICE WAS DISCONNECTED FROM THE POWER.

I don’t know what you mean. The NO image doesn’t run with Dolby Vision (see my description above; and I haven’t found an extra dovi.ko for the NO image. But even if it did, Profile 7 probably wouldn’t work.).
Then, what do you mean by “Then with separate media”?
And what should I test again after I’ve gone back to the NG image?

To be honest, I don’t want to spend ages jumping back and forth between images. I’d also like to watch a few films in peace! :wink:

I think you can already say, that it’s a bug in the NG image, right?

Is it clear from my first post, that I wanted to report a bug?

Or is there another place, where I can do this?

14

Ok
Go back to 21.2 NG

I suggest clean install

15

As I wrote in post 1, I have already done a clean install (see “Installation 2”) with CoreELEC-Amlogic-ng.arm-21.2-Omega-Generic.img.gz on a new micro SD card.

The problem exists without me having changed anything on the system. I just kept clicking OK during the initial setup (language, SAMBA activated, etc.); the wired network is still displayed there, by the way.
Then I shut down, unplugged, plugged in again → after booting up, there is no wired network anymore and then the next time I shut down, it reboots instead…

16

Ok
Apologies
My replys are not helping
And seem to confuse/make matters worse!

Maybe best is to go to 21.2 NG discussion Thread

Post your questions there
And use the support link
Post dmesg etc

17

No no, thank you for your help! :+1:

At least we found out, that it is not somehow my device, but the NG image, since the errors with NE and NO do not occur.

I had already posted in the Ugoos X4Q thread:

But nobody has commented on it yet.

Then I went to How to report an issue you’re having with CoreELEC

… create a thread in the appropriate category, describing your issue, how to reproduce it and a debug log.

I thought I was in the right place under Support&Help/Ugoos!

Which thread do you mean, this one?:

What do you mean by “use the support link” and “dmesg”?

It would be a shame, if this couldn’t be dealt with, because otherwise the box works great with the DV support!

But my power supply has a slight beeping noise when it’s inactive (when the device is turned off). For this reason, and because I’m used to it anyway, I would like to always have it unplugged. But that’s not possible.

And I would have liked to have bought the device for someone else and pre-configured it, but when the device does such antics after it has been disconnected from the power supply, it is a bit difficult to explain…
And the fact that you can’t really tell what the operating status is from the device’s LED is also suboptimal.

18

Read again
How to report an issue

You are missing debug logs at least

19

Yes, I attached it here in post 1.

(But I hadn’t posted any logs in my other post in the Ugoos X4Q thread linked above, if that’s what you meant.)