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 this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in 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 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
