This doesn't work on a number of other Samsung devices, because the compiled bootanimation
program in this bundle refers to non-existent shared libraries on certain devices. Here's how to check if that's the case on your system:
1. Install the bootanimation
file from this package into /system/bin/bootanimation.test
2. Make sure it has 755 permissions (rwxr-xr-x).
3. Use a terminal emulator program to go into su
, and then navigate to /system/bin
3. Issue this command:
4. If you see any errors referring to "reloc_library" which end with "CANNOT LINK EXECUTABLE", then this bootanimation
executable will not work, because it refers to one or more non-existent shared libraries on your device.
Suggestion: relink this new bootanimation
executable as a static binary and resubmit it here. This will ensure that it doesn't try to run any shared libraries on the current device. I don't know if this kind of static linking is possible under Android, although it's a technique that often works to solve these kinds of problems under Unix/Linux.
---------- Post added at 11:56 AM ---------- Previous post was at 11:02 AM ----------
Another issue with this method:
On my phone (Galaxy S Relay 4G) and probably also on other Samsung devices, the system overwrites /system/bin/samsungani
with the original version upon every reboot. This prevents the altered samsungani
executable from running.