MX4 GPS doesn't work at all

[maarten klop]

When using location for navigation, GPS is essential. Location can also be based on Wifi or phone network, but accuracy for that is insufficient for driving/geocaching/any application except nearby restaurants.

I can currently only get a location based on wifi / phone network. If I disable this feature, I get no location at all. Not after reboot, not sometimes, not ever.

Trying to do: Navigate using GPS and/or network

What I expect: Accuracy is high with all location services on. It decreases slightly when network based location is switched off. It decreases sharply when only GPS is switched off.

What happens: Accuracy is very low (30m - 2000m) with all location services on. Location is impossible when network based location is switched off. It doesn't make a difference if I switch the GPS on or off.

This may be a hardware issue, and I'll probably be sending in my phone (MX4) for check/repair, but that would mean missing my phone. I'd much rather troubleshoot myself.

I already have location test and sensorsstatus to monitor this, but I want to know more about if the chip is functioning. Which logs are relevant? I've thought about flashing android on and seeing if that helps (which makes it a software issue), or doesn't (which makes it a hardware issue). Is there an easier way to get an answer to the software/hardware question?

Thanks!

Meizu MX4, Ubuntu 15.04r4

[Pat McGowan (pat-mcgowan)]

The locations service generally works ok on my mx4, but note that a gps fix can take several mins
Several improvements recently landed and others are in progress

[Thomas Voß (thomas-voss)]

Relevant logs are documented here: https://wiki.ubuntu.com/Process/Merges/TestPlan/location-service#Forensics

[Pat McGowan (pat-mcgowan)]

Seeing some problems recently when no wifi connection, often failing to get a fix

$ ubuntu-location-serviced-cli --bus system --get --property visible_space_vehicles
Visible space vehicles:
Attempted to unregister path (path[0] = com path[1] = ubuntu) which isn't registered

[Pat McGowan (pat-mcgowan)]

Output of
$ sudo GLOG_v=1000 GLOG_logtostderr=1 ubuntu-location-serviced-cli --bus system --test

[Pat McGowan (pat-mcgowan)]

When I request location in google maps it reports it cannot get precise location, and I do not see any process activity from the location stack in top

ps ax | grep location
 2154 ? Ssl 0:00 /custom/vendor/here/location-provider/bin/arm-linux-gnueabihf/slpgwd --preinst-dir /custom/vendor/here/location-provider/share --storage-dir /userdata/system-data/var/lib/ubuntu-location-provider-here
 2182 ? Ssl 0:00 /custom/vendor/here/location-provider/bin/arm-linux-gnueabihf/posclientd --preinst-dir /custom/vendor/here/location-provider/share --storage-dir /userdata/system-data/var/lib/ubuntu-location-provider-here
 2233 ? Ssl 0:00 /custom/vendor/here/location-provider/bin/arm-linux-gnueabihf/ubuntu-espoo-service --bus system
 2355 ? Ssl 0:00 /usr/lib/arm-linux-gnueabihf/indicator-location/indicator-location-service
 6837 pts/8 S+ 0:00 grep --color=auto location

[Pat McGowan (pat-mcgowan)]

I rebooted and now I immediately get an approximate location centered around .5 mi from my actual location

[Pat McGowan (pat-mcgowan)]

Now i see the location and trust daemons running

ps ax | grep location
 2130 ? Ssl 0:00 /custom/vendor/here/location-provider/bin/arm-linux-gnueabihf/slpgwd --preinst-dir /custom/vendor/here/location-provider/share --storage-dir /userdata/system-data/var/lib/ubuntu-location-provider-here
 2157 ? Ssl 0:00 /custom/vendor/here/location-provider/bin/arm-linux-gnueabihf/posclientd --preinst-dir /custom/vendor/here/location-provider/share --storage-dir /userdata/system-data/var/lib/ubuntu-location-provider-here
 2187 ? Ssl 0:00 /custom/vendor/here/location-provider/bin/arm-linux-gnueabihf/ubuntu-espoo-service --bus system
 2332 ? Ssl 0:00 /usr/lib/arm-linux-gnueabihf/indicator-location/indicator-location-service
 2805 ? Ssl 0:00 /usr/bin/trust-stored-skeleton --remote-agent DBusRemoteAgent --bus=system --local-agent MirAgent --trusted-mir-socket=/var/run/user/32011/mir_socket_trusted --for-service UbuntuLocationService --with-text-domain ubuntu-location-service --store-bus session
 3093 ? Ssl 0:00 /usr/bin/ubuntu-location-serviced --bus system --provider gps::Provider --provider remote::Provider --remote::Provider::name=com.ubuntu.espoo.Service.Provider --remote::Provider::path=/com/ubuntu/espoo/Service/Provider
 5734 pts/25 S+ 0:00 grep --color=auto location

[WESERTRAINER Flight Training (s-service)]

Still no GPS on my meizu mx4 OAT 10.1 at all. Tryed to check this issue by installation of SensorStatus App but still no GPS data available.

[Pat McGowan (pat-mcgowan)]

Please check if this file exists and if so delete it and restart
/var/lib/ubuntu-location-service/config.ini
If that fixes things please report back here

[WESERTRAINER Flight Training (s-service)]

config.ini deleted and phone restarted. Unfortunately after 15 min of acquiring outside under free sky still no GPS data in SensorStatus App available. Also no GPS data under UNAV availabe. All Apps are allowed to access Position Data.

[Pat McGowan (pat-mcgowan)]

seeing the same

[Pat McGowan (pat-mcgowan)]

using the command in comment #3 I see satellites but the app still doesn't show any data so assuming the app is not of help here, and it seems gps is working

phablet@ubuntu-phablet:~/loc$ ubuntu-location-serviced-cli --bus system --get --property visible_space_vehicles
Visible space vehicles:
 (type: gps, prn: 7, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 42 deg, elevation: 310 deg)
 (type: gps, prn: 8, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 67 deg, elevation: 187 deg)
 (type: gps, prn: 9, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 42 deg, elevation: 248 deg)
 (type: gps, prn: 11, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 13 deg, elevation: 180 deg)
 (type: gps, prn: 16, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 41 deg, elevation: 61 deg)
 (type: gps, prn: 21, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 9 deg, elevation: 38 deg)
 (type: gps, prn: 23, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 32 deg, elevation: 210 deg)
 (type: gps, prn: 26, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 16 deg, elevation: 76 deg)
 (type: gps, prn: 27, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 69 deg, elevation: 73 deg)
 (type: gps, prn: 30, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 14 deg, elevation: 307 deg)
 (type: gps, prn: 65, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 3 deg, elevation: 239 deg)
 (type: gps, prn: 66, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 16 deg, elevation: 289 deg)
 (type: gps, prn: 67, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 8 deg, elevation: 339 deg)
 (type: gps, prn: 74, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 29 deg, elevation: 100 deg)
 (type: gps, prn: 75, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 67 deg, elevation: 30 deg)
 (type: gps, prn: 84, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 32 deg, elevation: 36 deg)
 (type: gps, prn: 85, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 67 deg, elevation: 108 deg)
 (type: gps, prn: 86, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 30 deg, elevation: 182 deg)
 (type: gps, prn: 211, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 39 deg, elevation: 192 deg)
 (type: gps, prn: 212, snr: 0, has_almanac_data: 0, has_ephimeris_data: 0, used_in_fix: 0, azimuth: 67 deg, elevation: 91 deg)

[WESERTRAINER Flight Training (s-service)]

First of all: Partially Success !

Deleting /var/lib/ubuntu-location-service/config.ini and restarting device seems to unlock the GPS-Functionality at all !

A first position fix has only been available after connect to WIFI Network.

SensorStatus shows continously updated position data. Also UNAV has been able to locate the correct position.

unfortunately after two or three minutes GPS falls asleep and stops updating position data in SensorStatus.

Also UNAV stops updating position data.

After restarting SensorStatus and also restarting UNAV refreshes position data. Restarting UNAV only leads to an error report by UNAV: No access to GPS.

The output of

ubuntu-location-serviced-cli --bus system --get --property visible_space_vehicles

is also satellite data and additionally:

Attempted to unregister path (path[0] = com path[1] = ubuntu) which isn't registered

But I don't know what that means !

My general impression: Perhaps the GPS-problems may be caused by incorrect interaction with the power-management software

[Victor Gabillon (victorgabillon)]

GPS has been not working on my Meizu MX4 for a long time time now. Recently it went back to life after the OTA 13 update but only for a couple of hours.
After I tried to connect to WIFI, the GPS dropped. And now, after reboot, or delete the config file as advised in previous comments, I am back to the No-GPS state.
It used to work sometimes when wifi was available but now it seems that the phone is also recently having big problems connecting to WIFI (cannot connect to my work wifi for instance).

[Alessandro Roncador (roncador-ale)]

in my device (Aquaris E5) GPS stopped working after OTA-13 update.