[GiGaBlue UHD QUAD 4K] Crash and stuck in reboot loop after Front Panel Display setting change.

[goo]

What type of support thread are you creating?

Possible bug

What OpenViX Image build number are you using?

6.8.006 (release)

Have you tried re-flashing WITHOUT settings restore?

YES

Have you tried re-flashing WITH a settings restore?

YES

Just updated to openvix 6.8.006, and after changing Front Panel Display Skin from Default/Current to Default+Picon (which I think used to be the default Default) and restarting, the box got stuck in a reboot loop.
I tried unsuccessfully to flash it with the same image from a Kingston 8GB USB stick (which I have used successfully before). It displayed image found, but 40 minutes later nothing else seemed to happen. I had to start it in rescue mode and flash it from a network Windows PC. Using Magic-FHD skin.

 

[twol]

If there is a crash can you post crash log
Do have other image slots flashed - if so then it easier to reboot to one of the other slots.
If not then in future always better to flash new release into new slot and restore settings

 

[Huevos]

Connect to the box via ssh. Log in with your password if set. Then type "init 4" followed by "enigma2". Grab the output and post it here.

 

[goo]

i didn't have logs running when it crashed and there is nothing in the logs folder.
Yes I have other slots flashed but not recent images, so didn't want to reboot to them. I reflashed the same slot from a windows PC then restored the settings saved from the update from 003 to 006.
Works fine now, just warning anyone changing Front Panel Display Skin from Default/Current to Default+Picon (depending on skin) they may get stuck in a reboot loop.

 

[Huevos]

We can't reproduce that.

 

[abu baniaz]

Crashes will always generate crash logs. A few people keep saying that you have to enable the logs, this is incorrect.

The default location is the internal flash memory. As a new image has been flashed on the same partition, that has now been overwritten. Best to change the location to the HDD.

The debug logs are different to cashlogs. They have to be enabled.

 

[sarma]

Just updated to openvix 6.8.006, and after changing Front Panel Display Skin from Default/Current to Default+Picon (which I think used to be the default Default) and restarting, the box got stuck in a reboot loop.

This sounds similar as being discussed in

M

[VU+ Uno4KSE] Thread 'Enigma2 crashes after updating from .003 to .006'

Apr 4, 2026

After updating to version .006 my PVR started bootlooping. After quite long debugging session I finally managed to find the culprit. If I remove this line from settings everything works correctly.

config.usage.swap_time_remaining_on_vfd=2

• miloytyn
• Replies: 12
• Forum: ViX Team Images Support Discussion

and

Crash/bootloop with 6.8.007 (RemainingToText.py, config.usage.swap_time_remaining_on_osd=3) · Issue #1256 · OpenViX/enigma2

I got a repeating Enigma2 crash after just some 5-10 seconds uptime. After Enigma self-relaunches, it crashes again after 5-10 seconds. Total cycle is some 17 seconds :-( Luckily only Enigma crashe...

github.com

Only some values (0 and/or 1 ?) work for the "remaining" & "elapsed" time display options, both for GUI (vfd) and for the small screen (osd), until the fix (from commit f778906) gets applied to the next release.

Example of faulting options in "settings" file:
config.usage.swap_time_remaining_on_vfd=2
config.usage.swap_time_remaining_on_osd=3

Either remove those option to use the default, or use 1 there as the value, as it seems to work.

 

[twol]

[Converter] EventTime/RemainingToText: Attempt to remove spaghetti · OpenViX/enigma2@f778906

Contribute to OpenViX/enigma2 development by creating an account on GitHub.

github.com

 

[Huevos]

I will start a new release build in the near future once the changes are fully tested by the beta-testers.