summaryrefslogtreecommitdiffstats
path: root/obex
Commit message (Collapse)AuthorAgeFilesLines
* am 0c2d82c6: am 848a1e3d: Merge "OBEX: Fix PrivateOutputStream small write ↵Jaikumar Ganesh2011-05-201-12/+9
|\ | | | | | | | | | | | | problem" * commit '0c2d82c6f28ab6ec73d66fcc1f62e067829df426': OBEX: Fix PrivateOutputStream small write problem
| * OBEX: Fix PrivateOutputStream small write problemErik Ljungberg2011-05-201-12/+9
| | | | | | | | | | | | | | | | | | | | | | When data less than max packet size in length is sent into the write method the data will only be added to the internal buffer. If several calls to write is performed by the application continueOperation will not be called at all. The solution to the problem is to always check the internal buffer size and to call continueOperation every time maxPacketSize bytes is in the internal buffer. Change-Id: I5ebfa3c26db2c1aefe1a115d7782d8ceaa760937
* | am 24a16e6c: am c34c88b9: am ec1a8f7a: Merge "Unable to push files to Windows 7"Jaikumar Ganesh2011-04-192-2/+8
|\ \ | |/ | | | | | | * commit '24a16e6c53d9b45c0cfdf150425002adc919955b': Unable to push files to Windows 7
| * Unable to push files to Windows 7Erik Ljungberg2011-03-222-2/+8
| | | | | | | | | | | | | | | | | | Windows 7 says it can handle the maximum OBEX packet size. However if the maximum packet size is used the transfer will fail. This should be fixed by Microsoft but until they do the only way to solve this is to reduce the maximum packet size for the OBEX client. Change-Id: I51975eec972395ae3f1f21cca236b223d0812ef3
| * Bluetooth OBEX timeout problem.Anders Petersson2010-10-271-3/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Long time to show notification of file transfer failed after canceling transfer via remote part. Device A is in contact with our device, B. When device A Cancel a transfer operation, it sends OBEX_OPCODE_DISCONNECT HeaderID and the length of package to B. B use the length of package to read remainder bytes from A. If the bytes B read do not meet the received length it will block and wait for remainder bytes from A. But when B compute the remainder bytes it forgets to subtract the three bytes it has already read through HeaderID and the length of the package. So the operation was blocked until the operation timeout. Change-Id: I0f8bf62d3119e081b5c01af9fc05fe586fd4fabc
* | Removing android.security.MessageDigestBrian Carlstrom2011-02-011-4/+8
| | | | | | | | | | Bug: 3392028 Change-Id: I6b9732da17d086ba00c846c3ad1c7fb39baf9502
* | Bluetooth OBEX timeout problem.Anders Petersson2010-10-271-3/+5
|/ | | | | | | | | | | | | | | | | Long time to show notification of file transfer failed after canceling transfer via remote part. Device A is in contact with our device, B. When device A Cancel a transfer operation, it sends OBEX_OPCODE_DISCONNECT HeaderID and the length of package to B. B use the length of package to read remainder bytes from A. If the bytes B read do not meet the received length it will block and wait for remainder bytes from A. But when B compute the remainder bytes it forgets to subtract the three bytes it has already read through HeaderID and the length of the package. So the operation was blocked until the operation timeout. Change-Id: I0f8bf62d3119e081b5c01af9fc05fe586fd4fabc
* Add ABORT support to Obex libLixin Yue2010-03-162-0/+39
|
* Update OBEX lib setPath Flags handling logic to be compatible with spec.Lixin Yue2009-12-161-1/+1
| | | | | | | | From IrOBEX, 3.3.6.1, we can see below explanation for Flags bit 1: 1 Don't create directory if it does not exist, return an error instead. The correct understanding should be: if bit 1 is set to 1, we'll not create directory if it not exist; if bit 1 is set to 0, we'll create it if it not exists.
* Update OBEX to fix missing several contact entries issue.Lixin Yue2009-11-103-18/+52
| | | | | | | | | | | | | | | | | The third parameter count of PrivateOutputStream.write() should be the size of vcards data plus header length, excluding the 3 bytes for the response message and 3 bytes for the header ID and length. Adjust the return value of getMaxPacketSize() by minus headser size, so that applications should not get packet slipped during multiple sharing operation. Do not set the header to null in getHeaderLength() to get PBAP PTS passed; Per OBEX spec, for Get request: Only the last packet need send the 0x49(End of Body); for intermediate packets, we need to send 0x48 (Body). If all packets use 0x49, some carkit like Nokia PD-17 will fail to download all contacts, except data in the last packet. Bug: 2246927 Dr No: Eastham
* Modified random variable to use java.security.SecureRandom for ↵Oscar Montemayor2009-09-201-3/+3
| | | | authentication challenge genration.
* Fix connection ID issue in Obex libTao Liejun2009-09-152-7/+7
| | | | ConnectionID should be consistent in one Obex session.
* Improve Obex compatibilityJackson Fan2009-08-192-1/+6
| | | | | Handle headers with excessive whilespace Send correct reponse code when client abort onPut
* Fix a bug introduced in obex cleanupTao Liejun2009-07-151-1/+1
| | | | | Avoid exception when an empty array is passed to convert to Unicode Before cleanup, there used to be an empty try/catch
* Fix minor obex bugs and re-format the commentsTao Liejun2009-07-1417-841/+493
| | | | | | | | | | re-format comments move connectible to connectable remove unnecessary throws remove not-used function ClientOperation.readResponse() fix client abort case for PUT set mOpen for PrivateOutputStream add to platform.xml
* Obex library cleanup, third passTao Liejun2009-07-0717-1395/+1118
| | | | | | | | - Change variable namings - Remove interface public modifier - Move 2 duplicate methods to ObexSession - Removed unused code and variables - Use static variables for some protocol defines
* Obex library cleanup, second pass.Nick Pelly2009-06-305-184/+152
| | | | | | | | | | | | | | o Use mMemberField variable naming as per style guide o ClientSession.trans is only used in the ctor, doesn't need to be a member o Rename connectionOpen to mOpen and isConnected to mObexConnected to reduce confusion o Refactor duplicated code into helper functions (setRequestActive()) o Fix whitespace around comment blocks o Change unnecessary public scope's to package private (eg setRequestInactive()) o Remove a redundant factory method ClientSession.createHeaderSet() o Rename OPTIMIZATION to TODO to match Android style o Rename java.io.IOException to IOException o Be consistent with variable naming - use header not headers
* Obex library cleanup, first pass.Nick Pelly2009-06-3020-717/+288
| | | | | | | | | | | | | | | | o Add Android.mk file. o Add @hide so it is not exposed in the public API. It is not yet in shape. o Prefer @throws to @exception o Do not use @version. This is meaningless in Android. o Prefer classes 'final' unless explicitly allowing inheritance (See "Effective Java" item 15) o Prefer CamelCaps java naming even for acronyms (OBEXHelper -> ObexHelper) o Use the built-in MD5 library. o Move ObexConstants into ObexHelper. o Remove unused variables. o Prefer stricter access priveleges. Most importantly, avoid public fields. o Don't use 'import java.io.*'. Name each class explicitly. o Delete commented out code. If its not used then remove it.
* Add javax.obex library, contributed by Motorola.Nick Pelly2009-06-3019-0/+7269
Based of a JSR-82 reference implementation. This check-in is 'as-is' from the source provided June 25. This code does not conform to Android style and quality guidelines. I will be working with Motorola to improve it. If it does not see substantial improvement in the Eclair timeframe it will be deleted.
generated by cgit v1.1 at 2024-12-26 09:26:09 +0000