GPS and location detection not working on Nexus 4

Bug #1367884 reported by Tomas Öqvist
38
This bug affects 9 people
Affects Status Importance Assigned to Milestone
touch-preview-images
New
Undecided
Unassigned

Bug Description

Mako with MultiROM, utopic r235

None of the apps I have tried including Weather, Google maps, OSM Touch and SensorStatus are able to use the phones GPS. The SensorStatus app actually reports "Found supported backend", but finds no position or other GPS data.

Location detection on the other hand is doing something, but it is really far off when it comes to determining the actual location of the device. The Weather app suggests my location as Vänsjö, Jämtland, which is about 400 km north of Stockholm where I am at. OSM Touch reports "no location available" and Google maps "Your location could not be determined"

I don't know if the GPS has to "waken up" somehow, but it has not shown any form of life for me on Ubuntu Touch, even though it works perfectly fine when booting the phone as Android.

Revision history for this message
jeffcooper (jeff-cooper) wrote :

I noticed this a few weeks ago and it has not been rectified.

I have asked the osmtouch developers if they know abouut it
https://answers.launchpad.net/osmtouch/+question/254334

Revision history for this message
Tomas Öqvist (tomoqv) wrote :

Did Iyou ever have location in OSM Touch? I don't think I have, certainly not with GPS. Neither in OSM Touch nor any other app.

Revision history for this message
jeffcooper (jeff-cooper) wrote :

Yes, I did have location detection working well in OSM Touch. I don't know if it was GPS or not but it certainly was working.

Revision history for this message
Tomas Öqvist (tomoqv) wrote :

It was probably not the GPS, because I have also gotten location in OSMTouch at some point, but it was so far off that could not possibly be a GPS position. I have copied this bug report to https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1368367 because I think that bugs against Touch Preview Images are no longer monitored by the Ubuntu Team. Please continue the discussion there.

Revision history for this message
jeffcooper (jeff-cooper) wrote :

Digging into it today I found the following after running OSM Touch and touching the location detection arrow :-

phablet@ubuntu-phablet:/$ cat /var/log/ubuntu-location-service/com.ubuntu.location.WARNING
Log file created at: 2014/09/11 15:24:31
Running on machine: ubuntu-phablet
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
E0911 15:24:31.517678 2420 skeleton.cpp:177] Error creating session: Client lacks permissions to access the service with the given criteria
E0912 08:52:39.514560 2419 skeleton.cpp:177] Error creating session: Client lacks permissions to access the service with the given criteria

So it seems like a permissions issue?

Also, going back to the start of the warnings:-

phablet@ubuntu-phablet:/$ cat /var/log/ubuntu-location-service/com.ubuntu.location.ubuntu-phablet.invalid-user.log.WARNING.20140809-134227.916
Log file created at: 2014/08/09 13:42:27
Running on machine: ubuntu-phablet
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
W0809 13:42:27.226502 916 ofono_nm_connectivity_manager.cpp:171] Exception while creating connected radio cell: org.freedesktop.DBus.Error.UnknownMethod: Method "GetProperties" with signature "" on interface "org.ofono.NetworkRegistration" doesn't exist

All warnings are the same as above until:-

phablet@ubuntu-phablet:/$ cat /var/log/ubuntu-location-service/com.ubuntu.location.ubuntu-phablet.invalid-user.log.WARNING.20140822-100144.924
Log file created at: 2014/08/22 10:01:44
Running on machine: ubuntu-phablet
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
E0822 10:01:44.903519 1942 skeleton.cpp:177] Error creating session: Client lacks permissions to access the service with the given criteria

Then:-

phablet@ubuntu-phablet:/$ cat /var/log/ubuntu-location-service/com.ubuntu.location.ubuntu-phablet.invalid-user.log.WARNING.20140827-070346.912
Log file created at: 2014/08/27 07:03:46
Running on machine: ubuntu-phablet
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
E0827 07:03:46.443877 912 ofono_nm_connectivity_manager.cpp:141] Error while setting up access to radio and network stack: org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1

Then the rest are the permissions errors with one more of the "Error wile setting up access" errors.

And for reference:-
phablet@ubuntu-phablet:/$ system-image-cli -i
current build number: 203
device name: mako
channel: ubuntu-touch/utopic
last update: 2014-08-22 07:57:57
version version: 203
version ubuntu: 20140821.1
version device: 20140811.1

last update: 2014-08-22 07:57:57 corresponds to the start of the permissions errors.

Revision history for this message
Tomas Öqvist (tomoqv) wrote :

@jeffcooper: Could you please also update https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1368367 with this information?

Revision history for this message
jeffcooper (jeff-cooper) wrote :

Also, thinking back, location detection was definitely working on 1st of July which was prior to me upgrading to utopic.

Revision history for this message
jeffcooper (jeff-cooper) wrote :

Missed the post containing the link

https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1368367

while posting further today.

It's dificult to know where is the most appropriate place to post bugs but I don't think that this bug is to do with the location indicator. It is more lkely to be do do with the location service. How about

https://bugs.launchpad.net/ubuntu/+source/location-service ?

Revision history for this message
Tomas Öqvist (tomoqv) wrote :

You are probably right, I missed that one. I will report the bug there as well.

Revision history for this message
Tomas Öqvist (tomoqv) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.