What are the conditions under which the `sv_mask_alm` field in `struct nrf_modem_gnss_agps_data_frame` will stop being 0xFFFFFFFF?
I am providing almanac data for SV's 2-32 (generated from nRF Cloud today) by writing with `NRF_MODEM_GNSS_AGPS_ALMANAC`.
The modem is continuously getting a good location fix (<5 meters) within 10 seconds after restarting, implying that it has a good idea of current time, almanacs and ephemeris.
However each time the modem restarts, the `sv_mask_alm` field is still set to 0xFFFFFFFF.
Printing out the almanac expiry times for each SV from `nrf_modem_gnss_agps_expiry_get` confirms that the modem thinks the almanac data is valid for the next 2 weeks.
[00:16:49.185,699] <inf> act_gnss: Fix started [00:16:49.185,699] <inf> act_gnss: Providing almanac assistance ffffffff [00:16:49.265,625] <inf> act_gnss: Providing time assistance (1376279646) [00:16:49.266,143] <inf> act_gnss: Providing location assistance (APP) [00:16:49.269,561] <wrn> act_gnss: EXP: 00000023 7200 0 [00:16:49.269,561] <wrn> act_gnss: A EXP: 144162 1353761 1353761 1353761 [00:16:49.269,592] <wrn> act_gnss: A EXP: 1353761 1353761 1353761 1353761 [00:16:49.269,592] <wrn> act_gnss: A EXP: 1353761 1353761 1353761 1353761 [00:16:49.269,622] <wrn> act_gnss: A EXP: 1353761 1353761 1353761 1353761 [00:16:49.269,622] <wrn> act_gnss: A EXP: 1353761 1353761 1353761 1353761 [00:16:49.269,622] <wrn> act_gnss: A EXP: 1353761 1353761 1353761 1353761 [00:16:49.269,653] <wrn> act_gnss: A EXP: 1353761 1353761 1353761 1353761 [00:16:49.269,653] <wrn> act_gnss: A EXP: 1353761 1353761 1353761 1353761
After a large number of runs, eventually the bits will be cleared to 0, but there is no reasoning that I can detect as to why this occurs.
I am looking to get a better understanding of these flags, in case there are further improvements I can make to my assistance data.