Related
Hi,
I have a HTC Touch 3G:
The phone is recognised (the name), it seems to pair ok (had to put in a 16-digit PIN), but then the car (Passat 2008) kit cannot connect to the phone for some reason.
Is there any solution for this subject?
Regards,
SpiderXman
I believe, you have to turn on the rSAP-Profile in the BT section of your Jade.
The VW vehicles have a BT-Unit, that only works with mobiles, that have the rSAP (remote SIM Access-Profile) enabled.
You know, how to enable it ?
Start-->Settings--> Bluetooth --> SIM Access
Hope this helps.
Greetings from Cologne,
Arniebirdy
Thanks for your help,
However I have done this procedure without success.
SpiderXman
Emanuel Ferreira said:
Hi,
I have a HTC Touch 3G:
The phone is recognised (the name), it seems to pair ok (had to put in a 16-digit PIN), but then the car (Passat 2008) kit cannot connect to the phone for some reason.
Is there any solution for this subject?
Regards,
SpiderXman
Click to expand...
Click to collapse
Hi/ I have the same problem with BMW X5 2004. paring is OK, but it dosn't work. it looks like connect and then disconnect (on phone screen headset icon appear and disappear). SIM access anable but no sucses
With touch 3452 it was not a problem. HTC support team told me that it is a conflict with BT kit on BMW. Now I see not only.... What to do???????
For most of the things discused here no one has paid.
For the things people have paided for go to the garage, i know i would!
Tom Lenferink said:
For most of the things discused here no one has paid.
For the things people have paided for go to the garage, i know i would!
Click to expand...
Click to collapse
You know you can, but how to resolve this issue ???? I think any payment can't, can it?
Hi,
using Jade's BT SAP with BMW 3 series (E91).
Works like a charm, except one issue: names in BMW phonebook appear sorted by first name.
In Jade its sorted - as it should be - by last names.
No solution found until now.
Anybody an idea?
Thanks
@ConsultantR
Try this for older BT Kits: http://www.jetwaremobile.com/
ConsultantR said:
Hi/ I have the same problem with BMW X5 2004. paring is OK, but it dosn't work. it looks like connect and then disconnect (on phone screen headset icon appear and disappear). SIM access anable but no sucses
With touch 3452 it was not a problem. HTC support team told me that it is a conflict with BT kit on BMW. Now I see not only.... What to do???????
Click to expand...
Click to collapse
Hi there,
I have a similar problem with my Volvo S40 2009. My Jade and the car connects each other but every 15-30 seconds the connection cuts off. It is very annoying while talking to someone, just in the middle of the conversation the radio starts to run again, since Jade loses connection to the car.
Is this some kind of configuration or setup issue? Any help?
I had this on / off problem too.
It was a fault in the phonebook contacts (some signs are obviouly not allowed in this bluetooth stuff (e.g. / or ")
So i moved all contacts to a folder, that wasn´t synchronised and that worked fine. Afterwards i added this removed contacts back step by step and was able to identify the problematic ones.
The easy way instead is to set up the phonebook to SIM only and copy the most used contacts to the SIM
Regards Quirlsen
Quirlsen said:
I had this on / off problem too.
It was a fault in the phonebook contacts (some signs are obviouly not allowed in this bluetooth stuff (e.g. / or ")
So i moved all contacts to a folder, that wasn´t synchronised and that worked fine. Afterwards i added this removed contacts back step by step and was able to identify the problematic ones.
The easy way instead is to set up the phonebook to SIM only and copy the most used contacts to the SIM
Regards Quirlsen
Click to expand...
Click to collapse
Thanks for the hint Quirlsen. Is it only the Name and Surname lines, which I have to correct? Otherwise it would be impossible, since I also have the Windows Live(Msn Messenger) contacts in the Contact List.
By the way is there a way to remove those Msn Messenger Contacts from the phonebook? They just popped up after I logged in once to Windows Live.
To be honest, i don´t know.
I´ve exported my whole contact list to csv, cleand it up with Control+H and imported it back (i had to add all picvtures afterwards
Your Win Live prob you could solve by defining different phonebooks for sync with phone and other stuff.
Sadly enough I have noticed that the xperia X1 does not like my premium volkswagen carkit. As used in passat or audi or skoda superb, bmw, Mercedes, etc.
I have an RNS-510, but have also tried it with a RNS-310. Both having the premium carkit in it. Also called carkit III.
It uses rSAP to enable transfer of contacts and phone settings control.
I have tested with a nokia N95 and it works perfectly fine with that after you enable the remote sim access profile. Also known as SAP.
Sadly enough, the X1 refuses to connect. The carkit just says the phone is not compatible.
Anybody have any clue what to do?
Maybe a custom ROM which does have this functionality? Or a tool that can be added?
u r talking about remote sim access right?
my rom (cmex absolute touch) got an option to enable it under bluetooth setting (connections)
Yes or You use this little cab! Works perfectly with VW Golf VI PRemium Handsfreekit. I used the smaller file, but if it dont works try the bigger one!
In the bluetoothsettings you should find the sap profile after the installation, and in the programs a small utility to activate it. the Xperia himself has no SAP Profile!
wow!
I definately came to the right place! I will try this out tommorow first thing and let you know if it works!
Thnx's again. Also considering your rom now achmed20, because I believe this is quite basic functionality which should have been there in the first place!
As I said, I'll let you know if this worked!
not working yet
Well, that helped, a bit.
I get to the connection screen, have to enter the 16 digit pincode and after that the car just says connecting, and stays doing this for a minute or two and then just says failed or not compatible.
So I'm a lot further, but it isn't working yet! I'm thinking because of all the things I have tried, I might have broken it somewhere, but unsure how or what.
Thinking of maybe flashing it with a different (custom) rom, to see if that might fix the problem.
Anyone have any other advice?
no experience with the kind of trouble your having but if you want to try off on a fresh start, i would do a hard reset, then install the cab fix that was recommended.
still not working
I just installed the cmEX absolute TOUCH rom and did a hard reset after that.
Enabled rsap on the last tab of bluetooth and the car says its connecting and just does that for a long time (after entering pin code). Sadly enough, it just times out.
Anybody have any clue what could be the problem? I have the feeling we are allmost there, but there is just a little thing causing it to time out.
rsap even says it's connected to my skoda and everything.
From what I can gather, the cmEX absolute TOUCH rom is based on a touch HD.
more testing!
Okay, from what I have been able to gather, the following is going on.
The carkit is trying to log on in a frequency that it cannot handle.
I have been able to connect the carkit, download the address book and make calls with my Xperia now. No problems what so ever....except one. I was using a SIM from a collega whom has a different network!
I use t-mobile and my collegea has kpn/telfort. Doing more research, I have learned that kpn/telfort and vodaphone use the 1800 band frequency. And that t-mobile uses the 900 frequency.
I am not entirely certain at this point that this truly is the real problem, but, my phone works, my carkit and car works, so all the software bits are in sync, but only using a different sim. Rebooting the phone, changing nothing but the sim, makes it completely broken again!!
I'm using a RNS-510 with the Skoda/VW premium carkit. If anyone is able to shed some light on this and what possible fixes could be, I'd really like to hear!
I have been looking (and mailed) if a fiscon unit could potentionaly fix this problem. They also have units which intergrate with the system.
But I'd rather find a software solution, obviously. Sadly enough, manny cases can be found where people have problems, often, with no solution. This problems is *NOT* specefic to the Xperia, I do realize that now, since the new ROM, rSAP is working just fine.
more complex then ever....
Okay, things just more complex then ever before.
My x1 using a HTC touch HD rom base and rSAP from HTC (default in rom).
KPN sim = works and can call
Vodaphone sim = logs in but carkit crashes on trying to connect to cell towers. But car connection functions.
T-mobile sim = connection to carkit never gets finished.
I'm totally lost. Using a friends N95, all the sims work flawlessly.... which makes me even more clueless, because the carkit reads the sim data and then connects using it's own radio to the cell network.
Please, advice? How can this be fixed? Is there a different version of the HTC rSAP software available maybe?
The plot thickens again.
Using my sim card in my X1, not working. Original ROM, Original ROM + rSAP extensions, cooked rom from touch HD with native rSAP. Just non-functional.
Using the exact same phone, without the t-mobile sim but with the KPN sim, works perfectly, no problems what so ever.
Using an older Nokia E50, both sims work flawlessly, also my t-mobile sim.
This leads me to one conclusion and that is that the HTC rSAP implementation is seriously bugged.
Anyone have any idea on how to proceed? Somewhere I have read that the HTC's wouldn't handle 3G or UMTS sims and only use older ones. But, using the KPN sim I connect to 3G and it works. Also the nokia E50 of N95 can use any network and it just plain works. There for that statement is wrong in my opinion and it is caused by buggy software of HTC.
Anyone have a good idea on how to proceed? Lots of people having this problem and buying nokia's, but for no real reason other then buggy software it seems.
I really like my X1, and payed a lot of money for it, so I really need this to start working.... Please assist and help, also people with a diamond or other HTC, using the same software.
sadly enough, no progress
Did some tests again today, but sadly enough, no progress yet.
I'm going to try and get a hold of a Touch Diamond and a Touch HD and see how those preform with my sim. If my suspiciouns are correct, they will also fail, making this a combination of bad software with bugs with certain sim's.
That is the conclusion I am faced with right now... sadly enough, no idea how this can be remedied.
Are there developers whom might be able to write a reliable rsap implementation or will HTC ever come with a working version?
What do you guys think?
Sonyericsson will not provide SAP for the Xperia. Thats the point....
Been in contact with support
I have been in contact with Sony-Ericsson support and they tell me they cannot make the X1 compatible, because it is not just software.
Off course, to me this sound like total bull****, seeying I have allready had an raap connection with the X1. But this was either using HTC software add-on's or using a rom that was based on the htc touch HD.
Sadly enough, I cannot work without this functionality... and thus will be forced to sell my phone and buy... a nokia.... not bad, since I have had nokia's all my life. But I really really do not eNjoy beying forced to do so.
But everybody has known that the xperia has no SAP Profile... in every test, in every Datasheet you can see it! Why you buyed an xperia?
Wrong order
I orderd the x1 around the same time I orderd my new car (Skoda Superb II 2.0 TDI Ambition Business line ).
The car came with a carkit that can only do rSAP, but it is very very nicely intergrated with a external antenna, full adress book acces, etc. etc.
To my amazement, there was no rSAP on the phone, while all current high end models do carry support for it. Thus thought that a simple program or rom fix would provide it.... sadly enough, while some stuff works, it is very very flaky.
So it's a combination issue, off course I realize that. But I'd rather replace my phone and sell the x1, then having to change the carkit piece in my car (it is far more expensive). And still, I just cannot believe that such a basic function, is not in there.
Especially because it is made by HTC, which do carry this functionality!
So the problem was created by having both products in the same time frame. And my reluctance to believe such a high end phone would not carry this protocol.
From closer reading though. It seems that the x1 (with a custom rom) is not at fault here. If my speculations are right, any htc device with rsap from factory even has a big change that it is not going to function. Also reflected by my tests.
Using a HTC touch HD based rom on the X1, rsap is added and functions brilliantly using a KPN sim. Vodaphone works sometimes and crashes the carkit now and then and using a t-mobile sim, it does not work, at all. Since I have a t-mobile business account... it doesn't work at all for me.
I have not been able to get a hold of a Touch HD or Touch Pro to test if these problems also form on that phone, but will do so when I get the change.
So for now, even the HTC software seems to be bugged and thus I have formed my conclusion that my best option is to go back to nokia (which I have used for about 10 years now). The x1 is great, but not beying able to call in the car.... that just isn't going to work for me.
The new N97 looks pretty decent....
I have a jetta 06 tdi with mfd2(dvd version rev c) and skoda (kufatec) bluetooth modul installed by myself. I can do a Synchronisation of the Phonebook with Names and Numbers , dialed and missed calls , incomming calls with Names and i have a option to accept or decline a Call from the fis display , using my Multifunction Steering Wheel. Everything working perfect with my Xperia x1i.
Hmm
Most likely that module is a fiscon module or an older part of skoda. Am I correct?
The fiscon does not use rsap and older premium carkits from VW also did not. But their newest carkits included in the passat CC and skoda superb II are rsap only.
Quindor said:
Most likely that module is a fiscon module or an older part of skoda. Am I correct?
The fiscon does not use rsap and older premium carkits from VW also did not. But their newest carkits included in the passat CC and skoda superb II are rsap only.
Click to expand...
Click to collapse
Im not sure we can post a direct link here to another website , but there is what im using in my Jetta : http://www.kufatec.de/shop/product_....html/XTCsid/9f268df051bdc7806c7825cc426d606c
Old Version
Ah, yes. That is an orginal skoda part, but it is the older version from the Superb I and not the Superb II. That uses the other profiles and not rSAP.
touch HD behaves just the same
Hi everybody.
I had the chance to test both X1 (rSAP from cabs in post #3, thanks by the way) and HD (native rSAP implementation) on a VW touareg premium car kit and I must say they suffer from the same problems: most of the time the connection is established, but immediately drops and enters an endless loop of connection/disconnection, where everything can happen: car kit crashes, phone crashes, vodafone goes bankrupt, etc.
What hurts the most, though, is that very rarely and randomly, the connection with X1 is firmly established and everything, for unknown reasons, starts to work fine. This drives me crazy, for it would be a lot easier to cope if the feature wasn't available full stop.
Nonetheless, this makes me think a solution must exist somewhere, but I'm too much of a noob to find it...
Hope this helps, byebye.
I picked up my Audi A4 last week, and the MMI + telephone connection high works to a limited degree with the Touch HD.
It correctly identifies the Orange network, 3G, varying signal strengths, and can dial out and receive calls, but I don't have access to other functions such as the phone's last dialled calls, missed calls, phonebook/contacts list (biggest problem!), etc.
I'm using the original 1.14.405.3 (22273) WWE rom which came with the HD, but has anyone had any success with the MMI by using other roms?
Guess this does not help, but I had the same problem with a brand new mercedes C200 and Dutty's 2.8 firmware...
Cheers
[update]
maybe this thread helps a little: http://forum.xda-developers.com/archive/index.php/t-456900.html
some say it worked after upgrading to 1.19...
personally I think bluetooth has always been ****ty
Pretty interesting that a version of Duttys made it stop working, at least it shows bluetooth compatibility is affected by different roms. Thanks for the link, it seems the JetWare program might work too, but updating the rom is a last resort for me since I've never done it before. I'll try JetWare first, and if it stops working after a few days, I'll go for the rom update. Thanks again!
You'r welcome! I am on Duttys 3.0 right now but never had a car again with bluetooth so couldn't test
If you never flushed your HD - try! You will be massively excited I swear
Compared to the original firmware the phone was unusable slow and had a ugly user interface... I can really suggest Duttys 3.0! Once you are through the process of flashing it's quiet easy...
Cheers
Heh, maybe I'll go for the regular handset option for my next car, seems like it'd be less of a headache. Anyway I upgraded my HD to 1.19 and there was no change in displaying phonebook contacts, so I decided to flash Dutty's v3.3 and it still doesn't work properly...but I'm liking Dutty's a lot, definitely glad I upgraded to it. Thanks for suggesting it!
I'm back to square one again though, so if anyone else has some advice/experience with getting it to work, I'm all ears
Anyone at all?
Is the Audi new or used? If it is used you might have an older version of the MMI software. Good luck getting Audi to do the upgrade for you. Check out the forums at Audiworld.com.
I have an A6 and have the same problems.
Have you tried Jetware? I used that for awhile but I found I would rather use a headset now.
I use a Touch Pro with my 09 A4 and I have the same problem. Everything works great except when it comes to syncing the phone book. After pairing the phone with the car, a message pops up asking if I'd allow the car to access my contact. I'd answer yes, but then nothing happens.
For some unknown reason, I was able to upload the phonebook once. I don't know what I did differently that time but the phonebook mysteriously showed up in the car memory. However, the next time I started the car the phonebook was gone.
Hi everyone. My HD works fine on my 2006 Audi A8L. After initial pairing with the MMI (default pairing code is "1234") you have to wait a little while and the phone book and recent calls pop up. In the Phone > Setup of the MMI I selected only to use phone memory.
One issue I have is that the 150 contacts I have are somehow displayed in 2 iterations of the alphabet, each showing only a half the contact list.
Also good to know. Pairing with Audi's MMI is only possible the first 5 minutes after you turned the power to the car on, ie. turning the key one notch, or starting the engine, so be sure to have your Touch HDs bluetooth on already.
Audi's Bluetooth phone features are on a phone by phone basis, Audi have a list of all the handsets that they have tested and the features that are available using that phone and the firmware for the phone that it needs to produce those results.
I work for Audi so if there's any questions I'll do my best to answer. (I work in parts)
I have 2 TP2 both with Vodafone UK WM6.5 stock ROMs.
Have just tried to send pictures between them but get the message "Device does not support a suitable service to perform this operation"
I can send to an old sony but when i paired the TP2s it didnt give me the option to transfer filec for some reason?
Any one know if there is a solution or if this is something i will not be able to get round?
I'm also having all sorts of crap with bluetooth from connecting and not connecting to having to disable and enable all the time to get it to work again.
Havnt got it to work at all, never had a problem with WM6.5. strange they see each other but wont send and recieve
I have a bluetooth function in my Volvo. Worked as a charm with the O2 Live of my wife and my HTC TP.
Since I have the TP2, I can't get it to work. Tried to pair them from both sides and everything seems to work, until I want to call or get a call...
On dashboard screen I can scroll my contacts, but when it comes to call, I see the calling and connecting, but NO sound!!!
Quite frustrating, as I drive alot around.
Had this with the WM6.1 and hoped this would be resolved with the 6.5 (changing back to the original MS BT stack), but no...
Anybody fresh ideas or work-arounds?
Just spoke to HTC, they are unaware of any problems but he is going to get a couple of phones to try them out then get back to me so hopfully there will be a solution soon?
I am having a similar problem with the ATT Tilt2 version and my 2005 TL. Everything connects just fine, but if I try to make a call it just disconnects. If I delete and re-pair the phone it will work until I leave the car. Sometimes rebooting the phone also makes it work. I seem to remember an issue with my Kaiser early on and HTC put our a BT update. I have also reported this to HTC via the web form but haven't heard back yet.
Same here, was able to receive files from an i900 Omnia but wasn't able to send files to this i900 Omnia! Really strange!
Havnt heard back yet but have also just noticed other devices can not find TP2 even though i can find them.
Have made sure my device is visible and all bluetooth is on, trouble is i dont know anyone else with this phone to compare but as i have 2 bought months apart and they act the same im asuming its a fault with software and hoping theres a fix?
My problem is a little different, if I try to use activesync through bluetooth, my headset disconnects, which is pretty stupid.
I really wonder why the hell did they change the bluetooth stack from microsoft, giving us a fancy bluetooth manager interface but crappy performance / less features.
Any ideas or fixes? Cant seem to find any
I found the issue with mine... for whatever reason the BT while showing connected will not place a call while the phone is locked. I always lock my phone so I don't make calls and create bogus contacts in my pockets. I had Wn6.5 on my 2 yr old Tilt (TyTn II) and this wasn't an issue, nor was it with 6.0 and 6.1...
Anyone experienced this or know how to disable?
igo keyboard and mouse
tilt 2 bluetooth conectivity would allow igo keyboard and mouse connect to it software, cant get them to work.
any sugestions
It's not a good sign that Jet Blue doesn't work with the TP2 bluetooth stack.
any one off u have have tomtom installed if u do that can be the prob i have a tilt2 and with tomtom installed i coulnt use bluetooth take a look at a fix i made just incase that is ur problem
http://forum.xda-developers.com/showpost.php?p=4822359&postcount=44
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?