intergalacticmonkey

This would be really great. There's no need to reinvent the wheel, either: https://askubuntu.com/a/1368911, https://specifications.freedesktop.org/thumbnail-spec/thumbnail-spec-latest.html Thanks to this awesome spec, all you have to do is parse the thumbnailer entries...

Fixes this error when trying to build: ``` > Task :libpdfviewer:app:mergeReleaseResources > Task :libpdfviewer:app:compileReleaseKotlin 57 actionable tasks: 10 executed, 47 up-to-date Configuration cache entry reused. onGraph.java:318) at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.lambda$execute$0(DefaultTaskExecutionGraph.java:314) at org.gradle.internal.operations.CurrentBuildOperationRef.with(CurrentBuildOperationRef.java:80)...

gocryptfs volumes on USB drives use the same `/mnt/media_rw` path: Also, I should've probably mentioned this before, but CryFS volumes work fine on internal storage.

Getting this error when trying to build the app to test potential fixes :( ``` $ ./gradlew assembleRelease Calculating task graph as no configuration cache is available for tasks: assembleRelease...

Submitted a tiny PR to fix a build error I was having: https://github.com/hardcore-sushi/DroidFS/pull/282 But now I'm having this and I'm not sure how to fix it. It's a long one...

> Did you create the CryFS volume with DroidFS or with the desktop cryfs program? DroidFS. > Does something differ if you move the volume in a sub-directory on your...

> Which is strange. Can you check that the archive file at `app/libcryfs/vendor/boost/Boost-for-Android/boost_1_77_0.tar.bz2` seems valid? Indeed, the sha256 of the file didn't match the expected hash. I re-downloaded it. Weird.

Went ahead and spun this off into a new issue since it was polluting this one.

Got some more details to share: I tried opening a CryFS volume off a USB drive on my Pixel's stock ROM just to make sure it wasn't a GrapheneOS issue....

> What's the filesystem of your USB drive? I tried both exFAT and FAT32.