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
Hey :)
I have an interesting bug when using v4.4.2 QGroundControl64.apk running on a SIYI MK32 remote control (ARM64).
Expected Behavior
After launching the QGC app after android boot it should connect, but only does so after restarting the app once.
Current Behavior
After booting up the android based remote QGC only connects after starting the app a second time. So if I boot and then launch the app it wont connect, if I then close it and start again it connects fine. I tried this on 2 separate systems (2 different drones running the same software stacks) and it is so far 100% consistent.
The flight module is running Arducopter 4.5 on a Cube Orange+
Does anyone faced the same issue, have a solution or can give me a pointer to fix it in the code?
Steps to Reproduce:
Please provide an unambiguous set of steps to reproduce the current behavior
Reboot android device
have a radio connection established to the flight module
start QGC app
System does not connect
restart app
system connects
System Information
When posting bug reports, include the following information
Operating System: android
QGC Version: 4.4.2
QGC build: stable
Flight Controller: Cube Orange+
Autopilot (with version): Ardupilot Copter 4.5
Detailed Description
The text was updated successfully, but these errors were encountered:
Hey :)
I have an interesting bug when using v4.4.2 QGroundControl64.apk running on a SIYI MK32 remote control (ARM64).
Expected Behavior
After launching the QGC app after android boot it should connect, but only does so after restarting the app once.
Current Behavior
After booting up the android based remote QGC only connects after starting the app a second time. So if I boot and then launch the app it wont connect, if I then close it and start again it connects fine. I tried this on 2 separate systems (2 different drones running the same software stacks) and it is so far 100% consistent.
The flight module is running Arducopter 4.5 on a Cube Orange+
Does anyone faced the same issue, have a solution or can give me a pointer to fix it in the code?
Steps to Reproduce:
Please provide an unambiguous set of steps to reproduce the current behavior
System Information
When posting bug reports, include the following information
Detailed Description
The text was updated successfully, but these errors were encountered: