| CHANGELOG.md (0346f11d884525c33c2c73350b5a6313c7a831a1) | CHANGELOG.md (508bb0cd2c78d06a73c2c85e96a7bcb6d807f847) |
|---|---|
| 1# Change Log 2All notable changes to this project will be documented in this file. 3 4The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) 5and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). 6 7--- 8 --- 29 unchanged lines hidden (view full) --- 38- SM: support storing bonding information for devices with identical IRK but different public addresses 39- GAP: restart advertising when private address changes 40 41### Changed 42- Drop iOS support 43- HCI: provide status instead of undocumented int error code and bool for API functions 44- GAP: local name, EIR data, class of device and default link policy can be updated at any time 45- L2CAP: provide status instead of undocumented int error code and bool for API functions | 1# Change Log 2All notable changes to this project will be documented in this file. 3 4The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) 5and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html). 6 7--- 8 --- 29 unchanged lines hidden (view full) --- 38- SM: support storing bonding information for devices with identical IRK but different public addresses 39- GAP: restart advertising when private address changes 40 41### Changed 42- Drop iOS support 43- HCI: provide status instead of undocumented int error code and bool for API functions 44- GAP: local name, EIR data, class of device and default link policy can be updated at any time 45- L2CAP: provide status instead of undocumented int error code and bool for API functions |
| 46- L2CAP: remote features not required for SDP connections |
|
| 46- RFCOMM: `RFCOMM_EVENT_PORT_CONFIGURATION` contains rfcomm_cid and remote flag, emitted for query config 47- RFCOMM: provide status instead of undocumented int error code and bool for API functions 48- RFCOMM: remote port configuration, line status, and modem status are sent by channel state machine 49- HFP: API functions return status code if appropriate 50- HFP: removed one parameter from hfp_ag/hf_activate_voice_recognition function, instead introduced hfp_ag/hf_deactivate_voice_recognition 51- HFP: merged legacy and enhanced Voice Recognition Activation (VRA) API. If available enhanced mode will be preferred. 52- HFP: separate events for activation (HFP_SUBEVENT_VOICE_RECOGNITION_ACTIVATED) and deactivation (HFP_SUBEVENT_VOICE_RECOGNITION_DEACTIVATED) instead of combined HFP_SUBEVENT_VOICE_RECOGNITION_STATUS with status field. HFP_SUBEVENT_VOICE_RECOGNITION_ACTIVATED contains field "enhanced" to indicate if enhanced mode is used. 53- HFP: enhanced VRA: HFP_SUBEVENT_VOICE_RECOGNITION_ACTIVATED is emitted after VRA is ready and the the audio connection is established. This simplifies HFP HF client logic, i.e. client can call `hfp_hf_enhanced_voice_recognition_report_ready_for_audio directly` upon reception of HFP_SUBEVENT_VOICE_RECOGNITION_ACTIVATED event. --- 840 unchanged lines hidden --- | 47- RFCOMM: `RFCOMM_EVENT_PORT_CONFIGURATION` contains rfcomm_cid and remote flag, emitted for query config 48- RFCOMM: provide status instead of undocumented int error code and bool for API functions 49- RFCOMM: remote port configuration, line status, and modem status are sent by channel state machine 50- HFP: API functions return status code if appropriate 51- HFP: removed one parameter from hfp_ag/hf_activate_voice_recognition function, instead introduced hfp_ag/hf_deactivate_voice_recognition 52- HFP: merged legacy and enhanced Voice Recognition Activation (VRA) API. If available enhanced mode will be preferred. 53- HFP: separate events for activation (HFP_SUBEVENT_VOICE_RECOGNITION_ACTIVATED) and deactivation (HFP_SUBEVENT_VOICE_RECOGNITION_DEACTIVATED) instead of combined HFP_SUBEVENT_VOICE_RECOGNITION_STATUS with status field. HFP_SUBEVENT_VOICE_RECOGNITION_ACTIVATED contains field "enhanced" to indicate if enhanced mode is used. 54- HFP: enhanced VRA: HFP_SUBEVENT_VOICE_RECOGNITION_ACTIVATED is emitted after VRA is ready and the the audio connection is established. This simplifies HFP HF client logic, i.e. client can call `hfp_hf_enhanced_voice_recognition_report_ready_for_audio directly` upon reception of HFP_SUBEVENT_VOICE_RECOGNITION_ACTIVATED event. --- 840 unchanged lines hidden --- |