Hi everyone,
I'm in need for some serious help here and I can't express enough how grateful I will be to whoever helps me out here.
The phone I'm using is a Galaxy S5 SM-G900F.
I used to be on 4.4.2 Stock ROM and I flashed XtreStoLite INTL 2.2 ROM (Android 5.0) and now my car Bluetooth connects to my phone but only shows "Call audio - Use for phone audio" Bluetooth profile and not "Media audio - Use for media audio" Bluetooth profile as it used to when I was on 4.4.2.
This means I take calls on Bluetooth and everything regarding calling works well (I can even download Mono Bluetooth Router and streamed mono music through that) but I can't stream music/sound (for example, GPS directions) from my phone to the Bluetooth in my car (A2DP style, you know, the regular).
It is important to note that on a different Bluetooth Speaker I have (NudeAudio), everything works well and as expected and both profiles are visible which is all the more confusing.
I searched on Google and came across these two interesting threads:
https://productforums.google.com/forum/#!topic/nexus/pioR9Zo-mUc <-- This is exactly my problem
https://code.google.com/p/android/issues/detail?id=79488
It's as though they've revamped the way the Bluetooth profiles are read so my phone only recognizes the Phone Audio channel.
This is one of the features I use most with my phone and if anyone knows of any solution to this I would be so incredibly thankful!
If it's not working with a custom ROM, chances are it's a problem with that ROM
Flash stock and test
*Detection* said:
If it's not working with a custom ROM, chances are it's a problem with that ROM
Flash stock and test
Click to expand...
Click to collapse
Thank you for the input.
Considering that the ROM I used is very close to the stock ROM and I have had no other issues - I would love it if there was some way to handle this issue specifically.
If anyone knows of some tools or something that could help me with troubleshooting this Bluetooth profile issue - that'd be great.
Related
Ok, I'm looking for some way to route the audio of my Magic to a mono BT headset. I have been searching the threads and Google for days now and unless I'm blind (come to think of it I've been called this before) I can't find any app for this purpose. I had a program called BT Audio for my WM phone that worked like a charm. Anyone got any ideas or up for the challenge to making an app let me know?
Android 1.5 introduced A2DP support, so all you should need to do is pair the device and fire up the music app (might be a couple more settings in between, but AFAIK it's a simple pairing job). So I'm wondering if your headset doesn't support A2DP and that WinMo app was channeling audio through the regular headset profile.
AdrianK said:
Android 1.5 introduced A2DP support, so all you should need to do is pair the device and fire up the music app (might be a couple more settings in between, but AFAIK it's a simple pairing job). So I'm wondering if your headset doesn't support A2DP and that WinMo app was channeling audio through the regular headset profile.
Click to expand...
Click to collapse
Your right my headset doesn't support A2DP (It's cheep ). I know it is possible though, cause sometimes when I am using an app or game with audio and someone calls in I hear the audio through the BT headset for a sec before the phone connects.
WinMo had a few different apps for this so I'm surprised that I haven't been able to find anything for android yet. I didn't think it would be that hard to do.
It could be that its built in to the ROM that I have and I just haven't found the settings for it yet. I'm using the My Hero ROM. If anyone knows Let me know.
Hi!
Once you pair your device (on my Cyan ROM anyway...) you can go into the BT settings, long select the device you just paired with, choose options and if it supports X feature on the BT profile (in this case, audio) then there will be a check box that you can click to enable that function/feature.
Other than that, you might have some luck searching the Market for an app similar to BT Audio. I used to have a Shadow and I know exactly what app you are talking about, all in all though I was less than impressed with the meager selection of apps I had available compared to what I have now; and definitely even the out-of-box experience is light years ahead of any WM experience. What I ended up doing instead was just grabbed a new Stereo BT headset and problem was solved There was one on http://www.woot.com a little while ago that I'm loving (LG BT250 I think?).
Good luck!
-Chad
ive also been looking for this, cant find it either though
What I ended up doing instead was just grabbed a new Stereo BT headset and problem was solved
Click to expand...
Click to collapse
I wish I could . I didn't mean the one I have was cheap in the way of money cause it cost me $80. Cheap in that it was the cheapest of the headsets that I could get with voice recognition built in as I work and drive around a lot of noise. I didn't want to pay the $130 for the good one.
I wonder if there is anyone with the right skills out there that can write a app like this. hint hint.
I do appreciate all the work that goes into making these cool app that I use every day so if nothing shows up, I guess I'll have to live without.
Thanks guys!
Android 1.5 introduced A2DP support, so all you should need to do is pair the device and fire up the music app (might be a couple more settings in between, but AFAIK it's a simple pairing job). So I'm wondering if your headset doesn't support A2DP and that WinMo app was channeling audio through the regular headset profile.
sirnuntry said:
Android 1.5 introduced A2DP support, so all you should need to do is pair the device and fire up the music app (might be a couple more settings in between, but AFAIK it's a simple pairing job). So I'm wondering if your headset doesn't support A2DP and that WinMo app was channeling audio through the regular headset profile.
Click to expand...
Click to collapse
And the point of saying this again is what exactly?
llotech said:
And the point of saying this again is what exactly?
Click to expand...
Click to collapse
Dunno, I think they just want to advertise the site in their sig...
I have a stereo Bluetooth headset (Plantronics 855) that works great with the Droid; however, there are times when I want to sent A2DP to my Jawbone Prime, which is not A2DP compatible. The profile only shows phone audio when selecting the device in the Android BT manager. What needs to happen to transmit full audio to a non-A2DP headset is enabling SCO (Synchronous Connection-Oriented) connection. I have searched everywhere I cannot find a software gateway that enables this feature in the Droid. There is an app in the market called Sound Route Switcher that claims to enable this but then blames Android for is application not working with Bluetooth.
I will keep looking and post anything that I find but I am stumped to this point.
Thanks dbigdawg
There's a little Greek in there for me, but I appreciate the effort and I'm sure many others will too. Look forward to what you can find.
Hate to bring back an OLD thread, but has there been a solution found?
Last I looked was back in April.........................Nothing
But like I said before I have been known to be blind to anything past the end of my nose!
I really miss being able to listen to music all day and not have on headphones.
Thanks for the reply bud. Maybe with some luck I can see if I can find that old file I had that was supposed to work, but didn't on 1.5. Now that I use 2.1, it might be a different situation. If I can locate it I'll post it here.
Hi, there is a new app named "Super BT Mono" which could route audio to bluetooth mono earpiece. It might be what you are looking for.
Thanks
Thanks for the info. That Super BT Mono did the trick for me.
Hi all,
Apologies in advance if this is in the wrong forum, but it does pertain to the array of 2.1 ROMs out there.
I am in search of a 2.1 based ROM that has fully functioning A2DP stereo bluetooth capabilities.
Ive used Fresh 2.0d for a long time (still do), tried DamageControl 2.08 etc.
Only one that I had some success with was DarchLegend v5.0.5, but it seemed to have problems getting my contact pictures from Facebook etc. (Admittedly I may have to try it again).
My question is whether anyone can recommend a ROM where A2DP is known to work perfectly?
Also, a more general question: are ROMs like Fresh and Damage Desire-based as opposed to Darch being Legend-based? If this is the case, what are the benefits of a Desire-based ROM over a Legend-based ROM?
(I fully admit that I don't know enough about this stuff...I've tried to search but am still in need of answers - please help a curious guy out!)
Thanks for all the help
I've used an a2dp stereo bluetooth (Blueant X5i to be specific) with the ZenEXP (mytouch based) rom, with Fresh Toast 1.1 and with Fresh 2.0d. ZenEXP seemed the best to me, but they're all glitchy. Slacker works fine with the headset. Pandora will stop playing music over it after the screen turns off. I don't use the built in media player so I can't say how well that works. NPR stream & tweet and iheartradio both worked with it just fine too. If it gets a hiccup though, it'll stop the audio and the bluetooth will get stuck saying it's disconnected and it won't reconnect properly until you restart the phone. Pandora did this any time the screen turned off.
Just yesterday I upgraded the firmware for my blueant Q1 and streamed some audio from slacker just fine. Also checked htc music app and worked too. Ill do more extensive testing tonight. Im on Damage control v2.08 which is a sprint hero based rom.
I notice that both of you above are using Blueant...
Here's my problem...I have both a Jawbone ICON and Bluetooth Stereo speakers in my 2010 Mazda.
The Jawbone seems to work fine when I upgraded it to support A2DP, but I just don't really like it because its quiet and outputs just through one speaker (obviously). My Mazda is the one Im really trying to get working...it worked flawlessly on a 1.5 based ROM (proving that the speakers/bluetooth in the car itself works)...its just on these 2.1 based ROMs.
Any ideas?
dom2114 said:
I notice that both of you above are using Blueant...
Here's my problem...I have both a Jawbone ICON and Bluetooth Stereo speakers in my 2010 Mazda.
The Jawbone seems to work fine when I upgraded it to support A2DP, but I just don't really like it because its quiet and outputs just through one speaker (obviously). My Mazda is the one Im really trying to get working...it worked flawlessly on a 1.5 based ROM (proving that the speakers/bluetooth in the car itself works)...its just on these 2.1 based ROMs.
Any ideas?
Click to expand...
Click to collapse
I have a 2010 Mazda 3i with bluetooth that worked fine with android 1.5 but the audio is messed up with android 2.1, it plays at 2 times the normal speed and will randomly slow down and sputter at times. I am thinking about rooting my phone in a couple days and playing around with the bluetooth files if possible since you aren't having any luck with any of the 2.1 ROM's out there
bluetooth
My phone worked perfectly on bluetooth in my tacoma with car m_media. Since 2.1 it works sometimes. The sprint store told me it was not the phone which I know it is and I should get a newer bt device. It was new last year. I have now found if I go into airport mode for a few seconds and then go back the bt will work until I get away from the truck again. I have to do the airport thing everytime I come back, but it will work.
Jawbone A2DP update
Anyone with jawbone can now use earphone as headphone for 'any' media from Hero, http://mytalk.jawbone.com/jb2/mytalk/beta, hope this helps!
jjjjayd13,
Hi All,
I have a 16GB TF .. and it's been very good so far. However, I'm having an issue that I think is probably simple .. but google & xda searches don't find anyone else with the same issue.
I want to use Skype over the tablet, but with a bluetooth headset. Using the TF with just the internal mic & speakers is pretty speakerphon-ish .. and I'd like to use a headset.
I have a couple of BT headsets (one of them 2.1 w/ EDR), and I can pair any / all of them to the TF. Problem is, the audio doesn't come through over the head set, and I don't know how to force it to.
The TF (now running 3.1) acknowledges that the headset is connected (to phone audio it says) .. but the only options in the configuration is to remove it.
What am I missing? I see reviews all over the place where folks are using the tablet to play movies in the car, and piping the audio out via BT? I think I must be missing a config step .. but can't find it.
Thanks for your help.
Im kind of in the same boat but I dont think honeycomb has a "phone audio" functionality. Only "media audio," which is what you would use when piping audio to external speakers.
its the same on the phone, those headsets only connect to mono phone audio so if I was playing a movie or music its silent. So for right now I think you are stuck until they figure out how to make specific apps recognize the phone audio device.
Makes some sense .. so it knows there's a "phone audio" aspect to things out there, but we don't have any way to force the Skype audio to be phone audio and not media.
So if I had a stereo headset, would the system work with it and pipe the audio out since it would recognize it as a media audio system?
Where does the mic fit in all of this?
I have a BT combination headset/headphones which I paired with the Transformer, and from testing it I can say the following:
1. The transformer paris with the device and recognizes both the "handsfree" and "media" profiles that the headphones support.
2. The "media" profile (also called A2DP, stereo bluetooth, etc) works fine. I have listened to music in stereo though them and all of the controls like play/pause and previous/next work properly. If you want to listen to movies, music, or whatever else you should be fine.
3. I can hear Skype through the headphones, but testing revealed that Skype is using the Transformer's build in microphone rather than the one in my headphoens. It also doesn't respond to the call button. Thus, it seems to be using the "media" profile to deliver sound.
So, even though the Transformer can clearly recognize handsfree profile, it either isn't passing it to apps or Skype isn't asking for it.
It looks like as long as you plan to be Skyping with the tablet infront of you, you can get almost the same functionality of a handsfree/headset by using a BT headphones instead. As long as you don't plan to leave the tablet in one room and talk in another you should be fine.
hey so i tried Super BT Mono Free Trial and it actually worked. thought it was Froyo only and reportedly broken with gingerbread.
using Samsung WEP450 paired "handsfree" profile, turned on Super BT Mono and to my surprise audio from music player routed to the BT headset. sound is crappy, and so far can't get audio from BeyondPod to the BT headset.
rooted 8.4.4.11 with netformer 1.5 OC 1.6 ghz and juwe11 ram profile.
...
try jabra... coz jabra headset supports a2dp i had the same issues until i bought a jabra
Good help :] but way to dig up a year old thread xDDD""
hehehehe
Thing O Doom said:
Good help :] but way to dig up a year old thread xDDD""
Click to expand...
Click to collapse
hahaha just wanna keep answering those unanswered questions coz before i couldnt post here and i see a lot of questions left unanswered and i know how it feels just like to help out in anyway
On the stock ROM I cant get Bluetooth song titles working on my car stereo, it worked when I used to use cyanogenmod but not anymore. I'm using Google play music on 4.4.2, does anyone know what the problem could be?
Are Bluetooth song titles working for anyone else?
aarynb1 said:
Are Bluetooth song titles working for anyone else?
Click to expand...
Click to collapse
Custom ROMs have much better support for the various Bluetooth protocols. Depending on car manufacturer they may have a completely different set of protocols, then the ones supported by the stock Nexus 4.
If it works with Cyanogenmod, then I would use it.
Hi all - is anyone here trying to the SHIELD Remote with full android rather than the stock firmware?
I am, and everything works (even volume control and headphone audio output!) except the microphone.
If anyone has any suggestions for how I could go about debugging the microphone input, I would very much appreciate it as it's the last thing preventing my setup from being perfect.
The message I see when I press the voice input button on the remote is "Can't open microphone" (screenshot at end of this post: http://forum.xda-developers.com/showpost.php?p=64552147&postcount=14 )
Android is clearly just not recognising it as an audio input device, but I'm not sure why.
My guess would be that the stock firmware has a kernel module loaded or some modification to the Android bluetooth stack to support bi-directional A2DP devices rather than just one way.
Has anyone here ever seen Android working with a bluetooth device with audio input? Perhaps a bluetooth headset with microphone? Does that use A2DP?
Hi there, any progress ? trying to find some solution for the same problem!
andrewthecoder said:
Hi all - is anyone here trying to the SHIELD Remote with full android rather than the stock firmware?
I am, and everything works (even volume control and headphone audio output!) except the microphone.
If anyone has any suggestions for how I could go about debugging the microphone input, I would very much appreciate it as it's the last thing preventing my setup from being perfect.
The message I see when I press the voice input button on the remote is "Can't open microphone" (screenshot at end of this post: http://forum.xda-developers.com/showpost.php?p=64552147&postcount=14 )
Android is clearly just not recognising it as an audio input device, but I'm not sure why.
My guess would be that the stock firmware has a kernel module loaded or some modification to the Android bluetooth stack to support bi-directional A2DP devices rather than just one way.
Has anyone here ever seen Android working with a bluetooth device with audio input? Perhaps a bluetooth headset with microphone? Does that use A2DP?
Click to expand...
Click to collapse
Just to answer last part.
Bluetooth headsets, mono as well as stereo, work fine on full android rom. Including microphone.
Btw, it is controlled in phone sections (headset) of the bluetooth stack and not a2dp which is headphone profile.
Google and by extention nvidia, have changed something in handling microphone from the remote, and that change is probably closed source.
Note 5 ?
Thanks for the heads up Idan73, I've actually since figured out the same thing by connecting a friends bluetooth headset to my NSTV (it worked fine).
I'm going to dig into the original nvidia rom and see if it's something simple like a system APK which is handling the remote audio input.
I assume it isn't in the kernel as I believe zulu99's full android ROM is already using the same untouched kernel from nvidia.