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?

Callers deafened by ringtone when I answer by Bluetooth

Anyone else got this issue and is there a new bluetooth stack or something to resolve it?
When I click the answer button on any bluetooth headset (currently using the iqua solar powered one), the sound is temporarily diverted to by mobile before the bluetooth properly picks up, and also during that slugging moment, any ringtone playing is diverted to the caller's earpiece (i.e. sent out by my mic).
One caller complained it had nearly deafened them.
Anyone able to help?

Having the same issue with my parrot bluetooth and my Tilt

Can someone purrlleeeease help with this issue? I am now scared to answer any calls, lest I get shouted at with, "GOD WHAT WAS THAT NOISE? IT NEARLY DEAFENED ME!"

You really haven't give a lot of info here.
I mean what Rom are you running, what BT hardware and reg tweaks do your use etc.
Info is required to be of any assistance.
Note my signature shows exactly what Rom(s) I'm currently using.

Many thanks. Here are my versions:
HTC TyTN II
ROM: 1.0 Sleuth
ROM date: 08/28/07
Radio version: 1.27.12.11
Protocol version: 22.45.88.07H
Essentially I think a new Bluetooth stack might solve it, but I really wish to avoid losing all data by flashing a new ROM altogether.
A new Bluetooth stack on its own would be wonderful... or a way to restore my data back to a newer ROM. Would Sprite Backup do that if I use Sleuth's WM6.1 ROM?

CJSnet said:
Would Sprite Backup do that if I use Sleuth's WM6.1 ROM?
Click to expand...
Click to collapse
I know the commercial version is supposed to support "Rom Upgrade" support but I'm not sure if that is in the version that is floating around the forums.
What you can do though is make a backup prior to upgrading.
Then upgrade to test if the problem is fixed in one of WM6.1 roms.
Then downgrade and restore your back-up.
Now you will know if there is even a point to expending the effort of trying to extract the BT Stack.
Don't take offense at this next statement but if you put forth that effort it might endear someone more skilled to your cause as you've provided a "Proof of Concept" so to speak.

Okay I have just upgraded to Sleuth's v3 (WM6.1). Sadly the bluetooth issue remains, despite the new Radio version.
If someone calls, and I answer using the bluetooth headset, for 1 second their audio is output to the speaker of the Kaiser. I believe it is during that second that they also hear the end of the ring tone, which is what deafens them.
An unsatisfactory workaround is to use a quite ringtone or vibrate only, but that is hardly ideal. If anyone knows of any other solution or a bluetooth stack that is a bit snappier when answering via headset, it would be great appreciated

CJSnet said:
Okay I have just upgraded to Sleuth's v3 (WM6.1). Sadly the bluetooth issue remains, despite the new Radio version.
If someone calls, and I answer using the bluetooth headset, for 1 second their audio is output to the speaker of the Kaiser. I believe it is during that second that they also hear the end of the ring tone, which is what deafens them.
An unsatisfactory workaround is to use a quite ringtone or vibrate only, but that is hardly ideal. If anyone knows of any other solution or a bluetooth stack that is a bit snappier when answering via headset, it would be great appreciated
Click to expand...
Click to collapse
Same issue here with the same new ROM.

I'm having the same problem. When I push the button on my BT HF it gives a horrible noise to the caller at the other end for a second. In my case I doubt it is ring tone, it doesn't sound anythin like the tone I'm using, it's just like loud crackling or smth.
I can't give you any version numbers cause by TyTN II is sent off to warranty (3rd time already). This time it stopped accepting and making calls while showing 3G symbol. Previously I had band selection on auto and had no problems. Now even after hard reset no calls could be made so off it went again. The first two faults where the speaker and the "Fn" light.

I am having the same problem, the handet is at HTC's repair facility for this and a few nagging issues. I will report what they find.
Mine isn't so much the ringtone it just sounds like a loud static sound. I thought it was the headset but I tried it with 3 different headsets and the Bluethooth in my car and they all have the same problem.

Got my phone back today and I can't say I'm impressed with HTC. First they requested that I send it in the original box then must have thrown it out and sent it in some crap box without enough padding. They didn't even send a note or invoice saying what had been done, which was nothing.
They claim they couldn't find anything wrong and when I called support the guy thought it a joke.
Needless to say it is still deafening and I am pissed.

Same Issue Here... It is almost as if there is a dely in cutting off the WAV/WMA file. Bluetooth Picks up and and both parties get the end of the ring tone.
Had the issued with the origional AT&T rom
Have the issue with Slueth 3.0 and Alex 5.2
If anyone finds a fix please let me know...
I am using PhoneAlarm - Don't know if that is related.

I've had the same complaints from some of my callers, and try to answer between rings as much as possible. The complaints have gone way down. Of course, we shouldn't have to jump thru hoops to answer our phones!

Does anyone have contact info to point HTC to this worrying thread? We need a patch release ASAP. A phone that can't answer calls properly? Yikes.

No issues with my BlueAnt Z9. Have you guys tried different headsets?

I think you may have just been lucky. It is uncommon to A) answer during the ringtone, and B) have the caller complain about the loud noise.
It happens on my Bluetooth earpiece, and Nokia car kit, and JVC car kit. So, it is for HTC to resolve.

I've tried three headsets and it happens on all of them. It happens even when I have the phone on vibrate.
I spent an hour on the phone with HTC support and they are awful, even after telling her that it happens on three different headsets she says that is sounds like a headset issue not an issue with the phone.
When I explained for the third time that I would agree if it happend with one headset but since it happens with all of the headsets it would support my arguement that it is an issue with the phone.
It was like talking to a wall. I wish I had an alternitive to HTC at this point, I love their design and have never had a problem with any of their other phones but this their lack of support is amazing.

I think its with all HTC phones. Happened with my Dash - Wing and now Tilt.
But I've never had anyone complain about hearing music on their end...I can just hear it on my headset for about 1 sec. I've also had my SMS tone play wile on a call and also my VM tone play while on a call and I've asked them if they heard that and they said no.
I also only use noise cancelling headsets.

VooDoo1 said:
I think its with all HTC phones. Happened with my Dash - Wing and now Tilt.
But I've never had anyone complain about hearing music on their end...I can just hear it on my headset for about 1 sec. I've also had my SMS tone play wile on a call and also my VM tone play while on a call and I've asked them if they heard that and they said no.
I also only use noise cancelling headsets.
Click to expand...
Click to collapse
I've never had a problem with any other handset, I've had a Qtek 9100, MDA, O2 Exec, Wing and a Dash.... crap I spent a lot on phones. The only one I've had problems with is the TyTNII.

Same problem here. And sometimes the speaker will very briefly go into speaker mode as I answer! Not good.

Vibration alert doesn't stop and audio breaks after a2dp.

Just as the title states... ie: I get an sms or email alert and the vibe just keeps on going until I goto volume silence then I can reactivate the volume.
I use ring and vibrate together for all alerts.
Anyone else have feed back with this or a similar problem?
*edit*
So I have done some testing and would like if someone else who uses a bluetooth headset to listen to music could try using BT a few times turning it off and on (when on use the htc media player) and see if after receiving a text message or email if your audio fires properly and your vibe stops. I have not used the BT all day today and the vibe/ring has performed perfectly. Basically after using BT a soft reset is in order.

What apps are you using?
Are you using any of the phone profile software such as SPB Phone Suite, Phone Weaver, Phone Alarm or the like? I had this issue occur when using Phone Suite and it was resolved when i de-installed the software.

I had same problem. I got mail and the vibration didn't stop. I don't use any profile manager. But I had same problem with Cruise with Wm6.1.

No profile managers at all. I have had this happen once before with an asus p527.
I have since done a hard reset on my diamond, we'll see how it goes. I did the reset because initially I've done alot of playing around testing apps and hacks to see what works best, I have re installed the apps I know work and have done. very little tweaking... Fingers crossed.

@thebiker
Do you use Bluetooth Audio for music or voice calls?
I think I have narrowed the problem down to this for myself.
I use my jabra 320 to listen to music on my way to work, after disconnecting the problems begin, vibrate doesn't want to stop and the ring doesn't want to work. A quick soft reset and everything appears to be good until I use my BT Headset again. Are you able to see a similar trend as I am? As I mentioned already I had this issue with my Asus so maybe there is a problem in general with Microsoft's BT Stack when using it with a2dp and in general derails audio on the system. My thinking is the audio is actually what is stopping on me so the Vib doesn't have the audio to tell it when to stop.
Thoughts on this matter anyone?

Bump... added some info to the first post and modified topic slightly, to more acurately describe my newer findings.
If someone using BT can try what is in the first post... thank you.

I have the Jabra BT620s headset and have the same problem. I can listen music and when a call comes in I can answer it and people hear me.
When I disconnect the headset i don't get any sound. Need to do a soft reset to get sound back on my phone. So no rings or sounds untill a soft reset is performed.
Stupid bluetooth... Anyone with a fix?

I can't find anyway other then soft reset. If you look at the volume after disconnecting a headset it sets the volume to 0.
I also have this issue on a tilt running winmo 6.1 and Microsoft BT Stack. So I believe it is a MS Operating/BT Stack issue.

What rom are u guys using? i'll try to have a look and experiment with the 1.37 rom

Shipped ROM: 1.34.831.1 WWE
Date: 5/25/08
WM6.1 CE OS 5.2.19588 (Build 19588.1.1.4)
Radio: 0.93.25.NS16
Protocol version: 52.24.25.08H

any news on this ?

I encounter this problem when receiving voice calls. No sound and neverending vibrate. Also, on several occasions the sound disappeared during the conversation. Only a soft reset could bring it back. The volume showed just good values, so it wasn't a spontanious mute.
I don't use a BT headset, never did. In fact BT isn't enabled at all. I did change the ringtype to ring and vibrate, perhaps thats the trigger. I changed back to default ringtone setting, lets see what happens.
I hope this will be solved quickly, it makes my Diamond a bit unusable as a phone...

rondol1 said:
I encounter this problem when receiving voice calls. No sound and neverending vibrate. Also, on several occasions the sound disappeared during the conversation. Only a soft reset could bring it back. The volume showed just good values, so it wasn't a spontanious mute.
I don't use a BT headset, never did. In fact BT isn't enabled at all. I did change the ringtype to ring and vibrate, perhaps thats the trigger. I changed back to default ringtone setting, lets see what happens.
I hope this will be solved quickly, it makes my Diamond a bit unusable as a phone...
Click to expand...
Click to collapse
Interesting results... I can so far state that so long as I reset after using BT Headset I don't experience this problem. There maybe more pointing to a bad audio driver in general that BT causes to crash immediately and potentially regular use like you have may also cause it to go loopy, might be a specific app and the way it interfaces with the audio api.

citats said:
Interesting results... I can so far state that so long as I reset after using BT Headset I don't experience this problem. There maybe more pointing to a bad audio driver in general that BT causes to crash immediately and potentially regular use like you have may also cause it to go loopy, might be a specific app and the way it interfaces with the audio api.
Click to expand...
Click to collapse
The only app I installed afterward is TomTom Nav6. But I remember the problem happend before installing this app as well. I made several hard resets but no change. Perhaps I try once more, don't change any setting and keep it clean for some days.

The same problem here with ROM ITA.

rondol1 said:
The only app I installed afterward is TomTom Nav6. But I remember the problem happend before installing this app as well. I made several hard resets but no change. Perhaps I try once more, don't change any setting and keep it clean for some days.
Click to expand...
Click to collapse
let us now what the result is..... maybe it is tomtom ?

xivius said:
let us now what the result is..... maybe it is tomtom ?
Click to expand...
Click to collapse
Nop - got the problem before installing any additional software.
I confirm that I also have the problem after using my BT stereo headset.
SR solves the problem ... until I use my BT headset again

UPDATE: UNRESOLVED on 1.37 stock rom, but i can hear people's voices on the line, but doesnt wake up on sms and no alert, and no call ring tone after using A2DP for 5 mins and switching off Bluetooth, using HTC Player in Touch FLo 3D

Baronic said:
UPDATE: UNRESOLVED on 1.37 stock rom, but i can hear people's voices on the line, but doesnt wake up on sms and no alert, and no call ring tone after using A2DP for 5 mins and switching off Bluetooth, using HTC Player in Touch FLo 3D
Click to expand...
Click to collapse
So you have no ringtone anymore ? And after a soft reset ?

no ringtone no sms tone, soft reset, press volume key, resolves it.

No incoming or outgoing audio. Anyone ? Anyone ?

Hello. I've been relentlessly searching everywhere for a solution to my plight.
My Diamond touch works fine for the first few incoming and outgoing calls but then all of a sudden there is no incoming or outgoing audio when I make or receive a call. I.E. the call connects but I can't hear the caller and they can't hear me. The phone still rings and caller display still works. Likewise I can still place a call in the normal way. Just no audio in either direction. Soft reset sometimes restores normal operation but sometimes a hard reset is required.
The phone was originally on UK Orange network but is now unlocked and running on UK O2.
I got to grips with flashing quickly enough and I have now tried upteen combinations of roms and radios but nothing seems to help.
Has anyone else had this problem ? Or better still managed to cure it ?
Any help or suggestions would be so so so appreciated.
Oh yeah just in case it's relevent.. The phone seems to work perfectly in every other way. wifi, bluetooth, 3G, gps etc. Battery life is a wee bit pants but I'm not too concerned about that.
Thanks in advance guys !

brianbelfast said:
Hello. I've been relentlessly searching everywhere for a solution to my plight.
My Diamond touch works fine for the first few incoming and outgoing calls but then all of a sudden there is no incoming or outgoing audio when I make or receive a call. I.E. the call connects but I can't hear the caller and they can't hear me. The phone still rings and caller display still works. Likewise I can still place a call in the normal way. Just no audio in either direction. Soft reset sometimes restores normal operation but sometimes a hard reset is required.
The phone was originally on UK Orange network but is now unlocked and running on UK O2.
I got to grips with flashing quickly enough and I have now tried upteen combinations of roms and radios but nothing seems to help.
Has anyone else had this problem ? Or better still managed to cure it ?
Any help or suggestions would be so so so appreciated.
Oh yeah just in case it's relevent.. The phone seems to work perfectly in every other way. wifi, bluetooth, 3G, gps etc. Battery life is a wee bit pants but I'm not too concerned about that.
Thanks in advance guys !
Click to expand...
Click to collapse
M8. I don't think you're on your own on this one. I have the same problem ...or similar. My phone pairs OK but drops the blue tooth connection usually on audio but quite often altogether. Re-pairing is a pain in the A$$. It's definitely a phone issue as I have the older qtek and a nokia that work with my kenwood system without a hitch but pair up the diamond and I'm pulling my hair out after 5 minutes.
I've tried the latest stable radio, setting pin code to 0000 & also turning off security but it still drops connection after an outgoing or incoming call.
Does anyone have a fix for this?

...and jetware 1.3 doesn't solve this either. Installed it the other day and pretty much the same ...audio is fine until a call is terminated and then it drops A2DP but sometimes stays connected on telephone. Other times both drop off!

bt stack
In my case it looks like the BT stack on the diamond is not compatible with the Kenwood DNX8220BT stack. I see quotes that HTC implemented their own stack for the Diamond so could someone put me out of my misery and tell me if it's possible to change the stack to something like that on the wizard as that works flawlessly with my Kenwood satnav?
ADD+

My phone does that weird thing too where I couldnt hear the other person on line. I have manage to found a quick fix for it tho.
Solution 1: During the call (when you notice you cant hear the other person), press the middle circle button (which will activate the screen if dimmed out), then press the speaker icon. This allows you to continue the conversation on speaker with the other person on line without having to soft/hard reset.
Solution 2 (works sometimes): During the call, reduce the volumn, wait a secnd or two, then raise it again.

Bt3030 - Shb6100/7100
Have the same problem with Philips shb7100 and shb6100. i also have tried the Jabra BT3030.
I used and test them on a Tyten and wizard no problem at all.

I had same problem before...found out is hardware problem...sent to htc care and after tat everything ok.

ADD+ said:
In my case it looks like the BT stack on the diamond is not compatible with the Kenwood DNX8220BT stack. I see quotes that HTC implemented their own stack for the Diamond so could someone put me out of my misery and tell me if it's possible to change the stack to something like that on the wizard as that works flawlessly with my Kenwood satnav?
ADD+
Click to expand...
Click to collapse
I have the exact same model (kenwood dnx8220bt and XDA ignito (diamond), same problem where everything is okay but when you go into the contacts menu and try to make a call, BT connection either drops or nothing happens when you try to make the call.... this is a joke.... how can my old HTC P3300 work with it without a problem and this newer Diamond flop like a fish...
any updates or news??

I've the same problem. No Sound after some call or others sounds play. When this happens and if I receive a call the others not listen my voice. This means that when audio disappear, speaker and also microphone not work, like the system can't comunicate with them. The volume control not resolve my problem. I've done HR and with nothing installed in my phone the problem come back again after few minutes. So it's not a problem of third part bad software, but htc orginal software or hardware problem.
Anyone solve it o have idea?
Thanks!

I join the list - having problems with my xcarlink which used to work with my P3300
Tried using A2DP Toggle which helped on the artemis but seems to have NO effect at all on Diamond
The Diamond does connect flawlessly to my jabra earpiece and my Sony ericsson bluetooth speaker

ninja_pimp said:
I had same problem before...found out is hardware problem...sent to htc care and after tat everything ok.
Click to expand...
Click to collapse
I have the same problem. Sent my HTC back twice for repair but still no solution. The first time they didn't found the problem, the second time they replaced the speaker.
What did they do with your phone to fix it?

According to this thread http://forum.xda-developers.com/showthread.php?t=431826 it is a hardware issue. The phone needs to go back to the supplier as it is faulty.

X1 wired headset receive calls problem

Hi!
I have one black X1i SW ver R3AA010, GENERIC_UK rom.
Great phone, but i have problem with the wired factory headset.
If i have call, phone playing ringtone, and i want receive this call, but no effect. Another problem is mic is on the phone enabled, not on the headset - in ear-phone mode.
On another forums reported same problem.
I see now only one solution:
1.,Unplug Headset from phone
2.,Incoming call, after hearing rintone - plug in the headset
3.,Problem is fixed..., but only to next soft reset or next unplug
Is there any registry mod or cab fix to this?
example : manual headset mode on/off
pls help me, thank you

As you mention, the problem has been scarcely discussed in other threads (and forums), but no one's seemed to find a solution. I'm not even aware if the headset problem is a general flaw in X1, or we're just a few unfortunates.
I won my X1 in a competition so I don't think I'm really in a position to be pissed off, but this defect is indeed a MAJOR drawback, and it surprises me it hasn't been criticised more loudly in e.g. reviews and forums.
The problem smells to me like a firmware issue (though I really don't have a clue), i.e. something that our friends at Sony Ericsson (are you out there, guys?) should be able to fix in an update, but they don't.. :-(
Anyway, my workaround is to make sure the headset is 'armed' in advance whenever I want to be prepared for an incoming or outgoing call. E.g. before I hop on my bicycle, I 'simply' make a short call to whatever number, e.g. to my voicemail, and as soon as there's a connection I plug in my headset and hang up. Now the headset works - I test it by pressing the headset button twice, which should initiate redialling the last number used.
In any case, it shouldn't be necessary to make such arrangements! My previous mobile was a crap, crap Nokia - but I miss it because its headset worked like a charm.
In fact, just out of curiosity - if anyone reading this has an X1 without any headset problems (i.e. mic and button not being responsive), please speak up. Maybe we can then isolate the problem.