Strange behavior when opening "Recently" shorcut and then the app

[sguinetti]

Describe the bug This process only consists of two steps, first "Recently" is opened and then the app. The Zapping mode must be activated. After that, two cases of strange behavior happen (the app must be closed first ):

• If the stream remains in a floating window, it will appear inside the floating window when the app is opened normally. You need to press the full screen icon to access and fix the problem. (1).
• If the stream is opened in full screen, the home button is pressed and then the app is pressed normally, the stream runs in the background. To stop the active stream, it is necessary to select another stream or exit the app. (2).

To Reproduce Steps to reproduce the behavior (1):

1. Go to launcher
2. Click on "Recently" (can be accessed as an independent shorcut from the launcher)
3. Then, go to launcher again.
4. Click on the app as usual.

For the next behavior (2):

1. Go to launcher
2. Click on "Recently" (can be accessed as an independent shorcut from the launcher)
3. Click on the full screen icon in the floating window
4. Then, go to launcher again.
5. Click on the app as usual.

Expected behavior In the first behavior, the app is displayed only on the floating screen.

In the second behavior, the app is displayed with the stream sound in the background.

Screenshots Capture for the first behavior. This is the floating window.

Smartphone (please complete the following information):

• Device: Galay A04
  • OS: Android 13
  • Version 1.14.0-alpha11 (app)

Additional context These tests work with Zapping mode activated. The bug also applies when zapping mode is disabled, but behavior 2 is very likely to happen.

[sguinetti]

The problem continues in beta-03 (from 1.14 version). I also perceive the audio in the background.

[sguinetti]

Again, the behavior continues in beta-10. In some cases there is a glitch between the icons in the bottom bar.

[sguinetti]

Since the issue https://github.com/oxyroid/M3UAndroid/issues/135 has fixed via Snapshot, the bug no longer appears.