Database Develop

Problem with Bluetooth and OUTGOING calls

I'm running into a somewhat frustrating problem with making bluetooth calls on my AT&T Tilt.
(For reference, my Tilt has been reflashed with austinsync's 145mb bigstorage ROM, but the problem I'm going to describe ocurred on the original stock ROM, as well)
Periodically, when I make outgoing calls, the call will disconnect within the first minute. Upon watching the problem closely, I realized that my bluetooth kit (Acura HFL, preinstalled) always showed the calls as "Connecting" and not "In Use" when the problem ocurred. Any time the display said "In Use" I found the calls were not disconnected (unless I hit an actual dead spot)
What I've concluded is that the Tilt is not consistently setting the bluetooth flag that indicates that a call is in progress but, instead, conitnues to transmit that the call is connecting. For many bluetooth headsets, this is an irrelevant distinction; however, some handsfree kits (such as myself) will disconnect on their own if a call is not connected (or reported as connected) within a certain time. A variation of this problem has occurred with random calls initiated from my handset - in those cases, the call gets transferred to my handsfree only if I initiate a "transfer" command from the bluetooth kit; however, if the "call in progress" flag is not set corretly, the handsfree kit assumes that there is no call to be transferred.
In all cases, when my outgoing call was answered, the Tilt, itself, displayed that I was connected, and began running the timer. The problem seems to be limited to having that status transmitted via bluetooth.
I've already tested my handsfree with several other phones; the anomaly appears to exist with the Tilt only.
Incoming calls appear to be immune from this wierdness.
Has anyone else encountered this issue? I'm assuming this isn't a hardware problem but, instead, a bug in the BT stack. Any thoughts on a workaround? Anyone try Jetware with the TIlt/Kaiser? Any guess if that might solve the problem?
Thanks for any thoughts on this!!!
AMG

Spent an hour on the phone with AT&T and then HTC today - they were able to replicate the problem - So I guess there's a fighting chance of getting this resolved somehow, some day... Anyone here think there's a chance of a homegrown fix from this community??

BMW i_Drive has this problem
I too have noticed the problem. My BMW screen shows "Connecting" after I turn the car on, and it stays that way until I do a soft reset. It also seems to freeze the BMW system. It is not every time, but often enough to be frustrating.
We W8z I guess

No issues on my 2003 5 series BMW. I'm running the HTC TyTN II ROM however. I wonder if this makes a difference...

Camstech said:
I too have noticed the problem. My BMW screen shows "Connecting" after I turn the car on,
Click to expand...
Click to collapse
I've noticed an intermittent failure to connect on bluetooth on my Honda too. If I soft reset the Kaiser - I get a BT connection no problem.
Odd!- Lets hope some brightspark in these forums fixes it ASAP! I'd been blaming PhoneWeaver - Ooops
Graham

I've got exactly the same problem with the original (shipped) english ROM and my new Audi A6. If the outgoing call shows "Connecting", the call is terminated any time between 4 minutes 30 seconds and 4 minutes 55 seconds after the call has begun.
I also use Jetware Software to access/synchronize the phone's contacts with the car. I was going to blame them, but it turns out we might have a problem in the WM bt stack... What I read this evening on their (Jetware) support forum: If the phone is connected with a power cable during the call and the screen is left on, the disconnects don't seem to occur any more. If that's true, we're probably looking at some kind of power saving "feature". And who knows, maybe there's a nice registry key ... that said, I'm going to try this out tomorrow and let you know.
By the way: Incoming calls are no problem at all. They show as "Connected" in the car's display, though.

fermin said:
I've got exactly the same problem with the original (shipped) english ROM and my new Audi A6. If the outgoing call shows "Connecting", the call is terminated any time between 4 minutes 30 seconds and 4 minutes 55 seconds after the call has begun.
I also use Jetware Software to access/synchronize the phone's contacts with the car. I was going to blame them, but it turns out we might have a problem in the WM bt stack... What I read this evening on their (Jetware) support forum: If the phone is connected with a power cable during the call and the screen is left on, the disconnects don't seem to occur any more. If that's true, we're probably looking at some kind of power saving "feature". And who knows, maybe there's a nice registry key ... that said, I'm going to try this out tomorrow and let you know.
By the way: Incoming calls are no problem at all. They show as "Connected" in the car's display, though.
Click to expand...
Click to collapse
No luck. Whether it's connected to the power or not, screen off or on, no change in behaviour.

I"d like to chime in on this but I know I probably shouldn't, mainly because I haven't used the phone to make a call in my car long enough.
I had an '04 TL and my Tilt paired and worked fine on it. In the 3 weeks I had the phone, there was only one instance where the phone dropped its BT connection and I had to pick up the handset. All of my calls have been anywhere from 1 min. to around 5 min. I can't recall making any calls longer than that.
Just recently, I traded my '04 for a '07 TL. It paired up easily, voice recognition is a lot better, and my calls come in more clearly than in my older TL. Again, no conversations longer than 5 minutes. I may try to have a longer conversation on my drive home today to see the response.
Thanks for the heads up. I'll definitely keep an eye out for some of the symptoms you're experiencing.

I too have this exact problem. I have an '07 TL Type-S, and an AT&T Tilt. My phone worked fine until the 2nd official WM 6.0 release back in February, then it started exhibiting these exact symptoms. I'm now using Dutty's WM 6.1 and it is still happening but not as much. Hopefully we can get this fixed someday!
Does Bluetooth relate to the radio version? I wonder if I could get a WM 6.1 with an older radio if that would fix the problem?

Motorola S705 A2DP bluetooth headset

What a truly excellent headset, this is the first headset I've ever had that just works.
On the Bluetooth side of things it claims to have hundred metre Bluetooth, which I always thought would only work if the device it is connected to is also hundred metre capable, which may or may not be the case as I have not been able to get a hundred meters away yet. What I will say is that unlike any other headset I've ever had, I can for the first time freely wander around my flat without any audio dropouts or interruption both on phone calls and whilst listening to music no matter how far away from my phone I get. The fact that it has a standard headphones connector is a brilliant idea and allows me to use my Sennheiser's
Another first is the FM radio, that actually does work using the headphones cable as the aerial. I have had several devices in the past that have attempted to do this, and none have ever worked properly as they tend to only find the strongest signals (the worst offender being the Nokia HS-12). As an added bonus the radio is also RDS.
It has a simple but intuitive menu system, the sound quality is excellent but thats probably more to do with my headphones than the actual device.
The downside is that it is a little bit big but this just makes it a comfortable size to use.
It is hard to put into words how well it just works, my previous headset a Sony Ericsson HBH970, had some funny quirks. For example, when in stereo mode if you have audible taps enabled it would be mute for the first four screen taps, and then on the fifth screen tap It would play all the taps together as though it had been buffering the audio, whereas this plays them as they happen. I think ultimately, quirks like this come down to the fact that the majority of headsets that we purchase are not designed to be used with PDA phones, but rather specific phones from the same manufacturer as the headset, this device has been designed from the ground up work with everything. Or so, it says. and I for one believe it.

does it have vibrate option?

nope, my other option was the itech clip D-radio (not to be confused with the itech clip radio), which does vibrate, and also has the abilitiy to let you look though your last calls list and dial from that ! but availability is an issue because it is new, so unless you want it from a dodgy hong kong ebayer with only 95% feedback and a history of selling counterfeit items. you will have to wait !
PS it has no RDS and only 10M bluetooth but is otherwise very similarly featured

ice_coffee said:
nope, my other option was the itech clip D-radio (not to be confused with the itech clip radio), which does vibrate, and also has the abilitiy to let you look though your last calls list and dial from that !
Click to expand...
Click to collapse
Are you sure the D-radio vibrates? The sites I see says it has "3 buzzer alert modes for incoming calls" which I thought probably meant it has three different ringtones built in for different caller IDs.

hmmm you have got me thinking now, but im fairly sure I read that it vibrated, but maybe your right.

ice_coffee said:
hmmm you have got me thinking now, but im fairly sure I read that it vibrated, but maybe your right.
Click to expand...
Click to collapse
I hope you are right. I really need a pendant style A2DP headset that vibrates.

I thought it's not being sold any more? I was looking to use it with the bluetooth vibrating bracelet but couldn't find it on the moto website.

One issue ive never seen mentioned>

Hello everyone
I recently, (finally) ordered a headphone/usb splitter thingy so i can play my tunes off the tilt in my car. Either thru an fm transmitter or a headphone/tape converter i put in the tape deck in my car. First off, im totallly impressed how great the sound is thru the stereo, a combo of car stereo settings/ and the audio booster/equalizer make even slayer sound good at the proverbial (11).
My question is this, im not sure if the att sites around here are jacked way up (power-wise) or what. But that annoying beeping, fluttering, digital sound you get thru your house speakers if you set your phone to close (or your tv or anything else w/a speaker for that matter)... its happening in the car also.
I can understand when im using the youtube player, the thing is streaming.
But even just playing mp3's or watching a movie thats on the SD card, i still get it from certain towers in certain towns. We have hellacious service here in New England, with alot of the towers on major routes not even doing handoffs correctly, resulting in missed calls etc. So i have a reason to wonder if its the service im getting i suppose.
Being the (non) brainiac that i am, i took a shield from a 25 pair cable i was punching down at work the other day, and put a large piece of it over my headphone wire/connector. Would this do anything? Is there such a device you could buy? (some sort of RF/emf shield?) It seems to work if the phone itself is the problem (youtube)... however coming thru by a certain cell tower again the other morning, that thing was chirping and burping like 2 dollar gutter whore.
Any suggestions or comments on this are appreciated, sorry for the rambling.

I live in North Mississippi near Memphis and have experienced the same issue. Sorry that I am no help towards a solution. Just thought I would let you know you are not alone.

freekquency said:
Being the (non) brainiac that i am, i took a shield from a 25 pair cable i was punching down at work the other day, and put a large piece of it over my headphone wire/connector. Would this do anything?
Click to expand...
Click to collapse
Nope, the RF emitted by the phone is acting direclty onto the low level circuitry inside the car radio.
Even if you're not streaming anything, when the phone switches to another cell toper it notifies it that it has done so, and thus will communicate for a moment. How often it will do so, whether it will be on every tower or only after defined amounts of time, or even every group of X towers is defined by the operator. If you say coverage is know to be bad they might have just set it to notify on each tower and the phone is often switching.

Sometimes placing your phone on an antistatic bag, like Hard Drives come in helps. At least it does with computer speakers.

The noise is referrd to as RFI (Radio Frequency Interence) and EMI (Electro
Magnetic Interference). Both of these are what is affecting your system.
As your phone gets POLLED (Where are you message) by the cell phone tower, it responds with a "Here I AM" message. Its this initial communication
(handshake) that that is causing the interference.
http://electronics.howstuffworks.com/question230.htm
From another website:
"a cellphone tower can only support a limited number of simultaneously
connected cellphones. It therefore needs to know exactly when a cellphone
leaves its range, or disconnects from the network altogether, so it can free
up its connection slot for use by another cellphone. Normally a phone
communicates a disconnect to the tower whenever possible (for example if
it's getting out of reach and connects to another tower, it then disconnects
from the first and the connection gets transferred gracefully from the old
tower to the new one, even in the middle of a conversation). However, if you
just yank out the batteries, the phone gets utterly destroyed, you suddenly
enter a cage of faraday or even an underground tunnel, ... the phone will
have no time to notify the tower, so the tower needs to check up on
supposedly connected phones from time to time to check that none of them are
MIA. It's basically similar to an ICMP ping on the Internet. And that's what
you hear over your speakers. Similar thing happens right before a call or
SMS comes in, or when you dial out: there's two-way communication, and the
RF interference the cellphone puts out is picked up by your audio
equipment."

Either move your phone, or turn it 90 degrees to the right or left. It has to do with the phone switching over to Edge (or if it's always on Edge, you're gonna get it regardless) and the speakers are picking up the radio traffic as interference. It shouldn't happen when the phone is on 3G/HSDPA. Just repositioning the antenna, i.e. the phone, has always worked for me. You could also look up distortion reducing tricks, there was something on Makezine.com about putting magnets on the speaker wires to get it to stop, but I couldn't find the entry right now.

Cool beans, thanks for all the info. I understand about handshakes and all that and figured that was exactly what was happening. Doesnt seem to matter 3g/H/E certain towers do it no matter what im doing. As i noted the towers around here have been having major issues w/ handoffs so who knows. BTW not only does your cellphone poll constantly, but usually your phone call is happening on at least 2 towers at a time. So once tower A gets more signal then tower B it switches over to A (which already has your call processing at the same time) So yea its gonna happen no matter what i do. Truthfully its not that big of an issue, but i just came up w/ the greatest cheapo mount, and of course where i have the dam thing is directly over the stereo. lolz
Thanks again!

[Q] GNote voice control + BT headset = Inconsistent and VERY UNRELIABLE experience.

Is this a rant or do I have valid questions? I guess the moderators will decide.
I have done a bit of searching here and on Google about: Vlingo, GoogleVoice Talk, Samsung powered by Vlingo on the GNote and I cannot believe I am not catching more hits about others “complaining” about the inconsistent behavior and general unreliability of voice control on Android and the Gnote in particular.
Add Bluetooth to the mix and it becomes MOST frustrating. I use a PlantronicsVoyager Pro+ headset.
I long push the BT headset button and never know what to expect; will it work this time, will it not?
· When I get a response from the phone, by that Imean the phone switches to the voice control app, It sometimes announces how many missed calls I have and then prompts me “voice talk is ready” or at other times “Vlingo is ready”. Sometimes it just announces how many calls I missed and goes no further, at other times after announcing the number of missed calls it will continue on to state that “it” is ready at which point I can say “Call blahblah at home” etc.
· Many times the phone just does not react at all as if I did not long push the button on my BT headset even though in Settings> BT settings on the phone it shows that the headset is paired.
· Some days, when the line item above occurs, I click on my “paired” BT headset listed in BT Settings and I can hear the acknowledgement tone in my ear “The Voyager also has a voice that states “Phone 1 connected “ and then I can initiate a call via BT. After I end the call the connection to my BT headset drops off again and I cannot initiate another BT session unless I again tap on the paired BT headset listed in BT settings..
· I can often resolve these issues by either powering off\on the BT headset or by rebooting the phone.
· Again, without changing any settings in Vlingo,Voice Talk or with BT settings; Some days I get an announcement that I have a new TXT message (in my headset and via the speaker which of course to me should be either\or but not both, sometimes the announcement tells me who sent the TXT msg. and speaks out the message that was sent, other days I don’t even get an audible notification.I am NOT making any changes to any of the settings at this point.
· Somewhere in the settings section of the phone,Vlingo or is it voice talk I was able to select a specific sound to play for incoming TXT messages which I have yet to hear played when a TXT msg. is received.
Oh and yes, there is a difference in the way things behave based on if the phone is charging or not or if the screen is off or not.
I also find it rather confusing with the various settings that control all this being spread across numerous different settings screens. By that I mean Android has a settings> Voice input and output” page Vlingo has its settings pages, Voice Talk as well and who the hell knows which one has president over the other, or which program is going to do your bidding, etc.
All very confusing and unfocused IMO.​
I wonder if anyone at Samsung, Vlingo or Google for that matter has tried to use this “Voice activated solution” on a daily basis.
I’d like to see the chairman of Samsung, Geesung Choi, give this a go and hear his opinion on all this as Samsung has gotten into bed with Vlingo on the GNote to the point where you cannot disable it.
I come from Windows Mobile and MS Voice Command which obviously is not in the same league as these solutions, nor with Apples Siri BUT for what MSVC was, it was reliable and one could count on being able to use voice control over BT and expect it to make a damn phone call or tell you the correct time without sending you to a website.
I am not sorry for the rant here!
It seems to me that the Android OS, these third party voice solutions and the whole thing needs to be more cohesively integrated within the OS and the various apps (email, messaging, calling, etc.) and implemented in such a way that it simply works reliably!
I know that some of the inconsistencies I list above may be due to a variety of causes. HW, SW, BT stack, Voice Apps, etc. and not to forget pilot error (me). But we are dealing with a great phone, a highly configurable OS and a great BT headset and the results are less than stellar here.
We are upon ICS and if this stuff does not “come together” in its implementation and become much less fragmented and confusing on how to configure the mess of settings, Google should not be surprised to see many people choose the iPhone because no matter what one thinks of the iPhone, it isv ery consistent and cohesively thought out and gives the end user a feeling that I wish I had, and no I am not a fanboy of the iPhone, I am simply statinga fact that many people would agree with.
“It simply works”.
Not to lose sight that I am asking questions here:
Am I the only one experiencing these inconsistencies and frustrations?
Am I the only one who sees these settings spread out all over the place as less than ideal?
Do we have to accept that Android is an open environemt to mean a lack of consistency in the way apps are configured and customized?
Is everyone just "dealing with it" and willing to accept this as status quo?
AND PLEASE DO NOT FLAME ME for sharing my frustrations and my opinion. I need to be able to rely on hands free communications and I need it to work. I need the large screen of the GNote and I love what Samsung has given us.
BUT
I need it to work!
I will now go back and play with all these settings and see if I can make sense of it all.

Bluetooth/Phone Call Issues, Anyone?

Has anyone else been unable to make phone calls after connecting to your vehicle's bluetooth? Most of the time, I can make phone calls without issue. Sometimes, I can't even hear the call ring when I'm connected to bluetooth. Occasionally, when I turn my vehicle off, the call goes silent instead of transferring to the earpiece on the phone. The only way I can fix the issue is rebooting the phone. This has become increasingly frustrating for me, since the issue is so inconsistent.
I'm running the stock ROM, rooted and un-encrypted.
Thanks!

Same here
I'm having the exact same problem you are having with my Ford Touch Sync, Bluetooth has work maybe once. At other times only the music over bluetooth has work. But was unable to make hands free calling! I also made my ford touch sync a trusted device, and the problem with connection still continues! Hope someone could provide some suggestions
Stock rooted- TWRP- encryption removed

I am having issues also. Just today, my phone shows I am connected to my Pioneer Navi head unit, and the Pioneer shows connected to my phone. I proceed to make a call. The audio on my radio mutes as it should, and nothing. No ringing, no busy signal nothing. so i hang up and try three more times. on that third retry, i heard the other party faintly, realizing that even though my radio muted and shows BT connected, the call went through the ear speaker on the phone. When I hung up the phone, my radio unmuted.
Last week, I was having issues where i couldnt hear any rings or busy signals. It would be silent for 20 seconds or so, then i hear the other party say "hello".
I honestly thought it was my head unit, since it is about 4 years old. But now I see others with similar issues on other brand bluetooth systems in their cars.

robbnice said:
I'm having the exact same problem you are having with my Ford Touch Sync, Bluetooth has work maybe once. At other times only the music over bluetooth has work. But was unable to make hands free calling! I also made my ford touch sync a trusted device, and the problem with connection still continues! Hope someone could provide some suggestions
Stock rooted- TWRP- encryption removed
Click to expand...
Click to collapse
I just got my N6 today and I'm having trouble with My Ford Touch as well. I can get it to pair and play music, but it won't "connect" to my phone. It's odd because my N5 works fine with it. I would assume the N6 wouldn't be different.
We probably have to wait for an update from Ford, which will probably take months...
EDIT: Well I decided to try it again. I deleted the Nexus 6 entry as well as the Nexus 5 entry. Went through the pairing process again and it worked as intended. Not sure what happened the first time.

I ran into the same problem as others where my N5 worked flawlessly with my Ford Sync in my fusion, but the N6 is terrible.
I love the phone, but this is really annoying. I get into the car and sometimes it connects immediately, other times I have to turn off and back on the bluetooth about 3 times for it to finally connect. Very weird. Ford offers an upgrade to my Sync system, but wants $50 to do the upgrade. Pass.
I might try what the other person did and delete all entries for phones and pair it again. Unfortunately, the weather is pretty bad outside, so it might need to wait a short bit.
Has anyone else had luck re-pairing with their car and had reliable connections?

I use Ford Sync.
robbnice said:
I'm having the exact same problem you are having with my Ford Touch Sync, Bluetooth has work maybe once. At other times only the music over bluetooth has work. But was unable to make hands free calling! I also made my ford touch sync a trusted device, and the problem with connection still continues! Hope someone could provide some suggestions
Stock rooted- TWRP- encryption removed
Click to expand...
Click to collapse
I use Ford Sync, and everything works as expected. I am Stock and unrooted. I guess it would come down to what version of Sync. Mine is from 2012. No touch screen. I also delete all other entries on the system and start from scratch making sure that the N6 is the main device.

If I can wake up the screen on my own, outgoing calls work fine
PaisanNYC said:
I am having issues also. Just today, my phone shows I am connected to my Pioneer Navi head unit, and the Pioneer shows connected to my phone. I proceed to make a call. The audio on my radio mutes as it should, and nothing. No ringing, no busy signal nothing. so i hang up and try three more times. on that third retry, i heard the other party faintly, realizing that even though my radio muted and shows BT connected, the call went through the ear speaker on the phone. When I hung up the phone, my radio unmuted.
Last week, I was having issues where i couldnt hear any rings or busy signals. It would be silent for 20 seconds or so, then i hear the other party say "hello".
I honestly thought it was my head unit, since it is about 4 years old. But now I see others with similar issues on other brand bluetooth systems in their cars.
Click to expand...
Click to collapse
I have a Nexus 6 running Benzo ROM (5.1.1) and I have a GPS Nuvi 3580 bluetooth-enabled which I want to use to make calls while driving. I have added this device to my trusted devices so my phone unlocks as soon as it connected to it.
If my phone screen is on, then I'm able to call anyone from the bluetooth device, no issues. But as soon as my screen goes off, I can't make calls and when I switch on the screen on my own, I see a message "Process system isn't responding. Wait or close?"
Irrespective of what I select on this message, the call goes through. But it totally defeats the purpose of handsfree bluetooth mode. Is there something that is not allowing the bluetooth device to wake my phone up.
Also when I receive an incoming call, I see the notification on my GPS but I can't receive the call in one go. It takes multiple calls for it go through. I have also noticed that my bluetooth device keeps disconnecting and connecting without any change on either the phone or the GPS side.

androidfan91 said:
I have a Nexus 6 running Benzo ROM (5.1.1) and I have a GPS Nuvi 3580 bluetooth-enabled which I want to use to make calls while driving. I have added this device to my trusted devices so my phone unlocks as soon as it connected to it.
If my phone screen is on, then I'm able to call anyone from the bluetooth device, no issues. But as soon as my screen goes off, I can't make calls and when I switch on the screen on my own, I see a message "Process system isn't responding. Wait or close?"
Irrespective of what I select on this message, the call goes through. But it totally defeats the purpose of handsfree bluetooth mode. Is there something that is not allowing the bluetooth device to wake my phone up.
Also when I receive an incoming call, I see the notification on my GPS but I can't receive the call in one go. It takes multiple calls for it go through. I have also noticed that my bluetooth device keeps disconnecting and connecting without any change on either the phone or the GPS side.
Click to expand...
Click to collapse
Since I last made that post you quoted, i purchased and installed a 2015 model of the Pioneer AVIC-8100NEX. It has Android Auto, but can be used with the regular Pioneer UI also. I have had no issues anymore with this new radio. Maybe the BT protocol in the radio is newer? Im not that tech savvy to know. But the 2015 radio had no issues with BT calls anymore, on Pioneer's UI or Android Auto's UI.