Questions about nRF Connect v1.3.0

[Jeffery]

1. By the toolchain manager, the sdk connect and zipped toolchain were downloaded.

    I used the downloaded SES to compile examples. For others, they can compile successfully.

    For \nrf\applications\connectivity_bridge, it got error when I opened nRF Connect options.

    Please see attached PIC1 and PIC2.

2. For AGPS, it can be found there are two examples: GPS with SUPL client library and nrf_cloud_agps.

    What is the difference between them?

    Is SUPL way  to load AGPS data from SUPL server of the local LTE carrier?

    Is nrf_cloud_agps to load AGPS data from NRF CLOUD? How you provide AGPS data from NRF CLOUD side?

    Which one is more fast and more stable?

3. If nrf_cloud_agps is better, how did 3rd party cloud to refer to? Did you have document to tell us the process loading AGPS.  

4. Actually, at ncs v1.2.0, I did add SUPL client library at asset tracker example. In cold start, it can save 20 seconds to fix GPS,

    compared to original asset tracker without AGPS.

Thanks.

Jeffery

[Heidi]

Hi!

1. The connectivity bridge is made for the nRF52840 on the Thingy:91, so try building for the board "thingy91_nrf52840".

2. The main difference between these two is that the GPS with SUPL client library gets the assisted GPS information from Google's SUPL server, while nrf_cloud_agps gets the information from Nordic's cloud solution, nRF Connect for Cloud. 

The nrf_cloud_agps is recommended if you're application is using nRF Connect for Cloud as the Cloud solution. If you're using something else, like your own server, or AWS, then using Google's SUPL server might be easier.

I can't answer to which one is faster or more stable. Both samples are stable, as they're a part of an official release of NCS. 

SUPL is a protocol for downloading this assist GPS data. nRF Cloud does not use the SUPL protocol, it uses LTE. 

3. This is the documentation for nRF Cloud AGPS. 

4. Yes, that sounds correct.

Best regards,

Heidi