Related
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
Running one of the latest nightlies on cm7. Can anyone fire it up and see if it behaves as such for you? Works fine on my evo3d, but not nook sadness.
This might not help much, but it is working fine on my NC w/ 7.1 stable.
i appreciate it, i might have to drop back to get it working. i thought it may have something to do with slingmedia releasing a 'tablet' version of the app and nixing devices with high resolution but that doesn't seem to be the case
I've gotta say - I've been a little disappointed since rooting my phone a couple weeks ago. I haven't gotten any additional features that I wanted - though running Olympus Rom - it seemed everything ran a little snappier than it used to.
However, today I found out that my MHL adapter no longer works. With Olympus, I got an immediate crash, then after reboot - my adapter only worked to charge the phone. No HDMI out.
Then - after installing a Nocturnal Rom which was supposed to be stock with some tweaks, all I get is an immediate crash when connecting to my MHL adapter. Whether or not the HDMI cable is connected. WTF.
Can anyone tell me a ROM they've got working MHL with? I'm guessing the hboot might make a difference, since I never got USB host capability and some other features I expected out of Olympus Rom.
i think olympus used my kernel and older version had hdmi/mhl issues on hw002 phones, but was fine on hw001 (i test on 001)
flash my r13 release over ur rom - should fix your issue.
P0ll0L0c0 said:
I've gotta say - I've been a little disappointed since rooting my phone a couple weeks ago. I haven't gotten any additional features that I wanted - though running Olympus Rom - it seemed everything ran a little snappier than it used to.
However, today I found out that my MHL adapter no longer works. With Olympus, I got an immediate crash, then after reboot - my adapter only worked to charge the phone. No HDMI out.
Then - after installing a Nocturnal Rom which was supposed to be stock with some tweaks, all I get is an immediate crash when connecting to my MHL adapter. Whether or not the HDMI cable is connected. WTF.
Can anyone tell me a ROM they've got working MHL with? I'm guessing the hboot might make a difference, since I never got USB host capability and some other features I expected out of Olympus Rom.
Click to expand...
Click to collapse
Thanks Chad. Unfortunately, the new problem I'm having seems to be that for some reason - I can't flash a new kernel? No matter what I do - your old kernel shows up under the settings menu.
Thanks Chad - I was finally able to change my kernel to r13 using Flash Image GUI. MHL works great now!
It definitely seems to have been an issue with hw002. I still don't have USB host though - so if you find that it's possible to get us a kernel with working USB host for hw002 phones - please let us know.
I was running CM9 nightlies, which worked great. Then I flashed back to an official ROM and updated to the official ICS. Now I'm getting frequent disconnects when listening to music via bluetooth audio (bluetooth speaker dock, in-car bluetooth, etc). I never once had this issue with CM9 nightlies.
Anyone else experience similar issues?
EvilTelephone said:
I was running CM9 nightlies, which worked great. Then I flashed back to an official ROM and updated to the official ICS. Now I'm getting frequent disconnects when listening to music via bluetooth audio (bluetooth speaker dock, in-car bluetooth, etc). I never once had this issue with CM9 nightlies.
Anyone else experience similar issues?
Click to expand...
Click to collapse
I am too. Never had a problem with Gingerbread but just upgraded to the official ICS and it's freaking annoying.
I'll probably be switching back to CM9 nightlies. Even in its pre-beta state, it seems far more reliable than the official ICS ROM.
I do really like Samsung's music player app, though. I only wish I could install that on CM9 somehow.
If you are having BT disconnects on ICS,
Try plugging in the charger while testing it. The phone won't enter deep sleep while charging.
Some of the BT devices are not playing well with ICS.
My BT under ICS is about the same as under GB (all stock) except that my headset pause/play button no longer works under ICS.
daverup said:
If you are having BT disconnects on ICS,
Try plugging in the charger while testing it. The phone won't enter deep sleep while charging.
Some of the BT devices are not playing well with ICS.
Click to expand...
Click to collapse
Well, CM9 is ICS and I had no issues with my BT devices. It's something unique to the official ROM.
Maybe there's a way to modify the BT/sleep behavior on the official ROM, but at that point why not just use a custom ROM that works better?
EvilTelephone said:
Well, CM9 is ICS and I had no issues with my BT devices. It's something unique to the official ROM.
Maybe there's a way to modify the BT/sleep behavior on the official ROM, but at that point why not just use a custom ROM that works better?
Click to expand...
Click to collapse
I started having trouble with BT disconnects a few months back when I began testing Shostock2 and AOKP custom roms. I think custom roms are great, I just prefer Shostock2.
The charging cable plugged in work around will be my best suggestion for non-rooted ICS with BT disconnect issues.
My thread on this is:
http://forum.xda-developers.com/showthread.php?t=1609686
I'm still using Tasker to avoid the problem.
Probably something changed in the BT software somewhere...
I'm getting high voltage warnings with the stock ics and once the battery passes 35 percent it drains quickly. If I plug it to charge the phone just gets hot I have to restart to get it to charge
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
daverup said:
I started having trouble with BT disconnects a few months back when I began testing Shostock2 and AOKP custom roms. I think custom roms are great, I just prefer Shostock2.
The charging cable plugged in work around will be my best suggestion for non-rooted ICS with BT disconnect issues.
My thread on this is:
http://forum.xda-developers.com/showthread.php?t=1609686
I'm still using Tasker to avoid the problem.
Probably something changed in the BT software somewhere...
Click to expand...
Click to collapse
I installed the F1 Galaxy Nexus ROM (ICS 4.0.4) and never had any problems with Bluetooth disconnects. So hopefully it's fixed now. I'm dl'ing the latest ShoStock 4.0.4 and will see if it's fixed as well.
Not sure I'm using the correct terminology there, but I've read that the latest OTA update fixes a bluetooth issue. Was hoping it fixes the issues I've seen with random connection dropping between the phone and my bluetooth piece.
I've also read the new update breaks root as well as several people reporting poor battery performance after updating. So, was curious if anyone has just the bluetooth fix in a flashable file?
If you want to experiment, the second post in my kernel thread has a link to a kernel built using the stock Linux Bluetooth drivers instead of the HTC drivers. I would be curious to know if it fixes your or not problems.
Ah, nice. I will definitely look into it.
Do you know what else that OTA update supposedly fixes?
No idea. Waiting for the kernel source to see if anything was fixed there. No way to tell what they changed outside of the kernel.
oh so that was HTC's doing. I bought a cheap audio dongle to connect my phone to my car stereo and it works great, but every now and then the signal drops, so I chalked that up to my cheap Chinese adapter, not the phone.
I have a similar Probem, whenever I want to connect my DNA with the car radio, I always have to enter the code again, which is very annoying, have the 2:04 update on it was also previously with 1.15.605.2, maybe someone has an idea?