Hi am using a locationManager with a Nmea listener. Everything seems to work fine but here is the issue.
I log out the messages in my logcat and i notice something very strange... The messages seems broken or lacking information
example from the logcat.
09-24 11:41:36.899: D/BLUE(3153): LocationManager $GPGGA,094138.0,,,,,0,,,,,,,,*7F
09-24 11:41:37.899: D/BLUE(3153): LocationManager $GPGGA,094139.0,,,,,0,,,,,,,,*7E
09-24 11:41:38.899: D/BLUE(3153): LocationManager $GPGGA,094140.0,,,,,0,,,,,,,,*70
09-24 11:41:39.899: D/BLUE(3153): LocationManager $GPGGA,094141.0,,,,,0,,,,,,,,*71
09-24 11:41:40.899: D/BLUE(3153): LocationManager $GPGGA,,,,,,0,,,,,,,,*66
09-24 11:41:42.899: D/BLUE(3153): LocationManager $GPGGA,,,,,,0,,,,,,,,*66
09-24 11:41:43.899: D/BLUE(3153): LocationManager $GPGGA,,,,,,0,,,,,,,,*66
09-24 11:41:44.899: D/BLUE(3153): LocationManager $GPGGA,,,,,,0,,,,,,,,*66
09-24 11:41:45.909: D/BLUE(3153): LocationManager $GPGGA,,,,,,0,,,,,,,,*66
As far as i know. The format of the GPGGA should be something like this
$GPGGA,123519,4807.038,N,01131.000,E,1,08,0.9,545.4,M,46.9,M,,*47
Now i tried other types like GLL and its the same issue. I also tried just reading the bytes directly with bluetooth but its the same thing.
Anyone have similair issues with Nmea messages?
It looks like the GPS does not have a fix. Are you certain you have a good enough signal? Please verify outdoors under an open sky.