hardcore-sushi
Hi i have vault not opening after forced closing (app), unknown error code: 0
I accidentally did this and after entering the correct password I get this error… and I had almost full occupancy of space in my phone: less than 100mb remained free… (I then purged enough of it, in an attempt to rebuild) used cryfs… can't remember what version… like xchacha20-poly1350… when creating a copy in internal storage (inside droidfs) all 8000+ files were transferred… along with the error.
Version 2.1.2, android 12, miui…
———
attempt... create a new partition... failed incorrectly. I created a file in the new partition, closed droidfs completely... in explorer in the folder for the new partition there are no new files except cryfs.config... reopened the application... no new partition... create again, with the same name... error 0... same... problem worse... in the application... bad.....
The volume may have been corrupted. It would help if you could show your logcat. Do you believe it could be similar to this issue?
Can the original cryfs program open your volume?
reinstalling helped. Fix your buggy app.
please read it again. @hardcore-sushi
It would help if you could show your logcat.
I didn't see anything. I looked. Nothing to see.
I checked. It happens when my memory goes negative. The problem is solved by erasing all data. Enough information for your own test, to identify the problem, to fix it. I'm waiting; it's causing a lot of inconvenience. @hardcore-sushi
I cannot help you if you don't provide the information I requested. What do you mean exactly by " when my memory goes negative"?
The problem is solved by erasing all data
Do you mean deleting the app data or the volume?
I cannot help you if you don't provide the information I requested. What do you mean exactly by " when my memory goes negative"?
This means that all of my 256gb were completely filled with various files, and my attempt to fill them even more is causing errors. During this state, when the file manager shows that there are zero bytes free at the moment, I go into the application, start editing some file, like txt, adding usually a lot of text, save and exit. then something happens, probably the application crashes. When I enter the application next time, when I try to open any volumes I get error 0. This is absolutely exactly what happens to me.
The problem is solved by erasing all data
Do you mean deleting the app data or the volume?
erasing all application data without deleting the application.
this is fixed, it doesn't happen again when clearing enough memory through some excess file cleaner app.
@hardcore-sushi
According to the information you provided, it seems that the volume and its state saved in DroidFS were out of sync. It's something that can be expected when you run out of space.
If you want to help the project, you can share your logcat when the app crashes or when you try to open a desynchronized volume. Maybe this will reveal some unknown bugs.
I've been looking. I couldn't find how, where. 3 applications used @hardcore-sushi