strange behavior when opening a file

[OmlineEditor]

there are two ways to open a file using a file manager

1) select documents or photos from the menu in the list and open the file from this menu. (ready built-in menu) 2) select the carrier phone, go to the documents folder or the DCIM folder and open the file from there. (I use my hands to tell the path by moving through the folders)

if I open it, I use the first option (ready built-in menu) the error is shown that the file is read-only. if you open the same file using the second method then there are no problems

[Keidan]

For point 1, are you using HexViewer or an external file manager (if so which one?)?

Generally if you have this kind of message it's because Android returns this kind of error, which is a catch-all error. I'll look with the emulator if I can find a workaround, but if Android denies me access, I won't be able to do anything...

[OmlineEditor]

the standard built-in android 9 file manager. the first option opens the folder immediately. the second option is to specify the path to the folder

[Keidan]

Okay, I understand better. The first one will generate URIs that don't match anything on the smartphone, I seem to have seen people on stackoverflow talking about this. I'll see if I can base it on what they did...

[Keidan]

I don't have the same error as you with the emulator, but I think the problem is similar. It is due to a regression introduced when fixing the file corruption, where I was opening the file in read and write mode. In your case, it should be opened in read-only mode, which makes sense because in this mode (opening from outside), I will only read the file and nothing else...