There is this app for Android:
https://play.google.com/store/apps/details?id=googoo.android.btgps&hl=en You scroll across the top from right to left you see "main" "status" "NMEA" like in the pictures and there is a Google map and position seen.
As long as you have a live internet link on your phone, you can get your rocket position displayed.
You install the app, allow mock locations in your devices setup (you did become a developer right?) Now, you pair your Bluetooth receiver say an EggFinder. Now you fire up the "Bluetooth GPS" and it will allow you to bond to the HC-06 or -05
board that's bringing in your rocket's position. Click on it and your device will ignore your internal GPS and you can see the rockets position on the map if you keep scrolling in this app.
Now, if you minimize the "Bluetooth GPS" app (You'll see a little blue ball in the upper left pulldown) any GPS app you call up will be using this stream you have coming into your device, ie. your rocket and ignore the internal GPS of your Android device.
You can see where your rocket is but you can't navigate. It's a fun trick to mess with it.
I've been messing with 3DR radios in another thread and discovered with a $6.25 Neo-M8N clone I can send combined GPS/Glonass strings over Rf and have more accurate plotting of a rocket's position. Problem is "GPS Rocket Locator" can't read these
strings. But............ Fire up the "Bluetooth GPS" Android app, it can read these strings and show a 16 - 20 satellite lock. Wow, very stable with little jitter here. Now, minimize "Blue tooth GPS" and fire up GPS Rocket Locator and you'll get the blue dot
as the rocket location. For some weird reason, GPS Rocket Locator cannot read the raw GPS/Glonass strings UNLESS they are going through the "Bluetooth GPS" program. I don't know why but I couldn't get the tracker to come up
with the red pushpin. I couldn't get several APRS programs to read the combined GPS/Glonass strings as a local GPS position either but running it through B/T GPS and GPS Rocket Locator can decode and plot the position as the Blue GPS or blue dot.
Soooooooooooooooo, what do you do about local position? Well, I got a cheap B/T GPS source, fired it up, got a lock, paired it to the Android and opened GPS Rocket Locator. In the setup, instead of using the HC-06/05 (that's already being used as
the rocket's position) I selected the B/T GPS source I just paired. After a short time, I get the Red Pushpin that's my local source. Fun trick but it's bass ackwards. Works.
Adrian Adamson from Featherweight reports in another thread he has a prototype tracker that also uses GPS/Glonass for more accurate plotting. Will likely be forsale and he'll get plenty of customers I expect.
Drove around and got this:
The blue dot (rocket) and red push pin (local) jumped very quickly together once a second. Usually with the rocket as the red pushpin (EggFinder) and the blue dot as the local position, when I drove around in the car with both devices, I
get the red pushpin (rocket) changing once a second whereas the blue dot would only move once every 5 seconds. Once every 5 seconds for a local position is perfectly fine with tracking but for some weird reason, when running the
system in reverse, using GPS/Glonass strings for the rocket, the positions of both is pretty instantaneous.
There is interference galore with 3DR on 433Mhz, 500mW. Maybe 900Mhz might be better. I found as long as I didn't have the -M8N GPS lying on the 3DR radio, it receives the position strings pretty well. Lying on the radio and the
GPS loses lock. Perhaps something about the "spread spectrum" transmitter that interferes with the GPS in close proximity. As long as the GPS was out on its short cable, it had good signal strength as shown on the UCenter UBlox
utility.
Kurt