Add baud rate setting for the GNSS serial port receiver

[bettellam]

Today I was "playing" with Qfield windows.

I usually use bluetooth connection to connect the GNSS receiver and I don't encounter any particular problems, everything OK.... ... at a certain point I wanted to test USB connection... ... try, and try again no result.... Qfield does not receive position.

After two hours of attempts and checks with other programs I thought of checking the default configuration of the COM port in windows: baudrate was set to 9600, but my GNSS receiver is configured to 115200.

With this simple change magically QField started to work, everything perfect I hope this solution can be useful to other users.

I think it is useful to implement in QField a combobox where you can choose the connection baudrate: https://github.com/opengisch/QField/blob/1dde789af9ed962364b99e7b770a3bd8e554a82a/src/core/positioning/serialportreceiver.cpp#L57 SWMaps:

Here .... I wonder: "is this one of the reasons why QField, with an android device, does not connect to an external GNSS receiver connected with USB? " ... this regardless of the access permissions to the smartphone's USB port (android.hardware.usb)... https://github.com/opengisch/QField/blob/80fe9af7b97a2a32c869172d9f1fef4952b2097a/platform/android/AndroidManifest.xml.in#L31

[m-kuhn]

@bettellam could you provide a pull request with a patch to test this? Even if it's without a UI yet, it would be good to validate if the assumption on Android side holds true.

[bettellam]

@m-kuhn Thank you for your trust, but my programming skills are very poor, it's not my job .. at my age I should just be a grandfather... ;-) (I read code already written and I can interpret it). Anyway I'll try.

[nirvn]

@bettellam , is this still a need?

[bettellam]

@nirvn These were tests I ran with Windows, and with the correct configuration, they resolved the issue. I think it can be closed permanently. No other users have reported any problems with this topic.