Related
Sorry if this is a question that has popped up before but I have searched the previous queries in BT headsets and found quite a few different problems but I don’t seem to have found anything directly relating to this so here goes
I recently purchased the Bluetake bt400 GII headset, and it works fine, it bonds ok and the reception is perfect
My only problem is that I can’t seem to get the headset to ring when a call comes through to my XDA II!
I has only done it twice and that was completely spontaneous, I have since tried many test call and the headset will not ring, however after the ringing has stopped and I get the missed call icon, if I press the Power/Talk/pairing button the headset rings once! :shock:
I have looked in the user manual and on the website itself but all I seem to get is either "the device and headset will ring simultaneously" or "sorry this device may not be supported"
Arg :!:
Any suggestions :?:
Thanks
Binks
Both my colleague and I use XDA2s and we work in the same office. Today, both of us have had incoming calls, while the unit is in its cradle. I took mine out of the cradle, checked who was calling and hit the green button. The call was answered (according to the display) but I could hear nothing. My colleague had exactly the same happen to him, from a different caller. Has anyone else had this, or is there a technique to answering a call when the XDA is in its cradle?
Hello,
I have had no problem answering calls from within the cradle -
I did exactly as you said - picked up the device from the cradle, but I pressed the "answer" button on the screen, all works fine for me.
Cheers
I have answered lots of times the same way with no problems, I've even put the unit on speakerphone... Very handy when cradled...
Did you use a headset before?
The following happend for me once:
I use the headset for listening music. Phone is ringing. I unplug the headset, because I have a poor quality Hama one, and in a loudy bus, the internal speaker of the PDA is better.
But I hear nothing. The only way to take a phone call, with the headset.
I think the PDA's headset connector switch was wrong. After I plug and unplug the headset many times, my wallaby worked. (The PDA felt the headset plugged, so switch off the speaker but the headset wasn't pluged. Soft reset did not help)
This is my story
Rayan said:
I have answered lots of times the same way with no problems, I've even put the unit on speakerphone... Very handy when cradled...
Click to expand...
Click to collapse
Same thing with me, I answer lots of calls using the speakerphone while imate is on cridle... I have no problems at all.
GoldenSands said:
Same thing with me, I answer lots of calls using the speakerphone while imate is on cridle... I have no problems at all.
Click to expand...
Click to collapse
There is a setting, to automatically switch on speakerphone when PDA in the cardle?
Thanks!
Thanks, everyone, for the feedback. Neither of us had used headphones, but we both have BT headsets, which we had used that morning - one's a Jabra BT200 and the other is a Bluetrek G2. I don't know whether that is relevant or not.
If anyone out there uses a BT headset and can tell me how they select a number from contacts and ring it so that the headset works - I'd like to know! Mine only seems to work if initiate the call from the headset.
(off topic, sorry) is there any way of getting the phone to answer calls/dial calls in hands free mode? or creating a profile that does so (ie when i am in car and xda is in a (non handsfree) cradle.
Re: Thanks!
andyb said:
Thanks, everyone, for the feedback. Neither of us had used headphones, but we both have BT headsets, which we had used that morning - one's a Jabra BT200 and the other is a Bluetrek G2. I don't know whether that is relevant or not.
If anyone out there uses a BT headset and can tell me how they select a number from contacts and ring it so that the headset works - I'd like to know! Mine only seems to work if initiate the call from the headset.
Click to expand...
Click to collapse
have you tried turning off bluetooth headset from the today screen, that may cure your problem.
Sallala said:
There is a setting, to automatically switch on speakerphone when PDA in the cardle?
Click to expand...
Click to collapse
I do not know if this feature is availble. I did a little search on my imate but did not find such a feature! but will be nice to have it!
The only option available is to asnwer received calls after certain rings!
it would be worth cheching how old the rom version is on your xda2 as there is an issue with the very early versions of the rom (1.03.00) for example. In this version nither the cell line or the gprs cant be connected while the XDA2 is in its cradle. current version should be 1.60.00.
hope this helps
When I press the button on my bluetooth headset to answer incoming calls the ring stops for the caller and on the cingular 8125 (rom 2.25), but there's about a 2-3 second delay before the phone actually connects the call to the headset.
On the caller side they have 2-3 seconds of dead airtime. Because of the delay in connection the caller is normally saying hello - hello - hello (etc) y the time the call has connected to the headset.
I've tried 3 different bluetooth headsets (Moto 850, Plantronics 645 & 655, Jabra JX10) and they all experience the same problem.
I've verified it's not associated with the 3 second ring delay issue (posted on xda) - phone rings almost immediately.
Any thoughts, recommendations, hacks/tweaks will greatly be appreciated. This is becoming more of a problem, as I use my phone mostly for business.
Otherwise the phone has been outstanding.
I've been using a Jabra BT250v for over a year and have had the same thing with both my Treo 650 and the Cingular 8125. I finally got used to the slight delay - it's taught me to be a little more patient 8)
However, I'm also curious if there is a hack to cut down on that 2 second 'wait time' before the BT headset picks up the call...
When I press the button on the BT headset to answer incoming call the ringing stops on the caller end and on the cingular 8125 (rom 2.25), but there's a 2-3 second delay before the phone actually connects the call to the BT headset.
On the caller side they have 2-3 seconds of dead airtime, after the ring stops. Because of the connection delay, the caller is already saying hello - hello - hello (etc) thinking the call has been answered.
I've tried 3 different bluetooth headsets (Moto 850, Plantronics 645 & 655, Jabra JX10) and they all experience the same problem.
I've verified it's not associated with the 3 second ring delay issue (posted on XDA) - phone rings almost immediately.
Any thoughts, recommendations, hacks/tweaks will greatly be appreciated. This is becoming more of a problem, as I use my phone mostly for business.
Otherwise the phone has been outstanding.
BT headset delay
I have the same issue with T-mobile MDA and Jabra BT250V. Not only does the delay confuse callers, but they hear the ring tone and buzzing of the vibrator before they hear me... hello...hello...hello. It really sucks.
I have tried a Motorola headset (H350) the delay is shorter but the headset sound quality sucks. I was going to try the Jabra JX10 next and hope for the best.
I've also tried using the "BT on" feature of PocketZenPhone to avoid the delay. Not a satisfactory solution.
Does anyone have a solution for this? Is anyone answering calls on their BT headset and getting a quick connection? Is this just me?????
dratliff said:
When I press the button on the BT headset to answer incoming call the ringing stops on the caller end and on the cingular 8125 (rom 2.25), but there's a 2-3 second delay before the phone actually connects the call to the BT headset.
On the caller side they have 2-3 seconds of dead airtime, after the ring stops. Because of the connection delay, the caller is already saying hello - hello - hello (etc) thinking the call has been answered.
I've tried 3 different bluetooth headsets (Moto 850, Plantronics 645 & 655, Jabra JX10) and they all experience the same problem.
I've verified it's not associated with the 3 second ring delay issue (posted on XDA) - phone rings almost immediately.
Any thoughts, recommendations, hacks/tweaks will greatly be appreciated. This is becoming more of a problem, as I use my phone mostly for business.
Otherwise the phone has been outstanding.
Click to expand...
Click to collapse
i have the moto HT820 stereo bluetooth headset and experience nothing like that, even when running my bluetooth gps reciever... the call is answered as soon as i hit the button... only problem i have is the lagging and skipping music, but i dont listen to music so its not a problem
My H700 delays on both of my Qteks (Wizard and Prophet). It only delays if I close the boom. If I leave the headset with the boom open it picks up right away when I press the side button. With the boom closed when it rings, I find that if I open the boom I have to wait 2-3 seconds for the sound to transfer. If I open the boom and press the button, 2-3 seconds it will hang up on the caller because I guess opening the boom is picking it up already
However, my HT820 stereo headset doesn't have any of those problems. Quick and easy, picks up right away; however there's no boom. My Bluespoon AX5 doesn't delay either.
pdxadmin said:
I have the same issue with T-mobile MDA and Jabra BT250V. Not only does the delay confuse callers, but they hear the ring tone and buzzing of the vibrator before they hear me... hello...hello...hello. It really sucks.
I have tried a Motorola headset (H350) the delay is shorter but the headset sound quality sucks. I was going to try the Jabra JX10 next and hope for the best.
I've also tried using the "BT on" feature of PocketZenPhone to avoid the delay. Not a satisfactory solution.
Does anyone have a solution for this? Is anyone answering calls on their BT headset and getting a quick connection? Is this just me?????
Click to expand...
Click to collapse
I had a bt250, and that delay is a known problem with the bt250,possibly making the problem worse
The headset pairs ok, it works but unreliable: Calls are recieved ok, calls outgoing from the phonepad ok but the problem is voice-dial.
Sometimes it works as it should: I activate voice dial by the button on the BT headset and the call is made, no problem.
Nine out of ten times however the voice dial does get its audio input through the PHONE mike and not through the headset mike, which usually ends up with getting the complete wrong person on the phone.
This btw happens to be my father - in law, who is called Rob. Somehow all unclear voice dials that I create because of this malfunctioning system are directed to him and it drives him and me crazy!
So I just deleted his voice tag to prevent possible family relations getting ruined.....
Ok, back to business: Is this just the OEM voicedialprogram by Cyberon and will I be better off with another voice speed dialling program or is it the Bluetooth manager in the Hermes that is crap?
This happens on two different BT headsets I own: A Jabra 250 and a brandnew Plantronics Discovery 655.
Any ideas and suggestions on this subject are very welcome before I swap my VarioII for another device.......
dido here
i am trying a motorola 300 series or something on my MDA. everytime i activate the voice command thing it listens to the device instead of my BT headset. i thought it might be due to using the BTaudio changer program that lets my headset play music from the wizard but sounds like i'm not alone here. anyone got any ideas?
So I'm not the only one........One of the great features of such a device is that you can actually make notes and work your agenda etc. while talking on the phone. Now if the voice commands do not go through the headset it is pretty useless.
I think it is a BT related issue. I don't think another program like Microsoft Voice Command is going to change that.
It might be a bug in the T-Mobile rom. I have not seen this issue from Tytn users yet..........
i have the HTC tytn with Imate rom but still same problem as u guys. The bluetooth voice dialing only works with the Handset after while instead of the bluetooth Headset . However it does go back to normal after Reset...So i hope one day this problem will be solve
I am on MDA VARIO II (Dutch) and am using a cheap Bluetrek which costs I think 30 USD (got is for free when getting the VARIO II).
Works perfect
So you can actually make voice dial tags through the headset? And you also hear the confirmation through the headset? You can easily test this by covering the MDA mike and speaking softly the voicetag in the headset.
Please give me your rom and radio info?
My ROM versions:
ROM: 1.21.114.3
Date: 06/20/06
Radio: 1.05.02.00
Protocol: 32.36.7010.04H
Th truth is though, I have only two voice tags: Home & Office.
Those two usually work just fine. I recorded them via the Vario and not via the headset.
To tell you the truth, when I used any of my WM 5 devices I never used to have many voicetags, just can't be bothered to record them all. I did use the Cyberon voice comander, which seems to work beter then the voice dial thing that is built into the ROM. Although for us dutch people, you have to learn how to pronounce the dutch names (like Nachtigaal for example) in an english manner , LOL
I think my Vario II is faulty. I have not seen this issue on any other forum yet. I will walk into a T-Mobile shop this week and see how the headsets performs on another Vario II. If it does work I'll swap mine for another one.
Keep you posted..........
Jeroen,
Can you post the serial number of your device and the approx. Date of purchase? I have an acuaintance who has an VARIO II and he seems to complain about the Alignment problems ! Strange I thought that T-Mobile's Vario II's were cured of this disease.
Thanx
P.S. Oh and also of course if you are suffering from the Alignment probs?
Ok, today I checked the BT handsfree profile functionality with another Vario II at the local T-Mobile shop and it worked fine. So my Vario II was declared faulty and I will recieve a new one as soon as T-Mobile NL gets the new batch in.
Churchill: I have a 634 Series and I bought it two weeks ago. I only experienced SA issues two times.
Thanx Jeroen,
I seem to have the SA issue sporadically, and it started after I tryed a taiwanese software for businesscard scan & ecognition. I need to find time to perform a hard reset
My Vario 2 does the exact same thing sometimes the voice dial actually works throught the handsfree mic, but most of the time it wants me to actually speak to the phone. I HAVE SEEN THIS PROBLEM MANY TIMES BEFORE, so I dont think its your headset, I know some people got around it by installing Microsoft Voice command, but for it to work properly with that I think it is necessary for the Bluetooth headset to have te serial profile. (dont quote me on that last bit!!) But like I said I think its a common issue.
Jeroen!
I started to become worried that i might have the same issue like you with the Voice tags. So today I have recorded a bunch of them (approx 15) then hid my phone inside my suit jacket and then put my coat on and then tryed to dial using my Bluetrek S21 (which I got for free with my Vario II) every single voice tag worked on the first try. I have recorded the voice tags using the phone itself without the headset.
So it must really be a faulty device, but hey you knew that already
Workaround!!
I was having similar problems with the voice sometimes coming from the Bluetooth Headset and sometimes coming from the phone speaker itself. After a bit of investigation, I have found out that if the voice tag was not recognized / successful, the next time the sound will come from the phone and will not be transferred to Bluetooth. If the voice tag is recognized successfully, the next time it will work properly.
I have found a workaround for the problem. If after pressing the Bluetooth call button, the voice comes from the phone, I quickly press the Bluetooth call button again, and the voice from Bluetooth mic is recognized properly.
I don't know about the other Headsets, but with my Headset (Sony Ericsson HBH-662), I hear a short beep each time the audio is switched to Bluetooth and back. So for me the sequence of operation is normally like this.
Normal Operation:
-Press Bluetooth Call button
-Short Beep (Audio transferred to Bluetooth)
-Beep from Voice Dial Software (Indication to start speaking)
-Speak the Voice Tag
-Repeat of Recognized Voice Tag from the Voice Dial Software
-Short Beep (Audio Transferred back to Phone)
-Phone Dialing Start
-Short Beep (Audio Transferred to Bluetooth. Similar to when manually dialing)
-Normal conversation
Error In Operation:
-Press Bluetooth Call button
-Short Beep (Audio transferred to Bluetooth)
-Short Beep (Audio transferred back to Phone)
-Beep from Voice Dial Software (from Phone speaker)
(At this time if you speak into the phone mic, the normal operation will start)
-Error Beep from Voice Dial Software (from Phone speaker)
-Next time the same error will be experienced.
Workaround:
-Press Bluetooth Call button
-Short Beep (Audio transferred to Bluetooth)
-Short Beep (Audio transferred back to Phone)
-Quickly press Bluetooth Call button again (no short beep will be heard)
-Beep from Voice Dial Software (from Phone speaker or from Bluetooth if you are quick enough)
-Speak the Voice Tag (Bluetooth Mic)
-Repeat of Recognized Voice Tag from the Voice Dial Software
-Short Beep (Audio Transferred back to Phone)
-Phone Dialing Start
-Short Beep (Audio Transferred to Bluetooth. Similar to when manually dialing)
-Normal conversation
After this the next time normal operation will be resumed.
I hope that this works for others also. Please give your comments.
Effan
Orange SPV M310 has same issues
BarnOwl said:
Ok, today I checked the BT handsfree profile functionality with another Vario II at the local T-Mobile shop and it worked fine. So my Vario II was declared faulty and I will recieve a new one as soon as T-Mobile NL gets the new batch in.
Churchill: I have a 634 Series and I bought it two weeks ago. I only experienced SA issues two times.
Click to expand...
Click to collapse
I have been driven nuts trying to find a solution to this exact problem. I have a UK Orange SPV M3100 and use a Motorola HS850 Bluetooth headset. I have never managed to initiate a call through the headset, it always requires me to speak the name into the phone itself... useless and dangerous when driving!
So your T-Mobile Vario II was faulty? Maybe there are a bad batch of Hermes devices. I will try taking mine into the Orange shop and see if I can get it to work on another unit... maybe I have a faulty phone too.
I will post back my results, just in case other have the same issues.
MW
You should check out the 'MS VoiceCommand 1.6 with Bluetooth and TyTN?' thread.
It's rather long and techy, and doesn't just apply to using MS VoiceCommand 1.6. but it basically does resolve the issue with the Tytn where voice input is not directed to the bluetooth device after pressing the call button.
It took me 3 attempts to get it working, following the instructions in the thread, but it does work very well now.
It is also documented on the wiki.
http://wiki.xda-developers.com/index.php?pagename=Hermes_Utils
Good luck.