diff options
author | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2021-12-06 18:19:45 +0100 |
---|---|---|
committer | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2021-12-06 18:26:24 +0100 |
commit | dc996b016053328cfcc1568bae76eb93466fbb9e (patch) | |
tree | 8a911418135ba2d0ee45541999fdba56f1d0e54b | |
parent | 3c73bbf5ad4928f0be545c7e99d6e2f75adcd949 (diff) | |
download | device_samsung_midas_common-replicant-11.tar.gz device_samsung_midas_common-replicant-11.tar.bz2 device_samsung_midas_common-replicant-11.zip |
Re-add the bootanimation zipHEADreplicant-11-nlnet-eu-grant-825310-replicant-updatereplicant-11
While booting the device without the bootanimation zip, we had the
Android logo being displayed.
This led me to think that the problem was coming from the zip file
and not missing kernel configuration. I then tried Replicant 6 zip
file and they worked.
I then used diffoscope and found out that the main difference between
the working and non-working file was the zip compression level.
The bootanimation.zip files are supposed to be uncompressed, but when
using mat2 to make them reproducible, it compressed the files when
recreating the cleaned zip.
So we now use a fork of mat2 that default to no compression when
creating zip files.
We will then need to either upstream support for that or not use mat2
during the zip process.
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
-rw-r--r-- | midas.mk | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -65,7 +65,8 @@ PRODUCT_COPY_FILES += \ # Boot # ######## PRODUCT_COPY_FILES += \ - $(LOCAL_PATH)/init.midas.rc:root/init.midas.rc + $(LOCAL_PATH)/init.midas.rc:root/init.midas.rc \ + vendor/replicant/artwork/tests/bootanimation/vertical-720x1280.zip:system/media/bootanimation.zip \ ############################ # Codecs (audio and video) # |