Issue metadata
Sign in to add a comment
|
BlueZ should not remember gatt database after disconnection for unpaired devices |
||||||||||||||||||||||||
Issue descriptionAccording to Core Specification v4.2 [1] and v5.0 [2], the attributes should be cleared between unbonded devices after disconnection, since the attributes are no long valid. [1] Page 525, Section 2.5.2 Attribute Caching, Part G, Volume 3: "For clients that do not have a trusted relationship with the server, the attribute cache is valid only during the connection." [2] Page 2227, Section 2.5.2 Attribute Caching, Part G, Volume 3: "For clients that do not have a trusted relationship with the server, the attribute cache is valid only during the connection."
,
May 30 2017
Specifically about notifications: page 2238 Section 3.3.3.3 Client Characteristic Configuration, Part G, Volume 3: "The Client Characteristic Configuration descriptor value shall be set to the default value at each connection with non-bonded devices."
,
Oct 31 2017
,
Oct 31 2017
Hi Joseph, This is the root cause of issue 719581 .
,
Oct 31 2017
You can change the GATT cache policy in the main.conf: https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/src/main.conf#n78 Just change it from 'always' to 'yes'. Note that always only cache attributes of device which uses public or random static addresses which in effect is their identity address, device using privacy will not be affected by this policy since once disconnected the whole device object is removed.
,
Nov 2 2017
,
Apr 17 2018
Per Miao's comment in C#4, this is a duplicate of issue 719581 which was already fixed. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sonnysasaka@chromium.org
, May 30 2017