GPS on MX4 UT edition w/OTA10
-
Hi,
Does anyone succeed to have GPS working on MX4 ?
Based on my experience and tests:
uNav, Pure Maps (btw, tremendous nice SW), Gmaps never ever got FTTF, even lying the phone outdoor for hours.uSensor finds supported backend and active, no error in source status , but still no position infomation (lat, long, etc)
sudo gps_test shows sometimes gps info, but ends systematically with a segfault:
#############
*** setup signal handler
*** get gps interface
*** device info
id = gps
name = Hardware GPS Module
author = The MTK GPS Source Project
*** init gps interface
** Creating thread: 'GPS NATIVE THREAD' (start=0xb6cd2d79, arg=0xb6cdba54)
** After thread_create: 'GPS NATIVE THREAD', error=0 (start=0xb6cd2d79, arg=0xb6cdba54)
**** Thread wrapper start (start=0xb6cd2d79, arg=0xb6cdba54) ****
*** set capabilities
capability is 00000001
*** setting positioning mode
*** start gps track
*** status callback
*** engine on
*** status callback
*** session begin
*** gps tracking started
*** tracking....
*** nmea info
timestamp: 28983000
nmea (69): $GPGGA,235944.000,8960.0000,N,00000.0000,E,0,0,,137.0,M,13.0,M,,*4E*** nmea info
timestamp: 28983000
nmea (45): $GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30*** nmea info
timestamp: 28983000
nmea (71): $GPRMC,235944.000,V,8960.0000,N,00000.0000,E,0.000,0.00,050180,,,N*40*** nmea info
timestamp: 28983000
nmea (39): $GPVTG,0.00,T,,M,0.000,N,0.000,K,N*32*** nmea info
timestamp: 28983000
nmea (23): $GPACCURACY,3162.1*3FSegmentation fault
##############Any chance to debug or fix?
BR,
-
Same here. GPS stopped working under Ubuntu Touch just before they gave up and it doesn't work under UBports for MX4 with OTA-11.
Each time I want to use it, I have to wait about 1 hour until unav or Pure Maps finds my location. Even I do not move, I have to wait the same time, when I try it again.
I changed the OS for some weeks to Android/Flyme and it was not much better. Only Google Maps found my place fast by means of WiFi. But all navigation apps failed for at least first 30 minutes of driving.
So I think it's a hardware problem.