Skip to content

GitLab

Switch branch/tag
  1. 27 Sep, 2016 1 commit
    • Ajay Panicker's avatar
      Fix setPairingConfirmation permissions issue (1/2) · 0665d10a
      Ajay Panicker authored 
      setPairingConfirmation was set to only require BLUETOOTH_ADMIN
permission which shouldn't be able to set the confirmation itself.

This is restricted to BLUETOOTH_PRIVILEGED permission.

Bug: 29043989
Change-Id: Iae8e31b25795989446265fdcc5eb27e6ffaf29aa
(cherry picked from commit df3304a3)
      0665d10a
  3. 27 May, 2016 1 commit
    • Ajay Panicker's avatar
      Add guest mode functionality (3/3) · 122feb9a
      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: If4a8855faf362d7f6de509d7ddc7197d1ac75cee
      122feb9a
  5. 22 Apr, 2016 1 commit
  7. 24 Feb, 2016 2 commits
    • Liejun Tao's avatar
      DO NOT MERGE Enhance AVRCP Absolute Volume control implementation · 674c089a
      Liejun Tao authored 
      
1. Remember the current local volume level, current remote volume level.
When user adjusts the volume, compare the returned remote volume
level with desired volume level, if they don't match, do retry.

2.Learn and remember the volume mapping between phone volume level and
remote volume level as the user adjusts volume. When user adjusts to one
remembered volume level, use the mapping directly. Otherwise calculate
the remote volume level and try with method described in step one.

3. Blacklist device if remote device does not tell its initial volume.

4. Define optional threshold for initial volume level to avoid headset
being too loud upon re-connection.
Signed-off-by: default avatarLiejun Tao <baibai@motorola.com>
Change-Id: I78112f5f401666f5a680561473a5c7f914071fbe
      674c089a
    • Andre Eisenbach's avatar
      DO NOT MERGE Read Bluetooth interop database entries from settings (2/2) · a71eb120
      Andre Eisenbach authored 
      Interop database entries are stored in the system settings entry
"BluetoothInteropDatabase". The format is a list of entries separated by
";". An entry consists of a BDA fragment, followed by a comma and an
integer representing a feature from interop.h.

Example:
To disable LE secure connections for devices starting with BDA 11:22:33,
use "11:22:33,0".

Bug: 26548845
Change-Id: I5903930178b70d1eb52d64b1c6051ce8ee346da4
      a71eb120
  9. 16 Feb, 2016 2 commits
  11. 22 Jan, 2016 1 commit
  13. 22 Oct, 2015 1 commit
    • Ajay Panicker's avatar
      Remove Vcard filter for call-logs · b211df6f
      Ajay Panicker authored 
      Timestamps were being incorrectly filtered out of Vcards when sending
call-logs. 

Bug: 25084927
Change-Id: Ied8912e7d2fdbcc6e6980c3773c4ec5a449842ec
      b211df6f
  15. 20 Oct, 2015 1 commit
    • Ajay Panicker's avatar
      Fix file permissions for Bluetooth share · 66d64309
      Ajay Panicker authored 
      Used a file provider to serve up URIs to allow
applications to access files in the external
Bluetooth directory.

Bug: 23367919
Change-Id: Iadcdcafb235f3eeb50a0e147f3ef982fc9ee38b3
      66d64309
  17. 12 Oct, 2015 1 commit
  19. 07 Oct, 2015 1 commit
  21. 25 Sep, 2015 1 commit
  23. 18 Sep, 2015 1 commit
  25. 11 Sep, 2015 1 commit
    • Ajay Panicker's avatar
      Allow senderAddressing on default filter for message Listing · 1c28582b
      Ajay Panicker authored 
      Adjusted the PARAMETER_MASK_DEFAULT constant for when a
message listing request is recieved and a message filter isnt
provided. This new filter value causes the sender_address field
to be sent along with all the other default information.

Bug: 22163529
Change-Id: I49444cfb341d2e6cc72bdab55aa441d712b03f14
      1c28582b
  27. 10 Sep, 2015 1 commit
    • Ajay Panicker's avatar
      Move SMS message to proper folder after sending · 0ebd4e58
      Ajay Panicker authored 
      Move a SMS message to the correct folder upon receiving an intent
detailing if the message was succesfully sent or not. If sent
successfully, move to the SENT folder, otherwise move it to
the FAILED folder.

Bug: 22992865
Change-Id: Ifdcfb7bb613844f507ef27460ead520c6573b89d
      0ebd4e58
  29. 08 Sep, 2015 1 commit
  31. 07 Sep, 2015 1 commit
    • Casper Bonde's avatar
      SAP: Fix missing attribute in disconnect_ind · 471e023d
      Casper Bonde authored 
      
The internal TEST flag was removing too much code.
To make it easier to run test, and avoid future issues
with removing needed code, the TEST flag is no longer used
to remove code.

This bug was noticed when running the PTS testcases without the
PTS_TEST flag set. It is assumed that this fix will make
TC_SERVER_DCN_BV_02_I work without the PTS flag, but unless PTS
have updated their test case to accept both a gracefull disconnect
and a forced disconnect, TC_SERVER_DCN_BV_03_I will still fail in
a production build. The SAP spec suggest to use a gracefull disconnect
when initiating a disconnect from a server, hence it is not a good
idea to expose a force disconnect option to the used without first
having tried a gracefull disconnect. Hence the PTS test case
implementation is in conflict with the intented use specified in
the SAP specification.

Without this fix a build with PTS_TEST=false will not work as
intented.

PTS_TEST replaced with system property bt.sap.pts. Set it to true
to enable the force disconnect button.

Bug: 23614694
Signed-off-by: default avatarCasper Bonde <c.bonde@samsung.com>
Change-Id: I776a53d6e786c21000ef62094f9a9948ee5880b8
      471e023d
  33. 03 Sep, 2015 1 commit
    • Casper Bonde's avatar
      SAP: Fix logic to skip padding bytes for requests received · e377aae9
      Casper Bonde authored 
      
As per SAP spec, padding bytes can be 0-3 bytes, but the current code
has incorrect logic, that would lead to calculation of padding bytes
as 4 in case the APDU length was multiple of 4, which would lead to
incorrect parsing logic in SAP Server and can lead to issues of no
response for APDU request from SAP Server as it keeps waiting for
reading more bytes from rfcomm which are not present.

Also check added in code not to send msg to RIL if socket is null to
prevent crash in BT Sap module.

Bug: 23024598
Signed-off-by: default avatarCasper Bonde <c.bonde@samsung.com>
Change-Id: I24e4a6b850709c9c32b7e0992626a0219dacef03
      e377aae9
  35. 01 Sep, 2015 2 commits
  37. 27 Aug, 2015 2 commits
  39. 20 Aug, 2015 1 commit
  41. 19 Aug, 2015 1 commit
    • Sharvil Nanavati's avatar
      Make location enabled check configurable when returning scan results. · 72ecb4ca
      Sharvil Nanavati authored 
      Some device classes (e.g. Wear) don't allow location to be enabled but
would still like to allow LE scanning to take place. This patch allows
the location enabled check to be bypassed if the platform is so configured.
Even if the location check is disabled, the calling app must still have
one of the location permissions.

Bug: 21852542
Change-Id: I206366ce262776d4668c0c42e066f0e20f5fdfeb
      72ecb4ca
  43. 14 Aug, 2015 2 commits
  45. 12 Aug, 2015 1 commit
  47. 08 Aug, 2015 12 commits