Loosen signature injection behavior in non-secure mode

If secure mode is possible, let signature injection depend on secure
mode setting. If not, depend only on the config value. Even some TWRP
recoveries seem to still have issues with injecting the verification
keys. As nobody seems to be reporting any useful info on why this is,
we're (optionally) disabling signature checking when secure mode is
disabled, until we can figure out what the problem is.
Dismissing update available notification now snoozes it for 24 hours

Previously it would come back whenever a background check took place
Add LOG_TAG variable to Logger code
Force debug logger to English locale formatting
Update IT Strings

Change-Id: I7862b7538a244b612ef8e1bf7d806eb1fe98cc33
Make sure TWRP signature verification is off in non-secure flash
OpenDelta: CS Translations

Change-Id: I6deea50583fbf4edb39b06cd3cd68f41c9e9371c
Merge remote-tracking branch 'omni/android-4.4' into android-4.4
OpenDelta: SV translations

Change-Id: I1e69de939b8502790e027beb12aff5bbdda1f22e
OpenDelta: EL translation

Change-Id: I1a15dc8e7e7ca88ecc0187a62eb2b9e70d729217
OpenDelta: Chinese Simplified translation


Change-Id: Ib141a43964d69b749dc2e85f58b79df3c63b9603
Merge "OpenDelta: Chinese Simplified translation" into android-4.4
Merge strings.xml and strings_DATE.xml into single strings.xml

For consistency and compatibility with some tools. Of course, this
completely breaks compatibility with other tools and workflows,
but that is for another time to QQ at.
Keep screen on during download/patch/verify on select devices

On some devices the download/patch/verify process can freeze if the
screen turns off. This appears to be an issue with the fuse daemon.
This is temporary work-around until the real issue can be found and
fixed.
Override Application and enable debug logging from there

Some debug messages weren't being logged as the debug logging enabling
code ran after the code outputting debug information. Moving the code
to enable logging to Application::onCreate prevents this from happening
Update copyright notices
Scan secondary storages for initial flash file

Scan secondary storages (sdcard, OTG drives, etc) - as listed by the
SECONDARY_STORAGE environment variable - for the initially flashed
file. In case the user used one of these storages to flash OmniROM
originally instead of the 'internal' storage, this should now locate
the relevant file to use as base for patching, rather than having to
download the full nightly.
Merge remote-tracking branch 'omni/android-4.4' into android-4.4

Conflicts:
	res/values/config.xml
	res/values/strings_20131218.xml