Database Users

Multiple Bluetooth Devices

Hi there guys, its been a while since posting but I have some great news regarding using multiple bluetooth devices in the car.
A few weeks ago I purchased a Navman 4410 GPS unit for my XDAII. With the new "72" rom the Navman worked perfectly with my XDAII straight out of the box over bluetooth.
Today I installed a Sony Ericsson HBC-30 bluetooth hands free carkit (Which also worked perfectly out of the box). I was interested to know if I could have the GPS unit operating and have the handsfree carkit working at the same time.
I was simply sitting in the carpark, with the GPS connected and onscreen, then I used my other phone to call my XDAII... the call came up on screen (interrupting the GPS screen) I pressed the "answer" button on the Sony Ericsson handsfree kit, and the call came through perfectly!
Once finished with the call I pressed the "hangup" button on the handsfree kit, and then a few quick taps on the screen returned me to the GPS navigation screen.
Certainly not perfect, however it appears that the bluetooth issues are finally getting resolved, and allowing us to begin using the XDAII as it was intended.

Hi Colonel, thanks for your update, it is comforting to know that they are finally sorting out BT problems.
Is there any way to get the phone screen to automatically close after finishing a call? so I don't have to manually close it to get back to my GPS screen?

No I dont think you can. Not without altering the GPS software to continually make sure its "on top" of other windows... but then you'd have a problem with seeing the "incoming call screen" as the GPS software would try to jump on top of it.

I'd be so happy simply if I could make HCB30 and Blutrek G2 headset work side by side on my Qtek...

points are:
1-where coul i get that da***n 1.72 rom for my xda 2
2-where could i get the g2 HS in italy(even worlwide...) or all over the web at reasonable price
help a newbie...

Kolonel,
I can confirm your experience as far as BT GPS is concerned.
I however still have one issue to solve: When the MDAII (=XDA2) can't connect to the GPS (BT off, GPS off, GPS out of reach) and I start TomTom3, TomTom3 keeps searching for the GPS which results in a almost freezing MDA2.
Using rom 1,72 from Qtek I bonded the BT GPS and confirmed the question about assigning a com port.
In TomTom I assigned this (COM5) com port.
All works fine except for the issue mentioned.
Does this sound familiar?
Clues?
BTW in the BT settings screen there is nothing shown about the assigned com port (just free space next to the two lines that should indicate the in- and outbound com ports). I found COM5 to be assigned to BT by trial and error . . .

edsub said:
Kolonel,
I can confirm your experience as far as BT GPS is concerned.
I however still have one issue to solve: When the MDAII (=XDA2) can't connect to the GPS (BT off, GPS off, GPS out of reach) and I start TomTom3, TomTom3 keeps searching for the GPS which results in a almost freezing MDA2.
Using rom 1,72 from Qtek I bonded the BT GPS and confirmed the question about assigning a com port.
In TomTom I assigned this (COM5) com port.
All works fine except for the issue mentioned.
Does this sound familiar?
Clues?
BTW in the BT settings screen there is nothing shown about the assigned com port (just free space next to the two lines that should indicate the in- and outbound com ports). I found COM5 to be assigned to BT by trial and error . . .
Click to expand...
Click to collapse
edsub,
Are you using "Bluetooth Tools"? Because I am not, i'm using the native bluetooth stack only.
I am using "Outbound" Com port 5 ONLY for my GPS. My 1.72 rom is the IMATE rom.
Im afraid that i'm not familiar with tomtom. So I cant help you there, sorry.

I am deliberately only using native MS bT stack.
I am only using COM5 for GPS too
What does the BT Settings show under
"Bluetooth Serial Port Setup"?
With me:
"Outbound COM port" checked, but after the colon is a "<not present>" shown.
"Inbound COM port" UNchecked, after the colon is a grayed-out "<not present>" shown.
Like i said I AM able to use the GPS via COM5.
Maybe this issue is a pure TomTom issue, I think your answer could clarify that.

edsub said:
I am deliberately only using native MS bT stack.
I am only using COM5 for GPS too
What does the BT Settings show under
"Bluetooth Serial Port Setup"?
With me:
"Outbound COM port" checked, but after the colon is a "<not present>" shown.
"Inbound COM port" UNchecked, after the colon is a grayed-out "<not present>" shown.
Like i said I AM able to use the GPS via COM5.
Maybe this issue is a pure TomTom issue, I think your answer could clarify that.
Click to expand...
Click to collapse
Edsub, thats really weird... mine is:
"Inbound COM port:" UN checked, and after the colon is a grayed out "COM4"
"Outbound COM port:" checked, and after the colon is a black "COM5"

bluetooth
hi guys
im using imate 172 and tomtom 3 with a sony ericsson hb35 it works first time all the time with the standard stack. it works that good i even went and sold my carkit and just got a hold instead :lol:

@Kolonel Klink: I guessed it's strange. What ROM are you using exactly (OS & Extended).
I use the 1.72 Qtek rom with my own Extended Rom (wich is based on the Qtek ExtRom to which I added T-Mobile Nl customisations). I am sure there is nothing regarding Bluetooth in my ExtRom.
I heard from someone who uses the iMate 1.72 OS Rom (with his own cooked ExtRom) that he has the same results as you have.
Just trying to find to cause of this. Maybe I have to reflash to the iMate 1.72?? (shouldnt make a difference as both iMate and Qtek OS ROM's are the same 1.72.00WWE . . . .)
@freelockuk: Most interesting is the origin of your ExtRom. Arent there any Bluetooth enhancements in that ExtRom (like there were in the 1.60.36 T-Mobile NL ExtRom) that maybe make your 1.72 work better than mine concerning Bluetooth?

addition to prev post:
I noticed that there were two BT registry settings missing to get the assigned COMport show in BT Settings.
Also noticed another interesting value:
[HKEY_LOCAL_MACHINE\ExtModems\bluetooth_dun]
With me this one is:
"port"="BSP9:"
In prev versions it was:
"port"="BSP4:"
Can anyone with a 1.72 ROM that has a BT GPS mouse working via SPP AND who can start Tom Tom without the BT GPS mouse 'connected' post their setting of this key??

Okay, i've not cooked my own extended rom. I'm using the stock standard one from iMate.
I did find something odd today. I went into an IT expo and I turned flight-mode on. When I was finished I left and turned flight mode off. Then got in my car. I tried to make a call and it didnt go thru the handsfree kit.
Weird! I had to repair the device. So I did... and it all worked fine again. So I turned flight mode back on then off, and I ended up with the same result. It appears to lose the pairing when you turn the flight mode on.
Very odd!

I still have not found a solution to the behaviour where TomTom locks up the MDA with is isnt able to connect to my BT GPS.
Today I found out that this same behavious accurs on devices (not just MDA, HP too) that use a serial (wired) GPS when they take the current off the GPS . . .
That means:
1. TomTom Navigator can't cope with the situation where it cant connect to the GPS that is installed
2. With me TomTom navigator is not able to use the Bluetooth protocol on its side to cope with the (for Bluetooth GPS quite usual) unavailability of the BT GPS.
Again: Can anyone post me some info on this :?: :?:
Especially the registry items under
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\]
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\SerialPort]
[HKEY_LOCAL_MACHINE\ExtModems\bluetooth_dun]
[HKEY_LOCAL_MACHINE\ExtModems\bluetooth_dcn]
are of interest

@ Klink
Thanks for sharing your experiences, I'm watching them with interest.
Just wanted to as you about using your navman and the headset at the same time.
In your first post to this topic, you mentioned your 'carpark' test. I assume you weren't moving at the time, so the navman wasn't trying to give you directions.
What happens when you're driving along, getting instructions (ie. "turn left in 300m") from your navman, and the phone rings? Does the navman stop giving directions while you are talking on the phone using your BT handsfree? When you hang up does it resume giving directions again?
Thanks,
Hooligan

Emtact Trine BT GPS, Bluetrek G3 BT Headset
Like all of you my exprience is that it all works together.
But I've one problem. When navigating with TomTom and there is a incoming phone call and when I accept the call with my headset TomTom continues navigating but the sound of my QTEK2020 is muted during the call. So the instructions of TomTom cannot be heard.
I'm using plain MS BT Stack.
Regards,
Mark

This behaviour seems not the be dependent of the use of a BT headset. I have a carkit and during a call TomTom stays active in background. Sound of TomTom is muted however, which I find nice.
When the phone call is ended, TomTom starts talking again.(also nice)

first of all my nevigation program works great with the jabra 250 bt , it also mutes the program during a call is madeqreceived but :
there is anothe program that is called "ontime" that sends trqaffic status to the imate, using the gprs andthen calculates the fastest root( from junction to juction) and the problem is:
if i want to use buth progtams with royaltek gps bt rbt1000 they both need the com5 port fot bt.
to solve this problem one can use a prog called: "gpsgate" which makes a virtual port for the programs to use so u can use several program with one bt device.
for some it works only with bt tools, for others it doesnt work at all, gos knows why?!
but - if any1 needs a solution - here is one.
have a nice day , spark
QTEK 2020 - 1.72.00 WWE - 1.06.01
Back Pack - jabra 250 BT- royaltek rbt 1000 GPS BT - DESTINATOR3(LIKE TOM TOM 3) - soon will recieve sd 1gb*40

Spark, where did you get 'gpsgate'??

here is the link
http://franson.biz/gpsgate/download.asp

MDA Compact (MDAc) and BMW Bluetooth Module (SA633)

Hi
I just got my new BMW 330 (E90) with Navigation and Bluetooth. I can pair my MDAc but that's it.
When a call comes in, My BMW signals it. Sometimes I can get the call with the button in the steering wheel. Sometimes not. Sometimes I can but the connection breaks down in the middle of the call.
I see the reception of my MDAc in the display and when a call comes I also see the number of the caller.
I cannot make a call (dial out).
I read a lot but did not find a solution yet. Has anyone experience with BMW carkits or any advice what to change in order to get it going. I sort of refuse to have another handy...
BTW I have the latest T-Mobile Update (1.12) but I did not install everything from the extended ROM.

I have exactly the same problem with Audi bluetooth, with my Nokia 6230 works perfectly, with my S100 I have the same problems you have experienced. I have an old ROM 1.06, but I see that even with 1.12 the problems are not solved.
I tell what I tried: I've installed various BT stacks (Toshiba, Widcomm, Bluesoleil also with crack). Toshiba pairs but does not find any service, Widcomm does not run, Bluesoleil does not have the needed profiles.
I have installed the CAB from VCABT project (see the thread in this forum), I can answer from the car I can call using the car voice command but I can't use the S100 buttons.
Hope that somebody could help us.
dgv

fdigianv, have you tried the new A2DP Stereo BT Tool to see if it works better with your Audi.
I just upgraded my JAM to 1.12 and have yet to try it with my Audi A6 4.2 2005 MMI BT System.
I'm tired of waiting for Audi to fix anything. It seems like the only fixes or upgrades they offer come in the form of a new car release.
I like you can call out from the Audi, but those on thger other end of the call complain about sound quality.
I'm getting ready to make a move to the new Treo MS Mobile device, or a smartphone that works better with my Audi.

I spoke to BMW this morning and they claim has more to do with the version of Bluetooth installed on the phone than BMW's implementation of Bluetooth.
BMW supports Bluetooth verson 2 and up.

PIONEER DEH-P70BT and 02 XDA EXEC

Hi I cant get my Pioneer bluetooth radio to connect to my XDA EXEC I have used my Pioneer radio to connect to other phones fine.
Anyone else got this working?
also can u rename the Bluetooth on the EXEC

I don't have an answer, but can you comment on how the pioneer radio works as a hands-free kit?
Not technically how it works, but how you have found it ie: echo's, caller experience etc.

Works fine the mic that comes with the radio works great, I installed it in the top right hand corner of the drivers side, and even if passanger wants to talk the person hears other end,
Some people have said that there is a bit of a Echo on there end.
Normally it conncect to bluetooth phones easy, juts click on register it finds phone then enter code on phone and done.
I have managed to see the radio from connecting from XDA to the radio, but the radio will still not register it !!. can anyone help.

Don't use the radio's 'register' function. Go to connect and set it going then go to the pda and add a new BT device with the code 1111. Worked for me on my JAMin.
Regards

Can anyone confirm if the Exec is compatiable with this stereo? I've got an Orange M5000 and was thinking of getting this stereo, specifcally for the bluetooth functionality.
I don't think the phone is on their compatibilty list, but I know these lists aren't always kept up to date.
Thank you in advance!

ianlarner said:
Can anyone confirm if the Exec is compatiable with this stereo? I've got an Orange M5000 and was thinking of getting this stereo, specifcally for the bluetooth functionality.
I don't think the phone is on their compatibilty list, but I know these lists aren't always kept up to date.
Thank you in advance!
Click to expand...
Click to collapse
Maybe you should tell us your ROM version so we can see if it has A2DP support.

ROM Version 1.30.90 WWE
Radio Version 1.03.00
Ext Rom 1.30.174 WWE
Thanks

Remote SIM Access Profile (rSAP) working on Orange SPV M3100!!

I've been looking around these forums for a while now trying to find a solution to the Orange/rSAP issue, and have finally found a solution...
I've basically just combined the instructions from various posts about various things to make this work, so i'll include all the info i found and try to credit people where necessary - apologies in advance if i've forgotten any, but i looked through so many threads and pages it was unbelievable!
Anyway, this is basically a step by step for getting your Orange SPV M3100 (and probably any Hermes/TyTn variance that has had remote SIM access removed by the provider) to work with a rSAP enabled accessory (the VW Passatt Bluetooth Premium kit in my case).
First, you need to change the TyTn's bluetooth identity to be a phone, or the rSAP accessory will not recognise it (funnily enough, bluetooth rSAP car kits don't look for pocket PCs). Here's how:
Download PHM RegEdit - it is important to use this exact program as due to Orange's stupid application locking it is the only registry editor i have found that can be installed.
Next, edit the following value:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SY S]
"COD"=dword:52020C (hex)
Bear in mind the new dword is a Hex value, so be sure to select "Hexadecimal" from the Base menu.
For reference (in case something messes up), heres the original value (the Pocket PC identifier):
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SY S]
"COD"=dword:1048852 (decimal)
Next, soft reset. For some reason i had to restart, change the value again (as it had reset itself), backup the registry and soft reset again for the change to take effect. God knows why, couldnt be arsed to figure it out.
Once this is done, you need to unlock and mount the phone's ROM. The easiest way i've found to do this is using the Fit4Cat Hermes Tweaker. The download will most likely require a forum signup, but its free so what the hey...
Use the hermes tweaker to unlock and mount the ROM, save and restart.
When the TyTn has restarted, if its worked you will see an Extended ROM volume in file explorer.
These files need to go in there helmi_c's SAP Test cab (you will need to unRAR first).
This was taken from the following thread: Helmi BA WM2k5 AKU3.2 Beta (v.1.3 Beta)
Cheers for that, helmi! You are a genius
After that, restart. If you do NOT have a new application in your Programs directory called SAPSettings, go into your Extended ROM and install helmi's btsap_test.cab file manually, then restart.
You should now have SAPSettings working fully:- just go into the app, click the enable button and away you go!
I hope this works for everyone, its worked on the 3 M3100s and the O2 XDA Exec ive tried it on so far with no problems so hopfully all is good.
Please post up your results here - itd be good to know the outcome
Cheers,
-JD-

Thank you
At last - I too am trawlling through these forums trying to put together a SAP package for the M3100.
Just one thing for the amateur here - how do you "unRAR" a file???
Thank you
p.s. I dont suppose you know if this will work on aC600 too??? I'll try it when I get a moment..

Better get a CIngular ROM and u hv built in SAP app

hdubli said:
Better get a CIngular ROM and u hv built in SAP app
Click to expand...
Click to collapse
That may be, but not if your pocket pc is company owned.
I should think that a lot of people wanting rSAP will have businessmobiles and probably business phone contracts too. Installing non-orange ROMs on an orange business contract pocket pc is NOT a good idea...hence this way around.
Theres always a reason
p4uly said:
At last - I too am trawlling through these forums trying to put together a SAP package for the M3100.
Just one thing for the amateur here - how do you "unRAR" a file???
Thank you
p.s. I dont suppose you know if this will work on aC600 too??? I'll try it when I get a moment..
Click to expand...
Click to collapse
To unRAR....get a copy of winRAR to unarchive the package
and i should thing the aC600 would work too as long as its on a WM5 Orange ROM.
Cheers,
-JD-

Same Problem with my VPA3 compact III and FWD Audio com
Hi all,
i´ve the same problem.
My CarKit "FWD audio com" won´t connect via SAP with my HERM200 Vodafone 1606 VPA 3 compact III. It always connect via 4 Char Code for talking. SAP Code (16 Char´s) won´t ask and so i´m not able to use the SAP-functions
I tried like the instruction from above.
At first I had the unrar-Problem with "helmi_c´s SAP Test cab".
Everytime you save it to disk, it´s not able to unpack.
If you don´t save it to disk and if you installed WINRAR, just
OPEN it und unpack it via WINRAR to HD ! Now it works.
Back to my Handy and the instruction
I was able to install everything, but if I start Install of "helmi_c´s SAP Test cab" in the Extended ROM there will be a message, that I don´t have rights to install !
I don´t know if the instruction will fix my problem nether the File is for my Fone, but I´ll try.
Does anybody can help me and answer why my phone won´t install "helmi_c´s SAP Test cab" ?
Can Cingular, which I don´t understand, help me ?
Fone: HERM200 Vodafone 1605 VPA compact III
Fone-ROM: 1.20.162.3
Car Kit: fwd audio com

I have a T-Mobile Vario II, and am looking into buying the Sony-Ericsson HCB-700 carcit. I have SAP settings in my programs, will it work ??

Scholle2 said:
Hi all,
i´ve the same problem.
My CarKit "FWD audio com" won´t connect via SAP with my HERM200 Vodafone 1606 VPA 3 compact III. It always connect via 4 Char Code for talking. SAP Code (16 Char´s) won´t ask and so i´m not able to use the SAP-functions
I tried like the instruction from above.
At first I had the unrar-Problem with "helmi_c´s SAP Test cab".
Everytime you save it to disk, it´s not able to unpack.
If you don´t save it to disk and if you installed WINRAR, just
OPEN it und unpack it via WINRAR to HD ! Now it works.
Back to my Handy and the instruction
I was able to install everything, but if I start Install of "helmi_c´s SAP Test cab" in the Extended ROM there will be a message, that I don´t have rights to install !
I don´t know if the instruction will fix my problem nether the File is for my Fone, but I´ll try.
Does anybody can help me and answer why my phone won´t install "helmi_c´s SAP Test cab" ?
Can Cingular, which I don´t understand, help me ?
Fone: HERM200 Vodafone 1605 VPA compact III
Fone-ROM: 1.20.162.3
Car Kit: fwd audio com
Click to expand...
Click to collapse
Did you install the Fit4Cat tweaker? Have a play with the options in it - from what i can remember, theres an some options about being able to install non-signed apps and rights.
If that doesn't work ill have a look for you.
Churchill said:
I have a T-Mobile Vario II, and am looking into buying the Sony-Ericsson HCB-700 carcit. I have SAP settings in my programs, will it work ??
Click to expand...
Click to collapse
Depends entirely upon whether the HCB-700 uses rSAP or HFP (hands free profile) to connect to your vario....
If it uses rSAP then chances are it will work, but without having used your exact kit i can't say for definite i'm afraid.
-JD-

Thanx for the info

OK - I have tried to load the fit4cat tweaker to the c600 - it doesnt work - neither does my regedit software - so it requires more cunning.
With the M3100 I could not load the PHMRegedit - instead i used Vidya which seems to have worked.
The car kit I am trying to pair with is a mercedes MHI - it has worked with my Nokia 6230i up until now.
The regedit doesnt have a HEX function but converting 52 02 0C into DEC I get 5374476 - however looking at the original post it could be 5202C - which means 335916.
I have tried 335916 - and at first the car kit sees it - dials the long number in-order to pair with the phone - but then dies. after a few attempts the car kit stops to see the phone.
I have asked some colleagues to try this with their Bluetooth Passats - I will report back on this later.
Also I will now go and try 5374476.
With helmis test CAB - I only got on cab file after un-rar'ing it. is that OK? also is it the latest version of the file?
Thanks

p4uly said:
OK - I have tried to load the fit4cat tweaker to the c600 - it doesnt work - neither does my regedit software - so it requires more cunning.
With the M3100 I could not load the PHMRegedit - instead i used Vidya which seems to have worked.
The car kit I am trying to pair with is a mercedes MHI - it has worked with my Nokia 6230i up until now.
The regedit doesnt have a HEX function but converting 52 02 0C into DEC I get 5374476 - however looking at the original post it could be 5202C - which means 335916.
I have tried 335916 - and at first the car kit sees it - dials the long number in-order to pair with the phone - but then dies. after a few attempts the car kit stops to see the phone.
I have asked some colleagues to try this with their Bluetooth Passats - I will report back on this later.
Also I will now go and try 5374476.
With helmis test CAB - I only got on cab file after un-rar'ing it. is that OK? also is it the latest version of the file?
Thanks
Click to expand...
Click to collapse
The reason you wont be able to get PHMRegedit and Fit4Cat to work is the fact that you're on a c600 rather than an M3100....
Anyway...the dec you're looking for is (as you stated you were going to test) 5374476 so that one should work...
What you need to do now is have a forum search for unlocking the Extended ROM on the c600 and the follow the instructions from there.
You should get a .cab file and a folder from the unRAR...
Yes this is the latest version of the file and works fine
-JD-

Testing
Right - have tried with both DEC values for the bluetooth and they both seem to work. Good so far.
Further Good News - It works with the Passat Car Kit - excellent
However when it comes to pairing with the Mercedes device (essentially a bluetooth dongle that plugs into where the phone cradle normally goes) the phone does not respond to the Car Kit when it dials the pairing number.
So I guess I'll post this on Helmis thread and see if there are any more tweaks...

where can you get a cingullar ROM from? has it been tried on a Hermes 100?

any luck
did you have any luck finding out how to pair with the mercedes bluetooth dongle. I can get Comand to see the device but it does not pair.

Mercedes Car Kit Not Working
Sorry - the Mercedes MHI (European variant) does not want to pair!!
I have tried my phone - with the tweaks in a VW passatt Bluetooth car - and it works.
I have tried my phone with a BMW I drive - and it is fine.
It also works with the Audi Bluetooth and a Nokia and Parrott Bluetooth kit.
So Mercedes have done something very odd with their kit....
And whats more infuriating is that there seems to be no way of asking mercedes techncial questions without the answer "that phone is not shown as compatible in the list".
Currently I am using the phone in speaker phone mode and have a pay as you go sim in the car kit for outgoing calls.
Apparently the U.S. Version of the MHI dongle is different - but I have not found anyone out there who has tried this threads update on a U.S module.
Oh well - here's hoping Orange release a ROM update tht comes out to update the phone in the future.

thanks for your reply
Doing the same with my T-Mobile phone and using a pay as you go sim in the car.
Really annoying.

I can't get it to work with the new Audi system. Have an Audi Allroad manufactured 10/06 with the new PT4 telephone system and a HTC Tytn.
Pairing it with the handsfree profile works and I can make calls and access the contacts in the Tytn.
Pairing it with the SAP profile also works but I do not get any network and can´t access the contacts in the Tytn. Tried changing [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS]
"COD"=dword:52020C (hex) but I get the same results. Have not tried the other tweak since I already have "SAP Settings" under programs.
Any ideas about what to do?
UPDATE: Tried manual network selection from the car and was very surprised when my network "Vodafone Sweden" showed up as available and some other networks as not available. When I choose "Vodafone Sweden" it tries to connect and then says "Network error". Could it be a problem with SAP and Vodafone Sweden? Will try my wifes sim when she comes home.

please has anyone found a solution to pairing with a Mercedes device?

Sorry
Sorry - No..

Although your phone says it has SAP already the file atached on the first page of this thread is an upgrade to the Bluetooth Stack - so please try with the file (you can always remove it if it doesnt work).
Hopefully that should then work.
Are there any particular functions you want to use via SAP that you cannot do with Headset Profile??

When I tried another sim (Telia) it worked! Talked to Telenor/vodafone and they said I should ask the car or telephone manufacturer what type of sim I should have, Telenor/vodafone has several different sims.
I want to use SAP to get use of the outside antenna for better reception an no "radiation" (don´t know the word) inside the car. I also want to use the separate bluetooth handset that can´t be used when using handsfree profile.
Do you think the other bluetooth stack can help me get the contacts in the Audi phone?
Update: tried to install BTSAP_Test.cab manually but it says that installation failed since it doesn´t have enough authority in the system. Have mounted and unlocked extended rom with Fit4cat Hermes Tweaker and soft boot but it doesn´t work.

Prob to connect my Universal with Parrot 3200 LS color hands free

hi everybody
I have a problem to connect my Universal with my Parrot 3200LS color car hands free.
My Universal has a WM6 cooked Rom (FLA242 V1.0) with a Radio Rom 1.18. I had the same problem with the stock Orange Rom (main and radio), that's why i have upgraded to WM6, thinking it will resolved my problem....
Description of the problem : i turn on my car, the Parrot turn on and give me a pin code. The Universal ask me if i want to connect it in BT, i agree and input the pin code. That's ok, the Parrot download my contact and i can use the phone. When i come back later in my car, i turn on, the Parrot don't recognize my Universal and give me a new pin. Or it connect with my Universal and cut the link when i want to use it.
I precise that this Parrot turns perfectly with my previous smartphone (BlueAngel) and my wife's basic Nokia too.
Is there anybody who i have had the same problem ?
Is it a radio rom problem ? (i have the problem with my new one and the stock one !)
thank you for your answer