When in pointer capture mode, mouse pointer disappears and
further mouse events are dispatched to the focused view
in the window which has requested capture.
The captured events have the source SOURCE_MOUSE_RELATIVE
belonging to SOURCE_CLASS_TRACKBALL. They are
dispatched through dispatchCapturedPointerEvent /
onCapturedPointerEvent. There is also a new listener.
Pointer capture mode may only be granted to a currently
focused window, and will be canceled upon a window focus change.
Test: cts-tradefed ... --test android.view.cts.PointerCaptureTest
Bug: 30897034
Change-Id: I6e5934aa415ac2b6dda1cee173d0f23e5021af84
The getService() and registerAsService() methods of interface objects
now have default parameters of "default" for the service name. HALs
will not have to use any service name unless they want to register
more than one service.
Test: builds
Bug: 33844934
Change-Id: Id22d27d7e401de426b1a236067c1b4c7f6c99a3e
The getService() and registerAsService() methods of interface objects
now have default parameters of "default" for the service name. HALs
will not have to use any service name unless they want to register
more than one service.
Test: builds; verify HAL still works
Bug: 33844934
Change-Id: I2f296bc40e36082d8889d2796cf839cb41a21fc3
The getService() and registerAsService() methods of interface objects
now have default parameters of "default" for the service name. HALs
will not have to use any service name unless they want to register
more than one service.
Test: builds; verify HAL still works
Bug: 33844934
Change-Id: I7ad730bc5b52b9bd3c63410f6f926cbc08d0b73c
The getService() and registerAsService() methods of interface objects
now have default parameters of "default" for the service name. HALs
will not have to use any service name unless they want to register
more than one service.
Test: builds; verify HAL still works
In support of b/33844934
Change-Id: Iaf379982c1e8e03b46a1fddf5f047c70cd3e6938
The getService() and registerAsService() methods of interface objects
now have default parameters of "default" for the service name. HALs
will not have to use any service name unless they want to register
more than one service.
Test: builds; verify HAL still works
In support of b/33844934
Change-Id: Icff606bb704d2ee60e1fa8fbbb57ff0cc6db9bc1
Added "Tow Known" as a possible gnss measurement state. As well added Automatic Gain Control (AGC)
to allow jammer detection. Also added the GNSS carrier frequeny to SV status. Also added vertical
GPS position uncertainty, speed uncertainty and bearing uncertainty. Also propagate locaton new
fields to geofence engine.
Test: Existing unit tests still pass.
Change-Id: I472b2fd2516cb7614877dea4bb054a34f50844dc
Update to be compliant with the HIDL change to pass the nanoapp's binary
data via struct NanoAppBinary, which contains explicit fields parsed out
of the common nanoapp header, and the rest of the data after the header
passed separately.
Bug: 34182159
Test: run hello world context hub GTS test
Change-Id: I9e961c0f57567b3061302f193e4907332dcbad09
Update nativeSendMessage() to simplify the logic for mapping the hub
handle to hub ID, and also update the types of some variables to ensure
their correctness. Also, rewrite unnecessary alias declarations as
simpler using declarations.
Test: run hello world context hub GTS test
Change-Id: I8f9154a0ff2c81eff9eb509e9b0936e34569ec55
Removal of legacy FlpHardwareProvider jni,
and minimal java implementation.
Restoration of GNSS batching functionality,
with default implementation using
fused_location.h supporting libraries, would
continue in the Treble aligned GNSS HAL.
Bug: 31974439
Test: Ensured that system boots cleanly, and FLP HAL is not used
and that GPS operation (GMaps & 3rd party test app)
still looks fine.
Change-Id: I7b3834ddd4e754576af30cdbe2a92f53947d85a7
Adding a placeholder for nanoApp abort handling.
The placeholder is necessary to check in HAL changes.
It does not do anything interesting for now.
Test: Build compiles.
Change-Id: Iaf1220c73f28ccd4cb4e5e3830e7988b45c4d899
This change saves and loads a different brightness setting when the user
goes in and out of VR Mode.
Test: runtests frameworks-core
Test: Turn vr mode on and change brightness (should remain separate from
normal brightness)
Bug: 30984614
Change-Id: If3c3e81b592e0c6fd037e5783559683e5cb58379
Bug: 31974439
Test: Verified that threads that are not attached to JNI
gets attached and on exit, gets detached.
Change-Id: Ib089720998131ceb107fa5b318a0fcbdf91076ec
This change saves and loads a different brightness setting when the user
goes in and out of VR Mode.
Bug: 30984614
Change-Id: If3c3e81b592e0c6fd037e5783559683e5cb58379
This change saves and loads a different brightness setting when the user
goes in and out of VR Mode.
Bug: 30984614
Merged-In: Ie5578bbd6ea346f0eb34fe4abbfd604a5d7c0c93
Change-Id: Ie5578bbd6ea346f0eb34fe4abbfd604a5d7c0c93
