jks

Make sure the Kiwi server is not running on the destination Kiwi where you are going to replace the dx.json file. You can't change the file on-the-fly while the server is running. It reads the file once at startup and that's it. However it gets written each time a change is made from the Kiwi UI.

So other sources are reporting that most of the Galileo ephemerides seem to have returned to normal. I have noticed this in my testing and the "TDoA capable" count on kiwisdr.com/public has been > 250 all day.

These same sources also said there was little correlation between sats with the alert flag set and sats with ephemerides "issue of data" (IODE) values indicating invalid navigation data. When I added code to track the age of updates to the IODE I noticed the same thing. So this criteria needs to be added in addition to just looking at the alert flag. This is apparently how professional receivers work.

Unfortunately GLONASS, BeiDou, NAVIC et al. don't transmit signals on the L1 frequency (1575.42 MHz, 2 MHz b/w) used by the GPS front-end chip of the Kiwi.

All right, v1.304 has individual enabling of Navstar/QZSS/Galileo acquisition.

Update: the Kiwi in Kuwait has an excellent, strong signal. The DRM signal itself is supposed to be coming from Kuwait according to http://www.hfcc.org/drm