| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
Add support for Bluetooth FTP server v1.1 using the javax.obex package
Change-Id: Iaa61d61a5f02691df1b1477b6589fdee7aaf1e20
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
During OPP transfer, the Bluetooth application uses a ContentProvider
to keep track of how many bytes have been transferred. An update()
is called every 64Kb and in turn causes a couple of query(). One of
the listeners updates a notification. All of this causes a lot of
small memory allocations and means that the GC has to clean up a lot
of objects during transfer.
Partly fixed by only calling update() every percent of transfer
instead of every 64Kb block, which means it works best on large
files.
Change-Id: Ia24b5e460fd52ed066867887ff6d22c579ec8e7e
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If a contact name is entered with any of the following characters
:"<>*?|\n\t
the transfer of that contact fails. This is due to the underlying
filesystem (FAT) not being able to handle these characters in a
file name. This fix corrects that situation by replacing any
whitespace characters with a space and strips any illegal FAT
filesystem characters completely.
Change-Id: I5021bd26a16c31810a61bac3f70439c1153451c2
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It is not possible to accept/reject an incoming obex file transfer
using key-press. Only touch screen press was working.
With this fix, key press down is not ignored and it is possible
to accept/reject an incoming obex file transfer with key-press.
ST-Ericsson Change ID: ER260817
Change-Id: Ic7f668bd1b0efa549d0218edc8719efee1984941
Signed-off-by: Christian Bejram <christian.bejram@stericsson.com>
|
|
|
|
|
|
|
|
|
|
|
| |
On some screen sizes the progress bar was drawn over the text.
This problem was solved by changing current xml for displaying progress bar.
It now uses a modified Android default xml for normal notification
messages. The previous xml had problems when using mdpi displays. The
new fix solves this problems and also makes the UI homogeneous with the
other notification messages.
Change-Id: Ib4905a5a7e4b5aded5a6317ca06a77686f7b7b07
|
|
|
|
|
|
|
|
|
|
|
| |
The standard Android code doesn't correctly handle creation of byte
packets when sending vCard data. The length of a String is used to
specify the number of bytes being sent, which works if all
characters are ASCII (1 byte per char), but if Unicode characters
exist within the string, then bytes vs String length differ which
causes a truncation of the vCard during Bluetooth send.
Change-Id: Ic39dd53a38f1f353523c625940b0317b00e86d4f
|
|
|
|
|
|
|
|
|
|
|
|
| |
The value tag sent as a byte array was not parsed correctly
leading to illegal strings. The list count value was not used
according to the specification, now refers to number of entries
that should be returned. Specification for Phone book access
profile chapter 5.3 default max list size of OxFFFF (65535)
taken from 5.3.4.4. Now uses default values when Application
Parameter headers are missing.
Change-Id: Ib17f2208a91b4f896d9beebaf3a21566502ac291
|
|
|
|
|
|
|
|
| |
Pull the new versions of the three affected strings back from gingerbread
(where the placeholders are explicitly marked as such) and reimport the
zh-rTW translations.
Change-Id: Ica839e87d3efe32f5cc8ae0ab42346d8f60d3015
|
|
|
|
| |
Change-Id: Ia0887bd64eafcb3a3ef329b84805a2859cde44eb
|
|
|
|
| |
Change-Id: I5351f0f604a561458f284c0e9444d5aec7767733
|
|
|
|
| |
Change-Id: I118b7e54616b1144be81c8e9ea5de04efb388a97
|
|
|
|
| |
Change-Id: Ic96221d5e692ef4089ef4db39bcfedc392e6d321
|
|
|
|
|
|
|
|
|
|
| |
There were just too much shared code between the classes - we
cannot have them in 2 different process - it can work sometimes and
will fail sometimes depending on the ordering of processes.
Rework involves a lot of code change at this point of time.
Bug: 2684281
Change-Id: I76784650c5f635c1e961392b682c1d33fc2f343f
|
|
|
|
|
| |
Bug: 2674275
Change-Id: Ib5f5d2ebe3ff6ab02e43df38097a89541e132b55
|
|
|
|
| |
Change-Id: I70a15978fd77c45efd8a4e6478c98ee953c49a99
|
|
|
|
|
| |
Bug: 2603200
Change-Id: Ie6a40c12fafac5927b616f31a8335df0181f9e18
|
|
|
|
|
| |
Bug: 2542260
Change-Id: I00f9d8216d70543b93cfbcdb2cd8da8331044d77
|
|
|
|
|
|
|
|
| |
1. Use the right context instead of application context.
2. Make PbapActivity run in the same process as PbapService as they
share state.
Change-Id: Ib50c63c271dd8b30108f22734c47ee8645cd4839
|
|
|
|
| |
Change-Id: Ia71a5b3bb970463132b2c25b90cf3897fc227fb9
|
|\ |
|
| | |
|
| |
| |
| |
| | |
Change-Id: Ia703afd0c3fd603a68f606b684bdf76cd2de32fe
|
| |
| |
| |
| | |
Change-Id: I5fa328f2b8fd78986b9a1958e5899feca254f316
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| | |
Add support to Browser link share via BT;
Add support to share files via BT in 3rd party file manager;
Change-Id: I9a93eb0891d0f670109afd44ab4064f7f15b01f3
|
|\ \ |
|
| |/ |
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When Opp service restart, we will trim the database.
a) No visible case is deleted.
b) Invisible complete outbound (failed and successful) are deleted.
c) Invisible complete failed inbound are deleted.
d) Invisible complete success inbound are deleted if needed to keep records max
to 1000.
Live folder only has received files, so the above makes sense.
Change-Id: If27080721d9abed025162ff805f661fde01564d3
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is to fix below issue: when an ongoing transfer is almost to complete,
click the ongoing notification to launch TransferActivity, there will be
possible crash due to NullPointerException.
Root casue is: when TransferActivity onCreate() is called, the transfer is
still ongoing, so mIsComplete is false; but when onCreate() call to
updateProgressbar(), the transfer may change to complete, and then updateButton()
will be called; In updateButton(), mAlert (which will be initialized in father
class AlertActivity) still not intialized, which caused NullPointerException.
Change-Id: Ibfe363f3822386a38b9b108e29f60ad6673f70f6
|
| |
| |
| |
| | |
Change-Id: I3cdd8eee24082d0b0bf63d1bb80102cf8093b265
|
|/ |
|
| |
|
|\
| |
| |
| | |
the cluster of Opp nofications, we introduce the concept of Opp transfer history. Only 2 notifications exist for finished opp transfers, one is for outbound transfers, and another is for inbound transfers. User can see all detailed items in corresponding screen when click the notification."
|
| |
| |
| |
| |
| |
| | |
cluster of Opp nofications, we introduce the concept of Opp transfer history. Only 2 notifications exist for finished opp transfers, one is for outbound transfers, and another is for inbound transfers. User can see all detailed items in corresponding screen when click the notification.
Change-Id: Iffed353ea6b0d7c958c71fe8d3996937058ced30
|
|/
|
|
| |
Bug: 2485875
|
| |
|
|
|
|
| |
tight coupling.
|
|
|
|
| |
Bug: 2456698
|
|
|
|
| |
Change-Id: I96a9ed96420c20f9291e004a2d9e02300d53ff26
|
|\
| |
| |
| |
| |
| |
| | |
Merge commit '0341ac9aa9f48d71e10d8b1a7382a4ee75fbe3e2'
* commit '0341ac9aa9f48d71e10d8b1a7382a4ee75fbe3e2':
android-2.1_r1 snapshot
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Merge commit '8916d261ab985d191999ec9f8751819434ec4cc0' into eclair-plus-aosp
* commit '8916d261ab985d191999ec9f8751819434ec4cc0':
android-2.1_r1 snapshot
|
| | |\ |
|
| | |/| |
|
| | | | |
|
|\| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Merge commit 'ac1140f71690c537a0a318446731611341e163b8'
* commit 'ac1140f71690c537a0a318446731611341e163b8':
empty initial commit
|
| |\ \ \
| | |/ /
| |/| /
| | |/ |
|