Client Supported Features value not persisted for bonded devices
- Dominant language
- C
- Stars
- 893
- Forks
- 512
- Avg merge
- 13d 31m
- Merged PRs (30d)
- 7
Description
Nimble host currently does not persist the state of the Client Supported Features characteristic for bonded devices across connections. When a bonded client reconnects, any features it previously enabled are reset to default.
According to the Bluetooth Core Specification (Vol 3, Part G, Section 7.2): For clients with a trusted relationship, the Client Supported Features characteristic value shall be persistent across connections.
This affects GATT/SR/GAS/BV-04-C qualification test case
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the Client Supported Features characteristic handling for bonded-device reconnects in the GATT/SR/GAS/BV-04 qualification scenario. Verify with GATT/SR/GAS/BV-04 that a trusted client's previously enabled features remain after reconnecting rather than resetting to defaults.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100