[SOLUTION IN THIS POST]
There seems to be a compatibility issue with the new Bluetooth 4.0 of my HOX when pairing with some devices that have BT 3.0 version.
My own issue is with the Car Audio System of my 2008 C350 Mercedes Benz. The Bluetooth telephony worked perfectly with my DHD.
Now, I can pair my HOX with the system, but when I receive a call I can hear the other party only for 2 seconds then the voice is gone. As if we've both muted the call.
On the other hand, when I call someone, the phone call goes through just fine.
I've been reading a lot concerning this subject, and it seems that people are having the same problem with their SGIII.
A software update of the SGIII that was released for some carriers seems to have fixed the issue.
Also, my sister's iPhone 4S works fine with the system, even though it has BT 4.0.
So I believe this issue can be fixed, but it needs one of the Gurus on XDA to come up with a fix
My issue was slightly different (phone would pair but not connect) and I got onto my car kit manufacturer (in this case was a parrot system used in a mitsubishi) and found out I could update that. Since updating my car kit have had no problems at all.
That's good to hear. I read somewhere that updating the car system could be a solution.
But I'm hoping a solution could be made on the phone's side.
xbiggyl said:
That's good to hear. I read somewhere that updating the car system could be a solution.
But I'm hoping a solution could be made on the phone's side.
Click to expand...
Click to collapse
there might be nothing wrong on the phones side, have you checked to see if you can update your devices that are having problems as suggested?
i've had no issues running even bt2.1 stuff
Updating did not fix the issue.
Other phones (with older versions than BT 4.0) work perfectly.
I don't have access to updating my car's audio system atm, so I'm hoping something could be done on the phone's side.
But since this isn't a very wide spread problem among XDA users, I'm thinking it's not going to be an easy task.
Update:
Today, I tried something. After answering a call, the same thing happened (after 2 seconds I could no longer hear the other party but the call didn't drop)
On my HOX I chose Speaker and I was able to hear the other person talking; switched it back to BT handsfree (my car's audio system) and it worked.
Even though this is not a solution, but at least now I can answer a call when I'm driving. I just have to switch to Speaker then BT... Still better than nothing
Having a similar problem with mine, it pairs fine, I can access the phonebook etc but as soon as you try to make a call the bluetooth disconnects. However, i've found that if you turn the bluetooth off and back on again and re-pair it, it seems to work properly.
Would be nice if it just worked first time though.
p5x said:
Having a similar problem with mine, it pairs fine, I can access the phonebook etc but as soon as you try to make a call the bluetooth disconnects. However, i've found that if you turn the bluetooth off and back on again and re-pair it, it seems to work properly.
Would be nice if it just worked first time though.
Click to expand...
Click to collapse
Which ROM/Kernel are you using? And which car audio system are you trying to connect to?
bmw car
viper x rom but tried it on others and had the same problem
p5x said:
bmw car
viper x rom but tried it on others and had the same problem
Click to expand...
Click to collapse
After reading about this subject extensively, it seems that updating your car audio system is the best solution.
I suggest you take an appointment with the BMW service station and have them update your system.
yeah, i'm going to look into it. did you get yours sorted?
Bmw bluetooth 4.0
Same problem here on first connect every thing works fine but the next time the connection is lost with the first call.
Bmw doesn't have a update yet.
Would be cool if someone on xda could fix this for us.
p5x said:
yeah, i'm going to look into it. did you get yours sorted?
Click to expand...
Click to collapse
No I haven't yet. But I guess I'll try to get an appointment for next week.
For the time being, the workaround I came up with (switching to speaker phone then back to BT during a call), is working for me.
staalduinen74 said:
Same problem here on first connect every thing works fine but the next time the connection is lost with the first call.
Bmw doesn't have a update yet.
Would be cool if someone on xda could fix this for us.
Click to expand...
Click to collapse
Does the call drop completely? or you simply stop hearing the other party?
I noticed something new today.
During a phone call (connected to Car Audio System), and I receive an SMS, the same thing happens (but the workaround still works).
staalduinen74 said:
Same problem here on first connect every thing works fine but the next time the connection is lost with the first call.
Bmw doesn't have a update yet.
Would be cool if someone on xda could fix this for us.
Click to expand...
Click to collapse
have you checked with them recently?
Have you tried other phones with the car? wondering if the SGS 3 would have the same problem...
---------- Post added at 10:23 PM ---------- Previous post was at 10:21 PM ----------
xbiggyl said:
For the time being, the workaround I came up with (switching to speaker phone then back to BT during a call), is working for me.
Click to expand...
Click to collapse
thing is, when I try to make a call the bluetooth connection drops so I have to turn the bluetooth off and back on again to be able to reconnect
p5x said:
thing is, when I try to make a call the bluetooth connection drops so I have to turn the bluetooth off and back on again to be able to reconnect
Click to expand...
Click to collapse
Have you tried a custom kernel? I recommend Faux
SOLVED
Even though this is an old thread, I wanted to let you know that this issue has been fixed.
By updating my Hboot to 1.31 and using a jelly bean ROM, I no longer have a problem with Handsfree over Bluetooth.
For those of you who are still facing this issue, I hope this helps.
NOTE: Before updating to new Hboot, you need to make sure your CID allows it. Check here.
Also you need to flash a jelly bean ROM afterwards, I use ARHD and it's pretty good!
.
Cheers!
Related
Well I'm using LVSW 04-08-07, and I'm having issues with my Bluetooth staying connected.
Basically it will just randomly shut off on the phone and I have to re-enable it in order for my headset to work.
At first I thought that it was my headset ( Jawbone ) but then I tried it in my car with my Motorola T305 speaker and it does the same thing.
Does anyone know what could be causing this?
I had the same problem too. I am using my sony bluetooth headset witht eh latest LVSW 4-8-2007 rom which I didn't have problem with any other roms. Maybe there are specific settings that we missed out ???
Well it's good to know it's not just my phone with this issue...
Make sure that you have the bluetooth voice command set to "enabled".(start>programs>b/t voice command config>enabled) I have not had any disconnect issues since I set that up.
Hope this helps.........Later
BT
Same here, until 04 version it was ok (on the other LVSW versions). Now it randomly disconnects.
Also seems like my battery is draining WAY faster.
nukenine said:
Same here, until 04 version it was ok (on the other LVSW versions). Now it randomly disconnects.
Also seems like my battery is draining WAY faster.
Click to expand...
Click to collapse
Be sure to check/turn off I/r beam function.I had horrible battery life until I looked and found that the receive incoming beams was checked. I unchecked it and my battery life has increased greatly!
Hope this helps........Later
BTW I have had this issue with ALL LVSW roms, not just the latest one. But the roms are so damn good that I am willing to fix the few small issues they may have.
^^^ Beam now off - thanks.
But BT still disconnects like it's going out of fashion. Will probably downgrade to 03-26 which to mee seemed more ok than this one. Thanks anyho.
nukenine said:
^^^ Beam now off - thanks.
But BT still disconnects like it's going out of fashion. Will probably downgrade to 03-26 which to mee seemed more ok than this one. Thanks anyho.
Click to expand...
Click to collapse
Do you have the bluetooth voice command config in your programs? If so, open it and enable the b/t. If not, it is in one of the threads regarding m$ voice command issues. It seems to help keep the bluetooth connected.
Later...............
ahfunaki said:
Well I'm using LVSW 04-08-07, and I'm having issues with my Bluetooth staying connected.
Basically it will just randomly shut off on the phone and I have to re-enable it in order for my headset to work.
At first I thought that it was my headset ( Jawbone ) but then I tried it in my car with my Motorola T305 speaker and it does the same thing.
Does anyone know what could be causing this?
Click to expand...
Click to collapse
I had similar issue with LVSW 040807 and bluetooth headset (specifically with M$ Voice Command) but I did not the issue with the 032607. It might have something to do with the AD2P fix that was applied in that version.
Also how his the Jawbone headset, is it as good as the marketing?
Same proble here!, my TyTn randomly disconnect from my Parrot bluetooth car hands free, it's a really annoying thing.
I had sam problem using previous LVSW version.
Not using voicecommand at all - battery gone after half a day.
BT disconnects left, right & center.
Previous LVSW version worked fine.
I'll downgrade as soon as I find some time (to re-install my stuff ).
Same here using 05.04.07 (or LVSW-547)
I am using LVSW and it drops out maybe once to twice a day.
Battery life is good. I easily get a good day out of the phone with out charging. That includes several hours of talk time.
Hopefully in future realease he fixes the problem.
Great Rom.
Hmm if there is no solution to this I might just have to downgrade...
Hi,
I have a bluetooth phone in my car, when I first connected the HTC Desire HD up, it had no problems, it paired and everything looked fine... around 10 minutes later, I noticed the bluetooth had simply disconnected from the car but was still running on the phone. I tried to reconnect it up to the car but it wouldn't, I then turned it off, and turned it back on.. it struggled to come back on, but after a few attempts it did come on and the car connected again...
About 5 minutes later the same thing happened again. At this point my phone started to really slow down, I looked in watchtower and the bluetooth was at the top of the list, soon as I turned off bluetooth the phone was responding fine again.
I have since tried connecting to the car multiple more times and have contacted HTC about it, but it seems to disconnect at random times.
Has anyone else experienced similar problems? I heard of similar problems with the original desire so wondering whether it could be something similar.
Kev
Hi Kev,
I am having similar problems with my Desire HD and Audi in car bluetooth system. I posted on another forum and found others were finding the same...
I pair my phone and within couple of minutes the phone has disconnected and won't re-connect.
Not found any definitive answer as yet, but seems BT in this phone isn't so good. Also read a post saying HTC were aware of this but an update wouldn't be available for sometime.
Hopefully someone else can shed some light!
Ben
I also noticed this the last few days with my Bury CC9056 carkit. I have my DHD since October 18th, and up till last friday it connected fine. Since then it connects to the carkit, but within a few seconds the connection is lost...
Sent from my Desire HD using XDA App
Me too. My connection to my Jabra car kit is stable once connected... but trying to get it connected in the first place is a total headache.
Never had this problem with my Desire, so why HTC should change the Bluetooth function in the HD is a mystery.
Sent from my Desire HD using XDA App
tbh i'm glad its not just me thats experiencing problems meaning it could be a software problem rather than something with my handset in particular.
I have been in touch with HTC about this, and I have just sent them the link to this thread so they can see i'm not the only one with this issue, so if anyone else has this issue it may be good to try and keep it all in here.
quentin_rayner said:
Hi Kev,
I am having similar problems with my Desire HD and Audi in car bluetooth system. I posted on another forum and found others were finding the same...
I pair my phone and within couple of minutes the phone has disconnected and won't re-connect.
Not found any definitive answer as yet, but seems BT in this phone isn't so good. Also read a post saying HTC were aware of this but an update wouldn't be available for sometime.
Hopefully someone else can shed some light!
Ben
Click to expand...
Click to collapse
Mines also the audi in car system - do you find that you struggle to turn the bluetooth off and on again once it disconnects or that your phone becomes a little laggy until you turn the bluetooth off?
Yeah - I use the bluetooth widget on the home screen and once it disconnects, it will either take ages to turn off and on again, or it takes 2 presses to turn off.
I have just purchased a Plantronics 230 headset as need bluetooth for my job and it works perfectly - it's no where near the quality of the in car one though.
Also booked in my Audi as it's still under warranty - spoke to them on the phone and they said they will try and update the firmware but the Desire HD isn't on their supported phone list. Have seen a copy of this and not many phones are!!
I would of thought though, that as long as the phone does connect to the phone system in the car that it is compatible.
I have had 30mins once out of it before it disconnected and it was absolutely perfect in that time, including the phone book etc.
I do believe its something to do with the bluetooth on the phone as its a bit strange the way it struggles to turn on again once it fails.
quentin_rayner said:
.. Also booked in my Audi as it's still under warranty - spoke to them on the phone and they said they will try and update the firmware but the Desire HD isn't on their supported phone list. Have seen a copy of this and not many phones are!!
Click to expand...
Click to collapse
That really hacks me off. I mean, BT is a standard. The only reason Audi can give for not supporting a phone that supports at least the same level of BT as them is that they (Audi) do not adhere to the BT standard.
Now, we all know in real life that cars and phones have problems/bugs/whatever BUT unless they can show that there is indeed a *bug* with the phone then the onus should be on Audi to support it.
Dave
Just for the record, it is not just Audi. With me it is together with the Bury carkit, where it first worked fine. (and also works with all other phones...)
Leon
Sent from my Desire HD using XDA App
I can confirm the issues with the BT. I have a parrot Mki9000 in my car and the first time when i tried to connect the DHD , the phone stopped to respond and I was forced to restart it. Since then the phone is paired with the car kit and works fine in a2dp mode for playing music, but when i try to make a call it simply not work. Yo better discribe the problem I will give an example:
The phone i properly connected and playing music, then it's ringing, but the ring sound is coming from the phone speaker not from the car. Then If i answer the call the sound comes from the phone (it shows that there is connection to the car kit). I've tried to press the speaker icon and there is a list with output devices (the phone, loudspeaker, and my car kit) I've tried to select the car kit several times , but there was no success. When I close the phone the music start to play from my car's BT system , so I think there is a problem with the handsfree function/protocol only a2dp works great , and I didn't have any issues with it. Also I've tried file transfer via BT, it works fine two.
Mitsubish Outlander carkit
I can confirm the same issue with the Mitsubish outlander carkit. It even happens that it drops the conversation. sometimes it's ok for half an hour, sometimes it disconnects after 1-2 minutes.
I also have a Jabra (bluetooth) headphone and noticed that if you pick up a call on the phone the sounds doesn't route to the headphone. If I pickup on the headphone it works fine.
ZoidAndroid said:
I can confirm the same issue with the Mitsubish outlander carkit. It even happens that it drops the conversation. sometimes it's ok for half an hour, sometimes it disconnects after 1-2 minutes.
I also have a Jabra (bluetooth) headphone and noticed that if you pick up a call on the phone the sounds doesn't route to the headphone. If I pickup on the headphone it works fine.
Click to expand...
Click to collapse
I have a Pioneer head unit with BT in the car and that seems to work OK, not withstanding the fact that the HU has BT issues of its own (hardware fix needed - I'll get a new unit rather than fix it as I want one with A2DP) but once connected it works fine.
I have a Plantronics headset that seems to exhibit the same problems as your Jabra. At least if I use the phone to answer the call the sound comes through the phone. Also, if I have been using the headset the next call I make goes through the phone speaker which is a pain.
I'm wondering if HTC are routing the sound through the device that's actually *controlling* the call? So even if a headset is paired and connected to the phone, if you use the phone to make the call, as most people would, then it assumes that that's where the sound should get routed. If so, doh .....!!!!!
Just to add, if the sound does get routed to the phone you can use the 'choose speaker' option on the screen to route it to the headset but you shouldn't have to do this.
Anyone reported these issues to HTC and got a meaningful response?
Dave
I did send an email to HTC. Their wonderfull answer was about: "is your phone mentionned in the compatabilylist of the carkit, if not drop the problem there"...
I am still waiting for a response from HTC.
Mines got to a point now where I cant even make a call, it connects to the car, I go through phone book (on car) choose person to call, press call.. it tries for a couple of seconds then comes up disconnected, about 10 seconds later the phone disconnects from the car and will nto reconnect.
My phone then lags like mad until I turn bluetooth off which according to watch tower is taking up about 80% of the CPU.
any updates/solution to all these problems ?
I need it to work with MW600 before buying Desire HD
Last contact I had with HTC is they told me it had been escalted to the software team, so i'm guessing next time a software update comes out it could come about in that, but at the minute no still not fixed.
ZoidAndroid said:
I also have a Jabra (bluetooth) headphone and noticed that if you pick up a call on the phone the sounds doesn't route to the headphone. If I pickup on the headphone it works fine.
Click to expand...
Click to collapse
I've always thought that that's the way it is on all BT headset phones, it makes sense, if the incoming call was for my girlfriend, she can answer from the phone itself, and it automatically routes this through the phones speaker, and if it was answered from the headset, then it routes to the headset.. makes sense to me, I think it's quite good that it does that!
Do any of you have the process com.android.phone crashing when making a phone call through BT?
Ditto my mitsubishi outlander factory bt system. Seemed to work fine first time but then disconnected during first call and would not reconnect for days. Then after connecting not all functions would work ...no incoming call alert on car system, no dialling from car etc. I know the car system is fine as all functions work perfectly with my old nokia xpress music.
Sent from my Desire HD using XDA App
I trust that all of you bother to report this to HTC, at least once per instance ?
- otherwise I don't know when they'll fix this..
Hi,
I have completely stock, locked boot loader and no root , GN that received OTA last night.
Before the update, my Samsung HM7000, Bluetooth headset worked flawlessly. Since the update I get disconnected frequently, Google Now or any other voice command takes forever to pass initializing.
Anyone else experiencing the similar issue?
Thanks
Sent from my Galaxy Nexus
I guess no one has any issue with Bluetooth?
Sent from my Galaxy Nexus
Hi,
No for me everything is working fine.
Hawon said:
I guess no one has any issue with Bluetooth?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
I'm having issues -- it works fine for audio and phone, but when I try to do voice search while the headset is on, the phone will often freeze on "initializing."
Same issue as op
http://forum.xda-developers.com/showthread.php?p=28829994#post28829994
rabidrotty said:
Same issue as op
http://forum.xda-developers.com/showthread.php?p=28829994#post28829994
Click to expand...
Click to collapse
Well, not really the same issue. For me, the Bluetooth headset (Motorola s305) connects fine. It just seems to cause trouble with voice search.
I have the same issue- it fails to initialize and sometimes I will get a blue cloud that says "try again?". It is inconsistent- sometimes works flawlessly, sometimes the second time it will work, and sometimes cannot get it to initialize at all.
Noticed something similar myself.
I used to have a set up where when driving I had two bluetooth devices paired simultaneously.
1) Phone audio to car.
2) A2DP (media) audio to belkin BT to AUX adapter/receiver)
I've noticed since JB 4.1.1, my car will continuously disconnect from my phone whenever the phone is also paired with the Belkin adapter. Not too sure what to do (I have tried deleting and recreating the pairs just to be sure...)
Hawon said:
Hi,
I have completely stock, locked boot loader and no root , GN that received OTA last night.
Before the update, my Samsung HM7000, Bluetooth headset worked flawlessly. Since the update I get disconnected frequently, Google Now or any other voice command takes forever to pass initializing.
Anyone else experiencing the similar issue?
Thanks
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Did you ever managed to fix your issue? I'm having the same problem with my bluetooth connection. It connects fine to my car but after few minutes it disconnects and I have to reconnect by hand then it disconnects again. Can't keep a bluetooth connection anymore. Was working perfectly in ICS and I think it was also working well in JRN84D (Android 4.1). I believe that it's the JRO03C (Android 4.1.1) update that ****ed everything up.
Steve
BT handsfree disconnecting
Uni7 said:
Noticed something similar myself.
I used to have a set up where when driving I had two bluetooth devices paired simultaneously.
1) Phone audio to car.
2) A2DP (media) audio to belkin BT to AUX adapter/receiver)
I've noticed since JB 4.1.1, my car will continuously disconnect from my phone whenever the phone is also paired with the Belkin adapter. Not too sure what to do (I have tried deleting and recreating the pairs just to be sure...)
Click to expand...
Click to collapse
I have the same problem after upgrading my GSM GNex to 4.1.1
I have Kenwood KCA-BT200 hands-free adapter in the car and it was working fine with ICS.
After update it does not connect automatically and I have to switch BT off and back on on the phone for hands-free to connect. Once connected it will stay so for as long as the phone is active (screen is lit up). When screen goes off the phone disconnects after about one minute.
I have tried to recreate pairings, fiddle with BT visibility settings on the phone - nothing helps.
Hello everybody,
I've been having issues with bluetooth on the Nexus too.
My problem, though, is that the bluetooth won't start at all. It worked just fine before the update to 4.1.1 (from ICS 4.0.4).
Now, when I restart the phone and try to switch it on, it doesn't do anything. Right after, getting out and into the settings again, the sliding on/off switch seems to be grey as if it cannot be moved.
Any solutions or ideas??
Thank you.
Alex> said:
I have the same problem after upgrading my GSM GNex to 4.1.1
I have Kenwood KCA-BT200 hands-free adapter in the car and it was working fine with ICS.
After update it does not connect automatically and I have to switch BT off and back on on the phone for hands-free to connect. Once connected it will stay so for as long as the phone is active (screen is lit up). When screen goes off the phone disconnects after about one minute.
I have tried to recreate pairings, fiddle with BT visibility settings on the phone - nothing helps.
Click to expand...
Click to collapse
Yep, it dies predictably after screen-off for me as well.
---------- Post added at 10:32 PM ---------- Previous post was at 10:30 PM ----------
UlixesTNT said:
Hello everybody,
I've been having issues with bluetooth on the Nexus too.
My problem, though, is that the bluetooth won't start at all. It worked just fine before the update to 4.1.1 (from ICS 4.0.4).
Now, when I restart the phone and try to switch it on, it doesn't do anything. Right after, getting out and into the settings again, the sliding on/off switch seems to be grey as if it cannot be moved.
Any solutions or ideas??
Thank you.
Click to expand...
Click to collapse
Try deleting the bluetooth folder named after the MAC address of your BT chipset in /data/misc/ (I think)?
Uni7 said:
Yep, it dies predictably after screen-off for me as well.
---------- Post added at 10:32 PM ---------- Previous post was at 10:30 PM ----------
Try deleting the bluetooth folder named after the MAC address of your BT chipset in /data/misc/ (I think)?
Click to expand...
Click to collapse
Won't that mess everything up?
Yesterday it actually worked a few times (enabling/disabling). Today it doesn't anymore. I can't think of any reason why it should be doing this... Any other solution?
Thanks!
UlixesTNT said:
Won't that mess everything up?
Yesterday it actually worked a few times (enabling/disabling). Today it doesn't anymore. I can't think of any reason why it should be doing this... Any other solution?
Thanks!
Click to expand...
Click to collapse
It regenerates when you restart phone/re-enable bluetooth. I had to do that reset when TB messed up BT pairings on a restore.
BT not pairing
Same issue as OP.
After update to JB from ICS my BT ear bud continually tries to pair. I have removed it and re-added it. I notice it now asks for the pairing code, which I enter but alas doesn't work. Also noticed that my calendar is empty now as well.
Same game over here. Disconnection right after pairing (with my car and Macbook Pro). Driving me nuts -.-
I have the same issue with my galaxy nexus running stock jelly bean 4.1.1. The bluetooth wont turn on and is greyed out in the menu. I just got my phone from this person, and i vaguely remember when i turned it on the first time that the bluetooth was on.(it was running 4.0.4), but im not sure. is this a hardware problem or a software problem? any one has a fix to this?
any help would be greatly appreciated!!
Everyone on this thread, please go star this bug. It appears to be this exact problem. Maybe someone in googleland will notice.
(please prefix with http and remove spaces since xda forums won't let me post a link until I post 10 times. Ugh)
code.google .com/p/ android/issues/ detail?id=35737
Now after updating to 4.1.2. when I don't allow my car access to my phonebook it works! Macbook still disconnection bug.
Not every person in this thread is talking about the same bug.
The bug with this is that bluetooth pairing causes issues with initializing dictation or google now and s-voice.
It is real and easily reproducible on the siii or the note ii, but that's all I've tried. Very annoying bug.
Hello.
I have installed Cyanogenmod 11 on my HOX.
although everything looks to be working fine, I still have issues with my Bluetooth.
When driving in my car, and want to place a call, I used to be able to use Cyberon Voice Commander to place the call.
It still works when i use it on my phone without Bluetooth, but when I am connected to my car everything stays silent.
It worked with stock firmware, and I can recieve calls using bluetooth, and I also can use the car stereo to play music from my phone,
but just making a call with the Voice commander does not work.
Does anyone have similar experiences with this, or does anyone have a solution?
Search the thread, been mentioned a lot there !
Hello,
I have been searching, and also looked in the thread for the HTC (HTC One X CyanogenMod 11.0 nightlies, http://http://forum.xda-developers.com/showthread.php?t=2583037) but I could not find an issue which is matching my problem.
Unfortunately I am (yet) not able to post this issue in the HTC One Cyagenomod thread...
I don't own a BT headset so I can't properly debug the issue. I know that a lot of people complain about it but there is not much I can do unless they actively try to help. You could provide logs when pairing the device, turning it on and when doing a call.
I might by a BT headset in the future. So there is hope .
Hello,
I was not sure which logfiles you wanted, so I grabbed the output from dmegs and made a logcat and put it in a zip fie.
Here they are.
Thanks for your effort, though.
Thanks for the logs.
Can you describe the behaviour a bit more? What exactly does not work? Imitating the call through Bluetooth, hearing your partner through Bluetooth or recording through Bluetooth. And can you test other apps for me. Like Skype or the normal phone without cyberon.
Do you know if your car is recognized as a normal handsfree Bluetooth device or something special? If you happen to know it.
Also some apps (like Google Now) need to be told to use BT devices.
Hello,
Bluetooth itself is working normally, I can use it to play music on my car's stereo, and when I recieve a call it works fine, I can hear the other party, and they can hear me.
It's just when I want to make a call, I can see Cyberon Voice commander starting up, but I don't hear any sound, and it also does not respond on voice commands.
When I disable Bluetooth, the app works normal.
On stock HTC rom, the app also works fine.
I own a Ford Focus 2011, and it shows up in bluetooth as Ford Audio.
The profiles active are audio for telephone and audio for media (sorry, translated from dutch).
The default Voice Dialer at least I can hear on my headset, haven't tried in the car yet with this version of Cyanogenmod.
It does not seem to respond to the micophone though.
The previous version of Cyagenomod would also not play over my car speakers.
Will try again when I get back home, did not use my car today.
Please test tomorrows nightly. I fixed some issues and I think they address your problems.
Try this Kernel http://forum.xda-developers.com/showthread.php?t=2586808 On the latest Version is a fix for BT maybe it helps
Hello,
just tried to test the "Voice dialer" through my car stereo, I can hardly hear it, and it does not recognize anything I say.
At least not in a way it would be useful for me
With tomorrows version you mean CM-11-20140314-Nightly, or the one after that?
Could not see anything about Bluetooth in the changelog, but I'll wait for the next version.
Will report back.
charly_s said:
Hello,
just tried to test the "Voice dialer" through my car stereo, I can hardly hear it, and it does not recognize anything I say.
At least not in a way it would be useful for me
Click to expand...
Click to collapse
With the other kernel? You probably already had the BT fix when using the CM kernel.
charly_s said:
With tomorrows version you mean CM-11-20140314-Nightly, or the one after that?
Could not see anything about Bluetooth in the changelog, but I'll wait for the next version.
Will report back.
Click to expand...
Click to collapse
Yes, 20140314, see line 6.
http://www.cmxlog.com/11/endeavoru#cm-11-20140314-NIGHTLY-endeavoru.zip
Hello,
I tested it with yesterday Nighties, and it's working now.
Cyberon Voice Commander could now be used with the Car bluetooth set.
Thank you for solving this.
I hope the logs I uploaded were of any use.
btw, I did take a look at the change log, and the line "tegra3-common: system/audio.h: Use correct DEVICE_BIT_IN bits" didn't ring any bells in my head in combination with Bluetooth.
Anyway, it is solved for me (and maybe for several others as well), so I want to express my gratitude by saying: Thank you very much:highfive:.
Has anyone encountered issues with connecting with a car bluetooth? My wife phone conntects with no issues.. She can use the cars remotes to make and receive calls.. Mine I have to pick a contact from the phone for it to work, it will not work with the car or my work truck controls.. It seems everytime it ask if my car or truck can access my contacts, I always choose allow, but nothing happens, but it works with the wifes.. This is with the Lollipop update, that we both have...
happened to me I just rebooted my phone and it connected, also check settings for that paired device
Rom-Addict said:
happened to me I just rebooted my phone and it connected, also check settings for that paired device
Click to expand...
Click to collapse
Got one to work, in my truck.. The car it worked for a while, then quit.. I will try it agian to see if it will stcik... Most likely caused by the 5.0 update..
I've noticed a Bluetooth problem that suddenly started in the last week or so. I upgraded to Lollipop when it first hit, and didn't have any problems.
Now, however, after Bluetooth works fine for awhile (I can connect to a Pebble watch, Bluetooth speaker, car Bluetooth, etc) all day long - then all of a sudden it can't connect to ANYTHING. Toggling Bluetooth off\on doesn't fix it.
Restart the phone, then everything works just fine for awhile. Until it doesn't, and I have to restart again.
Anyone else experiencing this pattern?
I've actually had the opposite happen. I have a iSimple bluetooth box in my car. I've never been able to auto connect with either VZW Note2 or 4. The CS rep told me it had to do only with VZW phones and he couldn't help me out. On another forum, another member mentioned he didn't have any issues with his older phone, so I dug out my old HTC Incredible. Sure enough, it would auto connect. Something changed with Lollipop, and now my Note4 will finally auto connect to the iSimple box. I tried using a third party Bluetooth app prior, but it didn't fix the problem.
Finally got the one in the car working as well... Because the wife and I have the same phone, I just simply changed the name of my phone and it works fine..
If your talking about the developer edition one rom update.. YES.. What fixed mine was wiping everything and redoing the one rom lollipop, then twrp, then installing Ricks Rom Lollipop, things have been perfect. I even addressed it in the ricks rom thread the week.
I haven't had any issues connecting devices but since Lollipop, when I am connected to a bluetooth speaker (car, bose, other bluetooth speakers) the audio gets choppy randomly.
I have done some searching and found others (LG g3) who had the exact same issue after updating to Lollipop.
I have tried rebooting, using different music apps, unpairing/pairing, forgetting the device ect and nothing seems to work. Anyone else having this problem after updating to lollipop? Anyone know how to fix it?