[MOD][XPOSED] SpotifyAVRCP - Bluetooth track info from Spotify - Xposed Framework Modules

SpotifyAVRCP:
Spotify doesn't send track information via bluetooth, in the past there have been patched versions of Spotify floating around to add media metadata over bluetooth. This is an xposed module that does the same thing, it hooks into an internal track change function and broadcasts a standard android media intent.
The Spotify APK is run through proguard so method names are likely to change - which means this may not work with all versions and future updates could break it - in which case I will try and fix asap and upload a new version.
Requirements:
1) Have Xposed Framework Installed
Instructions to install SpotifyAVRCP:
1) Download & Install SpotifyAVRCP from bintray or in the Xposed Installer Downloads section
2) Enable SpotifyAVRCP in Xposed Installer
3) Restart device
4) Play Music
Changelog
Latest: 1.0.0 Beta - 30/11/13 (Download)
Initial Release
Support for Spotify Version 0.7.3.636
Notes
It seems that this mod might only be useful for bluetooth info on android 4.2.x and below. 4.3 introduces AVRCP support and should handle things properly. However this mod might still be useful if you have other legacy applications which rely on the old broadcasts to get track information - this seems to be the case for both Pebble and Gear smartwatches.
If you're reporting problems, please include the Device, OS Version and end device you're trying to get to work.

---

Works a treat on my Note 3 Now just the album art hahah!
Show me where to deposit beer money for you?

---

ice_prophecy said:
Works a treat Now just the album art hahah!
Show me where to deposit beer money for you?
Click to expand...
Click to collapse
I'll get the album art working and then think about accepting beer money.

---

So just further feedback:
When I said it was working a treat, I only tested it on my Galaxy Gear (which displays Media Information) in the media control centre.
I tried it in my Toyota Altara S (2012) and the media head displays
(No Data) for each field.

---

ice_prophecy said:
I tried it in my Toyota Altara S (2012) and the media head displays
(No Data) for each field.
Click to expand...
Click to collapse
Is there a media player which does work in your Toyota? If so, I can grab it and check which intents its sending. At the moment I'm sending the default android "com.android.music.metachanged" intent which, as far as I understand it, is what the os reads to generate the avrcp data.

---

jbergler said:
Is there a media player which does work in your Toyota? If so, I can grab it and check which intents its sending. At the moment I'm sending the default android "com.android.music.metachanged" intent which, as far as I understand it, is what the os reads to generate the avrcp data.
Click to expand...
Click to collapse
Yes, the default android music player. I'm running the stock Samsung TouchWiz ROM for Note 3 n9005:
Music 6.0.1
I've also attached the APK made from a TitaniumBackup View attachment com.sec.android.app.music-58e673dbcbf733750a580d16571af5d4.apk
I'll try re coupling the devices again in the meantime

---

ice_prophecy said:
Yes, the default android music player. I'm running the stock Samsung TouchWiz ROM for Note 3 n9005
Click to expand...
Click to collapse
Out of curiosity does it support album art in the car? Or just to the gear?

---

jbergler said:
Out of curiosity does it support album art in the car? Or just to the gear?
Click to expand...
Click to collapse
Yes, when using the default music app:
I am able to see the album art and all tag information on both the Car and on the Galaxy Gear. (Edit: Give me 2 seconds to run out and double check)
I am only able to see tag information in the Car. The Gear however displays album art and tag information.
Annoyingly, the car will always autostart the Default Music app over Spotify.... it brings annoyance to no end...
There is one unrelated caveat, which is probably more related to the car's shortcomings is the lack of Unicode-8 for foreign characters. The Gear does not have this issue.

---

ice_prophecy said:
I've also attached the APK made from a TitaniumBackup View attachment 2423632
Click to expand...
Click to collapse
You're on an odexed rom, can you grab the Music.odex from the app directory on your phone as well?
Actually nevermind - I can't deodex it without grabbing the whole rom, what build are you running, ill download a deodexed copy of your rom and grab the apk.

---

As requested:
View attachment com.sec.android.app.music-5fa6d510e8cc2d8c98a6c1947cf90481.odex.gz
EDIT: I'm running a completely stock Samsung Note 3 Rom. I've only rooted it, but have never flashed any recovery/rom.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

---

Not working for me either using Nexus 4 with 4.4. As soon as my device connects is says "Nexus 4" and after that it's just empty. If I launch Google Play music it is sending metadata perfectly and if I switch to Spotify after that Spotify is also sending it perfectly. I had this exact behaciour before installing your module or Metafy or the modified Spotify app.
I also tried disabling Google Play music but that doesnt seem to have any effect except for that I cannot use mentioned workaround anymore. If theres anything I can do to help please let me knoe.

---

Flaiker said:
Not working for me either using Nexus 4 with 4.4. As soon as my device connects is says "Nexus 4" and after that it's just empty. If I launch Google Play music it is sending metadata perfectly and if I switch to Spotify after that Spotify is also sending it perfectly. I had this exact behaciour before installing your module or Metafy or the modified Spotify app.
I also tried disabling Google Play music but that doesnt seem to have any effect except for that I cannot use mentioned workaround anymore. If theres anything I can do to help please let me knoe.
Click to expand...
Click to collapse
So launching google play music means that spotify metadata comes through properly? Can you try and force stop google play music once the spotify metadata is working and see if it continues to work?

---

jbergler said:
So launching google play music means that spotify metadata comes through properly? Can you try and force stop google play music once the spotify metadata is working and see if it continues to work?
Click to expand...
Click to collapse
Sure. To clarify: Launch spotify -> play song -> no metadata -> launch gplay music -> start playing a song (will pause spotify) -> metadata of that song is dislayed -> switch back to spotify, unpause -> gplay music pauses -> metadata displayed is now the spotify song and will update accordingly when the song changes
Problem is that you need to do this trick again anytime you lose bluetooth connection.
-------------------------------
Tested it, still works after force closing play music and even deactivating it. It seems to me as if Google Play music initializes something that is necessary for metadata transfer.

---

Flaiker said:
Tested it, still works after force closing play music and even deactivating it. It seems to me as if Google Play music initializes something that is necessary for metadata transfer.
Click to expand...
Click to collapse
Ok, thats super strange but at least it gives us something to work with. To clarify, what the xposed mod currently does is inject the metachanged intent so that a 'standard' intent shares the info systemwide - which seems to trigger things like smartwatches getting their metadata. I didn't realise the previous patches didn't quite achieve what it was described as.
I've just dredged through the spotify apk and as far as I can tell it initialises everything as it should. Admittedly the android docs on how this stuff is meant to work is rather vague.
Could you test a couple more scenarios for me?
What happens if you just open google play music but don't start playing - does Spotify still send the correct metadata then?
What about other media players, I think PowerAmp supports AVRCP these days, could you test it and see how the behaviour compares to Spotify / Google Play Music?

---

jbergler said:
Ok, thats super strange but at least it gives us something to work with. To clarify, what the xposed mod currently does is inject the metachanged intent so that a 'standard' intent shares the info systemwide - which seems to trigger things like smartwatches getting their metadata. I didn't realise the previous patches didn't quite achieve what it was described as.
I've just dredged through the spotify apk and as far as I can tell it initialises everything as it should. Admittedly the android docs on how this stuff is meant to work is rather vague.
Could you test a couple more scenarios for me?
What happens if you just open google play music but don't start playing - does Spotify still send the correct metadata then?
What about other media players, I think PowerAmp supports AVRCP these days, could you test it and see how the behaviour compares to Spotify / Google Play Music?
Click to expand...
Click to collapse
Just having Google Play Music open or starting it doesnt do anything. I need to start playing a song with it for any metdata transfer to work.
On PowerAmp I have exactly the same behaviour. Doesnt send anything until I play sth in Play music. I even switched some of the settings in the bluetooth section but couldnt get it to work on its own.
Surely the developers of popular music apps who have AVRCP functionality must know about this problem, in he other thread quite a few other people reported the same problematic I have.

---

Flaiker said:
Just having Google Play Music open or starting it doesnt do anything. I need to start playing a song with it for any metdata transfer to work.
On PowerAmp I have exactly the same behaviour. Doesnt send anything until I play sth in Play music. I even switched some of the settings in the bluetooth section but couldnt get it to work on its own.
Surely the developers of popular music apps who have AVRCP functionality must know about this problem, in he other thread quite a few other people reported the same problematic I have.
Click to expand...
Click to collapse
One would assume so, I'll see what I can dig out of the google play music apk but so far its not obvious what might be causing the problem.

---

jbergler said:
One would assume so, I'll see what I can dig out of the google play music apk but so far its not obvious what might be causing the problem.
Click to expand...
Click to collapse
I've been trying to get this fixed for a while now. I even made a Tasker profile that would automate the play music trick but that didnt work all too well either.
If you saw the metafy app in the other thread, that doesnt work either for me, the problem seems to be sending metadata via bluetooth, completely unrelated to spotify. If you have anything you want to have tested that could help solving this please dont hesitate to ask me.

---

Don't work on 4.3 in my S4 neither (stock with root only)
Enviado desde mi GT-N8000 usando Tapatalk 4

---

Not working on Xperia z 4.2 playing through car stereo Bluetooth. Walkman app works fine though.
Enviado desde mi C6603 mediante Tapatalk

---

Works with note 3 and pebble!
Works GREAT with VZW Galaxy Note 3 (stock 4.3 MJ7) and Pebble's stock music controller! Thanks so much!!! Put up a beer link soon!