dlw

Yeah, I’ll dig that way. I realized the CDC driver must be working though because I had no problem talking over an OTG cable to a Pixhawk here using that...

Also, interesting to note - it looks like RX might be working correctly - when the ubx driver is trying to configure the M8P at 9600 baud it detects an...

@bkueng @thomasgubler I saw your names on the QGC ubx driver. I've forced QGC to use the FTDI adapter as a U-Blox GPS for debugging and hooked up a logic...

The following image is the TX/RX scope of macOS successfully connecting to the M8P (around 7 seconds it hits the correct baud/protocol). [macOS Successful RTK handshake with M8P](https://i.imgur.com/vLIS7w7.png) The next...

Another follow up - I'm finding that the serial write messages on android are getting cut short for some reason. I've fixed the baud rate to 9600 and forced it...

Another note on that android plot - the 6 bytes represent the 2 SYNC bytes, the 2 byte MSG ID, and the 2 byte payload length - 0x28 = 40...

Thanks @bkueng I'm digging into QSerialPort and how it interfaces with the lower level serial drivers (qtandroidserialport and the hoho usbserial drivers). I'm just wondering why every other serial interface...

Tracing down the issue I see [_serial->waitForBytesWritten(-1)](https://github.com/flightwave/qgroundcontrol_public/blob/14de1c0022c93126750963868f93ed4b91a8cf6f/src/GPS/GPSProvider.cc#L211) is a culprit. I've noticed that the write implementation in [SerialLink is different](https://github.com/flightwave/qgroundcontrol_public/blob/14de1c0022c93126750963868f93ed4b91a8cf6f/src/comm/SerialLink.cc#L89) and doesn't use this function - which is why android...

Currently you don't. The branch linked above has some changes that has a "kind-of" working instance of RTK on android - but you won't be able to use a radio...

Not yet - but possibly in the near future. Feel free to check out https://github.com/mavlink/qgroundcontrol/pull/8210