Bluetooth Play/Pause not working - Samsung Galaxy Nexus

I'm trying to use my Jf3 Freedom Bluetooth Headphones with my Verizon Galaxy Nexus. They pair and the audio is great but the Play/Pause/Next/Previous buttons do not work when using programs like Spotify but they do work when using Google's Music app. They used to work fine with my Sprint Epic 4G. Anybody having similar issues and knows a fix? I've searched but can't find anyone reporting this issue.

Related

[Q] Bluetooth A2DP/Track Titles

I searched and couldn't find another thread about this so here goes...
Got a new bluetooth car stereo and my music and calls sound great, but my EVO doesn't transfer the track title/artist/album info to the stereo for some reason. I know it's not the stereo itself as my friend paired his BlackBerry and it showed the track titles. Tried this in stock music app, DoubleTwist, PowerAMP and unrooted on 2.2 and rooted w/CM7. Thanks in advance!
EDIT: Possibly just answered my own question but if anyone can confirm that would be great...it looks like the EVO only supports AVRCP v1.0 so far?? And if so, is there any way to upgrade the BT profile to 1.3 or 1.4 to allow for metadata transfer? Again, thanks in advance.
Yeah... the evo bluetooth profiles fail.
I'm currently using PowerAmp and love it...I know that metadata xfer is and has been working for stock player for a while, but does anyone know if this feature is available on any ROM besides AOKP? They're dropping support for us :crying:
bwaredapenguin said:
I'm currently using PowerAmp and love it...I know that metadata xfer is and has been working for stock player for a while, but does anyone know if this feature is available on any ROM besides AOKP? They're dropping support for us :crying:
Click to expand...
Click to collapse
bump
If you're using a new phone with bluetooth 4.0, AVRCP 1.3, metadata transfer will not work until the music player devs update their programs. A rooted phone may work. For non rooted we are at the mercy of the devs, and poweramp has been promising an update for over a year now.

[Q] Bluetooth compatability

I'm thinking of upgrading to this phone, one of the main reasons is that my current device, which has galaxy S guts, is not compatible with most bluetooth devices. I like to use an app called blueputdroid that turns my phone into a universal keyboard as well as an ELM bluetooth device that turns my phone into a dyno along with the torque app for my car.
For some reason the way samsung built the bluetooth makes it not work with a lot of these things, I know it's not the apps or 3rd party devices as I use my old G1 now for it, but would much rather just have my main phone be my one device.
Have any of you tested blueputdroid or any bluetooth devices? If not could someone try out blueputdroid with this phone (it's free in the market) any help would be much appreciated thanx!!
Says it has detected unsupported Bluetooth stack.. Install cyanogen Rom, etc.
Thanks, at least this phone is likely to get cyanogenmod support which will fix the problem my SK sure as hell won't
My GS2 works perfect with my ELM adapter. It worked perfect with my Vibrant too. I've never had a single problem with any bluetooth device on either of them.
I've had a lot of bluetooth problems with both my vibrant and now my GS2. Both work reliably with my wife's mini cooper bluetooth but they both have had problems connecting to the garmin nuvi I use for handsfree in my car (and forget about the A2DP on it).
I tried a lot of roms on my vibrant (incl stock) and they did lots of cool stuff but never made the BT connect reliably. Then I came across this thread: http://forum.xda-developers.com/showthread.php?t=795691
I made the suggested change to /system/etc/bluetooth/audio.conf and voila! I finally have good BT with my vibrant.
So I got my SG2 last week, rooted it and found that it also had the bad settings in /system/etc/bluetooth/audio.conf. However it also lacked BLN (backlight notification) and few other tweaks I've come to love on my vibrant so I flashed juggernaut 2.6. That fixed all the major foibles with the SG2 but it still won't reliably connect to my garmin.
I opened up the filesystem to find that /system/etc/bluetooth/audio.conf is no longer there! Does anyone know where it went?
Apparently I don't have enough posts to ask in the dev forum where juggernaut was posted http://forum.xda-developers.com/showthread.php?t=1322642 so I'm hoping someone will see this plee for help.
thanks
the phone has BT 3.0, but it is backward compatible with BT 2.0 and 1.0 devices
i haven't had any trouble using it with my car deck (streaming audio & phone), my large collection of stereo BT devices, and other BT enabled phones & PCs/Laptops
the remote control feature from the stereo headsets works properly, for fast forward, backward, play, pause, talk, mute, etc
the only thing i have yet need to test BT on is with a BT smart wrist watch

Bluetooth and Galaxy Nexus

Hi guys, question. My Nexus plays music through my aftermarket stereo fine through bluetooth but my annoyance is that the info doesn't show up. ie artist name, songs etc. While my ipod shows it all. I've read that it's just bluetooth firmware on the stereo/iphone/android but it's still such a pain in the a** that Iphone has the benefits while Android being better doesn't get as much. =( My question is do any bluetooth guru's out there know of a workaround or way to have info show up. My next step is trying different players etc.
The data needs to be sent by the application playing the music. I've found that Apollo will send this data to the screen on my 2012 Civic, the stock player does not.
I think certain ROMs have the latest bluetooth firmware. I think CM9 does? Not positive. I would also like to know if there was some way to update the firmware, on any ROM.
Cheesejam said:
I think certain ROMs have the latest bluetooth firmware. I think CM9 does? Not positive. I would also like to know if there was some way to update the firmware, on any ROM.
Click to expand...
Click to collapse
My GN wont connect for Bluetooth Audio (A2DP bluetooth receiver plugged into car ipod dock) - I have tried and tried, different roms, etc, no luck - my 3 year old Droid X works just fine, but my 8 month old Nexus wont connect - WTF. I enter password, get error that unable to pair.
My phone pairs to the car bluetooth phone no problem, but will not pair to audio.
Any suggestions???
Thanks!

[Q] Streaming audio questions? T-Mobile

Hey guys, I have a question for you. I have a VZW GNex and have no issues at all with it (except the high bill). I am looking to transfer to T Mobile and have purchased a used GNex unlocked to run on the TMo network. The phone works great.
However, I do have one issue, streaming audio. I use either iheartradio or google music to stream, and when sitting here in my room I don't have an issue, but in the car the audio keeps cutting out every 10 seconds or so and I have to restart the stream.
Anybody else on TMobile have this issue? Any way I can change it?
TheRandom1 said:
Hey guys, I have a question for you. I have a VZW GNex and have no issues at all with it (except the high bill). I am looking to transfer to T Mobile and have purchased a used GNex unlocked to run on the TMo network. The phone works great.
However, I do have one issue, streaming audio. I use either iheartradio or google music to stream, and when sitting here in my room I don't have an issue, but in the car the audio keeps cutting out every 10 seconds or so and I have to restart the stream.
Anybody else on TMobile have this issue? Any way I can change it?
Click to expand...
Click to collapse
Are you using bluetooth in the vehicle?
Nope I'm not andno clue to the fact as well
Sent from my Galaxy Nexus using xda premium
chrisinsocalif said:
Are you using bluetooth in the vehicle?
Click to expand...
Click to collapse
I have tried with using bluetooth AND just a cable running from the headphone jack of the phone to the aux in port on my stereo with the same result.
Figured it out when I got on the phone with Tmo... apparently they had to update the IMEI number to fully unlock it? Doesn't make much sense to me, but it works now.

[Q] Bluetooth AVRCP 1.3 Issues.

I've have a GS4 & a GN2 and both send metadata just fine for me over bluetooth, such as my modded pandora that will send the track info, Well on my GN3, metadata crashes bluetooth sent by pandora & spotify. Google's Music Player sends just fine. I've came across a few others with the same issue as well, I've tried using the stock Pandora player to see if Android 4.3 implemented the AVRCP 1.3 correctly and no metadata was transmitted. Has anyone came across this issue?
Purest said:
I've have a GS4 & a GN2 and both send metadata just fine for me over bluetooth, such as my modded pandora that will send the track info, Well on my GN3, metadata crashes bluetooth sent by pandora & spotify. Google's Music Player sends just fine. I've came across a few others with the same issue as well, I've tried using the stock Pandora player to see if Android 4.3 implemented the AVRCP 1.3 correctly and no metadata was transmitted. Has anyone came across this issue?
Click to expand...
Click to collapse
I have an ATT SM-N900A Note 3 and have tested it with my Ford Focus 2013 and I have the same problem. No track data is listed. Where is used to work when I would use my Galaxy S3 phone running a stock Android 4.3 rom. I have a similar thread going in the ATT Gnote 3 forums.
http://forum.xda-developers.com/showthread.php?t=2473555
On a side note (pun intended) I had a buddy of mine bring his Tmobile Note 3 over to test on my car and I got the same results. I was able to see texts messages, but I got no track metadata sent over from either Pandora or BeyondPod where it works with my previous phone.
Hope that helps confirm the issue here for ya as well.
Purest said:
I've have a GS4 & a GN2 and both send metadata just fine for me over bluetooth, such as my modded pandora that will send the track info, Well on my GN3, metadata crashes bluetooth sent by pandora & spotify. Google's Music Player sends just fine. I've came across a few others with the same issue as well, I've tried using the stock Pandora player to see if Android 4.3 implemented the AVRCP 1.3 correctly and no metadata was transmitted. Has anyone came across this issue?
Click to expand...
Click to collapse
I noticed the same thing. It worked great on 4.3 AOSP ROMs on my Note 2 but not on stock 4.3 on Note 3.
Sent from my SGH-T889
Worked on my 4.3 galaxy nexus, but nothing on the note 3 (T-Mobile) both are using slacker
Sent from my T-Mobile note 3
I've tried all versions of pandora modded AVRCP & all crashed bluetooth on my TMO Note 3, I've heard the same for modded spotify as well. No issues with any other phones though. I've tested on multiple bluetooth receiving devices, the newest modded pandora will crash bluetooth when its not even connected. Only crashes when meta data is sent.
This is frustrating
Any idea how we can fix this?
Unfortunately, I'm thinking we may have to wait for custom Roms, or a fix from Samsung. Either way, I hope we get something quick.
Sent from my SAMSUNG-SM-N900A using Tapatalk
T-Mobile Galaxy Note 3 and having the same problems. I can stream music to my pioneer avh-x8500bhs but no data is being shown. If I use the google music app it works fine. I also noticed that the appradio app does not connect at all through bluetooth. I am thinking that somehow it is connected to this problem. I tried custom roms and custom kernels but still not working correctly.
Same Issue
jimmydigital00 said:
T-Mobile Galaxy Note 3 and having the same problems. I can stream music to my pioneer avh-x8500bhs but no data is being shown. If I use the google music app it works fine. I also noticed that the appradio app does not connect at all through bluetooth. I am thinking that somehow it is connected to this problem. I tried custom roms and custom kernels but still not working correctly.
Click to expand...
Click to collapse
I have the same exact issue with Pandora. I didn't know what was causing it so I submitted a ticket with Pandora and nothing was able to work. This functionality was working when I had the Note 2. Hopefully Samsung comes out with a fix for this.

Categories

Resources