My droid would use whatever BT headset (stereo or not) for the phone when my headphone jack was also in use (to use car stereo) for audiobook player.
I have new Fascinate and I swear it did the same until I rooted it. Regardless, it will be close to a deal breaker if I cannot find a solution to this.
Even if the headset indicator is ON, the sound still goes to the headphone jack, RIDICULOUS
In my opinion, plugging into headphone jack should only take over media type output (music, audiobook player, video) and LEAVE PHONE ON BLUETOOTH. We should at least be able to chose this behavior in a setting.
So is this a Samsung screwup? do other Samsung devices behave this.
How hard would it be for a dev to build an app to FIX this on Fascinate.
I thought I was the only one with that situation... I would love to know the answer/fix, however I have a feeling someone will be by soon to move this to the general forum...
I actually wanted the opposite. Overall, I liked how bluetooth was handled on my old chocolate and was surprised by the differences in eclair. I expected my bluetooth to be able to grab all audio, regardless of what apps were running. For instance I wanted to use my BT with a fring call. Seemed sensible!
Anyway, I went searching, and the prevailing opinion was that bluetooth was locked up until Froyo (and tightly tied to actual calls).
Does anyone know if audio is handled in a gracefully way in current AOSP or CM?
Swyped w/ XDA App. When in doubt, mumble.
soba49 said:
I actually wanted the opposite. Overall, I liked how bluetooth was handled on my old chocolate and was surprised by the differences in eclair. I expected my bluetooth to be able to grab all audio, regardless of what apps were running. For instance I wanted to use my BT with a fring call. Seemed sensible!
Anyway, I went searching, and the prevailing opinion was that bluetooth was locked up until Froyo (and tightly tied to actual calls).
Does anyone know if audio is handled in a gracefully way in current AOSP or CM?
Click to expand...
Click to collapse
I believe that my Droid 1 behaved my desired way on 2.1 and 2.2, can't remember if I used this way on 2.0...
I was assuming this was a 'problem' on Fascinate or Samsung, not android OS in general.
I thinj its a problem with fascinate. I was driving for 5 hours last week and I had bluetooth connected to my garmin and used one of those cassette thingies to play music from my fascinate. Sometimes I were able to talk without unplugging the headset.
Another reason I suspect its fascinate is cuz when I use my old blackberry headphones I have unplug and replug to use it for conversations.
Btw whats good stereo heaphones with mic that works with the fascinate?
Sent from my SCH-I500 using XDA App
I have a friend with a Vibrant and his apparently does NOT have this problem, so I am wondering if a Bluetooth file from his system might work on my phone.
There are 3 BT files in system dump:
BT OPP
BT services
BT test mode
so is one of these the file that would determine what path audio would take in any given situation? (e.g. headphone jack occupied while BT headset connected, desired paths media>headphone phone>BT)
I REALLY need to fix this before my 30 days are up or phone probably going back.
I got my hopes up when I discovered the 'secret menu', but I don't see any setting in there that seems appropriate.
I've tested with the superclean 0.7 DL30 rom and this same problem still exists
Please let me know if anyone finds a solution.
[email protected] said:
i've tested with the superclean 0.7 dl30 rom and this same problem still exists
please let me know if anyone finds a solution.
Click to expand...
Click to collapse
stupid ass samsung friggin morons!
It looks like this is a problem on other Samsung Galaxy S phones as well, see a thread and app someone made in the Epic forums.
http://forum.xda-developers.com/showthread.php?t=842571
it is just the phone app
this problem is extremely frustrating. if i have headphones plugged in the mic works just fine. the mic is only turned off when i use an AUX cable. It would be nice to be able to drive and not have to worry about unplugging the AUX cable everytime I wanted to use my phone.
I downloaded the Epic app they made over there but all it did was hard lock my phone with my first test. I dug into the code but I'm a wee bit over my head so I'll hit up the books and see if I can't work with the guy who made the Epic one to see about getting it working with our phone.
This was with the .7 superclean DL30 rom, I'd love for someone else to try one of the other DL30 roms and see if they have any better success.
I contacted the author of the app and he replied back stating he had a buddy with a fascinate test it and it worked fine and that it might be an issue with the busybox version included with the .7 superclean 2.2 rom I was running and that it relied on busybox having the pidof command. Later tonight I'll dig into this a bit more and post back hopefully a fix and instructions on hwo to ensure this is working
I got this working http://forum.xda-developers.com/showthread.php?t=842571
The Froyo version works just fine on the original DL30 leak and on rubiks .3 DL30 but does NOT work on DL30 super clean .7 or .9. In .7 I got a hard lock that I had to do a battery pull to fix and in .9 the app ran and looked like it worked, but the audio routing did not change as expected.
All credit to cicada, I did nothing more than test it
I have not tested this on any 2.1 ROMS
thande said:
I got this working http://forum.xda-developers.com/showthread.php?t=842571
The Froyo version works just fine on the original DL30 leak and on rubiks .3 DL30 but does NOT work on DL30 super clean .7 or .9. In .7 I got a hard lock that I had to do a battery pull to fix and in .9 the app ran and looked like it worked, but the audio routing did not change as expected.
All credit to cicada, I did nothing more than test it
I have not tested this on any 2.1 ROMS
Click to expand...
Click to collapse
I am on original DL30 leak and did NOT work for me... at least with Ambling Book Player. Not sure if it matters what app we are using to play media file. It shouldn't, but this whole problem should not exist. SAMSUNG morons!
Ok so i tried with my Rubiks DL30 ROM installed. The app opens up, no FCs or bricks or anything, but it doesn't work. I had my wife call me when i was driving, I picked up and she said she could hear me but I still couldn't hear her. I'm assuming that the car's mic is functioning but it still doesn't fix the issue. Is there a bluetooth adapter out there i can stick in the aux jack? Well i guess the first question should be, can the phone handle having two BT devices connected at the same time? i.e. hands-free calling and BT audio adapter
I'd say maybe try another full wipe and re-flash. I've switched over to the superclean EB01 roms, currently on 2.3 and hasn't had any issues with this working on 2.1, 2.2 or 2.3. I did have 2.2 initially not function with this tool, similar to what you reported above with it looking like it was working but not actually doing anything but a full wipe and reflash did the trick.
ok... thanks, at least you've run into that problem so i'm willing to give it another go. I'm currently on SC 2.4 so i guess i can be your guinea pig
I'm on SC 2.4 currently and had it stop working on me again. At work now but I'm going to try setting the app off and then back on, I have had to do that sometimes when flashing as the files get overwritten. This was working properly in SC 2.3
Hey man, thanks for the updates and info... you're really like the ONLY person that's giving me any hope on this. I thought the compatibility issues were busybox related? So I don't see why it wouldn't work on SC2.4
Would someone please fix this on Fascinate... ? pleeeeezzzzzz
hi guys i think i saw a thread or post before about this but i am not quite sure, and hate to post the same question that has been answered before but i couldnt find that.. anyways i am running straight up axura 2.3.1 and i noticed whenever i play music on it, i would only hear it on headphones/earphones but not on the phone speaker. any ideas?
thanks i appreciate the help alot
It is like stuck on headphone mode even headphone isnt plug. Ive odin back to stock, reflashed and nothing works
Edit. I dont have any system sound. i can hear alert sounds and all. hmmmmmmm any ideas?
Unless you have the speaker turned off (which I doubt) you may just have a bad flash I have this rom on my wife's phone and I just checked it works fine. So reflash is probably the easiest and fastest way to fix.
oka1 said:
Unless you have the speaker turned off (which I doubt) you may just have a bad flash I have this rom on my wife's phone and I just checked it works fine. So reflash is probably the easiest and fastest way to fix.
Click to expand...
Click to collapse
i reflashed and back to stock, flashed bionix, axura. still no media sound and system sound. i highly doubt its axura itself, since i flashed it a couple times before and had no/little bugs but not anything with the sound
edit: i was researching and found that somewhere between the line, it might be this issue
http://forum.xda-developers.com/showthread.php?t=991465
how can i flash that?
Can anyone who has the AT&T Galaxy S II confirm if it correctly handles call recording using the handset mic/speaker, speakphone, and bluetooth?
Some other threads on the generic Galaxy S II are positive (http://forum.xda-developers.com/showthread.php?t=1069217), but you just never know what AT&T and the other US carriers will do to their phones.
Thx.
I have no option to record a call.
On the generic Galaxy S 2 thread, folks are having good luck with Callrecorder By Dsoft.
Maybe give that a try?
Callrecorder S By Dsoft works great with the handset but can be very very flaky when recording with a bluetooth headset. sometimes it works great sometimes you'll lose the other persons audio and all you hear is a loud hum.
Total Recall is the same. i went through all of the tests and either got the same as with Callrecorder or when it did work the other persons audio was so low as to be inaudible.
actually i take that back, total recall doesn't seem to want to work through the handset at all.
Just a tag to keep this information updated.
This works wonders on my SGS2 w/ UnNamed v1.3.1 & Entropy DD_12/01/2011
Hi guys, I have asked this question in various ICS/Miui 4 threads with no help.
Any time I use my phone via headphones to make calls, on any ics rom, I get horrible call quality. I have tried just about every ics/miui(4) rom out there, flashed the mute/unmute patch...nothing works. When the party I call answers, I don't hear it, there's a 1-2 sec dropout, and then when they talk, it cuts out, just like being in a no signal area. I have full bars, and the problem is only on headphones, and as soon as I take it off and put it up to my ear, it's clear. Also, if I go to a 2.2 or 2.3 rom, all is good, and the headphone jack is fine because music plays fine (under ICS), it's only a phone call issue.
Anyone else experience this?
Also, latest rom I am on has 2 different phone apps...both= same issue...
This is the exact same thing I'm facing on all ics roms and it seems no1 knows how to fix it. Hope somebody does soon.
Sent from my T959 using XDA
Running SD 6.0.1 with SD kernel 5.0.2 and I've flashed the 35B bootstack.
Phone calls, notifications, etc., all play fine through the speaker, and through the headphones. However, I cannot hear phone calls through the earpiece. Mic is working fine - the caller can hear me, but I can't hear them.
I've read about headphone jack issues, although I never use headphones. But I exercised the jack anyway. No luck. Tried wiping cache and Dalvik cache also.
Could this be software or is it most likely hardware?
Anything else to try?
To determine if it is a hardware issue try another ROM or simply restore your obligatory backup of the stock ROM. Report back. If it doesnt work on stock its most likely a hardware issue. If it does work on stock, its a ROM or kernel issue.
Haven't flashed back to stock yet, but I did clean flash XDABBEB's ROM. So I changed ROM, kernel, and got rid of xPosed. Still no sound from the earpiece. Probably hardware.
Edit: Restoring back to full stock made no difference. Warranty replacement is on the way.