Nexus 5 GPS Errors and other issues

  • I had this problem once (gps located me 300km away) due to hardware. I changed the back-lid and other components (changed my mainboard to phone with broken mainboard) and gps problems were gone. Check the springs touching the lid.

  • Just an update
    1)Checked the hardware nothing about seems damaged
    2)No the new unav updates didn't fix the issue

    issue here: doesn't find my location.

    Scanning around the forum it seems other people with nexus 5 have the same issue. As seen here

    I am just wondering if people who have a nexus 5 could kindly test to see if you get correct location because I starting to think its a bug and not a hardware issue.

    Specifically test on OTA 5
    Just an idea because I am at a loss. Sorry if I keep spamming this issue. Thanks.

  • @that_rin No problem will charge one of mine and see what I get. If anyone else can help or confirm that would be great. Thanks.
    Edit: same issue here

  • Ok we may have a conflict with held over info. Just re installed 16.04 dev with wipe via the installer on nexus5. Downloaded uNav. Opened uNav allowed access to position (this will annoy you) 10 secs and location bang on. No messing about straight there.
    So could you remove uNav via UT Tweak tool clearing cache data info the works first then uninstall and restart the phone. Then install uNav again and see what happens.

  • I checked today while walking to work: N5 with Ubuntu 16.04 (2018-W42) from RC-Channel, uNav 1.9 with opentopo map:
    Initial location after reboot takes less than 1 Minute, but is ~100m away from real location. It takes more ~30 seconds to find the real location (+/-5m).
    After turning off the screen it gave the first time a gps-error and needed to reboot.
    Next tests with turning off the screen (from 1 minute to 4 hours): 3-5 seconds to find location ~50 m away, 5 more seconds to find location +/-5m.
    I got an error executing /usr/bin/gps_test, (with and without sudo), no idea why.
    But uNav works as it should.

  • Here is my experience. I flash my device with wipe data. Install Unav, the location is detected correctly within seconds. After reboot, location isn't detected any more, no matter what I try.

  • @lakotaubp Cleared the cache and uninstalled unav installed after reboot.

    Still having the same issue where it starts me about 20 to 30 miles away from my current position.

    Currently on OTA 5 Stable
    tested with map box and others

    I dont really want to wipe my phone to much invested into it.

  • @lyovushka I don't have the Nexus with me now will test later.

  • @that_rin no don't do that. Let's have a bit more investigation. Just for info did you delete the data and config as well or just the cache

  • @lakotaubp yes I checked all the boxes in UT Tweak tools when clearing unav.

  • @that_rin Thanks for your input and help.

  • @lyovushka Sorry can't replicate this. Restarted my nexus5 uNav had location in 5 mins. More investigation requipped are you mobile data,wifi or both.

  • @Lakotaubp I have both wifi and data. On OTA-3 it usual took seconds to get my approximate position. Why does it take 5 minities? Is AGPS (mozilla location services) off on 16.04?

  • @lyovushka My uNav now not working latest dev update has stopped it on OPO (555) uNav version 2.0. On both wifi and data. Uhgh. Nexus 5 back up on wifi.
    Edit OPO back after 1hour on wifi and data.

  • @lakotaubp I have done wifi and mobile data, wifi only, and mobile data only.

  • If the problem is that the initial location is too far away but it gets better, that's to be expected. Your initial location lock is provided by the Mozilla assisted location service. This could be extremely accurate or extremely poor in your area, but it depends on how many users of Firefox for Android there are around.

    A hardware GPS lock sometimes requires the phone be near a thin window or outside (such as in a car). Inside an apartment complex will usually not do any good.

    I just fired up my Nexus 5, Nexus 7, and Fairphone 2, all got a location lock in seconds. I've been using Mozilla Stumbler to improve their data in my area, so that's to be expected.

    Your location issues are really strange, but they all come back to the GPS hardware lock never happening... I'm not sure why that would be, though.

    In the future, though, please post a separate topic for separate issues. It makes it much easier to follow the discussion and see exactly what the issue.

  • @that_rin hey, nexus 5 gps and OTA-5 works here.
    I have the issue with initial location, but after a few minutes it works. When I'm in hurry, I closed unav and relaunch it just after it found the wrong itinerary. This time, I have the correct position. Hop it could help.

  • Same isue for me with the Nexus 5. But if I reboot the system the just after start uNav then sometime it works fine. No trouble with OnePlus One

  • Hey @that_rin, I'm with you. In my case, GPS has never worked, but I've only started using UBports recently, since the problems began. I did get a few suggestions from the main Telegram group, so I'm going to bring those over to this discussion, in case they provide any useful leads.

    Debugging resource

    myii, [18.11.18 01:11]
    GPS has never worked on my Nexus 5 since first installation. SensorsStatus doesn't show any values. uNav has never resolved correctly. GPS is enabled and for each of the apps. What's the right way to troubleshoot this?

    Rodney, [18.11.18 01:15]
    [In reply to myii]

    Rodney, [18.11.18 01:15]
    ubuntu-location-serviced-cli --bus system --get --property visible_space_vehicles is probably of particular interest

    myii, [18.11.18 01:26]
    [In reply to Rodney]

    phablet@ubuntu-phablet:~$ ubuntu-location-serviced-cli --bus system --get --property visible_space_vehicles
    Attempted to unregister path (path[0] = com path[1] = ubuntu) which isn't registered
    Problem executing the CLI: org.freedesktop.DBus.Error.ServiceUnknown: The name com.ubuntu.location.Service was not provided by any .service files

    Rodney, [18.11.18 01:27]
    i think you might need to run it with sudo

    myii, [18.11.18 01:28]
    Exact same output as above with sudo.

    Starting ubuntu-location-service

    Rodney, [18.11.18 01:27]
    or maybe that means the location-service isn't running

    Rodney, [18.11.18 01:28]
    does it appear in ps afx|grep location output?

    myii, [18.11.18 01:28]

     3777 ?        Ssl    0:00          \_ /usr/lib/arm-linux-gnueabihf/indicator-location/indicator-location-service
     7674 ?        Tsl    0:02          \_ system-settings settings:///location
    23356 pts/19   S+     0:00              \_ grep --color=auto location
    14209 ?        Ss     0:00 /usr/bin/ubuntu-location-provider-geoclue2

    Rodney, [18.11.18 01:29]
    try running sudo start ubuntu-location-service

    myii, [18.11.18 01:30]

    phablet@ubuntu-phablet:~$ sudo status ubuntu-location-service
    ubuntu-location-service start/running, process 23508

    myii, [18.11.18 01:31]
    ubuntu-location-serviced-cli still returning the previous output.

    Error in /var/log/syslog

    myii, [18.11.18 01:31]
    Noticed this in syslog:

    Nov 18 00:37:58 ubuntu-phablet kernel: [ 1488.385225] init: ubuntu-location-provider-geoclue2 main process (9716) killed by SEGV signal
    Nov 18 00:37:58 ubuntu-phablet kernel: [ 1488.385259] init: ubuntu-location-provider-geoclue2 main process ended, respawning

    So no progress so far.

  • @that_rin Maybe there's hope after all... I've been doing a bunch of troubleshooting and somehow it's all working properly. GPS resolution within around 10 seconds for all applications involved.

    Now, I wouldn't be surprised if I lose this once I reboot, which I'll test at some point soon. I stopped and started services so there's something in there that may be plaguing you as well. If I manage to isolate the workaround, I'll report back here with my findings.

Log in to reply