A month or so ago I started to have problems with my call waiting, with BT Headset set up. I was using the T-Mobile 1.60.36 ROM, with the most current BT Tool (one with the clock and two batteries) on my MDA II when the first issue started.
While on a call another call came in and the notification occurred just like always, but the BT Headset did not recognize the new incoming call. If I choose ignore incoming call I would lose the current call on the headset, but the call was shown on the device as still active. If I choose answer new incoming call both calls could not hear me on the BT headset, but both displayed on the device active.
I switched to 1.72 UK Beta, but the problem persists. Never had this issue before and do not know why all of a sudden this is an issue. I would have thought a complete ROM switch/hard reset, etc. would have fixed this problem.
Anyone else have this issue or problem with inability to get call waiting?
Related
I use the Plantronics M3000 Blue Tooth ear piece.
Recently I have been missing 1/3 calls because the Blue Tooth won't pick them up and if I try to answer them on the XDA it comes up with "Unable to answer the call".
I don't know if this problem is related to the BT device but I certainly didn't encounter it before I started using it.
Any ideas on what's causing the problems and how to resolve it?
Thank you.
Fully charged
First we have to do some error tracking
Is the BT headset fully charged,
Secondly when missing the call was headset bonded
Was Bluetooth enabled on XDA and BT haedset enabled
Then we can go to some more serious problem checking
Fully charged
Very good points. I think fully charged may be an issue, but not always.
I am confident with bonding and connectivity.
Points aside, can't I override the BT connection and just collect the call by pressing <Send> on the XDAII?
yes
Yes you can also accept the calls with the handset green button, and then still press the accept button on your bt headset to transfer to that afterwoods, and vica versa
So back to my original problem
On one out of three occasions I am physically unable to answer my phone with the green <send> button, it displays the message:
"Unable to answer call".
Does anyone know why this message appears? Is there a conflict with my BT earpiece or could there be another issue all together?
Thank you.
What BT headset are you using. I have both the Jabra BT200 & 250 and have had issues with both picking up call from the headset.
I use the same set up Plantronics M3000 and XDA II, I also get this issue.
However, If I don't get to the phone in time (when I don't have the BT headset on) I still get the issue, My guess is that I am trying to accept the call but the caller has ended........
unable to answer incomming calls !!
hi - on my xda 2 i get the same problem and i am not using blue tooth at all - the xda 2 occasionally wil not pick up the incoming call. having read other posts on this site i am under the impression that the phone aspect of the xda 2 is prone to glitches and is a weak point........... further information around this point is sought :?
Re: unable to answer incomming calls !!
ohmlogic said:
hi - on my xda 2 i get the same problem and i am not using blue tooth at all - the xda 2 occasionally wil not pick up the incoming call. having read other posts on this site i am under the impression that the phone aspect of the xda 2 is prone to glitches and is a weak point........... further information around this point is sought :?
Click to expand...
Click to collapse
Me too! Even without BT headset!
XDA2 phone is very poor
Me too, XDA2 phone is rubbish
:?
Very happy with my XDA II and works well with my SE HBH-60 BT headset.
I have had the "unable to answer call" message too. Without a BT headset. I was under the impression I got this message when the call had just switched through to voicemail but the XDAII hadn't noticed yet.
Jamie
jwhitham said:
I have had the "unable to answer call" message too. Without a BT headset. I was under the impression I got this message when the call had just switched through to voicemail but the XDAII hadn't noticed yet.
Jamie
Click to expand...
Click to collapse
Originally, my opinion was that someone is calling my non-voice number. I have three mobile numbers : for voice, fax and data. I have the fax-number redirected to my mobile box (it's integrated messaging system where voice messages are delivered by mail as WAV files and faxes as PNG files). But the data-number isn't redirected. On my previous GSM phone, when someone called my data number, the message "data call - connect terminal by cable/IrDA" was displayed. So on XDA I thaught that "unable to answer call" message is displayed when someone dialed my data-number. But it wasn't true - he dialed my regular voice number, so it is a real serious bug !
Just to add to the record, I too have the problem of being unable to answer calls sometimes. This does not happen all the time though, every now and then but enough to be irritating. It's possible though I can't say for sure that pressing the 'answer' soft button rather than the green hardware button is more reliable as I've not had that problem with the 'answer' soft button.
maybe some of those issues are a result of some of the more exotic gsm stuff like
I have three mobile numbers
Click to expand...
Click to collapse
and prepay'd sim and .......
diamondjimxda2, I think your problem could be caused by something else.
I am - like you - with Vodafone - and I also use a BT headset (Jabra 200). Every few times I have the problem that I cannot answer incoming calls - bother with and w/o the headset.
For me it doesn't occur directly after a soft reset, but after a few hours of use. So far my best guess is a relation to some software and I currently suspect Pocket Informant being the source... at lest I noticed a few times that answering a call worked before I opened PI and didn't anymore when it is running.
Not that I now think PI is the problem, but something doesn't quite work together as it should...
By the way: my device information is
ROM version 1.03.00 USA
Radio Version 1.05.14
Ext ROM Version 1.03.43
Hi All: I have paired the headset fine with my phone and made calls before but I can not switch a call from the handset to the headset while a call is already in progress. Once I end the call, I can pair the headset fine to make a NEW call but I'm having problems switching the call when it is already in progress. I can go to the phone and manually switch it to hands free but I thought that if I powered on the headset while a call was already in progress, that would route the conversation from the handset to the headset. Is that correct or can it not do this without some tweaking? Thanks.
I have the same setup and I can answer the call on the phone, then "open" the H700 and the phone re-directs the call thru the headset within about 2 seconds from opening the headset.
If I'm on the headset, I can press and hold the call button on the H700 and the call goes on hold. I can "close" the headset and then un-hold the phone using the touch screen and resume the call on the 8525.
Now I believe that the standard bluetooth stack is crap, and I have had many instances where the phone just stops linking the Bluetooth. I can usually restore the link just by using the comm manager to turn off the bluetooth radio, then turning it back On. I have even done this during a call and it worked.
I have always had solid, loud audio with the H700, BUT, several callers have mentioned that my voice was often clipping a word every few seconds. I don't know what that's all about.
Do you know whether you need to select any special settings or do anything special in the pairing setup with the phone or headset? I do not know how to have the conversation directed to the headset after turning it on when I am already on the call. It works fine to start a new call or to answer a call directly through the headset but can't join a call in progress. Would appreciate anyone's help. Thanks.
I have now tried 3 different bluetooth headsets with my AT&T Tilt with Stock Rom. First was my BlueAnt V12 I used great with my RAZR then I bought a Motorola S705 now I have Sony HBH-DS980.
With the BlueAnt V12 the audio was low and tinny and couldn't hear the caller
The Motorola S705 sounded good minor choppiness but the callers couldn't hear me worth a damn. Both of these devices paired great and kept connection, only the Motorola would loose connection if I got a system alarm or if I was streaming music. For just handset operation it worked great. With the Sony it seems to be a crap shoot when they are going to work. I installed JetWare to enable Caller ID Name and Ringtone through headset and when I pair them the first time they work great all day long. However if I turn bluetooth off on the phone and then back on I have issues with disconnecting and sound not going through headset for calls.
So I installed the new Official AT&T Rom from HTC's Site the other day hoping the bluetooth improvements they made would help. I decided to try JetWare again just to see if it worked, again I started having problems again. So I hard reset and didn't install the JetWare Extensions. For the first day everything worked great. Next day I fired it up it's up to it's old tricks of disconnecting after a call.
Anyone else having these issues? My state is going to be bluetooth only while driving in about 4 months so I really need bluetooth to work.
Can you charge the sony ds980 via usb?
No it has a real strange plug for charging
Hi, I have the Sony Ds980. I've experienced similar problems in the past.
check your Bluetooth settings on the phone: communication manager --> Settings --> bluetooth. Select your device (ds-980) but don't double click on it. and then check its mode: in that window, ensure that you have checkmarks in both options (i.e, Turn on bluetooth & make sure this device is visible to other devices). Sometimes, when you restart your bluetooth headset, the second option is left unchecked, thus causing disconnections between it and the device.
another option is to trigger the headset button. sometimes, when a call comes in, I would have to do this once or twice before it connects.
I think it is a bug.
i have the Jetware extension and MSVoice, and they help with the caller ID.
HTH,
rgds, Manny
I'm trying to decided between the DS980 and the Moto S9.
I'm so tired of wasting my money on crap.
Thanks I'll have a look at those settings, I just wish JetWare uninstalled nicely
I have been running it lately without JetWare and the only issue I am having this way is the wireless stereo portion disconnects after each Incoming call it does not do this if I place a call.
With JetWare I can sometimes keep it connected no matter what the issue is it connects but when I place a test call it rings on the headset but when I answer the call it isn't comming in on the headset it is still on the phone although the call button works and ringing on the headset works. It got to be a pain to have to place a few test calls to make sure the headset was working.
dalavar said:
Thanks I'll have a look at those settings, I just wish JetWare uninstalled nicely
I have been running it lately without JetWare and the only issue I am having this way is the wireless stereo portion disconnects after each Incoming call it does not do this if I place a call.
With JetWare I can sometimes keep it connected no matter what the issue is it connects but when I place a test call it rings on the headset but when I answer the call it isn't comming in on the headset it is still on the phone although the call button works and ringing on the headset works. It got to be a pain to have to place a few test calls to make sure the headset was working.
Click to expand...
Click to collapse
Well, that does it for me. The DS980 is officially off my list.
Hi, guys. I have a problem with my xperia and hands-free bluetooth funcionality (I have tested with several hands-free). In half of a call, I start to hear the voice through the phone, and not through the hands-free, but the bluetooh is turned on, and I'm able to manage the phone through the hands-free (I can see the contacts, start and finish a conversation, etc). Simply the sound is in the phone, not in the hands-free.
I have too the same problem that everybody has (the bluetooh turns off), and I had fix it with BTKeepAlive.CAB, published in this forum (Thanks to the creator)
¿Anyone can help me?
I'm having a similar problem, but with my in-ear bluetooth hands-free.
When making a call, either from the phone or by redialing with the hands-free, the sound ends up in the phone. When answering an incoming call, either with the phone or with the handsfree, sound ends up in phone.
I've tried three different handsfrees (two SonyEricsson and one Invisio), with same result.
The strange thing is, when having an ongoing call, with the sound in the phone as stated above, I can hear a low noice in the handsfree, indicating that it is active. When pressing menu, the only option, regarding handsfree, is "Turn handsfree off".
Is there anyone that has a solution to this?
BUMP
Anyone?
thorell said:
I'm having a similar problem, but with my in-ear bluetooth hands-free.
When making a call, either from the phone or by redialing with the hands-free, the sound ends up in the phone. When answering an incoming call, either with the phone or with the handsfree, sound ends up in phone.
I've tried three different handsfrees (two SonyEricsson and one Invisio), with same result.
The strange thing is, when having an ongoing call, with the sound in the phone as stated above, I can hear a low noice in the handsfree, indicating that it is active. When pressing menu, the only option, regarding handsfree, is "Turn handsfree off".
Is there anyone that has a solution to this?
Click to expand...
Click to collapse
I believe I can aswer this myself after following an instruction in another thread here on XDA, even if the solution sounds a bit strange:
I've made a hardreset, and re-installed every program that I want, everything with Bluetooth turned OFF. After that, I turned BT on and added my handsfree. Now its working super.
I've just encountered a strange and frustrating issue that began a couple of days ago on 7/12. I have a Galaxy S4 running 4.4.2 and a 2010 Nissan Altima. I've had my car for 4 years and have never had this issue with any of my phones until this past Saturday so I am convinced it is my phone that is the issue. The Bluetooth pairing will connect without issues (indicator on both phone and car screen indicates so) and I am able to make/receive a call with sound successfully for one time. If I a make or receive a second call, there will be no sound both on my end or the caller on the other end. I know the call connects since the call timer starts on both my phone and the car screen as well as on the caller's phone (tested out with my wife's phone while in the car). I will not even hear a ring tone, the call will just connect without sound. Even if I disconnect the Bluetooth connection, there will not be any sound coming from my handset and the caller on the other end cannot hear me when trying to perform a call. The issue can be temporarily fixed with a phone restart. After making one successful call on Bluetooth after a phone restart, the no sound issue will return. I'm not sure what to do at this point. I've re-done the phone pairing with my phone and car but the issue resurfaces. I see somebody posted a very similar issue on a different website on the same exact day I started getting the issue (Can only hear phone calls on Bluetooth) so I am wondering if we got some sort of app update that has started to interfere with Bluetooth connections. Any advice would be appreciated. Thanks.