Related
I don't know if anyone has noticed... but the new ROM version (1.72 + radio 14) has actually improved concerning serial bluetooth connections -- especially on my BT GPS.
Now when I bond with it, it asks me if I want to use the serial profile. I say yes, and it uses COM 5 for my BT GPS. All works fine. No need to use the Blueooth tools software that was needed before.
So this is actually an improvement, but hard to notice unless one tries "the old fashioned way" with BT GPS.
Works like a charm......
I have not tried it with BT GPS, but looking at what everyone else went through with their Headsets and bonding issues, I can defintiely attest to the fact that the new BT Stack on 1.72WWE works great! I have never had to re-pair my Jabra BT 250 since I paired it the first time two weeks ago. I have also been able to ActiveSync over BT without any problems.
Lucky u guys, when i did the update, i cant active sync through BT
first_major:
Try this attached document and see if it helps.
sheran_g,
Thaks alot, all i was missing was to do the active sync profile, your document helped me.
Thaks again
(some) GPS problems with 1.72 (and 1.66)
Victor said:
I don't know if anyone has noticed... but the new ROM version (1.72 + radio 14) has actually improved concerning serial bluetooth connections -- especially on my BT GPS.
Now when I bond with it, it asks me if I want to use the serial profile. I say yes, and it uses COM 5 for my BT GPS. All works fine. No need to use the Blueooth tools software that was needed before.
So this is actually an improvement, but hard to notice unless one tries "the old fashioned way" with BT GPS.
Works like a charm......
Click to expand...
Click to collapse
I have noticed the added WM function for BT GPS on COM5 (already with 1.66), however 'since' 1.66 I can not get my BT GPS to work with Alturion.
The strange things are:
- At first it still worked with 1.66 but a week after it failed and Alturion and I can not get it working since (incl. 1.72 upgrade).
- if I start Alturion the blue GPS LED starts flashing fast (green LED indicates satelite lock) which suggests BT connection, but still it says "NO GPS FOUND" all the time!
- With TT3 the GPS is working ok (with BT and serial profiles)
I dare not to hope, but if anybody has an idea please let me know. I prefer not to downgrade to 1.60 since I see many issues with this downgrade on this forum.
Victor said:
..... I say yes .....
.... unless one tries "the old fashioned way" with BT GPS.
Click to expand...
Click to collapse
I can not remember that NO was an option. Do you mean this with the old fashion way???
Ronald
Hi guys
I'm guessing that the 1.7 upgrade is not avalable in Australia??? I cannot find it on the MyXDA website for download? is this update that you are talking about not for Australia/Asia?
Cheers...
sheran_g said:
first_major:
Try this attached document and see if it helps.
Click to expand...
Click to collapse
dude the filedoesnt work, can u upload it again?
Smiley
smiley_thing69 said:
sheran_g said:
first_major:
Try this attached document and see if it helps.
Click to expand...
Click to collapse
dude the filedoesnt work, can u upload it again?
Smiley
Click to expand...
Click to collapse
You might need to download Adobe Acrobat Reader in order to view the file. You can find the Acrobat Reader here.
dont try dow view the file in IE
Download it first and THEN view it
This works for me
smiley_thing69 said:
sheran_g said:
first_major:
Try this attached document and see if it helps.
Click to expand...
Click to collapse
dude the filedoesnt work, can u upload it again?
Smiley
Click to expand...
Click to collapse
With gozilla I can also not download the pdf, but with "save target as" it works.
@sheran_g
BTW Thanx for the post
Re: (some) GPS problems with 1.72 (and 1.66)
ronald2oo2 said:
I have noticed the added WM function for BT GPS on COM5 (already with 1.66), however 'since' 1.66 I can not get my BT GPS to work with Alturion.
The strange things are:
- At first it still worked with 1.66 but a week after it failed and Alturion and I can not get it working since (incl. 1.72 upgrade).
- if I start Alturion the blue GPS LED starts flashing fast (green LED indicates satelite lock) which suggests BT connection, but still it says "NO GPS FOUND" all the time!
- With TT3 the GPS is working ok (with BT and serial profiles)
I dare not to hope, but if anybody has an idea please let me know. I prefer not to downgrade to 1.60 since I see many issues with this downgrade on this forum.
Click to expand...
Click to collapse
Are you sure this isn't TomTom's GPS Driver causing this? TT's GPS Drivers since v2.08 have locked the BT Com Port for exclusive access by TomTom and this prevents other apps from accessing a BT GPS. Solutions are either install v2.07 which was the last driver that did not do this or remove 'the Tomtom~GPS' entry which is the culprit, removing this removes the BT Com Port lock but does not affect the use of TomTom.
@ griffog
Actually I use TomTom ~GPS 3.03 which does not have this problem anymore! Anyhow I still (temporarely) remove the TomTom ~GPS driver and soft-reset when I test with Alturion.
But thanx for the tip.
BTW it does effect the use of TomTom for me! I guess you have a serial (non BT) GPS !?
Ronald
No I use BT GPS unit's exclusively. I'll have to investigate this as I have not heard that v3.03 no longer has this problem!
@griffog
I have this information from the Dutch PocketPC-club TT forum.
It is also consistent with what I see since the TT3.03 upgrade, even while my other GPS application (Alturion) is not working. If I run TT GPS and close it and then start Alturion the Blue LED of the GPS starts flashing fast (sadly I still get "no GPS found" however).
Ronald
:wink: remember you heard it first from me, the Premier GPS Resource :wink:
Excellent news! I've just loaded it up to test and you were right It's such good news that I've posted a front page news item, thanks
Indeed it was very good news.... but therefor also more disappointing for me that I don't get Alturion -my second GPS application- to work (on the eve of my holidays).
If you also use Alturion 5.3.1.4 (you seem in to GPS), can you share your configuration with me?
OS (1.66+?)?, BTHTools or WM serial BT profile? GPS? GPS config in Alturion? and anything else you might consider important.
I really need some new straws to grasp because I have no more ideas about what to try.
Ronald
Sadly Alturion hasn't made it across the channel. I'ce contacted them on numerous occasions for a review copy but never received a reply.
Another cool fix is the fact that you can now be connected through Activesinc using the cradle and at the same time now you can receive MMSs without a problem.
Before the 1.72 upgrade, you just couln't do that. :wink:
Hi there I'am new here.... seached the forum and google a lot but didn't find an answer...
Just flashed from XDALive 2.0 to Black 2.0, radio 1.38.00.10 and HardSPL v6 with help of the manual of mrvanx.
My problem with the rom of XDALive 2.0 was that TomTom 6 keep hanging serveral time. The headset (bluetooth build in CAR, peugeot 207) was working perfectly. After the upgrade to Black 2.0 the TomTom problem was solved , it works perfectly now. The only what came up was the bluetooth headset probleem. The connection is ok but I don't hear any sound??
Flashed back radio ROM to 1.35 no results...
Found something interesting...
When its not connect with the carkit, turn on bluetooth, dail a numbers and turn on the Speaker, it will eventually connect to the carkit automaticly (and I got sound thourgh the carkit!
When searching for bluetooth devices it will find the headset and the carkit goes into 'calling mode'. When dailing a contact directly after that the carkit will work. But the next try it will mute the radio but doesn't give any sound on the carkit.
When allready connected with bluetooth on the carkit it wont give any sound thourgh it.... strange.. Tried serveral other ROMS but they are giving me the same problem...
Widcomm BT Stack (http://forum.xda-developers.com/showpost.php?p=1072773&postcount=72) also tried, didn't help... anyone some suggestions?
PS.: My old nokia still works, it can't be the carkit..
Question for you. after you setup your carkit do you go into the bluetooth and set it to your handsfree device. There seams to be a few changes to the way WM6 chooses the handsfree device if you have several set up.
I have to change in WM6 bluetooth which headset I am using when I switch between the 3 headset I have. I have to go to Start\Settings\Connections\Bluetooth Click/Hold on my headset that I want to make active - you will get a Menu wit Edit/Delete/Set as Hands-free/Set as Wireless Stereo (last should be grayed out if it doesn't support Strereo)
Choose Set as Hands-free
After doing this my headset works fine. Try it and see if it works for you.
jcb_home said:
Question for you. after you setup your carkit do you go into the bluetooth and set it to your handsfree device. There seams to be a few changes to the way WM6 chooses the handsfree device if you have several set up.
I have to change in WM6 bluetooth which headset I am using when I switch between the 3 headset I have. I have to go to Start\Settings\Connections\Bluetooth Click/Hold on my headset that I want to make active - you will get a Menu wit Edit/Delete/Set as Hands-free/Set as Wireless Stereo (last should be grayed out if it doesn't support Strereo)
Choose Set as Hands-free
After doing this my headset works fine. Try it and see if it works for you.
Click to expand...
Click to collapse
When searching for a new bluetooth device WM6 sees a headset and the connection is successful. The 'Set has headset' is availible and is set. The option Wireless Stereo isn't support I think, its not availible as an option.
When calling you can turn on/off your headset back to the phone. That works but there is still no sound on the headset.
balck 2.0 does have issues. i also have same with motorola hs850.
only just found out. havent fixed.
bt connects as phone pad shows it.
headset bleeps on connect call and disconnect call. but no sound is sent or received.
always set to headset though not hands free.
will have to test further but definitely an issue. i didnt ask jj out of respect for his withdrawl of support.
I don't think it a problem with Black 2.0. Too many people say it works no problem.
I'm on black and all three of my head sets work like a charm. I have 2 Motos an H810 and a H700 and an Plantronics 510. I also have been able to use internet sharing, BT file transfer, and BT sync with Black 2.0
But it could be an incompatability between the WM6 M$ BT stack and your hands free kits.
Test your phones with another BT device and see what you get.
Same problem with HS850
simon_darley said:
balck 2.0 does have issues. i also have same with motorola hs850.
only just found out. havent fixed.
bt connects as phone pad shows it.
headset bleeps on connect call and disconnect call. but no sound is sent or received.
always set to headset though not hands free.
will have to test further but definitely an issue. i didnt ask jj out of respect for his withdrawl of support.
Click to expand...
Click to collapse
I have exactly the same problem, and I didn't solved yet....but I've found this bypass:
When the phone rings I answer with the bluetooth handset and receive the beeb on connect call.....then I close the BT headset and as soon as I re-open it, I have the headset working.....I have to do this for every incoming or outgoing call.
My BT headset was working well with the black 1.2.
This is the only issue I've found in the black 2.0.....I think is the most stable and fast rom.
Bye prengo.
jcb_home said:
I don't think it a problem with Black 2.0. Too many people say it works no problem.
I'm on black and all three of my head sets work like a charm. I have 2 Motos an H810 and a H700 and an Plantronics 510. I also have been able to use internet sharing, BT file transfer, and BT sync with Black 2.0
But it could be an incompatability between the WM6 M$ BT stack and your hands free kits.
Test your phones with another BT device and see what you get.
Click to expand...
Click to collapse
My other Bluetooth devices are working fine. My bluetooth GPS receiver works just fine with TomTom... no issues there.
Just flashed back to XDA-Live (v0.20.1) and the headset works without any problem.
Only thing now is Tom Tom 6 hangs directly after the start of it. Anyone familiar with this issue?
thx
PS.: what is the differance between the Black 2.0 and XDA-Live (v0.20.1) ? other bluetooth driver versions besides the os version? Maybe there is a way to combine..?
A common thread seems to be the HS850
I have the exact same problem with my HS850. I get the call connect beeps but no sounds come through. The issue exists if the headset is connected when the call is made. If I make the call, then flip the boom and turn the headset on, then I get sounds no problem.
I had this issue with both LVSW 4-08 and Black 2.0. I eventually went back to XDA Live 0.20.1 and my BT issues all went away.
cruzer said:
PS.: what is the differance between the Black 2.0 and XDA-Live (v0.20.1) ? other bluetooth driver versions besides the os version? Maybe there is a way to combine..?
Click to expand...
Click to collapse
WMXL .20 is based on a beta WM6 build and Black 2.0 is built on an RTM build (non-beta)
With Moto HS850 too.
edwinyuen said:
I have the exact same problem with my HS850. I get the call connect beeps but no sounds come through. The issue exists if the headset is connected when the call is made. If I make the call, then flip the boom and turn the headset on, then I get sounds no problem.
I had this issue with both LVSW 4-08 and Black 2.0. I eventually went back to XDA Live 0.20.1 and my BT issues all went away.
Click to expand...
Click to collapse
Exactly the same here with HS850. Tried everything after 20070320_RUU_Hermes_WWE_3.23.0.0_1.34.00.10.exe but kept getting no sound.
I have experienced the same problem with my 407 hands free system. My Orange SPV C600 works without a problem, it does not show signal strength and battery level though. Using my M3100 with any of the following listed below works perfectly:
HTC English QTEK_001 2.11.255.1 03/07/07 2.11.255.102 1.38.00.10 32.71.7020.12H OS 15673.3.3.1 AKU 3.3.1
Cingular English CWS__001 2.15.502.3 04/09/07 ?? 1.40.30.00 32.73.7020.16H OS 15706.3.5.2 AKU 3.5.2
XDA-Live (v0.20.1) English 3.22.110.1 01/04/07 None None 5.1.195 (WM6) OS 17217.6.0.0
I have found all the above roms work perfectly with my TomTom 6.030 software. I am currently using Black Version 2, I have also used LVSW roms and found the same issue with any running the OS 17736.0.2.0
mike6502 said:
I have experienced the same problem with my 407 hands free system. My Orange SPV C600 works without a problem, it does not show signal strength and battery level though. Using my M3100 with any of the following listed below works perfectly:
HTC English QTEK_001 2.11.255.1 03/07/07 2.11.255.102 1.38.00.10 32.71.7020.12H OS 15673.3.3.1 AKU 3.3.1
Cingular English CWS__001 2.15.502.3 04/09/07 ?? 1.40.30.00 32.73.7020.16H OS 15706.3.5.2 AKU 3.5.2
XDA-Live (v0.20.1) English 3.22.110.1 01/04/07 None None 5.1.195 (WM6) OS 17217.6.0.0
I have found all the above roms work perfectly with my TomTom 6.030 software. I am currently using Black Version 2, I have also used LVSW roms and found the same issue with any running the OS 17736.0.2.0
Click to expand...
Click to collapse
It's great that you tracked this down so specifically. I guess this means for those of us with these issues, we have to avoid newer WM6 builds until someone looks into this.
idee2000 said:
Exactly the same here with HS850. Tried everything after 20070320_RUU_Hermes_WWE_3.23.0.0_1.34.00.10.exe but kept getting no sound.
Click to expand...
Click to collapse
Can't just be the ROM as my HS850 works perfectly with Black Pro 2.0
rabdo said:
Can't just be the ROM as my HS850 works perfectly with Black Pro 2.0
Click to expand...
Click to collapse
I have the same problem as the others with my HS850. No audio if the headset is on when a call is made or received but if I close the boom and re-open it, viola it works again.
I did have a problem with HTweakC where I changed the A2DP setting to on and now no matter what I do I can't get it off again. I might re-flash and see if that helps.
I don't know if it matters but I have MS voice command on my phone, even though the MSVC16BThack doesn't work anymore. (my phone is an 8525) Hope someone can figure this out, I really like the speed and stability of this ROM but if I can't get my BT to work I'm going to have to downgrade.
AdamsJourney said:
I have the same problem as the others with my HS850. No audio if the headset is on when a call is made or received but if I close the boom and re-open it, viola it works again.
I did have a problem with HTweakC where I changed the A2DP setting to on and now no matter what I do I can't get it off again. I might re-flash and see if that helps.
I don't know if it matters but I have MS voice command on my phone, even though the MSVC16BThack doesn't work anymore. (my phone is an 8525) Hope someone can figure this out, I really like the speed and stability of this ROM but if I can't get my BT to work I'm going to have to downgrade.
Click to expand...
Click to collapse
I am using Cyberon Voice Commander v2 - maybe that is why it is working for me
Hi,
I am using radio rom 1.40.30 and Black 2.0.
I am using H700 BT headset
the problem i face are opposite from you all.
If i am already talking halfway and i flip the boom to continue talking with the BT headset...it won't work.
if i receive a call and I flip the boom while the phone rings, it is ok and i can even press the button on the h700 to answer the call.
Radio 1.40.30 seems to connect with the BT headset much faster.
last time when i was using my previous default factory rom, when i flip the boom while the phone is ringing, it will take ages to connect
why not u guys try radio rom 1.40.30 also
rabdo said:
I am using Cyberon Voice Commander v2 - maybe that is why it is working for me
Click to expand...
Click to collapse
I did a hard reset, paired the headset, and tried it right away and still had the issue so it's not VC 1.6. It has to be related to the ROM as I have the same Radio ROM for all three OS images and only the XDA Live ROM works correctly.
edwinyuen said:
I did a hard reset, paired the headset, and tried it right away and still had the issue so it's not VC 1.6. It has to be related to the ROM as I have the same Radio ROM for all three OS images and only the XDA Live ROM works correctly.
Click to expand...
Click to collapse
Sorry, what I meant is that perhaps Cyberon Voice Commander is 'fixing' the issue on my system, rather than saying MS VC 1.6 was causing the problem. Next time I hard reset I will test my headset BEFORE installing cyberon software
Ok I'm still having this problem and this is what I have tried so far:
I downgraded to XDALive v0.10 and my BT worked, but no WiFi
So I upgraded to HardSPL v6, then installed the 1.40.30.00 Radio rom, and then went back to Cingular Black 2.0, WiFi back but no BT unless headset is activated after call is initiated.
Installed Cyberon Voice Commander, didn't effect anything, still no BT
Removed Cyberon Voice Commander and re-installed MS VC 1.6 installed all the hacks and still no audio in the headset.
So it looks like it is something in the ROM that is killing the BT functionality. Maybe because the XDALive is based on a beta WM6 and the Black is based on a full version?
I've been struggling for several months now to get my MDAC III working with my built-in car Bluetooth hands-free. The full details are below, but in short, I'm told that the system seems to work OK with Wizard, and I'm wondering what about the Wizard could be different to the Artemis (Bluetooth stack perhaps?), and if there is a difference, is there anything I can do about it?
The full issue: The system I'm trying to connect with is in a Land Rover Freelander 2 (LR2 in the US) Initial pairing was a bit hit and miss, but now I've got the the phone paired with the PTI, that's not a problem and they automatically pair whenever I start the car.
I can succesfully initiate or answer a call from the car, but the call itself isn't routed through the car's speakers/mic, it just goes through the phone as normal. However, once in a call if I select the "privacy" option on the PTI (which would normally have the effect I've already got of passing the call to the phone), and then select the "hands free" option, it does what it should and routes the call through the car. Effectively, it's as if the system starts in "privacy" mode rather than "hands free". Once I've done this once, subsequent calls work fine, routing straight through the car, but only until the ignition's turned off. The next time I start the car up I'm still paired, but calls go through the phone again.
If anyone's got any suggestions, I'd really appreciate them.
Thanks!
Try this
Had similar in a BMW...
Try www.jetwaremobile.com
Thanks, did try that but didn't seem to help, it seemed to be more geared towards additional functions like phonebook syncing rather than just getting a working connection in the first place. Maybe I'll give it another go.
Same Probleme On 207
hi,
I have the same ....
I precise that work fine with the original m650 rom, i search many hours but i found nothing, i try bluetooth toggle with no effect...
please help us !
thank for dev for everything they do !
RE
I try many combinaison so:
if i want to use my bt car kit, i'm forced to validate hands free option at every phone call...
I think it's btaudiotoggle the cause of mly problem, he is included in the aje rom...
you think it's possible ?
TangerineTractor said:
Had similar in a BMW...
Try www.jetwaremobile.com
Click to expand...
Click to collapse
Thanks TangerineTractor!
I fixed the problem I have with car kit of OPEL ANTARA using the software you said. It works disable sending Phonebooks.
I am having a similar problem with Wizard Mobile 6 cooked ROM. Before with the official O2 ROM on my Xda Mini S, it worked fine. The car would automatically recognise the phone whenever in proximity, and all calls would go through the speaker.
Now, I have to press the car kit's button (Nokia Bluetooth) each time I get in the car, to tell it to search for devices - i.e. the phone doesn't automatically announce its presence.
So, is there a different Bluetooth Stack we can try?
My Orbit works fine with my Nokia CK-7W using a B&B ROM.
Thanks, and yep that's the same car kit I have.
When you get in the car, do you have to do anything, or does the car kit automatically detect the phone? Mine doesn't since getting the Wizard Mobile 6 cooked ROM.
Do you know what Bluetooth Stack you use, and if I can download it anywhere for the Wizard?
No, just switch on the ignition key and away it goes. Also if the car kit is set as the default hands free if the phone rings it should try to connect to the car kit.
The radio I am using is 2.95.90 I have no idea what bluetooth stack it is, Tom Codin cooked the ROM, he will know.
Okay thanks. Does anyone know if the BT Stack is part of the Radio ROM? If so I'll just try a different Radio ROM.
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 have problems with my Bluetooth and the paired device in the car with almost every recent ROM.
After about 10 minutes driving with a connected phone, the Bluetooth shuts down on my Diamond. When I go to Settings -> ... > Bluetooth -> Mode -> Turn on Bluetooth is unchecked. If I check it again it connects again with the phone and about 10 minutes later it's off again.
I went back to the RUU_Diamond_HTC_WWE_EastEurope_1.93.479.3_Radio_Signed_Diamond_52.29.25.12_1.00.25.05_Ship.exe. It's against my feelings, believe, etc. but I want to solve it .....
I installed Advanced Configuration Tool (3.0), went to Bluetooth -> Audio gateway power save and Disabled it. I did it because I was reading about suspended devices and power save features. I thought that the loss of Bluetooth is been caused by a saving power feature.
After a soft reset, the Bluetooth stays connected.
It's a start, but I'm not happy with it ... I would like to use cooked ROM's and optimal settings in the ROM.
There are other tweaks too in Bluetooth, for example the supported bitpool, etc. Perhaps those settings cause the shutdown of a connected Bluetooth device instaed of the power save feature.
Has anyone this kind of problems too with paired Bluetooth devices?
If so, would you like to help me to find the cause?
If not, can you describe what device you use (Jabra, TomTom, car radio, etc.), which ROM, which radio and extra tweaks?
Hi
I do have the same problem. I am using my Diamond with my Opel Astra (Vauxhall) and a CD70 radio with built in handsfree (Opel UHP). It disconnects after 10 minutes and after calls. Everything else works fine. Changing rom and radios has not helped so far. If I don't close the comm manager it stays connected but disconnects after a call because the comm manager is closed with the end of the call. Is there a way to force the comm manager not to close?
Olli
olliver said:
Hi
I do have the same problem. I am using my Diamond with my Opel Astra (Vauxhall) and a CD70 radio with built in handsfree (Opel UHP). It disconnects after 10 minutes and after calls. Everything else works fine. Changing rom and radios has not helped so far. If I don't close the comm manager it stays connected but disconnects after a call because the comm manager is closed with the end of the call. Is there a way to force the comm manager not to close?
Olli
Click to expand...
Click to collapse
I have a CD70 too in a Opel Zafira.
This "comm manager" thing is interesting, but it looks to me like an Opel issue.
Can't you flash firmwares by opel?
Riel said:
Can't you flash firmwares by opel?
Click to expand...
Click to collapse
That's an option, but my Trinity (P3600) performed great with the same car. Will an upgrade solve my problems? I know one thing, it's not cheap either.
I tried it with different ROM's, but it still happens.
I tried it with different radio's, nothing changed.
Till today, I've got now the new radio (v1.05.25.BS14).
http://forum.xda-developers.com/showthread.php?t=432770
It has fixed the delays in GPS + faster GPS fix and more important fo me Bluetooth didn't stop today.
I'm sure 100% sure yet, but seems to be better.
I got something to complain too about the new radio. The radio signal is less strong than the .05 radio.
Same problem here
My Vectra is equipped with CD70.
Previously I've owned a Kaiser and the problem was solved by one of the 6.1 radios, bluetooth connection was rock solid.
Right now I have the same problem with Diamond - after every single phone connection, when I'll hangup, the phone disconnects CD70. When I'll try to reconnect manually using CD70 everything is fine.
I've noticed that the same problem exists when I'm using Nokia bluetooth headset - one call, bluetooth connection dropped...
I've tried following Diamond radios:
.05
.07
.08
.BS14
and two Raphael radios by Bepe:
1.03.25.18
1.02.25.11
Each Diamond radio behaves the same way. Each Raphael radio adds a bonus - random bluetooth connection problems.
Right now I'm back with .05, I think I'll look for the software I've seen once (can't recall the name) - it's a PDA application designed for connecting to the car bluetooth systems and it has been cerftified to work fine with CD70.
Use Jetware Mobile for htc-diamond.
jetware
That's the software I couldn't remember the name.
Anyway I gave it a shot and it gets even worse, I couldnt get the connection lasting longer then 2-3 minutes, totally unstable
Right now I got back to radio .08 - the bluetooth link is rock solid, I guess I'll just need to get used to reconnecting after each phone call
Same bluetooth system in my car, same problems as you guys.
To avoid the disconnections after calls you need to go, with 'Advanced Config' to bluetooth->Audio gateway power save, and switch it to disabled.
For me this little change solve the 'first' problem, but I have another one that I don't know how to solve: the aparently random bluetooth disconections. Sometimes BT is not disconnected in hours, sometimes in days.
I am also using Jetware Mobile, but i didn't feel any improve...
The random ones depend on the radio rom version - I was using .05 and it was rock solid.
I will try .16 with audio gateway started and with power save disabled as you advised - I thought about it earler but previously I tried to disable the power save without enabling audiogateway service
Well, we will see if it works or not.
Hi,
I also have a Vectra CD/70 combination, for 2 yrs now.
I had a HTC3300 and 2years i had not a single problem with Bluetooth connection.
Now i have a HTC Diamond Touch Pro and have the same problems you guys have.
I tried all your suggestions, radio's and so on with no good result.
The good news is .. its an Opel problem and it seems to be that a Bluetooth Firmware Upgrade is available from Opel Germany. I just contacted my dealer and next week he will Upgrade my bluetooth firmware.
I will keep you guys informed.
Hello,
had the same problem with my Opel CD70.
Using Jetware Mobile and limited the entrys who copied to the car to a max. of 5. Also disable the call lists. Now it works.
I think the Opel/Vauxhall Bluetooth Connection disabels if to many entries are copied to the car.
Hello,
any News about our Bluetooth Problem ???
I also have a CD70 from Opel and I cannot understand why my Diamond swich of Bluetooth after a while ?
Is it an Opel-Problem or does anybody now an Application which helps ?
Thanks a lot for Your help,
Stepos
Hi,
I am currently using BTrestore (http://home.casema.nl/rgschmidt/WM/Downloads/BTRestore_V_1_0_0_PPC.ARMV4.CAB). This utility checks the status of the bluetooth stack every 5 secs and (re)enables it everytime it's down. It seems that the 5 secs are short enough to keep the phone connected. It's not a real solution and unfortunately this tool is sometimes instable too, but it absolutely extends the connection time with the UHP.
Maybe bullock can tell us if the carkit upgrade solves anything...??
I also created a ticket at HTC, but they refuse to troubleshoot user specific issues. They told me they only look into issues if they get enough calls from different users and to keep an eye on the update site (they seem to be able to solve issues without knowing what the actual issue is...). So I would encourage everyone here to create a HTC ticket for this issue. I still think it is an HTC issue: a bluetooth stack should never go down without any user intervention.
Good luck!
BTrestart and Jetware Mobile doesn`t help, my Touch diamond disconnect again from Opel CD70 and swiched off Bluetooth !
Can anybody help ?
Sorry guys, the OpelDealer is still "searching" for the Bluetooth upgrade.
After several phonecalls maybe next week (1st week of Febr) it will be made available to the dealer.
Like i said ... i willl keep you informed ... still have this lousy problem !!
..does anybody use the new Rom 2.03 ? Any difference ?
I also asked my Opel-Dealer for an Update of UHP, next week I 'll get new Information....
... well guys I had my CD70 updated !! I am/was very sceptical because the only thing they did was a re-install of the Language of the Navi System with a version 2005 CD. I asked if that was all to correct my Bluetooth problem .... the (smiling) answer was YES.
I have it now for 24hrs ...... and Bluetooth is still on )
I will let you know the result after a week !!
..i can't beleave it works with a 2005-update ! Great !
My Opel-Dealer is still busy in selling 10 Opel Corsa every day (..the magic word is "Abwrackprämie") , so I'll have a date there next week...
When I bought my Vectra the dealer had also to reinstall the Language-CD, maybey it was the wrong version....
...... Sorry guys ......
This update DOES not do the magic trick !! So we have to find another solution
who has the right idea ??