Related
Anyone ever have connectivity/inconsistent connectivity with Bluetooth on the Vibrant?
I never use it, but another XDA user mentioned they were having issues.
If you have had issues, what suggestions can you make?
The only connection problem I have ever experienced is sometimes with my phone, it will connect --- disconnect ---then connect when I first turn on my car (Infiniti m35) but it does that all in a matter of 5-7 seconds then it never has issues after that. Bluetooth is remarkable on this phone....... wish the GPS was as good. Running latest Bi-winning now
Me and my wife have both had the same issue with a paired device not connecting and you have to turn Bluetooth off and then back on and all is well. Doesn't happen often but can be a little annoying when it does. By the way my wife's vibrant is completely stock and I'm on cm7.
Sent from my SGH-T959 using XDA App
oka1 said:
The only connection problem I have ever experienced is sometimes with my phone, it will connect --- disconnect ---then connect when I first turn on my car (Infiniti m35) but it does that all in a matter of 5-7 seconds then it never has issues after that. Bluetooth is remarkable on this phone....... wish the GPS was as good. Running latest Bi-winning now
Click to expand...
Click to collapse
I quit reading when I saw m35. Love that car. Oka, want to hire a NC boy for cheaps? ha.
I use Jawbone Era and it randomly disconnects even when phone is in my pocket and bluetooth in ear. It reconnects a few times but mostly I have to turn the headset off/on to reconnect. Froyo 2.2.1 is better with Bluetooth than 2.2.0
It might be the headset though, our phonen is one of the FEW devices that has Bluetooth 3.0
Even the new LG G2X has 2.1 and not 3.0
I use bluetooth headset regularly on bionix 1.3.1. No disconnections, but the signal strength seems week as there is lot of distortion if the phone is in my pocket. So I have to always hold phone in my hand.
Sent from my SGH-T959 using XDA App
The issues I have (no matter what ROM I use) are Connect - Disconnect - Connect and then the stack is hosed. Have to reboot the machine to get Bluetooth to reconnect (Using Motorola H117). Also, can't figure out the exact pattern, but if I get a notification while bluetooth is on I turn it off and no more notification sounds... or ringing... or anything. I have to reboot to get sounds back.
I connect to my car stereo and sometimes I hear skipping. With my plantronics headset sometimes the signal gets weak if the phone is in my pocket
Sent from Glensta's phone
It is a weak signal in the phone. I have had several phone over the years and my old nokia flip phone was the only one that could do more then 3 feet without issues. My HTC kieser, HTC Shadow, N1 and my current SGS all have issues with my BT headset if the phone is in my pocket on the opposite side of my body from the headset. My old Nokia would let me use the same headset a room away so go figure.
One thing I have noticed is I if I try and transfere a file to any phone(other then the nokia) the file transfere always fails. It works to and from a PC but not to another phone of any kind(except the nokia).... very odd.
my bluetooth has been inconsistantly connecting since I started using 2.2.1 ROMs. it always worked fine previous to that on all the 2.2 ROMs I used.
zaphod_fl said:
The issues I have (no matter what ROM I use) are Connect - Disconnect - Connect and then the stack is hosed. Have to reboot the machine to get Bluetooth to reconnect (Using Motorola H117). Also, can't figure out the exact pattern, but if I get a notification while bluetooth is on I turn it off and no more notification sounds... or ringing... or anything. I have to reboot to get sounds back.
Click to expand...
Click to collapse
After turning bluetooth off on my phone or turning off my headset once or twice I frequently lose all sounds as well. Glad i'm not the only one.
I have the problem of sound not switching back to the speaker if I turn off either the headset or Bluetooth on the device.
How does Samsung screw something as simple as this up and it not be fixed after 4 official updates?
Nothing about Samsung's top notch screen is worth dealing with the headaches that come with their software. I'm trying to wait for the second generation dual core devices but, if I see good reviews on the Sensation, I am jumping off the Samsung emotional rollercoaster.
Sent from my SGH-T959 using XDA App
I have been back and forth with Samsung over the past 6 days attempting to troubleshoot this.
I have used a Motorola H117 and a Rocket Fish Stereo Headset that I have used with the phone. The following *almost* replicates the sound system crash every time.
1. Turn on Bluetooth headset
2. Press button
3. Voice Dial a contact
4. Phone conversation for 25 - 30 minutes
5. Disconnect phone conversation
6. Bluetooth remains connected for another 20 - 30 minutes
7. Turn off Bluetooth headset... no more sounds from phone.
Nothing fixes it short of a reboot of the phone.
I am running STOCK 2.2 KB5 right now. Factory Reset, No root, on the 5th Phone replacement from T-Mobile. I have an open case with 2nd Level support with Samsung however they have given me every excuse from "It's your headset" to "We don't replace phones". I have not asked for a phone replacement and I am earnestly trying to troubleshoot this problem with them.
If anyone has any additional information, please add it to this thread. I have passed the URL for this thread on to Samsung (I do not know if they will bother with hitting it) but I am cross posting at the T-Mobile forums as well as publishing on Twitter.
My only issue is that I have to manually connect bluetooth every time I get in the car. I don't know if this is a problem with my phone or with the bt-fm transmitter our both. otherwise, once I'm connected, music plays great.
Sent from my SGH-T959: Trigger 3.2, Overstock 2.4.1
Basically, my BT has been pm'sing on any 2.2.3 and up ROM.
zaphod_fl said:
7. Turn off Bluetooth headset... no more sounds from phone.
Nothing fixes it short of a reboot of the phone.
Click to expand...
Click to collapse
I have the same problem. I found an alternative to rebooting your phone to hear your sound again. Just play a visual voice mail message and hit the speakerphone button in the UI. Your sound will return. You can also play a google voicemail message and hit the speakerphone. It's not a fix but it will keep you rom rebooting your phone several times a day.
I use 2 Bluetooth devices on my phone.
Sony bluetooth headset:
Skips a lot, depending on what I have running. It's worse the more apps I have. To get the best performance, I usually need to end task everything that's running, clear all RAM, then run the music app again. I use the stock music app. I have had better performance out of several ROM's. I think it might be tied to the kernal used, depending on how much space is left (i.e. Bullet's 339mb kernal that I'm using with Simply Honey). Almost like there's a buffer issue.
Kenwood headunit:
I only use the bluetooth connection for handsfree while I'm driving. The only issue I've encountered is that the bluetooth connection is not always automatically restored everytime I get in my truck. If I go into Wireless and Network>Bluetooth, I can get the connection working again. It seems to always be a phone issue, not the headunit.
If you want a beta tester for something, let me know. I use both the headphones and headunit quite frequently.
We just got a '12 Honda Odyssey.
My Sensation works perfectly with the car's bluetooth but the wife's Vibrant is crap for connecting. Very disappointing. Came here hoping rooting her phone and installing CM7 would fix the problem, but that appears to not be the case.
Shame.
No more Samsung phones for us....
I use trigger 8/22 and the Bluetooth works better than ever. Stock gave me head aches
Sent from my SGH-T959 using xda premium
+1 for Vibrant bluetooth problems. I have a garmin nuvi in my car and sometimes it works, sometimes I get the connect-disconnect-connect, and sometimes it doesn't even try to connect.
I've tried stock, bionix 1.2, 1.3.1, and NextGen 2 and only bionix 1.2 seemed to work reliably.
When it works it is fine.
When it does the connect-disconnect-connect thing it sometimes works for phone calls be most often the audio is going through my handset even though the phone claims a BT connection has been made.
Finally in the case where the BT stack is so f'ed up that it doesn't even try to connect it seems like there's some serious battery drain that doesn't show up on the battery stats screen. I suspect the BT is stuck in some kind of loop that causes it to fail and burn lots of power.
The inconsistency is probably the most aggravating part of the whole thing...
I havent seem to run in to anyone with this issue.
I pair my phone to my car stereo fine in the stock GB rom. Play music and talk on the phone endlessly.
But with any ICS version so far, even official. It causes reboots, randomly.
Am I the only one suffering from this?
Not the same, but something similar.
I can connect with my car stereo, have to do it twice (once for music streaming and once for handsfree). Once connected, i can stream music fine. Even the controls on my steering wheel work. When I receive a phone call sound is muted and i can talk fine as well.
After I hang up the phone, the music doesn't come back, only a 0.5 second stutter every 2-3 seconds. On my phone, in the music player I can see that it's my phone that has the problem; the visualisation displays exactly how i hear the sound.
This behaviour also occurs when I turn off my car and turn it on again.. there doesn't seem to be a single thing that i can do to get music to play again, just some fiddling usually gets it to work (but then i have to stop my car first before i can have music..)
If anyone has any ideas for troubleshooting let me know!
I honestly think ics has compatibility issues with certain bluetooth devices.
We can only hope they realize this and take measures to correct it.
Gingerbread is flawless.
Sent from my GT-I9100 using XDA
Just a notice that this seems fixed for me now.
I've upgraded to the 4.0.4 Rom found here: Click!
Next to this i'm using the app "doubleTwist"
ICS talks a different language then gingerbread when it comes to A2DP, especially for the play/pause commands, which seem important to me..
A2DP issues
I find I have similar issue. I have a SONY bluetooth deck in my car and my phone will lock up and force restart mid song or mid phone call.
Anyone have any ideas apart from flashing that 4.0.4 Rom
So, I'm having a strange issue with my new Note that I can't quite determine where the root cause may be, or if it's a known issue.
If I register my Note with my car as both a phone and an audio device (how the Infiniti nav/stereo works) I can use the Note as a phone fine UNLESS I start an audio app, such as Pandora. Once a2dp audio starts the Note will no longer connect as a phone device, but it works fine for audio.
I had the phone paired with the stock ATT rom but only used it as a phone, so unfortunately, without a restore to stock, I can't tell if the problem exists with the stock rom.
I flashed to flappjaxxx's rom (which I love) the same day I setup the phone to run Pandora via Bluetooth and that's when I started seeing the problem.
I also see some random connect/reconnects that seem a bit more than usual.
So, I can't say there's a correlation, or if this is a known ICS beta issue or what, but I'm hoping it is and that it's not a design flaw
Way I see it it's either:
1. Flashing to any ICS beta rom has the problem, currently?
2. It's in flappjaxxx's build (doubtful)
3. It's user error...(possible )
4. It's an app issue (ie. Pandora is causing the problem?)
Anyone have any thoughts, suggestions or insights? I've done some searching but haven't found this exact issue yet on any posts.
Thanks!
I have a Kenwood DNX9960 in my Avalanche. It connects also for phone and for streaming media. I can be streaming media from either the stock music player or an internet site like pandora or TuneIn and my calls will automatically come through. When the call ends it goes right back to streaming.
It autoconnects to both as long as my phone is in range when I turn on the kenwood. I did have an issue at first where it would not autoconnect. I deleted the pairing from both my phone and headunit. Then when I repaired I paid close attention to check any boxes to "Always" allow connection and I haven't had any issues since.
I understand the normal pairing process, I've had several phones before that worked fine prior to the Note. So, I'm thinking that it is probably a corrupt bluetooth db... I'm going to be reflashing to Flaps new rom and we'll see how that does
Is there a way to delete the pairing from the nav? I would try that
Sent from my SAMSUNG-SGH-I717 using xda premium
There is. I've tried it all, on both sides of the pairing.
I've reflashed the phone to the B6 from FJ, still no joy. The pairing db was new (so no chance of corruption on the phone) and the pairing deleted on the device.
It seems to be a problem with the phone switching between a2dp and phone bt. When a call comes in (while playing say Pandora over bt) the audio cuts out and then the car shows "disconnected" and then "connection failed" if trying to reconnect to the Note as a phone (ie hitting the phone button in the car).
I'm hoping it's the current ICS build. Just have no way to really know. Hoping some other folks will have seen the same issue.
Going to run some tests with different audio sources and see if the behavior is the same.
Well things seem to be working now, for no obvious reason I'll have to assume that the reflash resolved the issue, I just can't tell for sure why it didn't work immediately after. I think it's due to deleting the old pairing on the car and not shutting down the vehicle.
Cheers.
BT connections
I have similar problem connecting to van audio system (vauxhall). After some experimentation it appears to be an ICS problem, if I reflash my note with gingerbread I have seamless connections for both audio and phone. As soon as I upgrade even with offical ICS bluetooth connections become problematic, I can pair but not autoconnect. Tried samsung and they just "fob off" with it's an incompatable device. Until a bug fix is issued it appears as though it's a choic of staying with gingerbread and have a working system or ICS and no handsfree.
While my watch is a calisto 100, Im going to assume for the sake of assuming things that for the most part, all of these watches have this quirk.
I got the watch a few days ago just to see if It could replace my gear. And it sorta did. I also wanted to toss some music on it/ spotify for jogging/etc.
First Thing i noticed was my bluetooth headset would connect and then promptly disconnect. I noticed if i turned off phone audio and only enabled media audio, it would last a bit longer... random...sometimes a whole song..sometimes 10 seconds....etc.
To troubleshoot I started out knowing that if phone audio was unchecked i could at least connect and listen for a few seconds or minutes.
So I started there, wifi off/data on/ bluetooth on. still would randomly disconnect..I then wrote a little app to grab the bluetooth wakelock to see if that was what the deal was...No dice..it stays awake in sleep mode. I then put the watch in sports mode to see if there was any difference..keeping the hardware awake... No dice..same thing....So then I disabled the data connection and low and behold ..the headset stays connected.
as soon as i enable data...the disconnects randomly happen.. Im assuming again that the fact i can go 10 minutes or 30 seconds or 15 minutes and 10 seconds...or whatever random amount has something to do with the radio transmitting and receiving.
Anyone have a second to duplicate anything ive done here....
The other variable is that I am running on tmoble, so no 3g.. good old edge...I have not gotten desperate enough yet to toss in an att simcard to see of radio on in 3g mode with bluetooth works well ..so thats another variable here.
I have not the faintest idea why phone audio crashes the bluetooth driver..but it does..and requires a reboot
aliosa27 said:
While my watch is a calisto 100, Im going to assume for the sake of assuming things that for the most part, all of these watches have this quirk.
I got the watch a few days ago just to see if It could replace my gear. And it sorta did. I also wanted to toss some music on it/ spotify for jogging/etc.
First Thing i noticed was my bluetooth headset would connect and then promptly disconnect. I noticed if i turned off phone audio and only enabled media audio, it would last a bit longer... random...sometimes a whole song..sometimes 10 seconds....etc.
To troubleshoot I started out knowing that if phone audio was unchecked i could at least connect and listen for a few seconds or minutes.
So I started there, wifi off/data on/ bluetooth on. still would randomly disconnect..I then wrote a little app to grab the bluetooth wakelock to see if that was what the deal was...No dice..it stays awake in sleep mode. I then put the watch in sports mode to see if there was any difference..keeping the hardware awake... No dice..same thing....So then I disabled the data connection and low and behold ..the headset stays connected.
as soon as i enable data...the disconnects randomly happen.. Im assuming again that the fact i can go 10 minutes or 30 seconds or 15 minutes and 10 seconds...or whatever random amount has something to do with the radio transmitting and receiving.
Anyone have a second to duplicate anything ive done here....
The other variable is that I am running on tmoble, so no 3g.. good old edge...I have not gotten desperate enough yet to toss in an att simcard to see of radio on in 3g mode with bluetooth works well ..so thats another variable here.
I have not the faintest idea why phone audio crashes the bluetooth driver..but it does..and requires a reboot
Click to expand...
Click to collapse
Excellent troubleshooting. What batch/firmware do you have? I don't use sim/data on this so I'm couldn't replicate your observation just yet.
However, days after I got this, I tried bluetooth connection on 2 different BT speakers (Monster and Supertooth) --no disconnects even on screen off. There was a millisecond gap when screen turned off but that's it, music just kept on playing. Maybe the latest firmware already have some BT fixes. Dunno but glad BT music streaming works for me. I have yet to try it on my Backbeat Go2 BT headset.
I have 4th batch 1/8 2100
Kernel: 3.4.5
Firmware: Omate_Truesmart_20140513.103530_V2.0
Asked a question a while back about the issue with Bluetooth audio cutting back to the phone speaker, is there a fix out for it yet? If not, do Huawei know about the bug?
Thanks
Original post text below.
I have this little problem with my new Huawei.
(I have a Mate 10 Pro, couldn't find a section for that specific model)
Whenever I connect it to my car or Bluetooth headphones, the audio from my phone will randomly switch from my car speakers or my headphones to the phone speakers. The only way to get it outputting audio through the Bluetooth device again, is by reseting my Bluetooth connection. However, it does this every time and its driving me insane.
Can someone help me with this? Thanks in advance.
Click to expand...
Click to collapse
My mate 10 pro have terrible bluetooth problems with my earphones, sbc low quality and very noisy. Acc totally broken.
Hxxli said:
Asked a question a while back about the issue with Bluetooth audio cutting back to the phone speaker, is there a fix out for it yet? If not, do Huawei know about the bug?
Thanks
Original post text below.
Click to expand...
Click to collapse
Can't help with a solution I'm afraid but I get the same on BLA-L09 C782, firmware 131. It sometimes refuses to connect to anything until I switch into airplane mode and back.
Other times it will connect fine then switch to loudspeaker almost immediately - even though bluetooth still says it's connected (and the play/pause button works on the device). It seems fairly random and reconnecting a few times gets it to work for a while, but it's annoying when it happens while driving.
My guess is that it's an audio routing issue, so most likely a software glitch.
Has anyone switched to a treble rom and still finding the problem? Or has anyone noticed it has gone with a later firmware update?