#8 Critical Bug in 7.0: Filesystem inaccessible

[Weirdalsuperfan]

Thanks for addressing my previous tickets. Your fixes from ticket #5 have been a lifesaver.
I'm on 7.0 (x86 version) using an emulated Google Pixel 2 with Genymotion on Windows 10. I have pretty much just OCR Manga Reader on my Android box.

First I just want to say that I somehow managed to spent 5 hours trying to fix this today.

I don't know if I only just noticed this bug because I haven't been reading manga much lately, or if this bug was the reason I stopped reading manga, but in any case, I'm unable to use the app's Open function to navigate to the root directly in order to see my files, whether that be EPWINGs or manga. The files I want to get at are mounted at mnt/shared, and it seems like it's not easy or perhaps possible to change this mount point with my VM - in any case, unless I have full control over where I put my files, I currently can't view them with OCR Manga Reader even though I can with programs like EBPocket, or a sophisticated file explorer. Images attached (likely cause in bold at the end of this ticket, but I'm sure you already know the cause).

If you look at the attached images, you'll notice that in the "Open" menu in the app, as you cycle from Reader_7.0_a all the way through Reader_7.0_e, even though you keep going up to the parent directory, the folders start to cycle from: being inside the "0" folder (which seems to be /mnt/sdcard or just /sdcard, with a bunch of folders like acv, Alarms, Android, DCIM, etc.), to "emulated" (which appears to contain the "0" folder), to "storage," which contains the emulated and the self folders. Clicking on self, as it is empty on my system, shows it is empty. Clicking on emulated shows the 0 folder, and inside that is, again, all the folders in /sdcard. The loop seems to be a combination of this /sdcard folder being shown as what's inside emulated, and that, clicking "Back to parent folder" while in "storage" (i.e. while you can see the emulated and self folders) leads right back into the /sdcard directory with all those acd, Android, DCIM, etc. folders . In addition, As you can see in my screenshots of my actual filesystem, emulated and self have nothing in them.

#Actually, I guess whether emulated appears to contain sdcard or storage or nothing depends on what file manager you use.

I think the problem is maybe that even though the current directory is "storage," going up (which should lead to the root folder) leads to the sd card ("external storage")? I think maybe you intended to go to storage FROM the root folder, but instead it's going there before it even reaches root

Now, as you can see in RegularFileExplorer.png, I can't see beyond this /sdcard filesystem normally either. I need to use a more advanced file explorer like Amaze in order to properly navigate (although again, EBPocket traverses my directory structure just fine). You can see how /sdcard shows up under both root and /mnt in my directory structure for some reason. The pictures DirectoryStructure1.png through DirectoryStructure6.png show the relevant parts of my directory structure, starting with the mnt folder I'd like to be able to view (DirectoryStructure1.png). DirectoryStructure5.png shows that my emulated storage is empty.

I tried placing a blank .txt file under emulated to see if that changed anything, but it didn't.

**Notably, this bug does not exist in version 6.6 (I cloned my VM and replaced 7.0 with 6.6 just now), so I think it's related to at least one of these two changes in 7.0:
-If no items were found under "/storage/emulated", a directory will be added that represents the external storage folder.
-Pressing "Back to parent folder" when current directory is root will now navigate to the external storage folder.
**

As it stands, I am currently unable to read anything that isn't under Recent, since although the app can access files (including my EPWINGs), I can't navigate to select them anymore through Open. I can't reconfigure my EPWINGs either, and now I have to downgrade to 6.6 in order to use the app, losing access to all the features you so kindly created from my previous tickets. I imagine the only reason I even have files in my Recent tab is because either they were there when I upgraded, or when I upgraded I wasn't looking at the storage or emulated directory. It seems like navigating away from root, or perhaps even from mnt, is a death trap.

Following the above logic, one temporary fix I just tried that actually worked (btw I tried this on a clone, not on the VM I want to use) is to install an older version of the app and then to navigate to the folder of interest, and then to install the new version again. This only works because the app saves the folder it was looking at when you last used "Open file." The only problem with this is that I need to uninstall v 7.0 to downgrade, so I need to save my Recent history, etc., but I don't even know where those files are stored.

Sorry for the long post. I'm sure it wasn't all necessary. Hope it can be fixed soon.

[Weirdalsuperfan]

Basically, the bug is that once you navigate to storage, you are trapped there.

[cb4960]

Thanks for the detailed report, I'll take a look.

[Weirdalsuperfan]

Were you ever able to figure out the problem? I feel like an easy patch could be an option to allow you to save you path or something, so that if you accidentally navigate too far up and fall into this trap, you can reset back to where you were. Kind of hacky, but if it works, I'd be happy.

[cb4960]

I just uploaded version 7.1 which may help to solve the issue. I don't have permissions to display root with the SDK version I'm building against, and I don't have any rooted devices to test with, but I was able to add a "mnt" folder (which maps to "/mnt") and a "shared" folder (which maps to "/mnt/shared"). They should be displayed in the folder shown in Reader_7.0_d.png. On my newer devices I can see the "mnt" folder, but on my older devices I cannot. Let me know if that helps.

[Weirdalsuperfan]

It works! Thanks for your continued efforts. You are truly the unsung hero of the Japanese learner community.