| 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/SapMessage.java
|
| e377aae948e58f974c3af14360d2f6ce09b868aa |
|
28-Aug-2015 |
Casper Bonde <c.bonde@samsung.com> |
SAP: Fix logic to skip padding bytes for requests received
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: Casper Bonde <c.bonde@samsung.com>
Change-Id: I24e4a6b850709c9c32b7e0992626a0219dacef03
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapMessage.java
|
| d73503eb9d27edf6b942876f510d347e9c4a2970 |
|
22-Jul-2015 |
koh.changseok <koh.changseok@lge.com> |
SAP: Do not send padding when packet size is mutiple of 4
Bug: 22943799
Change-Id: I48d411f4e3a79a891360a9a855c4680bea19d748
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapMessage.java
|
| 22fa8a39e020ff8f74b7d8ac052bddd8328cadc5 |
|
28-Apr-2015 |
Casper Bonde <c.bonde@samsung.com> |
SAP: Correct ResultCode for setTransportProtocolResp
Changed to respond with "Error, not supported" according to
the SAP specification, to pass PTS tests.
Change-Id: If4f3ddf27468d13f1162c19ab6c0a712fc81fd92
Signed-off-by: Casper Bonde <c.bonde@samsung.com>
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapMessage.java
|
| b6791189b3c8be04b521b8520aed006f012304d1 |
|
27-Apr-2015 |
Casper Bonde <c.bonde@samsung.com> |
SAP: Shorten long lines
Change-Id: I89d5bf6d68b8aba9d9e86e891bfb1b79eb241432
Signed-off-by: Casper Bonde <c.bonde@samsung.com>
/packages/apps/Bluetooth/src/com/android/bluetooth/sap/SapMessage.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/SapMessage.java
|