Naviator Forums

The Navigation Solution for Android Aviators

You are not logged in.

Announcement

Become a fan of Naviator!
For urgent issues please use our Contact Form.
Naviator version 3.9.1 is now available. Click here for details.
New: We are pleased to offer complementary annual subscriptions to pilots who hold a valid CFI certificate issued by the FAA. Click here for details.

#1 2015-Jul-14 9:36 am

JohnAJohnson
Member
Registered: 2013-Jul-20
Posts: 67

3.3.3 and XGPS170

I haven't been able to connect Naviator and my XGPS170 together on the last couple of flights, which I think jibes with the 3.3.3 update.  The two had worked fine until recently and the XGPS170 continues to work fine with another Android app, and with an iPad app. I have turned Bluetooth on and off and unpaired and (re)paired, and in Naviator, I have reselected the Bluetooth Device, tried to reconnect, and toggled GPS on and off.  Naviator never makes the connection (the blue light on the XGPS170 always flashes as if it is searching for something to connect to).  The Naviator ADS-B Diagnostics screen shows a receiver connection, but red heartbeat, gps, and FIS-B Uplink.

Last edited by JohnAJohnson (2015-Jul-14 9:40 am)

Offline

#2 2015-Jul-14 3:07 pm

bkspero
Member
Registered: 2011-Sep-24
Posts: 122

Re: 3.3.3 and XGPS170

JohnAJohnson wrote:

I haven't been able to connect Naviator and my XGPS170 together on the last couple of flights, which I think jibes with the 3.3.3 update.  The two had worked fine until recently and the XGPS170 continues to work fine with another Android app, and with an iPad app. I have turned Bluetooth on and off and unpaired and (re)paired, and in Naviator, I have reselected the Bluetooth Device, tried to reconnect, and toggled GPS on and off.  Naviator never makes the connection (the blue light on the XGPS170 always flashes as if it is searching for something to connect to).  The Naviator ADS-B Diagnostics screen shows a receiver connection, but red heartbeat, gps, and FIS-B Uplink.

I've rebooted the tablet and reconnected ok at that point.

Offline

#3 2015-Jul-14 3:31 pm

flyzone
Member
Registered: 2012-Oct-04
Posts: 223

Re: 3.3.3 and XGPS170

I also have connected my XGPS170 with 3.3.3. No issues.

Offline

#4 2015-Jul-15 6:06 am

JohnAJohnson
Member
Registered: 2013-Jul-20
Posts: 67

Re: 3.3.3 and XGPS170

I figured it out this morning.  I have been loading two apps (Naviator and iFly GPS), and toggling back and forth between the two while in flight (some features are better or exist in one, and not the other).  It seems that whichever app loads first grabs the XGPS170 and won't share with the other.  In the last couple of flights, I had been loading iFly GPS first, and of course Naviator couldn't access the XGPS170.

Offline

#5 2015-Jul-16 11:23 am

jimgfitzgerald
Member
Registered: 2012-Oct-26
Posts: 530

Re: 3.3.3 and XGPS170

You need two tablets.

Offline

#6 2015-Jul-27 2:37 pm

JohnAJohnson
Member
Registered: 2013-Jul-20
Posts: 67

Re: 3.3.3 and XGPS170

Problem isn't as simple as I thought.  Naviator is still having difficulty connecting to my XGPS170, and when I can get it connected, after I exit the software (back back), it won't free up the XGPS170.  Naviator still runs in the background, which is fine, but won't release the XGPS170, which isn't fine (I need to be able to run another app in flight to get winds aloft).

I have done a couple of complete delete and reinstalls, no help.

Again, this is a recent problem.  I've been running the XGPS170, and Naviator and other apps for years and it is only recently that I've had problems, and the problems are only with the Naviator/XGPS170 interface.  Has there been any recent changes to the ADS-B/Bluetooth/XGPS170 routines?  If not, and tips on further troubleshooting would be appreciated.

Last edited by JohnAJohnson (2015-Jul-28 2:11 pm)

Offline

#7 2015-Jul-28 3:12 pm

flyzone
Member
Registered: 2012-Oct-04
Posts: 223

Re: 3.3.3 and XGPS170

If it is just a matter of getting Naviator to stop running you can go to Settings/Apps/Naviator/Force Stop to end it all.

Offline

#8 2015-Jul-28 3:40 pm

rash
Member
Registered: 2013-Mar-19
Posts: 76

Re: 3.3.3 and XGPS170

Also, when I've wanted to make sure Naviator has "given up" the 170, I'll hit the "recent apps" button (on my nexus 7), swipe it away there, then turn bluetooth off (and back on if needed)...

Offline

#9 2015-Jul-29 11:48 am

jimgfitzgerald
Member
Registered: 2012-Oct-26
Posts: 530

Re: 3.3.3 and XGPS170

I use Advanced Task Killer to shut down Navigator. You shouldn't have to, but you do.

Offline

#10 2015-Jul-29 12:22 pm

Mike
Administrator
From: Vancouver, BC
Registered: 2011-Mar-16
Posts: 1,206
Website

Re: 3.3.3 and XGPS170

This code hasn't changed in quite some time so I'm not sure why this problem has just started to manifest with the latest update. In any case, I'll review the code to make sure there aren't any obvious issues with it.

The "back back" method of exiting Naviator should take care of everything, but if you need to kill the Naviator process for whatever reason the method suggested by rash is the quickest and easiest. All it takes is a single tap and a swipe. There shouldn't be any need for task killer apps on modern versions of Android.

Cheers,
Mike

Offline

#11 2015-Jul-30 2:01 pm

jimgfitzgerald
Member
Registered: 2012-Oct-26
Posts: 530

Re: 3.3.3 and XGPS170

I have always had to kill Naviator using Advanced Task Killer on my Nexus 7 and Droid.  If I don't, it continues to download TFR's.

Offline

Board footer

Powered by FluxBB