aed51b5e1151240567d990bacff01b66572fd45b |
|
10-Feb-2017 |
Marie Janssen <jamuraa@google.com> |
Use resources for pairing ui package The pairing package is set to "com.android.settings" which means overlays can't change the package that's responsible for UI interaction when pairing and access request events happen. Move it to a resource. Test: pair a device, initiate pair from remote Change-Id: I5731bcdcfed58b72b4e15e3e60035c7e8144b7d4 Bug: 35163738 Fix: 35219650
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
fbdf4f223574f48f8f3db83ea88e063a7551f799 |
|
20-Jan-2017 |
Marie Janssen <jamuraa@google.com> |
Broadcast pairing intents to settings package Intent broadcasts intended directly for pairing dialogs should only be specifically targetted to those packages. Bug: 34395439 Test: pair a device, pair a device remotely, and connect devices Change-Id: Ieb1354d534d4dc0457279aa3f1d3020b3a3ee37b
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
86c29fe88456bdcfbd4334647b04ef81ff384a06 |
|
22-Dec-2016 |
Sanket Agarwal <sanketa@google.com> |
Separate Phone Policy from mechanism Create a new policy file which interacts using either public APIs (such as Intents) or uses equivalent functions which are exposed by the binder. This is an attempt to be able to separate policy such that different devices can have different policies. Bug: b/33079907 Test: JUnit tests Change-Id: I6c5a7ee9eb4e10f5f649794546acde5ec4b297aa
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
95ba9eb75fe596dd231bf142fd3535ea489469ce |
|
08-Sep-2016 |
Hemant Gupta <hemantg@codeaurora.org> |
SAP: Close RFCOMM connection immediately if access is denied. Usecase 1) Pair with carkit and connect HF and A2DP/AVRCP. 2) Carkit sends SAP connect request. Reject this request from DUT. 3) Power off/on carkit. 4) Carkit sends SAP connection request to DUT. Expectation: SAP connection is rejected, but carkit can reconnect HF and A2DP/AVRCP Observation: Unable to connect any profiles after power cycling carkit. Root Cause: Even thought DUT rejects incoming SAP RFCOMM connection request whose access was previously rejected by DUT, RFCOMM connection is not closed from DUT until time out of 30 seconds. This prevents carkit from sending new connect request for previously connected profiles like HFP, A2DP/AVRCP. Fix: Close RFCOMM connection in case request is from remote device whose access is already denied by DUT in previous attempt. Change-Id: I31bd2dfd862f7f69e46b8012924942e08e850c95
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
eb7b90f5b93db1230a5b64caa3d8d05a642e33a6 |
|
10-May-2016 |
Marie Janssen <jamuraa@google.com> |
Cleanup unused requires in java files Change-Id: I7b055c1d3d3f6a69e9f49c077853ab45fcad7106
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
a86b03167e6949f1afd0eb0e57c4339b6f8b5200 |
|
06-Mar-2016 |
Hemant Gupta <hemantg@codeaurora.org> |
SAP: Fix ANR(s) in SAP server code Fix ANR in SAP Server code in following scenarios: - Multiple call to stop in Sapservice leads to ANR, as check was not present in stop to prevent unregistering BroadcastReceiver if not already registred. - Remove redundant call to closeServerSocket from initSocket as this could lead to ANR when there is simultaneous call to closeService as part of BT being switched off and call to start SAP as part of BT being turned on when BT on off sequence is tried repeatedly. Change-Id: Ia6bc5ca7c9da9ae4a4c12e8207fb9ff6b9159e82
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
0e0883602b97ed9bf2a86c49a93345c91da5167e |
|
06-Mar-2016 |
Hemant Gupta <hemantg@codeaurora.org> |
SAP: Remove sdp record while BT is being turned off to prevent leak Remove sdp record created dynamically for SAP server during BT off state. Without this call, there is leak in sdp layer in stack as sdp record is never removed, even though the socket is closed. Also proper checks are added to prevent call to remove sdp record when adapter is null. Change-Id: I739cc3115f6cd7fedf9085e8522c96da257e9568
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
222d110bd00c9120f776c5893374d5427053e452 |
|
07-Mar-2016 |
Hemant Gupta <hemantg@codeaurora.org> |
SAP: Fix issue of socket listener not getting re-started Add logic to properly handle ACL_DISCONNECTED to restart socketListener to handle scenarios where socket listener was not getting started due to abnormal ACL disconnect. Change-Id: Iac5ec52f485e692b14bb0065e30a68cae007a49d
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
987a8cdbdc36548f76ad63fc5ab33f8b3ce2f69a |
|
07-Mar-2016 |
Hemant Gupta <hemantg@codeaurora.org> |
SAP: Update UI connection and notifications properly Update connection state to upper layers only when SAP SLC is connected i.e. status indication is sent to SAP Client. Also notification to disconnect SAP Server from UI is shown only when SAP is successfully connected, and not when SapServer object is created. Change-Id: Iaf40584220b51f6193bed9a54d159cffd32698e9
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
471e023da5f39d21ebcb1d3fad43a591c15f6be3 |
|
28-Aug-2015 |
Casper Bonde <c.bonde@samsung.com> |
SAP: Fix missing attribute in disconnect_ind 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: Casper Bonde <c.bonde@samsung.com> Change-Id: I776a53d6e786c21000ef62094f9a9948ee5880b8
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
3c81700fa6a57cdceb256e03d942f71842d75878 |
|
08-Jun-2015 |
Kim Schulz <k.schulz@samsung.com> |
SAP: turn debugging and test flags off Currently DEBUG, VERBOSE and PTS_TEST_MODE is on as a default. There is no reason for that in production code (except for during test where the code needs to go through PTS test) Bug: 21692162 Change-Id: Id092a79959fa38608d06755cc43148eee9ec3e00
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
244e9c62a85a4b94e21bf1a8dee456e22bc767c4 |
|
08-May-2015 |
Casper Bonde <c.bonde@samsung.com> |
SAP: Make it possible to enforce a 16-digit pin code (3/5) This change enable the posibility to enforce using a 16-digit pin or MITM for a RFCOMM or L2CAP connection. This is needed for the SIM access profile. Change-Id: I42ada9b36d24d43697a2010eccbc0103f15af77d Signed-off-by: Casper Bonde <c.bonde@samsung.com>
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
a49b4e45faf378e3848c4f6eb468e0a14565aa6c |
|
17-Apr-2015 |
Casper Bonde <c.bonde@samsung.com> |
SAP: Fix exception at shutdown Restructures the disconnect/shutdown code, to avoid exception. Also ensure cleanup of notifications and profile public state. This also fixes the bug introduced when handling ACL_disconnect intent, where the rfcomm-listener was not restarted. Change-Id: I3b4561f610abc77011689b7cfb67a4b54c41500c Signed-off-by: Casper Bonde <c.bonde@samsung.com>
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
bbb071e6d73df46230ec654e3066a46f6e35a88d |
|
22-Apr-2015 |
Casper Bonde <c.bonde@samsung.com> |
SAP: Dynamic use of wake locks This changes the way wake locks are used for SAP from acquiring wake lock at connect, and releasint at disconnect to acquiting a wake lock each time activity is detected, either between Bluetooth and the RIL or between Bluetooth and the client. The wake lock is released when there has been no activity for one second. This is the same scheme as for MAP, except using a lower timeout value, based on analysis of the traffic when connected to a Nokia 616 car-kit. Change-Id: Ie4bcf7e991d81e88b64dc4ba20fa74b327fde3c6 Signed-off-by: Casper Bonde <c.bonde@samsung.com>
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
f98ad52d9b979273b01fb97466f2e077dc7b6bd6 |
|
21-Apr-2015 |
Casper Bonde <c.bonde@samsung.com> |
Add support for MITM for BluetoothSockets (2/4) This change enables use of the option to enforce Man-in-the-middle protection for the authentication process for the Sim Acces Profile. Change-Id: I98244d5e822c25f3f8f51833f38c79e13bb60e63 Signed-off-by: Casper Bonde <c.bonde@samsung.com>
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
1f1103e93ba7ebd48c57c9627dc7b262c6f01c77 |
|
16-Apr-2015 |
Casper Bonde <c.bonde@samsung.com> |
SAP: Change to use new SDP Api (2/4) Added support for Sim Access Profile (SAP) in the SDPManager. To make it easier to test, both SDP record creation and seach is added. Change-Id: I871eb762389e3717b8bd6bc37a8ffc09fff6f589 Signed-off-by: Casper Bonde <c.bonde@samsung.com>
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|
cee0d1b1f13b4401a895be650605fa307e70bdb6 |
|
19-Mar-2015 |
Casper Bonde <c.bonde@samsung.com> |
Add support for Bluetooth Sim Access Profile (3/4) Server side of the Sim Access Profile. Enables a Bluetooth device to take over control of the SIM. This is usefull in cars where the internal antenna in the phone can have a low signal level. For this profile to work, the RIL driver must allow for this feature to be used, and it must provide the API needed. The API is based on protoBuf. This change includes some SAP test cases. Change-Id: Ia46493383efed6b8a89ca270bdafa60fc1a150c1
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapService.java
|