questions for AGPS

RE: questions for AGPS

Siyou — Wed, 03 Jun 2020 01:37:30 GMT

[quote userid="81181" url="~/f/nordic-q-a/60294/questions-for-agps/251847"][/quote]

I am not sure how you would do that?

To my knowledge, the SUPL library gets the MCC/MNC directly from the modem, so you would have to do something on the network side to fool the modem.

Get it to work with google SUPL server by using dummy MCC/MNC in nrf\lib\supl\os\lte_params.c

No further issue now, please close this case.

RE: questions for AGPS

Siyou — Mon, 01 Jun 2020 02:40:57 GMT

[quote userid="81181" url="~/f/nordic-q-a/60294/questions-for-agps/251847"][/quote]

Siyou said:

Does the modem fw mfw_nrf9160_1.2.0 support AGPS with SUPL session?

Yes. Mfw 1.2.0 should work just fine with NCS v1.2.0, including the SUPL library.

To me, it looks like the problem is on the application side, but if you take a modem trace, I can check that the modem behaves as normal.

Resolved by upgrading the NCS SDK to latest(refer to this case)

RE: questions for AGPS

Didrik Rokhaug — Wed, 27 May 2020 08:21:54 GMT

[quote user="Siyou"]We will try to test the google SUPL with simulated MCC/MNC, do you think it practicable?[/quote]

I am not sure how you would do that?

To my knowledge, the SUPL library gets the MCC/MNC directly from the modem, so you would have to do something on the network side to fool the modem.

[quote user="Siyou"]Does the modem fw mfw_nrf9160_1.2.0 support AGPS with SUPL session?[/quote]

Yes. Mfw 1.2.0 should work just fine with NCS v1.2.0, including the SUPL library.

To me, it looks like the problem is on the application side, but if you take a modem trace, I can check that the modem behaves as normal.

You could also try to add debug log output from the at_cmd library if you haven't already: CONFIG_AT_CMD_LOG_LEVEL=y

As the application restarts, you might need to use immediate logging to get log output before the reboot: CONFIG_LOG_IMMEDIATE=y

RE: questions for AGPS

Siyou — Wed, 27 May 2020 07:15:55 GMT

One more question:

Does the modem fw mfw_nrf9160_1.2.0 support AGPS with SUPL session? We found the SUPL session will crash with mfw_nrf9160_1.2.0.

Here are the test results by using the same application firmware with different modem firmware:

1), application could download AGPS data and finish SUPL session with mfw_nrf9160_1.1.1

[15:01:26.401]AT+CGMR
[15:01:26.408]mfw_nrf9160_1.1.1
OK

//Debug log:
[00:00:11.184,204] <inf> agps: GPS data id: NRF_GNSS_AGPS_DATA_ID(3)
[00:00:11.184,234] <inf> agps: New AGPS data requested, contacting SUPL server, flags 59
[00:00:11.184,509] <inf> agps: GPS control suspended
Starting SUPL session
[00:00:12.421,020] <inf> lte: +CEREG: 2,"0001","01A2D101",7,0,0,"11100000",~
[00:00:12.772,338] <inf> lte: +CEREG: 1,"0001","01A2D101",7,,,"11100000","1~
[00:00:12.772,369] <inf> lte: Connected to LTE network.
Established LTE link

ip 6cb1:7dc0:: (c07db16c) port 7276

Connected to SUPL server "supl.google.com:7276"

2), SUPL session will reboot when testing same application with mfw_nrf9160_1.2.0

[15:04:07.034]AT+CGMR
[15:04:07.041]mfw_nrf9160_1.2.0
OK

[00:00:33.969,604] <inf> agps: GPS data id: NRF_GNSS_AGPS_DATA_ID(3)
[00:00:33.969,635] <inf> agps: New AGPS data requested, contacting SUPL server, flags 59
[00:00:33.987,701] <inf> agps: GPS control suspended
Starting SUPL session
*** Booting Zephyr OS build v2.1.99-ncs1  ***

RE: questions for AGPS

Siyou — Tue, 26 May 2020 07:09:42 GMT

Hi Didrik,

Thanks for your sharing, but our project needs SUPL method AGPS, the nrf cloud AGPS may not suit our application.

We will try to test the google SUPL with simulated MCC/MNC, do you think it practicable?

RE: questions for AGPS

Didrik Rokhaug — Tue, 19 May 2020 14:17:53 GMT

Thanks for the clarification.

I have tried to ask around for A-GPS in China tips, but unfortunately, I have not gotten any good answers.

We have recently started providing A-GPS data through nRF Cloud, in addition to the SUPL library.

I got a bit conflicting answers when I asked how well nRF Cloud (which is built on AWS) works in China, but it might be worth a try: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/nrf9160/nrf_cloud_agps/README.html

Note that you have to use the master branch to test the nrf_cloud_agps sample.

RE: questions for AGPS

Siyou — Fri, 15 May 2020 07:21:23 GMT

Hi Didrik

Thanks for your help and info.

[quote userid="81181" url="~/f/nordic-q-a/60294/questions-for-agps/247395"]One of my colleagues says that China Telecom has a server that can be used if you are using China Telecom, but we have not been able to find the IP address of that server. Is it the 221.176.0.55 server you are using?[/quote]

Yes, previous test I used 221.176.0.55 as SUPL server which is China Mobile SUPL server's IP address, but failed with China Mobile NBIoT network.

As your suggestion, I tried China Telecom SUPL server(suplcn.sirf.com 114.80.208.5:7275) in Shanghai, but still failed:

1) Set SUPL as "suplcn.sirf.com", device will get DNS error:

[00:00:21.943,084] <inf> agps: New AGPS data requested, contacting SUPL server, flags 59
[00:00:21.961,181] <inf> agps: GPS control suspended
[00:00:39.478,698] <inf> lte: +CEREG: 2,"5AFD","0B2AFDD2",9,0,0,"11100000",~
[00:00:47.678,375] <inf> lte: +CEREG: 1,"5AFD","0B2AFDD2",9,,,"00000001","0~
[00:00:47.678,405] <inf> lte: Connected to LTE network.
Established LTE link

Failed to resolve hostname suplcn.sirf.com on IPv4, ret: 22, errno: 0)

[00:00:51.518,493] <inf> lte: +CEREG: 0,"5AFD","0B2AFDD2",9,0,0,"11100000",~
[00:00:51.971,923] <inf> agps: GPS restarted

2) Set SUPL as "114.80.208.5:7275", it will get the same failure as China Mobile SUPL server.

[00:00:13.062,683] <inf> agps: New AGPS data requested, contacting SUPL server, flags 59
[00:00:13.080,718] <inf> agps: GPS control suspended
[00:00:33.500,396] <inf> lte: +CEREG: 2,"5AFD","05DF7154",9,0,0,"11100000",~
Starting SUPL session
[00:00:38.793,487] <inf> lte: +CEREG: 1,"5AFD","05DF7154",9,,,"00000001","0~
[00:00:38.793,487] <inf> lte: Connected to LTE network.
Established LTE link

ip 7250:d005:: (5d05072) port 7275

Connected to SUPL server "114.80.208.5:7275"

ULP encoding length: 38

Bytes sent: 38

read again

read again

read again

read again

read again

read error: -1

ULP ossDecode fail 5

SUPL error: 1

ULP encoding length: 18

Sending SUPL message failed, bytes_sent: -1

SUPL session internal resources released

[00:00:44.063,507] <err> agps: SUPL session failed: -1
Done

[00:00:44.357,391] <inf> lte: +CEREG: 0,"5AFD","05DF7154",9,0,0,"11100000",~
[00:00:45.021,911] <inf> agps: GPS restarted

RE: questions for AGPS

Didrik Rokhaug — Mon, 04 May 2020 13:45:22 GMT

Hi again.

I have not been able to find any other SUPL servers that are accessible from China.

However, our team in Asia might know more.

Best regards,

Didrik

RE: questions for AGPS

Didrik Rokhaug — Wed, 29 Apr 2020 15:09:24 GMT

Hi, I am not aware of any SUPL servers that are supported in China, but I am looking into it.

The error you get is DATA_ERROR, which means that the data you receive from the server is not formatted correctly.

I have seen that error with another Chinese customer that tried to use the same server, but I was not able to identify the problem at the time.

One of my colleagues says that China Telecom has a server that can be used if you are using China Telecom, but we have not been able to find the IP address of that server. Is it the 221.176.0.55 server you are using?

I will look more into it tomorrow.

RE: questions for AGPS

Siyou — Tue, 28 Apr 2020 06:10:59 GMT

Hi,

The stack size remained as 4KB, added "CONFIG_NEWLIB_LIBC=y" and
"CONFIG_NEWLIB_LIBC_ALIGNED_HEAP_SIZE=16384"

Can you provide some SUPL server which supported chinese NB-IoT in China area for verification?

I have tried the server "221.176.0.55" with China Mobile NB-IoT but no luck, Could you help check below error log and point out how to get it work?

00> Starting SUPL session
00> [00:00:42.133,605] <inf> lte: +CEREG: 1,"5B82","01966A1C",9,,,"00100001","0~
00> [00:00:42.133,605] <inf> lte: Connected to LTE network.
00> Established LTE link
00> ip ddb0:37:: (3700b0dd) port 7275
00> Connected to SUPL server "221.176.0.55:7275"
00> ULP encoding length: 38
00> Bytes sent: 38
00> Bytes received: 7
00> ULP ossDecode fail 5
00> SUPL error: 1
00> ULP encoding length: 18
00> Bytes sent: 18
00> SUPL session internal resources released
00> [00:00:42.500,152] <err> agps: SUPL session failed: -1
00> Done
00> [00:00:42.819,000] <inf> lte: +CEREG: 0,"5B82","01966A1C",9,0,0,"11100000",~
00> [00:00:43.192,077] <inf> agps: GPS restarted
00> [00:00:45.192,199] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 20s
00> [00:00:45.192,321] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 20s
00> [00:00:45.217,224] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 20s
00> [00:00:46.217,254] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 21s
00> [00:00:47.217,773] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 22s
00> [00:00:48.216,857] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 23s
00> [00:00:49.217,376] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 24s
00> [00:00:50.217,346] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 25s

RE: questions for AGPS

Didrik Rokhaug — Fri, 24 Apr 2020 11:29:20 GMT

Great to hear you got it working!

May I ask what stack size you ended up with?

The "No location data available" means just that: the SUPL server does not have any location data to provide you. Instead, the library will fall back on its own table.

Google's SUPL server is keeping a database over cell tower positions, but this database is not complete. So the "No location data available" is expected and happens all the time.

When that happens, the library will fall back to assuming you are at the geographical center of the country you are in. How much this helps depends on the size of your country, and where in the country you are.

RE: questions for AGPS

Siyou — Fri, 24 Apr 2020 09:48:48 GMT

Hi Didrik,

Thanks for your help, now I can connect to the SUPL server and download the data.

But there is a new problem: it seems the AGPS has not took effect, I tried several times the results were the same. Can you also take a look at below log? Sorry I have not any knowledge of SUPL...

What is the meaning of log "No location data available"?

00> Starting SUPL session
00> [00:00:08.593,597] <inf> lte: +CEREG: 2,"0001","01A2D101",7,0,0,"11100000",~
00> [00:00:09.005,401] <inf> lte: +CEREG: 1,"0001","01A2D101",7,,,"11100000","1~
00> [00:00:09.005,432] <inf> lte: Connected to LTE network.
00> Established LTE link
00> 
00> ip 6cb1:61c0:: (c061b16c) port 7276
00> 
00> ULP encoding length: 38
00> 
00> Bytes sent: 38
00> 
00> Bytes received: 34
00> 
00> ULP ossDecode success, choice 3
00> 
00> SUPL server responded using version 2.0.4
00> 
00> SUPL response received
00> 
00> ULP encoding length: 57
00> 
00> Bytes sent: 57
00> 
00> Bytes received: 708
00> 
00> ULP ossDecode more input 4
00> 
00> Bytes received: 1416
00> 
00> ULP ossDecode more input 4
00> 
00> Bytes received: 2124
00> 
00> ULP ossDecode more input 4
00> 
00> Bytes received: 3065
00> 
00> ULP ossDecode success, choice 5
00> 
00> [00:00:09.490,722] <inf> agps: Injected AGPS data, flags: 1, size: 16
00> 
00> [00:00:09.491,943] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.492,553] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.493,316] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.494,110] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.494,720] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.495,391] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.496,063] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.496,673] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.497,253] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.498,107] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.500,762] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.501,373] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.502,136] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.502,716] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.503,356] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.504,058] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.504,669] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.505,371] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.506,134] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.506,713] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.509,338] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.510,009] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.510,742] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.511,383] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.512,115] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.512,725] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.513,366] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.514,190] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.514,984] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.515,563] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.518,188] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.518,951] <inf> agps: Injected AGPS data, flags: 2, size: 72
00> 
00> [00:00:09.519,348] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.519,714] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.520,172] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.520,538] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.521,087] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.521,453] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.522,003] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.522,399] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.525,024] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.525,390] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.525,970] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.526,306] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.526,672] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.527,160] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.527,526] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.528,076] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.528,442] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.529,022] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.530,273] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.530,670] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.531,158] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.531,555] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.532,104] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.532,470] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.533,020] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.533,386] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.533,721] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.534,179] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.534,545] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.535,095] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> [00:00:09.538,482] <inf> agps: Injected AGPS data, flags: 3, size: 32
00> 
00> No integrity data available
00> 
00> [00:00:09.539,093] <inf> agps: Injected AGPS data, flags: 4, size: 8
00> 
00> [00:00:09.549,652] <inf> agps: Injected AGPS data, flags: 6, size: 144
00> 
00> No location data available
00> 
00> No MCC location info available, MCC: 1
00> 
00> SUPL POS received
00> 
00> read again
00> 
00> Bytes received: 34
00> 
00> ULP ossDecode success, choice 6
00> 
00> SUPLEND:
00> 
00>   Mask: 0
00> 
00>   Status: 0
00> 
00> SUPL END received
00> 
00> SUPL session internal resources released
00> 
00> SUPL session finished
00> 
00> Done
00> 
00> [00:00:11.405,761] <inf> lte: +CEREG: 0,"0001","01A2D101",7,0,0,"11100000",~
00> [00:00:12.769,317] <inf> agps: GPS restarted
00> [00:00:14.769,439] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 7s
00> [00:00:14.769,561] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 7s
00> [00:00:14.806,579] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 7s
00> [00:00:15.806,671] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 8s
00> [00:00:16.807,250] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 9s
00> [00:00:17.806,884] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 10s
00> [00:00:18.807,067] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 11s
00> [00:00:19.806,213] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 12s
00> [00:00:20.806,793] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 13s
00> [00:00:21.807,373] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 14s
00> [00:00:22.806,610] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 15s
00> [00:00:23.807,373] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 16s
00> [00:00:24.807,098] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 17s
00> [00:00:25.806,884] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 18s
00> [00:00:26.807,464] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 19s
00> [00:00:27.807,067] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 20s
00> [00:00:28.806,640] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 21s
00> [00:00:29.807,220] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 22s
00> [00:00:30.807,006] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 23s
00> [00:00:31.807,586] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 24s
00> [00:00:32.807,189] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 25s
00> [00:00:33.806,762] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 26s
00> [00:00:34.807,434] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 27s
00> [00:00:35.807,098] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 28s
00> [00:00:36.807,647] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 29s
00> [00:00:37.806,915] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 30s
00> [00:00:38.806,945] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 31s
00> [00:00:39.807,739] <inf> agps: Tracking:0 Using:0 Unhealthy:0, since last fix 32s
00> [00:00:40.807,586] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 33s
00> [00:00:41.807,769] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 34s
00> [00:00:42.809,112] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 35s
00> [00:00:43.808,593] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 36s
00> [00:00:44.809,204] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 37s
00> [00:00:45.808,837] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 38s
00> [00:00:46.808,837] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 39s
00> [00:00:47.809,387] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 40s
00> [00:00:48.808,807] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 41s
00> [00:00:49.808,319] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 42s
00> [00:00:50.808,868] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 43s
00> [00:00:51.809,417] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 44s
00> [00:00:52.809,020] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 45s
00> [00:00:53.808,746] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 46s
00> [00:00:54.809,417] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 47s
00> [00:00:55.808,959] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 48s
00> [00:00:56.809,417] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 49s
00> [00:00:57.808,959] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 50s
00> [00:00:58.809,600] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 51s
00> [00:00:59.809,143] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 52s
00> [00:01:00.809,570] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 53s
00> [00:01:01.808,593] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 54s
00> [00:01:02.809,539] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 55s
00> [00:01:03.809,143] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 56s
00> [00:01:04.809,600] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 57s
00> [00:01:05.808,990] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 58s
00> [00:01:06.809,387] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 59s
00> [00:01:07.809,936] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 60s
00> [00:01:08.809,326] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 61s
00> [00:01:09.809,204] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 62s
00> [00:01:10.809,295] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 63s
00> [00:01:11.809,844] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 64s
00> [00:01:12.809,326] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 65s
00> [00:01:13.809,844] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 66s
00> [00:01:14.809,356] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 67s
00> [00:01:15.809,906] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 68s
00> [00:01:16.809,539] <inf> agps: Tracking:1 Using:0 Unhealthy:0, since last fix 69s
00> [00:01:17.809,539] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 70s
00> [00:01:18.810,119] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 71s
00> [00:01:19.810,729] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 72s
00> [00:01:20.810,272] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 73s
00> [00:01:21.810,791] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 74s
00> [00:01:22.810,241] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 75s
00> [00:01:23.810,760] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 76s
00> [00:01:24.810,729] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 77s
00> [00:01:25.811,309] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 78s
00> [00:01:26.810,729] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 79s
00> [00:01:27.811,584] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 80s
00> [00:01:28.810,699] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 81s
00> [00:01:29.810,821] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 82s
00> [00:01:30.811,462] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 83s
00> [00:01:31.810,882] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 84s
00> [00:01:32.810,943] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 85s
00> [00:01:33.811,706] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 86s
00> [00:01:34.811,401] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 87s
00> [00:01:35.811,584] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 88s
00> [00:01:36.811,309] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 89s
00> [00:01:37.810,943] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 90s
00> [00:01:38.811,645] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 91s
00> [00:01:39.811,157] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 92s
00> [00:01:40.811,157] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 93s
00> [00:01:41.811,859] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 94s
00> [00:01:42.811,614] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 95s
00> [00:01:43.811,065] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 96s
00> [00:01:44.811,767] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 97s
00> [00:01:45.811,157] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 98s
00> [00:01:46.811,828] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 99s
00> [00:01:47.810,668] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 100s
00> [00:01:48.811,370] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 101s
00> [00:01:49.812,103] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 102s
00> [00:01:50.811,737] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 103s
00> [00:01:51.811,401] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 104s
00> [00:01:52.811,981] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 105s
00> [00:01:53.811,370] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 106s
00> [00:01:54.811,462] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 107s
00> [00:01:55.812,225] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 108s
00> [00:01:56.811,553] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 109s
00> [00:01:57.812,133] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 110s
00> [00:01:58.811,401] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 111s
00> [00:01:59.811,492] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 112s
00> [00:02:00.812,164] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 113s
00> [00:02:01.811,553] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 114s
00> [00:02:02.811,035] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 115s
00> [00:02:03.812,377] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 116s
00> [00:02:04.812,072] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 117s
00> [00:02:05.812,286] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 118s
00> [00:02:06.811,981] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 119s
00> [00:02:07.811,645] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 120s
00> [00:02:08.812,408] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 121s
00> [00:02:09.812,011] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 122s
00> [00:02:10.811,676] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 123s
00> [00:02:11.812,561] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 124s
00> [00:02:12.812,286] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 125s
00> [00:02:13.812,438] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 126s
00> [00:02:14.812,469] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 127s
00> [00:02:15.811,828] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 128s
00> [00:02:16.812,530] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 129s
00> [00:02:17.812,042] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 130s
00> [00:02:18.812,805] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 131s
00> [00:02:19.812,286] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 132s
00> [00:02:20.812,530] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 133s
00> [00:02:21.811,981] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 134s
00> [00:02:22.812,683] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 135s
00> [00:02:23.812,042] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 136s
00> [00:02:24.812,774] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 137s
00> [00:02:25.812,561] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 138s
00> [00:02:26.812,927] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 139s
00> [00:02:27.812,255] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 140s
00> [00:02:28.812,774] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 141s
00> [00:02:29.812,225] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 142s
00> [00:02:30.812,835] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 143s
00> [00:02:31.812,164] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 144s
00> [00:02:32.813,110] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 145s
00> [00:02:33.812,896] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 146s
00> [00:02:34.812,927] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 147s
00> [00:02:35.812,957] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 148s
00> [00:02:36.812,927] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 149s
00> [00:02:37.813,018] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 150s
00> [00:02:38.813,079] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 151s
00> [00:02:39.812,500] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 152s
00> [00:02:40.812,377] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 153s
00> [00:02:41.812,927] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 154s
00> [00:02:42.812,438] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 155s
00> [00:02:43.813,262] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 156s
00> [00:02:44.813,110] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 157s
00> [00:02:45.813,110] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 158s
00> [00:02:46.813,201] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 159s
00> [00:02:47.813,232] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 160s
00> [00:02:48.813,262] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 161s
00> [00:02:49.813,201] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 162s
00> [00:02:50.812,774] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 163s
00> [00:02:51.812,561] <inf> agps: Tracking:2 Using:0 Unhealthy:0, since last fix 164s
00> [00:02:52.813,720] <inf> agps: Tracking:3 Using:0 Unhealthy:0, since last fix 165s
00> [00:02:53.813,385] <inf> agps: Tracking:3 Using:0 Unhealthy:0, since last fix 166s
00> [00:02:54.814,697] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 167s
00> [00:02:55.814,178] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 168s
00> [00:02:56.814,178] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 169s
00> [00:02:57.813,934] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 170s
00> [00:02:58.813,690] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 171s
00> [00:02:59.814,270] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 172s
00> [00:03:00.814,361] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 173s
00> [00:03:01.814,086] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 174s
00> [00:03:02.814,117] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 175s
00> [00:03:03.814,575] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 176s
00> [00:03:04.814,208] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 177s
00> [00:03:05.813,629] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 178s
00> [00:03:06.814,361] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 179s
00> [00:03:07.814,086] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 180s
00> [00:03:08.814,025] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 181s
00> [00:03:09.813,995] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 182s
00> [00:03:10.813,995] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 183s
00> [00:03:11.813,934] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 184s
00> [00:03:12.814,758] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 185s
00> [00:03:13.815,307] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 186s
00> [00:03:14.814,636] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 187s
00> [00:03:15.814,697] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 188s
00> [00:03:16.814,849] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 189s
00> [00:03:17.814,910] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 190s
00> [00:03:18.814,758] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 191s
00> [00:03:19.814,819] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 192s
00> [00:03:20.815,551] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 193s
00> [00:03:21.814,819] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 194s
00> [00:03:22.814,941] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 195s
00> [00:03:23.815,002] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 196s
00> [00:03:24.814,849] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 197s
00> [00:03:25.814,575] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 198s
00> [00:03:26.814,941] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 199s
00> [00:03:27.815,460] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 200s
00> [00:03:28.816,009] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 201s
00> [00:03:29.814,636] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 202s
00> [00:03:30.814,422] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 203s
00> [00:03:31.815,032] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 204s
00> [00:03:32.815,551] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 205s
00> [00:03:33.814,514] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 206s
00> [00:03:34.815,246] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 207s
00> [00:03:35.815,277] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 208s
00> [00:03:36.815,002] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 209s
00> [00:03:37.815,155] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 210s
00> [00:03:38.815,063] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 211s
00> [00:03:39.815,521] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 212s
00> [00:03:40.815,216] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 213s
00> [00:03:41.815,124] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 214s
00> [00:03:42.814,971] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 215s
00> [00:03:43.815,338] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 216s
00> [00:03:44.815,795] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 217s
00> [00:03:45.815,490] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 218s
00> [00:03:46.816,009] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 219s
00> [00:03:47.814,910] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 220s
00> [00:03:48.815,460] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 221s
00> [00:03:49.815,093] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 222s
00> [00:03:50.815,490] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 223s
00> [00:03:51.816,101] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 224s
00> [00:03:52.815,704] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 225s
00> [00:03:53.816,375] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 226s
00> [00:03:54.815,216] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 227s
00> [00:03:55.815,734] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 228s
00> [00:03:56.815,612] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 229s
00> [00:03:57.815,643] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 230s
00> [00:03:58.815,368] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 231s
00> [00:03:59.815,673] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 232s
00> [00:04:00.816,192] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 233s
00> [00:04:01.816,741] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 234s
00> [00:04:02.815,368] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 235s
00> [00:04:03.815,155] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 236s
00> [00:04:04.815,917] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 237s
00> [00:04:05.815,979] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 238s
00> [00:04:06.816,467] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 239s
00> [00:04:07.815,856] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 240s
00> [00:04:08.815,551] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 241s
00> [00:04:09.816,406] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 242s
00> [00:04:10.815,979] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 243s
00> [00:04:11.816,589] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 244s
00> [00:04:12.816,711] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 245s
00> [00:04:13.815,399] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 246s
00> [00:04:14.816,192] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 247s
00> [00:04:15.816,040] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 248s
00> [00:04:16.816,101] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 249s
00> [00:04:17.816,101] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 250s
00> [00:04:18.816,131] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 251s
00> [00:04:19.816,253] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 252s
00> [00:04:20.816,925] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 253s
00> [00:04:21.815,612] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 254s
00> [00:04:22.816,192] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 255s
00> [00:04:23.816,345] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 256s
00> [00:04:24.816,406] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 257s
00> [00:04:25.816,497] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 258s
00> [00:04:26.816,314] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 259s
00> [00:04:27.816,314] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 260s
00> [00:04:28.817,108] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 261s
00> [00:04:29.816,406] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 262s
00> [00:04:30.816,528] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 263s
00> [00:04:31.816,314] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 264s
00> [00:04:32.816,375] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 265s
00> [00:04:33.816,894] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 266s
00> [00:04:34.816,497] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 267s
00> [00:04:35.816,162] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 268s
00> [00:04:36.816,711] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 269s
00> [00:04:37.816,558] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 270s
00> [00:04:38.816,711] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 271s
00> [00:04:39.816,558] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 272s
00> [00:04:40.816,009] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 273s
00> [00:04:41.816,589] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 274s
00> [00:04:42.817,077] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 275s
00> [00:04:43.816,864] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 276s
00> [00:04:44.816,894] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 277s
00> [00:04:45.816,650] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 278s
00> [00:04:46.817,504] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 279s
00> [00:04:47.817,535] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 280s
00> [00:04:48.817,626] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 281s
00> [00:04:49.816,802] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 282s
00> [00:04:50.817,352] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 283s
00> [00:04:51.816,986] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 284s
00> [00:04:52.816,741] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 285s
00> [00:04:53.816,314] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 286s
00> [00:04:54.817,077] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 287s
00> [00:04:55.817,169] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 288s
00> [00:04:56.816,833] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 289s
00> [00:04:57.816,650] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 290s
00> [00:04:58.817,047] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 291s
00> [00:04:59.817,199] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 292s
00> [00:05:00.816,925] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 293s
00> [00:05:01.817,108] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 294s
00> [00:05:02.816,558] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 295s
00> [00:05:03.817,779] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 296s
00> [00:05:04.817,321] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 297s
00> [00:05:05.817,169] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 298s
00> [00:05:06.817,047] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 299s
00> [00:05:07.817,352] <inf> agps: Tracking:3 Using:3 Unhealthy:0, since last fix 300s

RE: questions for AGPS

Didrik Rokhaug — Thu, 23 Apr 2020 15:53:34 GMT

It looks like you are able to initialize the decoding library now, which is good.

The error a stack overflow, as is said in the log.

You could try to figure out what thread overflows by using k_current_get, but my guess is that it is the GPS thread where you are running the SUPL library.

You could try to increase the stack size of that thread a bit more.

RE: questions for AGPS

Siyou — Thu, 23 Apr 2020 01:30:34 GMT

Still failed, the system will crash, here is the error log after enabled the Newlib libc

And the result will be same with or without option "CONFIG_NEWLIB_LIBC_ALIGNED_HEAP_SIZE=4096"

Starting SUPL session
[00:00:17.443,603] <inf> lte: +CEREG: 2,"0001","01A2D101",7,0,0,"11100000",~
[00:00:17.874,969] <inf> lte: +CEREG: 1,"0001","01A2D101",7,,,"00001111","1~
[00:00:17.875,000] <inf> lte: Connected to LTE network.
Established LTE link

ip 6cb1:61c0:: (c061b16c) port 7276

ULP encoding length: 38

[00:00:18.049,774] <err> os: r0/a1:  0x00000002  r1/a2:  0x20023788  r2/a3:  0xf0f0f0f0
[00:00:18.049,774] <err> os: r3/a4:  0x2002fe58 r12/ip:  0x00000000 r14/lr:  0x00043dcf
[00:00:18.049,774] <err> os:  xpsr:  0x41000000
[00:00:18.049,774] <err> os: s[ 0]:  0x00000000  s[ 1]:  0x00000000  s[ 2]:  0x00000000  s[ 3]:  0x00000000
[00:00:18.049,804] <err> os: s[ 4]:  0x00000000  s[ 5]:  0x00000000  s[ 6]:  0x00000000  s[ 7]:  0x00000000
[00:00:18.049,804] <err> os: s[ 8]:  0x00000000  s[ 9]:  0x00000000  s[10]:  0x00000000  s[11]:  0x00000000
[00:00:18.049,835] <err> os: s[12]:  0x00000000  s[13]:  0x00000000  s[14]:  0x00000000  s[15]:  0x00000000
[00:00:18.049,835] <err> os: fpscr:  0x20024acc
[00:00:18.049,835] <err> os: Faulting instruction address (r15/pc): 0x00037bd6
[00:00:18.049,835] <err> os: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
[00:00:18.049,835] <err> os: Current thread: 0x20023788 (unknown)
[00:00:18.538,238] <err> fatal_error: Resetting system
*** Booting Zephyr OS build v2.1.99-ncs1  ***

RE: questions for AGPS

Didrik Rokhaug — Wed, 22 Apr 2020 12:32:49 GMT

The answer I got was this:

This code does not use the zephyr kernel memory allocation code (k_malloc), it uses the libc vanilla malloc implementation. So this heap has to be tuned with either CONFIG_MINIMAL_LIBC_MALLOC_ARENA_SIZE or CONFIG_NEWLIB_LIBC_ALIGNED_HEAP_SIZE kconfig parameter, depending on which libc version is used.

However, before you start playing around with those options, I want you to try something else:
The GPS sample is using the Newlib libc, instead of Zephyr's standard minimal libc. However, the serial_lte_modem sample does not. Could you try to enable the Newlib libc?

You can do that by adding CONFIG_NEWLIB_LIBC=y to your prj.conf file

RE: questions for AGPS

Siyou — Tue, 21 Apr 2020 10:02:29 GMT

[quote userid="81181" url="~/f/nordic-q-a/60294/questions-for-agps/245791"]If you are using Segger Embedded Studio, did you remember to re-open the project after making the changes to the prj.conf file?[/quote]

We built the project by gcc on linux server.

[quote userid="81181" url="~/f/nordic-q-a/60294/questions-for-agps/245791"]I will ask our developers if they have other suggestions for you.[/quote]

Looking forward to your update, thank you

RE: questions for AGPS

Didrik Rokhaug — Tue, 21 Apr 2020 09:52:11 GMT

If you are using Segger Embedded Studio, did you remember to re-open the project after making the changes to the prj.conf file?

Looking at the GPS sample, it uses a stack of 4KB and heap of 2KB, so I don't know why your configuration did not work.

I will ask our developers if they have other suggestions for you.

RE: questions for AGPS

Siyou — Tue, 21 Apr 2020 01:06:16 GMT

Hello,

Sorry to push you, our project is waiting for this agps feature, can anybody provide the support of how to integrate the SUPL client library to serial_lte_modem sample?

RE: questions for AGPS

Siyou — Mon, 20 Apr 2020 09:15:39 GMT

[quote userid="81181" url="~/f/nordic-q-a/60294/questions-for-agps/245442"]In what thread are you running the SUPL library, how large stack does that thread have, and how much heap do you have?[/quote]

I start supl_session in gps_thread_fn() of slm_at_gps.c, the original THREAD_STACK_SIZE is 1KB, heap size as below:

CONFIG_MAIN_STACK_SIZE=8192
CONFIG_HEAP_MEM_POOL_SIZE=16384

I tried changing the THREAD_STACK_SIZE to 4KB but the supl_session still was failed as before.

how large stack does the supl_session need?

RE: questions for AGPS

Didrik Rokhaug — Mon, 20 Apr 2020 08:07:13 GMT

[quote user="Siyou"]How to ensure this? I download the library from your site and put them into "nrf\ext\lib\bin\supl"[/quote]

What I meant was how you had included it in your application. But yes, you have put the library in the right place.

[quote user="Siyou"][/quote]

Didrik Rokhaug said:

Have you enabled debug logging in the library?

How to enable the library logging?

After taking another look at the SUPL library, I might have misunderstood how the logging in the library works. The library should provide debug logging regardless, while you can decide if you want to print it in the log handler you provide to the library.

[quote user="Didrik Rokhaug"]Libsupl error 8 is LIBSUPL_SESSION_MISSING_ERR[/quote]

Again, I misunderstood where the error came from. It does not mean LIBSUPL_SESSION_MISSING_ERR, but OUT_MEMORY: https://www.oss.com/asn1/products/documentation/asn1_c_10.7/asn1c-runtime-return-codes.html

In what thread are you running the SUPL library, how large stack does that thread have, and how much heap do you have?

What happens if you increase those?

The SUPL error is LIBSUPL_DECODE_ERR, which is expected, as the library used for decoding fails to be initialized.

RE: questions for AGPS

Siyou — Mon, 20 Apr 2020 02:38:53 GMT

[quote userid="81181" url="~/f/nordic-q-a/60294/questions-for-agps/245282"]Are you certain that you integrated the SUPL library correctly?[/quote]

How to ensure this? I download the library from your site and put them into "nrf\ext\lib\bin\supl"

[quote userid="81181" url="~/f/nordic-q-a/60294/questions-for-agps/245282"]Have you enabled debug logging in the library? [/quote]

How to enable the library logging?

Updated the agps log as below:

00> Starting SUPL session
00> [00:00:22.179,504] <inf> lte: +CEREG: 2,"0001","01A2D101",7,0,0,"11100000",~
00> [00:00:22.490,875] <inf> lte: +CEREG: 1,"0001","01A2D101",7,,,"00001111","1~
00> [00:00:22.490,875] <inf> lte: Connected to LTE network.
00> Established LTE link
00> 
00> ip 6cb1:61c0:: (c061b16c) port 7276
00> 
00> ossinit failed, rc: 8
00> 
00> SUPL session internal resources released
00> 
00> [00:00:22.644,195] <err> agps: SUPL session failed: -15
00> Done
00> 
00> [00:00:22.682,647] <inf> lte: +CEREG: 0,"0001","01A2D101",7,0,0,"11100000",~

RE: questions for AGPS

Didrik Rokhaug — Fri, 17 Apr 2020 14:47:36 GMT

Hi.

Libsupl error 8 is LIBSUPL_SESSION_MISSING_ERR. Are you certain that you integrated the SUPL library correctly?

Have you enabled debug logging in the library? That might provide more details about what goes wrong.

Best regards,

Didrik

RE: questions for AGPS

Siyou — Fri, 17 Apr 2020 08:52:16 GMT

SDK: NCS v1.2

modem: mfw_nrf9160_1.1.1

SUPL client library: nrf9160_libsupl-v0.5.2