Skip to content
Snippets Groups Projects
  1. Aug 02, 2018
    • Jack He's avatar
      Add MessageLoopThread, ExecutionBarrier, and performance tests · 0ac5b1b6
      Jack He authored
      * Add MessageLoopThread to abstract thread implementation to our code
      * Add ExecutionBarrier utility class to help with thread synchronization
      * Add more performance tests and performance benchmarks to evaluate
        execution efficiency in both batch and sequential usages, for various
        thread implementations including:
        - libosi reactor on pthread
        - MessageLoop on libosi reactor on pthread
        - MessageLoop on STL std::thread
        - MessageLoop on Posix pthread
        - MessageLoop on libchrome base::Thread
        - MessageLoop on MessageLoopThread
      
      Bug: 110303473
      Test: make, native and Java unit tests,
            test/run_benchmarks.sh net_benchmark_thread_performance,
            test/run_unit_tests.sh net_test_performance,
            test/run_unit_tests.sh bluetooth_test_common,
            testplans/details/184455/3975
      Change-Id: I5b4ce2ee910a0f1d2edf95e0296916dea04d3f89
      0ac5b1b6
  2. Aug 01, 2018
  3. Jul 31, 2018
    • Venkata Jagadeesh's avatar
      Add security handling for LE connection oriented channels · e12fd994
      Venkata Jagadeesh authored
      Use case:
      Run PTS test cases TP/LE/CFC/BV-10-C to BV-16-C
      
      Steps:
      1. These test cases executed with two DUT as PTS support not available
      2. Set desired security level on DUT and Remote with tool
      3. Initiate LE COC connection request from DUT
      
      Failure:
      LE COC connection accepted though even remote security are not met.
      
      Fix:
      Added security handling for COC connection
      
      Test: Ran sl4a test for BleCocTest
      Change-Id: I5f6385d462698582e701b5a07953c0ccb932bbbf
      e12fd994
    • Aiswarya Cyriac's avatar
      Fix for Bluetooth device name is resetting to default name after reboot · b8b3655f
      Aiswarya Cyriac authored
      
      Reason: When the BT device name is updated is getting saved to the
      config data pointer but not to the persistent data (i.e. bt_config.conf).
      So, when the reboot is happening it is not able to get the updated device
      name from the persistent data (i.e. bt_config.conf) as during reboot
      bt_config_flush is not called.
      
      Fix: Saving the BT Device name to persistent data using btif_config_flush
      once it is set.
      
      Test: Manual Reboot test
      Bug: 110301897
      Change-Id: Ie329b475eaaf208ed667f27e271a00e230e4b95c
      Signed-off-by: default avatarAiswarya Cyriac <aiswarya.cyriac@intel.com>
      Signed-off-by: default avatarGaganpreet kaur <gaganpreetx.kaur@intel.com>
      b8b3655f
  4. Jul 30, 2018
  5. Jul 27, 2018
    • Joseph Pirozzo's avatar
      Set Browsed Player memory allocation · 30ce2b12
      Joseph Pirozzo authored
      When setting a browsed player memory for folder depth was incorrectly
      allocated based on folder item count not depth.
      
      Bug: 111370532
      Test: Set a browsed player that has a depth greater than item count.
      Change-Id: I6984c5852f623e7e9478429bdab3dcbcf57196e0
      30ce2b12
  6. Jul 26, 2018
  7. Jul 25, 2018
  8. Jul 24, 2018
  9. Jul 18, 2018
    • Hansong Zhang's avatar
      Clean up style in BLE White List code · 555a8d03
      Hansong Zhang authored
      * Remove unused code
      * Update BgConnHash to return size_t for hashcode
      * Change BLE scan_int and scan_win to uint16_t according to spec
      
      Bug: 111562702
      Test: SL4A BLE test and manual with BLE mouse
      Change-Id: Ieff3acbfaa95b7d804e57021d562218d9fbe42cc
      555a8d03
    • Cheney Ni's avatar
      Ignore SDP failure while bonding if SDP was not attempted · 22062116
      Cheney Ni authored
      When bonding, there is an ACL_UP event to the upper layers and some apps
      may want to fetch SDP in return. This can break pairing. In cases SDP fails,
      it causes the procedure to be finished before the LinkKey is generated.
      And thus the LinkKey is not committed to NVRAM and the device is not paired.
      
      Bug: 111189110
      Test: : Pair / Unpair BT accessories manually
      Change-Id: Iaefbe8b6c1fc3e78f0f120220992df84699a2eb8
      22062116
  10. Jul 17, 2018
  11. Jul 16, 2018
    • Ben YoungTae Kim's avatar
      Increase DM connection size for multiple links · 30a58db2
      Ben YoungTae Kim authored
      For multiple headset connections, it will be increased to support
      multiple services(HFP/AV/CT) for each links.
      
      Test: Connect to 4 or more headsets and play music
      Bug: 110972513
      Change-Id: I56f69e12fb1a4a614c69fa383e9c53675a189fc9
      30a58db2
  12. Jul 13, 2018
  13. Jul 12, 2018
  14. Jul 10, 2018
    • Hansong Zhang's avatar
      AVRCP: Reject when CT sends invalid RegisterNotification · 66a01d0d
      Hansong Zhang authored
      Check whether the RegisterNotification request from CT is valid, and
      safely reject invalid request
      
      Bug: 111260441
      Test: manually test with RIVA WAND speaker
      Change-Id: Ia2edd94e50fa7cb5b61be54f297adf971060a924
      66a01d0d
    • Treehugger Robot's avatar
    • Jakub Pawlowski's avatar
      Register for Service Changed notification after encryption · 80b719d5
      Jakub Pawlowski authored
      This fixes issue introduced in commit ddf6320b
      Registration for Service Changed notifications was
      disabled, because there was no good way back then to have
      "opportunistic" app. Since opportunistic apps were introduced, and the
      code in GATT_ConfigServiceChangeCCC is already marking connection as
      opportunistic, reenable notification registration.
      
      Test: manual verification, that Service Changed descriptor is set
      Change-Id: Iefaec3914829fa4a4a60dc3c3790c3daa9f4f4d8
      80b719d5
    • Jakub Pawlowski's avatar
      Get rid of warning when connecting LE device · 078f3bb8
      Jakub Pawlowski authored
      We are sending LE fixed channel notification to classic callback. Stop
      doing that. This triggers following warning in log output on every
      LE connection:
      W bt_smp  : smp_br_connect_callback is called on unexpected transport 2
      
      Test: manual with phone, verify warning is gone when connecting over LE
      Change-Id: I47597fa03744fb1bff03d287f790ea32fa033cc7
      078f3bb8
  15. Jul 09, 2018
  16. Jul 02, 2018
    • Pavlin Radoslavov's avatar
      Don't trigger AVDTP Suspend in response to AVDTP Suspend+Start from remote · 28faf875
      Pavlin Radoslavov authored
      If the remote device sent us AVDTP Suspend, and then AVDTP Start, don't
      trigger AVDTP Suspend from the local device in response to the AVDTP Start.
      
      Also:
       * Add a call btif_av_stream_start_offload() inside btif_a2dp_on_started()
         if we were started remotely.
       * Fix the order of calling btif_a2dp_on_started() and triggering
         an internal BTIF_AV_SUSPEND_STREAM_REQ_EVT event. Otherwise,
         BTA Suspend might be called before btif_av_stream_start_offload()
      
      Bug: 110015851
      Bug: 110186160
      Test: Manual
      Change-Id: I908d19f8caf5130b96a64153ff39bd4b52879713
      28faf875
  17. Jun 29, 2018
  18. Jun 28, 2018
  19. Jun 27, 2018
    • Myles Watson's avatar
      Move sepolicy files to system/sepolicy · 9325ad74
      Myles Watson authored
      Test: Toggle Bluetooth, ls -alZ /vendor/bin/hw/*blue*
      Change-Id: Ibf72f8bacc2f4975d06f4892e3b33ef6fb08aab7
      Merged-In: Ibf72f8bacc2f4975d06f4892e3b33ef6fb08aab7
      9325ad74
  20. Jun 26, 2018
Loading