| CHANGELOG.md (822ca440d24c603c5757d67e57eb2ae7a59c1172) | CHANGELOG.md (0b81d2a574f0a2bc297d86517e065a1a08615d68) |
|---|---|
| 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 --- 32 unchanged lines hidden (view full) --- 41 42### Changed 43- Drop iOS support 44- HCI: provide status instead of undocumented int error code and bool for API functions 45- HCI: use 1000 ms watchdog to force power off for hci_power_control(HCI_POWER_OFF) 46- GAP: local name, EIR data, class of device and default link policy can be updated at any time 47- L2CAP: provide status instead of undocumented int error code and bool for API functions 48- L2CAP: remote features not required for SDP connections | 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 --- 32 unchanged lines hidden (view full) --- 41 42### Changed 43- Drop iOS support 44- HCI: provide status instead of undocumented int error code and bool for API functions 45- HCI: use 1000 ms watchdog to force power off for hci_power_control(HCI_POWER_OFF) 46- GAP: local name, EIR data, class of device and default link policy can be updated at any time 47- L2CAP: provide status instead of undocumented int error code and bool for API functions 48- L2CAP: remote features not required for SDP connections |
| 49- L2CAP: replaced l2cap_register_packet_handler with l2cap_add_event_handler to register multiple handlers |
|
| 49- RFCOMM: `RFCOMM_EVENT_PORT_CONFIGURATION` contains rfcomm_cid and remote flag, emitted for query config 50- RFCOMM: provide status instead of undocumented int error code and bool for API functions 51- RFCOMM: remote port configuration, line status, and modem status are sent by channel state machine 52- HFP: API functions return status code if appropriate 53- HFP: removed one parameter from hfp_ag/hf_activate_voice_recognition function, instead introduced hfp_ag/hf_deactivate_voice_recognition 54- HFP: merged legacy and enhanced Voice Recognition Activation (VRA) API. If available enhanced mode will be preferred. 55- 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. 56- 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 --- | 50- RFCOMM: `RFCOMM_EVENT_PORT_CONFIGURATION` contains rfcomm_cid and remote flag, emitted for query config 51- RFCOMM: provide status instead of undocumented int error code and bool for API functions 52- RFCOMM: remote port configuration, line status, and modem status are sent by channel state machine 53- HFP: API functions return status code if appropriate 54- HFP: removed one parameter from hfp_ag/hf_activate_voice_recognition function, instead introduced hfp_ag/hf_deactivate_voice_recognition 55- HFP: merged legacy and enhanced Voice Recognition Activation (VRA) API. If available enhanced mode will be preferred. 56- 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. 57- 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 --- |