Related
Hello all,
I'm considering moving up to the XDA Exec; especially now that I see many contributors here have worked out how to get it running well.
However I suspect that, with its bigger size, using a bluetooth headset will be even more important. My experiences with my XDAII were that it was never quite reliable enough to use day-to-day (even after trying different bluetooth stacks etc.)
So what are your experiences:
- does it work well
- how about the voice dialling via bluetooth
- caller id on compatibale headsets work?
cheers,
Pete
I'd say it depends on your headset, but yes: The Exec handles my Bluetooth headset more reliably than my XDA2 did.
I've got a SonyEricsson HBH-65 that was occasionally great and occasionally infuriating with my XDA2, but it seems much happier with the Exec. It's not perfect since it's tough to interpret the various bleeps and boops that the headset gives out and understand what they mean, but I'm getting used to it. It'd be a lot easier if the headset makers could give us more than one button... :roll:
With my HBH-65 and my Exec I can receive calls and use voice dialling to make calls (provided I've configured the voice dial commands already). The voicedial bleeps are a bit quiet in the headset but trial and error might improve things.
Some people seem to have problems using voicedial if their Exec is closed and turned off, but I don't seem to have the same problem. The first press of the headset button switches the Exec on and then a second one gives me the voice prompt.
Hope this helps
I've tried a Bluespoon AX and a Plantronics Discovery 640 with my headset and while they both appear to work fine functionaly, the quality of the audio is bad. I've tested the same bluetooth devices with other phones and the quality is much better.
Does anyone else have this problem? I'm going to go into to O2 later today and see if they've had reports of this before. Maybe I have a dud device.
I have an Exec, a Jasjar *and* an MDA Pro the Exec is mine, the rest is Eval.) and the Exec and MDA pro handle BT Headset fine. The Jasjar however keeps dropping the connection between the device and the headset. Flashing the MDA Pro with the Jasjar ROM made that the Pro also started dropping the connection between device and headset.
Conclusion, something is flaky in the Jasjar Rom.
There are a number of posts relating to this dropping of connection in this forum.
G'day
I have had the Jabra BT800 for a few months and never used it as it was pointless with the XDA IIs, but it works perfectly with the JasJar. It even rings about half a second before the phone does and shows the callers number (pitty it doesnt show the name from the phones contacts).
I am happy i didnt sell the BT800, as now i can keep the JasJar closed in my pocket when i just need to answer the phone.
Paul
ive used a jabra bt250v no problems voice dial is much better and works fine but i havent found how to get the audiogaeway working any ideas anyone so i can get tomtom throught the headset
JJ and Jabra BT 800 work well and voice dial works very well. Have made 1.5 hours in the last two weeks and not dropped calls. When used inside a car or in a room the signal is okay but as soon as you use the Jabra BT800 and JJ outside the signal gets weaker.
I use my MDA Vario in connection with a Siemens HKW-600 Bluetooth Carkit w/ display.
Everything just works fine, audio is of good quality except for network provider and battery status not being displayed in the carkit's display.
With my previous phone (SE T-630) and my wife's Motorola V3 this does work (displaying T-Mobile and correct battery status) so the problem must be within the MDA Vario.
Trying to solve this I installed JETware software (as recommended elsewhere on this forum). Network provider and battery status were displayed but some settings (such as "use phone ring tones") just can not be disabled. This is very annoying as this caused limitation / cancellation of functionality I do have without this JETware.
Now, as everything else works fine, I only need a solution which enables that network operator and battery status are displayed in my Siemens HKW-600 carkit.
Are there any registry tweaks, utilities or other ways (other than JETWare) to manage this?
Me too!
I have the same problem (T-Mobil MDA III + Siemens HKW-600 Bluetooth Carkit w/ display) and I share your pain! My wife's Moto V360 displays perfectly. In addition, I find that an incoming call causes the Siemens ringer to ring at max volume sometimes so I'm terrified that a call might come in :shock:
Actually, I was just about to write my question when I found yours.
I experienced same with loud ring tones. But a solution is not that hard:
The volume of an incoming call could be lowered by decreasing the volume of the carkit: use the button on the right side of the display.
To compensate for volume while calling: raise the volume on the phone itself.
Hope this is of help for you.
I solved this issue by installing this: http://www.jetwaremobile.com/index.htm. My Qtek now displays the provider, signal strength and is using my ring tone - all that was missing first when paired with my Audi OEM handsfree.
DirkM said:
I solved this issue by installing this: http://www.jetwaremobile.com/index.htm(...)and is using my ring tone (...)
Click to expand...
Click to collapse
As you might have read, I have installed Jetware and experienced some problems with this, especially the use of the phone ring tone which can not be turned off. I appreciate your reply, but you just recommend what I want to avoid :wink:
Hi everybody,
I completed some tests using my bluetooth car kit (Audi integrated BT MMI car kit). Here is what I saw :
With the original french ROM (1.18.256.2)
Outgoing calls
90% of the calls were interrupted during dialing or connection. The main problem was UMTS stability with the french mobile operator named SFR. After deactivating UMTS/3G and falling back to GSM, 80% of the calls were interrupted during the first minute of communication because of BT unstability.
Incoming calls
Impossible to take a call : half were immediatly interrupted, half were answered using the internal micro instead of the BT one.
With the JasJam ROM (1.20.305.3)
Outgoing calls
After deactivating UMTS/3G support all the calls are stable. Every thing is working fine and the Audi BT car kit works just fine !
Incoming calls
Still impossible to take a call : quite all are not well handled. BT is still unusable to take calls.
I don't think the BT car kit is the problem, because I am using it every day with a Qtek 8310 (Tornado) and both incoming and outgoing calls are well handled.
If you've got some experience, please share it. I am so disapointed that this marvelous TyTN cannot replace my Tornado, only because this "merdique" (<------ french romantic word ) bluetooth functionnality is not working ! :evil:
Arnaud.
Hi Arnaud,
I too have problems - see:
http://forum.xda-developers.com/viewtopic.php?t=61594
Paul
Im also having problems with carkit.
Jasjam and kjam just dont connect with my carkit (while they pair with it) but Jasjam and all nokia / samsung phones work perfectly well with it. Even Palm treo 650 works.
Is this a problem with iMate sets or with Windows Mobile 5.0?
I've had a friend who also has a TyTN which we tried in my kit and it didn't work. It seems that users with other variants (e.g. Orange) don't have this issue?
Further (non-technical) tests have shown that if you answer or make a call, you can get the audio by going into the call menu and choosing "Turn handsfree off". My uneducated guess here is that there is some issue with the headset feature on the TyTN and by doing this, it resets the headset profile and bingo!
It is a pain in the ar$e doing this for inbound calls, but for outbound it is manageable - you simply dial the number and whilst it is connecting, do the menu->Turn handsfree off workaround. Hopefully the new ROM will fix it - when it arrives!!
Hi All,
Just to put in my experience.
I have an Audi A4 with a Gen II car kit. As there is no handset holder for the TyTn I am using the Bluetooth function.
I have the Orange SPV M3100 variant, which works absolutley fine with the Audi Bluetooth, with one problem....
As I don't yet have a car charger, when the phone goes into sleep mode, it appears to disable bluetooh (I occasionally get a 'BT OFF' signal on the car display). Switching off bluetooth, then switching on again on the phone tends to kick it back into life where it stays live for another ten minutes or so until the phone dozes off again..
I have heard of a few people who have also diagnosed the problem as possbily the phone going to sleep to conserve battery, and solved the problem with an in car charger. I will report back when I have a charger.
Again, I do not suspect the Audi car kit as I have previoulsy used this (on Bluetooth) with a Nokia 6230 and MDA Vario, with no problems at all (the Vario was externally powered from the car).
Maybe you TyTn owners can flash to the Orange ROM ;-)
Same Scenario Different Cast
I have a Lexus GS with BT.... here's my Undesired results
actually, the only Problem i am having is very annoying.
If i receive or make a call after i pair with the Car kit, EVERY Thing is fine,
The sound quality is good, the response time is good (no Delay).
BUT after that call is ended, the BT itself on the jasjam TURNS off...
so i have to turn the BT on After EVERY Single Call (either made or received)
Is this Normal, I don't think so, but i had to ask
I have the Original Ship ROM Arabic version
My BMW handsfree works just fine with my TyTN. No issues other than an occasional BT off (loss of pairing). Interestingly, it's not sleep mode related since it usually works just fine in that mode. Generally, disabling Bt then re-enabling it re-establishes the connection then all is well. I have no issues making or receiving calls.
No doubt CarKit issues will be addressed when HTC releases their ROM update. Recent information tells me that this update is pretty much guaranteed to be an AKU3.0 variant. There's a tremendous amount of BT stack improvements in this AKU that should improve this as well as A2DP bluetooth issues.
.. No issues other than an occasional BT off (loss of pairing). ..
Interesting! I have the same issue with MTeoR.. I wonder if MteoR and TyTn are based on the same HTC device PLATFORM.
Updated my Parrot CK3100 to the newest version and things still don't work too well. When I start a call on the Parrot it takes around 20 seconds to start dialing on the phone, and when I receive a call I have to pick it up, place it on hold, and retrieve from hold to be able to hear the other side.
I wonder what/why they changed in the Bluetooth stack, it worked perfectly on my Wizard...
Renault Laguna II integrated BT kit
Works OK with my Laguna system except for the signal strength indicator. It appears that this information is not sent or translated onto the screen in the car.... Calls are fine though, and I noticed that the car rings immediately, the moment the phone does. Could be because the TyTN has the "turbo lag" explained in another thread tho
Cheers
rmorby said:
Works OK with my Laguna system except for the signal strength indicator. It appears that this information is not sent or translated onto the screen in the car.... Calls are fine though, and I noticed that the car rings immediately, the moment the phone does. Could be because the TyTN has the "turbo lag" explained in another thread tho
Cheers
Click to expand...
Click to collapse
Try installing Jetware mobile extender, that adds signal and battery bars as well as network name.
I enabled Remote SIM Acces in the Bluetooth Menu and now my contacts sync on my Audi Bluetooth Car kit with WM 6.1.
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...
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.