Documentation-only change that clarifies that in the case where the
client isn't compositing any of the layers, the buffer handle
provided to setClientTarget may be null, and that this should not be
treated as an error by the device.
Bug: 28569722
Change-Id: Ia5825eb0a80c7f838894642654db7d7be14a3b6b
am: 129b414d7a
* commit '129b414d7a587f9c1319694244708edb64700ec3':
Add definition of an event send from a nano app to host.
Change-Id: Ibf932c447429140b220abf130e138de5e428dfa9
am: 2235cac
* commit '2235cac9ba091bf6b06d7e3bead24fdb36fcf1b5':
[sensor] clarify definition of the uuid field
Change-Id: I752206e779ec11c70db15492bf2f61ea792264f5
am: f709758
* commit 'f7097585dca47b8124c5c9e31cd8d381f1c1c97d':
clarify set failure due to power down
Change-Id: Id5cb76e31e723496b8d73d406082f209b97dd5ba
- some properties can have separate propety control power state
and setting such property when it is powered off should
lead into returning error from hal. Define -ESHUTDOWN as
error code to use in such case.
bug: 28385609
Change-Id: I41c1519ad00b43a83f3aa4e5f0627d75d87a960b
- some cars supprot them as zoned property
- If there is only one global control, only one zone (VEHICLE_ZONE_ALL)
should be declared for the property.
- also fixed errata in VEHICLE_FLOAT_OUT_OF_RANGE_OFF
bug: 28285692
Change-Id: I35c81fef70d7dff080da9dd52c8d0bb97727e94b
Add a flag to enable() to start Bluetooth in restricted
mode. In restricted mode, all devices that are paired during
restricted mode are deleted upon leaving restricted mode.
Right now restricted mode is only entered while a guest
user is active
Bug: 27410683
Change-Id: I994a2933fd60301927ff2df65da634f81d4c9428
Add a flag to enable() to start Bluetooth in restricted
mode. In restricted mode, all devices that are paired during
restricted mode are deleted upon leaving restricted mode.
Right now restricted mode is only entered while a guest
user is active
Bug: 27410683
Change-Id: Ibededbdb832275db4b6e78af83d26754f8b5a9ec
HAL info structure can not have pointers
Ideally this would become variable sized array,
but JNI is expecting fixed-size array here,
so, define reasonable size (2), which fits all the
known cases.
Change-Id: I1752d5bef9db60570b03a8dc8e54da2277aca95a
Signed-off-by: Alexey Polyudov <apolyudov@google.com>
also define some helper macros to simpify app id definitions
Bug: 28086503
Change-Id: Ib04069889b24d057db5fcd3a408c845951cafeea
Signed-off-by: Alexey Polyudov <apolyudov@google.com>
- added HVAC_POWER_ON property
- added special INT / FLOAT OUT_OF_RANGE values for
max / min / off state
- added dump call for debugging: necessary for debugging
- clarified subscribe behavior for ON_CHANGE type
VNS will make additional get call for checking initial
state.
- added clarification on possible -EAGAIN for set call
- added mute flag to allow muting radio from android
bug: 27721415
bug: 28022648
bug: 27971383
bug: 27971578
Change-Id: Ie9a7334b86ab53174b91a4dc651fd87ca17af3d9
