GPS and location detection not working on Nexus 4

[Tomas Öqvist]

Mako with MultiROM, utopic r239

None of the apps I have tried including Weather, Google maps, OSM Touch and SensorStatus are able to use the phone's 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.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[jeffcooper (jeff-cooper)]

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

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

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.

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

[jeffcooper (jeff-cooper)]

After further investigation I have now upgraded the radio firmware to
radio-mako-m9615a-cefwmazm-2.0.1700.84
as I had previously downgraded and upgraded this before when using older versions of Ubuntu Touch.

I don't think that made any difference.

I stoped and restarted the ubuntu-location-service

phablet@ubuntu-phablet:~$ sudo service ubuntu-location-service status
ubuntu-location-service start/running, process 917
phablet@ubuntu-phablet:~$ sudo service ubuntu-location-service stop
ubuntu-location-service stop/waiting
phablet@ubuntu-phablet:~$ sudo service ubuntu-location-service start
ubuntu-location-service start/running, process 5847

When running OSM Touch and SensorsStatus after the restart both apps asked for permision to access my location and location detection started to work again.

However looking in the logs I found the following warning:-
phablet@ubuntu-phablet:~$ cat /var/log/ubuntu-location-service/com.ubuntu.location.WARNING
Log file created at: 2014/09/13 10:29:17
Running on machine: ubuntu-phablet
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
E0913 10:29:17.485262 5865 android_hardware_abstraction_layer.cpp:157] Error downloading GPS Xtra data: /build/buildd/net-cpp-1.1.0+14.10.20140804/src/core/net/http/impl/curl/request.h@157 - execute: Timeout was reached: No space left on device

See: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1367835

[jeffcooper (jeff-cooper)]

The above worked until a reboot. After the reboot even restarting the ubuntu-location-service did not consistently help. After several attempts I got the location detection working again but still got the "Timeout was reached: No space left on device" warning once it was working.

[Tomas Öqvist (tomoqv)]

I have switched to rtm r1 single-boot and got location working in OSMTouch, Google maps and a weather site on the web. The accuracy indicated that the GPS was involved. But after a reboot, the location no longer works for me. Will see if it gets going again if I wait. It sure feels strange though, that it should suddenly stop working after a reboot.

[jeffcooper (jeff-cooper)]

I am now getting different errors in the logs after upgradin on the development channel now on utopic r243.

phablet@ubuntu-phablet:~$ cat /var/log/ubuntu-location-service/com.ubuntu.location.WARNING
Log file created at: 2014/09/21 08:54:13
Running on machine: ubuntu-phablet
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
E0921 08:54:13.130431 966 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
E0921 08:55:32.130309 1193 skeleton.cpp:126] org.freedesktop.DBus.Error.ServiceUnknown: The name com.ubuntu.espoo.Service.Provider was not provided by any .service files
E0921 08:55:32.137905 1193 skeleton.cpp:240] org.freedesktop.DBus.Error.ServiceUnknown: The name com.ubuntu.espoo.Service.Provider was not provided by any .service files

I was considering a reinstal and using the RTM channel but since Tomas' comment above I am not sure that will help.

[Tomas Öqvist (tomoqv)]

The location support in RTM is "hit and miss". Sometimes it works, sometimes it doesn't, but it is better than I ever achieved with 'devel-proposed'.

[Tomas Öqvist (tomoqv)]

It seems as if the GPS takes really long to "wake up" after a reboot. Just got it working again an hour or so after the last reboot.

[Johannes (hummlbach)]

Hello everybody!

I've get the following error (already mentioned above):

phablet@ubuntu-phablet:~$ test_ubuntu_app_api_location_service
E1005 14:19:23.096575 25459 skeleton.cpp:177] Error creating session: Client lacks permissions to access the service with the given criteria
ua_location_service_create_session_for_high_accuracy: Error creating instance: virtual com::ubuntu::location::service::session::Interface::Ptr com::ubuntu::location::service::Stub::create_session_for_criteria(const com::ubuntu::location::Criteria&): com.ubuntu.location.Service.Error.CreatingSession: Error creating session

For me it does not depend on the uptime or something... (It simply never works ;) [devel channel])
But GPS itself seems to work(?):

phablet@ubuntu-phablet:~$ test_gps
....
....
timestamp: -531229311
nmea (63): $GPGSV,6,4,24,21,14,074,,22,63,105,,27,77,139,,76,15,334,25*71
*** nmea info
timestamp: -531229311
nmea (65): $GPGSV,6,5,24,75,20,279,27,85,39,309,31,74,01,233,,70,21,180,*77
*** nmea info
timestamp: -531229310
nmea (61): $GPGSV,6,6,24,69,61,120,,84,71,039,,83,26,101,,68,35,037,*77
*** location callback
flags: 55
latitude: 48.649156
longtide: 9.204716
accuracy: 34.000000
utc: -531229384
....
....

Greetings
Johannes
So it seems to be a problem with the location-service itself(?). Or am I getting something wrong?

[Tomas Öqvist (tomoqv)]

Not much luck here lately. I have switched to rtm-proposed for Mako, but I haven't seen any sign of life for the GPS in the past week or soo. Now I don't even get GSM location. Good thing I don't rely on the GPS or mobile positioning on the phone, but it sure would be nice to have it working consistently...

[Johannes (hummlbach)]

I've played around a bit and got it working acceptably here... (I've switched to the rtm image some time but I think that's not the point...)
It seems like the location service is intentionally started without gps support. See ps -eaf | grep location and /etc/init/ubuntu-location-service.override. But deleting the .override file did not seem to be sufficient. It works for me if I let upstart start the location service with gps::Provider as the only provider... (exec /usr/bin/ubuntu-location-serviced --bus system --provider gps::Provider).

[Nara Huang (narahuang)]

I could also reproduce this issue on Mako using Vivid r88.

Package version:

ii indicator-location 13.10.0+14.10.20141007-0ubuntu1
ii libqt5location5:armhf 5.3.2-2ubuntu1
ii libqt5location5-plugins:armhf 5.3.2-2ubuntu1
ii libubuntu-location-service2:armhf 2.1+15.04.20150126.1-0ubuntu1
ii qml-module-qtlocation:armhf 5.3.2-2ubuntu1
ii ubuntu-location-provider-here 0.1+15.04.20141110-0ubuntu1
ii ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1

[alexoverton (alexjoverton)]

Can confirm this still exists. LGD Nexus 4. 15.04 (r150)

definitely an issue across the board nothing functioning re GPS sensors

[Zachary Igielman (zacharyi123)]

This bug still applies to me although running 'sudo service ubuntu-location-service restart' seems to temporarily fix it

[Hugo Venhorst (yougo)]

Device: LG Nexus 4
OS: Ubuntu 15.04 r168 dual boot

Still no gps at all for any app.

Is there anything at all I can do? File system is read-only at the moment. Not sure what breaks if I change that.

On android I heavily use gps and it's definitely a show stopper on uTouch :-(

[Jacques (jcl84)]

I'm experiencing the same issue. I have no GPS in any application, and none of the temporary fixes above do not work.
Device: LG Nexus 5
OS: Ubuntu 15.04 (r2)

cat /var/log/ubuntu-location-service/com.ubuntu.location.ERROR
Log file created at: 2015/05/02 00:59:53
Running on machine: ubuntu-phablet
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
E0502 00:59:53.853097 4789 skeleton.cpp:180] Error creating session: Client lacks permissions to access the service with the given criteria

[Hugo Venhorst (yougo)]

Device: LG Nexus 4
OS: Ubuntu 15.10 r220 dual boot

Still no gps at all for any app.

I can't make changes as the file system is locked.

can anyone confirm the instruction at #11 works?

Can anyone say when this will be implemented and released?

Can anyone say whether there is any effort to fix GPS on nexus devices out there?
if not, please just mark this bug as WONTFIX so i can stop hoping.

[jeffcooper (jeff-cooper)]

GPS is still a bit "iffy" for me but it works most of the time if I am patient and I let it get a signal.
I did go through the procedure to enable Nokia's GPS location service - System Settings > Security & Privacy > Location access > " Using GPS, ananymised Wi-Fi and mobile network info."
Currently on 14.10 (r19)

[[e-mail] (extraymond)]

On my nexus 4, it worked prior to ota4.
Can't get it to work on all multiple channels I've tested.

Any chance on getting this fixed?

[Tom Rhodes (tom-rhodes)]

I have problems with GPS on mako too, 15.04 devel channel.

Weather thinks I'm 60km down the road when I'm at home, when out and about sometimes it gets the right town, sometimes not.

Google Maps has only got my location once in about a week of trying.

Is this fixed upstream? I couldn't get stable to install.

[Tom Rhodes (tom-rhodes)]

Same on 15.10 r272

GPS really is a core feature of a smartphone, and Nexus 4 has played a core part in the birth of Ubuntu Touch. Anything I can do to help? How can I get you some debug info?

[Felipe De la Puente (fdelapuente)]

Hi,

I'm running mako with Ubuntu 15.04 20150727 (r22). Same issue with similar
Warning/Error messages in the location-service log files.

I think it used to work in the past with earlier development images (a year
ago or so...)

Is there a known issue without known solution, or just waiting to be
investigated?

Thanks!
Felipe.

On Wed, Jul 29, 2015 at 6:11 AM, Tom Rhodes <email address hidden>
wrote:

> Same on 15.10 r272
>
> GPS really is a core feature of a smartphone, and Nexus 4 has played a
> core part in the birth of Ubuntu Touch. Anything I can do to help? How
> can I get you some debug info?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1368647
>
> Title:
> GPS and location detection not working on Nexus 4
>
> Status in location-service package in Ubuntu:
> Confirmed
>
> Bug description:
> Mako with MultiROM, utopic r239
>
> None of the apps I have tried including Weather, Google maps, OSM
> Touch and SensorStatus are able to use the phone's 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.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1368647/+subscriptions
>

[František Kučera (linux-frantovo)]

„I let upstart start the location service with gps::Provider as the only provider“ as described in #11 – I have commented lines in /etc/init/ubuntu-location-service.override and restarted the service, so I got:

# ps aux | grep [g]ps
root 7065 0.1 0.5 151508 10048 ? Ssl 17:05 0:00 /usr/bin/ubuntu-location-serviced --bus system --provider gps::Provider

But GPS is still not working.

In the log file, I found an error:

# cat /var/log/ubuntu-location-service/com.ubuntu.location.INFO
Log file created at: 2015/08/02 17:05:53
Running on machine: ubuntu-phablet
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
I0802 17:05:53.963609 7065 ofono_nm_connectivity_manager.cpp:699] [connection_goes_via_wifi]
E0802 17:08:45.950181 7072 android_hardware_abstraction_layer.cpp:157] Error downloading GPS Xtra data: Timeout was reached: Operation timed out after 1428 milliseconds with 53576 out of 59748 bytes received

I also agree that GPS is very important function. I love Ubuntu because it brings real GNU/Linux to my phone, so I can do almost anything (e.g. run SQL database or even GlassFish in my pocket device), but if navigation is not working, I can't use it as a smartphone.

Where can I find more log files or debug it?

[jtd (jtdjtdjtd-business)]

Ubuntu phone 15.04 (r23) [mako]

Issue still persists (Weather "Scan for location" returns >100km away; does not ask me if I wish to "Allow" or "Deny" access; Security & Privacy > "Using GPS only"; Security & Privacy > "Allow access to location" does not include Weather app)

[Nicolas DERIVE (kalon33)]

Same here. With latest radio and ubuntu phone r23, neither GPS navigation app can't find my location using GPS, nor sensorsstatus.

Only weather app can approximate it, probably using other methods. Please fix this long standing bug!

[jeffcooper (jeff-cooper)]

GPS is still a bit "iffy" and now worse
since upgrading to current build number: 23
I can no longer seem to get GPS from Nokia HERE service
Nokia's GPS location service - System Settings > Security & Privacy > Location access > " Using GPS, anonymised Wi-Fi and mobile network info." is no longer accessible.
and it takes a age to get GPS from sattelite

Looking into the logs I see:-

/var/log/upstart/ubuntu-espoo-service.log
HERE binaries not found; disabling
ubuntu-espoo-service stop/pre-start, process 7700
HERE binaries not found; disabling
ubuntu-espoo-service stop/pre-start, process 3932

after trying to start espoo service
sudo service ubuntu-espoo-service start

my last /var/log/upstart/ubuntu-espoo-service.log.1.gz is from June
So I guess that is the last time this was working

I have tried reinstalling the latest Ubuntu Touch image but to no avail.

sudo apt-get install --reinstall ubuntu-location-provider-here
after making the filesystem read/write makes no difference

How would one go about installing the missing HERE binaries?

[kristbaum (kristbaum)]

Not working here too (OTA 7). Had similar issues on Bq4.5 device. Please fix it, a real showstopper.

[Lorn Potter (lorn-potter)]

Since it takes quite a bit of time to get a satellite fix, but it does get one eventually (nexus 4 here), we can probably assume that it is agps that is not working.

In the location log, I can getting errors such as:
E1123 16:30:46.685298 1232 android_hardware_abstraction_layer.cpp:157] Error downloading GPS Xtra data: Timeout was reached: Operation timed out after 1499 milliseconds with 50170 out of 58711 bytes received

Which to me points again to agps.

[Tom Rhodes (tom-rhodes)]

I'm now on 15.04 r37, rc bq.aquaris channel on the nexus 4, I've flashed the radio to the android 4.3 version and GPS still does not work for me at all.

It did work for about a month in September but since then it is broken again, I've tried stable, rc, rc-proposed, devel on the mako, and now the rc on the bq.aquaris channel. I've tried disabling gps, and keeping the loation detection on and then restarting, flashing the radio every proposed solution online so far has no effect for me. This is really frustrating as it's a core feature of the device and many apps and online services utilize or depend on it.

Where are the relevent logs and will it help to post them here?

[Tomasz Szyszkowski (tszyszkowski)]

It looks like nexus 4 is now not supported. Bug not fixed for a year... I want to try ubuntu touch on my nexus but error like in post #16 still exists in stable build. Any feedback from Ubuntu team?

[mindaugasd (mindaugasdi)]

Some people flashed "ubuntu-touch/stable/bq-aquaris.en" channel in addition with latest nexus 4 radio and it works.

Reference: http://askubuntu.com/questions/691468/how-to-use-gps-on-nexus-4

On my it does not work :( Since all nexus 4 should be the same, I wonder why it works on some nexus 4, but not on others. I am hoping there is something I can do to make this work...

[Marek (marecki)]

I have Nexus 4 with latest radio, yesterday I flashed the phone with bq-aquaris.en channel and it was not working. Maybe it would get the location eventually but if no location is acquired after 5 minutes, I consider it not working. I'm very much interested in knowing if anyone from Ubuntu team is working on resolving this issue. Thanks

[slash (slash-tux)]

Gents, for information after reading this topic i've been able to make the gps working.
By a sudo test_gps, after waiting couple of minutes it captured for the first time the position.

After i rebooted the phone and launched Unav, success it captures the position and the movments. I didn't perform heavy test yet.
I didn't applied a specific radio image.

FYI :
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 399
device name: mako
channel: ubuntu-touch/rc-proposed/ubuntu
last update: 2016-03-24 09:37:50
version version: 399
version ubuntu: 20160324
version device: 20160315
version custom: 20160324

I hope it helps

[mindaugasd (mindaugasdi)]

Yay, it works finally!:) (Almost)

I tried all kinds of posibilities many times, and it works only then:
1. Flashing bq-aquaris.en channel
2. Turn on GPS with Nokia HERE setting.
3. Restart.

Tests show, that it works independent of radio version, it can be old or new, does not matter (It always works if 1-2-3 above is done on any channel, and don't work if the opposite).

It matters to have /bq-aquaris.en channel installed, because I could not find Nokia HERE setting on '/ubuntu' channel..

Tested with SensorsStatus app and uNAV app, it works. But "sudo test_gps" command only shows empty values... and two "unkown error" at the start.

If I disable wi-fi and enable flight mode, gps still recognizes location correctly, so this means that GPS itself must be working.

Tried to drive with my finally working GPS today, but signal was very unstable, map choppy, unav was not knowing the direction and all kinds of other problem - mostly loosing signal. I could reacuire signal only by switching apps SensorsStatus -> uNAV, and visa versa, this way signal always reappears but only if I switch those apps, and after a minute, lost again.

I'll test more later (weeks). But glad it works just a bit, some more steps and it might be working well! :) Now the questions are why is does not know direction (compass etc.), why test_gps does not work, why maps are so choppy (not smooth) and what causes signal to always dissapear untill I swith apps.

[mindaugasd (mindaugasdi)]

OK, finished testing all the situations with all the channels and all the radios. Final conclusion - GPS works well.

Made an instruction how to use GPS on Nexus 4: http://askubuntu.com/a/760031/514318

Issues I described previously was caused by this bug:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1468020 (then more GPS apps are running at the same time)

[slash (slash-tux)]

On a daily basis, i'm not able to use the GPS. In order to get nearby information i'm relying on wifi(accurate)+3g(inaccurate), unfortunately i cannot use Unav app for instance.

I tried on my balcony test-GPS with success (catching a position), I decided to try by walking in my neighbourhood. I reboot the phone to use a "fresh" setup, and after 30 min test-GPS didn't catch anything.

the current config :

  system-image-cli -i
current build number: 349
device name: mako
channel: ubuntu-touch/rc-proposed/bq-aquaris.en
last update: 2016-07-02 00:26:02
version version: 349
version ubuntu: 20160702
version device: 20160401.1
version custom: 20160701-5-vivid

phablet@ubuntu-phablet:~$ 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

phablet@ubuntu-phablet:~$ ps ax | grep location
  890 ? 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
 1719 ? 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
 1833 ? Ssl 0:02 /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
 1925 ? Ssl 0:00 /custom/vendor/here/location-provider/bin/arm-linux-gnueabihf/ubuntu-espoo-service --bus system
 2847 ? 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
 3370 ? Ssl 0:00 /usr/lib/arm-linux-gnueabihf/indicator-location/indicator-location-service
25327 pts/44 S+ 0:00 grep --color=auto location

phablet@ubuntu-phablet:~$ sudo dmesg | grep gps | more
phablet@ubuntu-phablet:~$

phablet@ubuntu-phablet:~$ sudo cat /var/log/upstart/ubuntu-location-service.log

E0703 19:04:30.181362 2661 skeleton.cpp:190] Error creating session: Client lacks permissions to access the service with the given criteria
Attempted to unregister path (path[0] = sessions path[1] = 0) which isn't registered
Attempted to unregister path (path[0] = sessions path[1] = 1) which isn't registered
Attempted to unregister path (path[0] = sessions path[1] = 2) which isn't registered
Attempted to unregister path (path[0] = sessions path[1] = 3) which isn't registered
Attempted to unregister path (path[0] = sessions path[1] = 4) which isn't registered
 name -> com.ubuntu.espoo.Service.Provider
 path -> /com/ubuntu/espoo/Service/Provider
Instantiating and configuring: gps::Provider
Instantiating and configuring: remote::Provider
E0703 19:22:54.460836 2678 skeleton.cpp:190] Error creating session: Client lacks per...

[slash (slash-tux)]

And the logcat if it helps, see enclosed

[slash (slash-tux)]

Gents,

After several days of tests, i can confirm the GPS is working fine. It's taking 2-10 min to get the satellites.

- For some asking the radio (even if i'm not sure if it's relevant for the GPS) : M9615A-CEFWMAZM-2.0.1700.84

- I set /var/lib/ubuntu-location-service/config.ini to :
Engine::State=Engine::Status::on
Engine::SatelliteBasedPositioningState=SatelliteBasedPositioningState::on
Engine::WifiAndCellIdReportingState=WifiAndCellIdReportingState::on

Not sure if it's help for the pure GPS localization.

- last step :
Removing the phone from it's wallet type case ... I wasn't expected so much difference. I think this is the main factor contributing to have a poor signal.

The tests were performed through Unav and activity trackers.

As said before, the phone is under RC-proposed BQ-aquaris dual boot with multirom.