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 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: https://bugs.launchpad.net/location-service/+bug/1387708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
