From 201c7e7a38af4bb9ae09f5f81c2f041f8c23b9ab Mon Sep 17 00:00:00 2001 From: kai-morich Date: Fri, 5 Dec 2025 18:44:25 +0100 Subject: [PATCH] useReadQueue --- FAQ.mediawiki | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/FAQ.mediawiki b/FAQ.mediawiki index b2bfb41..d3f2dce 100644 --- a/FAQ.mediawiki +++ b/FAQ.mediawiki @@ -120,7 +120,11 @@ Therefore data loss can happen for continues read at high baud rates. If data is This effect is more likely for slower Android device and USB devices with smaller buffer size and typically starts with higher baud rates like 115k2 baud, but is hardly predictable. For low baud rates or non-continuous transfers this issue was not observed as the USB device will not run into a read buffer overflow before the next USB read transfer. -Using a higher thread priority (default for SerialInputOutputManager since ''usb-serial-for-android v3.1.0'') and offloading work from onNewData to other threads can mitigates the issue. +To mitigate the issue, you can +* use a higher thread priority (default for SerialInputOutputManager since ''usb-serial-for-android v3.1.0''), +* offload work from onNewData to other threads, +* batch process data, e.g. instead of showing each data fragment individually on a UI, +* use setReadQueue. It is recommended to use some sort of flow control like X-Modem protocol.