Please describe the problem you are having in as much detail as possible:
The application can start or restart by itself. It could be related to https://github.com/LISTEN-moe/android-app/issues/51 but I opened that one instead of commenting there as it somehow got worse with versions 6.x
I could see Listen.moe related logs about the current song in adb logcat before, but never bothered enough to report. Now it also have the application appearing in the notification as if it was paused after being used when it wasn't even launched once since reboot. IT appears as running, which is more than a background service and wasn't the case before 6.x.
Pre 6.x it already had a background service, which it already shouldn't have if user didn't run the application at all. The direct consequence of that, for which I can open a new issue if needed, is the data usage on both mobile carrier and Wi-Fi, easily amounting to more than 1GB/month in months the application wasn't even used once because of fetching metadata (currently playing song & probably also covers, even pre-6.x when the notification wasn't here, so basically, the application have a service fetching those permanently for no reason).
App version: 6.0.2
Android version: Oreo (8.0)
Device: Xperia XZ
EDIT: Also, when the notification's up but player's not playing, it's possible to discard the notification by sliding it… but this'll actually let the background service up.
Please describe the problem you are having in as much detail as possible:
The application can start or restart by itself. It could be related to https://github.com/LISTEN-moe/android-app/issues/51 but I opened that one instead of commenting there as it somehow got worse with versions 6.x
I could see Listen.moe related logs about the current song in
adb logcatbefore, but never bothered enough to report. Now it also have the application appearing in the notification as if it was paused after being used when it wasn't even launched once since reboot. IT appears as running, which is more than a background service and wasn't the case before 6.x.Pre 6.x it already had a background service, which it already shouldn't have if user didn't run the application at all. The direct consequence of that, for which I can open a new issue if needed, is the data usage on both mobile carrier and Wi-Fi, easily amounting to more than 1GB/month in months the application wasn't even used once because of fetching metadata (currently playing song & probably also covers, even pre-6.x when the notification wasn't here, so basically, the application have a service fetching those permanently for no reason).
EDIT: Also, when the notification's up but player's not playing, it's possible to discard the notification by sliding it… but this'll actually let the background service up.