I use a bluetooth headset all day and the issue I've had with all of the Rom's I've tried is chronic bluetooth crashing. In the middle of the call, when I'm not on the call, etc., I get the annoying alert "Phone has disconnected" often followed a brief time later with "phone has reconnected."
I have no idea what's causing this and I've used multiple bluetooth headsets and even car connections. This has happened with Lineage, Havok, ResurrectionRemi, Bliss, and all of the others I've tried, even with no other apps installed. I've also used multiple Galaxy S5 devices (I have three of them) and they all suffer this problem.
Is there an improved BT radio or something else that can be flashed independently to solve this problem?
I'd offer a bounty if I could to help me solve the problem but I am not sure if that's allowed on this forum.
No love here?
can you try this build? https://luis-builds.de/downloads/lineageos/cr/Samsung_Galaxy_S5_(klte)/
Related
Hi everyone. I have had my Tilt for 4months now and it has given me a lot of joy. I have flashed and reflashed with no problems at all. I am currently using Schap's 4.31 Rom with 1.27.12.11 radio.
About a month ago i installed a new car stereo that has bluetooth connectivity with my phone - worked like a charm, paired very easily and generally appeared to be working with no probs.
Then i noticed that if i was in a bluetooth conversation and somebody else was calling (on call waiting), if i switched calls i could not hear anything, and if i ignored the second call, when the person on call waiting hang up, both conversations were terminated. I thought it was odd, but i just deactivated call waiting and thought, "let them try calling me later".
The other, a lot more serious problem, is that sometimes, randomly as far as i realised, the phone will go totally silent - incoming calls won't ring, and when i try to make a call, when i press "talk" then phone does not make that beep that it makes when an outgoing call is initiated. Should the person i call pick up i cannot hear them at all.
A soft reset takes care of this problem, but it has happened to me 3 times already, and i think it was after a bluetooth call.
Has anybody faced this problem before? I need to be available on the phone 24/7 due to my work and i really need to find a solution for this. Yesterday afternoon i took a nap for 45 minutes and had six missed calls that i never heard cause the phone never rang.
The phone is always on "ring" and at full volume.
Any ideas would be welcome.
Thanks
Alkis
Same issue
I'm assuming since I also am facing this same problem that it is not uncommon. It seems to me that it happens after a bluetooth device is turned off. Somehow it sets the volume on everything to mute. I thought only a soft reset would fix it until I discovered that it was just shutting off the volume. Still annoying, though.
Tilt problems with phone going silent
This problem has occurred with my phone every since upgrading to the WM 6.1 and it is related to a bluetooth device being hooked up. Often when someone calls the ringer will go from vibrate to on, but the volume turns all the way off. It will then cycle to off completely. The cycling occurs when a call comes in or when I hang up. I can stop this problem from happening by disconnecting the bluetooth head set. I have tried three different headsets and the problem occurs with all of them (Jawbone I, Jawbone II, and Plantronics) so I know it is not the brand of headset. HTC said to try a download of a screen dimmer problem, but have not done that yet. Anyone have any better advice?
did u guys ever find a solution to this?
its quite annoying missing calls because my phone decides to go silent for some reason
Same issue with GPS
I have the same issue, even when using software that accesses the GPS via bluetooth port. Muting is irritating, but at least voicemail catches messages. What really bothers me is that sometimes the mute is turned off and the volume up, especially when in a private meeting where we do not want interruptions
Gregg
HTC Tytn II bluetooth causes silent setting
I too have had the issue where my phone will go into total silent mode after using my bluetooth stereo hands-free feature. It doen't happen after using my bluetooth headset though.
It happens pretty regular that after using the bluetooth hands-free of my JVC car stereo that when I take the phone elsewhere it is totally silent. no ringer, no alarm (Ptravel alarm is what I use), no audio if I make a call (or receive a call).
It also will cause the phone to be silent on subsequent calls on the bluetooth stereo hands-free: ie: I take a call, hang up and another call will come in and I can answer it but have no audio.
My Tytn II is running the HTC (AT&T) WM 6.1 upgrade. The only thing I have done is use the Advanced configuration manager and the Kaiser tweak to change a few settings for performance and visual enhancements.
I see others are having the same problems.....Has anyone else used the tweaks and maybe that is root of the problem?
Has anyone discovered a fix (really important). My only options are to soft reset every time I get out of the car or not use the JVC bluetooth capability (which is why I replaced the stock radio in the first place).
Thanks
Hi rrackman,
I'd advice for you to look at the following thread:
http://forum.xda-developers.com/showthread.php?t=438457
It's quite long, so better subscribe to it and wait for responses. Several people with Tilt's have the same problem. Myself I have a JVC NX-7000 and an unbranded Kaiser (HTC TyTN II). It works fine with WM6.0, but I have the same issues you mention with WM6.1. First advice while we're searching for the solution: downgrade to WM6.0...
Regards,
Nika.
Is there a solution to this problem?
Try WM6.0 ROM - check out the thread I mention in my sig.
Regards,
Nika.
I did indeed take a look at the thread you linked earlier. Sorry for making the quick post earlier, I should have mentioned that this is regarding the "unexplained volume drop to zero" symptom, not the NSI symptom. Fortunately I don't have the NSI problem, just the drop to zero problem.
Of course downgrading to 6.0 would be the key solution, was just hoping to find a way to avoid doing just that. My phone never had the problem prior to 6.1 and was running the exact same list of applications and settings.
Hello all
I recently put 4.2.11.1 on my G1. Now when I pair my headset with the phone. The audio is still transfered though my phone. Is this a known issue? is there a fix?
Tech Specs
Handset: G1 w/Cyanogen 4.2.11.1
Headset: Samsung WEP470
The headset worked fine with stock 1.6
The headset appears to pair fine, even verified the bluetooth 'button' is selected while in a call. Still audio goes through the handset and not the headset.
This really is my only issue I love cyanogen so far and hope that the Nexus One is cracked fairly soon after release.
I have the exact same issue with a parrot ck2100-bluetooth hansfree, also running latest cyanogen
I've had this issue and other Bluetooth audio problems under the last several CM releases (See http://code.google.com/p/cyanogenmod/issues/detail?id=819). When audio fails to go through the headset as you describe, turning the headset off and then on again often fixes it. If that doesn't help, then turning the headset off, toggling Bluetooth off and then on, and then turning on the headset usually works.
hrmm, hope this can get fixed I may have to abandon Cyanogen. I have to field call via bluetooth when I work from home.
usually this happens once a week for my bluetooth if i keep toggling BT on and off several times (usually do it if i forget my BT headset). easy fix. not a serious problem with me.
like the person above said: just turn toggle BT off then on, it should connect fine. if not, what i do is go through the settings and unpair them and pair, it should connect to the phone's audio. rinse and repeat.
not a serious bug that should keep anyone away from a certain rom... especially Cyans
Yall in the wrong forum ppl
If its an issue concerning Cy's rom go in his thread n follow the link to submite the issue.
If u trying to solve the problem go in Q&A and ask there or CY's thread.
This has nothing to do with development.
moved to Q&A
I am also having this issue.
I am having a parot c3100 and it pairs fine. But the sound is send to my phone instead of over my car audio system.
I tried bluetooth+headphone fix, but that doesn't help either.
It looks like every cyanogen (based) rom does have this issue ....
Does anybody have other ideas to get it fixed ?
Hi, I do know that there been reported quite a few problems with Galaxies bluetooth.
I have Motorolla HT820 headset. It connects without any problems. Starts playing music. However, every odd 30 (sometimes more) seconds it stops playing music for some 0.5-1 seconds.
Checked that headset works okay with other phones, so its problem in phone.
Anyone has similar problems, or it works for them without problem (eg. maybe other variants of galaxy s work better)?
Turn off WIFI. It is a common Android problem.
mirox3m said:
Turn off WIFI. It is a common Android problem.
Click to expand...
Click to collapse
Seriously? Thats it? I spent god knows how long trying to fix it, used different firmwares, searched in google quite a lot (obviously not good enough, as I thought its a galaxy only issue)... God android sux in some things...
Thanks, mate!
PS. Topic can be closed.
EDIT: After testing a few minutes it appears thats it is enough to just switch off - switch on WiFi to fix it (I assume for the duration of one session).
There are some weird issues I have been noticing with my SGS regarding bluetooth.
At first, I got slightly irritated when I found out I was suffering what I thought to be this issue on my SGS (noticed after flashing to JP6, later on JPX and now also on JPY). But since, I have been carefully narrowing down the problem (there seem to be several variants of the issue bundled within the one linked) and have finally figured out how to reproduce the error (sort of, at least in my setting: SGS-I9000, BMW 1series car BT system).
After setting a custom BT device name and pairing to the car, the BT handsfree works flawlessly on spot and if disconnecting and reconnecting later. The problem starts after rebooting. Now, here's where I'm getting inconsistent results.
Most times the bluetooth info I entered is simply reset to factory defaults: the pairing list is empty and the device name is set to the standard "Galaxy S".
Some other times however, it gets much more annoying: all the settings seem to be intact (pairing and device name stay as set) but BT connection always drops after about 60s (regardless of wheather you start/receive a call or not).
Is this a known issue? Did any of you experience this behavior? Any known fixes?
Thanks!
Phil
What ROM are you running? Get yourself onto the newest Froyo and see if the problem goes away. I definitely don't have problems with mine going to headphones, ear headset, or in car system.
Doc kitchen (jan 3rd) + Hardcore kernel JPY (which means latest kernel/drivers). This has been happening to me all along though, despite of rom changes (also happened with stock JP6 and darky's JPX).
Sent from my GT-I9000
Hi,
same problem for me: the bluetooth connection to my Parrot MKI9200 car audio system drops after a few seconds. This was not the case with ROMS older than JPX/JPY.
Are you still having this issue? I just flashed Serendipity 6.2 and have the same problem. When I reboot the Bluetooth settings are reset to default.
goodolsen said:
Are you still having this issue? I just flashed Serendipity 6.2 and have the same problem. When I reboot the Bluetooth settings are reset to default.
Click to expand...
Click to collapse
The issue disappeared on flashing to a new rom. I'm soory not to be able to give you more details because I found out the issue was gone by surprise (I had stopped using the car handsfree alltogether because of the issue).
Right now I'm on a Doc rom (hardcore kernel, JPY radio, ext4 system & data, ext4nj cache) and it works perfectly!
I've read extensively on the problems the RP2 has with various bluetooth devices. I'm having issues with getting bluetooth to function properly with my wife's van (Chrysler Pacifica). I've experimented trying many different things, but am still coming up short. The phone will pair perfectly the first time, and I can play audio through a phone call, Spotify, Poweramp, Google Maps, etc. Everything works perfectly as expected. If I simply toggle bluetooth off/on or reboot the phone, it will seem to reconnect, but within 2-3 seconds, it disconnects, and I get a com.bluetooth has stopped responding error. It will repeat this same error every time I try to reconnect. My first thought was that it was the dreaded two bluetooth overlays on the vendor partition, but I've tried repeating this process with the overlays deleted, too. I get the same results. Something else is getting in the way of proper bluetooth functionality other than those overlays, but I haven't the faintest idea where to look next. Any ideas?
Edit: Figured it out. Uconnect doesn't support AVRCP higher than 1.3.