...Or Should I ash my XDAIIi against a rock!! :shock: I recently upgraded to an XDAIIi (after 5 years iPAQ) :shock: right away there were problems and I sent one device back. The new device I upgrade the Rom and BT stack with the Modified_XDA_IIi_Upgrade_v1.11.162_Radio_1.04 and Broadcom Corporation BT-PPC AV files from this site. And of course not installed the O2 rubbish.
This did seem to help some. I am finding the XDAIIi to be very finicky. To the point I am asking myself if it is worth the hassle. My main issues (the ones that’ll cause me to throw the XDAIIi at the wall) are:
The BT handsfree profile. Now I understand that the BT Stack is wanting in general and I am even willing to put up with the degraded audio quality (even with the upgraded stack) But my problem is that after a few days or installing new progs. the handsfree link is useless. There is a crackling sound in the ear and the other side can’t hear anything.
To top it off! When I do a restore from a backup done just 10 minutes earlier when the BT stack was working does not eradicate the problem. Only a hard reset and rebuild will reset it. Even if I do a hard reset and then a backup the BT stack doesn’t work. Re-installing the BT Files doesn’t seem to help either.
If it is possible to actually get this thing working I would also like to know how to delete the O2 ext. ROM and replace it with a working backup/ cab installers of my own. So that in event the system needs a rebuild I can just hard reset and have all my program and setting restore (like the O2 stuff does). I can always leave backup of the contact data on card.
If it helps: I have a Jabra BT500 headset (it works a charm with any normal mobile phone I introduce to it to and even works with my PC, but be darned if it knows what my XDAIIi wants from it…)
Also I using the following programs (Although I have yet to isolate the problem to a specific program):
AgendaFusion (DeveloperOne)
Tengo & TengoThumb (Xrgomics)
RemoteKeyboard (TranCreative)
PhoneAlarm & ScreenGuard (PocketMax)
MultiIE (Southway)
PhoneDashboard and IPdashboard (Hudson Mobile)
WISbar Advance2 (this one may in general be problematic with the XDAIIi – I don’t know)
Thank you
Josh Engle
After playing around some days (and yes: i read through a lot of threats) i think that this problem (using a bluetooth headset to activate ms voicecommand for dialing and so on) is not only bugging me but a lot of others.
Thats why I want to start ANOTHER, more structured thread about this topic. If something is wrong, please correct me!
WANTED SOLUTION:
Most of you want to use voicecommand activated via a bluetooth device... in your car beside TomTom for example.
PREPARATION: Headset working
I assume that you already got your device working. For myself, I am testing with Supertooth II and a Nokia BH200 hands-free device.
PROBLEM 1: TRIGGERING
First off all, voicecommand needs to be "started" when you press a button on the headset. Usually, the application "windows/sddialer.exe" is launched when bluetooth gets a "voicecommand"-commando.
(Some headsets got their own button, some wants kinda double-click, others want their button hold for some seconds to do so...)
This problem can be solved by changing a key in the registry:
Code:
HKEY_LOCAL_MACHINE/Software/OEM/VoiceCommand/
..Then change the path value to:
\Program Files\Voice Command\voicecmd.exe
(or whereever you installed your voicecommand exe-file!)
Okay. Now the right application is launched when tapping on your bluetooth headset. But here you may encounter the next problem: It works only once.
PROBLEM 2: IT WORKS ONLY ONCE
That problem seems to be caused by voicecommand, because the gateway is left open after useage. (I have no idea if this is correct - i am just citing the opinion of some threads)
There are some attempts to solve this:
Darryl Burlings "Voice Enable": http://www.burling.co.nz/downloads.aspx
Project VCABT http://forum.xda-developers.com/viewtopic.php?t=23558&highlight=vcabt
VCBTFixer0.01.
JETware Hands-free Extension for Windows Mobile phones
http://www.jetwaremobile.com/
I tried them all and for me (german T-Mobile Rom 2.21) only Jetware's Tool worked. A reason MAY be that some of the hacks (vcabt, VoiceEnable,VCBTFixer0.01.zip) only work with an english ROM where all paths are correct: /programs and not /programme)
PROBLEM 3: Correct Audiotransfer
Some users report that it seems like there is still Wizards microphone in use - and NOT the one of the bluetooth device. Others again claim that voicecommands "answer" isnt delivered back to the headset but speaken via Wizards speakers... Since I used Jetwares Tool i didnt had that problem.
PROBLEM 4: Recognition Quality
Lets say you got somehow the correct and everlasting triggering of voicecommand via bluetooth working... then you may find out that recognition ends up with very poor quality.
Here a question for the "pros" in here: Could it be possible that this problem is related to poor bitrates in the audiotransmission via bluetooth? Could we increase recognition quality by tweaking that bitrate? Or will that end up with another problems (bt-bandwidth, cpupower while coding/encoding)?
PROBLEM 5: Interfering with other applications
Thats a future question... When everything works well with voicecommand - then you maybe want to use it in your car to have your hands free. And what else do most of us have there too? TomTom (or another navigation tool)!
So how will that work together with your voicecommand/bluetooth environment? Will TomTom "speak" via your headset too? Will the bluetooth gps mouse keep on working without problems?
And last but not least: Will you still be able to use your phone as a "phone" then?
Please share your ideas about theese problems... and if anyone got everything up and running (Voicecommand & Bluetooth, TomTom / GPS) it would be *very* appreciated if you could post a well written Tutorial / Howto
Regards, Licht
Good luck - for what its worth it works fine with certain BT headsets like the Moto HS850. Just the reg key does it.
Only thing is you have to hit the button on the BT headset 2-3 times sometimes to get it to work but it works perfectly otherwise.
Would LOVE to have a fix that would let me use with all headsets.
How does the jetware stuff work? I heard it screws up some other things?
Cause of "works only once" problem discovered?
I've gone through 4 different headsets with my Wizard and I found at least one commonality to which ones suffered the "works only once" problem:
All of the ones that had this problem were BT 2.0 headsets. The ones that worked fine were all BT 1.x headsets.
I also verified that on my new TyTN (which natively support BT 2.0) the BT 2.0 headsets worked correctly (no "works only once").
Not that this is any consolation to anyone with a BT 2.0 headset and a Wizard, but might help those looking for a new headset.
Changed over to Tytn... works perfectly without any hacks
here's my FWIW answer:
After extensive reading here and at Hofo, I settled on a Plantronics 510. Installed Burlings app and it worked. I hold the button to turn on VC (it will also wake the device from standby if its sleeping, even if its locked) and say my command. It will reply through the headset speaker. After that all audio is oing through my BT headset. (If you have VC telling you who's calling and telling you your appointments thats pretty nice, but if the phone rings you might need some new underwear)
Another long push of the headset button return audio to teh MDA's speakers. If I need to use VC again, I start all over. It sounds more complicated thatn it is in reality.
Recognition is so-so. I don't really use it in my pickup (its hot so my windows are down most of the time), but its pretty good in my car. I have to repeat myself maybe 10% of the time, at most.
Not sure how well written that was, sorry. if anyone has any questions I'd be glad to answer them. I've been pretty pleased with the combo. Especially since I got the 510 for $40 from amazon.
I searched and didn't find any previous postings regarding an issue with Parrot and Audi Hands Free (Bluetooth) car kits and the TyTn.
This issue is only with the TyTn and the Wizard devices work fine.
It seems to pair fine with the car kits but 5 minutes into usage...the TyTn turns the bluetooth off on the device.
Then about 1 min later, turns Bluetooth on again. The cycle then begins Off and then On ....
Here's a link on the Parrot forum.
http://www.parrot.biz/forums/english/viewtopic.php?id=2667
I've got the same problem with my Seat Leon (new model) bluetooth carkit !!!
I think it's the same module as in the Audi (all VAG related cars).
It's very irritating !
I hope they will fix it soon....
http://forum.xda-developers.com/viewtopic.php?t=58789&highlight=
:wink:
Er... not followed as far as parrot (down for maintennance) BUT
I've found with my Seat Leon kit that the phone needs to remain in a fully powered state - you can't put it into the sleepy state by the power button otherwise you get the intermittent but eventually endless dingling of it connecting and disconnecting.
Best way I've found is to leave it on asking for a password with the cover on.
edit: Should just point out that you also need to turn off any power off settings - except for the backlight.
Pyranwolf said:
Er... not followed as far as parrot (down for maintennance) BUT
I've found with my Seat Leon kit that the phone needs to remain in a fully powered state - you can't put it into the sleepy state by the power button otherwise you get the intermittent but eventually endless dingling of it connecting and disconnecting.
Best way I've found is to leave it on asking for a password with the cover on.
edit: Should just point out that you also need to turn off any power off settings - except for the backlight.
Click to expand...
Click to collapse
I'm going to try this !
I hope that it works.
Thanks anyway.
What kind of Leon do you have ?
I've got an A6 with BT kit and am having this problem. I cannot make/receive a call whilst running my BT GPS device & TomTom, although from reading this the issue may be the Audi kit anyhow.
Are there any fixes available - be it HTC or Audi? Or are there any work-arounds, such as add-on software for the TyTN??
Please help - it is driving me mad. Spoiling what is otherwise a great piece of kit.
I have been having this exact problem with my Audi A4 with Audi Bluetooth.
I did wonder if it was in some way connected with the phone going into sleepy mode as it is being powered by the phone battery.
Also, the bluetooth stops responding after 5-10 minutes, but if I am continously using the phone, it seems to be ok.
Therefore, I think I need to buy an in car charger, and see what happens...
Has anybody else tried this that can confirm it works?
Markee
Just a quick note to Paul_o
My Audi A4 / SPV M3100 / Tom Tom / Bluetooth GPS work fine together.
If I am in Tom Tom, and get an incoming call, the little call window pops up over Tom Tom, Tom Tom carries on and the phone audio is routed through the speakers - the only irritating thing is that the Tom Tom lady keeps interrupting... :wink:
Mark
Hi,
I'm using Vario 2 with Audi Bluetooth and also having the BT ON - BT OFF issues.
These are my findings.
- Without JETWARE software:
- BT goes ON and OFF in the car regardless of the VARIO 2 being on or stand-by, or the phone being battery powered or connected to the car.
- Once a conversation is started the BT connection seems to be remain ON.
- With JETWARE software
- If I leave the screen always on the BT connection stays always ON. Only backlight automatic switch-off is selected
- I have tried several screen toggle programs (which claim that they only power down the screen) but the BT goes OFF in the car after a few minutes.
I'm happy to test any other proposal.
Cheers,
C
What version of JetWare are you running, they have a beta which has settings for the Audi kit, this may help, there is also a registry setting that is meant to change the power settings when bt is connected. An extract from an email conversation with Jetware...
We have also addressed the power issue, but this fix requires a registry change. Please create a DWORD registry value in HKLM\Software\JETware\AGExt named InSessionPower with a value of 0 (valid values are 0-4, with lower values indicating greater power availability). This will tell the OS that the Bluetooth device should stay at full power while it is in a Hands-free session.
Not sure if this will help, my Hermes is ariving on Monday, I'm was hoping that all the problems i've had with my magicain and the audi kit would go away with the Hermes, but maybe not.
Give the key a go and let me know
Hi dh,
thanks for your reply.
I haven't installed the Beta version yet. However I have changed the registry setting and will test first thing tomorrow. If this doesn't fix the problem I will try the Beta version with the Audi setting.
I'll keep you posted.
Cheers,
Carles
Hi dh,
I have tested the two proposals (Change in the registry and the Beta version + Audi settings) without much luck. The BT connection with the car keeps going ON and OFF when the phone is running on battery.
Have you got your Hermes? any luck?
Thanks,
Carles
Got my Hermes (Orange M3100) a couple of days ago. I've installed the JetWare extention, and without the InSessionPower set the connection is dropped. So far with the setting applied it has stayed connected. I have had other problems like not being able to make calls etc, which is a bit of a issue. I need to do some more testing, as i've been messing with the phone a bit.
I'll update here in a couple of days
Must say i'm very disapointed with the phone regarding this. A couple of weeks ago i had a Wizard which worked flawlessly with the JetWare extention, no power issues, calls made and received without a single problem. I wonder what has changed with the bt implementation between the Wizard and the Hermes?
Hi dh,
You will see from my previous postings I have had the same problems too.
It should be noted, though, that the Vario (wizard) worked flawlessly with the Audi A4 Bluetooth without Jetware software.
Has anybody been able to prove there is no problems if the phone (SPVM3100) is powered whilst in the car?
Cheers
Mark
I have a factory fitted hands free system in my Vauxhall. Every other phone you can think of works with it...EXCEPT my XDA mini. It seems to pair up, but there is no signal showing from the carkit. It might work for a minute and then it drops out. Is it the XDA or Vauxhall that's at fault? It seems that nobody knows the answer and I paid serious money for this bit of car kit. I like the phone, it really is annoying. I have tried another XDA mini as well and that doesn't work either. Does anybody else have a Vauxhall with the same built-in system and not connecting?
Markee
I've had the phone plugged in without the registry entry and it seemed to be ok. If I can get to a stage of a working solution i'll test again without the registry entry and with external power.
dh said:
Must say i'm very disapointed with the phone regarding this. A couple of weeks ago i had a Wizard which worked flawlessly with the JetWare extention, no power issues, calls made and received without a single problem. I wonder what has changed with the bt implementation between the Wizard and the Hermes?
Click to expand...
Click to collapse
I'm guessing that since they went from BT1.1 to BT2.0 they had to make a new stack.
My Wizard worked PERFECTLY on my Parrot, my TyTN is almost useless on it.
you make a very good point ScottC, that'll be what it is.
Just driven home and could not make a single call with Jetware installed. Removed it and i could at least make a call, but i didn't get any status info or phone book. I didn't get a chance to leave it connected without Jetware for longer enough to see if it disconnected without external power, i imagine it will. I will test some more later/tomorrow. I'll also send an email to Jetware to see what there thoughts are regarding bt v2.0 and their product
Hello,
I have an Audi A3 with the factory fitted Phone kit but without the Audi Craddle so I'm using the Bluetooth connection.
I have tried the Vario (Wizard/QTEK 9100) and Vario 2 (Hermes/TyTN) and had similar problems with the two of them. Once the connection is stablished I can make and receive calls without problems. The issue is that the BT connection goes ON and OFF without an apparent reason.
The only thing I have seen is that when the Vario is kept on (only the backlight is off) the BT connection normally stays ON, regardless of the phone being powered or not.
I have tried Jetware, the Beta version, the registry entry, programs to switch off the screen...but haven't seen any real difference.
I have bought a bluetooth USB stick and will do some test at home to see if the problem is with the car or the phone.
I called T-mobile and they said it was a faulty phone, but I don't think so.
Keep the postings, we might end up finding a solution
Cheers
C
Try upgrade the BT software. I had the same problem after that i upgraded de Parrot software. Now i have the version 4.16
Hi,
I researched this quite extensively but no real solution yet.
I have Kaiser and I recently bought Audi Q7. Kaiser works fairly OK over Bluetooth (Jetware installed). I can see and import contacts - not a very elegant process since the name and surname get joined up and all the numbers, which belong to any one contacts are shown separately (with /M, /W etc.) and I have to do a lot of work manually to sort everything out after import. But I can live with that.
However, I would like to integrate my Kaiser into the phone prep located underneath the central armrest (I believe it is universal so I can put on any cradle supplied by Audi - it just seems from the list of supported devices that Audi sells no cradle compatible with Kaiser or any PDA phone), so it would use the power supply and antenna in the car.
Can anyone help me in any way?
So, no solution anyone? I've been searching for days now and it seems that the only practical thing would be to buy a cradle for another phone and then convert it somehow for use with Kaiser... Not a very elegant solution though...
BR
You can use Bluetooth rSAP adaptator for this connection: it is Audi ref. 8P0 051 440 for the A4 (2008);and it looks identical connection...
You may also have standard hand free bluetooth by the MMI (but this don't use external car reception), I can use the phone contacts also this way in A4...
Have a Citroen Bluetooth car radio (Blaupunkt) and was using that with a WM6 device. Lots of problems until I loaded Jetware which made it rock solid. Dumped the WM phone - now using a Android HTC (Desire).
Very unreliable bluetooth on Eclair - never solid and directory (phonebook) always an issue. Just switched to Froyo (Leedroid) hoping it would fix the issue. No such luck - most of time connects (pairing works fine) but as soon as I allow access from the car radio to the phone (to read phonebook) things go south.
Was wondering if I'm alone in this or if there is a fix for it. Ideal would be to have Jetware on Android - one great feature it has is that it can limit the phonebook transfer to a specific category - which is much more usefull then pushing the entire 500+ entries to the car.
Any help appriciated.
thnx
Exactly the same problems with wildfire/2.1. Was hoping 2.2 would fix it! SORRY TO HEAR otherwise.
No solution found yet. htc unable to help on the phone either.
(JVC 811 head unit)
Very disappointing after perfect WM integration.
Guy
Have a colleague that had the same issue on his Audi.
If you DENY access to the phone book - it works fine (although it takes a while to fully sync, and the number of entries is still an issue)
+1 for Jetware on Android - reeaaaaallly need it..
-Craig
+1 for Jetware for android.