bug report by remfan1994

[remfan1994]

Title: Compatibility issues on Android 13: notifications, open command/config‑file handling, storage data inaccuracies

Environment:

• App: TUI‑ConsoleLauncher (aka T‑UI)
• Version: probably 6.15 version currently on f-droid
• Device: cloud c8
• Android version: 13
• Installed via: apk downloaded from f-droid

Description:
While using T‑UI on Android 13, I encountered several issues that affect usability:

1. Notifications

   • Expected: T‑UI notifications should appear and update normally (including when enabled in config).
   • Actual: Notifications often fail to show or update. The notification permission (POST_NOTIFICATIONS) and Android 13 changes may not be handled fully by the app.

2. File “open” / Config file handling

   • Expected: Using the open command (and derived features) in T‑UI should open the target file directly. For example, config ‑open file.xml should open the file in the internal editor or TUIXT as documented. Also, the app TUIXT (or the T‑UI internal handler) should catch the config ‑file command by default and be listed as a handler, rather than always triggering Android’s “Open with” dialog.
   • Actual: When I run the open command, Android’s “Open with” dialog appears instead of the file being opened directly. TUIXT does not appear as a default handler and is not listed in the “Open with” list (so it cannot be selected). The documented behavior (config ‑open file.xml) is not functioning as expected on Android 13.

3. Storage / Data accuracy

   • Expected: Storage information reported by T‑UI (e.g., used/free space) should match the system metrics and reflect actual values.
   • Actual: Some storage data appears incorrect or inconsistent (for example, free/used space readings don’t align with Android’s storage view). It may be due to changes in Android 13 scoped storage or permission model. This Cloud C8 has 32 GB of total storage and 14 GB are used, yet T-UI displays only 20 GB of storage and 17 GB used.

Steps to reproduce:

1. Install T‑UI on an Android 13 device (with normal permissions).
2. Enable notifications in T‑UI config. Use it, then check whether notifications appear and update.
3. Use the command: config ‑open theme.xml (or other config file) in T‑UI. Observe whether the file opens directly or whether you get the “Open with” dialog.
4. Use a file open command, like open /path/to/file, and see if the intended file opens directly or if Android’s chooser appears.
5. Check storage stats displayed by T‑UI, compare them with Android settings (Storage) to see if they align.

Expected behavior:

• Notifications work normally (show up, update, tappable).
• The open command opens files directly in T‑UI‑managed/editor context, not via Android chooser.
• The config ‑open command is handled internally or lists TUIXT as a handler; TUIXT appears in “Open with”.
• Storage data is accurate and consistent with system metrics.

Actual behavior:

• Notifications missing or inconsistent.
• Calling open triggers Android’s “Open with” dialog instead of direct open; TUIXT not listed.
• config ‑open fails to open as expected; no default internal handler.
• Storage data appears incorrect / inconsistent. Claims 20GB total and 17GB used, when there is 32GB total and 14GB used.

Additional context / notes:

• These issues seem to correlate with Android 13 changes (notification permission, scoped storage, file‑intent behaviors).
• For reference: the “Customize T‑UI” wiki details config ‑open file.xml behavior. :contentReference[oaicite:4]{index=4}

Thank you for your continued work on T‑UI — hope this feedback helps compatibility with newer Android versions.