When I log a new QSO with a SOTA station on device A, export it as an ADIF file, and then import it into device B, the SOTA information does not appear in the target log. However, it remains available in both the source log and the ADIF file.
When you import an ADIF file into an operation, it only brings in the basic QSO information. It preserves any activity and location information from the PoLo operation into which you’re importing the QSOs.
It’s not meant as a way to sync operation between phones, but as a way to bring QSOs from other sources, like FT8 apps or other loggers, and combine them into the current operation.
In the meantime, we’re working on better ways to sync between devices.
Would it be a bad idea to make PoLo carry over all the available QSO information between devices, as long as the ADIF format permits it?
This would not only help with syncing across multiple devices, but also be useful for backup and restore purposes on the same device.
If you enable Developer Mode you can import and export a “QSON” file, which is the internal data format used by PoLo. The process is a bit cumbersome, but it will do if you need to move an operation right now.
As for sync and backups, I’m working on a service that will do this transparently and automatically.