is this still a top blocker?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387708
Title:
[TOPBLOCKER] Location services not getting location
To manage notifications about this bug go to:
No, the fix has been released to both Vivid and RTM. Manually marked as
Fix Released
** Changed in: location-service (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: location-service
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387708
Title:
[TOPBLOCKER] Location services not getting location
To manage
** Changed in: location-service (Ubuntu-rtm 14.09)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387708
Title:
[TOPBLOCKER] Location services not getting
** Changed in: location-service (Ubuntu)
Assignee: (unassigned) = Thomas Voß (thomas-voss)
** Changed in: location-service (Ubuntu)
Status: Confirmed = In Progress
** Changed in: location-service (Ubuntu-rtm 14.09)
Status: Confirmed = In Progress
** Branch linked:
Please note that we only managed to reproduce this issue on phones that
have been exposed to multiple OTA updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387708
Title:
[TOPBLOCKER] Location
** Attachment added: attaching various log files as requested
https://bugs.launchpad.net/location-service/+bug/1387708/+attachment/4253842/+files/location-logs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Some breakthrough:
Problem is caused by corrupted nvram data, when gps stack fails to identify
underlying hw and therefore does not know how to function.
Underlying hw info is stored in /userdata/android-data/misc/GPS_CHIP.cfg, which
is empty on broken phones, it should have text with chipset
1) when gps interface is started, start function never returns. Even
if gps stack fails to initialise, it should at least return. Or in other
case location service needs to initialise providers asynchronously to
prevent one misbehaving provider taking whole service down. Ideally
both should be
If I'm seeing this, does that mean I am experiencing the issue on my
phone?
phablet@ubuntu-phablet:~$ sudo cat /userdata/android-data/misc/GPS_CHIP.cfg
[sudo] password for phablet:
0x6582%s
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
0x6582%s from /userdata/android-data/misc/GPS_CHIP.cfg is correct value.
6582 represents mtk platform m6582.
When nvram gets corrupted GPS_CHIP.cfg is empty, as gps stack was not able to
determine underlying platform.
So this seems to be different issue what you are seeing Rick.
--
You received
Corrupted nvram file issue is now tracked by new bug in specific to
krillin: Bug #1389865
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387708
Title:
[TOPBLOCKER] Location services not getting
To test whether the low-level HERE stack gets a location, put
http://people.canonical.com/~lool/espoo-cli on your phone (will be included
along HERE bits in the future) and run with:
chmod a+x espoo-cli
GLOG_logtostderr=1 GLOG_v=100
13 matches
Mail list logo
