Settings: Alert user when they attempt to add an invalid number to BL.

  - BlacklistProvider will reject numbers that aren't valid, silently. So instead of
  resuming to a blank screen, we should alert the user that the number they attempted to
  add is invalid by utilizing BlacklistUtils#addOrUpdate method.

Change-Id: I1ca32427baad41c1c9379e18046e6ca7937b6d32
settings: prevent NPE if device doesn't support ActionBar

If the device FEATURE_ACTION_BAR (the device hasn't it enabled or a theme has disabled it), getActionBar()
will return a null reference. Just prevent to use that invalid ref.

JIRA: BUGDUMP-23210
https://jira.cyanogenmod.org/browse/BUGDUMP-23210
Signed-off-by: Jorge Ruesga <jorge@ruesga.com>

Change-Id: I210867b10193471c49e444c27c47e9de6baee822
Use actual storage type of sdcard/usb (2/2).

Currently, storage volume description for mount/unmount/format determined at
build time using PRODUCT_CHARACTERISTICS. For device which has only a sdcard or
only support usb storage, displayed description is correct. For device which has
both storage, the displayed description is totally wrong.

Use of actual storage type at runtime can eliminate the needed to specify
product characteristics, either default or nosdcard.

Change-Id: I9f8d53a4648d960f1009b1fe94787eecd4343427
Properly apply edit dialog brightness value.

Change-Id: If0bc90f045e5549dced296a7944e9ed0ea98b0c9
Settings: nl translations

Change-Id: I454c7d2489f11cd5ea9e992e742c5b2aef5f3fb6
Merge "Settings: nl translations" into kk44
CryptKeeper: update emergency call button to Holo

Change-Id: Id98a3345a7bb99b485ef608cec4319a84c040081
Automatic translation import

Change-Id: I20f3f718753a7ec48ead4ce3ad54cc09fbf6bd89

Conflicts:

	res/values-iw/cm_strings.xml
	res/values-zh-rHK/cm_strings.xml
Device Info: Move legal information to the bottom

Generally you put the more important settings at the top and i don't
really see any of our users *ever* clicking on this on purpose

Change-Id: I56edaf2b771cf2e79010e7140159d805a844ffa2
navbar: pass the context to getNavBarActions

We need a context to check for torch compatibility

PS2: add to getNavRingActions also

Change-Id: I41d319ea1c9a4f065b3c2b23efb3bc823e0045f9
Merge "navbar: pass the context to getNavBarActions" into kk44
AwesomeConstants: turn it inside out and airbrush some dragons on it

Change-Id: Ic0e076d1379361992d12b87548ee2063f05d47b3
Merge "Device Info: Move legal information to the bottom" into kk44
Settings: Fix AOSP ES translations

Change-Id: Ie596596891ad3ceacb846f7f059a64c09bb14c68
Settings: Modify and add AOSP JA translations

Change-Id: I36fd1817aa9be4c4ccb6054964b65cc2696c188f
Revert "Revert "Fix HighTouchSensivity (1/2)""

This reverts commit 8795728f12e2ef2347047f1b4e08358bca3452ab.

Change-Id: Ia4a06385b8e209f72bb1e9960f7319b5a4496c14
hareware ==> hardware

Change-Id: I9cf163c9bd6cf7324fafc522ccddb3b31679a652
RecentsSettings: welcome to the big kids table

it's a reasonably-large grouping of similar ui-settings. Let's get it away from the UNDESIRABLES in system_ui_more

ps2: Rather than ALWAYS opening omniswitch settings, choosing omni recents now presents the users with
     the same information as it had previously (that omni should be enabled and set to turn on at boot)...
     it NOW offers them a CHOICE to go to omni settings to set/check those settings

Change-Id: I104c5979cd26367b6a882adf76980b3ad10b4814
Merge remote-tracking branch 'upstream/kk44' into kk44