Related
Hi, i've upgraded my Tytn succesfully to WM6 Black Edition, works like a charm, great performance (better then WM5) only one major problem is that i cannot activate Rsap with "sapsettings" that doesn't seem available. I've downloaded the "ActivateMSBluetoothSAPProfile.cab" from another ROM but that gives an error.
Is there a ROM that has "Sapsettings" in the programs? I'd install that one then.
Any help is appreciated. Thnx.
Hi, I've had the same problem after upgrading my Hermes 300 to 3DES.3
I was missing the SAP or rSAP, which I needed for my Passat.
I found an OEM package here: http://wiki.xda-developers.com/index.php?pagename=HTC_Universal_WM6_Kitchen_Helmi
and downloaded the btsapprofile (direct link: ftp://xda:[email protected]/Uploads/Universal/helmi_c/Kitchen_OEM/btsapprofile.v1.45.rar)
Extract the content of this file to your PC. Copy SAPSettings.lnk to \Windows\Start Menu\Programs on your phone.
Copy SAPSettings.exe.0409.mui, sapsettings.htm, SAPSettings.exe, SALib.dll, BtSim.exe to \Windows on your phone.
Go to Programs on your phone - you should find a working link to SAP settings.
This did the trick for me.
Cheers - mgruett
You are my hero! Works 100%. Thank you!
While looking into this issue i found anothern, maybe easier solution together with my collegues (same problem here, for the VW Passat fleet)
Just open this file, unrar, copy .cab file on your Hermes, execute, softreset and off you go.
http://forum.xda-developers.com/attachment.php?attachmentid=29801&d=1155792304
tested it on 2 Hermes with WM6 and it works flawlessly.
rSAP with TyTN, s620 and Wizard
Hi,
when you're saying "100% working" and "works flawlessly" do you mean you have the Icon in your program folder or is it really working well with your car-kit ? Make phonecalls, Syncs phonebook etc. ???
I've a carkit from THB (bury) since ages in my car and upgraded the phone holders from old nokias up to the LT9100 with rSAP. As rSap pops up, I was 100% sure that this is the solution I'm looking for.
Since 6 months now, I try to get that damn thing working. It always fails with "Sim Card missing / not found". I could pair, it connects to the phone, disables the phone-module, but I couldn't dial a number, nor could I sync the phone book.
I tried it with Blueangel, Wizard, TyTN and my brandnew S620 without succes. I tried it with PPC 2003, WM5 and WM6 Roms, no chance. Of course, I followed the hints in the forum.
I sent the carkit to Bury to upgrade to the latest firmware and guess what ... nothing, always the same problem with Windows Devices, but my Nokia 9300 connects well in a second.
So, bottom line, I'm not sure if it is a Bury Problem with a bad rSAP support for WM or a WM Problem as my Nokia connects well.
Any thought or tipp is highly appreciated
Thanks
Chris
I just tried the download from WDawn (thanks incidentally) and aside from it resetting my background to the windows default, worked just fine. Enabled SAP, gave the phone a poke up the rear and tried it on a Nokia 616 car kit. This car kit uses SAP if available, otherwise falls back to HFP. It quite happily connected via SAP. Next text with be the Mercedes Bluetooth module, which would have to be the fussiest car unit I've ever come across and it only supports SAP (no HFP, HSP.. or other fall back).
The phone used is a DoPod 838 Pro running the newly released official WM6 ROM. I never had this success with the cooked LVSW ROMs that I used in the past.
Alex.
Progress but still troubled
WDawn said:
While looking into this issue i found anothern, maybe easier solution together with my collegues (same problem here, for the VW Passat fleet)
Just open this file, unrar, copy .cab file on your Hermes, execute, softreset and off you go.
forum.xda-developers.com/attachment.php?attachmentid=29801&d=155792304
tested it on 2 Hermes with WM6 and it works flawlessly.
Click to expand...
Click to collapse
Hello!
I have a HP Ipaq 914c and having troubles connecting with the VW Passat.
Here are the steps that I have made so far. Any help will be much appreciated.
1) Initialy on the VW menu searched for BT phones. Detected mine but whenever I selected it, returned back with the message: "Phone not compatible"
2) Dicovered here this tool BTSAP_Test, installed on the Ipaq and activated the "Remote SIM Access" checkbox button
3) VW now is able to pair with the phone (after inputing the 16 code number) but immediatly after pairing says that "Bluetooth is not activated on phone" ...
4) Looking on BT devices in IPAQ I can now see a device named "VW UHV PREM", but the only available service to use for this device is "Dialup Networking".
Am I missing something ? Thanks.
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 ??
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.
Hi all,
Anyone can confirm that Desire has a rSAP (remote Sim access)?
Some people are saying it doesn't work with their Nav, some say it is working.
Any one got it hooked up to their Vw/Audi/Skoda RNS Nav?
Looking to change from my TouchHD.
Cheers,
Android does not support the SAP/rSAP protocol. It may be that some people have it working on cars that use the HFP or HSP profiles.
Thanks mate, not good at all!!!
A little up now the phone's live...
Does it support rsap? is there any way to push contacts etc...?
I got an audi with a built in Bluetooth system, pairing ok, phone etc ok, but no possibilities with my desire to have rsap working
swissman said:
A little up now the phone's live...
Does it support rsap? is there any way to push contacts etc...?
I got an audi with a built in Bluetooth system, pairing ok, phone etc ok, but no possibilities with my desire to have rsap working
Click to expand...
Click to collapse
I also have the Audi built in BT system, and it works fine except that from what I've read about rSAP, I don't think it's working in that mode with the Audi.
The only difference (problem) I've been facing with my HTC phones vs. Nokia e71 is that the phone ring tone is not pushed to the car speakers when receiving a call. I was hoping it would work with the Desire as the default Audi BT ringtone is stupidly annoying.
Sorry off topic again, but I was wondering, are Bluetooth profiles generally defined by hardware or software? Or some by this, some by that?
Maybe you could check if it has another setting to retrieve data from the phone.
From what i know the new modules used in audi/vw/skoda are Novero modules (part of the nokia business) which only supports rsap.
The older modules are from harman/Becker and do support al the possible connectiontypes.
You can check which type you have under the passengers frontseat, the modules are build in under the seat, not in the radio.
If you have a Novero, tough luck. But you can always check on the local car junkyard if you can find an old car which does have a harman/becker, and build that one in
salahag said:
I also have the Audi built in BT system, and it works fine except that from what I've read about rSAP, I don't think it's working in that mode with the Audi.
The only difference (problem) I've been facing with my HTC phones vs. Nokia e71 is that the phone ring tone is not pushed to the car speakers when receiving a call. I was hoping it would work with the Desire as the default Audi BT ringtone is stupidly annoying.
Sorry off topic again, but I was wondering, are Bluetooth profiles generally defined by hardware or software? Or some by this, some by that?
Click to expand...
Click to collapse
Just wanted to add to eliminate any confusion. I can dial contacts saved on the phone and directly search for them on the car screen. But what I understood is that rSAP profile connects to the SIM card and fully replaces the phone, where it goes into some kind of sleep mode!
salahag said:
Just wanted to add to eliminate any confusion. I can dial contacts saved on the phone and directly search for them on the car screen. But what I understood is that rSAP profile connects to the SIM card and fully replaces the phone, where it goes into some kind of sleep mode!
Click to expand...
Click to collapse
Exactly... you can even read/send sms directly through the display and through your car multimedia system.
Ford
Just a little extra info, Desire now works with the Ford Convers+ system but ONLY on Android 2.1 Update1 (the stock Android 2.1 didn't work).
Just thought that may be why there's mixed reports of working/not working?
Tirinoarim said:
Just a little extra info, Desire now works with the Ford Convers+ system but ONLY on Android 2.1 Update1 (the stock Android 2.1 didn't work).
Just thought that may be why there's mixed reports of working/not working?
Click to expand...
Click to collapse
I got the stock Android and it's showing Android 2.1 update 1.... but not working ;-)
Hmm - well I'm trying to use my HTC Desire with a 2010 Audi A3 with BT and not having any luck so far. Although it paired and transferred the phonebook (took quite a few minutes with a couple of hundred contacts), it's now being really flaky and sometimes just refusing to connect at all. I tried un-pairing/re-pairing but to no avail. It just seems to work sometimes for a bit then stop again. By comparison pairing my Desire with a Jabra BT headset worked fine.
Anyone else having these problems? Anyone know of any updates for the Audi software? (if not I suppose I'll just need to wait for Froyo and hope that it fixes things )
my desire works well with my VW golf.
phone book, calls (dialing and receiving) and status dispay working. not working is SMS
Hey Folks,
there is room for some BT "education", because most people don't know the difference between rSAP and Handsfree.
Handsfree is working like a BT headset - most disadvantage - you are using the phoneunit of your mobile.
rSAP is using BT protocoll to get only the SIM card of your mobile and work together with the phoneunit of your car.
For Audi you can see on which mode your are conntected at the MMI-Display => "SIM card icon" stands for rSAP while "Mobilephone icon" represents handsfree mode.
no rSAP
I could be wrong, but I was of the impression that Nokia had patented the RSAP protocol, so you're not going to see it on non-Nokia phones. Irritating, really. Some car users have retrofitted their handsfree kits with a module that uses handsfree profile with some success but it's not going to use the car antennae etc in this case.
rSAP is a "STANDARD" for bluetooth protocoll in general.
Nokia was one of the first, thatswhy the Nokia unit has some "problems" in early releases....
Well I picked up my Skoda Superb last week, dealer told me they were fitting the new GSM 3 units that had just recently changed, not that it meant much to me.
Anyways it did work fine first couple days then started playing up with not connecting, I went into the options because I found it was connecting to media, but not phone, so I disabled the media option on the phone for the bluetooth connections and its been fine ever since.
Desire running Modaco R4, R5 & R6 now also ok.
Also saw a file posted on there that is meant to fix the iffy bluetooth connection problems, its been confirmed as working but I've not tried it as I've not had any more problems with it.
Will take a look though see if its connecting with a phone or sim card, I had noticed the signal always seemed really good even if the phone was berried in the car somewhere so maybe the rSAP explains it.
Tinyk said:
Also saw a file posted on there that is meant to fix the iffy bluetooth connection problems, its been confirmed as working but I've not tried it as I've not had any more problems with it.
Click to expand...
Click to collapse
Do you have a link to the thread that includes this file by any chance?
Do not mix up android 2.1 and 2.2.
AFAIK the modaco roms are froyo which should have a better bluetooth stack than eclair.
Well some good news! The FroYo/2.2 update on the Desire seemed to do the trick for me and I now seem to be able to get a stable BT connection with my A3. Phonebook transfer working fine too and it's reacquiring the connection when getting back into the car.
Any hope for Android 2.1?
Alanjrobertson: did you say you got your HTC Desire Android v2.1 phone working with your Audi, albeit a bit flaky? I cant get my HTC Desire Android v2.1 phone working with my VW EOS working at all.
What was the process you followed? The process I went through was to turn on phone’s bluetooth and make my phone discoverable. I then initiated a search from the car. It found my phone and displayed the correct name. However, when I chose the “connect” option on the car, it gave the error message: "mobile telephone phone is not compatible" on the car’s MFD.
Is this what you did? Is there a better way of connecting?
The car’s entertainment system is RNS510. I’m not sure if this is associated with Bluetooth or not.
My previous phone (Nokia 5800) worked OK, but my Desire doesn’t.
I am hoping that the Android v2.2 upgrade will fix my problems, but I’m still waiting for the update from Orange. It could take a while by the sounds of things.
I contacted HTC and they told me “The HTC Desire does not have the remote sim access profile. we currently have no plans to update the Bluetooth profiles on the device.” This makes me worried that when I eventually do get the Android v2.2 upgrade it will not work.
Any ideas other than waiting for the Android v2.2 upgrade?