| 5c091dc9449b583e18656a8850a61f557dfcc945 |
|
20-Jul-2017 |
Steven Moreland <smoreland@google.com> |
Merge "frameworks/base: use proper nativehelper headers"
am: 826eafd958
Change-Id: I36f10ff4d963284a313f1cc5b368f82549a4adb2
|
| 2279b2534272282a5b5152723235da397e49195c |
|
19-Jul-2017 |
Steven Moreland <smoreland@google.com> |
frameworks/base: use proper nativehelper headers
libnativehelper exports headers under nativehelper. These were
available before incorrectly as global headers in order to give
access to jni.h.
Test: modules using frameworks/base find headers
Bug: 63762847
Change-Id: I0f9f231acdebe460f279135462f43d3e32eff64d
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 34a0cdb98eb5561774ea4e7b3b602aad80c4a3cc |
|
09-Jun-2017 |
Jorim Jaggi <jjaggi@google.com> |
Properly run window animations at vsync-sf (1/2)
- Add new Choreographer instance that runs on vsync-sf
- Use this new Choreographer for WindowAnimator, and remove all
the hacks around it
Test: Open apps and close apps, notice no stutter
Test: Screen zoom animations
Test: go/wm-smoke
Bug: 36631902
Change-Id: I988ae25645effc3ac20efa7cb9b68f23444da0d0
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| e46af37e3e41ea8bdd3eacffb8c32b3bc6f9d254 |
|
04-Oct-2016 |
John Reck <jreck@google.com> |
DisplayEventReceiver -> @FastNative
Test: make && boot
Change-Id: Id75648a2398a13c5af24eabc217bdef778618872
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| c86a2e325ecb908ff7a98385f9852db123fc7ce6 |
|
23-Jun-2016 |
John Reck <jreck@google.com> |
Merge \"Remove FD from the right Looper\" into nyc-dev
am: db13dd41a9
Change-Id: I451ef3649426d9b8ea1bf15e388d0efa82dae442
|
| ac04f4e69a6de138c5afc668a2c89b7da7ff4e6a |
|
23-Jun-2016 |
John Reck <jreck@google.com> |
Remove FD from the right Looper
Bug: 29586513
Also gives BackdropFrameRenderer a direct-destroy
of Choreographer since it's hammering on new Threads
and we don't want to wait for the GC to release
FDs.
Change-Id: Id2ec0af2ee4d5304961c4ab87a104ccb92f35fc2
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 85ea32b02a2b281ee5092ef8c31c44a0ba3452a4 |
|
16-Mar-2016 |
Ben Wagner <bungeman@google.com> |
Switch frameworks/base/core/jni from gcc to clang.
Switch from gcc to clang and fix errors detected.
The immediate motivation is that gcc with libc++ stl does not use
'explicit' in the stl, causing issues for use of unique_ptr.
The longer term motivation is to fully move to clang.
BUG=22414716
Change-Id: If77436c1e7601f20289603862be33b85880ab4bd
(cherry picked from commit 60b1c8ef860b8cd5a1fa453a8951d6e8d7c44734)
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 3d3fe5026a6a3e951ef56ad16a100b8d5ae84574 |
|
04-Dec-2015 |
Michael Wright <michaelwr@google.com> |
Add choreographer API to the NDK.
Change-Id: Icb8cffd3cd3bd06814466be72db3e26f6a62cbc6
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 0dba1f611410e5075a910fb73ff3d3c703bbc5ce |
|
05-Oct-2015 |
John Reck <jreck@google.com> |
FastJNI canvas
Change-Id: Iae33a4785e52efe6f8bbe5bee258f4df830feceb
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| b57dd722f1dc0663417da37d3a82f8283ad3c982 |
|
24-Sep-2015 |
Elliott Hughes <enh@google.com> |
resolved conflicts for a884d81e to stage-aosp-master
Change-Id: Ice485967fa96f13786024b6939b826638e906ff0
|
| 76f6a86de25e1bf74717e047e55fd44b089673f3 |
|
19-Sep-2015 |
Daniel Micay <danielmicay@gmail.com> |
constify JNINativeMethod function pointer tables
Change-Id: I4036c924958221cbc644724f8eb01c5de3cd7954
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 1f2c7688c1f673790d61645632ae5e1838f021a4 |
|
03-Jun-2015 |
Michael Wright <michaelwr@google.com> |
Add new `hid` command.
This allows the shell user to inject HID events.
Change-Id: I37faff576299ff14092b61ed39f2a1c086f672a5
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 3b4049e79b1ea2872891cc0e87146e146111d502 |
|
18-Apr-2015 |
Jeff Brown <jeffbrown@google.com> |
Fix leaks due to GC circular references.
The DisplayEventReceiver and SensorManager event queue both get
leaked when the Looper thread they are attached to dies because
the Java object holds a strong reference to its native peer and
meanwhile the native peer holds a strong reference to the Java
object through JNI.
Fixed the issue by indirecting through a weak reference as was
done for InputEventReceiver some time ago.
Bug: 12455729
Change-Id: I3d80a2a190192d1a2981bf5ae0cad30f0f7688a5
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 46d8444631b4b1253a76bfcc78a29d26014d022f |
|
19-Nov-2014 |
Dan Albert <danalbert@google.com> |
Fix clang warnings in core/jni.
There are a few bugs in here too (mostly people expecting + to
concatenate C strings) :(
Change-Id: I0a243c05c4ea8b56e84896f37814d0fbea4c39d5
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 987f79f60bb1f0a4bcd3ef22e57301c743f0b94f |
|
19-Nov-2014 |
Andreas Gampe <agampe@google.com> |
Frameworks/base: Replace LOG_FATAL_IF in core/jni
Do not use LOG_FATAL_IF in JNI setup. This is one-time on startup
and important enough to always check.
Add a header with common helper definitions. Move to inlined functions
instead of macros to clean up the code.
Change-Id: Ib12d0eed61b110c45d748e80ec36c563e9dec7e5
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 0f0b4919667f418b249c497f5ad3e83fdf4437e5 |
|
12-Nov-2014 |
Andreas Gampe <agampe@google.com> |
Frameworks/base: Wall Werror in core/jni
Turn on -Wall -Werror in core/jni. Fix warnings.
Clang TODO: For GCC we need to turn off Wunused-but-set-variable in
the GL bindings. However, Clang doesn't have that warning and thus
complains about an unknown pragma. It is necessary to make the
pragma #ifdef-ed on the compiler being GCC.
Change-Id: I14cab48d45c2771eef0432082356c47ed44a3d7f
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 27285821b74ca9bc381d33f40028f06ff0f85e0c |
|
18-Dec-2013 |
Ashok Bhat <ashok.bhat@arm.com> |
AArch64: Use long for pointers in DisplayEventReceiver
For storing pointers, long is used as
native pointers can be 64-bit.
In addition, some minor changes have been done
to conform with standard JNI practice (e.g. use
of jint instead of int in JNI function prototypes)
Change-Id: I3c0855373c0e4bedc172adb82b103586de9219dc
Signed-off-by: Ashok Bhat <ashok.bhat@arm.com>
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 82b007d7572dceb0981b269338bd1ac6c40496c5 |
|
13-Dec-2013 |
Brian Carlstrom <bdc@google.com> |
Track Looper decoupling from ALooper
Change-Id: I54f4d36f105e60eaaa453ae60f591d634c681fd7
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 16823bd611689e9b5c0e1b675fee43579f85612a |
|
19-Nov-2012 |
Jesse Hall <jessehall@google.com> |
Process all display events in order
Display events in each batch received from IPC were being processed in
reverse order, and stopped after the first vsync event (latest
chronologically) was handled. This makes perfect sense for vsync
events, but is broken for hotplug events.
Now we process them all in order, handling all except vsync as we see
them. For vsync events, only the last is reported.
Bug: 7491120
Change-Id: I04528fea8f38c1013734d4aa92fb1955ac24d7cc
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| e87bf030766198bf5e1fe846167dba766e27fb3f |
|
21-Sep-2012 |
Jeff Brown <jeffbrown@google.com> |
Support HDMI hotplug.
Bug: 7206678
Change-Id: Ia5212b16658a5f5a2ccf8528eca7bebd45ca857a
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 80a1de1007ddc62e1af2a4746008f499145aeaab |
|
01-Jun-2012 |
Jeff Brown <jeffbrown@google.com> |
Use sp<LooperCallback> to fix race causing dangling pointer.
Bug: 6559630
Change-Id: I9b9c76577779841006f9c024a80685ba8b7cd0e1
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 603b44589682db3ff33ade172facb0c5e309f1be |
|
07-Apr-2012 |
Jeff Brown <jeffbrown@google.com> |
Ensure that apps crash if they throw exceptions.
Previously, if an app threw an uncaught exception in an input,
vsync or native activity callback, it would log the exception then
continue limping merrily along. In the case of input, it
could result in an ANR occurring because we had not drained
all of the pending input events and marked them as finished
(we only marked the most recent one finished).
Bug: 6304124
Change-Id: I87d76f7fd605e1a8af1237c66d8d62973080277e
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| bec0a8682c75a40df6d0dca17e23db2103a950f3 |
|
29-Mar-2012 |
Jeff Brown <jeffbrown@google.com> |
Refactor DisplayEventReceiver read loop.
Change-Id: I98ef802ec0ca48f768e3b0920e1b4b4f7f141050
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 58aedbc9bea13415e2d42cf7c9fe8a7efd243e66 |
|
14-Feb-2012 |
Jeff Brown <jeffbrown@google.com> |
Fix possible races in vsync infrastructure.
Applications sometimes crashed on exit due to the display event
receiver pipe apparently being closed while still a member of the
Looper's epoll fd set.
This patch fixes a few different possible races related to
the display event receiver lifecycle.
1. The receiver used to play a little dance with the Looper,
registering and unregistering its callback after each vsync
request. This code was a holdover from a time before the
surface flinger supported one-shot vsync requests, so we can
get rid of it and make things a lot simpler.
2. When the Choreographer is being accessed from outside the UI
thread, it needs to take great care that it does not touch
the display event receiver. Bad things could happen if the receiver
is handling a vsync event on the Looper and the receiver is
disposed concurrently.
3. It was possible for the Choreographer to attempt to dispose
the receiver while handling a vsync message. Now we defer disposing
the receiver for a little while, which is also nice because we
may be able to avoid disposing the receiver altogether if we find
that we need it again a little while later.
Bug: 5974105
Change-Id: I77a158f51b0b689af34d07aee4245b969e6260d6
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 3762c311729fe9f3af085c14c5c1fb471d994c03 |
|
06-Jan-2012 |
Steve Block <steveblock@google.com> |
Rename (IF_)LOGE(_IF) to (IF_)ALOGE(_IF) DO NOT MERGE
See https://android-git.corp.google.com/g/#/c/157220
Bug: 5449033
Change-Id: Ic9c19d30693bd56755f55906127cd6bd7126096c
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 8564c8da817a845353d213acd8636b76f567b234 |
|
06-Jan-2012 |
Steve Block <steveblock@google.com> |
Rename (IF_)LOGW(_IF) to (IF_)ALOGW(_IF) DO NOT MERGE
See https://android-git.corp.google.com/g/157065
Bug: 5449033
Change-Id: I00a4b904f9449e6f93b7fd35eac28640d7929e69
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 6779df2c28a68616134b1988f009221652d9f2ad |
|
07-Dec-2011 |
Mathias Agopian <mathias@google.com> |
Improve the VSYNC api a bit.
- add the ability to set the vsync delivery rate, when the rate is
set to N>1 (ie: receive every N vsync), SF process' is woken up for
all of vsync, but clients only see the every N events.
- add the concept of one-shot vsync events, with a call-back
to request the next one. currently the call-back is a binder IPC.
Change-Id: I09f71df0b0ba0d88ed997645e2e2497d553c9a1b
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|
| 0a0a1248cfc03940174cbd9af677bafd7280a3bc |
|
02-Dec-2011 |
Jeff Brown <jeffbrown@google.com> |
Add a new class to receive vsync events.
Change-Id: I4e384336d2813752a6d65fda6a77e86113a4510c
/frameworks/base/core/jni/android_view_DisplayEventReceiver.cpp
|