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
Hello all,
I was hoping someone could point me in the right direction to a Gingerbread ROM with a working media start/stop/call end headphone button (I'm using the OEM headphones that came with the phone) and 911. Both of these issues are documented bugs.
I've tried CM 7 and a couple of MIUI ROMs and the non-functioning headphone is pretty much a deal breaker, as I use my Vibrant for podcasts more or less everyday; the fact that 911 doesn't work just seems dangerous.
I've scanned lots of posts for different ROMs and neither issue really seems to come up telling me one way or the other and I don't have a day to load every single available GB ROM and figure it out via trial and error. Search hasn't been particularly revealing either.
For now, it's back to Team Whiskey NextGen v2, but I've tasted Gingerbread and I like it.
Thanks for your time.
The 911 issue should be fixed in the future. As for the head phone button issue - it will never be fixed until the GB source drops for our vibrant.
The button function is a kernel issue, not a ROM issue. The current kernels are ports of other phones hacked to work for our phone (thus another reason not so good battery life). (IE: I9000 kernels)
Don't hold your breath - don't think GB source will ever drop for our phones - Samsung dropped us like a wet diaper.
Does the fascinate have an in-line microphone on the headphone jack?
I'm trying to use a Square card reader which uses the jack in-line microphone but it doesn't work. I am running CM7.1 nightly 122, so I'm not sure if it's a problem with the ROM, my specific phone, or the fascinate i general. The card reader does work in my iPod Touch and my wife's Captivate (also running CM7.1, stable).
Anyone have any insight? Thanks!
I don't know about CM7.1 but the fascinate does have an inline mic, i've used it... stock rom, and GeeWiz both work.
Redeyes was on irc and trying to get it to work. It seems that the inline and ground (or something similar to that) have been switched in cm7 for some reason. Such devices should still work on touchwiz based roms.
Afaik there is no fix for cm7
Sent from my SCH-I500 using xda premium
I wonder if it could be fixed for AOSP? That would be most excellent IMO, I'd like to be able to use that feature of my headphones, but not bad enough to run a stock rom.
It does work on my Captive i897 running cm7.1 stable, perhaps that could be looked into to get a fix for the fascinate?
Having the same issues
I have also been having issues with the square reader. I did see someone suggest once that the plastic ring around the jack may have been impeding the connection, but after removing it, it still does not work. I've tried stock rom on the thing and I've tried CM7 stable and nightly 112 with no progress. I really hope this thread gets noticed a bit more so the problem could possibly be fixed in the near future. I'm currently on CM7 stable with no special radios added or anything. Here's hoping that something comes along soon.
I know it doesn't work on any GB AOSP builds, but I believe I read that external mics are working on AOKP build 27. I'm gonna try today...
~~~~There is no spoon~~~~
a bit more info,
Mic headphone jack does not work on any AOSP build EVER! JT never got it working properly and no one has ever fixed it. This means no headphone mic on ICS or GB AOSP builds, no CM anything.
This was all to get the square up reader working. I decided to flip the ground and mic wires on the square adapter itself, this did not work. Finally I loaded an AOKP build on a Droid Incredible and the same build on my Fassy, the Inc worked fine with the square app and mic worked. Fassy, no go.
In the end, the mic isn't active and it most likely will never be fixed. Time to move on I suppose.
Hello everyone. I have quite a big problem with the audio on the Galaxy Vibrant when flashing to JB 4.2.1 with CyanogenMod 10.1. Even with bare CM10.1, and whether with or without installing the gapps package, the audio (phone or music) would sound slower-paced and significantly distorted.. I guess the best way to describe that is with an example: a song sung by female vocalist would sound deep and a bit slow, and it would sound like that through the speakers or earphone. Could it be that the phone doesn't have enough processing power or appropriate audio driver? At first I thought I blew the speakers but then audio works just fine if flashing back to stock Froyo. I even flashed CM 10.0 stable version to find the same problem; in fact CM10 was even worse because in addition to audio distortion, the keyboard driver didn't work. CM10.1 seemed to work ok except the audio is not acceptable/usable. After a few times flashing back and forth I'm convinced that something is wrong but, being an Android noob I can't say what its problem is. I haven't tried ICS yet but kinda don't want to go with ICS.
I also notice that once flashed to CM10.1 the home button doesn't work anymore.
I looked around a bit and even googled for similar problem but I can't believe my Vibrant seems to be the only one with the problem. With the collective knowledge of smartphone gurus here, would someone please lead me to the light if you know what the problem is. Thanks a lot.
Hi guys,
Got a strange issue since a month.
When I get called the caller sounds very disorted and there is a lot of noise going on. It's barely understandable.
Same happens when I call someone.
The problem doesn't always occour but it's way too often to simply ignore it.
When I hang up and call back directly afterwards everything is fine.
I'm running Endrohix on my SGS3 atm.
This also happened to me with Archidroid and other ASOP roms. Haven't tried Stock Roms since I don't like them and there has to be another solution than going back to stock.
Greetings from Austria!
Change your kernel and check.
So i tried a lots of roms now. All sammy roms seem fine, as soon as it gets to AOSP (Omi, CM, Archidroid) the problem occurs. Tried a few kernel now, all seem to have the problem. Mainly tested Boffela and agni kernels and both have the same strange issue
nobody an idea?
Hardware
Seems like it's a hardware problem. Why don't you just go to a repair shop with that?
*#0*# test sound is OK??
How can it be a hardware problem if its working fine with sammy roms?
*#0*# gives me MMI-Error.
Had a chance to test on a few other cars today and found out something interesting!
Accepting a call by using the phone gives me a 50% chance to work, accepting it by the car radio always causes the sound bug
@verny94 ill test the setup in your signature and see if it works.. EDIT: just saw your's is sammy based, i'm pretty sure it will work
fold93 said:
How can it be a hardware problem if its working fine with sammy roms?
*#0*# gives me MMI-Error.
Had a chance to test on a few other cars today and found out something interesting!
Accepting a call by using the phone gives me a 50% chance to work, accepting it by the car radio always causes the sound bug
@verny94 ill test the setup in your signature and see if it works.. EDIT: just saw your's is sammy based, i'm pretty sure it will work
Click to expand...
Click to collapse
*#0*# is service menu. It must works but only on Sammy ROM.
I am really proud that my signature help you
Alright so I'm running Omega now and the sound problem is gone. But still i miss the speed of my Archidroid
BTW! I completly forgot to mention.. the strange noises only occour when i'm trying to talk over Bluetooth so if I make calls without bluetooth connection they work fine but if there is a hands-free or a car-radio involved the problems start
fold93 said:
Alright so I'm running Omega now and the sound problem is gone. But still i miss the speed of my Archidroid
BTW! I completly forgot to mention.. the strange noises only occour when i'm trying to talk over Bluetooth so if I make calls without bluetooth connection they work fine but if there is a hands-free or a car-radio involved the problems start
Click to expand...
Click to collapse
LMAO you mentioned the important part in the end
AOSP/CM based roms have had some bluetooth issues. Either not clear or breaks intermittently.
You can try Sammy or Sammy-based roms for better compatibility.
I've had this issue for a long time. It still occurs with the latest CM11. Here are more details:
https://jira.cyanogenmod.org/browse/CYAN-2884
Could you guys point me specific, tested Sammy ROM where that BT issue does not occur?