am d8a9af40: Merge "BT: Fix for vCard Listing error"

* commit 'd8a9af404413ad060eb4aa29a32370b44e61327e':
  BT: Fix for vCard Listing error
am b5f6bb1a: am d8a9af40: Merge "BT: Fix for vCard Listing error"

* commit 'b5f6bb1afba8d322d7453cb6a24751599897234a':
  BT: Fix for vCard Listing error
Merge "Require bonding and encryption for PBAP server"
Handle PBAP response packet as raw bytes

Adjust PBAP response packet to be always handled as bytes.
Currently, it is handled as string when is read from internal data.
This causes the lack of PullvCardListing packet and the abort of
PullPhonebook transaction when multi-byte characters are contained
into corresponding contacts.
This fix will avoid the lack and the abort by writing whole packet
into the target stream as byte.

Change-Id: I17ee3ada25718cc263c9e0942f75605bd971b638
Import revised translations.

Change-Id: I13bdd6fc76e46a3fee0c3cf85fc512cfb846a230
OPP: Notification position is changing

If several transfers is ongoing the Bluetooth transfer notification
is changing position. The reason for this is that the when field is
not set in the notification. Solved by setting when.

Change-Id: If999fae6dd2d6b5de38c3bfeba786ad2df9da48f
pullVcard of unknown phone number

When performing a pullVcardListing, pullVcardEntry or pullPhonebook
on a phone with a call list which contains an unknown phone number,
the phone returns "-1" as number/name. Corresponding errors exist
for private and payphone numbers, where the phone returns the name
"-2" and "-3", respectively. During pullVcardListing the Name
attribute may contain the phone number, in case the name is not
known. The latter is already implemented today, however, instead of
using e.g. "-1" as name when the phone number is not known the
phone should use Name = "Unknown". Currently there are no other
matching corresponding strings defined for private and payphone
number, which means that for now "Unknown" may be returned as name
also for these numbers.
During pullVcardEntry and during pullPhonebook when the phone number
is unknown then the Number attribute should contain the string
"Unknown". During the same scenario the FN and N attributes both
should contain the string "" when the name is not known. When it
comes to private and payphone numbers the same as for
pullVcardListing apply here, i.e. "Unknown" may be used in the
Number attribute also for these numbers

Change-Id: I33cf6ceecf5c8fba426eacbb3a507228f8e4de4d
Merge "pullVcard of unknown phone number"
Handle OBEX Abort packets sent from remote device

This patch adds support for handling OBEX Abort packets
sent from remote device, where the remote device is acting
as a client, sending files to the server.

Depends-On: I0fc2255c463c5ce1e8fa1d7febf144b60965a1be

Change-Id: I4bce05a9007ba02e9d9987ec3cbbf1db380247f0
Signed-off-by: christian bejram <christian.bejram@stericsson.com>
Merge "Handle OBEX Abort packets sent from remote device"
Merge "OPP: Notification position is changing"
am a2407587: Merge "Require bonding and encryption for PBAP server"

* commit 'a2407587440d487aa0171638eef29526515fde59':
  Require bonding and encryption for PBAP server
am 29cedf41: am a2407587: Merge "Require bonding and encryption for PBAP server"

* commit '29cedf4183144e450c226dec6668ff0d633cee93':
  Require bonding and encryption for PBAP server
pullVcard of unknown phone number

When performing a pullVcardListing, pullVcardEntry or pullPhonebook
on a phone with a call list which contains an unknown phone number,
the phone returns "-1" as number/name. Corresponding errors exist
for private and payphone numbers, where the phone returns the name
"-2" and "-3", respectively. During pullVcardListing the Name
attribute may contain the phone number, in case the name is not
known. The latter is already implemented today, however, instead of
using e.g. "-1" as name when the phone number is not known the
phone should use Name = "Unknown". Currently there are no other
matching corresponding strings defined for private and payphone
number, which means that for now "Unknown" may be returned as name
also for these numbers.
During pullVcardEntry and during pullPhonebook when the phone number
is unknown then the Number attribute should contain the string
"Unknown". During the same scenario the FN and N attributes both
should contain the string "" when the name is not known. When it
comes to private and payphone numbers the same as for
pullVcardListing apply here, i.e. "Unknown" may be used in the
Number attribute also for these numbers

Change-Id: I33cf6ceecf5c8fba426eacbb3a507228f8e4de4d
am e7df5087: Merge "Handle OBEX Abort packets sent from remote device"

* commit 'e7df508750728dc2bbd7729d54673bf16f7688c3':
  Handle OBEX Abort packets sent from remote device
am c50dbb00: Merge "OPP: Notification position is changing"

* commit 'c50dbb0067de1772ced124f5982a59468ad81426':
  OPP: Notification position is changing
am 6874774a: am e7df5087: Merge "Handle OBEX Abort packets sent from remote device"

* commit '6874774ab6b2fe5d90896be756d26a9887e4124b':
  Handle OBEX Abort packets sent from remote device
am 9d67ffda: am c50dbb00: Merge "OPP: Notification position is changing"

* commit '9d67ffdac68b49cfc72491f7e2c340df922dbcca':
  OPP: Notification position is changing
Import revised translations.  DO NOT MERGE

Change-Id: I6cf68cff7a9117c09f70cec068bfe119d9c1072b
am 390a9bf1: Import revised translations.  DO NOT MERGE

* commit '390a9bf15ffe2239b391dff3c7b20b8476e46bdd':
  Import revised translations.  DO NOT MERGE