I've looked for threads relating to this specific issue both here and in Google, but found no results yet.
I have a HTC Trophy that was previously connected to my car's Bluetooth system - I was able to browse my contacts, place and answer calls. This worked both on the launch firmware and in the NoDo update.
I recently upgraded to the Mango developer beta (needless to say - I'm not a registered developer...), and the Bluetooth seems to be having some problems. Just to be clear, I've already deleted and repaired the devices, even rebooting the phone and turning off the car first. The thing is: the phone connects to the car, and it even reads text messages out loud and takes voice commands (e.g., "call back" or "ignore" on the text message)... But calls simply don't work, whether I'm placing or answering them: the car's screen simply shows a "connecting" message, but the sound doesn't get put through. The phone also shows that it is placing the call. If I'm answering a call, the car displays the "connecting" message and the phone simply keeps ringing.
Does anyone have the same problem? Are there any reported fixes?
I have the same issue with my HD7 connecting to my factory fitted BMW unit in my E46.
The phone and car pair up, I can read my text messages on the nav unit, but incoming and outgoing calls only route through the phone, not the head unit.
I was having issues on NoDo as well where connection would keep dropping.
Since I installed Mango 7720 it has a stable connection, but no audio.
Head unit works flawlessly with my iPhone 4, so I'm guessing the HD7 is at fault somewhere.
The upgrade to 7720 solved the issue for me - calling and message reading are both working fine. The contacts don't all show up on the car's screen, though...
EvilAgent, Do you happen to have a BMW? I have a trophy with 7720 and when streaming mp3's over bluetooth to my car, the audio quality is bad. Do you have a similar experience?
It is a BMW, but I don't use Bluetooth to listen to music, I just go with the cable
Related
I have the Kenwood DNX8120 and it works fine with my Fuze (did have disconnect issues but just updated the Kenwood firmware which should take care of that) but the SMS feature on the radio doesn't work. I know only certain phones are compatible with this feature but on the Kenwood compatibility list there are several HTC devices that work. In any case, does anyone know how to enable SMS over bluetooth on the Fuze?
Thanks
I have the Kenwood DNX8120 in my car and have had no luck getting the Fuze to work correctly. It constantly drops connection. I updated the Bluetooth firmware and that only seemed to make matters worse. It will pair with the Kenwood, but either won't make a phone call or will take up to 60 seconds (or not at all) for the Fuze to recognize I it the call button on the radio. SMS, sent and received call history also do not work.
Have you had similar issues?
I can not get sms working. The only other issue I have is that after a call, it drops the connection. If I get another incoming call, it will reconnect and the radio will ring and handle the call. But, if I want to place a call, I have to either select "set as hands free" of something similar, in the bluetooth settings on teh phone and it reconnects and I can dial. I just upgraded to elite rc3 and the problem is still there. I havn't messed with it enough yet to know if it dials ok without having to bring the phone out of standby yet. I too have updated the bluetooth drivers from Kenwood and that didn't help. I also tried the jetware handfree extension and didn't see any improvement.
I called HTC about this, and they told me it only "officially" supports a hand full of car units. Mostly in the Audi and BMW. They don't "officially" support anything from Kenwood so they were absolutely no help on this. I've also noticed this phone drops all connections except cell and data when it sleeps. Wifi, GPS and Bluetooh all seem to go to sleep with the phone. This seems to make bluetooth pretty useless if the connection drops every time the phone sleeps and needs to be manually reconnected.
I haven't seen it drop the bluetooth connection during sleep. I see that the Kenwood supports some HTC devices but not this one specifically. The other wierd thing is that the first time it pairs it shows the battery indicator but after the next connect it doesn't show it. It shows the battery icon but shows it empty. The jetware extension however does fix that. I will play some more with it and report here.
After resetting my phone to AT&T's original setup, I am experiencing the exact same functionality as you. It now sync's my call history and phone book. No voice dial support or SMS yet. (These have never worked with any of my phones) It will disconnect after a couple phone calls and I have to set as hands free to reconnect. Also, mine still looses the connection to the unit when it goes to sleep. I'm keeping it on a car charger for now and turning off any sleep function when charging. That at least keeps it connected until I make a call. It's almost still not worth using with having to reconnect hands free. Maybe if a hands free quick connect shortcut could be created?
This is all really ridiculous that a phone with this kind of tech can't auto pair and be ready for a call. My LG Chocolate had absolutely no problems with the Kenwood. As soon as the Kenwood finished booting the LG would auto connect and be ready for a call.
I thought I found a workaround at
http://forum.xda-developers.com/sho...ghlight=bluetooth+connection+drops+phone+call
But, once installed an trying to run BT Restart I get an error saying that I need .net compact framework (version 1 or 2) installed. Not sure what to do now, cant seem to find a cab for this.
I've used this package from another post on the forum. It has many useful apps including the latest version of .net compact framework.
http://www.tyguy.net/_xchg/PPC/@essentials.rar
Let me know how it turns out!
I will take a look but I have 3.5 already installed. I guess that app needs the older version. Not sure I want to mess with downgrading it.
Not Kenwood
Hey Guys,
I drive a Jag XK8 and it has the same issues you are mentioning with your Kenwood, but its an Alpine unit, it drops calls, and after the first call connects the second call rings on the stereo but you can only answer on the handset.
I also recently had a new Jag XF for a week. It had a full integration to the phone. It also only showed the battery status when the phone first connected then the battery showed empty. It would drop bluetooth connections constantly on some days (every 90secs) and then somedays it would keep the bluetooth connected without issue. Very unreliable.
The reason I bring this up, is just to let you know these issues are not limited to the Kenwood.
Dave
Just an FYI. I have found it easier to just go into setup in the Kenwood and reconnect the bluetooth from there when the phone disconnects. It's under Setup/Bluetooth/Set, then just click on the device and hit connect. It seems easier than fiddling with the phone while your driving.
Upgraded my HD7 last weekend, very smoothly but now struggling to connect it to my BMW Bluetooth car kit.
Phone and headunit pair up with no issues, and I can access the address book and SMS from the nah screen but it will not route telephone calls through to the phone.
Also the Bluetooth connection icon on the HD7 top bar doesn't show up making me think something is wrong with Bluetooth radio on the phone.
My iPhone 4 connects fine and works with no issues making. Me think HD7 id more at fault
Sent from my HD7 T9292 using XDA Windows Phone 7 App
I can connect ok to my bluetooth stereo but I have noticed that with mango music cuts out more often and turn-by-turn navigation voice prompts don't work well. It apparently tries to connect as a phone call and cuts off all but the last few words.
Im seeing a large trend of HD7 with bluetooth issues. I have a trophy and dont have cutting out issues but I do have poor bluetooth music quality. Try this registry fix and see if it solves any of your problems. http://forum.xda-developers.com/showthread.php?t=843593&page=2
I also have a BMW with idrive. Where do you go to check SMS?
I m having issue of my Focus's BT not working. Whenever i turn on the BT is goes into searching mode and doesn't come out of that.
anybody facing the same issue?
mine is OS version: 7.10.7720.68
Not exactly, but in my opinion WP's Bluetooth software is just horrible.
It has two options - on and off. You can't change your phones BT name, you can't be invisible with bluetooh on, you can't transfer files. My sister can't sync her WP with her car, whereas I (on Android) just turn BT on and it syncs instantly.
I hoped Mango would fix that, but it didn't. It's just crap.
bluetooth isn't the best part of wp7 for sure...but it sync easy with an headset or a car stereo...
reading some threads about it i found that samsung devices have the worst wp7 BT hadware...
still, i'm alright to say that files transfers should be enabled
hmmm....my focus synced with my car stereo once....but recently it has started go into "Searching" mode and doesnt sync with car stereo
I only use Bluetooth in my cars and all my previous phones worked perfectly (iPhone, iPhone3G, iPhone4, Lg Quantum, Samsung Focus).
The HTC Titan on the other hand sucks. My two vehicles handle things different.
The Challenger (factory BT) will hold onto the call even if the car is off and the door open. The call will switch back to my old phones when out of range (basically in the house) or i manually shut off bluetooth.
The Jeep (aftermarket radio) once you open the door with the car off the call goes back to the phone.
The Titan has a problem were 1/2 of the time when the call is transferred back to the phone either manually, because the car turned off, or im out of range. The mic will not engage. I can hear the person but they cannot hear me.
Haven't had a problem with my Trophy... previous car was a Lexus IS220d and it synced and worked fine.
Currently driving a Jeep Wrangler and only once I've had the "searching for device" issue.
Bluetooth on Wp7 is quite poor. You can not select, which service an adapter shall support (handsfree and A2DP). It always use both services.
Windows Phone's Bluetooth support is abysmal, but you know what's worse: Samsung's support for Bluetooth on Windows Phone. Their last firmware update for the AT&T-branded Samsung Focus reduced out-of-call Bluetooth volume so that it's way too soft and text-to-speech is impossible to use because you can't hear it. If you turn up your Bluetooth headset or car volume to compensate, then in-call volume is way too loud. There is no fix or solution, except to restore the old firmware through Zune's backup. I've been running 2103.11.3.3 instead of 2103.11.8.1 for about 5 months now. I couldn't be more furious about Samsung and AT&T's lack of urgency to fix, or even acknowledge this. I'd even deal with the disappearing keyboard (as I have anyway) if it means keeping Bluetooth working. Regardless, after this experience I will never buy a Samsung phone again.
WP7 lacks rSAP, and for many of us with European cars are SOL. Wish Microsoft would listen as many of us have complained about needing rSAP.
Hello, hope you can help me with this issue... I've done a search but not come up with anything exactly the same.
My OPO used to work with my Sony MEX-N5000BT head unit (A2DP and AVRCP 1.5 compatible). It would pair straight away, no issues whatsoever.
I never got track info showing on the head unit (maybe the stereo was falling back to AVRCP 1.0?), but it would successfully play music and allow me to skip through tracks using the buttons on the Sony.
The phone function worked fine. I'd select BT Phone on the head unit, it'd let me choose between Phonebook, Redial, Recent Calls etc and would populate all of those lists.
I don't drive every day but do upgrade nightlies most days. I think I first noticed the following issue after flashing 17/10/14 nightly, but it may have been earlier. I can't find earlier nightly changelogs, so I don't know what changed around that time.
Since then, the BT Audio function mostly works fine, although the connection as a whole seems a little less stable and seems to struggle to maintain a bluetooth connection.
The BT Phone side of things has basically stopped working though, despite the head unit indicating that the BT phone and BT media connections are available. If I select BT Phone and try to access my phonebook, redial or recent calls I get 'No Suprt' or 'No Device'. If I switch bluetooth off and on again, I occasionally get 'Listing' which would previously flash for a couple of seconds before showing me my full contacts list. Now it just shows listing forever. I have once managed to get it to show me the full contacts list, but I'm unable to select a contact to dial.
I have successfully received one call via BT since this issue became apparent, but BT seemed to drop after a couple of seconds and the call reverted to my phone.
I've attached a logcat of me attaching to the BT head unit, playing media, then trying to access phonebook to make a call.
If anyone's able to suggest what the issue might be I'd really appreciate it!
Thanks in advance!
I just flashed the OTA update for Android 6.0 last week on my Nexus 5 and I noticed that with the new update, phone calls no longer get routed through Bluetooth on my Mazda3. It is able to pair fine with the car and can stream music through Bluetooth, but calls do not go through.
Here is what happens:
When I place a call, the audio automatically gets routed back to the phone. If the other person picks up, calls will continue going through the phone speaker unless I manually select route through Bluetooth. Sometimes this works and sometimes it doesn't, but it does get frustrating trying this workaround especially while driving.
I tried unpairing and re-pairing bluetooth with the car, cleared the data and cache of the Bluetooth app on the phone, and even tried a factory reset, but the problem still persists. Anybody else run into the same issue and found any possible fixes?
For the record, when I did this with Lollipop 5.1.1, it worked without a hitch.
Thanks!
I am having a similar problem trying to connect my Nexus 5 running Android 6.0 to my JVC car stereo. It continually complains of an invalid key, albeit both phone and car head unit show the correct key.
I am unable to make a bluetooth connection at all with the stereo. I had no issue with my Nexus when it was running 5.1, and my iPhone 5 continues to pair with the stereo.
I had this issue on the last preview but haven't seen it yet on final 6.0. For either regular calls or Hangouts calls.
I just rolled back to 5.1.1 and Bluetooth calls work fine with the car now. So it appears that it is a problem that is resident in 6.0.
Same here, but a little different: It pairs and when I start a call from the menu it goes down but the call is still up on the phone. When the other person picks up the call is re-routed to the car speakers... very strange behaviour!
Same behavior as what you are seeing when paired to a '15 Accord but works fine on a '14 Camry.
im at 6.0.1 and has the same problem, streaming music through bluetooth is ok but no voice call...
Any news on this? My wife's nexus has same problem. Nexus 5 with Android 6.0.1. compiling version M4B30Z.
I read on a different site to disable wireless scanning in location. Just tied that and have been able to make and receive calls from the car. Will be interesting to see if it continues to work.