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
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
Frameworks: Lockscreen Rotation Optional (1/2)

PS2: Change method to allow disable, enable
	portrait, landscape rotation.

PS3: Just clean up...same code.  Different
	style.

Change-Id: I164d31b8980562eb5df68dcb2846410d932a4e73

Conflicts:
	core/java/android/provider/Settings.java
	packages/Keyguard/src/com/android/keyguard/KeyguardViewManager.java
Frameworks: fix possible NPE + and missing expandable panel

Steps to reproduce for NPE:
- go into volume style settings
- switch to disabled
- switch to expanded
- NPE and hotreboot

Fix:
Check if mStreamControls is initialized and if not lock it and do it.

Steps for expandable error:
- go into volume style settings
- switch to disable
- press one time the volume button
- change to expandable
- change the volume and press the expanded icon
- result is it does not expand and is empty due of the missing volume panels.

Fix:
- if it was changed from disabled to expanded be sure that the additional volume panels
are recreated.

PS:
- fix another exception

Change-Id: I58d63d34f831b6a6f60f6eddb3a07fc916d464f3
Change SQL to improve performance.

To know the number of images, use "COUNT(*)" instead of "_id" in SQL.
Using "_id" gets all result set. and when getCount() is called, CursorWindow is filled.
But using "COUNT(*)" gets just 1by1 data.
So using "COUNT(*)" is more faster than now.
And this SQL is called everytime per a file during a file transfer in MTP
The better way is by using "EXIST".
But if using "EXIST", modify MediaProvider.call() method.
So i applied just a "COUNT(*)"

Change-Id: Ic5882af0fad2304f836b7b7043a4746359391609
Signed-off-by: muzbit.kim <muzbit.kim@lge.com>
Input: Fix Palm Rejection

A "bad merge" appears to have broken 'Palm Rejection' for devices
that use a stylus. This commit:

https://gerrit.slimroms.net/#/c/62/

appears to have only implemented half of the necessary changes in
InputReader.cpp for 'Palm Rejection' to work properly. This commit
adds in the missing pieces.

PS2: whitespace derp

Change-Id: I402df6ed45b53cf02299f0b6588c763c3cb3de48
Frameworks: Fix possible ANR and navigation bar freeze

Big thanks to ralpheboyo which provided us the first time a usable
anr trace where we can see what the actual problem is.

The random ANR is caused due of to much work on the navigationBarCanMove
feature. We call way to often the provider value even though it is only
needed on initiliazing or on update of the value. Currently we call it on every
possible navigation bar change and this multiple times.

To fix it just call it on init and on contentobserver changes and pass
the new value to the navigation bar view and the search panel view

PS:
- remove another call
PS
- add one security check just to be sure
PS
- get one step further and put out the navigation ring config as well
  and reduce it to just one call.

Change-Id: Ica6116289d5bc50e9bedcd34b4b165062fa3468d

Conflicts:
	packages/SystemUI/src/com/android/systemui/statusbar/BaseStatusBar.java
Framework: disable keyguard widget frame (1/2)

And another user request.  But...I can understand
	it now that I see it without.  They actually
	look quite nice this way.

Change-Id: Id0222140a41eec9e5cd27b769cf860ac62ede1c0