Nick

Seems like you're calling `super(message)`, although that doesn't seem to be having an effect. But manually setting the `message` property in the constructor does seem to have an effect.

I get much better behavior on TypeScript 3.0+, so I think my dependency on this is out of date.

Actually, now that I look at it some more, I'm going to reopen this. It seems like there hasn't been a release since the Typescript dependency has been updated, so...

This seems similar to #4. I'll copy my response there. In general, you should expect UART data to come in intermittently. Although it may stream continually, the interrupts may be...

Maybe you can use an `ArrayList` and convert that to a buffer after? Is there any sort of expectation you can make about the data? When I've used Modbus, there...

If I'm talking from Android Things to a Modbus peripheral, or vice-versa, there should be some established protocol of the types of messages being sent. You should be able to...

If there's no way to judge with start/end characters, you may be able to log the timestamp of each UART event and split it that way.

Seems like you've opened it in another activity without closing it. See [this Stackoverflow answer](https://stackoverflow.com/questions/48437428/android-os-servicespecificexception-gpio2-io02-is-already-in-use-code-16) to learn more.

Where are you closing it? In the activity's `onDestroy` method? Do you need to architect your application with multiple activities?

Can you add a type of asynchronous wait before starting your activity, like using a Handler: ```Java try { closeUart(); } catch (IOException e) { Log.e(TAG, "Error closing UART device:",...