Fix for "volume buttons change two volume steps per click" bug

This bug happens on all devices since CM9 or CM10 times.

To reproduce:
1) disable Settings/Buttons/Playback control
2) start music playback
3) turn off display
4) click on the volume buttons

When "Playback control" is enabled, the volume changes on the button up
event of short clicks only. When it is disabled, it changes on both
button down and up events. This fix cleans up the code and makes the
volume change only on button down when "Playback control" is disabled.

JIRA: CYAN-3202
Change-Id: If97218e35a8204ef602155f22b7eaaa5e13fb93c
Merge remote-tracking branch 'upstream/cm-11.0' into cm-11.0
Show devices connected to the WiFi hotspot(1/2)

Change-Id: I8378e0ae07332f62b92a1681951f1236f6ef5ff9
Add Screen Off option for buttons double-tap/long press (1 of 2)

This is being done primarily to replicate functionality on find7 Color OS.
Would it be better/possible to have this change only effect the find7?

Change-Id: I7e0c21b174b9cdd020c8d27c91c4c72201e228ff
Heads up master switch (1/2)

Create a global heads up switch to enable/disable the same.
The user still need to set each app in Settings -> Apps

PS: disabling through master switch will automatically turn of  call ui and mms heads up notifications

Change-Id: I650e230d275247251435c5cfeb728e375e927045
SystemUI: Improve AOSP JA translation

Change-Id: Id2b979eae5c0c2f169f842ccdd2c5cf11a930a48
FB: Heads Up background color && transparency [2/2]

    PS: manual rebase

    PS: fix my retardedness

    PS: fix heads up TRDS background resources

    PS: clear content holder background prior to setting TRDS
            drawable so that correct drawable for TRDS state
            is set

    PS: revert non-TRDS background to AOSP gray (default
            system notification background color)

    PS: clean up some unused code

    PS: add capability to set custom heads up text color
    Change-Id: I3942c0ce178491e3429e5ae7eb24b43ba07a1f40

    Conflicts:
        core/java/android/provider/Settings.java
        packages/SystemUI/src/com/android/systemui/statusbar/BaseStatusBar.java

Change-Id: I1f7c115cf72e647e3639b77c24ceb05aa75cb9a8
Quick settings: change behavior of swipe to switch

Now it's working not only in bottom bar but in all QS area

Change-Id: I0cbc336c5a4a6c9a180325791dbd508c6983a1ec
SystemUI: Remove unused strings

Change-Id: Ie8bf95abfeb4c13b30e9949aa9676ab39920bf29
core: Fix AOSP EL translation

* 'Minutes' was the same in singular & plural forms, fix that

Change-Id: I8444d879fa38fdbb9a89b96ff983c135cd0f3499
WallpaperCropper: respect max wallpaper width

Some devices with high resolution screen only support 2048px wide
wallpaper (used to be fixed in I5b25bd931db0b2610e260921f28b92d8b0966aa6)

Pre-KitKat this works as follows:

- Launcher calls WallpaperManager.suggestDesiredDimensions and we
  limit the maximum size in that function
- The wallpaper setting application calls WallpaperManager
  .getDesiredMinimumWidth and respects that size

However, after KitKat, it is all broken because WallpaperCropper
now calculate its own dimension and does respect the value set by
getDesiredMinimumWidth (and it calls suggestDesiredDimensions,
which is supposed to be reserved for Launchers!)

Attempting to restore wallpaper setting by:

- Having WallpaperCropper respect config_wallpaperMaxWidth
- Having CMWallpaper (which copy pasted code from WallpaperCropper)
  respect getDesiredMinimumWidth
- For third party applications, if they respect getDesiredMinimumWidth,
  then they will work, but if they don't (i.e. uses WallpaperCropper's
  code), then there's nothing we can do.

Change-Id: Ib7da12a1c70befbeef2f305593d3841acbc45243
AppWidget: Make widget update quickly

Can't display the Power control widget after power on DUT for
3 mins. Because of the  update intent is received after power
on DUT for 3 mins.

Set the intent to foregound

CRs-Fixed: 707605

Change-Id: I5418c84a7dc79466be7a30bb3672ea41976badb0
Merge remote-tracking branch 'upstream/cm-11.0' into cm-11.0
Return: Listanimation Views and Interpolator [1/2]

PatchSet:
    - optimize more:
    - call provider values only when needed and do not fire them permanently.
      so just do it if scroll state changed.
    - as well go out of the setAnimation method as soon as possible. We
      handle here methods which get called 10000 times during scrolling
      so we need to be as fast as possible.

PS:
- initialize the animation modes default to off just to be sure

PS:
- move state change out of OnScrollListener
- reduce the provider value call to only one call

Change-Id: I5e49d858318420e76101fa6334ff766bd9496c83

Conflicts:
	core/java/android/widget/AbsListView.java
SystemUI: RU translations [Sep 27 - build 56]
Merge pull request #11 from Pixelase/patch-1

SystemUI: RU translations [Sep 27 - build 56]
Merge pull request #1 from cristianomatos/cm-11.0