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
Changed module name back to sensors.$(TARGET_DEVICE) to assure
proper load ordering.
Fix use of GNU old-style field designator extension and a couple
type-mismatched comparisons.
Bug: 28251347
Change-Id: I7cf6cc1f78085b8b254729cd8ec42bdb20ea3f81
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
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
We're defining the version of a hardware module (hw_module_t), not
a hardware device (hw_device_t). Thus, we only have 16 bits for
our version number, instead of 32, and need to use the
HARDWARE_DEVICE_API_VERSION macro.
Additionally, for the CONTEXT_HUB_DEVICE_API_VERSION_1_0 define,
which has 1 and 0 hard-coded in the name itself, we hard code 1 and 0
within its definition.
We create CONTEXT_HUB_DEVICE_API_VERSION which will change as we update
the major and minor version numbers in this header.
Bug: 27798362
Change-Id: I58b9751dfb1989fd6bb7fbfc01329494cd88130c
Key agreement (ECDH) has been punted from the N release, and a
configuration method has been added to support version binding.
Change-Id: Ia4aeee1bd7ab88cda3b9faa653470e608aa55942
Moved the init release calls in the vehicle-hal-tool.
I assume the correct sequence for a set is :-
VehicleNetworkService -> VehicleHAL vehicle_device_open
VehicleNetworkService -> VehicleHAL vehicle_device_init
VehicleNetworkService -> VehicleHAL vehicle_device_set
VehicleNetworkService -> VehicleHAL vehicle_device_release
bug: 27816048
Change-Id: I3ac37eaf69027824bc6247f25a99f27527c1a2b9
