> Fixing GPS obviously needs to be one of the highest priorities, I know its > hard problem due to the interaction with the vendor however we cant be > handwavey 'its a build issue' any more, if someone on the v188 with the > latest gecko is not getting a fast GPS fix we need to know why,
For Flame, or any QC-chipset device, if you build gecko yourself you have replaced the QC geo layer, and their AGPS code. With no AGPS, the chip will take 12-15 mins minimum to download required satellite positional information from a satellite (the almanac+ephemeris) and get a first fix. If you are using the QC-build of gecko, then you should have GPS performance equivalent to any quality Android device. > I walked around my area with mozstumbler specifically in the hope that it was > a lack of agps coverage that was causing the slow fix, AGPS and network geolocation (mozstumbler) are separate beasts. AGPS changes time to first fix on a GPS from 12 mins to <30 seconds. Network geolocation uses cell and wifi signals to provide course geolocation within seconds. _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
