bbb4110b455b3aa29106d5b4f0a37e1be8e09475 |
|
09-Apr-2015 |
Casper Bonde <c.bonde@samsung.com> |
Obex over L2CAP + SDP search API Each profile had its own implementation of ObexTransport. These implementations were implemented very similar, and could easily be merged into a common implementation. Additionally it will make it easier to adopt the transport to support L2CAP. The SDP functionality is implemented in a way that is scalable, hence adding new record types is easy. Intents are currently used to distribute the SDP search results, as we have observed that the new client side profiles have been located outside the Bluetooth package. We strongly recommend to keep all bluetooth profiles within the Bluetooth package, to acoid the need for exposing all bluetooth interfaces through the Android framework. For instance this new SDP create API is internal to Bluetooth, hence cannot be used by the external profiles - hence they cannot use OBEX over L2CAP. The SDP search currently supports: - MAP both sides - OPP server (only the server needs an SDP record) - PBAP server (only the server needs SDP record) The SDP create record currently supports: - MAP both sides - OPP server - PBAP server The new l2cap sockets introduces a new wrapper class for a rfcomm and an l2cap socket. The wrapper design: - Creates two accept threads running while bluetooth is turned on. - When a connection is accepted the owner is asked wether or not to accept the connection if rejected, the connection will be rejected at obex level, else it will be accepted and the state is changed to busy. - Any further connections will be rejected at Obex level, until the state is changed back to idle. Notes tor executing the test cases: Test OBEX using local pipes(no BT) or two bluetooth enabled devices. Test SDP using two Bluetooth enabled devices Start server testcase first on one device, then start the matching client test on the other device. You cannot run all tests in one go, as they need to run on multiple devices. Edit the test sequesce to add/remove/modify the sequence of OBEX operations to perform. Use the new SDP record create interface. Change-Id: I3941793f9843abf4afa5ffbee40d1d01c118b29b Signed-off-by: Casper Bonde <c.bonde@samsung.com>
/packages/apps/Bluetooth/src/com/android/bluetooth/opp/TestActivity.java
|
a930b6831d0c70b6c5d34e548e6b1dceaa6529a0 |
|
01-Nov-2010 |
Mohammad Shamsi <m.h.shams@gmail.com> |
code cleanup. unused imports, local variabls and static constans removed from com.android.bluetooth.opp package. Change-Id: I0fd682a190221e216fac71723c05d3828b9fa42d
/packages/apps/Bluetooth/src/com/android/bluetooth/opp/TestActivity.java
|
888485a3f5fe991116c5536bb6d6903d47b63a70 |
|
31-Aug-2009 |
Tao Liejun <L.J.Tao@motorola.com> |
Cleanup Opp debug code Stop Rfcomm polling Delete a few unused functions
/packages/apps/Bluetooth/src/com/android/bluetooth/opp/TestActivity.java
|
af9af3c451fde7712e86c9430169c306b91836a4 |
|
15-Jul-2009 |
Jackson Fan <xyfan@motorola.com> |
Cleanup resources of OPP Modify according to Ranian's comments - adjust layout - remove Capitalized resource names - format
/packages/apps/Bluetooth/src/com/android/bluetooth/opp/TestActivity.java
|
6769b59d715ea98bd72eafcfea9acd2714a887da |
|
15-Jul-2009 |
Tao Liejun <L.J.Tao@motorola.com> |
Make opp compile Modify to make opp application compliable in new git -change package name -change manifest -modify a few comments
/packages/apps/Bluetooth/src/com/android/bluetooth/opp/TestActivity.java
|
09e9cba205af60b3f42e7a4d891a7d1392e1f2a5 |
|
11-Jul-2009 |
Nick Pelly <npelly@google.com> |
Initial drop of Motorola Bluetooth OPP code. Minor changes from Moto code: - Added Motorola BSD license - Moved com.motorola.bluetoothshare to com.android.bluetooth.opp - Updated com.motorola.obex to javax.obex - Moved Android.mk to Android.mk.hide: does not yet compile due to changes in Obex library.
/packages/apps/Bluetooth/src/com/android/bluetooth/opp/TestActivity.java
|