Skip to content

GitLab

Switch branch/tag
  1. 26 May, 2016 2 commits
    • Ajay Panicker's avatar
      Add guest mode functionality (2/3) · 10c15f82
      Ajay Panicker authored 
      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: I8f23d28ef0aa3a8df13d469c73005c8e1b894d19
      10c15f82
    • Marie Janssen's avatar
      DO NOT MERGE btif: check overflow on create_pbuf size · 5b9f286d
      Marie Janssen authored 
      Bug: 27930580
Change-Id: Ieb1f23f9a8a937b21f7c5eca92da3b0b821400e6
      5b9f286d
  3. 26 Mar, 2016 1 commit
  5. 26 Feb, 2016 1 commit
  7. 27 Oct, 2015 1 commit
  9. 19 Feb, 2015 2 commits
  11. 10 Feb, 2015 1 commit
  13. 06 Feb, 2015 1 commit
  15. 05 Feb, 2015 12 commits
  17. 03 Feb, 2015 3 commits
    • Andre Eisenbach's avatar
      DO NOT MERGE Change pairing_cb to assume temporary pairing by default · a708936d
      Andre Eisenbach authored 
      When pairing takes place, the pairing_cb.is_temp flag indicates whether
a pairing is temporary or permanent. Link keys are not stored for
temporary pairings. Since this is a "positive" flag, resetting the
pairing_cb control block (ex. memset to 0), it will assume persistent
pairing by default. Under certain circumstances, this can lead to a link
key being stored for temporarily secured connection.

This patch reverses the flag to be a "negative" flag. Renamed to
"persistent_bond", the default 0 meaning is now used to indicate a
temporary bond. If the lag is not properly set now, it will default to a
temporary bond and will not save the link key erronously.

Bug: 18345373
Change-Id: I06b1ba9331a70ebc29f4437bf836164658dec5ae
      a708936d
    • Andre Eisenbach's avatar
      DO NOT MERGE Change pairing_cb to assume temporary pairing by default · eebc8ab9
      Andre Eisenbach authored 
      When pairing takes place, the pairing_cb.is_temp flag indicates whether
a pairing is temporary or permanent. Link keys are not stored for
temporary pairings. Since this is a "positive" flag, resetting the
pairing_cb control block (ex. memset to 0), it will assume persistent
pairing by default. Under certain circumstances, this can lead to a link
key being stored for temporarily secured connection.

This patch reverses the flag to be a "negative" flag. Renamed to
"persistent_bond", the default 0 meaning is now used to indicate a
temporary bond. If the lag is not properly set now, it will default to a
temporary bond and will not save the link key erronously.

Bug: 18345373
Change-Id: I8558abc9eace609b1ba02485b0ff775fb6f3c6af
      eebc8ab9
    • Andre Eisenbach's avatar
      DO NOT MERGE Change pairing_cb to assume temporary pairing by default · 3efb9e2e
      Andre Eisenbach authored 
      When pairing takes place, the pairing_cb.is_temp flag indicates whether
a pairing is temporary or permanent. Link keys are not stored for
temporary pairings. Since this is a "positive" flag, resetting the
pairing_cb control block (ex. memset to 0), it will assume persistent
pairing by default. Under certain circumstances, this can lead to a link
key being stored for temporarily secured connection.

This patch reverses the flag to be a "negative" flag. Renamed to
"persistent_bond", the default 0 meaning is now used to indicate a
temporary bond. If the lag is not properly set now, it will default to a
temporary bond and will not save the link key erronously.

Bug: 18345373
Change-Id: Ifb61e7a23db07888a625db9ab851548600183136
      3efb9e2e
  19. 30 Jan, 2015 2 commits
  21. 29 Jan, 2015 2 commits
  23. 27 Jan, 2015 1 commit
    • Andre Eisenbach's avatar
      Change pairing_cb to assume temporary pairing by default · 89363761
      Andre Eisenbach authored 
      When pairing takes place, the pairing_cb.is_temp flag indicates whether
a pairing is temporary or permanent. Link keys are not stored for
temporary pairings. Since this is a "positive" flag, resetting the
pairing_cb control block (ex. memset to 0), it will assume persistent
pairing by default. Under certain circumstances, this can lead to a link
key being stored for temporarily secured connection.

This patch reverses the flag to be a "negative" flag. Renamed to
"persistent_bond", the default 0 meaning is now used to indicate a
temporary bond. If the lag is not properly set now, it will default to a
temporary bond and will not save the link key erronously.

Bug: 18345373
Change-Id: I6e821595877ff30d64dc6e33602ac049cab3dd1e
      89363761
  25. 19 Jan, 2015 1 commit
  27. 15 Jan, 2015 1 commit
  29. 13 Jan, 2015 1 commit
  31. 12 Jan, 2015 1 commit
  33. 07 Jan, 2015 2 commits
  35. 22 Dec, 2014 2 commits
  37. 17 Dec, 2014 1 commit
    • Andre Eisenbach's avatar
      Allow connection parameters updates by slave · 01a069a2
      Andre Eisenbach authored 
      GATT service discovery in the slave role does not update to fast connection
parameters when connected. Accordin to the 4.0 spec, the connection
parameter disable/enable call is used for only by the masster role.
The 4.1 and later spec allows the slave role to control the connection
parameter update so that a slave role GATT client can perform the service
discovery using fast connection parameters.

Also switched to requestiong 7.5ms connection interval by default during
service discovery.

Bug: 18266904
Change-Id: Ie6300587306be3d694937e3888069e252592be42
      01a069a2
  39. 10 Dec, 2014 1 commit
  41. 09 Dec, 2014 1 commit