You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have an older MTK based usb/bt receiver (outputs nmea) that uses the CDC-ACM driver. When I open it via this app, nothing happens.
However, when I first open the device once via https://play.google.com/store/apps/details?id=de.kai_morich.serial_usb_terminal (which shows nmea messages coming in correctly) and then close serial-usb-terminal app and reopen it in usbgps then all works fine and gps location is made available as expected. Once I disconnect the usb and reconnect I have to redo this procedure.
Any hints what could be missing in the initialization phase - or how I could assist debugging?
The text was updated successfully, but these errors were encountered:
Hey! I've had a look, and this app would probably need a large amount of refactoring in order fix this.
The app you reference uses this library, which probably provides support for more boards. I've used this library before, but it would probably be a large amount of work to update this app to use it.
I currently don't have a device which I can use to develop this, or the free time to make such a large change :(
I have an older MTK based usb/bt receiver (outputs nmea) that uses the CDC-ACM driver. When I open it via this app, nothing happens.
However, when I first open the device once via https://play.google.com/store/apps/details?id=de.kai_morich.serial_usb_terminal (which shows nmea messages coming in correctly) and then close serial-usb-terminal app and reopen it in usbgps then all works fine and gps location is made available as expected. Once I disconnect the usb and reconnect I have to redo this procedure.
Any hints what could be missing in the initialization phase - or how I could assist debugging?
The text was updated successfully, but these errors were encountered: