A few months back my Jabra Stealth started only lasting thru half the day, very abnormal. I assumed it was a headset problem and returned it and got another. Same problem but now the audio on inbound calls doesn't route to the headset until I toggle the BT off and on again in the call screen. Calling out the audio routes normally to the headset immediately.
Also, if I'm listening to my podcast player thru the headset jack, then get out of my car and start playing it thru my headset, there's no audio at all until I turn BT off and back on again.
I'm not sure if this is related to Lollipop as I think it predates that update, although I don't recall exactly when that update pushed out for AT&T, maybe it is all a Lollipop issue...
I've tried deleting all pairs, clearing the cache on BT and BT Test, wiping the cache in bootloader mode.
Related
I have Nokia bluetooth stereo headset BH-503.
I'm using it fine for calls but lately I cannot seem to get music audio through them. I suspect it may have happened when Tmobile sent the OTA update out (my phone was in the first batch, now on 1.15.110.11). Note - im not sure exactly when this started so may not be the update.....could be a dodgy app?
I was using spotify and the htc music player with the headset fine when I first got the Desire.
Both 'phone' and 'media' settings are ticked in the bluetooth options and obv tried disconnecting then repairing the two but still no joy.
Has anyone else noticed this? any other media bluetooth problems?
I can be listening to Spotify or HTC music player thru the phone loudspeaker and when a call comes thru the phone correctly diverts the call to the bluetooth headset then resumes music to the loud speaker once the call has finished.
It's as if the bluetooth media audio capability has been disabled!? Any help would be appreciated, it's driving my nuts!!
hmm seems to be fixed. I did one thing differently this time.....
Instead of activating bluetooth via the widget or settings>wireless&networks> bluetooth where you can check the bluetooth box to turn it on, i went into:
settings>wireless&networks> bluetooth settings and activated bluetooth from there.
When it connects to device it now says 'connected to phone and media audio' and plays fine now even when switching on via the widget.
V odd. Oh well happy chappy again
Hello guys,
I just got a Sony bluetooth headset and I am trying to use it with my HTC TYTN II. At first I paired the phone and the headset and I was able to listen to music and talk through the headset, all perfect. When I was listening to music, the bluetooth icon on my phone represented a music note and a headset over it.
When I turn the headset off once and then on again, it connects automatically with the phone but in some other mode. The bluetooth icon now represents the bluetooth sign with a headset over it. Now when I listen to some music, it comes from the speaker of the phone, not from the bluetooth headset. Talking through it is not a problem.
If I pair the phone and the headset again, it works just fine (showing again the music note) but once I turn the headset off and on again, I lose the music mode.
Does anyone know how to fix that? Thanks in advance.
I fixed the issue by installing AutoA2DP (found in this forum).
I've had a similar problem on my Tilt. I originally posted the following on the ROM thread. Since then, I have found that the AutoA2DP has not fixed the problem. I still have this issue about 70% of the time, and sometimes I can't get the bluetooth to work at all, not even after a soft reset. Sometimes it seems as if the bluetooth has no power, the phone can't communicate with the headset except when within a few inches of one another. Then it magically seems to resolve itself. Anyway here's my original post from the ROM thread.
The other day I installed an app on my phone called Schaps Network Plugin, which allows you to map network drives to the phone the same way you can do with a desktop. It allows me to access the home network directly via my wifi. It was something I needed and it seemed to work great, for a day. The next day my bluetooth headset would not connect. Long story only slightly shorter, it seems the problem was with the headset connecting via A2DP and doing so automatically. This always worked just fine in the past. Suddenly it wouldn't work. I tried a ton of things including a "fresh" install of everything and formatting my memory card to start with nothing on it. I flashed the original rom and then flashed this rom. I did hard resets each time. Did this twice. Even tried the bluetooth in the oem rom to see if I still got the problem. I did, and it is still with me. I can manually get the headset to connect via A2DP using the bluetooth settings, though even then it may take reconnecting several times to get it to work. However, when I turn the headset off and then on again, the A2DP does not reconnect, just the hands free. But the sound is not routed through the phone's speaker either, at that point. In fact you often get no sound at all, nothing via the headset or the speaker. OTOH, if you activate Voice Command, the headset does work while Voice command is running. After it shuts off, you are back to no sound. It seems as if the hands free works fine, but the audio gets partly routed to A2DP but does not connect to the headset. If I reset the phone, the headset connects correctly and efverything works until I turn the headset off again. Also if I pair the headset again, everything works correctly until I turn the headset off. Though pairing is not as trouble free as it used to be either. Sometimes it will not pair up wihtout repeated attempts. I did find this program, AutoA2DP which has patched the problem. It detects when a paired bluetooth device connects, and forces a connection via A2DP as well. But I never had this issue in the past, and my wife's phone still has no problem. I am not sure the Schaps Network plugin had anything to do with it, other than the timing. Seems odd to me that the bluetooth stack would suddenly develop issues that persist even after two fresh flashes of the rom. Any ideas, suggesitons, etc.? This is really bugging me, and although the patch seems to be working, the phone is still not acting "right." In the past, and on my wife's phone, if a bluetooth headset is turned on, it automatically connects, and all sounds, including the system sounds, are routed through the headset. Now, sometimes they are, and sometimes they aren't.
Hey guys,
I have recently started to experience some weird bluetooth problems. I have a Softbank HTC Desire (I live in Japan) and a LBT-AR200C2 bluetooth receiver. I had absolutely no problems whatsoever the first two weeks.
Yesterday, the bluetooth receiver would connect but no audio would play through the headphones. When playing a track from the player it would just skip over in 2-3 second increments and no audio was present (not even from the phone speakers). Not even reboot helped.
So, I decided to unpair and pair again to try and eliminate the problem. Everything is working now ... except for one big problem - the bluetooth disconnects every 3-4 mins. So, I start listening to a track, the screen goes to sleep and 2 mins later the music stops and Bluetooth disconnects. I unlock the phone and the Bluetooth reconnects immediately.
Besides the HTC Music Player i Have 3 and Museek installed. Could that be a problem?
Update: Listening to music without the Bluetooth receiver is ok - the music does not stop.
I seem to be getting exactly the same problem with my car kit.
I can pair it up, both car kit and Desire recognise that they are paired yet after approx 2 / 3 minutes it disconnects yet as the above poster indicates - it worked flawlessly for about 2 weeks.
I have deleted all the pairings, reset both the car kit and the desire back to Factory defaults but the problem happens straight away.
Googling desire and bluetooth seems to throw up a number of potential issues so was wondering if anybody out there had similar problems and whether anybody actually has a work around
cheers
WBC
Same issue with my Motorola HT820 headphones. Drop calls back to the handset and get silent periods when listening to music.
Has anyone else paired a headset to their slide and had media audio come through it?
I paired my old jawbone2 to my slide and when I was playing a game, game audio came through the ear piece. It only happened ONCE and now everything (except calls and the genius button) is back to the phone speaker.
Is that normal? Should audio be routed through my BT Headset like that? I was pretty certain only calls should go through to a non a2dp device.
I don't know anything about the jawbone2, but I have no problems. For regular phone use, I have a Motorola H500 and I always play Pandora in the car, and have never had music come through the H500, just voice like it should be. (I've used the H500 on the G1 I ordered on launch day, on a Motorola Droid, a Sprint EVO 4G, and the 3G Slide on a variety of stock and non-stock ROMs.) I also have a Motorola S9 A2DP headset, and the audio works as you would expect on it also on all of those devices. Maybe the Slide detects the Jawbone2 in a funky way somehow. What does it say when you go to Settings->Wireless & Networks->Bluetooth Settings->Jawbone2 (press & hold then select options.) If it's not a A2DP headset, it should just say "Phone, Use for phone audio." An A2DP headset will also say "Media, use for media audio." If you are lucky, the phone is just detecting it wrong and you can uncheck the Media option.
It only did it once and then went back to acting like a normal BT headset.
I am going to chalk it up as a fluke from initial pairing.
And under options it says phone audio only which is ok.
I'm replacing it with a Jawbone Icon tomorrow which supports a2dp and a whole slew of other nifty features for a single ear headset.
Don't deal with much bluetooth headsets but i do hook it up to my car stereo and i know there are settings in the bluetooth of that specific device. have you had a chance to look in there?
Bluetooth Pairing problems
I have similar problems when pairing to my truck stereo. It auto pairs when I get into the truck and works perfectly well the first time I make a call. But after that it doesnt disconnect properly AND it will disconnect but will stay paired.
I am able to go into BT setting and have it reconnect.
Works once then bam not connected again.
I have Android version 2.3.3
Baseband 47.3201.35.06U_7.07.35.025
Kernel 2.6.32.17 -Cyanogenmod-g501281a
Mem Info
183MB /418MB
Build GRI40
Connecting to a Kenwood Receiver
DNX9140
It worked fine for my Nexus Not sure why this is happening.
Thanks
I've been having issues with bad static/noise in voice calls when connected to my car's Bluetooth. Music streaming over Bluetooth is fine, however. Does anyone else experience this issue. I used to have an S6 paired to my car and it was perfect for both voice calls and music.
My audio for like music is fine but tried making a car handsfree the other day for the first time and couldn't hear the other person who said they didn't hear me either. I had to click on the dialer app to switch out it to phone speaker and then back to Bluetooth then it worked.
It's been like this since I first got the phone...it's almost unusable for phone calls in the car. I wonder if this is a software or hardware defect and if it will be corrected in a future update. I don't want to have to RMA this phone if I don't have to.
I'll try your workaround, acheney...thanks for the tip
Pixel XL connects via Bluetooth to both of my cars without problems. And call audio is fine both ways.
I have had zero issues with music streaming or phone calls. 2014 Infiniti q50
I'm having this issue too. Music and video play fine, but when someone calls i can hardly understand what they are saying due the static. Was hoping the update would fix the issue. I'm not sure what to do at this point.
Same issue. Audio over BT is fine. GPS navigation over audio was playing up, but now appears to be ok. The moment I call someone (or they call me) the call is all garbled and I have to switch to speakerphone.
My Bluetooth earpiece however works fine. Not sure if headunit issue or phone bt stack.
i have this same issue. so annoying. so far there's no solution?
eddyz said:
i have this same issue. so annoying. so far there's no solution?
Click to expand...
Click to collapse
None that i have found. Flashed AptX codec and still have same issue. Don't think it is hardware because the phone works fine when paired with other Bluetooth items like speakers, headphones, my watch, and other car stereos. Just doesn't like my factory pioneer unit in my Tc for some reason.
Audio issues for me have always been carrier issues.
Redialing the number usually fixed the call
I ended up finding if I mounted my phone far away from the head unit (near the door/drivers window for example) and tilted the phone in a weird way, the calls were fine.
I don't quite understand it, but seems like there is interference from the head unit when using BT to make calls, which for some reason isn't a problem when you play music (or GPS navigation is on).
Either the Pixel needs better shielding or there's something borked with the Bluetooth chipset.
I would like to use wireless headphones, but the in-channel headphones with a large battery and with good sound have not yet been invented
Yes!
I've only made a few calls over my cars bluetooth, but yesterday I ran into this:
Conversation was fine for several minutes, and then every word the other person said came through as static. When they paused between words or stopped talking, it was quiet. But as soon as they said a word again, it was static.
I toggled the call back to handset and it was fine. So I switched back to bluetooth, and it was fine for a minute or two, and then it became static voice again. I switched back and forth again and it was back to normal voice and remained that way.