Can anyone point me to a method of pairing an Orbit (with Official O2 WM6 Upgrade) with a Mercedes Benz Bluetooth (SAP) car kit. Please? I have tried copying the BT SAP Test cab and run it successfully which appears to give rSAP (Sim Settings) but I cannot pair the device.
I can find the device, I can dial the long pairing code but I get no request to enter it on the Orbit. The car kit seems to then time out.
(I have had the same problem with a Graphite, a qtek9100... etc.)
Best answer might be to dump the car kit but I live in hope!
now this is the right place
Thanks!
Now that I have the correct thread - I don't suppose you have an answer
is there no place to set the SAP to authorised? in settings. I have installed A new rom
the Artimis touch rom and it has the SimSAP options in it
The problem is,
the old bt "mouse" of the MB cars was incompatible with the HTC telephones. We tried with several models and software revision but to no avail (Hermes, Wizard, Prophet and Artemis, WM5 and WM6).
The new "mouse" (now smaller and less looking like a telephone) works now w/o problems. This seems to be a MB bug and no HTC bug...
I hope I helped you
Segitz said:
The problem is,
the old bt "mouse" of the MB cars was incompatible with the HTC telephones. We tried with several models and software revision but to no avail (Hermes, Wizard, Prophet and Artemis, WM5 and WM6).
The new "mouse" (now smaller and less looking like a telephone) works now w/o problems. This seems to be a MB bug and no HTC bug...
I hope I helped you
Click to expand...
Click to collapse
Which MB BT model/mouse are you talking about? The SAP or HFP one?
Related
These stacks I believe are newer than the Widcomm 1.5.0 series
I think Broadcom reset the version 1.0.0
These are Broadcom 1.0.0.3000 and Broadcom 1.0.0.3500
Build 3500 is slightly unstable but newer.
These came from an i-mate patch for a PDA2K.
DO NOT USE on an i-mate PDA2K (get the orginal unhacked ones from Club i-mate).
I removed files specific to that phone and basically left just the BlueTooth stack.
Recommend a HARD RESET before installing.
I've tested theses patches on a Sprint PPC-6601 (Blue Angle CDMA phone).
Do not do a restore of a backup before or after installing this because it may restore incompatible configuration files that may crash. Build 3100 is more robust against this problem.
Hey Bro
These two are for the Qtek 9090/Xda IIs or Xda II?
I am running 2.20CHS translated with Radio 1.18 and have been unable to get this stack to work. Has anyone tried it?
The ones I posted above are hacked by me to work on the CDMA version (Namely Sprint PPC-6601).
The ones referenced in this reply below are the original patches I started with that came from i-mate club. The offical phone name that the patches are for is "i-mate™ PDA2k" (GSM Slide out keyboard). I don't know how well they would work on the Qtek 9090.
Build 3500 http://www.blueridge.net/dereck/bt/PDA2k_Bluetooth_Fix.CAB
Build 3000 http://www.blueridge.net/dereck/bt/new/OEM_WWE_122_008.sa.CAB
Yes, good link but already bad quality with all bluetooth headset.
It's a shame.
It's a shame you don't give more details.
Which phone, which patch and what happened.
Works great on my phone.
I'm using the 3100 patch from the first post in this thread on a PPC-6601 with a HBH-300. Installed on top of a HARD RESET. That has Build 1.0.0.2200.
It's almost working perfect. Once in a great while if I go out of range for a long time I just toggle bluetooth and it reconnects immediately.
Dial Up Networking and Active Sync all work.
No static. No dropouts. Will go to sleep and wake up and still be connected.
I think that the "shame" was not for you but for imate as their patch don't solve all the issues. Maybe only a bad english ?
Tried on Himalaya_SE 2.06...
I'd merged the files from 2.02 and 2.06 and get a fairly stable handsfree, but I saw your files and got greedy... :twisted:
hmmm, it didn't work though. The installation freeze at splash screen after i cold reset the device.
I believe that there are still device specific entries in the cab files, but it's beyond me at this moment. :?
yes sorry. Just bad english because i am french
This website is wonderfull and a lot of information
But i bought a qtek 9090 (850 euros) and i realize that they sell some device with a lot of bug
Here is my qtek config
qtek9090
Patch fr bt 3000 or 3500 (it's the same : they are bugs both for headset quality)
Windows mobile 2003 SE 4.21.1088 build 14132
rom 1.12.20 FRE
radio rom 1.02.00
ext rom 1.12.146 FRA
Ericson 300 works good but it's too big for me. I am not robocop
But each headset i have tested with bt 3000 and 3500 becomes bad when you stay more than 1 metter from your device. There is scrashesssssssssss in the headset. You have to stay front of the device (in car for exemple) and it works perfectly.
But when i work the pda stay in my bag or other place then quality is horrible
That's why i said it's a shame from imate.
I think there is a defect on this device. I don't know what can i do to increase the audio quality when you stay far from the PDA.
If somebody can help me ????????
But i can see that everybody have the same problem and can't solve it.
Waiting for another ROM. HIHIHIHIHIHIHI they are mad to sell this device like this.
If somebody can find bt 3500 patch from imate in french i am very interested.
Thanks to everybody from xda developer : a great site
yes sorry. Just bad english because i am french
This website is wonderfull and a lot of information
But i bought a qtek 9090 (850 euros) and i realize that they sell some device with a lot of bug
Here is my qtek config
qtek9090
Patch fr bt 3000 or 3500 (it's the same : they are bugs both for headset quality)
Windows mobile 2003 SE 4.21.1088 build 14132
rom 1.12.20 FRE
radio rom 1.02.00
ext rom 1.12.146 FRA
Ericson 300 works good but it's too big for me. I am not robocop
But each headset i have tested with bt 3000 and 3500 becomes bad when you stay more than 1 metter from your device. There is scrashesssssssssss in the headset. You have to stay front of the device (in car for exemple) and it works perfectly.
But when i work the pda stay in my bag or other place then quality is horrible
That's why i said it's a shame from imate.
I think there is a defect on this device. I don't know what can i do to increase the audio quality when you stay far from the PDA.
If somebody can help me ????????
But i can see that everybody have the same problem and can't solve it.
Waiting for another ROM. HIHIHIHIHIHIHI they are mad to sell this device like this.
If somebody can find bt 3500 patch from imate in french i am very interested.
Thanks to everybody from xda developer : a great site
Note that I attached to the first post of this thread Build 3500 release 124 of the i-mate patch stripped down for use on PPC-6601 and VZ6600.
BT problems
Just installed the 3500 fix.
It improves slightly on the Jabra 250, but not enough to actually use it.
It Stabilized the connection between my Holux GR230 GPS and the Qtek 9090.
Hope there will be a better fix.
Try to look at the connection, problem with the Jabra is that it fluktuate from just right to zero every other second.
Nice to pay 800 Euro for something that do not work :shock:
I've added new patches to this the start of this thread.
They work primarily on PPC-6601. Read the attached notes.
Hi mswlogo,
Can you help me if you know which version works on a win2003se translated from chinees on himalaya?
Thanks
That phone is quite different.
I think some other folks are working trying to get this stack working on other phones like yours.
Most of the patches above have registry scripts run in them that will very likely not work on your phone.
The other patches assume you are already running late version BroadComm Stack.
I have HP hx4700 and the Widcomm version is 1.5.0 Build 2000
which one is newest?
That's a really good question.
I'm amazed to see BroadComm on 1.5 instead of WidComm.
What are the dates on the bluetooth files \windows\bt*.*
They are generally around 12/9/2004
It's hard to say what BroadComm and the venders are doing here.
Bluetooth stack on h6315
I just found a new bluetooth stack from:
http://www.ppcw.net/?itemid=2210#cmt9543
Installed on my t-mobile h6315. Device was previously inoperable with bluetooth headset. Device would go into power standby mode, and if bluetooth was running when it went to sleep, it would freeze requiring a soft reset. Now device wakes on power button, with bluetooth running, as it's supposed to. Device also wakes on incoming call, reconnects headset in less than 1 second, and allows me to answer call on the headset buttons. All other headset functions are working as designed, and sound quality seems good. My headset is plantronics 2500. Also, this stack adds a profile in the list for A2DP (??) high quality stereo headphones. Don't have any of these headphones, so don't know if this works on the h6315. Also, don't know if this is the same Broadcom/Widcomm stack you guys have been working with.
Installation is straightforward - put it on the device and tap it. Reset, delete existing device pairings, re-establish the device pairings, and you're ready to test.
All that patch is supposed to do is add two new bt profiles to the pda2k.
* High-Quality Audio support (A2DP)
* Keyboard support (HID)
I'm slightly suprised you got a performance gain out of it.
h6315
It's definately fixed the problems with my device hanging when it goes into standby with bluetooth running and the headset connected.
Now my question is should I install the build 3500 for the 6315 listed above? It appears to be a newer release than this. Any thoughts as to the differences? I'm having a hard time following from the thread as to all the other changes that are in this .cab, and why they are there? Can any one help summarize that?
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.
Hi guys!
I have my Magician (QtekS100) for over a year now, and I've been always very happy with it. One of my best purchases ever.
It has never gave me any problem until recently when I decided to purchases a GPS Bluetooth (Nokia LD-3W) and my nightmare started.
After many days of trying things, turns out this GPS is a bit special and doesn't like all BT Drivers/Roms.
As the Normal MS drivers won't work and I have to use others.
In your opinio what is the best BT Stack software?
My magician currently is ROM 1.06.03 ESN, ExtROM 1.06.117ESN, Radio 1.05.00, Protocol 1137.39 with the Toshiba Drivers.
Should I upgrade it to a new ROM?
bchuertas said:
Hi guys!
I have my Magician (QtekS100) for over a year now, and I've been always very happy with it. One of my best purchases ever.
It has never gave me any problem until recently when I decided to purchases a GPS Bluetooth (Nokia LD-3W) and my nightmare started.
After many days of trying things, turns out this GPS is a bit special and doesn't like all BT Drivers/Roms.
As the Normal MS drivers won't work and I have to use others.
In your opinio what is the best BT Stack software?
My magician currently is ROM 1.06.03 ESN, ExtROM 1.06.117ESN, Radio 1.05.00, Protocol 1137.39 with the Toshiba Drivers.
Should I upgrade it to a new ROM?
Click to expand...
Click to collapse
new blue tooth stack isnt out yet.
the old bsch stack works fine.. has a few bugs..
the toshiba stack and the Bluesoleil stack is very buggy
cya
Bluesoleil wasn't buggy for me when used for wireless internet. What I didn't like was its incompatibility with my headset. And I'm not willing to switch every time so I returned to MS. I'd love to use the new BCHS stack, but noone's got it right now.
Btw: why did you just copy & paste? Please correct it, there are only BT stacks!
Btw2: please tell me the difference between "O2 MINI NEW BLUETOOTH STOCK" and "BT STACK(BCHS)" :lol: :lol: :lol:
Chatty said:
Btw: why did you just copy & paste? Please correct it, there are only BT stacks!
Click to expand...
Click to collapse
Yes, I did copy from the Subject on other posts.
As far as I know the correct word is Stack and Stock is just misspelled
Stack applies to any Implementation of networking protocols, not just bluetooth.
http://en.wikipedia.org/wiki/Protocol_stack
You just got to love the Wikipedia!!! :wink:
BT Tools is the solution (for me at least)
try "bluetooth tools" this was the solution for me when I had Magician. worked for me with several BT GPS units + TomTom 5.21 and Falk/MarcoPolo Navigator 2004-2005
http://bluetooth.i-networx.de/index_e.html
I did not have any problems with my GPS receiver with either of the stacks. And I do know what a stack is. That's why I asked you to correct the spelling mistake.
I use Bluesoleil and am half-way happy.
Unfortunatly I cannot use MS stack because after some time it gives me the error about "please turn flight mode first", even if it is off.
Anyone know how to fix this?
Re: BT Tools is the solution (for me at least)
aleksandr said:
try "bluetooth tools" this was the solution for me when I had Magician. worked for me with several BT GPS units + TomTom 5.21 and Falk/MarcoPolo Navigator 2004-2005
http://bluetooth.i-networx.de/index_e.html
Click to expand...
Click to collapse
does this support a2dp
re
best is windcomm (broadcomm)!!!!!!
who have working version for magician?
johancz
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.
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