Don't let apps disable the SIM PIN entry screen.

As the user (who controls the app behaviour after all) likely doesn't
see the PIN screen as a lock screen (he likely wants telephony) and the
PIN screen is not shown on a timer-driven basis, it should be treated
specially.

Change-Id: I6b029124311f93fb3ba57efbff85bd64aadfb81a
Don't consider input restricted if keyguard is still disabled.

Change-Id: I00a351311d0933fe326bda33f5c988a6232cca16
Port power widget improvements from CM7 to CM9.

This is a squash of the following change IDs:
I42b4ad02c4eb8b57a2f4cf51a31148c4b0546b81
I6f619740659cfedec3a3c9517fb55275f601d792
Iaee471b29b306e9ebcc6a81799f7e36872951002

Change-Id: I4e40d8e27b9bb11367e30223ffb8024985476e74
framework: customizable kill app via back key timeout

Allows the time it takes for the back key to kill an app
to be customized via overlay.

Change-Id: Iaa43f81ee448ae7a7663254a830011a0bca5e60f
Smdk4210Ril: fix bad file format

Change-Id: I26a48a1422060a19c76fbc83af95ae7649442bf0
Merge "framework: customizable kill app via back key timeout" into ics
Revert "libstagefright: Fix MPEG4 timestamp"

A lot of applications (e.g. QuickTime, mkvmerge) apparently does not like the 64-bit timestamp and will fail to open the file.

This reverts commit 893586d4b7a0dbea070404323837ef4f0a7c9b79
Merge "Revert "libstagefright: Fix MPEG4 timestamp"" into ics
Fix sluggish to launch an app

The new trace feature/code in 4.0.4, which will dump the app stack
trace every 500ms if an app can't be launched within 500ms, is
holding the global ActivityManagerService lock unnecessarily. It
slows down the app's startup.

Change-Id: I91fbb043912b4d1fcf3e80d8ac4e61cd20ad89d1
Solution: move the trace file write operations out of sync block.
SamsungQualcommUiccRIL: use signalstrength value instead of # of bars

  * Math error in GSM level calculation gave high probability that 4
    Samsung bars would be shown as 3 AOSP bars.
  * Samsung sends # of bars in the signalstrength field of GSM and LTE,
    indexes 0 and 7. But this is on a 0-5 scale where AOSP uses 0-4 scale.
    The cutoff points for the bins are also different. Because of this
    confusion, just pass the measured signalstrength to the framework
    instead of computing signalstrength based on # of Samsung bars.
  * For debug and experimentation, Samsung's bar method can be enabled
    by setting telephony.sends_barcount=true

Change-Id: I8238af83f3a597b32eb99f42c71cbc263ad5bc82
Battery Light: Add ability to configure (Part 1 of 2)

Adds Quiet hours support and ability to configure the led if the
device supports multiple colors for the Light - enabled via overlay
with default as 'false'

Change-Id: I905dde400ba0780066f2b2a20142eaa27e158655
Smdk4210RIL: fix signalstrength

based on http://review.cyanogenmod.com/#/c/18220/

Change-Id: I872221e58e89412fcecf67c7208ab2c89aac7c04
Merge "Don't let apps disable the SIM PIN entry screen." into ics
Merge "Don't consider input restricted if keyguard is still disabled." into ics
Merge "Port power widget improvements from CM7 to CM9." into ics
Tablet powerwidget improvements (1/2)

Removes a lot of unecessary code, and does not limit toggles by 6 but dinamically adds the views to layout

patchset 2: remove tab

Change-Id: Id125605791d2de353e7466c4dfe135c32fb80df6
fix automatic timezone failing on some GSM networks

in the code that parses the NITZ string, someone made the assumption that if
any data follows the DST flag, it must be be the android emulator appending
an actual timezone string in "Area!Location" format.  However, it seems that
some carriers or perhaps in some locations, the carrier sends an additional
field in the NITZ string.  For example, this is a string from AT&T:

12/07/01,09:37:43-16,01,310

The extra field is "310" above.  This patch will only assume that the field
in question is a textual timezone if and only if it contains an exclamation
point.  Otherwise, the extra field is ignored and the timezone is parsed
as it should be.

Change-Id: I6cc4278027a6de5545d76b803f5359923e60878a
Signed-off-by: Gary Dezern <garyd9@gmail.com>
framework/base: hwui: Clear layer FBO after FBO cache is updated

Due to bug in GLRenderer stale FBO remains and can cause
corruption, clear layer fbo when fbo returned to cache.

CRs-fixed: 340481

(cherry picked from commit b01c082e12c4c4091016af1c95d851f29f5b7514)

Conflicts:

	libs/hwui/LayerRenderer.cpp

Change-Id: I8624879b4adbf9438a8c065b78932d1a4a2a15d4
Merge "Smdk4210RIL: fix signalstrength" into ics
servicemanager: Allow tegra audio to register as a service

Change-Id: I6c792b6f5f586cf40d4a9b834e793a68c1e458a7