| 7b55edea45ee5e5447ef8afaa6b144b698ba6f49 |
|
19-Apr-2016 |
Narayan Kamath <narayan@google.com> |
Tidy up uses of Integer.valueOf.
Use parseInt when the result is assigned to an int. Allocates fewer
objects.
bug: 28078871
Change-Id: Iabff8445d703859b20b0f26a407cd5890ec98b80
/frameworks/opt/bluetooth/src/android/bluetooth/client/map/BluetoothMapBmessageParser.java
|
| fb93d457178a706fc3d20df5bbfcff4ca80a1fc2 |
|
13-Jan-2016 |
Sanket Agarwal <sanketa@google.com> |
Enhance logging.
* Fix DBG to be static.
* Add new debugging to PBAP.
Change-Id: I61471466917e0e7c0771f2da7f17f21c51c46962
/frameworks/opt/bluetooth/src/android/bluetooth/client/map/BluetoothMapBmessageParser.java
|
| d87ff784eb2dfac818df247a153be548b13dfb02 |
|
21-Jul-2015 |
Sanket Agarwal <sanketa@google.com> |
Use only UTF-8 for fetching a message.
Currently the API lets the users fetch SMS using either UTF-8 or native
SMS-PDU format. SMS-PDU is not supported by the String() class (also its
more complicated than just a simple string encoding since it contains
recipient etc information). Besides, the library does not decode such
messages and leaves it to the user to handle them. Currently it decodes
it as the default character set on device which is incorrect behavior.
Hence in this change we ensure that the API can only be used with UTF-8
which makes the conversion of Strings consistent.
NOTE: It's OK to avoid supporting native charset since it is not
mandatory in MAPv12 spec.
Change-Id: Ic10a82ff69f848cb3f6e80353d3e63ce3910d306
(cherry picked from commit 4b4d3f8260c9b4476f900ee7b08ee66450624081)
/frameworks/opt/bluetooth/src/android/bluetooth/client/map/BluetoothMapBmessageParser.java
|
| 4231be1e03b7c5e563fea1fa7c56abfe2a1e61dd |
|
13-May-2015 |
Hemant Gupta <hemantg@codeaurora.org> |
MAPC: Fix following issues in map client code
- Fix NPE for ObexTime and dateTimeformat.
Handle possible NullPointerException while accessing
map client ObexTime constructor utility.
Send all parameters event, status and notification state to
Test Client for setNotifcationRegistration event both success
and failure case.
- Fix GetMessagelisting Request for maxlistcount value 0.
Include maxlistcount for value 0 in application parameters header
while composing obex GetMessageListing Request to MAP Server.
- Add maxListCount param in getfolderlisting.
A special case, where MCE APP send the folderlisting
with maxlistcount=0, startoffset=5, As DUT(MCE role)
does not include maxListcount param in folderlsiting,
when it's value set to 0 by MCE APP. So as per the spec,
MSE assume maxListCount = 1024 for folderlsiting & MSE
response as the bad request, when startoffset is Out of
range. Adding MaxListCount in folderListing to
solve this issue, when it's value set to 0.
- Handle exception for incorrect length value from MSE
Handle possible exception while parsing GET Message response
with incorrect LENGTH value fetched from MSE.
- Include ParameterMask Header in GET only when specified.
Include ParmaterMask in GET MessageLising Request only when
specific values are selected from TestClient.
ParameterMask is not a mandatory feild as per MAP1.1 Spec.
excluding ParameterMask for default or value '0' fix MSE IOT
issues that doesnot support ParameterMask Header.
Change-Id: I1bee3f512f877974bb8fd63f3b27dc3ce3ff8a13
/frameworks/opt/bluetooth/src/android/bluetooth/client/map/BluetoothMapBmessageParser.java
|
| 192d793d2586b620027edd5b45ff4c72a86cc7be |
|
08-Apr-2014 |
Hemant Gupta <hemantg@codeaurora.org> |
Bluetooth: Support MAP and PBAP Client role on Bluedroid.
Implementation of android.bluetooth.client.pbap and
android.bluetooth.client.map STATIC JAVA lib for PBAP and MAP
client role(s). These static libraries can be used by application
for PBAP and MAP Client role support on Bluedroid.
Change-Id: I173d2c095661704e2efb39516837c6b681193e9a
/frameworks/opt/bluetooth/src/android/bluetooth/client/map/BluetoothMapBmessageParser.java
|