Scrobbling issue

[Cale]

Hey,
My last.fm profile is connected in my subsonic settings. Scrobbling works fine if I use the browser to access my music, but through the Android app only a few songs scrobble from each album I listen to. They are all tagged correctly. If I listen to the same album through the browser, all tracks will scrobble. I tried unlinking and relinking my last.fm account, as well as unchecking and rechecking the setting to allow scrobbling in the Android app, the problem persists.
Help would be greatly appreciated.

[Cale]

I read the thread about asking for help so I will add information.

I believe I have already described the problem and what troubleshooting steps I have taken.
I am using a Huawei Mate 20 Pro running Android 11.0.0.162. When accessing my subsonic server through the browser, I was using Firefox 100.1.1 fir Android. The app I am using to stream from the server is the official Subsonic app, I cannot find the build number.
I am using Subsonic Premium, version 6.1.6 (build 0cfa60) – November 10, 2019.
Server: jetty-6.1.x, java 1.8.0_152, HSQLDB, Windows 10 (101.5 MB / 145.0 MB)
I am using a Windows 10 laptop.

I can't do the other things at the moment but if needed I will reply with them.

[J_T_W]

I'll preface by saying that I do not have a full understanding of the last.fm/scrobble mechanics via the Subsonic API (short of what you can read via the API documentation), but here is my general understanding. No application that scrobbles to last.fm should be reporting until it has actively played around 50% of the payload. This keeps scrobbles from happening as you advance through a playlist, or skip around. When you are listening via a browser, the Subsonic server itself is the rendering application and is thus responsible for keeping track of how much has been played, and reporting to last.fm. When you use an app, you are using the Subsonic API. Subsonic is delivering the payload as data to the app, not as a stream. The app itself is therefore responsible for queuing, playing, bookmarking, etc. the payload. When the app decides the playback has hit the required playback percentage, it then sends a request back your server via the API to scrobble.

At this point, Subsonic and the "Subsonic" app, are abandonware. Neither are open source, there is no development, and there is no developer support. If you continue with Subsonic as your back-end, you might try another app that has active support and development. No guarantee that will fix your issue, but at least might rule out some things if the other app works and the "official" one doesn't.

You might also consider moving off of the Subsonic server to a newer implementation. Both below suggestions run on multiple platforms, I'm a Windows guy so some of my supplemental info isn't as useful to non-Windows users.

If you're looking for a very lateral move, consider Airsonic Advanced https://github.com/airsonic-advanced/airsonic-advanced - It is in active development with frequent snapshot updates https://github.com/airsonic-advanced/airsonic-advanced/releases . Same feature set as Subsonic (API, Sonos, etc.) with updated code. As it is open source, you also get all the features Subsonic Premium gives you, but for free (see my last line). Minimal effort for installation (latest Java installed, then a command line shortcut to the war file - upgrades even easier with just a fast war file change).

If you're really more API focused, and looking just for a music streaming service (app over browser), you might consider moving off the Subsonic family of servers altogether. Check out Navidrome https://www.navidrome.org/ . That product is primarily to supply the API with a completely new back-end, and refocuses to just support audio (no video, podcast, internet radio, etc.). There is not yet built in support for Sonos, but you can find easy linking with something like Bonob https://github.com/simojenki/bonob. As with Airsonic Advanced, no subscription or fee to access the API. Navidrome does have a simplified web UI if desired.

Both products will need you to come up with your own DDNS solution for external access. Both support running as a service with something like NSSM https://nssm.cc/, and IIS works great as a reverse proxy if you wish to run them as SSL. As both also use the Subsonic API, your app of choice is compatible with these other offerings.

[Cale]

I'll preface by saying that I do not have a full understanding of the last.fm/scrobble mechanics via the Subsonic API (short of what you can read via the API documentation), but here is my general understanding. No application that scrobbles to last.fm should be reporting until it has actively played around 50% of the payload. This keeps scrobbles from happening as you advance through a playlist, or skip around. When you are listening via a browser, the Subsonic server itself is the rendering application and is thus responsible for keeping track of how much has been played, and reporting to last.fm. When you use an app, you are using the Subsonic API. Subsonic is delivering the payload as data to the app, not as a stream. The app itself is therefore responsible for queuing, playing, bookmarking, etc. the payload. When the app decides the playback has hit the required playback percentage, it then sends a request back your server via the API to scrobble.

At this point, Subsonic and the "Subsonic" app, are abandonware. Neither are open source, there is no development, and there is no developer support. If you continue with Subsonic as your back-end, you might try another app that has active support and development. No guarantee that will fix your issue, but at least might rule out some things if the other app works and the "official" one doesn't.

You might also consider moving off of the Subsonic server to a newer implementation. Both below suggestions run on multiple platforms, I'm a Windows guy so some of my supplemental info isn't as useful to non-Windows users.

If you're looking for a very lateral move, consider Airsonic Advanced https://github.com/airsonic-advanced/airsonic-advanced - It is in active development with frequent snapshot updates https://github.com/airsonic-advanced/airsonic-advanced/releases . Same feature set as Subsonic (API, Sonos, etc.) with updated code. As it is open source, you also get all the features Subsonic Premium gives you, but for free (see my last line). Minimal effort for installation (latest Java installed, then a command line shortcut to the war file - upgrades even easier with just a fast war file change).

If you're really more API focused, and looking just for a music streaming service (app over browser), you might consider moving off the Subsonic family of servers altogether. Check out Navidrome https://www.navidrome.org/ . That product is primarily to supply the API with a completely new back-end, and refocuses to just support audio (no video, podcast, internet radio, etc.). There is not yet built in support for Sonos, but you can find easy linking with something like Bonob https://github.com/simojenki/bonob. As with Airsonic Advanced, no subscription or fee to access the API. Navidrome does have a simplified web UI if desired.

Both products will need you to come up with your own DDNS solution for external access. Both support running as a service with something like NSSM https://nssm.cc/, and IIS works great as a reverse proxy if you wish to run them as SSL. As both also use the Subsonic API, your app of choice is compatible with these other offerings.

Thanks for the response, I'll have to go through that and try to make sense of it as best I can because I'm a bit of a noob. Appreciate the help though.