LiveBoot updated to v1.12
- Putting the fun back in to bootloops
I've just published v1.12 to the Play Store, it should be available within a few hours. Alternatively, you can grab the latest APK from the thread on XDA - http://forum.xda-developers.com/android/apps-games/liveboot-t2976189
The response to LiveBoot has been great so far - much better than I expected, actually. As always with a first release, there were a number of bugs to solve, and a lot of feature requests.
A fair number of these feature requests have been implemented in the latest version, and some major issues have been fixed.
One of the more common issues was the logs only showing up on screen for two seconds, and then going back to the normal boot animation. That issue should now be fixed.
Unfortunately, there are still a few users for whom it just doesn't work at all, and that issue is still under investigation.SuperSU requirement
There has been much whining and gnashing of teeth about the SuperSU requirement. I thought I explained the requirement relatively well in my posts, the app description, and even the popups in the app itself - but apparently to no avail.
As luck would have it, most of the users in question are running custom ROMs that do support init.d
. After some consideration I have added some basic init.d
compatibility to the app, for users who are not using SuperSU.su.d
(provided by SuperSU) scripts run at boot the same as init.d
scripts do, but guarantees are made regarding SELinux policies state, /data being available in decrypted state, and the timing of execution. init.d
scripts do not have this, and it depends on the init.d
provider (usually your firmware, but sometimes an app) and your current setup whether these requirement are met.
In practise this means that most popular source-built custom ROMs with init.d
SELinux, a data partition that is not encrypted
, and an older version of SuperSU or a different root altogether, may now work.
It should be noted however that there are still a large number of firmwares and setups (even with init.d
and non-SuperSU root) that will not (ever) be compatible. There really isn't anything I can do about that without significantly increasing the risk of bootloops, which is not an option.Changelogs
- Possible fix for only showing for two seconds during boot on some devices
- Fixed typos
- Pro: Made logcat buffers configurable
- Pro: Made logcat format configurable
- Made word wrap configurable
- Added option to disable logcat color coding
- Added option to darken the background
- Added option to save logs
- Added option to reboot
- Reduced APK size
- Added capability to use init.d if not using SuperSU. Not officially supported, correct working impossible to guarantee.