SystemUI: awful hack until Google fixes MDP

History:
Google adds tripple buffering in 4.1 - works splendid
Google merges changes in qcoms HAL in 4.2.2 that will trash the
composition engine in fullscreen mode

Change-Id: I6bfbac30e6b04c027d404f8026a9533681bcd4e7
Bug #14 disable pie on lockscreen

Change-Id: I4647aade6292cf49e5372e52d2ecff3bfe4b51f6
Some style fixes
Moar style fixes
Only disable pie on lockscreen if lockscreen is secure

allows users to acess notifications and quick tiles from the lockscreen
and still be secure. following aosp behavior

Change-Id: I8addbc958ec4e3211f9916b3428d3e3486b1c5a3
Merge branch 'jellybean' of github.com:ParanoidAndroid/android_frameworks_base into jellybean
Remove opaque check in GLRenderer when preparing dirty region.

Since preserved swap is enabled, we need to clear the color buffer
when the scissor rect is prepared for a new process. This prevents
garbage to be present from the previous process in the color buffer.

CRs-Fixed: 391492, 403067, 405916

Change-Id: I1f72a3dee2f5d58a984f4cd367c9f7bf08ab9d6a

Conflicts:

	libs/hwui/OpenGLRenderer.cpp

[PATCH] Remove opaque check in preparing dirty region

Since preserved swap is enabled, we need to clear the color buffer
when the scissor rect is prepared for a new rocess. This prevents
garbage to be present from the previous process in the color buffer.

(cherry picked from commit 2b5e584e2615852b68a69bb529c6926190246b64)

Change-Id: I92a4fa35e0746f12fcd736e21fd30d9c4b644a8a
CRs-Fixed: 391492, 403067, 405916

Conflicts:

	libs/hwui/OpenGLRenderer.cpp

Enable scissor when preparing dirty rect that is opaque

Now enabling scissor before setting it in the opaque case, previously was not doing so.

Change-Id: I1ea904cf01603096e423556090564291ab712d36
CRs-Fixed: 465346
Depends-on: 278453
Mms auto-retrieval (1/3): framework

Change-Id: I9b2f76d8cf9d67eddddfdf7737a948eea680329f

It's only porting this http://review.cyanogenmod.org/#/c/26166/
Part 1 of 3
Fix race condition in backlight adjustment.

When configuring the automatic backlight levels, there's a race
condition in setting the lux and brightness settings as the settings
provider doesn't allow storing multiple settings atomically. When
deleting rows, there's quite a high chance of DisplayPowerController
picking up a state where the lux values already have the lower number of
rows, but the brightness values do not, effectively leading to an
ArrayIndexOutOfBoundsException.

Fix that by
- waiting a second of cool-down time until applying the settings and
- adding a sanity check for the very unlikely case that the delay
  between writing both values is > 1 second

Change-Id: I44e41530fc5334aaefc4ab7d3a90542f78fabe0c
JIRA:CYAN-755
Revert "makefile changes for gcm javadocs"

We don't build it, nor do we have these sources.

This reverts commit 5f9922d7c3bce158e4c7a58929d4075e7c91e32e.

Change-Id: I877e617f90de1b832e26c98adbafc6238b98882f
services: don't clear wallpaper when SystemUI
disconnects.

When we restart SystemUI (or the user), sometimes
the wallpaper would get cleared. This patch just
captures its originating component and
if that is our SystemUI component, ignore the event.

Change-Id: I3e159dc2c013e7d7e552e3c0cef55e3ab970ca87
Signed-off-by: Roman Birg <romanbirg@gmail.com>

Conflicts:
	packages/SystemUI/src/com/android/systemui/quicksettings/HybridTile.java
Fix potential memory leak

Change-Id: I739851e3339fb8d97a5f34f36bedb9052384ee92
QuickSettings: cleanup
Removed unnecessary references to QuickSettingsContainerView, LayoutInflater
Tile layout is set by constructor

Change-Id: Ied57bf6613594864db0201c2af514fbe4bb651ed

Conflicts:
	packages/SystemUI/src/com/android/systemui/quicksettings/DesktopModeTile.java
	packages/SystemUI/src/com/android/systemui/quicksettings/DockBatteryTile.java
	packages/SystemUI/src/com/android/systemui/quicksettings/LteTile.java
	packages/SystemUI/src/com/android/systemui/quicksettings/ProfileTile.java
	packages/SystemUI/src/com/android/systemui/quicksettings/QuietHoursTile.java
	packages/SystemUI/src/com/android/systemui/statusbar/phone/QuickSettingsController.java
QS/PW: Check for mobile data instead of telephony permissions (1/2)

For QuickSettings and Power Widget check if there is
ConnectivityManager.TYPE_MOBILE network avaialbe directly instead of relying
on a checking for the PackageManager.FEATURE_TELEPHONY permission.  Some
devices like tilapia (Nexus 7 GSM) has mobile data but does not set the
telephony permission.

Patchset 2:
   	- Use ConnectivityManager.isNetworkSupported() instead of checking for a null
	  value returned from ConnectivityManager.getNetworkInfo(). Thanks
	- Have MobileNetworkTile use the QSUtil deviceSupportsMobileData method

Change-Id: I71bd6217cbe08622f805de4ae30a87df11340f5f
Fixes: CYAN-803

Conflicts:
	packages/SystemUI/src/com/android/systemui/statusbar/phone/QuickSettingsController.java
Build fixes

Change-Id: I5245b2317a3f2f3d4df73df60200e9b2dc7f5410
HybridTile: layout ID

Change-Id: Ia3b5d84c17bc589a2c9e38ceef708119444f569c
Merge remote-tracking branch 'upstream/jellybean' into HEAD

Conflicts:
	core/java/android/provider/Settings.java

Change-Id: I6db69dd14cb9f9d86c2dbf1e27de584b173e5797