No log files are written.

[EngelMT]

Hello everyone,

I would like to use the app with a FrSky FrID GPS tracker. So far, this has been working without any problems. I can see all the data I need for flying in the UK. Attached is a screenshot from my mobile phone screen.

However, in the UK, it is required that you record log files and be able to read them after the flight. I have selected "Log enabled" in the app. Nevertheless, I cannot find any records.

Perhaps someone can explain to me whether the app creates a directory path for the log or whether I have to do this manually. Information on what the path should look like would also be helpful.

I assume that the data is stored in CSV format. This should make it easy to read.

Many thanks for help

[friissoren]

What happens when you press the "show log location" button, just under the "Log enabled" check-box?
It should briefly show you a long path, which you can then navigate to when you have the phone plugged in via a USB cable to a PC (there might be other ways to access that location also).

[EngelMT]

Thanks for your fast responce. Here is the log path.

Do you see a mistake there?

I notice that the synchronisation doesn't seem to be working. That wouldn't have anything to do with the app. Do you perhaps have a tip?

[friissoren]

That path looks reasonable. How are you connecting your PC to the phone? USB cable?
I probably can't help much with that but typically you need to change the connection mode on the phone itself, in order to allow the PC to access files on the phone. Something like "file transfer mode" or MTP (media transfer protocol) mode or similar. Probably Google is a better help here.

When you pressed the "Show log location" button in the UI, did you see the pop-up at the bottom that shows the full path to the log file?

The second picture shows the sync status of Microsoft OneDrive on your PC for a folder. That has nothing to do with things on the Android phone.

[BluemarkInnovations]

I would recommend installing a file manager app like Google Files. Now you can browse to the folder without the need to connect to your PC. You could also move files to a more convenient folder that is accessible by your PC. This does not work. Likely newer Android versions have stricter security policies. Using the Files app, I cannot access the folder. Using Transferring fiels/ Android Auto mode on a Samsung S21, I still can access the folder using my PC. (But for a different Android version or phone, this could be different.)

If you sill have issues, there are also other apps. I think that DroneScanner of DroneTag allows you to export CSV files. Also, we provide a RemoteID app for Android (and iOS/iPad): DroneScout pro. The free version allows you to capture flight data and export it to GPX. Here besides download, you can share, or attach it to an email.

A bit off-topic, but relevant in my opinion. There are different RemoteID regions like FAA, Japan en EASA (EU). Each region has its own RemoteID transmitter requirements. Basically, the FrSky FrID is only allowed for operation in the FAA region. It is not compliant with EASA regulation!! In EASA region (including) UK you need to include the OPRN (OperatorID) in the RemoteID signal. Basically, you need a RemoteID add-on with a user interface or app where you can set the OPRN. A good overview of EASA compatible RemoteID transmitter hardware can be found on the EASA website.

Much more off-topic, if you would fly in the FAA region (US), I would say the FrSky FrID has issues with the height and should fix that in a firmware upgrade. The Height field in the EU is mandatory, it is the height above the Take-Off location. In your screenshot I see that both the Height, Alt Geod. and Operator Altitude are all around 235 m (which is not possible). I guess you are on the grond when you took the screenshot, and the drone was not flying 235 meter above the ground.

However, in the UK, it is required that you record log files and be able to read them after the flight. I have selected "Log enabled" in the app. Nevertheless, I cannot find any records.

So in short after you solved the issue of recording log files of your flight, you still fly illegal and get fined because you do not broadcast the OPRN number.

[EngelMT]

Hi together, many thanks for the info. So we will use an other ID Tracker.

[BluemarkInnovations]

To comment on the original post, I think that this app does not follow the latest Android guidelines to store data. And that some users will not be able to access the log files. And with newer Android versions this issue may get more dominant due to stricter security policies.

This is what a Google search returns: "Android app store files (specifically apps downloaded from the Google Play Store) and their data are primarily stored in internal memory under /data/user/{user_id}/{pkg} or /data/data/{pkg} for private data, and in /storage/emulated/{user_id}/Android/data/{pkg}/ for external/shared data. Accessing these folders on Android 11+ often requires specialized file managers or PC connectivity."

[gabrielcox]

Folks,
Lets remember that this is the issue section of an open source repository, not an app comment section. So lets keep the conversation to the actual source code. Suggestions and PRs are welcome.

@BluemarkInnovations , if something in the source is implemented wrong against the android standard, please point it out with a proper reference to the authoritative document. (not disagreeing, but I don't know what to make of a google search).

Doing some searching in the source, from what I can tell, it currently sets the log directory this way:

File file = new File(Environment.getExternalStoragePublicDirectory(Environment.DIRECTORY_DOCUMENTS), "OpenDroneID");
Which is documented here:

https://developer.android.com/reference/android/os/Environment

public static String DIRECTORY_DOCUMENTS : Standard directory in which to place documents that have been created by the user.

I do see other options like DOWNLOADS, and ExternalStorage, but I don't see the clarity that one of these is any more appropriate than the current selection.

What should the implementation change be?

[BluemarkInnovations]

@BluemarkInnovations , if something in the source is implemented wrong against the android standard, please point it out with a proper reference to the authoritative document. (not disagreeing, but I don't know what to make of a google search).

https://source.android.com/docs/core/storage/scoped
https://medium.com/the-android-caf%C3%A9/scoped-storage-android-all-you-need-to-know-244ec1d00f18
https://www.geeksforgeeks.org/android/scoped-storage-in-android/

Basically, it seems Android is rolling out the Scoped storage feature. So from an app point of view, everything works, but each app has its own file system.

The last link has this section:
Storage for Individuals
This storage is still the same as previously. It is the app's own private directory (/app/data/Package Name>) to which the app has unrestricted read and write access.

Storage That is shared
This is subdivided further into Media and Download collections. Image, audio, and video files are stored in the Media collection. Non-media files would be handled via download collection.

I think the folder is considered as individual app storage and for that reason not available.