>
> E/GeckoConsole( 283): [JavaScript Error: "NS_ERROR_XPC_CANT_CREATE_WN:
> Component returned failure code: 0x80570019 (NS_ERROR_XPC_CANT_CREATE_WN)
> [nsIJSCID.getService]" {file:
> "jar:file:///system/b2g/omni.ja!/components/NetworkGeolocationProvider.js"
> line: 332}]
> E/GeckoConsole( 283): [JavaScript Error: "NS_ERROR_XPC_CANT_CREATE_WN:
> Component returned failure code: 0x80570019 (NS_ERROR_XPC_CANT_CREATE_WN)
> [nsIJSCID.getService]" {file:
> "jar:file:///system/b2g/omni.ja!/components/NetworkGeolocationProvider.js"
> line: 307}]
> I/Gecko ( 283): settings 'handle' callback threw an exception,
> dropping: [Exception... "Component returned failure code: 0x80570019
> (NS_ERROR_XPC_CANT_CREATE_WN) [nsIJSCID.getService]" nsresult: "0x80570019
> (NS_ERROR_XPC_CANT_CREATE_WN)" location: "JS frame ::
> jar:file:///system/b2g/omni.ja!/components/NetworkGeolocationProvider.js ::
> WifiGeoPositionProvider.prototype.startup/settingsCallback.handle :: line
> 307" data: no]
>
I recently switched from a flame over to my open C and was running into the
same thing. It appears these errors are due to trying to use the
wifi-monitor. I don't know why the wifi monitor is failing to be created,
but you can still use MLS with just cell scanning. Just turn wifi scanning
off:
pref("geo.wifi.scan", false);
With the following prefs I get cell-based MLS results and then the hardware
gps kicks in eventually:
// base url for the wifi geolocation network provider
pref("geo.provider.use_mls", false);
pref("geo.cell.scan", true);
pref("geo.wifi.scan", false);
pref("geo.wifi.uri", "
https://location.services.mozilla.com/v1/geolocate?key=%MOZILLA_API_KEY%";);
// enable geo
pref("geo.enabled", true);
Note, you want geo.provider.use_mls to false, because setting that to true
completely overrides using the gps chip. A false setting here means use
gps and MLS.
Hope that helps!
Ben
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
