OnePlus gaming mode gets triggered when using the app

[PhilC813]

Checklist

• I can reproduce the bug with the latest version given here.
• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected app version

1.1.1

Affected Android/Custom ROM version

Android 15

Affected device model

OnePlus 13

How did you install the app?

GitHub releases

Steps to reproduce the bug

1. Open the app

Expected behavior

The OnePlus gaming mode doesn't get tripped

Actual behavior

The OnePlus gaming mode gets tripped as it seems to believe that the app is a game

Screenshots/Screen recordings

No response

Additional information

Hey! Awesome to see a first release of this project. I gave it a quick try and so I'm just reporting this small bug. Let me know if you need any logs to fix this.

[Pecacheu]

Thanks for the bug report!

Can you test if it happens on the base Fossify fork of File Manager (latest version should be v1.1.0). That way I know if it's a problem with the app in general getting flagged or something about this fork (perhaps a change I made in AndroidManifest convinces it that this is a game somehow?)

[PhilC813]

Good thought of making me try this. It's a new phone and I hadn't yet installed Fossify's app. Turns out that Fossify's app also triggers the gaming mode, so maybe I should open the issue on their repo? I have no other app installed that are incorrectly flagged like this one.

[Pecacheu]

Gotcha. I'd recommend opening it on the main repo then. I am syncing changes every so often, so if it gets fixed there it should be fixed here on the NAS-supported fork too soon enough.

[PhilC813]

Gotcha. I'd recommend opening it on the main repo then. I am syncing changes every so often, so if it gets fixed there it should be fixed here on the NAS-supported fork too soon enough.

Done!
Many thanks, and keep up the amazing work!