GitLab

applied fix from https://android-review.googlesource.com/#/c/198885/libs/binder/Parcel.cpp to resolve avc :denied {ioctl} logcat errors

Change-Id: I2ed003d78eb6027cef396b4f4d2db2fe1c047d9c
Signed-off-by: Zikim,Wei <wzq@rock-chips.com>

Android 6.0.1 Release 55 (MXC89K)

Hardware revisions of mali_t760 in rk3288 and rk3288w are different,
so the mali_so's are different.
But the product_department requires that rk3288 and rk3288w must used a unified set of images.

With this commit, we can put the two mali_so's in a unified system_img,
in the path /system/vendor/lib/egl/rk3288/libGLES_mali.so and
./vendor/lib/egl/rk3288w/libGLES_mali.so,
and the image can support rk3288 and rk3288w both.

This only extends the process of searching libGLES_mali.so,
the default process has a higher priority.

Change-Id: Ib904e178e225a7848c5dc91378a1d58adad7137f
Signed-off-by: chenzhen <chenzhen@rock-chips.com>

Change-Id: I3d44295146da8f5d54a0cacf1f033b052482fa46

Conflicts:
	libs/gui/Surface.cpp

Change-Id: I183aad080a8a822191aaaddcd4ba3e3bc1d4410b
Signed-off-by: Zikim,Wei <wzq@rock-chips.com>

Change-Id: I1f8b7c6a831eef50151bd143e0ea2e789c74d20b
Signed-off-by: Zikim,Wei <wzq@rock-chips.com>

Change-Id: I1fd0c7703ca1351fde07d96f7c2b20df26de288e
Signed-off-by: Zhiqin Wei <wzq@rock-chips.com>

Android 6.0.1 release 46

Due to more complex window layouts resulting in lots of overlapping
windows, the policy around FLAG_WINDOW_IS_OBSCURED has changed to
only be set when the point at which the window was touched is
obscured. Unfortunately, this doesn't prevent tapjacking attacks that
overlay the dialog's text, making a potentially dangerous operation
seem innocuous. To avoid this on particularly sensitive dialogs,
introduce a new flag that really does tell you when your window is
being even partially overlapped.

We aren't exposing this as API since we plan on making the original
flag more robust. This is really a workaround for system dialogs
since we generally know their layout and screen position, and that
they're unlikely to be overlapped by other applications.

Bug: 26677796
Change-Id: I9e336afe90f262ba22015876769a9c510048fd47

This reverts commit 3d13632b.

Change-Id: I3e081c4513b7719c82e2055e1fb9b153c0709755

use LCDC composer and full screen when external.

Change-Id: I9e256c9cfeefc23f1cbb2806977c6e421e135ad7

bail out if dup() fails, instead of creating an invalid native_handle_t

Bug: 28395952

Change-Id: Ia1a6198c0f45165b9c6a55a803e5f64d8afa0572
(cherry picked from commit 1de7966c72981aebc3c7f9978ab129678ac89258)

Android 6.0.1 release 43 (MOB30J)

Change-Id: I0235f090135486971cc6adc429e776c90cad1167

In the place of huangds.

Change-Id: Id03ad7f3903c5cabd779ece9d295e2dabe86035e
Signed-off-by: chenzhen <chenzhen@rock-chips.com>

Due to more complex window layouts resulting in lots of overlapping
windows, the policy around FLAG_WINDOW_IS_OBSCURED has changed to
only be set when the point at which the window was touched is
obscured. Unfortunately, this doesn't prevent tapjacking attacks that
overlay the dialog's text, making a potentially dangerous operation
seem innocuous. To avoid this on particularly sensitive dialogs,
introduce a new flag that really does tell you when your window is
being even partially overlapped.

We aren't exposing this as API since we plan on making the original
flag more robust. This is really a workaround for system dialogs
since we generally know their layout and screen position, and that
they're unlikely to be overlapped by other applications.

Bug: 26677796
Change-Id: I9e336afe90f262ba22015876769a9c510048fd47
(cherry picked from commit cdcd8f2b25a4bf32bb7506fc98ba541d274c9a31)

Due to more complex window layouts resulting in lots of overlapping
windows, the policy around FLAG_WINDOW_IS_OBSCURED has changed to
only be set when the point at which the window was touched is
obscured. Unfortunately, this doesn't prevent tapjacking attacks that
overlay the dialog's text, making a potentially dangerous operation
seem innocuous. To avoid this on particularly sensitive dialogs,
introduce a new flag that really does tell you when your window is
being even partially overlapped.

We aren't exposing this as API since we plan on making the original
flag more robust. This is really a workaround for system dialogs
since we generally know their layout and screen position, and that
they're unlikely to be overlapped by other applications.

Bug: 26677796
Change-Id: I9e336afe90f262ba22015876769a9c510048fd47

Change-Id: Ie1a6d8e725135cad22e2fb40c355c45eccc72262
Signed-off-by: huweiguo <hwg@rock-chips.com>

Providing AOSP software implementation of Geomag Rotation Vector, Game
Rotation Vector and Gravity sensors for platforms that does not have
hardware implementation of these sensors but do have primitive sensors
(accelerometers, gyrometers and magnetometers).

Previously, AOSP Gravity sensor is enabled only when all primitive sensors are
available. This is changed so that AOSP Gravity will be available even
no magnetometer is in the device.

Related bug/feature request:
    * b/17508800
    * b/22610016

TEST=Pass CTS sensor tests with fix ag/207083

Change-Id: I4e2d3e544884047d66e7fdbce2282f1f8234eae9
(cherry picked from commit f66684a6fb2a2991e84a085673629db2a0494fc6)

Sending transaction to freed BBinder through weak handle
can cause use of a (mostly) freed object.  We need to try to
safely promote to a strong reference first.

Change-Id: Ic9c6940fa824980472e94ed2dfeca52a6b0fd342
(cherry picked from commit c11146106f94e07016e8e26e4f8628f9a0c73199)
(cherry picked from commit ce156f60adb32c7cbebe50e313f51e564f93fe99)

Bug 27555981
Bug 27556038

Change-Id: I436b6fec589677d7e36c0e980f6e59808415dc0e
(cherry picked from commit 93c617fd2a5e7910e0ba5c0ed6da152d30920679)

Sending transaction to freed BBinder through weak handle
can cause use of a (mostly) freed object.  We need to try to
safely promote to a strong reference first.

Change-Id: Ic9c6940fa824980472e94ed2dfeca52a6b0fd342
(cherry picked from commit c11146106f94e07016e8e26e4f8628f9a0c73199)

Bug 27555981
Bug 27556038

Change-Id: I436b6fec589677d7e36c0e980f6e59808415dc0e

Providing AOSP software implementation of Geomag Rotation Vector, Game
Rotation Vector and Gravity sensors for platforms that does not have
hardware implementation of these sensors but do have primitive sensors
(accelerometers, gyrometers and magnetometers).

Previously, AOSP Gravity sensor is enabled only when all primitive sensors are
available. This is changed so that AOSP Gravity will be available even
no magnetometer is in the device.

Related bug/feature request:
    * b/17508800
    * b/22610016

TEST=Pass CTS sensor tests with fix ag/207083

Change-Id: I4e2d3e544884047d66e7fdbce2282f1f8234eae9
(cherry picked from commit f66684a6fb2a2991e84a085673629db2a0494fc6)

Merge branch 'rk32/mid/6.0/develop' of ssh://10.10.10.29:29418/android/platform/frameworks/native into HEAD

(cherry picked from commit 9199353be5c210038d0d02075062729d5d40cb84)
Signed-off-by: Hans Yang <yhx@rock-chips.com>

Conflicts:
	include/android/keycodes.h
	services/inputflinger/InputReader.cpp

Change-Id: I7c13513ded2f40ef6aa91684e8bda75aa1fce509

(cherry picked from commit bdebed5c5472211818cf7573d6bfe33807e40058)

Change-Id: I6cba0c12a225723bc6dfb6c0a80c0ec5590d4a2f