[1/4] Dialer lookup

Squashed commit of the following:

commit 7802111
Author: Xiao-Long Chen <chenxiaolong@cxl.epac.to>
Date:   Fri Mar 7 17:11:02 2014 -0500

    Add people lookup settings keys

    Change-Id: I2ff9bb7684d04f4f9b640939c7db269873aa3308

commit 0e5ed5a
Author: Xiao-Long Chen <chenxiaolong@cxl.epac.to>
Date:   Fri Jan 31 11:43:10 2014 -0500

    Frameworks: Add settings keys for forward and reverse phone number lookup

    Change-Id: I1c4c7825b4361b7a52dd419f83afd7b9fcbe1494

Change-Id: I68e4214e813695021b64c29ab1d831a944a6275a
Update IT Translation

PS4: Fix derps and update safe headset volume on the spot.
PS5: Conditional for safe volume aswell.

Change-Id: Iabf7613b90d84476405522c2352361d0153ec655
Audio: Fixed system/call stream volume can't adjust with HS connected.

Issue Description:
When headset connected, the system/voice call stream volume can't be
adjusted from Volume bar.

Root Cause:
Currently adjustStreamVolume is applied to stream type alias and the
device for the stream alias. So when headset connected and adjust
volume for SYSTEM_STREAM, the operation will be applied to RING_STREAM
(which is aliased by SYSTEM_STREAM) and speaker. As headset is returned
from getDeviceForStream(SYSTEM_STREAM), but speaker for RING_STREAM.

Solution:
Change the adjustStreamVolume to apply volume to the stream alias and
the device for the stream type exactly.

Change-Id: Icd226d9eb197017cd3c186a0096edaed755680ec
Signed-off-by: Guo Xie <gxie@marvell.com>
PIE: Prevent a rare freeze that appears on quick iterations.

Signed-off-by: Carlo Savignano <stevewatersy@gmail.com>
Merge "Audio: Fixed system/call stream volume can't adjust with HS connected." into kitkat
Merge "[1/4] Dialer lookup" into kitkat
revert our dialer lookup and keep inline with mainline aospa

Change-Id: I8193d08ecea599d2a7fbcc2c9c64b450047877ed
Signed-off-by: houst0nn <houstonn@gmail.com>
Merge branch 'kitkat' of https://github.com/AOSPA/android_frameworks_base into kitkat
base: Fix screen on stats after a boot

Prior to this change, the following sequence:

  * Turn the display off
  * Issue a reboot via adb
  * Unlock the device (after rebooting) before the screen turns off

results in the screen being on but the battery stats not reflecting
this fact.

In general, the mismatch occurs when either there is no serialized
battery stats state or when it is serialized in a state where the
screen is off.

Change-Id: I17374553fae6a08a1be8fdf445967509474177a9
Revert "Fix: Custom lockscreen force close"

This reverts commit 6af4b210145c34c0249ef703b8ba33f0ed4ca6e8.

Change-Id: Ia5956d70bbc8a98d141ff64e11a575e410d99952
Merge "Revert "Fix: Custom lockscreen force close"" into kitkat
Revert "Custom lockscreen"

The UI of the feature does not fit android guidelines and the feature itself seems a bit too much for me.

This reverts commit 2fa74b852a8e5750adbb5fa2f8db2b935ce56f06.

Change-Id: I3641ffba528b128015dbc1917938d472807a10db
Merge "Revert "Custom lockscreen"" into kitkat
Merge branch 'kitkat' of https://github.com/AOSPA/android_frameworks_base into kitkat

Conflicts:
	packages/Keyguard/src/com/android/keyguard/KeyguardViewManager.java

Change-Id: I6012dce563c299d1ca42537f2940d29c6428f788
Merge remote-tracking branch 'pa-legacy-kitkat/kitkat' into kitkat