Hey Guys, I've been following the cool stuff on this site for some time. It's always appreciated to have people working this stuff out. The default ROM that came with my Verizon (Harrier) is crap compared to the Testra ROM I got from this site.
Anyways, the reason for my post is in regards to setting up the Harrier as a DUN Client to a BT DUN enabled phone.
I have BT DUN working from the phone to a PC so I know it works.
When I browse the available services on the phone from the PC I see bluetooth serial port and bluetooth DUN.
When I browse the available services on the phone from within the Bluetooth manager on the Harrier the only available service I see available is Bluetooth Serial Port.
I tried setting up a 'Connection' using the Bluetooth serial port to no avail.
Has anyone had any success with BT DUN out from WM 2003SE using
BT ROM 1.0.0 Build 3500? or with any other similar setup?
Any suggestions?
Thx,
Ian
1. Copy this file "BTWizardProfiles.dll" to IIs
2. Modified Registry in following:
[HKEY_LOCAL_MACHINE\ExtModems\bluetooth_dun]
"port"="COM7:"
"DeviceType"=dword:00000009
"FriendlyName"="Bluetooth"
iroessle said:
Hey Guys, I've been following the cool stuff on this site for some time. It's always appreciated to have people working this stuff out. The default ROM that came with my Verizon (Harrier) is crap compared to the Testra ROM I got from this site.
Anyways, the reason for my post is in regards to setting up the Harrier as a DUN Client to a BT DUN enabled phone.
I have BT DUN working from the phone to a PC so I know it works.
When I browse the available services on the phone from the PC I see bluetooth serial port and bluetooth DUN.
When I browse the available services on the phone from within the Bluetooth manager on the Harrier the only available service I see available is Bluetooth Serial Port.
I tried setting up a 'Connection' using the Bluetooth serial port to no avail.
Has anyone had any success with BT DUN out from WM 2003SE using
BT ROM 1.0.0 Build 3500? or with any other similar setup?
Any suggestions?
Thx,
Ian
Click to expand...
Click to collapse
Woot, It's working
Just wanted to say thx for the inf.
Thanks for the inf,
Ian
Hello,
in a few weeks I'll get my new Ford car - equipped with the built-in bluetooth handsfree device. I tried to connect my MDA 3 to this device at several Ford dealers but didn't get any connection.
The MDA finds a "Ford Audio" but can't establish a connection.
Who has any ideas ?
Thanks in advance - Dieter
I have the same problem with a new mondeo...
Everything works with an old nokia 6630 (with a small nokia application I can browse the phonebook as well) but I'm not able to pair the bluetooth ford audio system with my HTC TyTN...
Any ideas?
try using a newer bluetooth stack.
What is a bluetooth 'stack' ?
And how do I change to a newer one?
nfumbruce said:
And how do I change to a newer one?
Click to expand...
Click to collapse
As far as I know, you'll need to update the Radio portion of your device's ROM based software (the basic software that drives the device).
The best bet in your case I believe would be to just grab a new complete update for your device by searching the wiki for downloads for your device. Download a newer official ROM, install it and try again.
You will lose all saved data on the device though so back it up>
Wiki is here http://wiki.xda-developers.com/
Did upgrading the bluetooth stack fix this connectivity issue to Ford Audio Bluetooth Handsfree devices?
Same problem. I've tried to upgrade bluetooth stack: my BA finds "Ford Audio" but doesn't connect. Please give us some help
bicasper said:
Same problem. I've tried to upgrade bluetooth stack: my BA finds "Ford Audio" but doesn't connect. Please give us some help
Click to expand...
Click to collapse
after correct pairing (code 0000), press "Phone" on the caraudio system and then "Menu". After that press left or right joypad on the caraudio to set the "Active Phone". It will search and your phone will be correctly paired.
The last paired phone will be automatically active when you turn on the caraudio system next time.
In some cases will also help to install on the device the JETware application... just try.
Problem Solved!
Thank you dark horse, followed your advice and it worked just fine. I can now connect via bluetooh in my ford.
Can't connect to new Ford Fiesta
Hello to everyone.
I just bought my new Ford Fiesta and I try to connect it with my Sony ARC S but I can't procced with the opperation. I search for new devise on sony, I find the Ford Audio and ask to connect, the Fiesta get it and provide me with the 4 digit code but, my sony doesn't open any keybord in order to write this code to connect so the after few seconds the car regect the connections.
My phone is ARC S LT18i and I had upgrade it to Android 4.0.3
Please any advice will be helpful,
Thanks in advance.
omg nice on there!!!
Thank you dark horse, i had the same problem!!
OX Mobile Spy
The best bet in your case I believe would be to just grab a new complete update for your device by searching the wiki for downloads for your device. Download a newer official ROM, install it and try again.
I have connected the TyTn to the car hansfree (Parrot) without problems.
The only problem is that I have to confirm the connection each time I want to use the hansfree and I have to introduce the password, etc.
In WM5 there was the possibility of adding trust devices to avoid confirming the connection each time. Is it not possible in WM6?
Thanks!!!!
I think it might be a problem on your end and not of the rom. I have synced up my 8525 with my friends bmw and had no problems at all. none at all. so you might need to reflash or check your stuff.
It works very well with my Acura TL handsfree so it may be a problem at your end.
Shamim
jaimedevesa said:
I have connected the TyTn to the car hansfree (Parrot) without problems.
The only problem is that I have to confirm the connection each time I want to use the hansfree and I have to introduce the password, etc.
Click to expand...
Click to collapse
Password or passkey ? I suspect you did not pair your device correctly. "Comm Manager" - Settings - Bluetooth Settings. Do you see your Parrot device in the list ? If yes - try to delete it and re-add it.
Has anyone had any luck with using their Hermes in a Ford, using their 'Advanced Bluetooth' car kit?
I have paired my MDA Vario II, running Schaps 3.60 WM6, with my new Ford Focus. This shows up as 'Ford Audio' on my phone. Incoming calls are now routed through the car stereo, and I can access my voice tags for outgoing calls by saying 'Mobile, Name'. So far so good!
The issue though, is with the Sim Access Protocol (SAP) routine. I have managed to access the phone contacts list just once, and that was after a wait of over 30 mins. I have never seen the list of recent or dialled calls. So all incoming calls show as just raw numbers, rather than names.
I have ensured that I transferred my main contacts to my Sim Card. I made sure that SAP was selected. I even downloaded and installed the Jetware SAP enhancement program. All to no avail.
Has anyone got SAP running, speedily, with a car kit?
Dont kno how much use this is going to be, but try using the rom Black Majic by JasJamming.
That is the only rom ive ever got to work properly with my Parrot 3200LS Car Kit.
I have a Focus ST with the advanced bluetooth car kit and have been able to access my contacts list when using Sleuth's ROM - but not the recent call list etc. I did not need to move my contacts to the SIM to get that though.
I've recently switched to FunKey's 3.62 ROM and while the car kit works for audio etc. I no longer get the contacts - having said that I haven't installed the BT SAP cab so no real surprises there.
To be honest I'm just glad the car kit works for audio - I've always had problems with the Tytn and car kits so it's very nice that it works at all
Thanks, jaso2005 and forza, for your comments. I think that WM6 has got a way to go to catch up even with Symbian, as far as car kits and SAP is concerned.
From your posts, it would seem that some ROMs are getting there.
I see that Shap's latest (4.00 Beta 2) contains the latest SAP utility and, as I am running his 3.60 ROM at the moment, I think I will wait for the 4.00 final release.
Schaps is just requesting people try his new beta ROM that has this feature.
Just throught I would add my name to the list of people having problems getting their Hermes to work with their Ford bluetooth carkit....
I've got my new s-max, but have not been able to get the phone work work with it. I can discover the car from the phone (ford audio) and pair it up. However, when I go to make a call, the phone does not think there is a carkit present. Also, if I go to the carkit setting on the ford computer it says it can't see a phone connected.
Hissing Syd & Forza, did you do anything special to get yours to work with the advance bluetooth? I've tried a couple of different ROMs and am now running Schaps 3.6a (have also tried 4)
thx
caspartfg said:
Just throught I would add my name to the list of people having problems getting their Hermes to work with their Ford bluetooth carkit....
I've got my new s-max, but have not been able to get the phone work work with it. I can discover the car from the phone (ford audio) and pair it up. However, when I go to make a call, the phone does not think there is a carkit present. Also, if I go to the carkit setting on the ford computer it says it can't see a phone connected.
Hissing Syd & Forza, did you do anything special to get yours to work with the advance bluetooth? I've tried a couple of different ROMs and am now running Schaps 3.6a (have also tried 4)
thx
Click to expand...
Click to collapse
I had the same problem with mine initially. The handbook says that you merely have to pair the phone, which you have done. Not true - you have to physicaly make your Hermes the 'Active Phone'. First, select Phone. Then press Menu. Then scroll to Select Active Phone, let it find your Hermes, select it, and it should work.
The selection of Active Phone is covered later in the handbook. It should be at the start.
Good luck!
Syd,
you'll love this, but the dealer forgot to put the bluetooth manual in the glove box. (I'm waiting for it come come through...) In the mean time, any chance of giving me some instructions on how to setup an active phone?
Thx
caspartfg - Have you activated the Bluetooth SAP?
In Schaps latest rom's 3.60a and 4.00 Beta this is in Programs > System Tools > SAP Settings
yes, I have tried with the SAP setting turned on and off. The problem I have is that the car cannot see the phone, even though it is paired.
Also, the phone does not attempt to make use of the handsfree when I make a call.
Thank you all for your suggested
C.
Make sure you have ticked the option to make the phone discoverable (Start/Settings/Connections/Bluetooth - Mode tab; "Make this device visible to other devices")
Hissing Syd is spot on - you do have to select it after the pairing. When I do mine, I delete any existing pairings on both the car and the phone. Soft reset the phone, turn the car radio off and then on. Then (with the radio switched on) search for bluetooth devices on the phone, pair with the "Ford Audio" service. Turn the radio off and then on, press Phone, press Menu, scroll to Select Active phone and press the centre button on Phone1. It can take a few minutes to finally pair up, but it does get there in the end!
I've turned on SAP on the FunKey ROM but still don't get contacts etc. coming through on the car kit - but as I said I'm not that bothered to be honest!
caspartfg said:
yes, I have tried with the SAP setting turned on and off. The problem I have is that the car cannot see the phone, even though it is paired.
Also, the phone does not attempt to make use of the handsfree when I make a call.
Thank you all for your suggested
C.
Click to expand...
Click to collapse
Thank all, just to let you know the phone is working with the carkit.
I've been able to make / receive calls. I have also been able to browse the contact list on my phone via the info on my convers+ dash. Also when calls come in, they show the name of the caller.
I'll do some more testing when I get the manual through, but all of the functions the carkit provides seem to be supported. I've also been able to make voice dialiing features of the car..
I love the fact you can talk to the ford and instruct it around the phone, radio, climate control, etc....... feels like a middle age version of knight rider.....
Thx all
C.
Having the same problem with an Orbit (Artemis)
caspartfg,
I'm having exactly the same problem with my Artiemis - have put something in that Forum but no reply yet
http://forum.xda-developers.com/showthread.php?t=340609
Also - what Bluetooth manual ! The standard mondeo manual has some info but not much. Am I missing the bluetooth manual as well?
jftilbury,
Took quite a bit of fiddling around, but got there in the end....
Which head-unit do you have? - Mine is the Sony version that comes with the new s-max titanium.
To answer your specific questions:
1) yes, there was a separate bluetooth manual. I had to ring the dealer and he posted me a copy
2) The thing the car manual didn't tell me about was that there is a second step to the pairing of the phone in which you need to active the phone in the head unit.
i) make sure the phone is discoverable in bluetooth
ii) pair the phone with head unit as you described above.
iii) select the phone setting on the head unit
iv) press 'menu' (I think) and then in one of the options you can set the phone to active
after that, it all worked a treat for me..... Let me know if this works for you. If my instructions are dodgy, I'll double check
Spot on !
Excellent, that worked a treat. I also have the Sony CD unit, but in the Mondeo, and it is now phoning anyone that will pick up the phone.
The phone book is now going across OK. My problem is that as my company's entire phone book gets sync'ed onto the XDA I now have around 500 numbers on the car menu making it unusable. Never mind, the phone works which is the main thing.
Voice recognition next...
Thanks for your help, I'll point the other thread here as well.
jftilbury said:
Excellent, that worked a treat. I also have the Sony CD unit, but in the Mondeo, and it is now phoning anyone that will pick up the phone.
The phone book is now going across OK. My problem is that as my company's entire phone book gets sync'ed onto the XDA I now have around 500 numbers on the car menu making it unusable. Never mind, the phone works which is the main thing.
Voice recognition next...
Thanks for your help, I'll point the other thread here as well.
Click to expand...
Click to collapse
I'm pleased that we helped solve your problem. My question to you, which ROM are you using? I still have problems with uploading the phone book to the Sony unit with my Schaps 3.60a ROM.
ROM version
I am using the standard ROM downloaded from the O2 support site at:
http://xda.o2.co.uk/xdaOrbitSoftware.html
This sends the download to the HTC site, with the file name:
RUU_Artemis_O2_UK_3.4.206.2_4.1.13.28_02.67.90_Ship.exe
The numbers I can find are:
CE OS 5.2.1238 (Build 17745.0.2.3)
ROM version: 3.4.206.2 WWE
ROM date: 4/18/07
Radio version: 02.67.90
Protocol version: 4.1.13.28
ExtROM 3.4.206.101
Not sure if this helps as it is for the Artemis.
Hissing Syd said:
I'm pleased that we helped solve your problem. My question to you, which ROM are you using? I still have problems with uploading the phone book to the Sony unit with my Schaps 3.60a ROM.
Click to expand...
Click to collapse
I am using Schaps 3.6a... The extra piece I did was to go into the advanced config, bluetooth tab and turn on OBEX. You should also make sure Remote SIM access is turned on in the SAP application.
Hope this helps, worked for me......
C.
Mine in fact worked too well - sending across all 500 numbers my company sync's onto my handset, making the phonebook unusable on the car.
However a Ford forum put me onto this bit of code:
http://www.jetwaremobile.com/
which does exactly what I want allowing me to create a category of people I want to appear in the car phonebook and away we go.
caspartfg said:
I am using Schaps 3.6a... The extra piece I did was to go into the advanced config, bluetooth tab and turn on OBEX. You should also make sure Remote SIM access is turned on in the SAP application.
Hope this helps, worked for me......
C.
Click to expand...
Click to collapse
Thanks very much for that crucial bit of info. Since I started this thread, I have changed ROM to RUU_Hermes_TMO_UK_3.60.110.4_6275_1.50.00.00_108_Ship.exe and, by enabling OBEX, it all works a treat.
I currently have a Diamond and TP2 with stock ROM's.
Diamond worked perfect with carkit untill i performed major ROM upgrade from htc.com. now it will connect and not reconnect on either device or carkit restart.
My TP2 behaves EXACTLY the same - connects and drops after either restarting. when connected it works fine - voice/dialing etc etc.
My car kit is a JVC KS-BTA200 connected to my KW-AVX810 head unit.
i've read all comments on google/xda's etc - well almost all! to no avail.
the devices are all set to visible obviously and all paired. ive read that a registry edit possibly fixes the issue but my TP2 & Diamond dont have the required reg strings. (that i can find!!)
i have the remote registry tool installed on my Desktop - so im ready to make changes!
please, if anyone can help i will very grateful!!
radak23 said:
I currently have a Diamond and TP2 with stock ROM's.
Diamond worked perfect with carkit untill i performed major ROM upgrade from htc.com. now it will connect and not reconnect on either device or carkit restart.
My TP2 behaves EXACTLY the same - connects and drops after either restarting. when connected it works fine - voice/dialing etc etc.
My car kit is a JVC KS-BTA200 connected to my KW-AVX810 head unit.
i've read all comments on google/xda's etc - well almost all! to no avail.
the devices are all set to visible obviously and all paired. ive read that a registry edit possibly fixes the issue but my TP2 & Diamond dont have the required reg strings. (that i can find!!)
i have the remote registry tool installed on my Desktop - so im ready to make changes!
please, if anyone can help i will very grateful!!
Click to expand...
Click to collapse
Hi, I am using my Touch Pro 2 with the same HU and Bluetooth adaptor as you but no such problem so far.
It used to have this problem then I try to connect using Window CE as the phone setup and choose another Connection Key instead of default 0000 to pair the phone with the HU.
ok, well i just tried connecting via searching for the device from the HU. it finds my device - i tap enter (to connect on HU) then it just jumps to a blue flashing 'connecting' then goes to a yellow 'error' straight away. if i select 'open' on the HU then it connects (connecting with a different ID - a number '6') but only untill i restart the HU.
also as a test i just tried an Xperia (just had one laying around LOL) and it does the exact same as mine!! ARRRRGHHH!
so im glad to say i believe it is not an HTC issue!
ok so i have an update - the problem is my HU will not pair correctly and it will not store a pairing. great.
another quick one - have found others are having trouble with their HU/adapters. thanks anyway everyone!
TP2 Bluetooth and voice dialing working fine ???
Have you tried to reset your carkit? I had the same problem after the rom-update with my TP1 and I put my carkit (Bury CC9060) back to factory settings. So I did the same this morning after I updated my TP2 and now it works just like a charm. Of course I don't know if your carkit has this possibility. Good luck, greetz Ton
'iznogoooog' - yes it work perfectly until you restart either device - 'ton66' - unfortunatley a reset is pretty much all i can do!!! eeeeek!
hopefully a reset will fix it! - i did unplug my b/tooth adapter then switch the unit on - then off then plug it back in.. didnt change anything.. oh well! will do complete re-set 2day!
BTW:
thanks so much for everyones help!
Got a questions. I am using the AVX-826 with build in Bluetooh. I want to know if you guys get the Signal Strength show on your Head unit is correct. on my unit pair with TP2. The Signal Strength indicator doesn't move. it always show the strength with my phone is connected to the unit and it stay that way.
The Battery Strength indicator does work and show the correct battery level.
I have exactly the same prob!
Hi,
I have a AXV800 and a BTA200.
My first device was a Artemis with WM6.0. No problem so far!
Then I changend to a Diamond with WM 6.1 and had the same problem as mentioned before. Now I tried my new TP2 and still the same problem.
And I tried the old Artemis again with a new 6.1 ROM and the same problem as on the other two phones.
Now I think it depends on the WM build. 6.0 seems to work 6.1 not!!!!!!!!!!
I did a reset on my AVX800 two times without luck!
I think I'm going to use a normal phone without Windows mobile for the next test!
Schelbi.