GPS not working on my BQ Ubuntu Touch

Please tell me if I need to sent you some info about this.

Thanks for your bug report and the screenshots. If you feel comfortable doing so, it would be great if you could attach the information as listed in https://wiki.ubuntu.com/Process/Merges/TestPlan/location-service#Forensics.

One other question: Has your system ever been connected to a wifi?

I want to help more but I dont know exactly how. For example this command "/var/log/ubuntu-location-service* " I should type this in Terminal? Or to conect the phone to a Ubuntu Computer and to try this?...

I'm sorry I can acces that folder on my Ubuntu Phone but I cant send you the info from them, If there should be an app that reports to you that info would be very easy for me... Sorry.

I succeded with ubuntu-location-service folder

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

I0410 22:50:52.075815 5219 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428624015000 nmea=$GPACCURACY,3162.1*3F
N,0.000,K,N*32
000,E,0.000,0.00,060180,,,N*4A
 length=23 context=0x1fcea80
I0410 22:50:53.069854 5219 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428624016000 nmea=$GPGGA,000016.000,8960.0000,N,00000.0000,E,0,0,,137.0,M,13.0,M,,*44

 length=69 context=0x1fcea80
I0410 22:50:53.072623 5219 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428624016000 nmea=$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
0,,137.0,M,13.0,M,,*44

 length=45 context=0x1fcea80
I0410 22:50:53.074841 5219 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428624016000 nmea=$GPRMC,000016.000,V,8960.0000,N,00000.0000,E,0.000,0.00,060180,,,N*49
 length=71 context=0x1fcea80
I0410 22:50:53.075567 5219 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428624016000 nmea=$GPVTG,0.00,T,,M,0.000,N,0.000,K,N*32
000,E,0.000,0.00,060180,,,N*49
 length=39 context=0x1fcea80
I0410 22:50:53.076815 5219 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428624016000 nmea=$GPACCURACY,3162.1*3F
N,0.000,K,N*32
000,E,0.000,0.00,060180,,,N*49
 length=23 context=0x1fcea80
I0410 22:50:54.069739 5219 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428624017000 nmea=$GPGGA,000017.000,8960.0000,N,00000.0000,E,0,0,,137.0,M,13.0,M,,*45

 length=69 context=0x1fcea80
I0410 22:50:54.071151 5219 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428624017000 nmea=$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
0,,137.0,M,13.0,M,,*45

 length=45 context=0x1fcea80
I0410 22:50:54.072736 5219 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428624017000 nmea=$GPRMC,000017.000,V,8960.0000,N,00000.0000,E,0.000,0.00,060180,,,N*48
 length=71 context=0x1fcea80
I0410 22:50:54.073477 5219 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::loc...

bogdan@bogdan-Lenovo-B580:~$ adb shell
phablet@ubuntu-phablet:~$ ubuntu-location-serviced-cli --bus system --get --property visible_space_vehicles
Problem executing the CLI: org.freedesktop.DBus.Error.ServiceUnknown: The name com.ubuntu.location.Service was not provided by any .service files

/var/log/ubuntu-location-service* and the result

NOw I tried to open GPS and location and then try this commands:

bogdan@bogdan-Lenovo-B580:~$ adb shell
phablet@ubuntu-phablet:~$ ubuntu-location-serviced-cli --bus system --get --property visible_space_vehicles
Visible space vehicles:
phablet@ubuntu-phablet:~$

So I have no vehicles. I have to mention that now with this commands I am inside, I dont have satelites visible...

sudo GLOG_v=1000 GLOG_logtostderr=1 ubuntu-location-serviced-cli --bus system --test
[sudo] password for phablet:
ubuntu-location-service stop/waiting
I0413 21:23:14.640486 10467 android_hardware_abstraction_layer.cpp:481] virtual bool com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::start_positioning(): 0xb51a80, 0xb564e0
I0413 21:23:16.423672 10467 android_hardware_abstraction_layer.cpp:231] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_status_update(uint16_t, void*): status=3, context=0xb51a80
I0413 21:23:16.423903 10467 android_hardware_abstraction_layer.cpp:231] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_status_update(uint16_t, void*): status=1, context=0xb51a80
I0413 21:23:16.424698 10485 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428969583000 nmea=$GPGGA,235943.999,8960.0000,N,00000.0000,E,0,0,,137.0,M,13.0,M,,*40
 length=69 context=0xb51a80
I0413 21:23:16.425644 10485 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428969583000 nmea=$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
0,,137.0,M,13.0,M,,*40
 length=45 context=0xb51a80
I0413 21:23:16.426131 10485 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428969583000 nmea=$GPRMC,235943.999,V,8960.0000,N,00000.0000,E,0.000,0.00,050180,,,N*4E
 length=71 context=0xb51a80
I0413 21:23:16.426651 10485 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428969583000 nmea=$GPVTG,0.00,T,,M,0.000,N,0.000,K,N*32
000,E,0.000,0.00,050180,,,N*4E
 length=39 context=0xb51a80
I0413 21:23:16.427069 10485 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428969583000 nmea=$GPACCURACY,3162.1*3F
N,0.000,K,N*32
000,E,0.000,0.00,050180,,,N*4E
 length=23 context=0xb51a80
I0413 21:23:17.418609 10485 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428969584000 nmea=$GPGGA,235944.999,8960.0000,N,00000.0000,E,0,0,,137.0,M,13.0,M,,*47

 length=69 context=0xb51a80
I0413 21:23:17.418826 10485 android_hardware_abstraction_layer.cpp:136] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1428969584000 nmea=$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
0,,137.0,M,13.0,M,,*47

 length=45 context=0xb51a80
I0413 21:23:17.419415 10485 android_hardware_abstraction_layer.cpp:136] sta...

And I succeded with /var/log/syslog

See the attachement

Thanks for providing the logs. According to those, gps positioning is in progress, and please note that it can take a significant amount of time until it acquires a fix, specifically indoors.

We rely on network-based positioning to provide an initial first fix as fast as possible. That technology requires a data connection and a SIM to be present in the phone. Do you have a data connection on the phone (simple test: can you browse the web)? Do you have a SIM inserted into the phone?

When getting logs i was indoor and i have sim inserted and 3G on.

But another day i was outdoor for 30 minutes, gps on, here terms accepted,
but here maps and google maps dont detect any gps signal.

I have an app SensorsStatus and today i was outdoor, gps on, but i dont get
any info about gps position.

În data de miercuri, 15 aprilie 2015, Thomas Voß <email address hidden>
a scris:
> Thanks for providing the logs. According to those, gps positioning is in
> progress, and please note that it can take a significant amount of time
> until it acquires a fix, specifically indoors.
>
> We rely on network-based positioning to provide an initial first fix as
> fast as possible. That technology requires a data connection and a SIM
> to be present in the phone. Do you have a data connection on the phone
> (simple test: can you browse the web)? Do you have a SIM inserted into
> the phone?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1442105
>
> Title:
> GPS not working on my BQ Ubuntu Touch
>
> Status in indicator-location package in Ubuntu:
> New
>
> Bug description:
> Hi. I tried to use GPS (HERE maps, Google Maps) on my Ubuntu Touch
> from BQ (I am on update 20), but the app dont detect my location. I
> have to mention that I check Here terms & Condition and GPS and
> location are checked.
>
> I attached some screenshot from what I did.
>
> To manage notifications about this bug go to:
>
https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1442105/+subscriptions
>

--
Trimis de pe Ubuntu Touch

is there a command for Terminal to try to force GPS to be on?...

I dont activate wifi when searching for GPS because ussualy when I need GPS I am not having any wifi, I'm on streets and searching for a location, so no wifi...

The same thing is happening to me with those two software.
Differently, with OpenStreetMap, I get this information: JavaScript Notice, Geolocation error: permission denied.

I affected too. I'm using the last release (r21) on the bq device. GPS on, HERE terms accepted, SIM inserted, mobile data enabled (it works for browsing) and last day I tried outside for about 40 minutes without luck. Any idea?

I'm affected too. I'm on r21.
Before the upgrade to r21 my location was detected at least occasionally.
Since the upgrade I was not able to get a fix at all.
I have here enabled, 2 SIMs in the phone and data enabled.
Most of the time I have mobile data enabled and WIFI disabled.
I enable WIFI only rarely for upgrades or such. (because of re/connection issues described elsewhere).

In general I dare asking what's the idea behind a GPS receiver that needs a data connection to get a fix?
For me aquiring an exact GPS position is most of interest when I'm in the 'wilderness' where you can be glad to get a phone signal at all. I see very limited use for a tool that tells me 'you're downtown vienna now' because there I can read the streetsigns and find my position quite well by other means.
I personally get well along without knowing my exact position.
But all the Scopes that deliver localized services are worthless without it.

Please don't get me wrong. I really don't want to criticize destructively.
I bought the device knowing, that not it won't be a cakewalk.
And I bought it to support the good work done and to help where I can.

@Robin, Lukas, can you get the info from https://wiki.ubuntu.com/Process/Merges/TestPlan/location-service#Forensics and add those to the bug?

@Lukas, the data connection is not needed to get a fix, but getting a position from the gps alone can take a while

@Sebastien: thank you for that link.
I have allready tried that ubuntu-location-serviced-cli commands before.
And I think that was exactly the cause for losing the ability to provide geolocations to the apps.
Now I remember that you have to reboot the phone after issuing those commands to give access to geodata back to the apps.
Obviously I haven't rebooted the device for some days now. (that's a good sign, isn't it?)
Now I get some data at least. Currently I'm indoors so it's only calculated from the cell info.
So I'll keep an eye on the GPS during the next days and report back here.

btw: the logfiles in /var/log/ubuntu-location-service are dated from january and february. that is long before I got my device. should I worry about that, or is it rather a good sign. indicating that currently everything is ok?

I have a similar issue ( BQ E4.5 ), on my phone the location service works only when I'm in a wi-fi network.

This is a shame because I love the NearBy scope, but it's useless without the location service. :'(

Today I tried it again. I sat out to the balcon, so I didn't move. And it worked. :) With enabled GPS and mobile data, it took 15 minutes to got a signal. So it works, but 15 minutes is too much time. In my Android phone it took about 2 minutes.

GPS works on my bq 4.5 , but need to long to take position (more than 10 minutes).

@Lukas Mutschmann-Sanchez: Ihave the same problems with "re/connection issues" Did writ a short bug - report:

https://bugs.launchpad.net/ubuntu/+bug/1448750

I have now the 22 update on BQ Ubuntu Touch stable and I have the same problem. Is there any progress with GPS location on 3G? On wifi is working. It's just a metter of 3G and Wifi. Anyone knows anything new about this bug?

Please note that the gps automatically switches off once the screen turns off and the device enters power saving mode. If you want to keep the device and with that the gps alive, please run: sudo powerd-cli display on on the device. With that, the chipset should have enough time to acquire a fix even if neither wifi nor mobile data is available.

On vineri, 15 mai 2015 21:21:53 EEST, Thomas Voß wrote:
> Please note that the gps automatically switches off once the screen
> turns off and the device enters power saving mode. If you want to keep
> the device and with that the gps alive, please run: sudo powerd-cli
> display on on the device. With that, the chipset should have enough time
> to acquire a fix even if neither wifi nor mobile data is available.
>

I tried like this:
- on 3g i activated locations and started here and google maps, but no
localisation
- than i typed in terminal sudo powerd-cli display on
- this made no diference, nothing happend

- than i started the wifi, and in the next second i knew my exact location
on both maps (but i am on wifi at home, so i dont need my location here)

So, the problem again is about 3g... My opinion.

--
Sent from my Ubuntu touch device

If you are getting position with WiFi, that sounds like you are getting the WiFi based location from the HERE service. This position can be fairly accurate, but is not GPS, it will also work without connecting to a WiFi point, just as long as WiFi is enabled and it can see a list of surrounding access points.

GPS is working for me again after the last update (on Nexus 4 though). Bear in mind that it will likely take around 12-20 mins to get a fix (the first time), and by the sounds of it the phone must not sleep in that time.

is that still an issue on r22? the update changes list some gps issues as resolved (http://people.canonical.com/~lzemczak/landing-team/ota/ota-3.5.changelog)

How I made my Ubuntu BQ GPS to work (with advices from BQ Support)

First I have gone outside and check this on the phone: System Settings> Security and Privacy> Location access> Using GPS, anonymized Wi-Fi and cellular network info. And after that I reboot.

I checked again that all location setting to be enabled and in 2 minutes the GPS worked for the first time I bought the phone.

I supose there will be more updates on software that we will not need to reboot to make something to work properly.

Another tool that can help you with checking hardware problem on GPS is "Sensor status" from Ubuntu store. Repeat the above steps and check the GPS status on that app.

This steps helped me and in my opinion this bug is closed using those sugestion I described.

Same here. I had the "Using GPS only" since I bought the phone and GPS never worked. Days/weeks of uptime should be enough to get a GPS lock, right?

Now I enabled the GPS/Wifi/mobile-network ("HERE"), rebooted, and like you said, within 30 seconds, the SensorsStatus tool started reporting GPS info. Yay.

Running latest 15.04 r24 atm (updated 7 july).

This does look like a bug which should be fixed; you shouldn't have to enable privacy-sensitive modes to get the GPS to work.
I'll go back and try what happens when I disable the "HERE" location detection again.

Still a completely unusable GPS ubuntu system on the BQ Aquaris 4.5 here 15.04 (OTA-8) updated 23-11-2015 bought in the second flash sale. A GPS only fix can hardly be found. WLAN and/or celldata does help a bit to 'guess' the location. But it's never accurate or fast enough to be usable. I thought maybe my phone was broken so i tried flashing the phone with android firmware from BQ and a GPS-fix was found whithin 3 minutes. Of course i flashed it back to ubuntu, but the this bug is present since the beginning and i'm still hoping this annoying issue will be fixed with a high priority.

2015-11-23 21:15 GMT+02:00 ockels <email address hidden>:

> Still a completely unusable GPS ubuntu system on the BQ Aquaris 4.5
> here 15.04 (OTA-8) updated 23-11-2015 bought in the second flash sale.
> A GPS only fix can hardly be found. WLAN and/or celldata does help a bit
> to 'guess' the location. But it's never accurate or fast enough to be
> usable. I thought maybe my phone was broken so i tried flashing the
> phone with android firmware from BQ and a GPS-fix was found whithin 3
> minutes. Of course i flashed it back to ubuntu, but the this bug is
> present since the beginning and i'm still hoping this annoying issue
> will be fixed with a high priority.
>

I have the same Ubuntu BQ 4.5 and after OTA-8 update I drive with a friend
car and the GPS worked very nice. And it didint needed restart in order to
work. OTA-8 is the best update until now.

--
Buzea Bogdan

>>2015-11-23 21:15 GMT+02:00 ockels <email address hidden>:
>>
>> Still a completely unusable GPS ubuntu system on the BQ Aquaris 4.5
>> here 15.04 (OTA-8) updated 23-11-2015 bought in the second flash sale.
>> A GPS only fix can hardly be found. WLAN and/or celldata does help a bit
>> to 'guess' the location. But it's never accurate or fast enough to be
>> usable. I thought maybe my phone was broken so i tried flashing the
>> phone with android firmware from BQ and a GPS-fix was found whithin 3
>> minutes. Of course i flashed it back to ubuntu, but the this bug is
>> present since the beginning and i'm still hoping this annoying issue
>> will be fixed with a high priority.
>>
>
>I have the same Ubuntu BQ 4.5 and after OTA-8 update I drive with a friend
>car and the GPS worked very nice. And it didint needed restart in order to
>work. OTA-8 is the best update until now.
>
>--
>Buzea Bogdan

Have you tried GPS only?

As i said, the GPS signal only works like a charm on Android on the same hardware, so it isn't a hw-issue.
After i tested the android image i flashed the phone back to the latest firmware downloaded from the BQ site and the GPS is still unusable for me.

Cellular and WLAN info can speed things up a but, but GPS only should work also.

The same with OTA-8.
No GPS, bq change my phone and it s the same

To ockels:
I have checked GPS and Geografical detection, not only GPS. But before OTA-8, if I checked this 2 options nothing happend. But now I could get GPS navigation indication on trafic using Unav app. And this without restarting the phone after the checking of the 2 options. And this is great!

@oeckels: When you say you flashed your phone with Android and got a GPS fix within 3 minutes, how did you make sure that the GPS chipset is not using any sort of assistance information? Even if you disable network-based positioning,t he GPS chipset will rely on a so-called SUPL server to download ephimeris data. For that, I'm curious what steps you did take on Android.

At any rate, to further debug your issue, it would be very helpful if you could include the logs and debug info listed in:

  https://wiki.ubuntu.com/Process/Merges/TestPlan/location-service#Forensics

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

I have found that turning on Geografical detection in the notification area, has no impact on gps switch in the battery's parameter.
The gps switch in the battery's parameter default value is off.

Both Geografical detection and gps switch in the battery's parameter should be on, to get gps works

Same behaviour here with bq Aquaris m10 (tablet). With wifi and GPS on doesn't find position (Here, OSMScout, uNav).
Since the tablet has no 3g it makes impossible to use offline driving directions.

Tried app Location Test with no results. I thought GPS might be broken so I did a system check (rebooting into tablet's checking system mode) and GPS seams to work fine but not in Ubuntu.

Forensics:
    /var/log/ubuntu-location-service*
Not present

    /var/log/upstart/ubuntu-location-service.log

    /var/log/syslog

    The output of: sudo /system/bin/logcat

    The output of: ubuntu-location-serviced-cli --bus system --get --property visible_space_vehicles
phablet@ubuntu-phablet:~$ ubuntu-location-serviced-cli --bus system --get --property visible_space_vehicles > ululsc-vsv.txt
Attempted to unregister path (path[0] = com path[1] = ubuntu) which isn't registered
    The output of sudo GLOG_v=1000 GLOG_logtostderr=1 ubuntu-location-serviced-cli --bus system --test
?field.comment=
Same behaviour here with bq Aquaris m10 (tablet). With wifi and GPS on doesn't find position (Here, OSMScout, uNav).
Since the tablet has no 3g it makes impossible to use offline driving directions.

Tried app Location Test with no results. I thought GPS might be broken so I did a system check (rebooting into tablet's checking system mode) and GPS seams to work fine but not in Ubuntu.

Forensics:
    /var/log/ubuntu-location-service*
Not present

    /var/log/upstart/ubuntu-location-service.log
Attempted to unregister path (path[0] = sessions path[1] = 2) 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] = 0) 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
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
Instantiating and configuring: remote::Provider
Attempted to unregister path (path[0] = sessions path[1] = 1) which isn't registered

    /var/log/syslog
Attached

    The output of: sudo /system/bin/logcat
Attached

    The output of: ubuntu-location-serviced-cli --bus system --get --property visible_space_vehicles
phablet@ubuntu-phablet:~$ ubuntu-location-serviced-cli --bus system --get --property visible_space_vehicles > ululsc-vsv.txt
Attempted to unregister path (path[0] = com path[1] = ubuntu) which isn't registered

    The output of sudo GLOG_v=1000 GLOG_logtostderr=1 ubuntu-location-serviced-cli --bus system --test
 length=17 context=0x6c5a28
I0610 04:19:13.580946 6236 android_hardware_abstraction_layer.cpp:135] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1465524006000 nmea=$GPRMC,000006.010,V,8960.0000,N,00000.0000,E,0.000,0.00,060180,,,N*49
 length=71 context=0x6c5a28
I0610 04:19:13.581164 6236 android_hardware_abstraction_layer.cpp:135] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1465524006000 nmea=$GPVTG,0.00,T,,M,0.000,N,0.000,K,N*32
000,E,0.000,0.00,060180,,,N*49
 length=39 context=0x6c5a28
I0610 04:19:13.581517 6236 android_hardware_abstraction_layer.cpp:135] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1465524006000 nmea=$GPACCURACY,3162.1*3F
N,0.000,K,N*32
000,E,0.000,0.00,060180,,,N*49
 length=23 context=0x6c5a28
I0610 04:19:14.571502 6236 android_hardware_abstraction_layer.cpp:135] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1465524007000 nmea=$GPGGA,000007.010,8960.0000,N,00000.0000,E,0,0,,137.0,M,13.0,M,,*45

 length=69 context=0x6c5a28
I0610 04:19:14.572310 6236 android_hardware_abstraction_layer.cpp:135] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1465524007000 nmea=$GPGSA,A,1,,,,,,,,,,,,,99.99,99.99,99.99*30
0,,137.0,M,13.0,M,,*45

 length=45 context=0x6c5a28
I0610 04:19:14.572486 6236 android_hardware_abstraction_layer.cpp:135] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1465524007000 nmea=$GPGSV,1,1,0*49
,,,,,,99.99,99.99,99.99*30
0,,137.0,M,13.0,M,,*45

 length=17 context=0x6c5a28
I0610 04:19:14.573317 6236 android_hardware_abstraction_layer.cpp:135] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1465524007000 nmea=$GPRMC,000007.010,V,8960.0000,N,00000.0000,E,0.000,0.00,060180,,,N*48
 length=71 context=0x6c5a28
I0610 04:19:14.573420 6236 android_hardware_abstraction_layer.cpp:135] static void com::ubuntu::location::providers::gps::android::HardwareAbstractionLayer::on_nmea_update(int64_t, const char*, int, void*): timestamp=1465524007000 nmea=$GPVTG,0.00,T,,M,0.000,N,0.000,K,N*32
000,E,0.000,0.00,060180,,,N*48
 length=39 context=0x6c5a28
I0610 04:19:14.573544 6236 androi...

I got it again working by "disabling roaming" in the data connection. http://askubuntu.com/questions/603101/gps-unvailable-on-aquaris-e45?noredirect=1&lq=1

how this can stll have the incomplete status? the gps is broken, it does not work on bq m10. the test_gps in /usr/bin results in segfaults. this is key feature of mobile (together with sensorsors) to do the cool stuff (not cool is like reading mail, tweeting, facebook, and other stuff calculating 1+1, at the moment ubuntu touch is capable only that), else I dont see what I need for the mobile linux.
I see gps outputs the nmea output. why not use the gpsd as middle layer. it also would make possible to use bluetooth gps more advanced/precise receivers.

/usr/bin/test_gps is known to segfault and we should totally remove it.

For "Why not gpsd?": It does not support assisted GPS in the way we need it, nor does it provide any sort of fusioning of network- and satellite-based positioning ootb. More to this, the NMEA that is reported back here does not report a position either, all the respective entries are marked invalid.

Let's focus on the issue at hand.

The bug is marked as incomplete as:

(1.) we fail to reproduce it reliably
(2.) spot something meaningful in the logs that tells us what is going wrong

With that, it would be very helpful if you could provide us with the information described in the forensics doc: https://wiki.ubuntu.com/Process/Merges/TestPlan/location-service#Forensics

If you are fine with switching your image to rw, the output of:

  > sudo apt install ubuntu-location-service-examples
  > sudo GLOG_v=1000 GLOG_logtostderr=1 /usr/lib/*/ubuntu-location-service/examples/client --bus system

would be very helpful.

Hello,

i have similar problems with my meizu pro5 since OTA 11 and no other OTA solves the problem. Unav starts, but nothing appears, no active button. The GPS is on, the data roaming is allowed and it worked perfectly with OTA 10. Google map doesn't find my position too, the same for the weather app. Only the clock app seems to be able to locate me.

I will do the forensics, but i need to understand what is asked (some files are not present, some other are not exactly what asked)

I also have the GPS not working problem. My phone is bq Aquaris E5, I have OTA 13 installed. I don't even have the "Using GPS, anonymized Wi-Fi and cellular network info" option present in my settings menu.