GitLab

Bug 28592402

Change-Id: I857e46c9ab3ffae0d96923d665d13a4128a6cafa
(cherry picked from commit 9a8c42a7)

This should be reverted when all system services have been cleaned up to not
do this. A process looking up a service while running in the background will
see the service registered by the active user (assuming the service is
registered on every user switch), not the service registered by the user that
the process itself belongs to.

BUG: 30795333
Change-Id: I1b74d58be38ed358f43c163692f9e704f8f31dbe
(cherry picked from commit e6bbe69b)

Prevent apps from registering services without relying on selinux checks.

Bug: 29431260

Change-Id: I38c6e8bc7f7cba1cbd3568e8fed1ae7ac2054a9b
(cherry picked from commit f03ba2c0)

Bug 29983260

Change-Id: Ib6e1cb8ae279010c5e9960aaa03513f55b7d873b

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

Bug: 28395952

Change-Id: Ia1a6198c0f45165b9c6a55a803e5f64d8afa0572

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

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 c1114610)

Bug 27555981
Bug 27556038

Change-Id: I436b6fec589677d7e36c0e980f6e59808415dc0e

Bug 27046057

Change-Id: Iede7c92e59e60795df1ec7768ebafd6b090f1c27

Bug 26877992

Change-Id: Ibbf4b1061e4675e4e96bc944a865b53eaf6984fe

Bug 27046057

Change-Id: Id7bd8cf95045b497943ea39dde49e877aa6f5c4e

Bug: 26338109
Change-Id: I8a979469bfe1e317ebdefa43685e19f9302baea8

Bug: 26338113
Change-Id: I019c4df2c6adbc944122df96968ddd11a02ebe33

Initial sensor flush at subscription is a mechanism to avoid sensors
to get stale samples before subscription happens. However, there is a
slight chance that a most recent sample will be lost during the flush
process. This is OK for continuous sensors but problematic in
on-change sensor as on-change event does not come continuously and
a lost event can cause inconsistent state in client. Flush at
subscription of on-change sensor is disabled in this CL to avoid new
important on-change event to be discarded during the initial flush
process.

Bugs: b/24647069
      b/25241873
      b/24804819
     
Change-Id: Ibda099c6b9f5fb6e200f13cf13a850b0026e9e7c

DO NOT MERGE: fix build try #2 am: 778b6f49 am: 034bc179  -s ours am: dbc9a478  -s ours am: a2685ebb am: 1d94a1d0  -s ours
am: bce101e7

* commit 'bce101e7':
  DO NOT MERGE: fix build try #2

* changes:
  Maintain Parcel ABI
  Revert "Revert "Track ashmem memory usage in Parcel""

DO NOT MERGE: fix build try #2 am: 778b6f49 am: 034bc179  -s ours am: dbc9a478  -s ours am: a2685ebb
am: 1d94a1d0  -s ours

* commit '1d94a1d0':
  DO NOT MERGE: fix build try #2

am: a2685ebb

* commit 'a2685ebb':
  DO NOT MERGE: fix build try #2

am: dbc9a478  -s ours

* commit 'dbc9a478':
  DO NOT MERGE: fix build try #2

resolve merge conflicts of 834ac204 to klp-modular-dev. am: 7f1ea80d am: fa632f6a am: 9ec97873 am: 1b28b05d
am: 0370a03b

* commit '0370a03b':
  DO NOT MERGE: fix build breakage

am: 034bc179  -s ours

* commit '034bc179':
  DO NOT MERGE: fix build try #2

add number constraint for samples per MotionEvent am: 5d17838a am: 72c8ca4a am: 9964d838 am: 90dc6dc8 am: 9830f11d
am: a82ace99

* commit 'a82ace99':
  add number constraint for samples per MotionEvent

resolve merge conflicts of 834ac204 to klp-modular-dev. am: 7f1ea80d am: fa632f6a am: 9ec97873
am: 1b28b05d

* commit '1b28b05d':
  DO NOT MERGE: fix build breakage

am: 778b6f49

* commit '778b6f49':
  DO NOT MERGE: fix build try #2

am: 9ec97873

* commit '9ec97873':
  DO NOT MERGE: fix build breakage

am: fa632f6a

* commit 'fa632f6a':
  DO NOT MERGE: fix build breakage

am: 7f1ea80d

* commit '7f1ea80d':
  DO NOT MERGE: fix build breakage

Makes sure we don't change the memory layout of the Parcel class
to maintain binary compatibility with prebuilts linking against
libbinder.

Bug: 25004154
Change-Id: I656687497f08bb85cefda796aafa2341e601e30a

This reverts commit 6880307e.

Bug: 25004154
Change-Id: I9b432d1ebc39f3bbcd7afdefc403f0fb6ced8158

Bug: 23905002
Change-Id: Ic7262861af91a8fff27692c0f68761cb3ab12aa3

add number constraint for samples per MotionEvent am: 5d17838a am: 72c8ca4a am: 9964d838 am: 90dc6dc8
am: 9830f11d

* commit '9830f11d':
  add number constraint for samples per MotionEvent

This reverts commit e2f499fb.

Bug: 25169267
Bug: 25191602
Bug: 25004154
Change-Id: I24bb0da4e8739ee5a0c251e4adac9904827144e0

On klp-dev, UINT16_MAX isn't available unless __STDINT_LIMITS
is defined, which it's not for this code. This isn't relevant
for later branches due to bionic commit
e2a292d278b94fec3d078b1f1b27c1f89942c276

Don't use UINT16_MAX when we can just hardcode 65535.

Bug: 23905002
Change-Id: Ia1fd0f749cb7a4d19866075abc28ed6960424e54

fix klp-dev only build breakage.

  frameworks/native/libs/input/Input.cpp: In member function 'android::status_t android::MotionEvent::readFromParcel(android::Parcel*)':
  frameworks/native/libs/input/Input.cpp:494:47: error: 'UINT16_MAX' was not declared in this scope

Bug: 23905002
Change-Id: I4b6b864ca64d39a8873d045a61e0ddaea2ab9109

am: 90dc6dc8

* commit '90dc6dc8':
  add number constraint for samples per MotionEvent

am: 9964d838

* commit '9964d838':
  add number constraint for samples per MotionEvent

am: 72c8ca4a

* commit '72c8ca4a':
  add number constraint for samples per MotionEvent

am: 5d17838a

* commit '5d17838a':
  add number constraint for samples per MotionEvent

Bug: 25004154
Change-Id: Id9d5656dd0605f1b50525596b75601309f67ebdc