Matej Drobnič
Matej Drobnič
Yup it works and it actually works very well, until it disconnects.
`getExecOutput` workaround is not suitable in many cases because it stores entire output of a command in memory, so it cannot be used for piping large things.
This seems to do the trick: ```kotlin (ProviderRegistry.getLoggingProvider() as TinylogLoggingProvider).writers.forEach { it.flush() } ``` However, from what I can see in the code, flush is not synchronized when logging thread...
Unfortunately, writes are created internally by the TinyLog. To use those synchronized decorators, I would have to create them manually to use this synchronized writer and by this not using...
Wouldn't then that not generate the javadoc (whole point of running dokka)?
From what I can see, this exclude does not even work at all? Because excludes are relative to the source set root. So if source set already starts in `build`...
I guess usage of the Android resources (`R` class) could be one clear indicator that this project cannot be a JVM project?
The phone was not offline for 2 weeks and I did not receive any warnings about phone connection, so I'm not sure it's that.
`gstreamer 1.26.1-1.1` at the moment, but I'm regularly updating it so it's usually the latest version. I can't say for sure about audio formats, because I have mix of them,...
Thanks for the info. I've actually been unable to reproduce this issue in a while, so I will close this issue and if it starts happening again, I will reopen...