-
Notifications
You must be signed in to change notification settings - Fork 358
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
document custom boot splash screen #155
Comments
Need to probably add this to FAQs as well |
Even if you do it that way, whenever you update your code the device loads the resin logo again isn't it? |
@seungja no, it should always load up whatever splash image you wrote over the resin-logo.png |
I must be doing something wrong then, i replace the splash/resin-logo.png then boot a Intel NUC with that image and the custom splash loads fine, but just after Post Provisioning (when you must remove the USB drive and boot from disk) it loads default Resin Splash from there onwards. 😞 |
@seungja ahh... I know what is going on. The issue is that this feature was broken on the flasher types (where resinOS is written to the internal storage, as in the case of the NUC) We have fixed that, but it has yet to be deployed on the intel NUC images. You can see the change log here: https://github.com/resin-os/meta-resin/blob/master/CHANGELOG.md#v19---2016-08-24 Hopefully in the next week or so we can get the latest version up on resin.io |
@shaunmulligan Thanks for the info!, i'll have to wait for the version change then 😃 |
hey @seungja , I believe that resinOS 2.0.4 is now available in production for the intel nuc. So in theory this feature should work for you. Let me know how the testing goes. |
Hello @shaunmulligan, i just made some tests with the resinOS 2.0.4 version. and sadly, the behavior is the same :( I even tried making a new application and starting anew but still just after post provisioning the splash resets to the default one. also i think this would be super awesome feature to have for deployments that require full branding of a product:
my constant enquiry for the custom splashscreen is that i'm working on a project for another company that requires that the branding must be all of their corporate identity, so i can't have the resin logo appear on reboots, updates or a new provisioning of a device |
Hey @seungja I spoke to one of the device engineers (@telphan) and he said it might be a regression, so he is going to look into what is going on. It might also be worth raising an issue on http://github.com/resin-os/resinos as it will have better visibility and tracking for the team there. |
Looks like this is documented at https://github.com/balena-io/docs/blob/master/shared/overview/2.x.md#dev-vs-prod-images but perhaps this issue is suggesting it should be documented more prominently? (see also #1307 ) |
This is a very old issue so likely those docs above didn't exist then. I also added in a reference via https://www.balena.io/docs/reference/OS/advanced/#disabling-rainbow-splash-screen so I think I'll close this for now as it'll return at least a couple results searching for splash. |
Customizing splash
We configure all of our initial images to produce a resin logo at boot, shutdown or reboot. But we encourage any user to go and replace that logo with their own. All you have to do is replace the splash/resin-logo.png file that you will find in the first partition of our images (boot partition) with your own image. NOTE: As it currently stands plymouth expects the image to be named resin-logo.png.
Front conversations
The text was updated successfully, but these errors were encountered: