touch-packages team mailing list archive

[Ondrej Kubik <ondrej.kubik@xxxxxxxxxxxxx>]

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 name.
Empty file is consequence of corrupted nvram file.
I have seen this one already during gps bring up, which was done on PVT phone, so nvram there was formatted several time, but now have this on production hw, so we need to investigate this further.
This bug should be moved to barajas project, since location service is just place where it pops out.

Two issues should be addressed:
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 done, with priority on gps stack always returning from start. Thomas any opinion here?

2) this is real problem and solution, we need to identify what is
corrupting nvram data during OTA

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1387708

Title:
  [TOPBLOCKER] Location services not getting location

Status in Location Service:
  New
Status in “location-service” package in Ubuntu:
  Confirmed
Status in “location-service” package in Ubuntu RTM:
  Confirmed
Status in “location-service” source package in 14.09:
  Confirmed

Bug description:
  Failing to get location fix from application.
  Neither network based nor gps location works.
  Bug has now been seen on 3 phones with and without SIM installed.
  HERE service seems to be running, but no reasonable location is reported.
  GPS is failing to get fix, tested with phone placed for 2 hours outside.

  On two of those phones location was working fine, but with OTA update to ~135 stopped working.
  hard to guess working image but somewhere around 129~131

  
  Problem is now reproducible on RTM release 137

To manage notifications about this bug go to:
https://bugs.launchpad.net/location-service/+bug/1387708/+subscriptions