This application is a hotfix for a really annoying (and potentially unsafe!) bug in the Epic4G:
http://code.google.com/p/android/issues/detail?id=11372
http://forum.sdx-developers.com/epi...audio-routing-on-epic-4g/msg115990/#msg115990
The long and sort of it is that when anything is plugged into the 3.5mm headphone jack, the phone will only play call audio over that jack.
In order to route the audio through the earpiece, bluetooth or speakerphone, you must pull the plug out of the jack. This is at the very least annoying, and at the very worst potentially dangerous if, for example, you're driving.
How-To
Download the APK attached below for your android version.
Install like any other APK using adb or your favorite file manager.
What it does
This simple application allows you to pick the audio device to use for call audio to override this behavior, and can be changed on the fly.
All in-call audio will be routed to the device you specify when something is plugged into the 3.5mm headphone jack. If nothing is in the jack, the default behavior for the phone applies.
This also allows you to use the Speaker Phone when the headphone jack is occupied, even though the button on the call screen is disabled!
Your configuration should persist between reboots.
What it doesn't do
This app does not route any other type of audio. Your music, notifications, etc will still play over the headphone jack or phone speaker.
Again, this *only* affects in-call voice audio, and only when something is plugged into the headphone jack.
Notes
This app completely overrides the options on the call page! If you want to switch outputs during a call, you will have to do it from this app - your call will not be dropped when changing the output device.
In order to route the call audio properly, the system's mediaserver service must be restarted, however.
This means that any other audio you have playing when you apply the change will be disrupted, and related services may force close. For example, Pandora will skip to the next song. Other applications may not behave that well.
Disclaimer
This app modifies files in the /system partition, so use this at your own risk! I am not responsible for any problems that arise from this hotfix on your device!
This is currently for the EPIC4G *ONLY* - Do not use this on any other device. Please contact me if you have a different phone which experiences this bug and I will see if I can get it working for you as well.
This is *BETA* software, a work in progress, please post here if you experience any issues, but I cannot guarantee it will work for you!
ROM DEVs, feel free to bake this into your roms in whole or part, I encourage it as this provides a workaround for a safety issue, but please give credit if you use or derive from this application.
Special thanks to UberPinguin - his initiative, debugging, code-diving and testing helped make this happen every step of the way!
Many, many thanks to everyone in #samsung-epic for helping me test and work this out.
Be sure to download the APK for the right android version on your phone!
epicBT - v0.3.5 (Froyo)
* Fixed crash/reboot when applying settings in DK17 roms
epicBT - v0.3
* Layout cleanup when root is unavailable
epicBT - v0.2
* Requires root!
* Superuser compatible
* auto-remounts /system RW if necessary
* Sends call audio to wired device ( default ), speaker phone, or bluetooth
Sources
https://github.com/cicada/epicBT
If this works as described above I will be so f-ing happy. One of my biggest gripes, solved.
No sh#t! I was just about to start searching the Market for an app like this! Downloading now to test.
Thank you!
bigdbag said:
If this works as described above I will be so f-ing happy. One of my biggest gripes, solved.
Click to expand...
Click to collapse
I agree
updated OP with source link
First of all,...Thank you, Thank you, Thank you for working on this... This was one of my biggest gripes with this phone and I couldn't understand why the "geniuses" at Samsung/Sprint couldn't get this right.
I've done some extensive testing in my car for the Eclair version and wanted to share my results:
For the most part, the app does what it's supposed to...but I did notice that:
1) the "on the fly" feature doesn't work so well. That is, when changing from one mode to the other, I had to reboot the phone to get the new setting to take effect. This feature would be great with an app like Tasker, which could automatically open up the app and ask you which setting you want to use when a headset/aux jack is plugged in,...thus giving you the flexibility to use the best option depending on your situation. Is there a way to tweak the app to recognize the switch without rebooting by resetting something like the mediashare service?
2) For some reason, the mic volume (volume heard on the opposite end of call) on the bluetooth setting is lower when the headset/aux jack is plugged in. I'm not sure whether the regular phone mic, speaker phone mic, or the bluetooth mic is utilized in this setting, but the volume is definitely harder to hear on the other end than when the headset jack is unplugged. I would guess about 20-25% lower. I tested this effect during the call as well by plugging and unplugging the jack while counting 1 to 10 and it's the same. Is there away to increase the sensitivity of the bluetooth mic when the headset jack is plugged in?
Donation coming if you can get this working! Thanks again.
sinman02 said:
1) the "on the fly" feature doesn't work so well. That is, when changing from one mode to the other, I had to reboot the phone to get the new setting to take effect.
Click to expand...
Click to collapse
Strange, it works well for me - it takes a second to switch outputs while mediaserver is restarting, but never had to reboot. I'll look into this, may have accidentally tweaked something in the last build.
UberPinguin and I are still looking at the sources to find a better fix that works the way it's supposed to - the trouble seems to be that Phone.apk is actually selecting the 'correct' source and setting options appropriately, but the underlying OS isn't switching outputs. Restarting mediaserver was the only workaround I could find for this.
sinman02 said:
2) For some reason, the mic volume (volume heard on the opposite end of call) on the bluetooth setting is lower when the headset/aux jack is plugged in. I'm not sure whether the regular phone mic, speaker phone mic, or the bluetooth mic is utilized in this setting, but the volume is definitely harder to hear on the other end than when the headset jack is unplugged. I would guess about 20-25% lower. I tested this effect during the call as well by plugging and unplugging the jack while counting 1 to 10 and it's the same. Is there away to increase the sensitivity of the bluetooth mic when the headset jack is plugged in?
Click to expand...
Click to collapse
I hadn't noticed any volume issues but truthfully I haven't been using the BT often because of this bug - I've just been letting my calls go to VM instead of crashing my car Volume selection should be working properly so I'll see if I can add something to select volume as well.
To be clear on the MIC, input should always be the proper input for whichever mode you choose - phone MIC for speakerphone and BT mic for BT HP/HS.
If you're on stock then the phone mic should be used when your wired device doesn't have it's own, however this is broken in all of our custom community kernels - Wired Headset mode should only be used when you actually have a wired headset with a MIC of it's own if you're using one of these, otherwise the phone doesn't enable any MIC at all.
I should note, that all my tests were conducted on outgoing phone calls. I don't know if incoming calls are any different. I am using the Syndicate rom.
If you can get the bluetooth volume issue resolved, I'll likely leave it there, but it would be nice to be able to switch on the fly to speakerphone mode when bluetooth isn't handy.
Question: Does the froyo version have the same implementation?
Please keep up the good work!
Sent from my SPH-D700 using XDA App
sinman02 said:
Question: Does the froyo version have the same implementation?
Click to expand...
Click to collapse
Yes, the froyo version is the same - Samsung used a different asound.conf in froyo ( added in some interesting VOIP pcm ), so this is the only difference between versions currently.
cicada said:
This application is a hotfix for a really annoying (and potentially unsafe!) bug in the Epic4G:
The long and sort of it is that when anything is plugged into the 3.5mm headphone jack, the phone will only play call audio over that jack.
In order to route the audio through the earpiece, bluetooth or speakerphone, you must pull the plug out of the jack. This is at the very least annoying, and at the very worst potentially dangerous if, for example, you're driving.
Click to expand...
Click to collapse
...So this should work on for Sip/VOIP apps like Sipdroid, 3CX, and Fring? I managed to pick up 3CX and Sipdroid through my bluetooth headset but no mic...meaning the other end could not hear me... There aren't that many good sip/voip soft wares out there for the Android today.. I rated Fring the BEST but with no bluetooth support.
EDIT: Nevermind... I read the post again.. I don't think this will do the job other than support for the actual phone.. but it would be nice to have that option for sip/voip as well.
The SIP/VoIP stuff may work better in Froyo considering there are dedicated PCM devices listed in the asound.conf - however I've never used any of these applications, so this is pure speculation.
You're correct, this does only effect in-call phone audio, those applications would be handling (or in this case, not) the bluetooth audio routing directly. I've found lots of other similar quirks with BT on the Epic4G, such as the << and >> buttons on my A2DP headphones not working.
cicada said:
The SIP/VoIP stuff may work better in Froyo considering there are dedicated PCM devices listed in the asound.conf - however I've never used any of these applications, so this is pure speculation.
You're correct, this does only effect in-call phone audio, those applications would be handling (or in this case, not) the bluetooth audio routing directly. I've found lots of other similar quirks with BT on the Epic4G, such as the << and >> buttons on my A2DP headphones not working.
Click to expand...
Click to collapse
I am using Froyo the DJ29 Build on the epic... Dare I try?
****ing yea! Thanks, downloading now. This has been my biggest complaint with the phone
Sent from my SPH-D700 using XDA App
Hell Yea! You rock! I Threw out a fairly long search sentence in google and actually found your post here. No sooner did I install and set it up that my phone rang while plugged into the car audio and FINALLY I can use my friggin BT headset without yelling hold on hold on I gotta unplug the stereo cable. This has really peeved me off since I got the phone. Now what I don't get is why this obvious flaw has been ignored by Samsung and Sprint. Nice job on making it work like it should. BTW running stock 2.1 with root. No bugs so far.
THANK GOD. someone fixed this. bugged me so much in the car when i'm receiving a call. will report any bugs.
bump, updated to fix crash in DK17 based roms
cicada said:
I hadn't noticed any volume issues but truthfully I haven't been using the BT often because of this bug - I've just been letting my calls go to VM instead of crashing my car Volume selection should be working properly so I'll see if I can add something to select volume as well.
To be clear on the MIC, input should always be the proper input for whichever mode you choose - phone MIC for speakerphone and BT mic for BT HP/HS.
If you're on stock then the phone mic should be used when your wired device doesn't have it's own, however this is broken in all of our custom community kernels - Wired Headset mode should only be used when you actually have a wired headset with a MIC of it's own if you're using one of these, otherwise the phone doesn't enable any MIC at all.
Click to expand...
Click to collapse
As others, I'm very grateful for this fix. After trying it out, if it works for me, donation on the way.
Regarding the MIC: My experience, all the way back to pure stock (IIRC) is that there is no MIC at all when a two-channel, stereo plug is inserted (headphones, cassette adapter, etc.). Every time I've been driving, listening to something via the headset jack, when a call comes in I can hear the other party, but they can't hear me at all until I unplug from the jack. So, even though there was no mic plugged in and the device was correctly sending 2-channel audio out through the jack (usually to a cass adapter, so I can listen via my car stereo), but doesn't "do the right thing" with the mic, even though the hardware and drivers are capable of detecting the absence of the mic.
It should, of course, default to the BT mic if there is a BT connection, or the built-in mic otherwise. For some reason this simple flow-diagram logic eludes Samsung.
So I got my first experience with this today...worked great. I was streaming Pandora, phone call came in, music was paused and I answered the call. Once I finished the call, the music continued playing. Minor detail, but since I was on WiFi, is there anyway that the music could have kept on playing while I was still on the call for the sake of my guys who were still working while I was taking the call? It's great that the music paused and resumed by itself, but it would have been cooler to have it keep going while I was on the call.
m5james said:
.. is there anyway that the music could have kept on playing while I was still on the call .. ?
Click to expand...
Click to collapse
Unfortunately Pandora's phone-state listeners control that, it'd have to be modified or their devs would have to add options for it. Would be cool though, I agree
I've got a hacked version of Pandora that allows unlimited skips, I'll have to ask the guy who did it to see if they can tweak that as well. Come to think of it, it'd be nice to have it keep going for the times I'm driving down the road as well so whoevers in the car doesn't have to sit there and listen to me blah blah blah.
Related
I've searched around on the forums for an answer to this but could never find anything that seems to match up to my issue.
I have a A2DP enabled headset and want to use it with apps such as Team Speak 3 beta, Vent, and other apps. But for some reason although phone media happily plays over onto my headset. My phone continues to only use the mic built into the phone instead of the bluetooth headset mic.
Any apps designed to use the headset specifically work (ie. normal phone calls, skype, vlingo) but otherwise apps ignore the headset mic.
I already tried using apps like BT Mono and Super BT Mono Froyo but they seem to only pipe audio to the headset, but don't do anything at all with the headset mic.
Does anybody know how to get the headset mic to be selected by apps instead of just the built-in mic?
My device is a Sumsung Galaxy S II ( I9100 ). Both Stock and CyanogenMod Gingerbread
good good good
Still hoping someone may know how to get the Galaxy S II phone to use a bluetooth headset mic instead of the built-in mic on the phone.
I'm really stumped on how to do this.
I still haven't seemed to have any luck finding a way to forcefully map apps to use the headset mic. I'm beginning to wounder if it's possible with the Android OS.
I have the galaxy s2 as well and I've retired several different things and have been unsuccessful with anything I've tried so far... Really difficult to drive and use vent without a headset.
Yeah I'm wanting to do the same thing.. I don't spose you've found a way in the last couple of months? Surely it can be done - may need to get a dev to write something for it though..
Sorry Lilfellabob, still no luck. I find it odd it's so difficulty to remap audio settings.
Even in Ice Cream Sandwich I can't find a way.
The app would need to be written to accept it. Its not a matter of your phone. Its the apps. Think about it for a min. If it works on apps made to use it but another app doesn't work then where does the problem lay?
The thing is, typically other apps should be able to re-route the app to use the headset mic. Alike how there are apps that can force other apps to use bluetooth audio instead of the phone speaker, even if the phone/headset can't use a2dp.
Dav_Edward said:
The thing is, typically other apps should be able to re-route the app to use the headset mic. Alike how there are apps that can force other apps to use bluetooth audio instead of the phone speaker, even if the phone/headset can't use a2dp.
Click to expand...
Click to collapse
Only if the code is there for it to do it. If they don't code it in then it doesn't work.
I'm having a similar problem but slightly the opposite.
I pair my phone to a Bluetooth device that lets me hear phone output on my car's speakers. However, the phone tries to use Bluetooth for the microphone when none exists. I want to force it to use the on-phone microphone. I can talk and talk but no one can hear me, unless I set the phone output to speaker or handset, which implies setting the phone input to amplified built-in mic, or just built-in mic, respectively.
In the Bluetooth settings I can set to use the Bluetooth device for music or phone, but ideally I would want "Phone" to be separated into "Phone output" and "Phone input" so I could uncheck input (and thus use the built-in mic.) This should be implemented at the Android level so that the setting can apply to all apps.
The same problem occured when I wired (2-stripe phone-to-car audio only, no mic) my Palm Pre directly to my car. I just tried with my GNex and it was smart enough to use the built-in mic when a microphone-less plug was connected.
zelendel said:
Only if the code is there for it to do it. If they don't code it in then it doesn't work.
Click to expand...
Click to collapse
wrong. its in the kernel. the new firmware on the android is is capable to transmit Audio Steam to Headset device as Audio only. i wont go 100% against coding to force it to but if they wanted to theres have to be some kind of exploit to do so. lets say if skype were to find that exploit or code it, it would be probably violate android policy.
HtcEvo4gLTE said:
wrong. its in the kernel. the new firmware on the android is is capable to transmit Audio Steam to Headset device as Audio only. i wont go 100% against coding to force it to but if they wanted to theres have to be some kind of exploit to do so. lets say if skype were to find that exploit or code it, it would be probably violate android policy.
Click to expand...
Click to collapse
Actually, what's going on is Skype is using the 'bluetooth device' hook of some sort, just like other apps that support piping audio to the bluetooth headset. However most apps don't use the bluetooth device API/hook and just dumbly send their audio to 'default output device' and 'default input device' blindly and let the OS or Kernel decide where to send it.
The OS or Kernel when it senses a bluetooth device with the 'media' profile on it is present, it changes the default output device to the headset, but it doesn't seem to bother doing the same for the bluetooth mic for the default input device.
Because apps like Teamspeak 3 just blindly use default audio device because it doesn't use bluetooth APIs in the app itself, I have no way to make it use the headset mic.
I wish someone could make a mod or app that will allow mapping the default input to a bluetooth mic when present.
As far as I know, Skype has problems using the BT mike as well. In fact, they took a user survey regarding the issue for android and iOS users. However, I cannot find the results of that survey / study, and Skype recommendations thereof.
User choice to use BT mike seems so BASIC to me, I wonder how it was overlooked...!
Rooting will crack open the full power of your Android device!
Dav_Edward said:
Sorry Lilfellabob, still no luck. I find it odd it's so difficulty to remap audio settings.
Even in Ice Cream Sandwich I can't find a way.
Click to expand...
Click to collapse
zelendel said:
The app would need to be written to accept it. Its not a matter of your phone. Its the apps. Think about it for a min. If it works on apps made to use it but another app doesn't work then where does the problem lay?
Click to expand...
Click to collapse
Rooting the device would give apps or the user permissions to modify system audio controller's (idk if it is anything like ALSA or anything..) settings to make app use the audio channel for the bluetooth headset... an example for the Galaxy s2 i9100 i have is the radio app "Sprit FM" has a "volume control stream" setting which allows the user to select what volume "control" will control the volume of the app's audio output
anywho... i hope it helps a little
rwong48, I have now the same problem that you have described. Have you solved it with any app for Andorid?
Thanks!
Solution
I found an app that solves this problem on android devices, it's called btmono and you can find it in the Google store. I tried to post the link but I don't have enough posts under my belt...
Anyways, pair your device, open the program (such as ts3), connect to your server and then turn on btmono. Voila!
Well, I tried to delete this after I saw that you had already tried btmono, but I couldn't figure out how so just disregard this message.
I already tried btmono, sadly although it works for the output audio, it does *not* work with the headset mic. Programs like TS3 will still keep using the phone's built-in mic, not the headset mine despite using btmono. The only thing btmono does is pipe the output audio to the headset only.
Thanks for the suggestion though
I can't believe they haven't fixed that yet. It is so basic...
Hey guys I'm going through the same issues with my note 2. Svoice was the only one that works but its painfully slow and inaccurate.
Anyways I've tried utter! robin and aivc. Aivc works pretty good but at least it uses the mic.
Utter is really promising but no Bluetooth mic. The devs have acknowledged it though. So hopefully soon.
Update: AIVC has one downfall. The app can't open if the screen is locked like utter and svoice can when prompted from bluetooth. Also, it only listens automatically the first time. If you close it without killing the app, you'll have to press the mic icon manually every time (which takes away from the purpose of handsfree).
I've touched on this question before but I may have been using some wrong terminology.
On my S3 I have successfully created a BT pairing with a BT Audio Device use which has a steroe out fed into my car's head unit's Aux In.
So, it is Auto-Paired. That is, when I step into my car and turn on the ignition thus powering up the BT Audio Device the paring is available to be used for Media Audio.
However, in order for my phone to route audio to the BT Audio Device I must enter the phone's BT menu and tell the phone to connect to the Device for Media Audio.
I can either do this through the notification pane to see pairings then tap the pairing to use for Media Audio or I can go through settings->BT and do the same thing.
Either way, it's a huge PITA to do this every single time I get into my car.
There has got to be a way to have the phone automatically route Media Audio through this BT Audio Device upon detection. My previous two phones had nowhere near the ability of my S3 but they had no issues whatsoever with automatically pairing and routing audio to this BT Audio Device.
Is the S3 really this stunted in the BT department? If so, is there an app that fixes this stupidity with grace and non-intrusiveness?
crabapples said:
I've touched on this question before but I may have been using some wrong terminology.
On my S3 I have successfully created a BT pairing with a BT Audio Device use which has a steroe out fed into my car's head unit's Aux In.
So, it is Auto-Paired. That is, when I step into my car and turn on the ignition thus powering up the BT Audio Device the paring is available to be used for Media Audio.
However, in order for my phone to route audio to the BT Audio Device I must enter the phone's BT menu and tell the phone to connect to the Device for Media Audio.
I can either do this through the notification pane to see pairings then tap the pairing to use for Media Audio or I can go through settings->BT and do the same thing.
Either way, it's a huge PITA to do this every single time I get into my car.
There has got to be a way to have the phone automatically route Media Audio through this BT Audio Device upon detection. My previous two phones had nowhere near the ability of my S3 but they had no issues whatsoever with automatically pairing and routing audio to this BT Audio Device.
Is the S3 really this stunted in the BT department? If so, is there an app that fixes this stupidity with grace and non-intrusiveness?
Click to expand...
Click to collapse
I feel ya, in the past, all I had to do was toggle BT on and go, now there's two or three extra steps which almost defeats the use of a toggle.
I just started searching for some answers and am honestly surprised no one else has made a big deal about this. If I find something, I'll post it up... For now, going to take a look at some system files and build.prop stuff, but it's not really my department.
Got some NFC tags and NFC Task Launcher hoping I could circumvent the BS with a hardware hack. But no, the best this does is auto toggle the BT radio and open the device selection screen where 2 more taps are required to actually use the device for media audio. Any new insight out there? Considering Tasker app but it is rather expensive and no free version to see if it does the trick.
My Bluetooth Auto Corrects Just fine to my cars Bluetooth... Toggle on and go. Running AOKP currently but it worked properly on stock, stock rooted, and Synergy as well.
I haven't gotten a chance to try this yet but I probably will tomorrow.
Tasker forum post indicating the problem is well known, prevalent and hardly any fixes exist:
https://groups.google.com/forum/?fromgroups=#!searchin/tasker/bluetooth$20audio/tasker/TLsjT9Exle8/ZLlgvEn5vUUJ
An app that forces the connection amongst other things:
https://play.google.com/store/apps/details?id=a2dp.Vol
A Tasker plugin leveraging the force connect code which happens to be GPL'd in case any of our fine developers would like to start making ROMs that address this major drawback of using a S3:
http://code.google.com/p/a2dp-connect/
crabapples said:
I haven't gotten a chance to try this yet but I probably will tomorrow.
Tasker forum post indicating the problem is well known, prevalent and hardly any fixes exist:
https://groups.google.com/forum/?fromgroups=#!searchin/tasker/bluetooth$20audio/tasker/TLsjT9Exle8/ZLlgvEn5vUUJ
An app that forces the connection amongst other things:
https://play.google.com/store/apps/details?id=a2dp.Vol
A Tasker plugin leveraging the force connect code which happens to be GPL'd in case any of our fine developers would like to start making ROMs that address this major drawback of using a S3:
http://code.google.com/p/a2dp-connect/
Click to expand...
Click to collapse
I haven't had any trouble with bluetooth devices reconnecting to my phone as soon as I power them on. I'm running cyanogenmod 10 rom.
Also you can get free trial of tasker from here tasker.dinglisch.net/download.html
zxsix said:
I haven't had any trouble with bluetooth devices reconnecting to my phone as soon as I power them on. I'm running cyanogenmod 10 rom.
Click to expand...
Click to collapse
It seems the issue may be primarily with BT Audio Gateways. I don't have this issue with my laptop at all and I'm imagining car head units rarely see this problem.
That said A2DP Volume App fixed this issue for me. Once configured I did have to manually set the device to use media audio one last time before A2DP Volume started doing it for me. I configured NFC Task Launcher to kill wifi, enable BT and launch A2DP volume when it contacts the tag in my car and it works perfectly. Since NFC Task Launcher front ends into Tasker and Tasker has the A2DP force connect plugin available I'm seriously considering getting Tasker for all the other cool features it can do besides scratching this particular itch.
crabapples said:
I've touched on this question before but I may have been using some wrong terminology.
On my S3 I have successfully created a BT pairing with a BT Audio Device use which has a steroe out fed into my car's head unit's Aux In.
So, it is Auto-Paired. That is, when I step into my car and turn on the ignition thus powering up the BT Audio Device the paring is available to be used for Media Audio.
However, in order for my phone to route audio to the BT Audio Device I must enter the phone's BT menu and tell the phone to connect to the Device for Media Audio.
I can either do this through the notification pane to see pairings then tap the pairing to use for Media Audio or I can go through settings->BT and do the same thing.
Either way, it's a huge PITA to do this every single time I get into my car.
There has got to be a way to have the phone automatically route Media Audio through this BT Audio Device upon detection. My previous two phones had nowhere near the ability of my S3 but they had no issues whatsoever with automatically pairing and routing audio to this BT Audio Device.
Is the S3 really this stunted in the BT department? If so, is there an app that fixes this stupidity with grace and non-intrusiveness?
Click to expand...
Click to collapse
You can fix this relatively easy by getting the app Tasker. I use it to do things like automatically start the music player I want when headphones are plugged in, to turning up the brightness automatically when I am getting an incoming call, etc. I am fairly certain you could set up the program to do whatever you want via bluetooth if you fiddle with it.
Gluck!
mdt73 said:
You can fix this relatively easy by getting the app Tasker. I use it to do things like automatically start the music player I want when headphones are plugged in, to turning up the brightness automatically when I am getting an incoming call, etc. I am fairly certain you could set up the program to do whatever you want via bluetooth if you fiddle with it.
Gluck!
Click to expand...
Click to collapse
LOL, if you had only read the rest of the thread...
Yeah, Tasker cannot do this OTB but with the A2DP Connect Plugin it can. Or you can just run the A2DP Volume app and do the same for free.
That the A2DP Connect code is GPL it would be super sweet if our developers incorporated the magic into the ROMs so that a base install didn't need apps to do something so simple as automatically route media audio to BT gateways.
This happens to me when I use the wrong settings in my cars head unit. My Toyota gives me the option to pair as a multimedia device, a phone or both. If you set it up as just a multimedia device then you won't have some functionality. Check your head unit manual and try to re-pair. You might have to delete the existing pairing for it to work right.
rfmodeler said:
This happens to me when I use the wrong settings in my cars head unit. My Toyota gives me the option to pair as a multimedia device, a phone or both. If you set it up as just a multimedia device then you won't have some functionality. Check your head unit manual and try to re-pair. You might have to delete the existing pairing for it to work right.
Click to expand...
Click to collapse
Yeah, it's not a head unit, it's an audio gateway that basically is just a BT receiver with a stereo out and no interface so it is what it is with no configuration options. This issue with the S3 appears to be primarily related to these types of devices.
crabapples said:
Yeah, it's not a head unit, it's an audio gateway that basically is just a BT receiver with a stereo out and no interface so it is what it is with no configuration options. This issue with the S3 appears to be primarily related to these types of devices.
Click to expand...
Click to collapse
Oh okay. When I look under the bluetooth menu in CM10 I have a paired connection that I named Car Multi-Media and if I look at its settings I see profiles called Phone audio and Media audio. I'm guessing you just have a Media audio profile. Not sure how to help you there. Sorry.
With my iPhone I just had a kensington dock connector that charged + had an AUX out - so I got power + audio through the dock.
With Android it's clearly not nearly as easy
My car does not have native bluetooth but it WOULD be nice to take this opportunity (if it makes sense) to be able to effectively use my android phone for audio, gps nav (spoken directions) and handsfree calling (or at the very least, receiving calls)
What would be the best way to accomplish this? My AUX-in is in my center console, covered... so I could stick a bluetooth->3.5mm adapter there..
This SHOULD work for audio, GPS and hearing calls - but what about speaking on the phone? Phone might be in pocket - but even if in a holder mounted on windshield would mic be positioned properly to speak into it?
One thing i would really love is to be able to use GPS navigation while listening to radio, but I'm not sure this is possible. When using GPS I either have to ignore voice prompts or switch to AUX and be music-less or restricted to music from phone...
FYI I have a 2007 Accord - the AUX port was added in after
I have an aux port and I don't think you are going to be able to do all the things you want through the Aux port. I use the aux port with a HTC Stereo clip and that streams just music to the aux port from any bt device (I have a N7 as well). That is all the Aux port will do and all I want it to do. However saying that I also have a Parrot minikit neo which connects automatically when I have my llama profile to switch on bt when disconnecting from any wifi, which usually means home or work. Using the Parrot or anything like that, you will be able to use navi for voice prompts and answer calls at the same time.
No not ideal, but works for me. No it's not seamless, but it works bottom line. lol
If anyone else has a setup, please post up!
I don't think there's a seamless way to accomplish what you're trying to do. I've got a 2010 Accord and use a windshield mount and AUX for music/GPS. Works well for me. I don't think there's a way to listen to the radio and GPS nav unless you're just using the N4 speakers.
I've been using this in my car.
http://www.amazon.com/XtremeMac-InCharge-Auto-Bluetooth-iPhone/dp/B005UKLW0W/ref=pd_sxp_grid_i_2_1
The mic is located on the huge male end of the 3.5mm plug and if placed or mounted properly(somewhere near the driver's mouth), you may be able to talk clearly as well.
I don't talk on the phone while I drive, so I disabled that function and have never used it.
This item was on sale a couple of weeks ago for $20 on one of those deal sites.
Also bought a 3.5mm extension cable to plug into the aux port on the stereo.
I haven't figured out how to have the radio and GPS directions come out the same speakers either.
I just got this yesterday:
http://www.amazon.com/Belkin-Blueto...56633664&sr=1-1&keywords=belkin+bluetooth+car
It mounts on the dash and has a microphone built in. It is powered (and the power cable includes an extra USB port so you can charge your phone while this thing is plugged in). I am in love with this thing, it works beautifully. I paired it once and since then, when I get in my car and push the button on this device, it automatically connects to my phone. If I'm talking on the phone or listening to music, the audio is automatically redirected to my speakers (if you're on a call and don't want it on your speakers yet, just don't push the button on the bluetooth adapter yet).
It works to control the phone too, I can push twice to go to the next song (works in google music and pandora, haven't tested others), click once to pause, hold for 2 seconds and release to pull up voice dailer.
Sound actually seems a bit improved as well compared to the AUX out on the phone. I find the AUX out volume to be extremely low, and this seems to be a bit louder, although I haven't done any actual tests to confirm.
I built a custom dock that has a charging cable built in, so I get in my car, set it on the dock, hit the bluetooth button on the adapter, and I'm listening to music and making calls. No wires to plug in, no hassle. It's great.
A couple of things I still need to test though. I haven't tried GPS while listening to music yet, so I can't confirm that functionality. I also have not tried other voice functions from the voice dialer to see if I can have it play a certain song or other voice commands.
Kaitlyn2004 said:
With Android it's clearly not nearly as easy
Click to expand...
Click to collapse
No... its not. But if you want easy... this is the way I recommend you go.
Unless your current in-dash stereo is an expensive aftermarket unit, just replace it with a new bluetooth enabled model. They are dirt cheap now-a-days and can be had for around $100-150.
While you may save "a little" money going with some crippled add on solution, a new unit will give you all that you are after plus a USB port for charging, all in a simple, single interface. Also, with add ons you may run into ground loops issues and other nonsense (which will take more money and time to address).
just my 2ยข... but I have considerable experience with a variety of add on bluetooth stuff, and if my head unit wasn't a $1500, double DIN, standalone GPS/DVD unit, I'd have yanked it and put in a cheap, new bluetooth capable unit in a heartbeat. I was talking to my brother on Christmas... he was in Starbucks getting his daily fix. Then walked out to his car where his new $150 Sony automatically picked up the conversation upon starting the engine, and I didn't miss a syllable.
Radiocore said:
I just got this yesterday:
http://www.amazon.com/Belkin-Blueto...56633664&sr=1-1&keywords=belkin+bluetooth+car
It mounts on the dash and has a microphone built in. It is powered (and the power cable includes an extra USB port so you can charge your phone while this thing is plugged in). I am in love with this thing, it works beautifully.
Click to expand...
Click to collapse
I've had one of these for a month or so. It works quite well, though I have some audio/volume issues due to my aux input being a soldered hack into my old Saab's radio. Not Belkin's fault. It works well for calls, pauses Spotify when Google Gnav is announcing turns, can pause or skip songs in Spotify, etc. $30 well spent.
Though after reading this thread, I'm thinking of changing out the car radio head unit for one that has integrated Bluetooth to do away with my hack. Found a well reviewed Pioneer on Crutchfield and Amazon for around $100.
Sent from my Nexus 7 using Tapatalk 2
Check out JVC as well. They have good support for Android, with Pandora, and a dedicated remote app too.
Yeah, I don't seem to have any of those volume issues, and I get now grounding feedback or anything.
A new headunit of course is the ideal solution, but I didn't want to give up my setup quite yet for that option, and right now the Belkin has treated me great.
I did test navigation while music is playing (google music app), it just lowers the volume of the music while she talks over it. Works just fine in my opinion.
Holding down the button on the Belkin brings up the voice caller, and it strictly only lets me do call commands. Anyone know how to change this so that holding the button on the bluetooth device will open a different app on my phone? Specifically, Google Now.
For those with the belkin, does it automatically connect when you get into your car?
Kaitlyn2004 said:
For those with the belkin, does it automatically connect when you get into your car?
Click to expand...
Click to collapse
I've been using the Jabra freeway Bluetooth speaker. Works great with excellent battery life. Auto connects when you get in car.
Hey,
I am having trouble with my Pioneer CD-BTB200 Bluetooth Adapter, which is a common problem, according to the very few available threads on the internet.
This also didn't work with any other Smartphone before i.e. Samsung S3 or Blackberry Bold 9700.
Cliffnotes:
-pairing, media streaming (different source) and receiving and making calls works great! No issues there
-transfering the contact list results in a big mess, I have to dig in there if I can figure it out or if I just transfer one contact after another....
-now for the problem.......I installed Cyberon Voice Commander because it gives me the best behaviour and voice recognition since I am a native German speaker. Google, Dragon and AIVC don't work really well. But it doesn't matter which voice assist app I use, because it is the Bluetooth adapters fault. The Nexus 5 is rooted and runs stock Kernel with KitKat 4.4.2.
When I press the voice dial button on my Pioneer AVH-P5000DVD deck it activates the Cyberon Voice Commander app (or whichever is set as default). so far so good, that is what I want.
But! the dialog between me and the phone is almost impossible because the output volume over the car speakers is way to low. I have to literally pick up the phone and look at it's display to see what the voice commanding app is doing because you have to wait until it is finished asking what I want to do. (just holding a phone is illegal in Germany)
Assuming the app understood me right and starts dialing everything turns to be fine from that point because the volume of the actual call is perfect!
When the phone talks back to me I have to crank the volume all the way up to understand it a little bit and then turn it back down fast before the phone call starts or it'll blow the speakers out....since my car is quite loud when on temperature I don't think I will understand anything when I am driving.
I heard that the app TASKER could be programmed to raise the Bluetooth volume at a certain point and then lower it again. I checked but it only goes up to 15, which I already have set before with the stock volume slider. Additionally I have no idea how to configure Tasker to (maybe) get rid of the problem.
Has anyone ever heard of a similar problem and / or has an idea how to handle it?
Again, it's only the voice command prompts that are way to quiet when I start the voice dialing function via Bluetooth, everything else is fine.
Fixed the issue with SoundAbout!
https://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix&hl=de
Now the voice prompts play loud and clear over the car speakers! Every other volume managing app failed miserably!
I used the latest Beta Version btw, going to buy the Pro Version soon.
http://soundabout.userboard.net/f8-download-beta-versions
I did very little changes to the settings, if anyone is interested I can hook you up with some screenshots
sutobe said:
Fixed the issue with SoundAbout!
https://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix&hl=de
Now the voice prompts play loud and clear over the car speakers! Every other volume managing app failed miserably!
I used the latest Beta Version btw, going to buy the Pro Version soon.
http://soundabout.userboard.net/f8-download-beta-versions
I did very little changes to the settings, if anyone is interested I can hook you up with some screenshots
Click to expand...
Click to collapse
I have this issue as well. SO what did you have to do with this app?
Hi,
anybody outhere with hearing aids who can make calls with their hearing aids as audio output and a working microphone?
If so, could you please state what
- hearing aids
- phone
- OS version
- and if you had to do something else (install an app, add a setting, ...)
?
Thanks!
I recently got myself a OnePlus 9 Pro and after pairing my Starkey HAs the phone outputs all audio to the HAs w/o trouble, even in a call -- but there's no microphone, hence in a call I hear the other party but they cannot hear me.
While the HAs are recognized as such, Accessibilty does not offer a setting for HA compatibilty, nor is there a way to pick the audio input device or at least check/modify the microphone volume.
All info I can find seems outdated or misses the point entirely (using HAs to make a call).
To answer my own question: w/ OOS 13.1 sound is routed directly to my hearing aids and one of the phone's built-in microphones picks up my voice (need to experiment further to find out how to hold the phone to get the best quality).
I currently try to figure out if it still works that way if I flash LOS ...