I installed PoLo on two Samsung devices (phone and tablet) and experience the same issue with both. In contrast to the introduction video, the „Export Log Files“ function does neither offer the option to store the files locally nor to copy the files. In this forum I found already two threads [How to export ADIF to local storage on Android? and POTA log don’t export - #12 by K7CAN] but not the desired workaround. Ham fellows confirmed that the export with local storage works flawlessly on Apple phones. I wonder why PoLo offers only apps on Android which support a share function and not e. g. the file manager for further processing. I also recognized that the import function provides access to all stored ADIFs, regardless of the memory used (internal or SD card). Permissions granted by Android do not seem to distinguish between reading and writing. At least I did not find a tick box for granting PoLo additional rights.
This is shows the screen on my Android Samsung phone:
Polo can only offer what the operating system allows.
I think your best option is to install Files by Google - see the posts you mentioned above for the link if you need it.
I think most people use a cloud service to share to so it’s immediately able to be picked up on other devices/desktop setups.
Alan
Alan, thank you very much for your immediate response and your comments.
So far, I have used VK port-a-log for my WWFF and SOTA activations. Since this program is installed on the same devices as mentioned above and also widely used by other activators, it may serve as a reference and for comparison. VK port-a-log has no problems at all to create a directory on my phone or tablet where the *.adi and *.csv files are stored. No supporting app is needed and the program saves the files automatically without an “export files” command. Consequently, I can easily download those files to my desktop computer for further processing and upload them to SOTA or WWFF directly from my mobile device or later on from my desktop.
PoLo can download, store and maintain/update databases for summits and parks on my mobile. The same holds true for my activation data which are also stored in a PoLo internal file format on my phone. Although locally stored on the device, those data are not directly accessible by the user. Even after initiating the conversion from the PoLo internal format to *.adi with the “export files” command, I have no direct access and no choice of local storage, but have to employ a supporting app [messenger, e-mail, cloud services etc.] for redirecting the files elsewhere. Although I appreciate your proposal regarding “Files by Google”, this seems to follow the same principle.
VK port-a-log, running on the same devices, provides the evidence that the *.adi files can be stored locally and that this is not an Android issue. In comparison to the *.adi files, which are usually only a few kB in size, PoLo also stores significant amounts of data locally in different formats. With this in mind, I am still struggling to believe that the Android OS is preventing PoLo from storing the *.adi files directly on my mobile.
Anyhow, PoLo still seems to be an attractive alternative to me and I am prepared to give it another try once the described hurdle can be cleared. Thanks again for your input.
Peter,
I am very familiar with VK-port-a-log. I have used for for some years. I used it in conjunction with DropSync to being my files back to the cloud.
By comparison, however, it is Android only and must be side-loaded after enabling developer mode.
PoLo is developed in React-Native providing cross platform delivery to Android AND iOS.
There are trade-offs when you decide to comply with all the standard/public security protocols. You must abide by the requirements which are set for you.
I’m afraid the ‘hurdles’ you refer to will most likely remain with PoLo. I personally use DropBox and find it extremely convenient. It is exactly as I used DropSync with VK port-a-log.
Alan
Alan,
“most likely” does sound much more promising than “definitely” or “impossible”. Therefore, I still have some hope that my request may be considered.
Thanks again for your time spent on reading and answering my post.
There are issues doing direct file exports on the Android version, and I’ve tried to figure out what the root cause is with little success. Since there are other ways to get the files out, I’ve pushed this problem aside for now to focus on other features, but it is definitely something I want to get fixed.
Thank you very much for providing some background information and the positive outlook. The steep development curve in the recent past and the vast number of already available features are quite impressive. I like your view on priorities and shaping the performance profile. PoLo is slim in appearance with the right number of windows and complexity. The worst thing that could happen now in the “polishing phase” is overloading with bling bling and unnecessary modules like e. g. a rotor interface. I am very pleased that you will see to my request when time permits. Thanks for all your hard work and good luck with the challenges still ahead.
Therefore, I still have some hope that my request may be considered.