Policy: fix keyguard statusbar showing while in ext desktop, fixes it in
apps like currents as well

Change-Id: Id3e4b99d60c33e4050e0e97c365d1ae739f603ec
allow widgets to minimize in extended desktop

Change-Id: I666f61644386ff10631185324f445a750571b104
derp

Change-Id: I83441eb7dbd8daedde5bdf4247d4b5445a8886c0
-Typo-

Change-Id: I5179ccbe2f3a1e16fb6d43011016a8769655d335
Applying ChannelScrolling to remove calculateDragAngle

To avoid angle calculation changed the logic to use virtual areas.
When try to drag or pan, check where the current touch point locates
and determine how to drag a page.

Change-Id: Id9bd08a69c4ac93ff385c8088e6c16bed5dc5f88
Signed-off-by: kiwon <kiwon98.lee@samsung.com>
Account malloc mmaped pages as native heap.

Currently when malloc uses a page rather than brk the heap gets accounted as
ashmem memory. Previously the memory would be accounted as unknown but since
[1] it gets accounted as ashmem. This change makes the accounting see this
memory as being native, ie the same kind of memory we associate with brk.

[1] https://android-review.googlesource.com/#/c/49583/3

Change-Id: I6f496cfeb590268d41d8e047b12cd5c90359e2b0
Merge "Fix ListView is not scrolled properly with arrows"

Change-Id: I682664789df2dea4b0a30de10d9b230bd75d748a
Merge "Recognize odex files in memory accounting."

Change-Id: I02735b77207fe2bb69dec91b5f624508eba957df
Track stack memory in MemoryInfo.

In /proc/pid/maps the main stack is identified as "[stack]". In Linux 3.4
thread stacks are identified as "[stack:<tid>]" where <tid> is the thread ID of
the thread using that stack. Add support in MemInfo's otherStats to track
memory being used by the stack.

Add sanity check on the length of the otherStats array.
Add detail messages to two null pointer exceptions.

Bug: 8265251

Change-Id: I2b228b147da9bdc5c7a4d825dfc628fcc7923927
Enable vecorized bitmaps for all devices

Change-Id: I2231234adf115cf7f83c4b2778b53461f7a5587e

Conflicts:

	core/jni/Android.mk
Settings: cleanup

Change-Id: Ib7207317ed1e59721194d4fff0e52949aa6ab113
FIX Null Pointer Exception on dialog cancel

Null Pointer Exception occurs because mWebViewCore instance
is made to null while calling destroyJava(). When
1.webview hosting activity goest to background, without calling webview onPause().
2. If app is launched again (having launchmode:singletask ) and another activity (not  webview hosting) comes on top top.
3. It destorys the previous activity holding webview which internally tries to cancel the dialog, but webviewcore instance is null.
Null pointer exception is raised.

Change-Id: Idbcd30d0b0d4a35819444bbaa5c73cced8bb35a3
Signed-off-by: Amit Kumar <amitkecian@gmail.com>
revert to old data/signal null icons

Change-Id: Ia071717100c217b66c0498e174558b3c31f86b9b
update preloaded-classes

Remove some preloaded-classes and fix typo for deleting log messages
as the followings during booting.

W/Zygote  (  163): Class not found for preloading: android.bluetooth.
BluetoothAudioGateway
W/Zygote  (  163): Class not found for preloading: android.bluetooth.
HeadsetBase
W/Zygote  (  163): Class not found for preloading: undroid.content.Ab
stractThreadedSyncAdapter$SyncThread

Change-Id: Id02e0cccaeb150f48e12d67b2d691df828842e4c
prevent policy from spamming logs

Change-Id: I948881c304a380da6b3f5a497670aafc34b7818c
conditional ime switcher

Change-Id: I4fdc63ca65119172ab99f9220f457352b771b1d3
enable usb audio hot plugging

Change-Id: I527e0976b6cadacb67084348ffe2de192247529a
Correct the target app token for input method window

The root cause is:
There is a defect in window manager service: When a new
activity that can be ime target is added into window manager
but the Z order of input method window don't need to be
changed, then the target app token of input method window
would not be updated to new one. This defect may cause that
the layer of input method window is calculated incorrectly.

The solution:
Correct the target app token for input method window.

Change-Id: I008311e3c9b1cf5fc320b614d8675c183c506d50
Fix race condition in ActivityThread.completeRemoveProvider()

This should solve the problem when exceptions like below are thrown:
java.lang.IllegalStateException: unstableCount < 0: -1
android.os.Parcel.readException()
android.os.Parcel.readException()
android.app.ActivityManagerProxy.refContentProvider()
android.app.ActivityThread.releaseProvider()

Change-Id: I97ca9f7f0b57221bc3aa41727936292cc79b92c9
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