Change-Id: Ied04d484b8f8092e6fd2bc1109c57cc92866820e

release-request-c9e3b153-009d-4386-b83e-337752602795-for-git_oc-mr1-release-4111654 snap-temp-L22900000075285650

Change-Id: I042607f633f95d92e07ad27416202471ef74899d

am: f6011e13

Change-Id: I8213f90b98d14d2e57132c2b0cdb58280751aaa5

am: 9de9c5d4

Change-Id: I6fb335aeefbc4d5b54641597f0aacabfb2680a79

am: 4a0e377a

Change-Id: Ib780f319811b89cf9af25c060fe4d87f43afe21b

am: 991e0444

Change-Id: I5abe71873af182fec41bb2276df281925020898d

* Owners are selected from top CL approvals or owners.
  They will be suggested to review/approve future CLs.
* OWNERS files are recognized by the new find-owners plugin, see .md files in
  https://gerrit.googlesource.com/plugins/find-owners/+/master/src/main/resources/Documentation/

Test: build/make/tools/checkowners.py -c -v OWNERS
Change-Id: I4c608a33bf3efaca24371a8066563da556cd1034

Change-Id: I56c84ec950647f64c8f409bbd672e5f723bf0b27

am: 971623a9

Change-Id: I498003ec208b6db8e07b7851a71db5acb3d97c90

am: ab0168f9

Change-Id: I27ed13335c512cfd5119126d116b1d6f60ee7a9b

am: 1b71d10d

Change-Id: Id7007c472b1b5f992e14e0394de5374e777f155b

am: 7f2b21a6

Change-Id: I8f06ee056ccc1087e785f8af73dc42e1021d8201

Fixes warnings during makefile parsing:
FindEmulator: find: `frameworks/opt/bluetooth/src/android/bluetooth/client/pbap': No such file or directory

Test: builds
Change-Id: Ib925da33eca52cb4fe4cfce5e227a4d9894c3315

am: 0302ca21

* commit '0302ca21':

Change-Id: I6edb314bc179f4b6423af6f9efc238c7859b8101

am: 6b52e8c4

* commit '6b52e8c4':
  Tidy up uses of Integer.valueOf.

Change-Id: Ia056788907fcd6eaf61cc68492bbdc5fd27feec2

am: b39b00b3

* commit 'b39b00b3':

Change-Id: I5fad795aa6c669a866c8e176ee2bbc9b087532c4

am: e2a4a6b6

* commit 'e2a4a6b6':
  Tidy up uses of Integer.valueOf.

Change-Id: I6ec5adcc841e09a2a275f4aae4f7827d6fe12281

am: 7b55edea

* commit '7b55edea':
  Tidy up uses of Integer.valueOf.

Change-Id: I5603fc72f6e8965fffcc483c6b5a76e3e0ecde5d

am: 7b55edea

* commit '7b55edea':
  Tidy up uses of Integer.valueOf.

Change-Id: Id6ea9ba040dad664d9b6db6454694cb7d138af74

Use parseInt when the result is assigned to an int. Allocates fewer
objects.

bug: 28078871
Change-Id: Iabff8445d703859b20b0f26a407cd5890ec98b80

am: 5c6dbd6d

* commit '5c6dbd6d':
  PBAP migration to BT Profile

Change-Id: If7b60d47d4c4acff7123a5cca76c19da70dd1bc6

am: 82559e6b

* commit '82559e6b':
  PBAP migration to BT Profile

Change-Id: Ibfb2e428cf5a895f2e0a022e038fc9868189e1e9

am: 69f0e158

* commit '69f0e158':
  PBAP migration to BT Profile

Change-Id: I2f8b995d1f63be7a11bd2e37235c4c13caddf34c

am: acddae02

* commit 'acddae02':
  PBAP migration to BT Profile

Change-Id: I74ddbcc69c3cad77257c3f92550bbfbc0d990fa1

am: ced8b4ed

* commit 'ced8b4ed':
  PBAP migration to BT Profile

Change-Id: I9b82a41e74d027f0798b8d83199e3f8efb8d206d

Removal of code that was migrated into packages/apps/Bluetooth.

Bug: 27490041
Change-Id: I482e0cc4193ac886c5f623c97841e8e1a8b0bc7c

Removal of code that was migrated into packages/apps/Bluetooth.

Bug: 27490041
Change-Id: I482e0cc4193ac886c5f623c97841e8e1a8b0bc7c

am: 80232af1

* commit '80232af1':
  PBAP takes Account so that VCardList can add them to operation list.

Change-Id: Ie896efde5f922c7c69cfbc201815a21d13bba02d

am: b15a8306  -s ours

* commit 'b15a8306':
  Use only UTF-8 for fetching a message.

am: a3acb17a

* commit 'a3acb17a':
  PBAP OBEX session uses Handler/HandlerThread now.

am: 6fbf3882

* commit '6fbf3882':
  Mas Obex client should use Handler instead of threads.

Since VCardList can create the commits for the accounts database, we
need to add Account information to the parser. This avoids having to do
this in client code.

Bug: b/26862739

Change-Id: I7690489c4e133c09dd4da6c8e3736ea71bb23a4b

* Fix DBG to be static.
* Add new debugging to PBAP.

Change-Id: I61471466917e0e7c0771f2da7f17f21c51c46962

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)

PBAP was using Java threads which was making synchronization error prone
(as revealed by just connecting/disconnecting pbap alongwith pulling
contacts). This change uses Handler to post messages and cleans up the
internal state of the OBEX client in general.

Also, make the BluetoothSocket close non-blocking. Before this change
the close() call was waiting on BluetoothSocket#open() to finish which
has a deadlock.

Change-Id: I0d8b3d08e19f6f34f0e115d08227b029c6c6751c

Using threads has the following issues currently:
* Can only handle one enqueue in flight. Makes the client dependent on
  checking sanity.
* Uses interrupts to clean up which can lead to race conditions.

Change-Id: Id3b2e2199fea2347dd2b7102ec60004e996fe344

Since VCardList can create the commits for the accounts database, we
need to add Account information to the parser. This avoids having to do
this in client code.

Bug: b/26862739

Change-Id: I7690489c4e133c09dd4da6c8e3736ea71bb23a4b

* Fix DBG to be static.
* Add new debugging to PBAP.

Change-Id: I61471466917e0e7c0771f2da7f17f21c51c46962

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)