bootlogo.mvi doesn't show when booting

[LraiZer]

enigma2.sh.in only searches for shows backdrop.mvi

if [ -x @bindir@/showiframe ]; then
	SKIN=`sed -En 's|config\.skin\.primary_skin=(.+)/skin\.xml|\1|p' @sysconfdir@/enigma2/settings`
	if [ -z "$SKIN" ]; then
		SKIN=`strings -n 10 @prefix@/lib/enigma2/python/skin.pyc | egrep -o -m 1 ".+/skin.xml" | sed 's|/skin.xml.*||'`
	fi
	if [ -n "${SKIN}" ]; then
		SEARCHDIRS="@sysconfdir@/enigma2/${SKIN} @sysconfdir@/enigma2/skin_common @sysconfdir@/enigma2 @datadir@/enigma2/${SKIN} @datadir@/enigma2/skin_default @datadir@/enigma2 @datadir@"
	else
		SEARCHDIRS="@sysconfdir@/enigma2/skin_common @sysconfdir@/enigma2 @datadir@/enigma2/skin_default @datadir@/enigma2 @datadir@"
	fi
	for DIR in ${SEARCHDIRS}; do
		if [ -d "${DIR}" ] && [ -f "${DIR}/backdrop.mvi" ]; then
			@bindir@/showiframe "${DIR}/backdrop.mvi" &
			break
		fi
	done
fi

[LraiZer]

For added info: OpenVix distro has a totally different recipes-distros build structure for bootlogo/s whereas every other oe-a team distro has the same.

There are missing fixes pushed to all oe-a team distros except this distro due to this different structure, such as the [vuduo2] update bootlogo.py fix ValueError

[Orlandox]

Vu+ Ultimo 4K:

If you copy this lcd.png to \Root\usr\share\, there is a bootlogo at LCD display.

lcd.png

[Huevos]

Odd. The enigma2 code only mentions bootlogo.mvi.
Some plugins mention backdrop.mvi, though.

Boot logotipo is core. Backdrop is opened by enigma2.sh when enigma start.

[thecaretaker]

Vu+ Ultimo 4K:

If you copy this lcd.png to \Root\usr\share\, there is a bootlogo at LCD display.

lcd.png

Nope, tried that and it doesn't show on the LED screen during boot.

It's the main screen I have issues with, not the LED display.

[birdman]

Boot logotipo is core. Backdrop is opened by enigma2.sh when enigma start.

I can't find any reference to it.

[LraiZer]

I can't find any reference to it.

Click the link in post #16 for backdrop reference

[birdman]

Click the link in post #16 for backdrop reference

Hmmm.... Must have had my eyes shut.
Turns out that my own script puts both files into /etc/enigma2 (along with a radio.mvi).

[Orlandox]

Nope, tried that and it doesn't show on the LED screen during boot.

It's the main screen I have issues with, not the LED display.

That is meant for Ultimo 4K (LCD size 800x480). What is the LCD size of Duo 4K SE ? 480x320 ?

lcd.png

[abu baniaz]

My H9S SE shows both a backdrop.mvi and bootlogo.mvi. They are located in /etc/enigma2. I have not tested other receivers yet.

[Joe_90]

I did a little experimenting with my AX 61HD. It shows both backdrop.mvi (briefly) and then bootlogo.mvi during the boot process. I placed the files in /etc/enigma2/

[thecaretaker]

Thanks guys and gals. I've tried everything but don't understand why. Maybe it is my TV and the timing the screen resolution changes during boot and it is just not quick enough to show the bootlogo.mvi. When I change screen resolution to 4K (2160p) and reboot, I don't ,even get to see the VU+ boot screen logo (TV switches to 576p) then it does 720p @60Hz before changing again to 2160p when I eventually get to see the backdrop.mvi proir to the picture showing with the infobar.

With boot from all other resolutions, I see the VU+ logo on the TV and on the LCD.

I can only assume it is a timing quirk with my TV and the VU+ Duo 4K SE which never happened with the Ultimo4K. Think I'll give up before I lose any more grey hairs :-)

EDIT: Orlandox, I resized your image to 480x320 and put it in user/share. Still didn't show on LCD during boot. I did try m8.



I wonder, During boot, Just after the 576p VU logo shows, I get a quick flash of digital dots for a millisecond before the screen changes to 720p @60Hz. I wonder if it is trying to show the bootlogo.mvi a fraction before the resolution changes and can't cope with an image of that size. I wonder if there is a way to pause the showing of the bootlogo.mvi by a second?

[abu baniaz]

The timing issue may be why you don't see it. That being said, the Duo 4k SE uses same chipset as ultimo 4k.

[thecaretaker]

OK, I've managed to get a better screenshot of that moment that shows before the resolution change to 720p @60Hz. I think this is the moment it is trying to show the bootlogo.mvi. What do you think?

Note that the TV isn't showing any screen resolution at that moment.

SnapShot.jpg

Here is a clip of the VU+ Duo 4K SE and the TV showing what I see on screen.

[LraiZer]

The timing issue may be why you don't see it. That being said, the Duo 4k SE uses same chipset as ultimo 4k.

Probaly start order is indeed not correct and is using the default "start 06 S ." param

OpenVix is missing all the INITSCRIPT_PARAMS for the duo4k models.

see. bootlogo fix vuduo4kse start order

INITSCRIPT_NAME = "bootlogo"
INITSCRIPT_PARAMS = "start 06 S ."
INITSCRIPT_PARAMS:vuduo2 = "start 70 S ."
INITSCRIPT_PARAMS:vusolo2 = "start 70 S ."
INITSCRIPT_PARAMS:vusolose = "start 70 S ."
INITSCRIPT_PARAMS:vusolo4k = "start 70 S ."
INITSCRIPT_PARAMS:vuuno4k = "start 70 S ."
INITSCRIPT_PARAMS:vuuno4kse = "start 70 S ."
INITSCRIPT_PARAMS:vuultimo4k = "start 70 S ."
INITSCRIPT_PARAMS:vuzero4k = "start 70 S ."

INITSCRIPT_PARAMS:vuduo4k = "start 70 S ."
INITSCRIPT_PARAMS:vuduo4kse = "start 70 S ."