James

Hello everyone! @alexander-daniel Is this still an issue? I'd like to help with this. I do think we can do what @aj8uppal and switch from streaming to making REST calls...

Thanks for helping with the analysis @hsanson !

Hey @brbeardm, Sorry about the delay. It's a bit difficult to grab some free time these days. I don't believe this is an issue [as this topic is actually noted](https://bblanchon.github.io/ArduinoJson/faq/the-first-parsing-succeeds-why-do-the-next-ones-fail/)...

This is incredibly exciting. Once I get a bunch of work finished by March's end, I plan on contributing to this in full force. No experience in Rust **yet**, but...

Hi everyone, @kai-morich . After months of digging, I think I might have explanation for this issue and the cascading failures. I'm running a similar issue to @vegidio and @Thaejaesh-S...

> Using an infinite timeout for reads would require an architectural change that I cannot commit to, and [asynchronous writes](https://github.com/mik3y/usb-serial-for-android/blob/a9c835bcb07e6e49e346cc1bcd890fabac2161ba/usbSerialForAndroid/src/main/java/com/hoho/android/usbserial/util/SerialInputOutputManager.java#L146-L154) through `SerialInputOutputManager`, I believe, are no longer possible. Unless you're...

`Try with a direct (blocking) write request. If data is smaller than USB packet size you will not notice any blocking.` This is how my application software is currently writing...

I was wrong about [ETIMEDOUT](https://android.googlesource.com/kernel/common/+/523e6d7f3186/Documentation/usb/error-codes.txt). According to the ancient tomes of Android hosted docs, it's a legit error code due to an arbitrary assigned timeout. The Host controller would experience/see...

Just a pulse update. I've got the USB protocol analyzer. I've had to shift gears for a separate project, but I'll be back on this in the new few days...

@Mohammedbinnazar , I should be back on this later this week. Hopefully, today once I dial in the SW changes for unrelated dev.