Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Idea: MOODE Startup Spashscreen
#11
So I've posted a crappy video on YouTube to show where I've gotten to with minimal surgery on moOdeOS. (Don't do what I did: using a smartphone to make technical videos is an exercise in frustration):

moOde Splash Screen

This was on an RPi3B+ with a Kuman 3.5-in HDMI LCD display mounted on it. The boards mate via the GPIO pins and using a cute little HDMI-HDMI jumper between the two boards.  This guy was cheap.

An OLED display would have been superior in almost every way but did I mention this guy was cheap? Because of the optical characteristics of the LCD screen and its backlight, I had to shoot the video off-axis, hence the keystoning, and some of the unevenness in focus and intensity. The color rendition is awful because I had no control over the camera settings.

In this 53s video, the power is switched on at t=4s, hence the flash and then the LCD board's firmware generated advertisement. Once the framebuffer is displayed you can see that I've suppressed all the usual niff-naff like raspberry logos, boot messages, and blinking cursor.

In this version, I did not use plymouth. I used the framebuffer imageviewer to display an image I made for a splash screen. The image doesn't show up until 13s after I turned on the power---it takes that long for the root filesystem to become available. Then we get into burble after about 30s because, I'm assuming, the Xserver grabs the framebuffer as it begins to initialize. Finally, the moOdeUI asserts itself after another 10s or so.

This isn't great performance but it's a beginning. One way to shorten the time it takes for the splash screen to appear would be to use plymouth instead of fbi, although I'm still arm-wrestling with plymouth in the raspbian lite environment. Another way would be to push the fbi activity into the initramfs so it can initialize earlier. I'm working both angles but I'm really interested in the latter approach because I've got plans for an alternative to moOde's local display using the framebuffer directly instead of using chromium/X11.

Details to follow.

Regards,
Kent

PS - @DRONE7

Yes they deliver wine by the glass. Of course the glass in question contains 750ml and requires the manual removal of a contrivance before I can drink from it.
Reply


Messages In This Thread
MOODE Startup Spashscreen - by pkdick - 04-09-2020, 09:32 AM
RE: MOODE Startup Spashscreen - by Tim Curtis - 04-09-2020, 12:22 PM
RE: MOODE Startup Spashscreen - by manolomalele - 09-01-2021, 10:22 AM
RE: MOODE Startup Spashscreen - by Tim Curtis - 04-09-2020, 01:03 PM
RE: MOODE Startup Spashscreen - by pkdick - 04-09-2020, 02:00 PM
RE: MOODE Startup Spashscreen - by pkdick - 04-10-2020, 05:56 AM
RE: MOODE Startup Spashscreen - by DRONE7 - 04-10-2020, 06:55 AM
RE: MOODE Startup Spashscreen - by TheOldPresbyope - 04-21-2020, 03:43 AM
RE: MOODE Startup Spashscreen - by pkdick - 04-28-2020, 04:13 PM
RE: MOODE Startup Spashscreen - by JST1963 - 05-01-2020, 09:11 PM
RE: MOODE Startup Spashscreen - by huey2011 - 02-18-2022, 10:45 PM
RE: MOODE Startup Spashscreen - by Cardone - 05-02-2020, 08:37 AM
RE: MOODE Startup Spashscreen - by Cardone - 05-02-2020, 07:39 PM
RE: MOODE Startup Spashscreen - by Tim Curtis - 05-02-2020, 10:47 PM
RE: MOODE Startup Spashscreen - by Cardone - 05-03-2020, 03:46 PM
RE: MOODE Startup Spashscreen - by Tim Curtis - 05-03-2020, 06:34 PM
RE: MOODE Startup Spashscreen - by manolomalele - 10-14-2021, 06:14 PM
RE: MOODE Startup Spashscreen - by manolomalele - 11-12-2021, 01:43 PM

Forum Jump: