GitLab

Reported by: sj222.choi@samsung.com

Change-Id: I67da4f8a19be72092aa6cd139e561f4e9dfc5f8f

Change-Id: Iaf7e43d35ab4a5da325ebae77cbb72617705c772

* commit 'e35568a2':
  Send local time, not GMT, in timestamp.

* commit '90e61845':
  Send local time, not GMT, in timestamp.

Bug: 5165745

Change-Id: Iffe0f7ce288c2bdb379d2a356f2c5ce346e13b43

The missed, incoming and outgoing call list shall always have its
time specified in local time according to PBAP V10r00 chapter
"3.1.4.1 Call History extension".

Change-Id: If0c4733552db3813d636a2f4658e64df1c6a4efe

The missed, incoming and outgoing call list shall always have its
time specified in local time according to PBAP V10r00 chapter
"3.1.4.1 Call History extension".

Change-Id: If0c4733552db3813d636a2f4658e64df1c6a4efe

- While an opp object is transferring ,there is a white border line on the left side of the progress-bar
  ,which is shown when user click down the notification bar.
- remove the background flag

Change-Id: I4786af460cdd50a9b853f4fa16a12214f4390952
Signed-off-by: jhtop.kim <jhtop.kim@samsung.com>

Update patch set for removing BOOT_COMPLETED.

BluetoothOppService.java : use sendMSG instead of sendMSGdelayed
BluetoothOppReceiver.java : delete boot-complete line
AndroidManifest : delete boot-complete line

Change-Id: Icf9a2f48a70ba519cb3caf93a0b33e13472d1f54
Author: jhtop.kim <jhtop.kim@samsung.com>

When the pin or link key missing case occurs,
we need to retry the socket connection. Use a timeout
of 1.5 secs instead of 2.5 secs because the ACL inactivity
timer is 2 secs.

Change-Id: I3d4c096bd823e3204e91040bea608e44471dd4ce

If BT is off, and if the user sends a file, BT will be turned on
and the "Enabling dialog" wil be shown. But with the hot feature,
BT turns on very fast which leads to the intent being missed and the
enabling dialog not being dismissed.

Change-Id: I4f4a6f08e04922a61eb7138b76383a77f8d37da4

Don't wait to start the listener.

Change-Id: I257332bc38a25b3ca772267a974b4280a8074c40

Since its a notification event for an ongoing event, add the flag.
That prevents it from being scrollable.

Change-Id: Iaea2e7005cb4f8ab5d0b594c4ef9b30343b730fc

Change-Id: Idd95427fb64014e47b6868043abece64b0183fe8

Change-Id: I0837f9e863ed402ef8240f9caeba78be9f9e0f1d

Change-Id: I5d5dde2e0a877ad06cdbfedc50be04117024290d

Strings and diglog are removed and will reappear and modified in Settings
app. We want phone AT commander to use the dialog too.
bug 4489572

Change-Id: I0283b5deff974e53384dc5a92bd01c02e12bbcd6

* commit '13d55be4':
  pullVcard of unknown phone number

* commit '4f97a7a9':
  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: Icf06e527032588f075ff848bea1ba90bf71e874f

This reverts commit 86d30be8.

Change-Id: I99ef1ccfc8082e7b1c90992424d74d8caeef5990

* commit 'a83320e3':
  Import revised translations.  DO NOT MERGE

In BluetoothOppTransfer where we check mRetry and e.getMessage()
if mRetry is false and e is not "Invalid exchange", the transfer is stuck

Change-Id: Ie7a4da215c9e74e167db9fa29c6e113a7a7a2c77

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

Change-Id: I6cf68cff7a9117c09f70cec068bfe119d9c1072b

* commit '9d67ffda':
  OPP: Notification position is changing

* commit '6874774a':
  Handle OBEX Abort packets sent from remote device

* commit 'c50dbb00':
  OPP: Notification position is changing

* commit 'e7df5087':
  Handle OBEX Abort packets sent from remote device

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

* commit '29cedf41':
  Require bonding and encryption for PBAP server

* commit 'a2407587':
  Require bonding and encryption for PBAP server