SystemUI: Set Status bar opaque during drawer pulldown on tablets only

The status bar only needs to be set as opaque when the notification
drawer is pulled down on 600dp and 720dp devices. On phones, this
is unnecessary as the top header of the drawer covers the status
bar on the phone UI. This change makes a huge difference in
reponsiveness on devices that run the phone UI as there is no
longer a delay before the drawer appears when interacting with it
on an activity with transclucent window decor.

Patch Set 3: Fix formatting, adjust comment
Patch Set 5: Delete file derp

Change-Id: I932bb92a5245f0323d3317776efbdc9151db449d
Revert "Don't recreate keyguard for MCC/MNC changes."

This reverts commit 46abf72997c6628db643fae69b8e0957c0163635.
FaceUnlock: Check if faceunlock is disabled

JIRA: CYAN-3622
Issue: https://jira.cyanogenmod.org/browse/CYAN-3622

Change-Id: Iaf656f1aecb72610a46183294de25151e8df4b05
Signed-off-by: Jorge Ruesga <jorge@ruesga.com>
Frameworks: Quiet Hours Automatic Switch (1/2)

Change-Id: I3e09891a60ffc5a11f5b5fabef8e06fb02dc9f5d
SystemUI: ES translations

Change-Id: Ief7186bfc019925dff7f36809b1895e4f1f1eea3
Frameworks: Fix memory leak + cleanup

Do not create new Objects onDraw + cleanup

Change-Id: Id1dc9ae85ccf820f2047528e12c4ecdc525f12d2
Framework: Lockscreen Slider Logic && Fix

Part 1: Keyguard array points directly to
	unlock handle and unlock handle
	ONLY.  Assist/Camera intents will
	never be used. It seems this logic
	in the code was devalued %100 by
	an array change that we'll never
	take advantage of.  I assume this
	was done so OEMs can revert the
	array and get camera/assist
	slider targets with minimal effort.

Part 2: Fix unlock icon colorizing if user
	lock targets are null.

Change-Id: I58206829de03828c7a0b838a4bbc56dbbc33c0c9
Frameworks: Fix linked volume does not persist after reboot.

The controling boolean value must be set before updateStreamVolumeAlias
is called first time. Otherwise updateStreamVolumeAlias will assume
it is always false till user toggle it in settings again.

Change-Id: I53455249909fa6ad69fa0ea6930f9065e5a14fdf
Keyguard: Fix Pin-Layout (squashed commits)

Squashed commits of the following:

commit fa06992ab7e49fe1e056787dd281384d92290be1
Author: Pawit Pornkitprasan <p.pawit@gmail.com>
Date:   2012-12-10 09:19:40 +0700

    keyguard: fix layout for sw320dp devices

    800x480px dpi devices have less screen space than the xhdpi devices
    Google designed the layout for and the layout needs adjustment.

    - Reduce the lockscreen security container size such that the clock
      widget has enough space to display its content.
    - In the SIM PIN/PUK view, Google put an empty widget on top, but
      we don't have space for that, increase its size such that the
      widget practically disappears.

    This should not have any effect on devices with larger screens.

    Ported from cm-10.2.
    * Removed invalid mdpi layout leftover from framework-res
    * Fix keyguard for mdpi devices too

commit 9c9c6d17772f4fa4681f43bea11fb5074e24093a
Author: Lorenzo M <djmesias@yahoo.es>
Date:  2013-12-08 23:05:32 +0100

    keyguard: fix-fix layout for sw320dp devices

    Default values need to be defined in sw360dp or larger devices will
    pick up sw320dp values automatically.

    On the maguro device the keyguard isn't properly centered.

    - Before http://review.cyanogenmod.org/54758:
        http://i.imgur.com/F6sokhA.jpg
    - After http://review.cyanogenmod.org/54758:
        http://i.imgur.com/OdTkZLL.jpg
    - With this commit:
        http://i.imgur.com/TThq9da.jpg

Keyguard: Fix PIN layout on sw320dp-mdpi devices

Commit: 294d0867079d21c0bcfb704315cdbb68a150dba4
Author: Michael Bestas <mikeioannina@gmail.com>
Date Jan 15, 2014 5:21 AM
    Fix a long standing lockscreen layout problem that
    was introduced in 4.2

    Before: http://i.imgur.com/9sVKHRR.png
    After: http://i.imgur.com/DLY4DRu.png

Change-Id: I3001e5678bc10ea7f287548c7d189fe0c45210ec