No longer scrobbling in 1.5.7 (Android 9)

[Thorarin]

I'm using Pulsar as a music player. My last scrobble was on February 4th 2019. Pulsar hasn't updated for a few weeks, so I suspect it has something to do with the update that was released to te store on February 3rd (version reads 1.5.7).

Pulsar is detected and scrobbling for it is enabled.
Android 9 on a Samsung S9+.

Copy to clipboard gives "no current song available" and the local cache stays empty. I can't find any diagnostic information to share with you.

[nguyenmq]

I just wanted to +1 this issue because I'm experiencing the same problem on my S9 after upgrading to Android 9. I also use Pulsar as my music player.

Additionally, after reinstalling Simple Scrobbler, there are no music apps detected.

[a-r-db]

Preferred Feature Format

• Request for Feature: (Super cool awesome scrobble perfection)
• Reason: (Life is music)

Preferred Issue Format

• Phone Model: (Samsung S10)
• Android Version: (9)
• SLS Version: (5.3)
• Music App(s) In Use: (ex. YT Music, Spotify)
• Detected Music Apps(s): (List what apps SLS detected)
• Enabled Options: (List what options you have enabled)
• Issue: (Description of What The Issue Is)
• Parameters: (ex. When, Where, Why & How The Issue Occurs)

[a-r-db]

I am using Android 9 right now.
It could be an issue with your options.

[Thorarin]

It happens with all the default options.

I deleted all app data, logged back into Last.fm. Then I play something in both Pulsar and Google Play Music, but the list of detected apps stays empty, like @nguyenmq described.

[a-r-db]

It has to do with Power Optimization being enabled.
Please try enabling "OnGoing" and "Phone notifications" in your Options please.
Android 9 is a little bit different than previous Android versions.

[Thorarin]

I've just enabled both options, but there is no change in behavior. Still no apps detected.

[a-r-db]

Well I am going to post a merge soon.
The README.md will have a discord chat room we can talk.
Also there is a Gitter chat room on the README.md
I cannot diagnose remotely, all we have are words to discuss the issue.
This is very strange behavior. I will do my best to look into it.

[a-r-db]

@Thorarin
Is there a chance this is what happened #451 ??

[Thorarin]

@a93-39a sounds like it might be the same problem.

Perhaps I can find some time to do some debugging, but my experience with Android development is very limited, so I can't make any promises.

[a-r-db]

No. That's fine, I can probably review the code and discern the issue.
I'll try to recreate the problem myself.

[a-r-db]

Seems to be some kind of SQLite issue.
This is a much older piece of code if I'm not mistaken.

I can send a trial version and it will be in .apk (and not a signed version) format so you would need to uninstall the current version.
I can send you a copy of a potential fix if you like.
Sounds good?

[Thorarin]

Sure, there should be contact details in my profile if needed.

[a-r-db]

We have a missing close database here
Can cause database corruption.
Most likely you should be able to clear the cache and the app should work again.
You will need to re-login after clearing the cache.

[a-r-db]

Hello friend.
#479
Please see the build pre-release for information on trying the newest android .apk