We can change the "SONY" logo in the kernel we are using for all those devices: https://github.com/sonyxperiadev/kernel/blob/aosp/AU_LINUX_ANDROID_LA.BF184.108.40.206_RB1.05.00.02.019.067/drivers/video/msm/mdss/splash.h
> convert b2gimage.png -separate -swap 0,2 -combine b2gimage.h And then remove the 16 first bytes.
This is also something we should be able to do on the KK build. I have tested and verified it on L kernel already.
Summary: Provide B2G boot logo on aries-l and others → Provide B2G boot logo on Xperia devices and others
Jacqueline, can you or some other UX people provide an image for this ? As a reminder, this is the very early stage boot logo. The logos we see are: 1. Kernel logo (the one in this bug), which is currently "SONY" branding 2. Boot animation (the moving fox) 3. Gaia System app logo (the Firefox OS branding) What we would need for the kernel logo is just a static PNG (with color if you want). It's easier if we have a small (will be centered) branding on black background since we can use the same on all devices that uses this kernel instead of having to hack more.
Attachment #8637821 - Attachment is obsolete: true
Adam, I'm not able to properly convert and make this displayed. Whatever the format or transformations I do, colors are always wrong on the device :(.
Created attachment 8637879 [details] [review] Kernel PR
Flags: needinfo?(adam) → needinfo?(lissyx+mozillians)
Attachment #8637879 - Flags: feedback?(lissyx+mozillians)
steps to reproduce: 1. Ensure PNG format without alpha (fill it with black) 2. convert b2gimage.png -separate -swap 0,2 -combine b2gimage.h 3. remove first 15 bytes (first line of 12 then first three on second line, usually "0x35, 0x35, 0x0A,") 4. ??? 5. PROFIT.
Created attachment 8637899 [details] [review] Kernel PR
Comment on attachment 8637899 [details] [review] Kernel PR Looks nice on Z3, Z3 Compact and Z3 Tablet Compact :)
Attachment #8637899 - Flags: review?(lissyx+mozillians) → review+
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.