It depends of what File Browser version you have.
The version from Jolla Store is restricted by SailJail. You can’t see all files with it.
The version from the link in post #27 is open and you can see all files.
In pulley menu / Viewing settings (Ansichtseinstellungen) you can enable ‘view hidden files’ to get listed all files, the ones beginning with a dot, too.
So any app in Jolla Store has to use SailJail, and there is no way to get an all folders permission in SailJail (I have seen permissions about a bunch of folder, but for example nothing that would allow ~/Desktop/ access) am I right ?
So a “complete” File Browser can only be found in openrepos/chum, that makes sense.
Thanks for the link !
I improved the hints to be less confusing now :).
Exactly; I’m working on a way to detect if the app is running in the jail so it can show a warning / explanation. Until then, I just hope people find this thread or notice the hint in the app description.
And thank you @Seven.of.nine for answering the questions! 
Hi @ichthyosaurus! Thank you for the great 3.0 update!
In the latest version from OpenRepos, there’s a small issue with external drives list on a home page:
Currently, I have no SD-card / USB drives installed, however the app has several dozens items listed. It identified many com.android folders as external drives, and also these folders:
/metadata
/vendor/dsp
/vendor/firmware_mnt
/vendor/bt_firmware
/mnt/vendor/persist
Thanks! I don’t have that issue on my phone… Can you start the app from the terminal and send me the output in a direct message? Don’t post it openly, there might be private stuff in the log.
I am looking for lines like this: `[D] unknown:0 - new mount detected: “SD Card” “/dev/mmcblk1p1” “ext4” “/run/media/nemo/SD Card”`` I will then mark all paths that clearly belong to the system as ignored so they don’t show up in the list anymore.
Q: How can I fix File Browser?
On try to open a PDF document from File Browser for reading it, File Browser says “File couldn’t be loaded” (Seite konnte nicht geladen werden).
On tapping on the file, File Browser shows the preview and the usually options (cut, copy, trash, rename…), on pulldown menu → open, the documents app tries to open but after 2 seconds it fails with the mentioned error message. On tapping the upper right button, the error msg comes immediately. From within the Documents app it’s also not possible to open a PDF file with the same error msg.
I also tried to deinstall the Documents app - reboot - reinstall, but the error remains.
What can I do? Thanks for any help!
That sounds like classic Sailjail issues… Are you sure you’re using the version from Openrepos?
Please start the app from the terminal and look out for these lines in the log:
[D] onCompleted:199 - running File Browser: version 3.0.0-1 (OpenRepos)
[D] onCompleted:201 - info: no explicit Harbour compliance
[D] onCompleted:202 - enabled features: sharing = 1 (0), PDF viewer = 1, storage settings = 1
I overlooked that line. That hints at a different problem. Can you open other PDF files or does it only happen with a specific one?
Also, try running sailfish-office from the terminal and see if it maybe prints something useful.
File Browser uses the documents app to show PDFs internally, so if it’s a bug in that app, I can’t fix it.
Yes, it’s the version from OpenRepos, but v 2.5.1-1, on SFOS 4.5.0.24 / Xperia 10.
The 3 lines are:
onCompleted:143 - running File Browser: Version 2.5.1-1 (stable)
onCompleted:144 - details: no explicit Harbour compliance
onCompleted:145 - enabled features: sharing = 1 (Share), PDF viewer = 1, storage settings = 1
Yes , it’s the same situation when opening sailfish-office from terminal and then try to open PDF from in SF-Office, so I agree that the Sailfish-Office PDF viewer is the culprit and not File Browser.
Do you have an idea how to fix SF-Office? Deinstalling - reboot - reinstalling didn’t help!
Shall I reinstall some libs?
edit: One of my tweaks was the culprit. Undid it, now everything works again. Thank you very much for caring @ichthyosaurus !
I also observed in the past, that sailfish file browsers tend to list long-gone sd-cards in the file system
Thank you @ichthyosaurus for the File Browser update! Installation from downloaded .rpm from OpenRepos went fine. Didn’t know about so many partitions existing on the phone!
There are listed:
user dir,
root,
vendor,
dsp,
and 4 x memory card with different sizes.
One of them is the ‘real’ one, the others are bt_firmware, persist and firmware_mnt, all with no permission to read.
I think @ichthyosaurus is doing a great job providing us File Browser, now also with root mode, but home page is f***ed up.
I’ve never had more then one X card on my X10III, and yet there is 20+ in latest upgrade.
Can I provide logs or something?
Ah that’s great, glad you could fix it .
That’s probably because these apps read the contents of /run/media/<youruser>/. That path could contain leftover directories that were once used for SD cards. That also means that they don’t show you any manually mounted folders.
File Browser uses actual mount points instead, but that brings different issues. Mainly: which are relevant to the user and which should be ignored? That’s why I have to update the ignore list now.
Yes, that would be great! See above for details: File Browser support and feedback thread - #35 by ichthyosaurus
@Bohdan already sent me a log with tons of mount points, but @Seven.of.nine mentioned a few that didn’t show up in that log. So maybe there are more differences between devices.
I released version 3.0.1 on Openrepos which should hopefully fix this and also sharing on 64bit devices. Let me know if it works
Thank you everyone for your feedback!
The File Browser is making very good and professional progress! Thumbs up!
And a very very big Thank you!
