am: 78a2b61782 -s ours
am skip reason: change_id If086c50ae803b384691f709057bceeac2fc1d9d5 with SHA1 387dc0efd1 is in history
Change-Id: I66e67c4a085300d2fea3e58e6c45dbd1a4864189
am: 9ed67f1ba6 -s ours
am skip reason: change_id If086c50ae803b384691f709057bceeac2fc1d9d5 with SHA1 32f799da52 is in history
Change-Id: I3e0d043ac5dd0f2656227d85fe22c80c20505a00
am: 01676b2564 -s ours
am skip reason: change_id If50f68df9579f84bddc9d70a0a30cd73f4485e96 with SHA1 e2e5a31362 is in history
Change-Id: I8de0517621facad6f880685b67979d235a3fc815
am: 63150de91d -s ours
am skip reason: change_id Ia0b6a56859889d538e21f807a88bc5217d89e64a with SHA1 cf7b336020 is in history
Change-Id: I993b5534a72d78070797aa1aedac27aa685e6190
This is only for the load and save Carrier ID field.
Bug: 130875004
Test: build, bootup, unit test
Change-Id: Id48587ca26fc9dc0f7678b5a449e2d39a2e90dae
The data and activation broadcasts were guardrailed using
elapsedRealtime of the *LogEvent*. However, it's possible to use
incorrect timestamps, and it's also possible that we could process
events that are old, which would result in the broadcast getting sent
too frequently. To fix this, we should use the current elapsedRealtime
instead of the LogEvent's elapsedRealtime.
I can remove the config activation broadcast if we think we should hold
off on it.
Test: bit statsd_test:*
Bug: 143155387
Change-Id: I4c58d2558d6ba3b4fd15a4a619d6f80a7bd7113f
am: 01f3aa4fff -s ours
am skip reason: change_id I3c678522e70b5d89a6a5a8f6bdb1e3fd91ca8aee with SHA1 61f098ecaf is in history
Change-Id: Ia293151feff2d0fa112867d30a818bf475a991e7
Original symptom: Cuttlefish devices would crash when the "recent apps"
tray was swiped up from the bottom.
Root cause: Raising the "recent apps" tray triggers a vibration. Close
to the bottom of the call stack responsible for this action in
VibratorService is the native function vibratorPerformEffect(). The
Java Language signature for this function has a long as the type of the
second parameter, as does the JNI signature that is registered with the
environment. The native function, however, uses an int type for this
parameter. As a result, when the arguments are passed via the stack on
x86 devices the high bits of the second long argument are read as the
contents of the third argument, which is a jobject reference. When the
code attempts to convert this NULL local reference into a global
reference the JNI code aborts the runtime for the process. Because the
VibratorService is part of the SystemServer, when it crashes the Zygote
is notified and restarts the entire shell.
Why this wasn't an issue on ARM devices: ARMs calling conventions pass
many of a function's arguments via registers instead of via the stack.
This means that the long argument is passed in a register, preventing it
from stomping on any other arguments. When the native function uses the
argument it simply reads the lower bits from the register and ignores
the higher bits.
Why this wasn't previously an issue on X86 hosts: ag/9158254 introduced
a new parameter to the vibratorPerformEffect() function. This new
parameter is located after the mis-typed parameter and will be aliased
to the high bits of the mis-typed long argument.
Fix: Correct the type signature of the native vibratorPerformEffect()
function.
Bug: 143082450
Test: Build -> start cuttlefish -> raise recent apps tray -> no crash
[adelva: port to AOSP to close potential ASAN issues]
Change-Id: If50f68df9579f84bddc9d70a0a30cd73f4485e96
Merged-In: If50f68df9579f84bddc9d70a0a30cd73f4485e96
to be configurable.
Bug: 143372960
Test: manual - took before and after videos
Merged-In: Ia0b6a56859889d538e21f807a88bc5217d89e64a
Change-Id: Ia0b6a56859889d538e21f807a88bc5217d89e64a
