mik3y/usb-serial-for-android (com.github.mik3y:usb-serial-for-android)
### [`v2.3.0`](https://togithub.com/mik3y/usb-serial-for-android/releases/tag/v2.3.0)
features:
- added CH341A support
- implement CH34x input control lines
- implemented CP21xx input control lines
- new `getControlLines()` and `getSupportedControLines()` methods
- `getControlLines()`requires less USB transfers than calling `getRTS()` + ... + `getRI()` individually
- `getSupportedControlLines()` tells you, which control lines are supported by a driver. Previously you had to check the driver implementation
changes:
- open() CP21xx with RTS, DTR unset, for consistency with other drivers
### [`v2.2.3`](https://togithub.com/mik3y/usb-serial-for-android/releases/tag/v2.2.3)
features:
- new `UsbSerialPort.isOpen` method
fixes:
- relax CH340 initialization
- make all `SerialPort` classes public
### [`v2.2.2`](https://togithub.com/mik3y/usb-serial-for-android/releases/tag/v2.2.2)
fixes:
- fix CP2102N initialization
- align device_filter.xml with devices recognized by DefaultProber
### [`v2.2.1`](https://togithub.com/mik3y/usb-serial-for-android/releases/tag/v2.2.1)
fixes
- fix CH340 initialization
### [`v2.2.0`](https://togithub.com/mik3y/usb-serial-for-android/releases/tag/v2.2.0)
features:
- support multi-port CDC devices
- support FTDI control lines
- added FTDI specific `get/setLatencyTimer, getModemStatus` methods
refactoring:
- reuse `UsbRequest` to reduce LogCat output
### [`v2.1.0`](https://togithub.com/mik3y/usb-serial-for-android/releases/tag/v2.1.0)
features:
- DTR and RTS support for CP21xx drivers
- reimplemented read timeout. **caution:** too short timeout can cause data loss, see [wiki](https://togithub.com/mik3y/usb-serial-for-android/wiki/Troubleshooting#how-to-set-timeout-in-readwrite-methods) for details
- include proguard rules in .aar library to retain driver classes instantiated by `UsbSerialProber`
fixes:
- improve error handling in `close` and more reliably interrupt `read` and terminate `SerialInputOutputManager`
- harmonize + cleanup error messages
- correct `purgeHwBuffers` parameter description
- manage USB permission intent in sample app
- more code coverage tests
changes:
- distinguish `IllegalArgumentException` and `UnsupportedOperationException` in `setParameter`
*If you had dedicated handling for `IllegalArgumentException`, you now have to handle both*
- `SerialInputOutputManager` now has infinite read/write timeout per default, to prevent data loss
*If you want to use `SerialInputOutputManager.writeAsync` you should set a readTimeout!=0 before starting the thread*
### [`v2.0.0`](https://togithub.com/mik3y/usb-serial-for-android/releases/tag/v2.0.0)
merged back changes collected in [kai-morich's fork](https://togithub.com/kai-morich/usb-serial-for-android)
new features:
- support ft\_232h, cp210\_ multiport devices
- CH34x: data bits, parity, stop bits
- CP21xx: mark+space
- support USB devices with other non CDC related endpoints
- CH34x: support more baudrates
changes:
- increased minimum Android version to 4.3 (API 17)
- Always use async read (`UsbDeviceConnection.requestWait`), as bulkTransfer (`UsbDeviceConnection. bulkTransfer`) can cause [data loss](https://stackoverflow.com/questions/9108548/android-usb-host-bulktransfer-is-losing-data) at high baud rates. Before this release only the CdcAcm driver used async read.
*With async read currently **read timeout != 0 is ignored. `read` blocks until data is available** (except Ftdi, where status data is available each 16msec).*
Instead of using `read` you can use the asynchronuos `SerialInputOutputManager` to be notified on available data. `SerialInputOutputManager.writeAsync` is also affected, as the loop blocks in a `read`. Instead you can `write` directly in your UI thread.
Configuration
π Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
π¦ Automerge: Enabled.
β» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
π Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.
This PR contains the following updates:
v3.7.0
->2.3.0
Release Notes
mik3y/usb-serial-for-android (com.github.mik3y:usb-serial-for-android)
### [`v2.3.0`](https://togithub.com/mik3y/usb-serial-for-android/releases/tag/v2.3.0) features: - added CH341A support - implement CH34x input control lines - implemented CP21xx input control lines - new `getControlLines()` and `getSupportedControLines()` methods - `getControlLines()`requires less USB transfers than calling `getRTS()` + ... + `getRI()` individually - `getSupportedControlLines()` tells you, which control lines are supported by a driver. Previously you had to check the driver implementation changes: - open() CP21xx with RTS, DTR unset, for consistency with other drivers ### [`v2.2.3`](https://togithub.com/mik3y/usb-serial-for-android/releases/tag/v2.2.3) features: - new `UsbSerialPort.isOpen` method fixes: - relax CH340 initialization - make all `SerialPort` classes public ### [`v2.2.2`](https://togithub.com/mik3y/usb-serial-for-android/releases/tag/v2.2.2) fixes: - fix CP2102N initialization - align device_filter.xml with devices recognized by DefaultProber ### [`v2.2.1`](https://togithub.com/mik3y/usb-serial-for-android/releases/tag/v2.2.1) fixes - fix CH340 initialization ### [`v2.2.0`](https://togithub.com/mik3y/usb-serial-for-android/releases/tag/v2.2.0) features: - support multi-port CDC devices - support FTDI control lines - added FTDI specific `get/setLatencyTimer, getModemStatus` methods refactoring: - reuse `UsbRequest` to reduce LogCat output ### [`v2.1.0`](https://togithub.com/mik3y/usb-serial-for-android/releases/tag/v2.1.0) features: - DTR and RTS support for CP21xx drivers - reimplemented read timeout. **caution:** too short timeout can cause data loss, see [wiki](https://togithub.com/mik3y/usb-serial-for-android/wiki/Troubleshooting#how-to-set-timeout-in-readwrite-methods) for details - include proguard rules in .aar library to retain driver classes instantiated by `UsbSerialProber` fixes: - improve error handling in `close` and more reliably interrupt `read` and terminate `SerialInputOutputManager` - harmonize + cleanup error messages - correct `purgeHwBuffers` parameter description - manage USB permission intent in sample app - more code coverage tests changes: - distinguish `IllegalArgumentException` and `UnsupportedOperationException` in `setParameter` *If you had dedicated handling for `IllegalArgumentException`, you now have to handle both* - `SerialInputOutputManager` now has infinite read/write timeout per default, to prevent data loss *If you want to use `SerialInputOutputManager.writeAsync` you should set a readTimeout!=0 before starting the thread* ### [`v2.0.0`](https://togithub.com/mik3y/usb-serial-for-android/releases/tag/v2.0.0) merged back changes collected in [kai-morich's fork](https://togithub.com/kai-morich/usb-serial-for-android) new features: - support ft\_232h, cp210\_ multiport devices - CH34x: data bits, parity, stop bits - CP21xx: mark+space - support USB devices with other non CDC related endpoints - CH34x: support more baudrates changes: - increased minimum Android version to 4.3 (API 17) - Always use async read (`UsbDeviceConnection.requestWait`), as bulkTransfer (`UsbDeviceConnection. bulkTransfer`) can cause [data loss](https://stackoverflow.com/questions/9108548/android-usb-host-bulktransfer-is-losing-data) at high baud rates. Before this release only the CdcAcm driver used async read. *With async read currently **read timeout != 0 is ignored. `read` blocks until data is available** (except Ftdi, where status data is available each 16msec).* Instead of using `read` you can use the asynchronuos `SerialInputOutputManager` to be notified on available data. `SerialInputOutputManager.writeAsync` is also affected, as the loop blocks in a `read`. Instead you can `write` directly in your UI thread.Configuration
π Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
π¦ Automerge: Enabled.
β» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
π Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.