Pass all theme apks to themeservice for processing

3rd party apps expect ACTION_THEME_RESOURCES_CACHED once a theme is installed
regardless of the contents of the theme.

Previously only packages with overlays were passed to the themeservice
for resource processing. The result was packages without overlays would
install and ACTION_THEME_RESOURCES_CACHED would never be broadcasted.

Change-Id: I7cf3f8267805ef2a0626b2690b708e7bbae46bcc
MediaScanner : Add support for default ringtones per sim

Change-Id: I1ed112a38d2b3676e31a78eb70ea0e16a3957b02
ums: support UMS on any volume

Change-Id: I43668a5200d30cef953e0d3e9ded2d8cf0cbbd22
Vectone UK (MNC01) considered non-roaming on T-Mobile (MNC30)

Change-Id: Id74c854f958be721be12451a124cfd2f8b150255
Crop wallpaper and lockscreen images before saving them

Images were saved as-is and could cause large heap usage when
Wallpaper loads them later. This patch crop the images to fit the
screen size before saving them (as wallappper cropper activity does)

Change-Id: I08c04d9d14a65355c4417f0414d7a6ac538b3ea0
Disabling "Charging sounds" should prevent wireless sound as well

This is a fix for CYAN-4689 and also partial fix for CYAN-812. As noted in CYAN-812, separate section may not be a bad idea but the "Vibrate" checkbox already works with wireless charging so the sound settings should be allowed as well. There is no other (non complex) way for users to disable "wireless charging started" sound without modifying Android system.

Change-Id: I3311b94a7771863e49c1f83049600377dcf52d45
LockscreenInterface from ToggleLockscreenTile (Part 2 of 2)

The current longpress intent of the lockscreen tile is to open
the security settings activity. However, all lockscreen options
were moved to their own fragment months ago. This fixes the
tile longpress to open the current lockscreen options.

Change-Id: Ibca8403e69886d2c83f5240c4cae9adbb61535be
Automatic translation import

Change-Id: I82e4f38290b58a5cc4c84e8fd98e8e5483761bbe
BackupManagerService: Unbreak "adb restore"

The new restoreOneFile() logic aborts the loop whenever the result
isn't an actual successful restore. The problem is that a normal
backup will have plenty of non-restore cycles (APKs that are already
present being the most common), so this breaks regular "adb restore".

Go back to the original logic of completing the loop as long as the tar
file has data (or an explicit abort is generated)

Change-Id: I808cdc1c3b374e29d8438c7051e37c24a7a9d991
BackupMangerService: Pass result code in non-interactive calls

Non-interactive calls are made by Nextbit.  Continue to expose
detailed error codes for all failures.

Also:
- avoid overwriting the non-okay result codes; and
- re-enable version mismatches enforcement.

Change-Id: I54983d8f270285942db20eaff1e6de4229ec781e
Merge remote-tracking branch 'github/cm-11.0' into HEAD