[devel-rc-proposed] GPS not working

Bug #1686590 reported by slash
26
This bug affects 6 people
Affects Status Importance Assigned to Milestone
UBports Nexus 5
Invalid
High
Unassigned

Bug Description

Gents,
With the image 2017041968380 the GPS is not working :

root@ubuntu-phablet:~# test_gps
*** setup signal handler
*** get gps interface
*** device info
 id = gps
 name = loc_api GPS Module
 author = Qualcomm USA, Inc.
*** init gps interface
 ** Creating thread: 'Loc_hal_worker' (start=0xb6ba77c5, arg=0x1ceba70)
 ** After thread_create: 'Loc_hal_worker', error=0 (start=0xb6ba77c5, arg=0x1ceba70)
 **** Thread wrapper start (start=0xb6ba77c5, arg=0x1ceba70) ****
 Diag_LSM_Init: Failed to open handle to diag driver, error = 2*** setting positioning mode
*** start gps track
*** gps tracking started
*** tracking....
*** status callback
*** session begin
*** set capabilities
capability is 00000007
*** status callback
*** engine on
*** status callback
*** session begin

Revision history for this message
slash (slash-tux) wrote :

Some other input :
# tail -f /userdata/system-data/var/log/upstart/ubuntu-location-service.log
 Diag_LSM_Init: Failed to open handle to diag driver, error = 2 Diag_LSM_Init: Failed to open handle to diag driver, error = 2Instantiating and configuring: remote::Provider
Attempted to unregister path (path[0] = com path[1] = ubuntu) which isn't registered
Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered
Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered
Attempted to unregister path (path[0] = core path[1] = trust) which isn't registered
 name -> com.ubuntu.espoo.Service.Provider
 path -> /com/ubuntu/espoo/Service/Provider
Instantiating and configuring: gps::Provider
 Diag_LSM_Init: Failed to open handle to diag driver, error = 2Instantiating and configuring: remote::Provider
Attempted to unregister path (path[0] = com path[1] = ubuntu) which isn't registered

Regarding the error msg : Diag_LSM_Init: Failed to open handle to diag driver, error = 2

I've found a similar error msg for Firefox OS and Nexus 5
https://bugzilla.mozilla.org/show_bug.cgi?id=1107742
They fixed it by the commit in the bug https://bugzilla.mozilla.org/show_bug.cgi?id=1112175

It's seems a permission issue defined in BoardConfig.mk
https://github.com/mozilla-b2g/device-hammerhead/commit/98e8bed41f06d62373146054c5e7b328d93d6582

-BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 androidboot.selinux=disabled
+BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1 androidboot.selinux=permissive

It's so far out of my capabilities to assess if this is applicable or not.

Rgds

Revision history for this message
slash (slash-tux) wrote :

And the last log i can pull is :

less /var/log/syslog |grep gps
ubuntu-phablet kernel: [ 1024.272978] msm_ipc_router_send_to: permission failure for test_gps

This msg makes me think the proposed solution could help.

Revision history for this message
slash (slash-tux) wrote :

Interesting point;

I cannot diagnostic the gps as mentioned above, but today the GPS worked !
So i've tried with success Unav and acrivity tracker.

So if possible we can change the bug title as "impossible to diagnose Gps".

Revision history for this message
Jean-Paul Lescouzères (soykje) wrote :

Hi,

Still no GPS working for me, even after recent update... Not an expert but if someone can tell me how to log from my phone, I'll be happy to participate.

Revision history for this message
slash (slash-tux) wrote :

Jean-Paul,

Simple verification
Did you try to launch Unav for instance outside, not under a roof, without a protection for your phone and wait up to 10 min ?

Otherwise you can generate, via adb_shell :
less /var/log/syslog |grep gps
tail -f /userdata/system-data/var/log/upstart/ubuntu-location-service.log
test_gps

But in my case the output is negatif while the GPS works.

Changed in ubports-n5:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Johannah Sprinz (neothethird) wrote :
Changed in ubports-n5:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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