Windows Mobile 5/Magneto & Jabra BT800 - MDA II, XDA II, 2060 Accessories

Has anyone got this working with full handsfree functionality? (caller id etc.).
Or other headsets that support caller id?
Thanks, JD

Anyone?
I'm trying the BT800 with WM5 and the 'caller id' function only shows the number on the headset, not the name. I've paired in handsfree mode, the names are in my contacts and I've tried different combinations of international format etc.
Pretty useless caller id unless it can display the name. Anyone had any success?
JD

On my 2.20 it only displays a "virgin" number. If it is already in the Contacts, or on the call list... IT DISPLAYS NOTHING!
If you get caller ID every time with 2005.. BE HAPPY!
BT800 sucks.
I am getting HBH662.

I'd be very interested in how you get on with the HBH662.
Sony Ericsson's site shows pictures of the caller id - but again only showing numbers, not names :shock:
I need to use my headset for business calls and caller id with NAME is crucial to me.
Jabra replied to my email to confirm this is a known issue. Which is a shame because apart from this the headset very close to perfect. Very reliable and clear and sits on my ear perfectly, doesn't hang off my ear like a lot of other similar design headsets.

xlive shows name ONLY WITH 2.20 translated for Himalaya. NOT 2005, nor on Imate PDA2 nor on MPX300.
BUT on 2.20, it times out and makes it not work after a few min.
I have not tried xlive on other devicers.

Related

True Mobility . . . the quest to get there

Hey guys. I'm posting my quest to true mobility and hoping some of you can comment or give some advice.
Even before I purchased the XDA II, I have wanted to become completely mobile with my wireless communicastions. I want to put a headset on and control everything with my voice. Though we're not quite there yet, here's what I am going for.
First accesory is the Jabra BT250 Headset. It works great with my XDA II. I have the Tmo rom. I have customized all my contacts with personal rings. I downloaded a program that reads text. Now whenever someone calls, Microsoft Mary via my XDA II, then via my headset says "You have an incoming call from ____." I wish there was a piece of software that could do this for me. All I want it to do is tell me someone is calling and read the person's name. MS Voice Command does a pretty decent job reading names, but there is not way to get it to announce calls. My method of producing a .wav for every contact works, but it's a pain to do, and you constantly have to make new files for new contacts. But most importantly though, this method makes it possible for me be know who is calling without touching my device. I dont' even have to touch it to answer as my headset has an answer button on it. This is the best I can come up with so far. If anyone has any sugguestions or can comment, please do so.
Next thing I want to do is to be able to dial calls via my headset. Jabra says in the manual the headset supports voice dialing on regular phones, but I don't think this complies with the XDA II. I spent a little time trying to get it to work, but I can't get MS Voice Command to hear me via the headset. Moreover, I would like to be able to listen to media playng on my device via the headset. I want to be able to create a connection or to make it think it has to be on because there is a "call" in order to let me use it like a regular, wired headset. Maybe there is software for this, I havn't found it though.
I also want my XDA II to read me my SMS messages when they come in. Pref. over my headset. I also want to to drive my car, give me my haircut, shovel the snow. Those are future projects though.

Imate PDA2 and Jabra BT800... almost right. Still buggy...

Just got my iMate PDA2 and paired it with my BT800. My long anticipated hopes of getting caller ID to work were almost answered until I encountered the following.
Anyone experience this?
Scenario:
(I live in the US, and use TMobile):
Call 1 comes in from 555-555-1212. The caller ID on the Jabra shows 1-555-555-1212. I do NOT answer the call.
Call 2 comes in from a PRIVATE caller (their caller id is blocked). The Jabra shows 1-555-555-1212 (the number of the previous call)!
Interesting thing is, if I did answer Call 1, all is fine with Call2, so I suspect the problem has something to do with Missed Calls. When you have a Missed Call followed by an incoming call that is PRIVATE, the Jabra doesn't know what to display, so it displays the previous incoming number.
The PDA2 itself works fine, it shows the proper caller ID... so... is this a problem with the Jabra BT800 or the PDA2???
Anyone?
-Kev

Free Voice dialing with HTC Vox (s710)?

I use Lubix Bluetooth UBHS-LC1 headphones
Is there a good freeware program or option that will allow me to voice dial from my blue tooth headphones? (my Vox is unlocked)
If not, what's the best way to go about it. thanks
been a couple of weeks and no one has replied to this... is there not anything that does this without costing $$$?
I use the voice speed dial that came with the phone (It was described on page 152 of my S710 user manual)
I just record a voice tag for a contact, then when I press the call button on my head set - the phone beeps and I say the voice tag and it dials the contact.
Why would I need another program to do this?

[PROB] Bluetooth issue on the fuze- can't hear incoming caller

I asked this in the Raphael Software area, but I'm posting it here as it really isn't a software that someone made..
OK, I'm pretty sure BT worked on the phone. Now, any time I answer from a BT device, the incoming caller is muted. He can hear me, I can't hear him.
If I transfer the caller to the phone (which btw I can hear him on the phone) and back again to the BT device, I can then hear him. If I answer the incoming call from the phone buttons, I can hear the caller on my BT device.
I must've spent like 30 calls to my phone (I'm ticked as I'm sure each one counted on my minutes) thinking of different ways to fix this.
I thought it was my BT headset, but it works on my Tilt. So I tried it in my car BT. It can't hear the caller either. So something is wrong.
Here's how I COULD fix it:
If I turn off MS Voice Command "announce incoming calls" my phone itself will play my ringtone while I hear a beep tone in my BT earpiece. If I answer it form my headset, it works!
UPDATE:
I had my unit bloat free by following the "How to skip the bloat! (Fuze)" thread. I did another HARDREST and did the same bloatfree. Right off the bat, I synced my BT and I can't hear the incoming caller. Something is messed up.
One other person has this issue so far. Can anybody else check it? Voice Command is one of the best things there is for this phone. Just make sure its checked to announce incoming calls. Don't worry if you don't hear the incoming call being announced(you might hear a bell sound behind your normal ringtone) as thats a different issue you'll get untill you patch it. Just answer the call from the headset and see if you can hear the incoming caller.
Same Deal
I'm having the same problem. I just unchecked the 'announce incoming calls' and we'll see how that works. I'm on a work conference call so I can't try it till later.
it should work with it unchecked, but that defeats one of the best features on the voice command. Another thing, if you have ring&vibrate set, it you uncheck that feature, the phone will ring and vibrate. so other people around you will know your phone is ringing. In a library, I liked to use the announce feature because my ear piece would ring but the phone would only vibrate.
Here is what worked for me today -and I have been on the verge of sending the phone back to ATT...
1. I deleted all my pairings
2. I paired my JawBone2 first
3. Then, I paired my Plantronics A2DP thing (I had paired this one first before because I had it with me when the phone arrived in the office).
Funny thing: First time I paired my Plantronics 855 I got 2 options under "Advanced" at the end of the pairing procedure: 1. "Stereo Headset" 2. "Handsfree" I checked both. When I re-paired (after pairing with the JB2) I only got the "Stereo" option (which I checked). So now, all works fine. I can hear folks at the other end on either headset (actually, I have added a V1 as well) regardless of whether I or they initiated the call.
We'll see what the future brings here. But, for today, this is working.
I tried hard resets. Still no go.grrr... I dunno about you, but it just drains me to redo all my contracts and settings on the phone after every hardreset.
Hopefully your BT will stay working. Someone else here reported that it worked then stoped working after a while.
I have the same issue called HTC support last week and they where able to replicate this issue. If more people call HTC they may fix this problem faster.
I called ATT about it. Not aware. Of course they tried it and worked. It seems to be random on when it quits working. I know mine worked for a while. I just don't know what caused it to quit. And now that it did quit working, I can't get it to transmit the incoming caller to my BT. He can hear me though.
If it wasn't an hour job to restore it back to the way it was, I would hard reset it again. Tired to that at the moment.
I'm having the same issues on my Fuze. I unchecked 'announce incoming caller' and now it works just like my previous phone. My question is, what does announce incoming call actually do? Is it supposed to say who is calling through the bluetooth headset?
I too have this issue in my car (I haven't tried it yet with regular headsets, but I imagine the result would be the same). I have made the tweaks to the registry to get the Fuze to announce incoming calls, but the announcement is so soft, I can hardly hear it. I also have the issue of not being able to hear the person calling me (outgoing calls are fine).
I just did some experimenting and was wondering if others can duplicate this.
With Announce incoming calls on, when a call comes in and you answer it with the button on the headset (or the answer button in the car), you can't hear the person on the other end even though they can hear you.
Now try having an incoming call answered by hitting the Answer button on the phone itself (I only tried it with the on-screen Answer button, I didn't try it with the phone's hard button). You can now hear the person on the other end and they hear you. I was able to duplicate this numerous times.
Same issues...
With Announce Caller on in Voice Command, I cannot hear the caller if answering via the bluetooth headset. I'm not even sure it's is announcing the caller, but the custom ringtone is playing. If during the call you switch off the handsfree (via phone menu), then turn it back on, you can once again hear the caller.
If I turn off the Announce Caller function in Voice Command, I only get beeps in the headset, but I can hear the caller.
AT&T Fuze
Yes. I'll say the callers name if its in your contacts, or it'll say the phone number if it isn't. real helpful if you don't want to take out your phone.
DaRealGMan said:
I'm having the same issues on my Fuze. I unchecked 'announce incoming caller' and now it works just like my previous phone. My question is, what does announce incoming call actually do? Is it supposed to say who is calling through the bluetooth headset?
Click to expand...
Click to collapse
Err isn't that was I said in the original post? I mean about how its answering from the BT device that causes the incoming caller to be muted.
jglev said:
I too have this issue in my car (I haven't tried it yet with regular headsets, but I imagine the result would be the same). I have made the tweaks to the registry to get the Fuze to announce incoming calls, but the announcement is so soft, I can hardly hear it. I also have the issue of not being able to hear the person calling me (outgoing calls are fine).
I just did some experimenting and was wondering if others can duplicate this.
With Announce incoming calls on, when a call comes in and you answer it with the button on the headset (or the answer button in the car), you can't hear the person on the other end even though they can hear you.
Now try having an incoming call answered by hitting the Answer button on the phone itself (I only tried it with the on-screen Answer button, I didn't try it with the phone's hard button). You can now hear the person on the other end and they hear you. I was able to duplicate this numerous times.
Click to expand...
Click to collapse
Yup. That's the issue. It's only if you have VC to announce the incoming caller on, and you answer the the incoming call from the BT device.
DerralVL said:
With Announce Caller on in Voice Command, I cannot hear the caller if answering via the bluetooth headset. I'm not even sure it's is announcing the caller, but the custom ringtone is playing. If during the call you switch off the handsfree (via phone menu), then turn it back on, you can once again hear the caller.
If I turn off the Announce Caller function in Voice Command, I only get beeps in the headset, but I can hear the caller.
AT&T Fuze
Click to expand...
Click to collapse
starstreak said:
Yes. I'll say the callers name if its in your contacts, or it'll say the phone number if it isn't. real helpful if you don't want to take out your phone.
Click to expand...
Click to collapse
that's what I thought. But even when the announce option is checked, I don't hear anything except ringing on my bluetooth headset.
That's a different issue. But fixable. Do a search for microsoft voice command call announcement.
starstreak said:
I dunno about you, but it just drains me to redo all my contracts and settings on the phone after every hardreset.
Click to expand...
Click to collapse
Are you serious? Have you tried to back up your PIM info with the Sprite Backup that AT&T includes free on the phone? Or even sync it with your desktop?
Err yes. But when it didn't fix the BT issue, I had to hard reset. And resyncing to the computer takes a while, so is trying to redo all the edits you previously made before the issue happened that forced a hard reset.
motionmind said:
Are you serious? Have you tried to back up your PIM info with the Sprite Backup that AT&T includes free on the phone? Or even sync it with your desktop?
Click to expand...
Click to collapse
I just got off with HTC support as well. The other poster that talked to the guy that confirmed it. That tech said he could get it work on the phone itself but not using BT. They have sent some thing to MS to try and get a hotfix for it. Once they get it they will post under the support for the Fuze.
Right now no fix for it.
Does anyone know if there has been a fix to this? On my fuze if I make a call with by BT headset I can't hear the caller when they answer.
are you guys answering the phone on your handset or on your phone? because if you answer a call with bluetooth paired on your phone directly the sound will come out of the phone's earpiece. if you answer the call on your bluetooth headset's answer/hang up button then the sound will come through the headset.

Voice Dialing with Fuze

Does anyone know if you can activate voice dialing over bluetooth? I know that there were several hacks that were necessary to get it to work over my 8525.
Thanks!
Yes you can. It's called Voice Commander. It should be on by default. You can say stuff like "call john smith" or "dial 123-4567" pretty cool.
Voice Command with Bluetooth Headset??
I have an old bluetooth headset, but it doesn't seem to work with Voice Command. Does anyone have one working?
Yes, i have used vc with 3 different headsets. One moto, one jawboneII, one plantronics, and one stereo sony brt50 with a2dp. All worked well when pressing the command button on the hs. I've noticed it doesn't work quite well using phone for the command or to answer when cal comes in. The audio drops or doesn't connect.
Hmm, I have an old Moto H505 from work and not only do I not seem to be able to initiate a voice command using the headset, if I do initiate one using the phone I do not hear the response in the headset.
Thanks for letting me know that it is possible....
I had some issues with the stock VC on the ATT ROM. With ROMeOS though it doesn't come with VC (or at least not that I could find) so I added the latest PPC VC (1.6.19214) and it seems to work just fine now (including announcing calls via BT).
I thought that VC in general did not work with bluetooths. This is a limitation of VC not the phone or the bluetooth. On my old mogul, you could get it to initiate the command but not hear your response or confirmation.
Works fine for me with a Jabra BT-135 headset -- giving commands, getting feedback, and answering phone calls all work as expected. The only thing that doesn't work is announcing the name of the caller for incoming calls; all I get is a ring for that. (I have the stock AT&T ROM.)
pre-record for voice dialing?!
starstreak said:
Yes you can. It's called Voice Commander. It should be on by default. You can say stuff like "call john smith" or "dial 123-4567" pretty cool.
Click to expand...
Click to collapse
That's OK, but what I really want is to record names for each PHONE# foreach contact, like "call Scott CELL" or "call Scott HOME" or "call Josh OFFICE" like I used to do with my HTC MDA w/ WinMo5. Can I do this? I've been searching the phone and forums and this site's postings too... any help?
If you can load the program - it is in the WM 6.0 ROM - it will work with bluetooth devices.
markmensch said:
That's OK, but what I really want is to record names for each PHONE# foreach contact, like "call Scott CELL" or "call Scott HOME" or "call Josh OFFICE" like I used to do with my HTC MDA w/ WinMo5. Can I do this? I've been searching the phone and forums and this site's postings too... any help?
Click to expand...
Click to collapse
There's no need to do that with voice command. As long as your contacts are stored properly (i.e., a contact's mobile number is stored as mobile, their home number is stored as home, etc) you can just say something like "Call name on mobile", or "Call name at home".
From MS on how to use it:
http://www.microsoft.com/windowsmobile/en-us/help/more/voice-command-tutorials.mspx
Thanks Syntrix, Joecd04475 for the help, appreciate it. Not real excited about saying, "Call.. Doe, John... at... Mobile" when I'm used to saying, "John cell", but looks like that's what we got w/ WM6
markmensch said:
Thanks Syntrix, Joecd04475 for the help, appreciate it. Not real excited about saying, "Call.. Doe, John... at... Mobile" when I'm used to saying, "John cell", but looks like that's what we got w/ WM6
Click to expand...
Click to collapse
Well, you can get rid of the "...", at least -- Voice Command, in my experience, seems to be pretty good at deciphering connected speech. And there's no need to invert the names, either (I don't even know if it would work that way). In any event, it doesn't seem a great hardship to say, in a normal speaking cadence, "Call John Doe at work."
You might want to have a look at the German ROM version as there is Cyberon Voice Command included which exactly does what you want. You can record voice commands for each phone number, program, ... on your own. I still think MS Voice Command is more preferable as you do not have the hassle to record voice commands for every contact and so on on your own.
CU,
Cactus World
Call John Cell isn't any different then Call John on mobile.
MSVC also allows you to control other aspects of your phone in addition to calling contacts.
Play Metallica
Play Iron Maiden
What time is it?
What is my signal strength?
Ringer vibrate
Ringer off
Ringer high
and a ton more things you can speak also.
NotATreoFan said:
MSVC also allows you to control other aspects of your phone in addition to calling contacts.
Play Metallica
Play Iron Maiden
What time is it?
What is my signal strength?
Ringer vibrate
Ringer off
Ringer high
and a ton more things you can speak also.
Click to expand...
Click to collapse
Well, on my MS VC the ringer stuff does not work properly with the TP. And controlling the audio player is kinda funny as you have to pronounce the artist's, album's and song's names in a German way So Iron Maiden would have to be pronounced "Eeron My den"
CU,
Cactus World
NotATreoFan said:
Call John Cell isn't any different then Call John on mobile.
MSVC also allows you to control other aspects of your phone in addition to calling contacts.
--snip--
Click to expand...
Click to collapse
Yes, this is a perfect example of the corporate 'give you *more* of what you don't want' that is difficult to avoid when you're innovative over customer-driven.
Voice Command looks like a very nice feature that will do a lot for me, especially the music options you listed (though I assume that requires I 'play nice' by using playlists, import music through Media Player). It's a large feature that I may become an expert in someday, but a busy week into using my new phone, I just want to dial my most used numbers while driving, and Voice Command simply does not recognise my commands 90% of the time. I have a pretty plain-jane American accent, but VC simply doesn't know what I'm saying.
markmensch said:
I just want to dial my most used numbers while driving, and Voice Command simply does not recognise my commands 90% of the time. I have a pretty plain-jane American accent, but VC simply doesn't know what I'm saying.
Click to expand...
Click to collapse
That's strange; I have been really impressed,with 100% accuracy over the dozen or so times I've used it to call people and dial numbers since I got my Fuze. What is your setup? Are you using it over a Bluetooth headset or via the built-in microphone? (Not sure if that makes a difference, as I've not had any problems either way, but it might be something to try with your phone.) If using the built-in microphone, how far away are you holding the phone when you speak? Is Automatic Gain Control off? (The help file, I think it was, recommended not using AGC.)
Sweet. I had AGC on. I'll switch it off and try out on the drive home.
I'm using a wired headset w/ inline mic, usually great sound quality on the other end (others listening to me) so I figured it should've worked fine. Come to think of it, back when I still used a HTC Wizard, I had AGC off too. Shoot, just realized, maybe the inline mic on my earbud is disabled, maybe I need to hold the phone up to my mouth?
Got so angry trying to get it to recognize me on the drive home, almost threw it out the window. "No, you stupd #%$& I said 'CALL! HOME! AT! HOME!' "
Also, I'm frustrated that my old Wizard 3.5mm headset jack (which played sounds in both ears: double mono for phone calls)---when I use it w/ my Fuze (with USB converter brick) it only plays phone calls AND MUSIC in 1 ear: very vexxing.

Categories

Resources