Add onBoot Receiver to handle boot configs
Make Message Relay work as it should
At the moment, Message Relay does not have any point. However, at some point messages will be moved to their own Tab Fragments and more messages might also be added.
In this case, one activity should not call another one. It just feels wrong, and the Tab Controller Activity may also not always be the one handling the messages. So we make a relay which can be called.
Then a Receiver can be added to handle them. This Receiver can be changed at any time without altering any message input classes.
Add log information message
Application Settings: Resolve script install issues
RootFW3 does not override existing files when copying or moving. So we should make sure that files really is gone before attempting to extract new once.
Overview: Add warning to content options
Some of the content options like system files, data and apps contain more than one directory which is moved or reverted depending on the state. Apps for an exmaple has app, app-private, app-asec and app-system. If one of these is not moved to the correct location, perhaps because of low space, we can't just show a green bullet.
Add Boot Receiver
Each time the application is launched after a boot, it takes longer to load as it needs to check all of the device setups. So we will do this automatically after each boot to speed up the first launch for users
Overview: Add warning when fschk has found partition issues
Update res/values/strings.xml