Closed provokateurin closed 3 years ago
I was not sure about the size of the splash screen images. I simply scaled the librem 5 images to the screen size of the devices, but they look off center on beryllium. How should this be done correctly?
Woohoo! Enchilada and fajita images both work!
Could we disable all output to the default console and go to UART instead? After the initial splash some more messages appear which obscure the text.
console=ttyMSM0,115200
edit: looks like just setting console=ttyMSM0,115200 redirects all logging, no need for quiet.
Should we expose partitions other than userdata? Like system / vendor / boot partitions? This would allow flashing a new boot image with dd instead of fastboot from a host, though the use case for this is slim.
With console=ttyMSM0,115200
it only shows the tuxes and a blinking cursors for me on the screen, but with quiet
I only see the splash screen and a blinking cursor somewhere.
@calebccff Can you test with just quiet
?
With
console=ttyMSM0,115200
it only shows the tuxes and a blinking cursors for me on the screen, but withquiet
I only see the splash screen and a blinking cursor somewhere.
You mean you don't get the splash when you specify a different console? That's really weird...
I don't have time to build jumpdrive today unfortunately, I'll try and take a closer look tomorrow.
I can send you updated images with only console, only quiet and both set later
Tested on OP6, everything works fine. The only minor exception being the framebuffer console partially obscuring the fbsplash, I've made a patch to fix it by disabling kernel logging during init. See attached 0001-info.sh-add-option-to-disable-kernel-logging.txt
The patch should also be added to beryllium and fajita, right?
Yeah it should
Adding support for other (close to) mainline Android devices will be very easy. beryllium has two panels which require different dtbs therefore the split of boot.img's. @calebccff needs to verify everything works on enchilada and fajita.