AGPS on Open C

[Panos Astithas]

Hi all,

I have an Open C shallow-flashed to latest v2.1 and everything about it seems fine, except for AGPS. When I'm indoors, HERE Maps always fails to find my location and logcat contains a bunch of these:

E/GeckoConsole(  286): [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/LocSvc_eng(  286): I/===> int loc_eng_init(loc_eng_data_s_type&, LocCallbacks*, LOC_API_ADAPTER_EVENT_MASK_T, loc_core::ContextBase*) line 1463
E/LocSvc_api_v02(  286): I/---> locClientOpen line 1941 loc client open
E/Diag_Lib(  286): Setting internal use port to rmnet0
E/LocSvc_eng(  286): I/===> void loc_eng_agps_init(loc_eng_data_s_type&, AGpsExtCallbacks*) line 2004
E/LocSvc_eng(  286): I/===> int loc_eng_set_server_proxy(loc_eng_data_s_type&, LocServerType, const char*, int) line 2294
E/LocSvc_eng(  286): I/===> int loc_eng_set_position_mode(loc_eng_data_s_type&, LocPosMode&) line 1772
E/LocSvc_eng(  286): I/===> int loc_eng_start(loc_eng_data_s_type&) line 1648
E/LocSvc_api_v02(  286): I/---> locClientSendReq line 2144 QMI_LOC_REG_EVENTS_REQ_V02
E/LocSvc_ApiV02(  286): W/[ZTE-GPS] efs file doesn`t exist in ARM9 need to inject
E/LocSvc_ApiV02(  286): W/[ZTE-GPS] Create cert file
E/LocSvc_ApiV02(  286): W/[ZTE-GPS] certfilesize=0
E/LocSvc_ApiV02(  286): W/[ZTE-GPS] No cer file

Here is a pastebin with a more complete log; does anyone know what the problem is?

http://past.pastebin.mozilla.org/6829989

If the problem cannot be fixed by anyone but ZTE, how can I make it use the Mozilla Location Service? I've tried setting the following prefs, but that didn't help:

pref("geo.provider.use_mls", true);
pref("geo.cell.scan", true);
pref("geo.wifi.uri", "https://location.services.mozilla.com/v1/geolocate?key=%MOZILLA_API_KEY%");
pref("geo.enabled", true);

In this case I am getting these errors:

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]

What am I doing wrong?

Thanks,
Panos

[Asa Dotzler]

I believe that this is an issue with how we "shallow flash."

A shallow flash of Gecko/Gaia stomps on the QC RIL and A-GPS code,
replacing it with MozRIL (and no A-GPS alternative.)

There are two potential solutions here. One, we ask QC to move that code
to a different place in OS so it's not part of the RIL stack that gets
replaced. Two, we provide an alternative A-GPS service.

The only workaround today I can think of is to stick with the base image
that includes the QC code, avoiding the move to nightly and sticking
with the 2.0 base image.

- A

> <http://past..pastebin.mozilla.org/6829989>

>
> If the problem cannot be fixed by anyone but ZTE, how can I make it use
> the Mozilla Location Service? I've tried setting the following prefs,
> but that didn't help:
>
> pref("geo.provider.use_mls", true);
> pref("geo.cell.scan", true);
> pref("geo.wifi.uri",
> "https://location.services.mozilla.com/v1/geolocate?key=%MOZILLA_API_KEY%");
> pref("geo.enabled", true);
>
> In this case I am getting these errors:
>
> 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"

[Panos Astithas]

Interesting, I thought the RIL would be part of gonk and therefore unaffected by shallow flash. Isn't there a build/configure time option to select which RIL to use? Shouldn't there be? (I might try to add it if so).

In the phones without QC silicon, don't we use AGPS for MLS? If not, I suppose there must be a way to configure gecko to use MLS, right?

About the workaround to stick with the base image, ZTE comes with 1.3 and there is no 2.0 to the best of my knowledge. Did you perhaps mean that flashing 2.0 won't stomp on QC RIL, whereas flashing 2.1 will? If so, I will certainly try that.

Thanks,
Panos

On Tue, Oct 21, 2014 at 3:31 AM, Asa Dotzler <a...@mozilla.com> wrote:

I believe that this is an issue with how we "shallow flash."

A shallow flash of Gecko/Gaia stomps on the QC RIL and A-GPS code, replacing it with MozRIL (and no A-GPS alternative.)

There are two potential solutions here. One, we ask QC to move that code to a different place in OS so it's not part of the RIL stack that gets replaced. Two, we provide an alternative A-GPS service.

The only workaround today I can think of is to stick with the base image that includes the QC code, avoiding the move to nightly and sticking with the 2.0 base image.

- A


On 10/20/14, 1:14 PM, Panos Astithas wrote:

<http://past..pastebin.mozilla.org/6829989>

If the problem cannot be fixed by anyone but ZTE, how can I make it use
the Mozilla Location Service? I've tried setting the following prefs,
but that didn't help:

pref("geo.provider.use_mls", true);
pref("geo.cell.scan", true);
pref("geo.wifi.uri",
"https://location.services.mozilla.com/v1/geolocate?key=%MOZILLA_API_KEY%");
pref("geo.enabled", true);

In this case I am getting these errors:

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]

What am I doing wrong?

Thanks,
Panos

_______________________________________________
dev-b2g mailing list
dev...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g

[Julien Wajsberg]

The fact is that some shallow flash scripts try to replace the RIL. I think one reason is that QC RIL doesn't always work properly on non-release branches.

Le 21/10/2014 12:55, Panos Astithas a écrit :

Interesting, I thought the RIL would be part of gonk and therefore unaffected by shallow flash. Isn't there a build/configure time option to select which RIL to use? Shouldn't there be? (I might try to add it if so).

In the phones without QC silicon, don't we use AGPS for MLS? If not, I suppose there must be a way to configure gecko to use MLS, right?

About the workaround to stick with the base image, ZTE comes with 1.3 and there is no 2.0 to the best of my knowledge. Did you perhaps mean that flashing 2.0 won't stomp on QC RIL, whereas flashing 2.1 will? If so, I will certainly try that.

Thanks,
Panos

On Tue, Oct 21, 2014 at 3:31 AM, Asa Dotzler <a...@mozilla.com> wrote:

I believe that this is an issue with how we "shallow flash."

A shallow flash of Gecko/Gaia stomps on the QC RIL and A-GPS code, replacing it with MozRIL (and no A-GPS alternative.)

There are two potential solutions here. One, we ask QC to move that code to a different place in OS so it's not part of the RIL stack that gets replaced. Two, we provide an alternative A-GPS service.

The only workaround today I can think of is to stick with the base image that includes the QC code, avoiding the move to nightly and sticking with the 2.0 base image.

- A


On 10/20/14, 1:14 PM, Panos Astithas wrote:

<http://past..pastebin.mozilla.org/6829989>

If the problem cannot be fixed by anyone but ZTE, how can I make it use
the Mozilla Location Service? I've tried setting the following prefs,
but that didn't help:

pref("geo.provider.use_mls", true);
pref("geo.cell.scan", true);
pref("geo.wifi.uri",
"https://location.services.mozilla.com/v1/geolocate?key=%MOZILLA_API_KEY%");
pref("geo.enabled", true);

In this case I am getting these errors:

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]

What am I doing wrong?

Thanks,
Panos

_______________________________________________
dev-b2g mailing list
dev...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g