Sorry, it took me a little longer... I'm entering Winter season already and are fully focussed on the next new major release
I had a look into the log. The problem is that the NMEA stream delivered by the MotoX is delivering valid and invalid fixes alternating. I have added a short sample below showing what is delivered for one second (i.e. 1 fix for a 1 Hz device):
Code: Select all
$GPGSV,3,1,21,02,13,063,34,05,43,057,32,12,16,165,26,18,11,202,26*74
$GPGSV,3,2,21,21,34,261,34,25,47,195,33,26,06,111,22,29,69,350,36*70
$GPGSV,3,3,21,31,08,272,28,13,02,045,,15,04,147,*4E
$GLGSV,2,1,21,66,55,113,32,82,26,307,32,80,23,300,23,79,21,241,25*6A
$GLGSV,2,2,21,65,30,040,34,88,26,082,27,81,56,012,38,67,21,172,32*6B
$GPGSA,A,3,02,05,12,18,21,25,26,29,31,,,,0.9,0.6,0.7*3E
$GPVTG,325.6,T,325.6,M,1.5,N,2.7,K,A*22
$GPRMC,184107,A,3754.218640,N,12218.621121,W,1.5,325.6,051114,0.0,E,A*07
$GPGGA,184107,3754.218640,N,12218.621121,W,1,09,0.6,14.0,M,-26.0,M,,*4B
$GPGSV,3,1,22,02,13,063,29,05,43,057,28,12,16,165,33,15,04,147,24*7D
$GPGSV,3,2,22,18,11,202,28,21,34,261,33,25,47,195,29,26,06,111,23*7A
$GPGSV,3,3,22,29,69,350,37,31,08,272,26,13,02,045,*47
$GLGSV,3,1,22,66,55,113,31,82,26,307,33,80,23,300,25,79,21,241,23*6A
$GLGSV,3,2,22,65,30,039,30,88,26,082,27,81,56,012,36,67,21,172,30*6F
$GLGSV,3,3,22,73,01,344,*53
$GPGSA,A,1,,,,,,,,,,,,,,,*1E
$GPVTG,,T,,M,,N,,K,N*2C
$GPRMC,,V,,,,,,,,,,N*53
$GPGGA,,,,,,0,,,,,,,,*66
The problem are the invalid fixes in the end. Looking just into RMC, we get a valid fix "$GPRMC,184107,A,3754.218640,N,12218.621121,W,1.5,325.6,051114,0.0,E,A*07" in the middle of the above sample which is "overridden" immediately by "$GPRMC,,V,,,,,,,,,,N*53" removing all the information received again.
Before I add another work around for some poor data quality, please check the following item first: are there any GPS apps and/or "Helper" apps installed on your device? In case one of these is installed, to may add the above invalid sentences while no external GPS is connected... Just a theory.