Error in 2.4 RTM. Android

Pedals2Paddles · Sep 5, 2016

It seems that RTM is not using the GPS location of the phone/tablet. Instead, it is using the "battery saving" triangulation using cell towers and WiFI. As such, your location will quite literally be all over the map. It would be like trying to use Google Maps or Waze without the GPS enabled.

It seems the work around is to make sure your set your phone's location services for GPS only (aka "Device only). That way, the app has no choice but to use it. Older versions of the app would force you to use high accuracy mode, which allowed for cell phone and wifi location based services. But it appears 2.4 does not. I'm going to try it later this evening if I have time to fly.

SteveReno · Sep 5, 2016

Thanks P2P for a local view point on this error in the Android Solo App.
Can any one using Solex, tell us if same error happening. It's been reported it's fine so far?

Pedals2Paddles · Sep 5, 2016

Just went out to test my theory. No dice. It didn't even try. My location as far as the 3DR Solo app was concerned was on the bench near the parking lot. Never updated at all.

SteveReno · Sep 5, 2016

Thanks for confirming the error.
I think Solex fixed it, but until we can also confirm this, then all Android users should NOT use RTM,
@Pedals2Paddles do you concur not using RTM on 2.4 Android?

pyrate · Sep 5, 2016

I have not personally confirmed, but some names I trust have confirmed solex does not suffer from the same issue

SteveReno · Sep 5, 2016

pyrate, If you trust them, that's good enough for me.

This is enough info. to Tell everybody STOP using the RTM function " Return to me" in the 3DR's Solo App. If you do, Your Solo may end up somewhere other then your location.

Were just trying to track down errors reported by respected users, the latest release 2.4 Solo app "Android" so as not have any malfunctions in flight to cause lost of Solo.

The Soloex App By Kelly Schrock. seems ok for this function.

Thanks goes to: for testing &/or reporting
Pedals2Paddles
pyrate
Stephan Schindewolf

pyrate · Sep 5, 2016

Had it happen to me during tests, its scary.
since I was testing close in it was easy to hit fly and recover.
But imagine you lose you connection with the tx at range and cannot intervene
bye bye solo
It works on IOS and Solex, so just leave it on return to launch until it get sorted out if you are on the official 2.4 android

Pedals2Paddles · Sep 5, 2016

I absolutely agree that RTM should not be used in the 3DR Solo app on an Android device.

pyrate · Sep 5, 2016

Did you have it happen?
freaky, mine took off full speed in a direction that I had not flown ever, and about 130 degrees out of align to where I was.
it was like whoa

Pedals2Paddles · Sep 5, 2016

It will go wherever the (horribly inaccurate) triangulation location says your phone is. It will do so at the RTL speed, which by default I believe is about 20mph.

SteveReno · Sep 6, 2016

Confirmation from Phu of Bug in 2.4 update on Android

Don't know if he can do anything about it anymore? Since he doesn't Code for 3DR anymore...Wow

SteveReno · Sep 6, 2016

@Maddog :
Read a your post somewhere about 3DR coming full circle with Ardu, Why can't ArduPilot jump in & fix this bug?

pyrate · Sep 6, 2016

Because so much of the code is not open.
Ardupilot team can only do so much without 3DR cooperating

Pedals2Paddles · Sep 6, 2016

Phu (former app developer for 3DR) responded to the long post on the Facebook group about this. He confirmed there is indeed a bug in how the 3DR Solo android app aquires location. So we're definitely not all totally nuts. He also confirmed that rewind was removed from the failsafe and home button pushes. It is only activated by long pressing the pause button and nothing else. Which yes, totally defeats its purpose.