Fix drawer category views not refreshing after file operations

[geoffreysisco]

Description

Drawer category views did not consistently reflect filesystem changes
after file operations such as create and delete.

In some categories (Documents, APKs, Recent Files), queries could include
entries from Amaze's trash directory (.AmazeData), causing deleted files
to remain visible and allowing repeated deletes to create duplicate
Trash Bin entries.

This PR addresses the issue by:

• forcing reload for drawer category views to ensure fresh data after operations
• filtering Amaze trash paths from category queries

This ensures drawer views correctly reflect the current filesystem state
across all categories.

Issue tracker

Fixes #4558

Automatic tests

• Added test cases

Manual tests

• Done

• Device: Pixel 9 Pro (emulator)

• OS: Android 16.0

• Rooted: No

• Version: 3.11.2

Verified in:

• Documents
• APKs
• Recent Files
• Images
• Videos
• Audio

Scenarios tested:

• Delete file → removed from drawer view
• Repeat delete → not possible (item is no longer visible after deletion)

Before/after reproduction videos:

Before

before.mp4

After

after.mp4

Build tasks success

Successfully running the following tasks locally:

• ./gradlew assembleDebug
• ./gradlew spotlessCheck

[VishnuSanal]

hi @geoffreysisco great work, thanks for contributing to amaze! :) I have some comments, please address them, and we are good to go, tahnsk!

• also, can you pls add the trash directory check to all quick access menu listings too? thanks!

[VishnuSanal]

can we pls use AppConfig.TRASH_BIN_BASE_PATH here?

[geoffreysisco]

TRASH_BIN_BASE_PATH is currently private in AppConfig, so it’s not accessible here.

I can expose it via a getter (e.g. AppConfig.getTrashBinBasePath()) and use that instead — let me know if you’d prefer a different approach.

[VishnuSanal]

hmm, nice, but I think we can add this selection to the cursor itself like below. WDYT?

    final String[] projection = {MediaStore.Files.FileColumns.DATA};
    final String selection = MediaStore.Files.FileColumns.DATA + " NOT LIKE ?";
    final String[] selectionArgs = new String[] {AppConfig.TRASH_BIN_BASE_PATH + "%"};
    Cursor cursor =
        context
            .getContentResolver()
            .query(MediaStore.Files.getContentUri("external"), projection, selection, selectionArgs, null);

[geoffreysisco]

I agree, that makes sense. I’ll move the trash exclusion into the query instead of filtering in the loop.

[geoffreysisco]

Thanks for the review.

I’ve started addressing the comments.

Documents, APKs, and Recent files now exclude the trash directory at query time instead of filtering in the loop.

For Images/Videos/Audio, the stale delete behavior is already handled via the forceReload change in MainFragment for OpenMode.CUSTOM, but they still go through listMediaCommon() for querying.

When you mentioned “all quick access menu listings,” should the trash-path exclusion also be applied in listMediaCommon() for Images/Videos/Audio, or only to the MediaStore.Files-based listings touched here (Documents/APKs/Recent files)?