I know AVRCP 1.3 support is built into Android 4.3, but from what I understand, some OEMs have built it into their phones running Android 4.2.x. At least, there are some user reports in the S4 and HTC One threads suggesting that Samsung and HTC have added it to their 4.2 builds.
Can any Moto X users say whether or not the Moto X supports AVRCP 1.3? I stream audio to my car's stereo over bluetooth, and I really want to keep the metadata flowing. I'm running an Android 4.3 ROM on my Galaxy Nexus, but that phone is starting to show its age. I'm locked into Verizon for coverage reasons, so I'm trying to find a new phone with AVRCP support built-in, since I won't be able to flash ROMs.
reggie14 said:
I know AVRCP 1.3 support is built into Android 4.3, but from what I understand, some OEMs have built it into their phones running Android 4.2.x. At least, there are some user reports in the S4 and HTC One threads suggesting that Samsung and HTC have added it to their 4.2 builds.
Can any Moto X users say whether or not the Moto X supports AVRCP 1.3? I stream audio to my car's stereo over bluetooth, and I really want to keep the metadata flowing. I'm running an Android 4.3 ROM on my Galaxy Nexus, but that phone is starting to show its age. I'm locked into Verizon for coverage reasons, so I'm trying to find a new phone with AVRCP support built-in, since I won't be able to flash ROMs.
Click to expand...
Click to collapse
There is no AVRCP 1.3 support on the Moto X, I was a bit bummed about it as well since my Gnex was rocking 4.3, but I wouldn't let that sway you from this phone, it is really a perfect Gnex replacement. One of the coolest features about Bluetooth music streaming is when you start driving it will automatically start playing music where you left off last time. Anyways, I am sure a 4.3 update will come eventually and AVRCP 1.3 will be there.
reggie14 said:
I know AVRCP 1.3 support is built into Android 4.3, but from what I understand, some OEMs have built it into their phones running Android 4.2.x. At least, there are some user reports in the S4 and HTC One threads suggesting that Samsung and HTC have added it to their 4.2 builds.
Can any Moto X users say whether or not the Moto X supports AVRCP 1.3? I stream audio to my car's stereo over bluetooth, and I really want to keep the metadata flowing. I'm running an Android 4.3 ROM on my Galaxy Nexus, but that phone is starting to show its age. I'm locked into Verizon for coverage reasons, so I'm trying to find a new phone with AVRCP support built-in, since I won't be able to flash ROMs.
Click to expand...
Click to collapse
1.3 = streaming of song track album of title as well as song length etc correct? If so, then yes. I was surprised to see it on the X... after coming from a 4.3 Nexus 4. On a 2011 Subaru Impreza WRX stock head unit.
Hayaku said:
1.3 = streaming of song track album of title as well as song length etc correct? If so, then yes. I was surprised to see it on the X... after coming from a 4.3 Nexus 4. On a 2011 Subaru Impreza WRX stock head unit.
Click to expand...
Click to collapse
Seconded. My aftermarket Sony head unit shows song title and artist. I don't think it's AVRCP 1.3 but something added on maybe my Motorola.
sanatar said:
There is no AVRCP 1.3 support on the Moto X, I was a bit bummed about it as well since my Gnex was rocking 4.3, but I wouldn't let that sway you from this phone, it is really a perfect Gnex replacement. One of the coolest features about Bluetooth music streaming is when you start driving it will automatically start playing music where you left off last time. Anyways, I am sure a 4.3 update will come eventually and AVRCP 1.3 will be there.
Click to expand...
Click to collapse
Hmmm, two yeses and one no. What makes you think it doesn't have AVRCP 1.3?
Add another 'yes'. Meta data streams to my Pioneer head unit just fine. It doesn't work QUITE the same way that my N4 does though. The X shows the Meta data, but also then shows a track #. The Nexus 4 doesn't show a track number.
reggie14 said:
Hmmm, two yeses and one no. What makes you think it doesn't have AVRCP 1.3?
Click to expand...
Click to collapse
Now I am super confused at why mine doesn't work! In the past my Gnex running Bugless Beast, the metadata would show up because that was one of his extras, then I flashed a new rom and it went away. Then recently when I flashed 4.3 it was back again, now with my Moto X no metadata is showing up. Very strange it works for you guys, maybe it's a problem with my head unit. I have a Sony headunit.
banq81991 said:
Seconded. My aftermarket Sony head unit shows song title and artist. I don't think it's AVRCP 1.3 but something added on maybe my Motorola.
Click to expand...
Click to collapse
my sony head unit does NOT show title/artist/song info over bluetooth. my hawai prism w/ cm7 did so i know it works. at least with google music.
what i do get is track number and time elapsed.
sanatar said:
Now I am super confused at why mine doesn't work! In the past my Gnex running Bugless Beast, the metadata would show up because that was one of his extras, then I flashed a new rom and it went away. Then recently when I flashed 4.3 it was back again, now with my Moto X no metadata is showing up. Very strange it works for you guys, maybe it's a problem with my head unit. I have a Sony headunit.
Click to expand...
Click to collapse
Historically, in my experience, Sony has never been good @ meta data. I had a head unit from them back in the day, one of the earlier MP3 playing head units. It couldn't even read the filenames correctly. They always came up just garbled despite the ID3 tags AND filenames being correct. I'd maybe see if there's a firmware update for your head unit?
icase81 said:
Historically, in my experience, Sony has never been good @ meta data. I had a head unit from them back in the day, one of the earlier MP3 playing head units. It couldn't even read the filenames correctly. They always came up just garbled despite the ID3 tags AND filenames being correct. I'd maybe see if there's a firmware update for your head unit?
Click to expand...
Click to collapse
Good call, I have definitely never upgraded the firmware. The strange thing is that it worked perfect with my Gnex on 4.3.... anyways, glad it works for you guys, I will look into my issue.
Related
Hey guys,
I've got a Kenwood KDC-BT945U car stereo and I'm curious what other people's experiences are using the bluetooth for music. For all of you using a bluetooth receiver in the car, when you play music, does the deck display the Song/Artist/Album/etc.? Mine plays fine. I can pause/play, skip forward/back, etc. The only problem is when it comes to actually displaying the information on the car stereo.
Any similar experiences?
Ps. Besides this problem, the deck is a great complement to the phone. If I can get this problem solved, I can stop using the USB altogether.
I was going to post a similar thread about my issues with the KDC-BT945U. Thanks for staring it. Are you running a custom ROM?
Music for me shows no tag info. My main issue is that foryo is a nightmare when it comes to this deck. Both the deck and the nexus has major pairing issues using froyo. I have not tried 2.1 stock or Cyan's 5.0.7, I assume they work fine. I am no expert, but I think it's the new Radio in froyo causing the problem.
Surprisingly, Paul's desire ROM and this deck work very well for me.
Checking the website, there is a Bluetooth compatibility section. They do not list the nexus. I'm hoping for a firmware update for the deck.
I do have a 30gb iPod in the glove box hooked up via the rear USB and it does display track info on the deck.
Yeah. In my infinite wisdom, I bought a ZuneHD rather than an iPod touch. . . The only Kenwood stereo I could find that was compatible with the Zune was like twice the price. Not exactly doable when I'm 28 days away from being a daddy. lol That said, I'm just using a jump drive for the USB. That's been working flawlessly, tags included. If I can figure out how to get the phone to transmit tag info, then I can drop the need to carry an mp3 player (or have a jump drive hooked up) altogether. I love listening to music from the phone while using the navigation, for the sheer fact that it cuts the music off to make announcements. . .just need to get it working right.
Edit. Btw, I an running eViL's latest FroYo. Noir Tri.
Mi|enko said:
Edit. Btw, I an running eViL's latest FroYo. Noir Tri.
Click to expand...
Click to collapse
Can you tell me what firmware your deck is running? Mines 3.11
Also can you tell me what Radio you are running? Mines 32.36.00.28U_4.06.00.12_7
Thank you
verboten said:
Can you tell me what firmware your deck is running? Mines 3.11
Also can you tell me what Radio you are running? Mines 32.36.00.28U_4.06.00.12_7
Thank you
Click to expand...
Click to collapse
Same as you. Latest FroYo radio and 3.11 on the deck. Have since wiped and flashed Evil's latest Noir IV (FRF83 based) and still the same results. I have a 16 gig jump drive in there, so I have plenty of music. . . it just kind of sucks for the navigation piece. Phone calls are fine, because they'll interrupt any of the inputs. . . nav doesn't have that luxury. :-\
Thank you for the reply,
I have switch over to Kang-o-rama 0.9 Final (Froyo FRF83). My BT registering is a bit better, but nothing like Paul's R22 desire ROM was. With Paul's ROM, I was able to just keep my phone in my pocket at all times and when I started my car, as long as BT was turned on, my phone and deck synced every time. Now i'm lucky if it syncs at all. I have to constantly re-pair with the phone, and even that is very flaky.
Also, During audio, only 'BT audio' is displayed, no tags.
verboten said:
Thank you for the reply,
I have switch over to Kang-o-rama 0.9 Final (Froyo FRF83). My BT registering is a bit better, but nothing like Paul's R22 desire ROM was. With Paul's ROM, I was able to just keep my phone in my pocket at all times and when I started my car, as long as BT was turned on, my phone and deck synced every time. Now i'm lucky if it syncs at all. I have to constantly re-pair with the phone, and even that is very flaky.
Also, During audio, only 'BT audio' is displayed, no tags.
Click to expand...
Click to collapse
Did the desire rom display tag info? I have to repair all the time too. . .might be worth switching just for that.
Mi|enko said:
Did the desire rom display tag info? I have to repair all the time too. . .might be worth switching just for that.
Click to expand...
Click to collapse
Unfortunately, the desire ROM does not display tag info.
Unfortunately I'm pretty sure that sending the tag info for songs over Bluetooth isn't currently possible. It's a limitation in Bluetooth though, not your head unit.
I have a stock Nexus One and a Kenwood KDC-X994 and after trying unsuccessfully to figure out how to get my song info to show on the head unit I contacted Kenwood about it. They informed me it wasn't currently possible to do this via Bluetooth and that it was Bluetooth that had the limitation, not my head unit.
On a side note, ever since upgrading to Froyo (stock) my phone will only stream music via BT to my head unit with the stock music app, and this is very aggravating. Seems to be an issue with Froyo from seeing other user posts about this topic. I sincerely hope Google fixes this ASAP!
ranphi said:
Unfortunately I'm pretty sure that sending the tag info for songs over Bluetooth isn't currently possible. It's a limitation in Bluetooth though, not your head unit.
Click to expand...
Click to collapse
not true, my blackberry storm 2 sends all the song info to my kenwood kdc-bt945u. so the problem is in the phone software not the hu or bluetooth
where are we at on this? im curious as i should have an eris by friday and want to know how compatible it will be with my head unit
Huh. Interesting. I guess Kenwood was wrong, then.
NFrank89 said:
not true, my blackberry storm 2 sends all the song info to my kenwood kdc-bt945u. so the problem is in the phone software not the hu or bluetooth
where are we at on this? im curious as i should have an eris by friday and want to know how compatible it will be with my head unit
Click to expand...
Click to collapse
kenwood kind of pisses me off, i dealt with them a lot after i purchased the hd radio unit for the 945u. i was trying to find out why you cannot access the equalizer or any audio settings in hd radio mode (extremely annoying) he said you just cant. i wanted a more detailed explaination and he just made some bs up to get me off the phone. but yeah, just so you guys know, if you get the hd radio for you head unit you wont be able to adjust the terb/bass or anything on the hd radio src. all you get it the direct signal.
but does anyone know if this song info problem has been fixed? in an update or anything?
I didn't want to bog down any of the various ROM threads with this, but I've noticed some odd behavior when pairing my D4 to my JVC head unit.
With stock Moto ICS and Eclipse 1.3.2 (still ICS), when paired to the HU, I can voice dial and control Pandora. I can sort-of control Google Music, but it won't display the ID3 tag info for any of the music, and although I can skip tracks it never recognizes anything but the player being stopped.
Now, if I go to Hashcode's WIP unofficial CM10 port, the HU control of GMusic works completely (as does all the Pandora control). I get ID3 tags, it recognizes when the player is stopped, playing, paused, etc. Of course, the current state of the CM10 port has the same BT issues with the phone side of things that the D3 had early in its development.
So now I'm wondering why there's the difference with the GMusic control/ID3 info. Does anyone know if it's something in the ICS/JB framework, or is it something related to the BT stack? Or perhaps something else entirely?
edit: So it turns out stock ROMs from pretty much every manufacturer (maybe all of them) do not support AVRCP 1.3+, but CyanogenMod does. I'm currently loading Hashcode's stock CM9 to see how it fares.
edit 2: Apparently CM9 has the same BT phone issues as CM10, I hadn't realized that. I guess I'm stuck with stock/Eclipse with no tag info until CM10 matures a bit more.
It is amazing just how many problems that this Droid 4 has when it comes to Bluetooth, and everything else. I don't understand how they could release these phones with so many issues. I see it more of a false advertising deal that just goes unchecked. I have major issues with bluetooth, if I get call waiting it resets my bluetooth connection (to where I hear my BT headset replay its boot up music). Half the time I have to pair the headset, then turn off the BT section and then turn it on again just for it to work. I am also constantly repairing the headsets as well. My two motorcycle headsets also also not happy and do not play well with the Droid 4. These headsets all seem to work fine with my older phones, T-Mobile G1, G2, G2x, and my Acer Iconia A500 tablet as well.
Here are my Headsets:
Jawbone Icon(Current Edition sold at Costco)
Parrot SK4000
Cardo Scala Rider FM
Not sure if my list helps any with research going forward, but it is something.
Tom
Yeah, BT performance is all over the place between Moto-stock, stock-ish Eclipse/mybearfish, and CM9/10.
I noticed while driving around today that in addition to everything I mentioned already, Moto-stock will tell the head unit when I get a text message, but stock-ish Eclipse/mybearfish doesn't. IIRC CM10 wouldn't do it either, but that's not all that surprising given its alpha state now.
I'm at a point now where I might finally be willing to give up the HW keyboard and just get a GNex in a month or two after Google announces whatever the hell is going on with the next Nexus phone(s).
Eh, BT works flawlessly for me. If you aren't stock, you shouldn't complain about BT because it probably isn't Motorola's fault.
If you are stock, that try a factory reset (sorry ), and if it still doesn't work, get a replacement 'cause your stuff is broken (just make sure it isn't your headset first!)
Except it doesn't work "flawlessly" because Motorola didn't put in support for anything newer than AVRCP 1.0. No amount of resets and replacements will change that.
I've only rooted, so it is not that big of a deal. Still is it that hard to upgrade that bluetooth section to something newer? This was supposed to be their latest hardware keyboard phone.
Sent from my DROID4 using xda app-developers app
Is anyone else aware of the TERRIBLE streaming quality via Bluetooth? the mids get crushed and sound terrible when I connect my X to my car. Did some research and found a fix for the GNex here:
http://forum.xda-developers.com/showthread.php?t=2184333
I tried to apply it to the X but it turns out there's no bluetooth-default.so in the system/lib/hw folder ... only a2dp.default.so
I replace just a2dp.default.so with the 'fixed' ones from that thread and then my phone wouldn't hold a connection to the car (Gmusic kept telling me "cannot play requested stream") and when I toggle off/disconnect from bluetooth my phone would reboot.
anyone got ideas for a fix?
there is a directory called bluez-plugin and inside that there's an audio.so and a bluetooth-health.so but I dare not mess with them hehe.
I haven't noticed poor quality streaming at all... I have used it a lot.
Sent from my XT1058 using xda app-developers app
nonotechnology said:
Is anyone else aware of the TERRIBLE streaming quality via Bluetooth? the mids get crushed and sound terrible when I connect my X to my car. Did some research and found a fix for the GNex here:
http://forum.xda-developers.com/showthread.php?t=2184333
I tried to apply it to the X but it turns out there's no bluetooth-default.so in the system/lib/hw folder ... only a2dp.default.so
I replace just a2dp.default.so with the 'fixed' ones from that thread and then my phone wouldn't hold a connection to the car (Gmusic kept telling me "cannot play requested stream") and when I toggle off/disconnect from bluetooth my phone would reboot.
anyone got ideas for a fix?
there is a directory called bluez-plugin and inside that there's an audio.so and a bluetooth-health.so but I dare not mess with them hehe.
Click to expand...
Click to collapse
The Moto X doesn't use the AOSP bluedroid stack, they stuck with Blue-Z stack so it doesn't have the same problems, and you can't apply the same fix (as you discovered).
My experience has been 100% positive with Bluetooth audio on this device, it sounds just as good as the fixed AOSP bluedroid stack does to my ears on all my BT receivers. I don't know for certain but it's pretty likely that the Blue-Z stack Motorola used is newer than the last one we saw in AOSP (Android 4.1) and there is probably an incompatibilty with your car if it really sounds that bad.
Before you guys jump all over me and call me an idiot ... I happen to be the guy that came up with that particular fix for the AOSP bluedroid stack in the first place :silly: (http://code.google.com/p/android/issues/detail?id=39632#c151) <--- woot! I'm this guy! LOL, whatever, I know. What the fix essentially did was set the bitpool (like a buffer) to the recommended size for high quality audio, but modern Blue-Z implementations didn't suffer from the same problem. It was introduced with AOSP Android 4.2 and persists in AOSP Android 4.3.
Do you have any other A2DP receivers to test against at your disposal? I've used my VZW Moto X against a Rocketfish Receiver (http://www.rocketfishproducts.com/products/home-theater/RF-BTR212.html), an HDMX Jam (http://www.hmdxaudio.com/jam-classic-wireless-bluetooth-speaker.html) and most recently a Bose Soundlink Mini (http://www.bose.com/controller?url=...s/bluetooth_speakers/soundlink_mini/index.jsp) -- playing as I write this post -- it honestly sounds just as good as my fixed Fascinate and my fixed Galaxy Nexus did, perhaps even slightly better!
Moto X A2DP = djp952 certified! :victory:
I have the same issue with poor sound quality when I stream music to my 2013 Subaru Legacy stereo. The problem seems to be that the sound is overly compressed and when a lot is going on it becomes especially noticeable. Part of the issue revolves around devices that don't support the newer APT-X codec, if the device supports that codec the sound is said to be fine however any device that uses straight A2DP will experience this issue.
djp952 said:
My experience has been 100% positive with Bluetooth audio on this device, it sounds just as good as the fixed AOSP bluedroid stack does to my ears on all my BT receivers. I don't know for certain but it's pretty likely that the Blue-Z stack Motorola used is newer than the last one we saw in AOSP (Android 4.1) and there is probably an incompatibilty with your car if it really sounds that bad.
Click to expand...
Click to collapse
I have had the same experience as you. I have tried my Moto X with about 10 different bluetooth receivers. I have had nothing but excellent sound quality.
djp952 said:
The Moto X doesn't use the AOSP bluedroid stack, they stuck with Blue-Z stack so it doesn't have the same problems, and you can't apply the same fix (as you discovered).
My experience has been 100% positive with Bluetooth audio on this device, it sounds just as good as the fixed AOSP bluedroid stack does to my ears on all my BT receivers. I don't know for certain but it's pretty likely that the Blue-Z stack Motorola used is newer than the last one we saw in AOSP (Android 4.1) and there is probably an incompatibilty with your car if it really sounds that bad.
Before you guys jump all over me and call me an idiot ... I happen to be the guy that came up with that particular fix for the AOSP bluedroid stack in the first place :silly: (http://code.google.com/p/android/issues/detail?id=39632#c151) <--- woot! I'm this guy! LOL, whatever, I know. What the fix essentially did was set the bitpool (like a buffer) to the recommended size for high quality audio, but modern Blue-Z implementations didn't suffer from the same problem. It was introduced with AOSP Android 4.2 and persists in AOSP Android 4.3.
Do you have any other A2DP receivers to test against at your disposal? I've used my VZW Moto X against a Rocketfish Receiver (http://www.rocketfishproducts.com/products/home-theater/RF-BTR212.html), an HDMX Jam (http://www.hmdxaudio.com/jam-classic-wireless-bluetooth-speaker.html) and most recently a Bose Soundlink Mini (http://www.bose.com/controller?url=...s/bluetooth_speakers/soundlink_mini/index.jsp) -- playing as I write this post -- it honestly sounds just as good as my fixed Fascinate and my fixed Galaxy Nexus did, perhaps even slightly better!
Moto X A2DP = djp952 certified! :victory:
Click to expand...
Click to collapse
I'm experiencing the same crappy BT audio I was with my galaxy nexus prior to your fix (thanks a lot BTW) on my moto x with the same BT receiver in my car. I've got a couple others I will try and report back later.
Moto x doesn't sound good on any BT device I have but none of them support apt-x which the moto x does? I know the rocketfish you mentioned has apt-x but not sure about the other 2. If they do maybe that's the difference in sound quality?
hyatari said:
Moto x doesn't sound good on any BT device I have but none of them support apt-x which the moto x does? I know the rocketfish you mentioned has apt-x but not sure about the other 2. If they do maybe that's the difference in sound quality?
Click to expand...
Click to collapse
I'm not sure either It's a good bet the Bose one does since its brand new. Seems like a pretty good theory!
I think I still have a really really old Scosche receiver kicking around somewhere I can try for you guys and compare it with an AOSP bluedroid-based phone.
http://www.csr.com/gogroove-bluesync-portable-bluetooth-speaker
Forgot to test on that which does have apt-x though I don't think it specifies in the manufacture or amazon site but that's the actual apt-x website. Can confirm that it definitely sounds better than my other devices.
Some Test Info if it helps
I have the same audio quality issue with my VZW Moto X, constant crackling noises, but I only experience it with one bluetooth receiver (of the ones I have available to test). Unfortunately, it's the only one I have built into my primary vehicle, so it's extremely frustrating. I don't have any data that indicates what these products support in terms of codecs, but here is some info if it is of any use in diagnosing the problem:
Pioneer DEH-X9500BHS - Works Great for BT-Audio and Pandora Mode
Satechi Soundfly View - Works Great
iSimple Connect ISHD651 installed in a 2008 Honda Accord - Worked Great with my Droid Inc 2, but horrible crackling with my Moto X.
mpkrcl said:
I have the same audio quality issue with my VZW Moto X, constant crackling noises, but I only experience it with one bluetooth receiver (of the ones I have available to test). Unfortunately, it's the only one I have built into my primary vehicle, so it's extremely frustrating. I don't have any data that indicates what these products support in terms of codecs, but here is some info if it is of any use in diagnosing the problem:
Pioneer DEH-X9500BHS - Works Great for BT-Audio and Pandora Mode
Satechi Soundfly View - Works Great
iSimple Connect ISHD651 installed in a 2008 Honda Accord - Worked Great with my Droid Inc 2, but horrible crackling with my Moto X.
Click to expand...
Click to collapse
I don't see any indication that states that deck supports apt-x. I read on the android bug report page that one user running 4.4 claims they've finally fixed this issue so I guess we wait for 4.4 now.
The deck does NOT have to support apt-x in order to sound good. The moto x is the best sounding bluetooth device I have ever connected to my deck, and my deck for sure doesn't have apt-x. I am so up tight about sound quality that i've always used a cable to connect my devices. The moto x is the first device I have used where I no longer need the cable and have thrown it in my closet somewhere.
seh6183 said:
The deck does NOT have to support apt-x in order to sound good. The moto x is the best sounding bluetooth device I have ever connected to my deck, and my deck for sure doesn't have apt-x. I am so up tight about sound quality that i've always used a cable to connect my devices. The moto x is the first device I have used where I no longer need the cable and have thrown it in my closet somewhere.
Click to expand...
Click to collapse
My Bose Infiniti head unit sounds amazing streaming Bluetooth from my wife's iphone4s and a load of rubbish while streaming from my motoX.
I'm very close to just saying screw it, giving in, and buying an iPhone.
Buy the iphone
Sent from my XT1056 using XDA Premium 4 mobile app
When connected to my car's bluetooth and using Google Music, artist/title/album info isn't being sent to my car's display, anyone else having the same problem? It works fine on my Nexus5 so I assume the Google Music app isn't the problem. What happens is it will usually correctly display the song info when I first launch the player but then it never updates. Could the Z3c be using an older bluetooth a2dp profile than the Nexus 5, anyone know how to check?
Track info displays and updates correctly in in my car.
I use Spotify and Google Play Music
ikon8 said:
When connected to my car's bluetooth and using Google Music, artist/title/album info isn't being sent to my car's display, anyone else having the same problem? It works fine on my Nexus5 so I assume the Google Music app isn't the problem. What happens is it will usually correctly display the song info when I first launch the player but then it never updates. Could the Z3c be using an older bluetooth a2dp profile than the Nexus 5, anyone know how to check?
Click to expand...
Click to collapse
Works flawlessly here.
Strange, I wonder why it would work flawlessly on my Nexus5 and not at all on z3c.
After some more digging around I found in Sony's Z3 Compact white paper, it lists bluetooth AVRCP profile version 1.3, whereas the Nexus 5 uses version 1.4, I think this might be the problem. I also found threads elsewhere on xda where people with phones running AVCRP 1.3 had the same issues in their car. I also tried using Spotify and the Walkman app and none of them work.
ikon8 said:
After some more digging around I found in Sony's Z3 Compact white paper, it lists bluetooth AVRCP profile version 1.3, whereas the Nexus 5 uses version 1.4, I think this might be the problem. I also found threads elsewhere on xda where people with phones running AVCRP 1.3 had the same issues in their car. I also tried using Spotify and the Walkman app and none of them work.
Click to expand...
Click to collapse
Worked with mine yesterday. So i doubt it is an issue with Revision numbers, try unpairing and Repairing
NRG1975 said:
Worked with mine yesterday. So i doubt it is an issue with Revision numbers, try unpairing and Repairing
Click to expand...
Click to collapse
I've tried everything already. AVCRP is the profile responsible for the car controlling the phone and getting the display info, the Sony is using an old version. Lots of people have reported problems with their car not getting display info on phones running the bluetooth AVCRP 1.3 profile.
ikon8 said:
I've tried everything already. AVCRP is the profile responsible for the car controlling the phone and getting the display info, the Sony is using an old version. Lots of people have reported problems with their car not getting display info on phones running the bluetooth AVCRP 1.3 profile.
Click to expand...
Click to collapse
Lots of people are reporting it as working, I am not sure that a newer version would fix the issue, as it is backward compatible.
It's not working, at all, for me.
I have a Sony XAV-601BT stereo in my car, and this worked fine with Samsung phones, Blackberrys, and iPhones. Even the Xperia ZL worked for AVRCP.
This one isn't. I can skip tracks and pause and play, but I get no song info through any app.
Very, very frustrated about this.
duraaraa said:
It's not working, at all, for me.
I have a Sony XAV-601BT stereo in my car, and this worked fine with Samsung phones, Blackberrys, and iPhones. Even the Xperia ZL worked for AVRCP.
This one isn't. I can skip tracks and pause and play, but I get no song info through any app.
Very, very frustrated about this.
Click to expand...
Click to collapse
I can follow up on this by saying that I took my phone to an electronics store with multiple radios on demonstration. It didn't work on any of them. I'm going to try completely resetting the phone to see if it helps.
---------- Post added at 05:46 AM ---------- Previous post was at 05:29 AM ----------
duraaraa said:
I can follow up on this by saying that I took my phone to an electronics store with multiple radios on demonstration. It didn't work on any of them. I'm going to try completely resetting the phone to see if it helps.
Click to expand...
Click to collapse
I'm starting to think it may be a regional/ROM based issue. Mine is on 23.0.A.2.93 and says there are no updates, so I'll see what I can find to make this work.
duraaraa said:
I can follow up on this by saying that I took my phone to an electronics store with multiple radios on demonstration. It didn't work on any of them. I'm going to try completely resetting the phone to see if it helps.
---------- Post added at 05:46 AM ---------- Previous post was at 05:29 AM ----------
I'm starting to think it may be a regional/ROM based issue. Mine is on 23.0.A.2.93 and says there are no updates, so I'll see what I can find to make this work.
Click to expand...
Click to collapse
Interesting, let me know what happens, that's the same exact problem I'm having. Also, I ordered my phone from the UK but I'm in the US, my phone is running 23.0.A.2.105. I see that there is a US firmware that some people are installing so I'm going to try installing that to see if anything changes.
ikon8 said:
Interesting, let me know what happens, that's the same exact problem I'm having. Also, I ordered my phone from the UK but I'm in the US, my phone is running 23.0.A.2.105. I see that there is a US firmware that some people are installing so I'm going to try installing that to see if anything changes.
Click to expand...
Click to collapse
Ugh. I wish I had known that. I just spent the last hour updating to the exact firmware you are on, and trying it, again with failure.
If you have more energy than I do, please go ahead and try the other various FTFs available
Just to save you guys a bit of time. I don't think your problem is region based either. I'm in Canada and I also imported my Z3C from UK and my track info displays perfectly fine over Bluetooth. My phone is bone stock.
Have you guys tried contacting Sony?
Eclypz said:
Just to save you guys a bit of time. I don't think your problem is region based either. I'm in Canada and I also imported my Z3C from UK and my track info displays perfectly fine over Bluetooth. My phone is bone stock.
Have you guys tried contacting Sony?
Click to expand...
Click to collapse
Could you be so kind as to let me know what head unit or other device you're using that it's displaying on?
Worst case scenario is I guess I have to throw some money at a new head unit.
The odd thing is I couldn't find any that worked at a local store. I tried quite a few.
duraaraa said:
Could you be so kind as to let me know what head unit or other device you're using that it's displaying on?
Worst case scenario is I guess I have to throw some money at a new head unit.
The odd thing is I couldn't find any that worked at a local store. I tried quite a few.
Click to expand...
Click to collapse
I'm using my factory head unit. 2013 Land Rover
I wanted to let you guys know that I heard from Sony about this issue. They acknowledged the bug and claim it will be fixed in the Android L update.
I no longer have this phone (because AVRCP didn't work, and it's kind of important to me) but for those of you who suffer from this, hopefully Sony will fix it.
Here's verbatim from Sony:
According to our internal teams, the issue should be fixed in the Android L release for the Z3 Compact.
Best regards,
Joe from Developer World
It worked fine for me. I also got the Sony Head Unit in my car (XAV-BT602).
What's really confusing me is that it worked fine even with displaying track titles and so on but somehow (and I really can't figure out what I could have changed) it doesn't work anymore. If someone finds a solution for this I would very appreciate his help.
duraaraa said:
I wanted to let you guys know that I heard from Sony about this issue. They acknowledged the bug and claim it will be fixed in the Android L update.
I no longer have this phone (because AVRCP didn't work, and it's kind of important to me) but for those of you who suffer from this, hopefully Sony will fix it.
Here's verbatim from Sony:
According to our internal teams, the issue should be fixed in the Android L release for the Z3 Compact.
Best regards,
Joe from Developer World
Click to expand...
Click to collapse
I suffer from the same Issue that the song information are not transmitted regularly. Only after a reconnect the songinformation is transferred once. I posted this issue in the support forum, but there is no reply up to now So i have left a remark about the support forum's quality ... Let's see
THX for your post
Rhonin
Rhonin86 said:
I suffer from the same Issue that the song information are not transmitted regularly. Only after a reconnect the songinformation is transferred once. I posted this issue in the support forum, but there is no reply up to now So i have left a remark about the support forum's quality ... Let's see
THX for your post
Rhonin
Click to expand...
Click to collapse
I also posted there to get you some support in the forum. I also contacted the support and I'll keep you informed if I know anything new.
At least I can confirm that audio info via bluetooth works in BMWs, Minis and Kias...
Has anybody managed to get their car's headunit to display track name and title when streaming music from the Moto X? All my car's headunit displays is 'Streaming' yet all info is present wheb using an iPhone 5 so it isn't the car that's the problem.
Thanks.
Try another player..
poweramp has some extra settings to this
_____
sent from XT1092
I get the name and title and album info in my 2014 Altima when using Google Music.
Nexus-S said:
Has anybody managed to get their car's headunit to display track name and title when streaming music from the Moto X? All my car's headunit displays is 'Streaming' yet all info is present wheb using an iPhone 5 so it isn't the car that's the problem.
Thanks.
Click to expand...
Click to collapse
I've used my Moto X in several different cars from different manufacturers over the past month and every one has displayed track info when using google play music and pocket casts over BT.
Thanks for the replies. I'll try another player and report back. FWIW the car in question is a 2012 Volvo C30.
Try a few other androids, it could be that it works only with ios
godutch said:
Try a few other androids, it could be that it works only with ios
Click to expand...
Click to collapse
So i tried Poweramp and checked abd unchecked every option going - still no luck.
As it happens my girlfriend has just purchased a Galaxy Alpha and this DOES display track info, using both Google Play Music and the Samsung Music app.
Any other suggestions? I'm at a bit of a loss as to why my Moto X doesn't...
Nexus-S said:
So i tried Poweramp and checked abd unchecked every option going - still no luck.
As it happens my girlfriend has just purchased a Galaxy Alpha and this DOES display track info, using both Google Play Music and the Samsung Music app.
Any other suggestions? I'm at a bit of a loss as to why my Moto X doesn't...
Click to expand...
Click to collapse
Can you check the manual/dealer to check which protocols your car uses?
godutch said:
Can you check the manual/dealer to check which protocols your car uses?
Click to expand...
Click to collapse
I could do, although the dealership is a few miles away and would charge for any software upgrades which may or may not work.
I suppose I'm just hoping that it fixes itself when Lollipop arrives!
Nexus-S said:
I could do, although the dealership is a few miles away and would charge for any software upgrades which may or may not work.
I suppose I'm just hoping that it fixes itself when Lollipop arrives!
Click to expand...
Click to collapse
Lollipop didn't fix this. My iPhone 5, my girlfriend's Galaxy Alpha and my sister's Galaxy S5 all give track info, yet my Moto X doesn't...
My moto x has always displayed the track and artist info when using google play through Bluetooth also. Maybe try removing device and adding it back to see what happens.
Nexus-S said:
Has anybody managed to get their car's headunit to display track name and title when streaming music from the Moto X? All my car's headunit displays is 'Streaming' yet all info is present wheb using an iPhone 5 so it isn't the car that's the problem.
Thanks.
Click to expand...
Click to collapse
Mine works on the 2014 Ford Fusion and my 2012 Mustang. This is while using Google Play Music. The artist picture shows up on my Fusion but not the Mustang.