Settings: fix Display settings FC on manta or devices without crt mode effect

we removed the animations category for devices without crt mode effects. Result
is the ListviewAnimation get now NPE on this devices due that they are in same category.

Fix it with just not removing the category due that ListviewAnimations are always present
and remove only the CRT mode option

Change-Id: Iaf88e1c5a729a0fb3b7692b0b83b88c58dd1ee93
Settings: ES translations

PS2: remove tabs

Change-Id: I275aa0d88b85e3590488ac21969ebb6f0375e7f3
Return: Custom Carrier Label [2/2]

Change-Id: I1965fe6fd6cef7eb0fb78d856db9edf69659573d

Conflicts:
	res/values/weapon_strings.xml
Add CPU & RAM info.

PS 2 : Cleanup

Change-Id: I0cce559c86321827d6f920d61ad9dfcb34a63b3c

Conflicts:
	res/xml/device_info_settings.xml
	src/com/android/settings/DeviceInfoSettings.java
[2/2] Settings: Make menu unlock configurable

For devices with hardware menu keys, menu unlock is turned on by default
This can cause unintentional unlocks. This commit adds the ability to turn
Menu Unlock on or off as desired (Settings -> Security)

System Default is for menu unlock to be ON. This default value can be
overriden using a device overlay:

overlay/frameworks/base/packages/Keyguard/res/values/config.xml
<!-- Allow the menu hard key to be disabled in LockScreen on some devices -->
    <bool name="config_disableMenuKeyInLockScreen">true</bool>

This commit requires the matching commit from frameworks_bases repo:
https://gerrit.slimroms.net/#/c/2394/

Based on: https://gerrit.omnirom.org/#/c/3318/

PS7: update overlay location
PS8: fix config value retrieval
PS9: rebase
PS10: catch NPE of mMenuUnlock if screen lock 'pattern' is used

Conflicts:
	res/values/slim_strings.xml

Change-Id: I8fc38b17315a050b10bb6d5fb13f6abf0f306e08
Remove notification pulse and light for devices without LED

PS2: if Light Options category is now empty, remove it

Change-Id: Ib42f792faeffe8c454a5e1dcf7ee0970254189b0
[2/2] settings: Add support for ADB over network

This patch actually consists of three parts. SlimKat has already patched the ADB service in vendor/slim: init.local.rc

Conflicts:
	res/values/slim_strings.xml

Change-Id: Ic6454dc7e0c910b485dc0f8a19e40d159040455e
Squash UMS Commits [2/3]

Credits: CyanogenMod

Change-Id: I9a57e993af4b216926dcb1c8d19a65a8f1646159
[2/2] Settings: Slims Hardware Key Rebinding

First thanks to CM team for the 2 years where we used their approach for our
custom hw key rebinding. This hardware key rebinding
patches did in the past a good job and we extended it prior 4.3 with a lot
Slim custom stuff.

But it is time to go new way and to do the complete
hardware key rebinding more flexible and more centralized. Especially due
that we have now all possible shorcutactions centralized in 4.4

Possible mapping are:
ACTION_HOME
ACTION_BACK
ACTION_SEARCH (in app search)
ACTION_VOICE_SEARCH
ACTION_MENU_BIG
ACTION_POWER
ACTION_NOTIFICATIONS
ACTION_QS
ACTION_RECENTS
ACTION_SCREENSHOT
ACTION_IME
ACTION_LAST_APP
ACTION_KILL
ACTION_ASSIST
ACTION_VIB
ACTION_SILENT
ACTION_VIB_SILENT
ACTION_POWER_MENU
ACTION_TORCH
ACTION_EXPANDED_DESKTOP
ACTION_THEME_SWITCH

and custom app/shorcut of course

Possible actions on all keys are:
normal tap / longpress / double tap

So to sumarize if it is in settings array enabled user can bind whatever of the above
actions to every hardware key action.

Main changes to prior solutions are:
- do not depend anymore on hardcoded integer values. We use now strings. This has
  the advantage that we can save whatever shorcut or intent URI we have into this
  value. And gives us the possibility in future without changing anything on the hw
  key rebinding code to get more options/or modify the options. Actions are holded
  like on all other of our features in ButtonsConstants.java
- All actions are peformed over our SlimActions like all other features. SlimActions
  takes care about all possible solutions the user can run into and sets the right
  open animation, keyguard handling etc etc. As well it is easier to maintain only
  one code base.
- Only observe and update the values on hardware key devices. On non hw key devices
  the complete code is non operational
- Removed in settings the not needed overlay due that we can use the fb one to
  check if it is a hw key device or not.
- Major cleanup of a lot old code.

This patch add as well one new SlimActions action....VOICE_SEARCH

To configure your device you need to add the device overlay as usual:

overlay/frameworks/base/core/res/res/values/config.xml
<!-- Hardware "softkeys" present on the device, stored as a bit field.
         This integer should equal the sum of the corresponding value for each
         of the following keys present:
            1 - Home
            2 - Back
            4 - Menu
            8 - Assistant (search)
           16 - App switch
        For example, a device with Home, Back and Menu keys would set this
        config to 7. -->
    <integer name="config_deviceHardwareKeys">7</integer>

Also requires fb commit.

Cheers HCP and kufi

Changes to prior patchsets:
- reflect fb changes
- simplify code
- code cleanup
- instance handling of error dialog
- some minor tweaks

PS:
- complete reworked....using now like on navbar etc custom dialogs to be
  consistent and pretty :D
- reset to default is not implemented yet...no idea if we want that or not. Any opinions on it?

PS:
- implement fb changes and use central HwKeyHelper class

PS:
- added reset button

PS:
- added double tap to all bindable keys

Change-Id: Ie4794073236f0b6fe308b931d7d6e9d02a1ddf02

Conflicts:
	src/com/android/settings/weaponx/NavigationSettings.java
Settings: add better dialog handling for adb over network

thanks fusionjack for this

his fix was accidentally removed

Change-Id: Icc09585f719e743ba5bd8b830586f2ebc0018a71