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.
Hello there!
Recently I have encountered a strange issue with the wired headphone stereo balance. The volume on the left side is as expected, but audio on the right channel is all but inaudible. It´s there, but extremely quiet. If I set the volume to maximum, audio on the right ramps up to being listenable (with what would usually be a low to low medium volume setting)...while the left is blazing like crazy, of course.
Using a stereo test MP3 (ping pong sounds, basically), I could verify that the channel seperation is correct, just to rule out that it´s a headphone jack/plug problem (i.e. the plug making no contact with the correct connectors inside the jack). Or, to put it simply, both audio channels do indeed get to the correct side of the headphone, just not enough on the one side.
I have no idea what could have caused this. Stereo balance was definitly working correctly the one time I tried wired headphones on the stock ASUS ROM, way back before I unlocked, rooted and installed custom ROMs. I haven´t tried it since, until a couple of days ago and that´s when I noticed.
Things I´ve tried since then:
- Dozens of different headphones, headsets, adapter cables. All show the same problem.
- Tried to clean out the headphone jack as best as possible.
- I even filed down the tip of one plug a bit to maybe get a better connection, but the connection itself doesn´t seem to be the problem.
- Factory resets, full wipes, different ROMs (stock, CM, CROMi).
- Different audio DSPs.
- A LOT of audio related apps (Volume+, EQs...)
- Audio players with built in balance control. These do indeed shift the stereo image to the right side, but don´t make the right channel itself louder, which results in a very quiet, kinda mono-y, hollow-y sound at normal volume levels.
I am assuming there is a hardware problem, and I assume it´s not the headphone jack itself, but something else in the circuitry.
I really, really, really don´t want to RMA the thing, since it took me *weeks* of discussion with ASUS support to get it unlocked in the first place (wasn´t able to, due to the infamous MAC/server mismatch thingie), and I don´t want to get it back with a new mainboard and perma-locked.
So, my questions are: What else can I try? Is there a way to boost the one faulty audio channel? Maybe by editing some system file or writing a script or something?
I´m unlocked, rooted and running CROMi-X 4.3b4 now (which is going to be great, once it matures, btw).
Thanks!
i do not know how many of you know about this:
Differential Sound is a feature in Viper4android - and i think many people do not know a use for it:
it can be used to correct the runtime in between your ears and your speakers in your car.
As the speaker in your car are at very different distances relative your ears (as a driver) the sound stage gets lost ...
People do buy high end stereo systems for their cars to get this feature ...
i was searching very long for this - until I found out that Viper4android does it (again - )
Try it out in your car - set the effect time to 2-5 ms and wonder about the little magic trick -
even though i use high end speakers and amp in my car - this little effect improved the sound by light years ...
(i got no connection with viper4android but am so happy with it, that i want to spread the word)
Cheers
hf
hope this can be used with a phone only connecting to Aux in of car stereo. Or is there any other way?
hainfelder said:
i do not know how many of you know about this:
Differential Sound is a feature in Viper4android - and i think many people do not know a use for it:
it can be used to correct the runtime in between your ears and your speakers in your car.
As the speaker in your car are at very different distances relative your ears (as a driver) the sound stage gets lost ...
People do buy high end stereo systems for their cars to get this feature ...
i was searching very long for this - until I found out that Viper4android does it (again - )
Try it out in your car - set the effect time to 2-5 ms and wonder about the little magic trick -
even though i use high end speakers and amp in my car - this little effect improved the sound by light years ...
(i got no connection with viper4android but am so happy with it, that i want to spread the word)
Cheers
hf
Click to expand...
Click to collapse
Yep - just connect your phone via aux-in
Sent from my GT-I9505 using XDA Free mobile app
Thanks for this my friend I have a 1200Watt Sub in my car with an amplifier and i am always looking for best settings for the in car sound
Do you have any other recommendations which i can do on Viper4Android for a better experience?
Hate to say it but I tried viper several times but was always a hassle to set it up and get it working correctly. because I change ROMs often its easier to just use poweramp and with dvc over Bluetooth enabled it also does this and evens out the speakers... Works really well.
@1qazwsx4 - yep thats one of the downsides to V4A ... sometimes its easy to install - sometimes its quite a hazzle (depending on your rom)
as i am at the moment stuck on Stock ROM: does poweramp´s dvc? works also on headphone out or only over bluetooth
Hi guys,
since the Update to 6.01, I have experienced, that the audio quality of the device (Android Auto, sound over USB) got worse.
I have a soundsystem in my car and I definetely hear the difference....
Somebody knows something that samsung changed something into the software in therms of sound quality?
Perhaps somebody have had a look into the code and see if samsung is doing some compression things or something like that...
slg60 said:
Hi guys,
since the Update to 6.01, I have experienced, that the audio quality of the device (Android Auto, sound over USB) got worse.
I have a soundsystem in my car and I definetely hear the difference....
Somebody knows something that samsung changed something into the software in therms of sound quality?
Perhaps somebody have had a look into the code and see if samsung is doing some compression things or something like that...
Click to expand...
Click to collapse
I didn't like the sound quality in lollipop neither. What i've found is that if you push the phone volume all up it sound even worse, all distorted. Are you using it full volume? Try 75% on the phone and amp up your system gain instead
What I found out is, that I have set the dynamic range compression on in spotify, with turning it off, it sounds way better now....
Connected via usb directly to android auto capable head unit there is no chance to adapt things on the mobile, also no adaption of volume.... seems that sound directly gets bitwise transported to the head unit, so no dac involved etc.... Also adapt sound feature is not working for that.... I only have to be sure that the music gets directly transported to the usb, without compression from the music app etc....