Related
:x i have been trying to get the bluetooth sync to work to no avail. i am using a 3com bluetooth usb adapter on my pc and card on my notebook. i am having problems with both when i try to synchronise. i can see my i-mate has been discovered and bonded; i can send files too. but i cannot synchronise. either there is a bug in the PDA software, or its really hard (needs a rocket scientist) to use!!! either way its dissappointing. can anyone help?
by the way my nokia and ericsson phones sync fine with my current setup.
I have the same problem using a toshiba portege 4010 with bluetooth built in, it works with my Nokia but not with the XDA i am using aytivesync 3.7.1
I would also like some help or ideas please
Thanks
John
Got bluetooth to work once
I got bluetooth to work only once using a Billionton USB Bluetooth adapter. The software is neat, but requires so much messing around with to get the PDA to actually synchronise in bluetooth mode. Unfortunately, I could not get it to work again. Should have documented what I did the first time.
After trying lots of times, it works. I sycronised a XDA2 in bluetooth mode.
There are a few important things
1. You first have to sychronise the XDA2 in USB Cradle to build a standard-partnership between desktop pc and XDA2.
2.remove the XDA2 from the Cradle.
3.look which com-port your bluetooth serial port is using
4.take these settings over to the active sync settings (must be exactly the same com port)
5. pair the two devices
6.start active sync on the XDA2 and sychronise via bluetooth
It works.....
i made a better description with screenshots (in german) but i don't know how to post it.
I use a toshiba laptop with bluetooth built in, but when i scan the available bluetooth things in the XDA 2 it only finds "voice gateway" and "SSA" or something like that, there is no serial port listed, when i scan a phone (nokia) it finds "dun" "serial port" "fax" etc etc.
So i cant connect my XDA2 as the only profiles it seems to have are Voice gateway and some SSA thing, so as there is no serial port listed i cant use activesync, i have bonded with both the voice and SSA thing to com ports from 5 to 9 and get a connection, but as its not a serial port it will not work with activesync.
Sorry for my terrible description of the problem, but if yours works i am sur e it will make sence to you
Thanks
John
Your right ! The XDA2 provides no serial port profile to my Bluetooth stick too. And thats why the Bluetooth GPS Receiver doesn't work.
I know this sounds strange, but with Active Sync Bluetooth definitely works.
Yes I finally got it to work a couple of days ago with a certain type of bluetooth usb adapter and software. All I can say, is that bluetooth is not very user friendly!!!! Activesync should have it show up just as it shows "infrared" in the connection settings. This will make it very easy to select it. In this day and age, you cannot expect a technology to be successful from mass usage if it is not totally idiot proof. BLUETOOTH is not.... WIFI will rule!!!!
Hi so have you bonded to the "ssa" profile, and then what ever com port you used you then changed activesync to use this port and it then works, because i tried this and it done not work.
I also have a tomtom bluetooth that a friend is borrowing, but by the looks of it there is no point in getting it back as if there is no serial port on the available using bluetooth that will not work either
Thanks
John
try this link. it may help u set up your bluetooth with active sync - http://www.bluetoothnews.com/features/ActiveSync.htm
@applecom
No. You just have to pair the Devices. Don't connect to any Profile.
Pair them and then start Active Sync from the XDA 2 and connect with bluetooth.
activesync and bluetooth with xda II
start > settings > system > bluetooth settings > Activesync over blutooth (START)
Nutty but there you go.
XDA II Bluetooth ActiveSync
I noted if you add or change the registry will work even better :
\HLKM\SOFT\Microsoft\Bluetooth\Activesync
IsBTASsetup from 0 to 1
Hi
I have changed the registry like you said, But how dose it work better, the only problems i have are when i ask activesync on the XDA to connect over BT it oftern trys and says port in use, i just retry a few times and it works. After doing the reg edit it did connect first time, but is this what you ment by "its works better"
Thanks
John
As this my first ever post, I don't want to come over as smug, but I took delivery of my XDA 2 today and it synced using bluetooth after about 25 minutes of 'messing'!
All I did was delete all the bonding between the PC and the XDA and told it to sync via bluetooth, initiating from the XDA, I thought that it had failed...but then the XDA sprang to life and 'Bob was my uncle'!!
Very impressed with my XDA 2, having used an XDA for about 8 months.
Andy.
Bluetooth Sync
What I meant was it has become easier to get XDA II sync via bluetooth. Please note that you have to unpair your PC first then change the registry and pair again. If your PC's Bluetooth dongle support Headset profile ( I used anycom USB220 which has this profile) you will see your XDA II asking you if you want Headset profile added and Activesync screen for bluetooth appeared as well. Changing the registry will always make the sync work is what i noted. Seems like XDA II Bluetooth supports many profile just that dont know how to make it works.
Bluetooth Activesync problems
I'm on the verge of giving up on this! Think I should stick to USB sync...here goes...
I've tried the tricks mentioned in the forum to try to get my XDA II to sync via bluetooth with my Sony VAIO laptop (it has built-in bluetooth). I can get the two devices to bond (I enter the PIN number on both the laptop and XDA and it succeeds) but then I try to run the Bluetooth Activesync setup (in Settings-->Bluetooth Settings on the XDA) I get an error message every time that says "Please bond with other Bluetooth device which supports serial port or Activesync profile as your Activesync partner!"
I thought I already HAD bonded the devices? Any ideas?
Cheers
Carlton
Finally sorted it out. Delete the partnership that you already have. Start from start>settings>system>Bluetooth Settings. When you clik start, then pair your device again. After the pairing, you will get the message that Bluetooth Active Sync is now ready.
Still no joy
Thanks for your help Merc.
I tried doing exactly what you suggested but still doesn't work. This is what happens:
I deleted the existing bond on both XDA II and PC.
I went to start>settings>system>Bluetooth Settings and clicked on Start. This gave me the message "Please bond with other Bluetooth device which supports serial port or Activesync profile as your Activesync partner!" like before, then automatically opened the Bluetooth connections control panel in the "Mode" pane. I chose 'Discoverable' and clicked OK. I then went to my PC and used the Wireless Link control panel and clicked 'Add' (to run Bluetooth connection wizard) which searched for devices. It found my XDA II and I entered the passkey on both XDAII and PC (same passkey on each).
The Bluetooth connection wizard then told me that the XDAII was offering DUN (dial up networking) services. I selected this and then clicked next. Was I supposed to select this (actually, it made no difference when I tried again without selecting!).
The wizard completed and both the PC and XDAII notified me that the bond was successful. I then waited and waited for something else to 'happen' (like a message to say that Bluetooth Active Sync is now ready.) but nothing happened. I gave it a couple of minutes.
I went to Activesync on the XDA and tried the 'connct with Bluetooth' just in case it had worked, but nothing happened. I went to Activesync on the PC and tried using a different COM port for infrared/serial links (as I assume this is what bluetooth uses) but no joy. I only had COM3 and COM4 showing in the connection settings in activesync, which surprised me as I thought there would be more.
That's it. I tried 3 times but still no luck. Any other ideas are greatly appreciated!
Cheers
Carlton
The
Your procedure is just like mine. But I used "On" and discovered the PC from the PDA. Do not use "Discoverable". Let me hear if you have any luck
The only way I have got it to work is assigning the bluetooth serial port to COM 6. Then set Activesync on the desktop to COM 6.
Any other COM port just won't work. Anybody else got it working on a different bluetooth COM port?
xdaguru
Hi folks,
I upgraded my Hermes with Schap's Windows Mobile 6 ROM. Works fine so far. But when I try to use my Bluetooth GPS it acts strange.
I paired the Bluetooth device and set up a COM-port for the applications. The first time it works. The next time, when I switch on Bluetooth and start for example TomTom, the Hermes tells me there is a new Bluetooth device that wants to connect. I checked and found out the GPS is still in the list of known Bluetooth devices and the COM-port is set. But the assistant is still bugging until I add the "new" device. After that of course my "old" device is gone.
How can I avoid this? Anyone experiencing the same problem?
I have the same issue, really annoying so would love to know the answer
Tafkas.Net said:
Hi folks,
I upgraded my Hermes with Schap's Windows Mobile 6 ROM. Works fine so far. But when I try to use my Bluetooth GPS it acts strange.
I paired the Bluetooth device and set up a COM-port for the applications. The first time it works. The next time, when I switch on Bluetooth and start for example TomTom, the Hermes tells me there is a new Bluetooth device that wants to connect. I checked and found out the GPS is still in the list of known Bluetooth devices and the COM-port is set. But the assistant is still bugging until I add the "new" device. After that of course my "old" device is gone.
How can I avoid this? Anyone experiencing the same problem?
Click to expand...
Click to collapse
On your Hermes:
Have you tried to checked off: "Make this device visible to other devices"?
Under: Start\Settings\Connections\Bluetooth\Mode (2nd tab on the bottom)
Option #1 (Hermes)
~If, "Make this device visible to other devices is not enabled, delete the pairing for your GPS.
~Check off "Make this device visible to other devices"
~Pair your GPS again (ensure that "Make this device visible to other devices" is still enabled)
Option #2 (GPS)
Don't know what kind of settings for bluetooth you may have on your GPS. I found for my car stereo, that I needed to leave it, in the "waiting/open for connection mode.
Now when I turn the car on it automatically connects the phone and stereo off my Hermes.
What I'm basically saying here is there may be a setting to leave your GPS automatically open for bluetooth connections?
I think option #1 may do the trick....
Hope this helps! Good Luck!
jac said:
On your Hermes:
Have you tried to checked off: "Make this device visible to other devices"?
Under: Start\Settings\Connections\Bluetooth\Mode (2nd tab on the bottom)
Option #1 (Hermes)
~If, "Make this device visible to other devices is not enabled, delete the pairing for your GPS.
~Check off "Make this device visible to other devices"
~Pair your GPS again (ensure that "Make this device visible to other devices" is still enabled)
Option #2 (GPS)
Don't know what kind of settings for bluetooth you may have on your GPS. I found for my car stereo, that I needed to leave it, in the "waiting/open for connection mode.
Now when I turn the car on it automatically connects the phone and stereo off my Hermes.
What I'm basically saying here is there may be a setting to leave your GPS automatically open for bluetooth connections?
I think option #1 may do the trick....
Hope this helps! Good Luck!
Click to expand...
Click to collapse
Mine is set to NOT be visable to others & my bluetooth GPS device just ha a on/off button.
paul8811 said:
Mine is set to NOT be visible to others & my bluetooth GPS device just ha a on/off button.
Click to expand...
Click to collapse
If your concerned about Security you can always change the Pairing codes.
and or turn off bluetooth when not needed.
I'm unaware of any cases where one can connect unless there paired, so in most cases access needs to be allowed on both ends, usually needing pairing codes. Even if it is one way, an approval code will still be needed.
What I found is this, if you want automatic connecting with one way pairing codes i.e. (Car Stereo to PDA or GPS to PDA) You'll need to allow "make device visible" checked off. The usual cause is a memory storing issue with the GPS or Car Stereo. I know that on high end Stereo's and GPS's they have on board memory which will save connection settings, where you'd put pairing codes on both ends and it will save the settings, thus negating the need to leave visible.
Don't know if I answered your question?
Hope I was able to shed some light on the subject....
Good Luck!
Just tried a few latest windows 6.1 roms and found out that my bluetooth headset (I tried a few) is not asking for passcode anymore (it used to ask to enter "0000"). On one hand - it's a cool feature saving you time and efforts to pair your devices. On the other hand- it's quite dangerous. Just imagine somebody near you (while you're having lunch) is playing with bluetooth on the laptop and connects to your phone without you knowing it. Potentially, he can download all your info from the phone. No good!
I was thinking that it maybe something wrong with my bluetooth or the ROM on the phone. But after I did a quick search here, it appears that Windows 6.1 has this neat feature of "automatic cycling of the standard passcodes" during pairing process. Is there any fix to this security breach? Or maybe I'm not getting it quite right?
well i still havent paired my headset with my pdacorner v23 NonRBSN rom but if you go to comm manager, hit settings, the click on bluetooth. On the tab Security there should be a box that says authentication passkey required. i dont know if thats bluetooth or infrared....but im sure its bluetooth.
Hope that works.
With all the wm 6.1's I've used it appears to only work with BT headsets... GPS and other BT devices need a key....
Cheers...
If that's so - it's good. I'll experiment with bluetooth dongle on my PC.
Hello, my name is Manolo and i'm a surveyor. I'm trying to use my HTC X7500 as a data controller for topographic relief. I own two Topcon hiper pro gps antennas than can communicate with a controller via bluetooth or RS232 cable.
My problem is that when i connect via bluetooth the athena x7500 to the gps antennas, it can see both of them, but it can't hold always the to connections separate at the same time. 99,9% of times i belive the athena connected first to one gps antenna and second to the other one, but at the end i understand it gets the signal only from one. So, to bypass the problem i tryied to connect the athena to one gps via rs232+usb adapter and the other one via bluetooth, but i can't get the rs232 connection. It seems that only Hp ipaq hx series can handle the rs232 connections.
Any suggestions?
Any software that manage bluetooth connections?
typical data controllers: http://www.data-collectors.com/index.html
topcon instruments:http://global.topcon.com/positioning/index.html
Thanks,
Manolo
I don't know if this is relevent, but here is a hint...
When I used to have a bluetooth gps antenna, I had to set up an outgoing com port dedicated to this antenna.
Have you created two different outgoing ports in the bluetooth options, one for each antenna ?
The guy on this thread - http://forum.xda-developers.com/showthread.php?t=515103 - found a usb-to-serial solution for his problem. Maybe he could help you. He also mentions some sort of hardware/driver he's used.
Hope this helps.
Thank you MysterD for answering.
Yes, i tryed to give a different COM to gps antennas, but with no success.
For working with this GPS antennas Topcon gives you also a PPC/Controller (named FC 100), with the antennas. So, HTC 7500 should be an emergency controller that i bought when the original controller got broken and i sent it to the assistance.
So, i checked the Software settings on the original Controller, and it connects on the antennas via bluetooth always on COM8. Yes, same port for both the antennas!
Infact, when i start the software:
1) it scans for bluetooth devices
2) i select the first antenna (a base antenna that i live in a point and don't move it)
3) it disconnect from the first antenna
4) it scans again for bluetooth devices
5) i select the second antenna (rover antenna, that i bring with me during the mesuraments)
6) the software goes into a mesurament menu and o start working.
On the HTC i must search the devices first and than start the software. That's the problem! If i give the same COM8 at both bluetooth devices at the same time, HTC gets confused.
Thank you Wovens.
I'm gonna try the drivers. Let's see if they work!
And there's no place in your software that would enable setting that first antenna should use port COMX and the second one COMY ?
Also, have you tried disabling the feature that lets Windows Mobile manage the GPS ?
On my Diamond, i go to Start > Settings > System > External GPS ("GPS Externe" on my French rom) > Access tab ("Accès", the third tab...) > Uncheck the only option on the tab (manage GPS automatically "Gérer GPS automatiquement" ...).
Yep, i think i already tried, but i'll try again and let you know it tomorrow.
Thanks
Okay,
assigning different ports to bluetooth devices seems working. But there is always something wrong: i can't start mesuring when i get into the mesure page. i don't know, i'll try to figure it out. Thanks anyway.
To connect the cable to the athena i probably need a driver for windows mobile. I'll try to find it.
Thank you very much guys,
Manolo
You're welcome.
Let us know if you succeed in getting your measures done !
Hi @ all,
just got my HD2 with german ROM and one of the first things I tried out was to get a connection to my car (Audi A6) through the remote sim access profile (SAP, rSAP) - but it didn't work...
Does someone use the HD2 in his car using the sim access profile, as available in Audi or VW cars?
I have
- Audi A6 Avant (model 03/2008)
- using the "Audi rSAP Adaptor" in the car cradle, located in the arm rest
- everything in the HD2 is activated for Sim Access
Result:
HD2 and car are connecting, I have to put the 16 digit security code in my phone, but after that the SAP mode does not start, and so I have no access to my phonebook. It seems that I only have a "normal" bluetooth handsfree connection, because the HD2 still shows that he is booked into the mobile network - and when rSAP is active, the phone itself disconnects from the network and "falls asleep".
I restarted my HD2 several times, also the rSAP-Adapter by turning ignition of the car off and on until the adaptor switches off, deleting the connections, creating new connections, but nothing helps...
Any comments or experiences from other users are highliy appreciated
Finally, I have to remark that my HTC Snap, which I just upgraded to WM 6.5, works very good im my car with the rSAP - no problems at all, I get all my contacts in the MMI.
Thanks in advance,
Jolig
Just got my HD2 and am having the same problem.
I'm trying to connect with a 2009MY Skoda Superb with the rSAP bluetooth kit.
This works fine with my E71 and my HTC Touch Cruise.
I've been told that there used to be an issue with OBEX authentication on previous versions of Windows Mobile. Apparently, it was important to disable this authentication. However, I can't see the checkbox in the version of WM that the HD2 is running.
Does anyone know what registry entry this checkbox might have been changing?
Thanks,
Bagpuss.
Thanks Bagpuss,
who gave you this information?
I hope someone can solve this problem....but I fear we have to wait until we have more HD2 - owners
-----------------------------------------------------
EDIT:
I just have read something about the "Schaps Advanced Configuration Tool" where someone with similar problems activated OBEX (but it was an older Win Mobile device, and some months ago) - perhaps this could help?
But I just installed version 3.3 of this tool, but it doesn't work on my HD2...
Hi Jolig,
Check out this thread:
http://briskoda.net/superb-ii/howto...us-rns510-using-non-compatible-mobile/131709/
on Briskoda.net.
One of the guys there had lots of problems getting his WM phone to work, and posted the fruits of his labours.
From what I can tell, we can't use the CAB file he mentions, as rSAP is built into the OS version that the HD2 uses.
I've actually logged this issue with HTC, and am awaiting their response. My company is considering the HD2 as our next standard handset, and we won't go for it unless the rSAP functionality works with all VW/Audi group cars.
I'll let you know if they get back to me.
Bagpuss.
Thx Bagpuss,
and yes, in my opinion it's a mess that the rSAP is apparently VERY unimportant for most people or manufacturers...otherwise we wouldn't have this trouble....
I will come back too if I should find some news.
Had the same problem, tried lots of stuff but none of my WM devices is able to work with the rSap protocol. Gave up on it and then my Skoda Columbus system was stolen.
Replaced it with a JVC 7000 with detachable front. Disabled the rSap carkit and am now using the JVC BT carkit wich is working great. The problem is in the MS BT stack. It is not supporting the rSap the way it should. Only phones that work flawlessly are Nokia's I'm afraid...
The lack of rSAP support is what made me ignore the iPhone this time around.
I was hoping that the HD2 would be a viable alternative, but sadly, it doesn't look like this is going to be the case.
As I bought it over the phone, then I've got 7 days in which to return it. If I can't get it to work, then I guess I'll be getting an N97 or N97 Mini (which will definitely work). :-(
Bagpuss.
@ Bagpuss,
otherwise, as I wrote, I can recommend trying the small HTC Snap (or also called Maple?).
Ok, this one has no touch screen and also a very small screen - but I can confirm he works with rSAP and is not too expensive. I will keep this one, although I now have the HD2
As to Bagpuss' information concerning the OBEX, I tried the following:
- installed the newest .NET framework version
(that was necessary to get Advanced Config Tool v 3.3 running)
- install Schap's Advanced Config Tool
- in the menu "Bluetooth", I enabled OBEX
- after that the config tool does a soft reset
...still no success....no SAP and no phone book
I also wrote an email to HTC - it's really annoying, having SAP in the phone etc. and nothing works.
I've a Golf VI (RNS510) and it's working very well. Just had to change Bluetooth security settings that by default does not make HD2 visible to other devices. And after partnership was established, I've reverted the settings to "Allow only devices from MyDevices to connect"
Hi Binks821,
Binks821 said:
I've a Golf VI (RNS510) and it's working very well. Just had to change Bluetooth security settings that by default does not make HD2 visible to other devices. And after partnership was established, I've reverted the settings to "Allow only devices from MyDevices to connect"
Click to expand...
Click to collapse
Can you confirm if your Golf has the premium bluetooth preparation?
There are two different versions of factory bluetooth kit for the RNS510, one which simply acts as a handsfree device, and the other (premium) which is a complete GSM phone.
It's the premium kit which uses rSAP, and which seems to be incompatible with the HD2.
You can tell if your Golf is using rSAP by checking to see if the signal strength meter on the HD2 shows any bars when connected to the car. If it does, then it's not using rSAP. If you see the signal meter with a little x in the corner, then it is using rSAP.
If you do have rSAP working, then I'd really like to know which firmware version your RNS510 is running, and also which firmware version you have in your HD2.
Thanks,
Bagpuss.
yes I've the premium version with RSAP access, not just handset.
Once partnership is established, it says SIM Access profile in Bluetooth settings, not Handset. And it disables my SIM on the phone, so no strength meter.
I had a Tytn before, and it was working the same way. Just when received my HD2 Monday, it was not working but default settings on the phone make HD2 not visible, So I received a message on the car saying "No compatible phone found". After playing with Bluetooth security settings, it was OK.
And of course I can import SIM contacts.
Be sure to check these settings (Settings tab in Sense, then Menu-> All Settings -> Bluetooth)
- Discoverable: always visible
- Advanced -> Connectivity: Allow all devices to connect, just during setup. After that change to "Allow only devices listed in My Devices to connect"
- Advanced -> SIM Access: be sure that rSAP is enabled
HD2 version info:
- OS: 5.2.21864 (21864.5.0.81)
- Manila: 2.5.19202525.0
For the car I have to check once I'll be in.
Hi Binks281,
Thanks for the confirmation.
I've now done some further testing in my car, and managed to have some success.
This is what I did.
In the car:
1) Remove all device pairings from the bluetooth system in the car.
On the HD2:
1) Perform a hard reset.
2) Turn on bluetooth. Make HD2 permanently discoverable.
3) Make sure rSAP is enabled (it is by default).
4) Turn off SIM pin (turns out this isn't necessary, but I wanted to make things simple).
So, at this point, I have the car system with no paired phones, and the HD2 with factory settings and no personal data (contacts etc.). I also made sure there were no contacts on the SIM card.
Back in the car, I perform a device search, and it detects the HD2.
I select the HD2, and the car displays the pairing password (1111 2222 3333 4444).
On the HD2, I enter the password.
I then get a prompt saying that Skoda_rSAP is trying to connect to the remote sim access service. I say allow, and also tick the box to allow all future connections.
After about 10 seconds, the maxidot in the car says 'New SIM card recognised', and prompts me to create a new user profile. I called it 'HTC_HD2'.
After about another 15-20 seconds, the car should extract the SIM details from the phone and the phone name, network and signal bars should appear in the car display.
You can now make calls, but there is no phonebook.
Given what others have said about the phonebook access, I'm pretty sure that this is what was stopping the pairing from working the first time I tried it. I've heard various stories, some which say that the phonebook access only works with SIM card contacts, some which say it only works with OBEX authentication switched off and so on.
If you look at the paired devices screen in the phone, then you can see connections coming into phone. First, you see a connection to the SIM Access profile, followed by a brief connection to the Phone Book Access profile. It was at this point, when accessing the phone book, that my previous attempts to pair failed.
I'm still trying to work out what is causing the problem with the phone, but I have done the following things:
1) Told the car to only sync phone memory contacts. By default, it's set to sync both SIM and phone memory. You can configure this on the car by going to Settings -> Phonebook -> Select Memory, and choosing 'Mobile Phone'.
2) Created four contacts in phone memory, one with only 1 mobile number, one with 2 numbers (mobile and home) and another two with three numbers (mobile, home and work). I've then gone into Settings -> Phonebook -> Upload and sync these across to the car.
So far, this has worked fine and disconnecting and reconnecting to the car works without a hitch.
I'm now going to try syncing a small subset of my contacts with ActiveSync to see if this also works.
If it does, then I'll gradually increase the number until it either works, or fails.
I'll report my progress here.
Bagpuss.
Thanks Bagpuss,
sounds interesting!
I think tomorrow I will try this also:
- remove all paired phones in the car-system
- delete all contacts
- disable SIM Pin
Temporarily I am not sure if I will do a hart reset in the first step because I've already installed so much... When the work fails, I thing I must do it
I will report what happened.
---------------------------
EDIT:
Ah, come on...TV this evening nothing interesting, wife in bed...I tried it, including hardreset
No success.
Bagpuss, what I detected:
First, you see a connection to the SIM Access profile, followed by a brief connection to the Phone Book Access profile. It was at this point, when accessing the phone book, that my previous attempts to pair failed.
Click to expand...
Click to collapse
This connection to the Sim Access Profile I see also, but only for one second, then it dissappears and then the connection "Handsfree" comes up - and this one remains....
I do not know else what to do.
I now reconnected my beloved HTC Snap/Maple, and now I will start installing my apps on the HD2....
Hi Jolig,
Sorry to hear that it didn't work.
By the sounds of it, the Audi system is somewhat different to the VW/Skoda one. From what I can tell, your system also appears to support using phones in handsfree mode (I'm guessing that the iPhone works in your car).
In the VW/Skoda cars, you can either have a car kit that acts as a handsfree device or one that uses rSAP, but not both.
It could just be that the HD2 isn't responding to the rSAP request quickly enough to satisfy the MMI. In that event, it falls back to using handsfree mode.
When it shows 'handsfree' on the HD2, can you use the MMI to make calls?
This whole area seems to be a bit flaky on the HD2, as I still can't work out why mine didn't work when I first tried.
Bagpuss.
Binks821 said:
yes I've the premium version with RSAP access, not just handset.
Once partnership is established, it says SIM Access profile in Bluetooth settings, not Handset. And it disables my SIM on the phone, so no strength meter.
I had a Tytn before, and it was working the same way. Just when received my HD2 Monday, it was not working but default settings on the phone make HD2 not visible, So I received a message on the car saying "No compatible phone found". After playing with Bluetooth security settings, it was OK.
And of course I can import SIM contacts.
Be sure to check these settings (Settings tab in Sense, then Menu-> All Settings -> Bluetooth)
- Discoverable: always visible
- Advanced -> Connectivity: Allow all devices to connect, just during setup. After that change to "Allow only devices listed in My Devices to connect"
- Advanced -> SIM Access: be sure that rSAP is enabled
HD2 version info:
- OS: 5.2.21864 (21864.5.0.81)
- Manila: 2.5.19202525.0
For the car I have to check once I'll be in.
Click to expand...
Click to collapse
Hello Binks821,
I believe that I have the same hardware situation like you but I can't get my HD2 started on my VW Passat with the Premium FSE. The problem is, that I can go through the whole "finding and connecting process" and can save the PIN but then the Connection gets lost between the HD2 and the PFSE. If seems that the PFSE can't connect to the Network (E-Plus) but why the BT-Connect gets lost in this case.
Maybe you can help me to get it work. Thanks a lot!
Negropo
Hello everybody,
maybe I found a solution that work for every sap-handsfree-set. I tried the hint was given on the german car forum "motor-talk" for the connection problem between a vw pfse and the htc touch diamond with wm 6.1 or 6.5.
The trick is that you have to disconnect the HD2 from the pfse by manual when the car first want's to connect automatically. You have to go to the BT-Setup to the tab where are the connected devices listed. If you click on the "+" right of the name of the device you should be seen the tab "Remote Sim Access" or in german "Sim-Zugriff". When the car connect's to the HD2you have to stop this by pressing disconnect in the right below corner of the HD2 screen. Then the connection is terminated. Now you have to start the connection manual over the menu in your car. In a VW you have to press only "connect" in the MFA. And then the HD2 should connect without problems. I don't know why it works but it does. Maybe there is someone here who can explain it and find another "automatic" solution for this problem.
Regards Norman
Well, I don't have a VW but an Audi with an rSAP-Adaptor in the middle arm rest. I fear this also doesn't work for me.
The problem is that this Tab "Sim Access" only appears for just one second, so I have no chance to make anything whithin this single second....and after disppearing of the tab "sim access" another tab "handsfree" appears - and stays. So it seems my Audi only recognizes a handsfree profile. I don't know why,
Temporarily I am happy that I still have my HTC Snap, which is working very fine with rSAP
@ Negropo, can you tell me in which thread at motor-talk you found that?
Thanks,
Jolig
Hi guys,
rSAP works fine with my Audi A4 BTA. I made the HD2 discoverable for any device and I activated the SIM access in the HD2 BT settings. Then I start searching for Bt device on my Audi BT and initiated the connection with the HD2.After inserting the 16 character pin everything works fine.
By the way ... the connections seems to be very stable. With the Touch Diamond I had from time to time connection interrupts where it was necessary to reset/restart the Touch Diamond again.
Best regards,
Matthias
@ Matthias,
"BTA" means that you have the built-in phone with rSAP, right? Is it a brandnew A4?