HOWTO : Get rSAP working with the Columbus RNS510 using a

[Agerbundsen]

This seems like a silly question, and does not relate to a Superb, but a new Yeti on order with the Columbus included. The dealer is also recommending a Parrot installation to get a hands free telephone function.Now the question: Does the Columbus provide both sound output from the telephone an input from a (built-in?) microphone? The manual does not seem clear on that point.Do you have experience with the quality of the telephne connection?My telephone currently is a Nokia 3120 Classic.My present Octy has a Pioneer nav system 900 something with a separately installed microphone on the A-pillar.Thanks

[grobster]

Has anyone else noticed that the compatible phones list given in Skoda literature is mega outgated!! Even in the Januray 2010 literature. I've looked at most of the phones on GSM Arena an many were discontinued in 2005/6/7 etc.

Can anyone recommend a current generation Nokia, Blackberry or HTC which works well with the Columbus etc?

Current phones which I've got my eye on is the Nokia E72, Blackbery Bold 9700, HTC Hero or HD2....does anyone have these working with the Columbus?

Cheers,

[Zaxus]

Hi, I hope you can help me. I have a Skoda Superb 09 plate with a HTC Touch 2 phone. I have tried the procedure on the following link (http://briskoda.net/forums/topic/117938-howto-get-rsap-working-with-the-columbus-rns510-using-a-non-compatible-mobile/ ) as I cannot seem to find anything for the Bluetooth GSMIII (UHV + rSAP) and I am getting the following error message when I tick the box next to the “Remote SIM Access” on the SAP Settings : “Unable to start Remote SIM Access Server”. I have installed the cab file numerous of times but keep getting the same error. I am keen to get this phone working in the car. Help please!!

I contacted Skoda and all they told me was they were waiting for a new listing of compatible phones!

[erniem]

Hi, I hope you can help me. I have a Skoda Superb 09 plate with a HTC Touch 2 phone. I have tried the procedure on the following link (http://briskoda.net/forums/topic/117938-howto-get-rsap-working-with-the-columbus-rns510-using-a-non-compatible-mobile/ ) as I cannot seem to find anything for the Bluetooth GSMIII (UHV + rSAP) and I am getting the following error message when I tick the box next to the “Remote SIM Access” on the SAP Settings : “Unable to start Remote SIM Access Server”. I have installed the cab file numerous of times but keep getting the same error. I am keen to get this phone working in the car. Help please!!

I contacted Skoda and all they told me was they were waiting for a new listing of compatible phones!

The touch 2 works, I have the RSAP add on installed, but you can't configure it. You need to also go into the bluetooth settings, scroll down to the advanced settings and expand it, and the scroll down and turn on Sim access. once done make sure you recycle the device.

[Zaxus]

The touch 2 works, I have the RSAP add on installed, but you can't configure it. You need to also go into the bluetooth settings, scroll down to the advanced settings and expand it, and the scroll down and turn on Sim access. once done make sure you recycle the device.

Thanks Erniem, I have tried all what you said but it still does not connect. I get to the point of inputting the 16 digit code then it stays on "connecting" for a while then shows "initialising" but it then goes back to the find device screen on the dashboard. Any other settings on the phone need changing?

[erniem]

Thanks Erniem, I have tried all what you said but it still does not connect. I get to the point of inputting the 16 digit code then it stays on "connecting" for a while then shows "initialising" but it then goes back to the find device screen on the dashboard. Any other settings on the phone need changing?

Try recycling the Columbus unit itself by holding the <> and Info buttons at the same time for a few seconds

Also check to see if the units are paired on the phone and if so set the bluetooth connection for SKODA_rsap is authorised on the Touch 2

[Zaxus]

Try recycling the Columbus unit itself by holding the <> and Info buttons at the same time for a few seconds

Also check to see if the units are paired on the phone and if so set the bluetooth connection for SKODA_rsap is authorised on the Touch 2

Hi, don't have an INFO button on my console/display. Have already checked the phone settings you stated and all set. Still cannot connect. Appreciate your help though. It seems like it wants to connect but fails after a while.

[mannyo]

I have been playing with my Superbs BT kit today, and have successfully got 2 phones working ok.

My company Nokia 6021 just worked straight out of the box, paired and downloaded the phonebook perfectly.

My HTC Touch Diamond 2 needed the software on this thread installed, once done the phone paired and I can make/receive calls no problem, however I cannot get it to download the phonebook from the phone. I just need to workout if its possible.

[bluroom]

Hi, Thanks for this thread - very useful - got my new Superb to work with my blackberry 9700 Bold without any problems.

Cheers

[TorqueDude]

Just got my Nokia 5800 working with some software from the Ford website...

Ford Connectivity

[simon superb]

Can someone help me set up my superb and blackberry pearl?

[malcfcook]

Can someone help me set up my superb and blackberry pearl?

Scroll back to my post #50 it worked for me. But not tried it with a pearl.

[mannyo]

The HTC Touch Diamond 2 with the latest official WM6.5 firmware (March 2010) kind of works ok, but you cannot select to download the contacts from the phone. Leaving it on sim card it works fine, but you dont get the phonebook. Switch to phone memory and it keeps on disconnecting and reconnecting. You can tell if you have the latest firmware as the homescreen has 3 application launch buttons below the clock.

[Apoelara]

I have an HTC touch HD. It is connected nicely with my Superb II.

The Bluetooth set up of the car has three options:

1) to get the phone contacts,

2) to get the phone and the SIM contacts and

3) to get the SIM contacts.

The problem I have is that when I choose 1 or 2 I’m getting a message from the card saying that it is unable to download the contacts. I can understand that it has to do with the phone contacts.

Is there any way of getting the phone contacts as well?

The second problem is to activate back the HTC when I disconnect it from the Superb. I have to put it to flight mode and then back to normal. Any ideas for this?

Thanks

[razrobinson]

So frustrating....

Blackberry 8250, Superb with Columbus.

Search finds the device - enter the 16 digit pin - and it just hangs there - even though the bluetooth light flashes on the BB.

(BB is configured on our network - so has a alpha password - not a sim pin - is that it?)

Oddly, after disabling security the transfer contacts works (well they appear on the console display).

Services available oin the Skoda_rSAP:

Voice Gateway

OBEX Object Push

My old Nokia works perfectly!

[Apoelara]

The only problem is still have is the one that I have noted in other post as below:

I have an HTC touch hd.

The problem that I have is that I cannot get the sms's back to my phone when disconnected from the car. i.e. I tried to copy them, the car display says copied to the phone but then I cannot see them on the phone. I have tryied with my friend's htc touch 3G and I can have the sms's back to the phone.

Anyone can help me found the correct settings?

Thanks a lot.

[Phish]

So frustrating....

Blackberry 8250, Superb with Columbus.

Search finds the device - enter the 16 digit pin - and it just hangs there - even though the bluetooth light flashes on the BB.

(BB is configured on our network - so has a alpha password - not a sim pin - is that it?)

Oddly, after disabling security the transfer contacts works (well they appear on the console display).

Services available oin the Skoda_rSAP:

Voice Gateway

OBEX Object Push

My old Nokia works perfectly!

I have the same symptoms - I am following the sequence in post #50 - i.e. setting the blackberry to listen before asking the phone to search - the pairing sequence starts on both machines but eventually the car times out with cannot connect. The phone remembers the partial connection as Skoda rSAP, with the same services as you. When I tell the phone to transfer the phonebook, the car partialy receives one vCard - I can examine it, but not save it.

Most frustrating!

I wonder of someone with a working Curve 8250 could have a look at the other settings on their phone - is your bluetooth encrypted? are other bluetooth services selected, or just SAP? Is there an overall security policy on your Blackberry - mine has a work imposed security profile?

I too have an old Nokia working perfectly, but that does not help me get my work done.

Any help gratefully received, thanks.

2 days later.. to edit my own post (well no-one else is listening!). I have made some further progress, I bumped into a work colleague who has the same phone (an 8250 Curve) but on O2, whereas I am on Orange. In theory the two phones are subject to the same work security policy, but I thought it was worth the attempt and dragged him down to the car park.

His 8250 connected to my Superb with no problems - after the 16 digit pin which I entered in the blackberry I got a prompt on the Superb to enter the sim pin on the maxidot display, which you do one digit at at time, followed by [save]. Then everything works - the address book from the Blackberry transfered into the Columbus and I can make calls from either the MFS or the phone button on the Columbus.

So I need to find out what the difference is between these two phones - I cannot believe that it is a difference between Orange and O2, but in case it is can those who have made a successful connection with a Blackberry please reply stating which carrier they use, and if their BB is subject to corporate security settings?

Thanks again.

Edited 2 June, 2010 by Phish

[J6PTP]

As everyone knows, the Columbus RNS510 unit requires an rSAP compatible phone in order to use the full functionality of the phone system in the car. If, like me, you�re someone who doesn�t own a Nokia or one of the few other phones that are designated as �compatible�, then this guide is for you. It is designed to show you how to get pretty much any phone running Windows Mobile connected to the Columbus, irrespective of whether it is deemed compatible or not. This won�t work for iPhones or Blackberry�s, it�s strictly a Microsoft Windows Mobile fix. I can�t absolutely guarantee it will work with every phone, but of the ones I�ve tested, it has worked with all of them so far.

This guide is aimed to be generic, in the sense that whilst the procedures are correct, different phones operate in different ways, and depending on whether you�re using WM Professional or Standard will also dictate how MS have labelled differing tabs/menu�s on your phone. The procedures however are still correct, but you may have to use a semblance of common sense to find some of the menus/programs I refer to in this guide for your specific phone.

DISCLAIMER : This guide is of a semi technical nature. I suggest anyone contemplating using it read it thoroughly first (including the notes & comments at the end of this guide), and if the are unsure of any steps, or do not understand something, please DO NOT do this. There is (very) slim possibility that you could damage your phone following this guide, and whilst I�ve tried to be as thorough as possible in explaining what to do, I cannot be held responsible if you screw up J If after all this, you�re still dead set on trying to get this to work, find a 10 year old kid, and ask them to do it. That way, if it all goes wrong, you can blame them instead of me

Also, whilst it will not invalidate any warranties, if you�re doing this on a company phone, they may have rules in place that state you can�t install software on your device or modify it in any way. Either way, please check first, and make your own decision.

Copyright : None. If it helps anyone, feel free to distribute.

Requirements :

1) That you�ve read the disclaimer, understand it, and accept it.

2) A mobile phone / PDA running Windows Mobile 6.1 Standard or Professional with standard Bluetooth capability. This guide MAY work with phones running WM6, but I haven�t tested it on any, so can�t be sure.

3) Familiarity with how to configure Bluetooth and turn it on and off on your phone (should be covered in your phone manual anyway, but please check first).

4) A PC/Mac/Laptop with internet access to both the Rapidshare & Microsoft websites (www.rapidshare.com & www.microsoft.com )

5) EITHER a) MS Activesync 4.5 (or above), and a suitable cable to connect your phone to your PC/Laptop

OR A storage card compatible with your phone, and the means of copying files to and from it.

Part 1 : Preliminaries and Downloading the required files.

1) First up, backup all your data on the phone. It is highly unlikely you will need this, but as everyone who�s ever installed any software knows, backup first, and then if it all goes wrong, you can at least return to whence you started. If you typically connect your phone to MS Outlook / Exchange, then this will backup up the critical info (contacts / calendar etc), otherwise you�ll need a 3rd party product to do this (a Google search will give loads of possible options)

2) Using your internet connection download the following file from Rapidshare

RapidShare: Easy Filehosting

This is a free to download site, and if you�re not a member you may have to wait a minute or so before you can download the file. It is virus free, but please don�t take my word for it, and as with any files from the internet, I suggest you scan it anyway using your A/V package of choice. As a check, the file is 47.3k in size.

3) In order to speed up the operation of mobile phones, and to reduce the memory used by the device, some versions of WM6.1 do not come with .NET Compact Framework 3.5 installed. This is a requirement for the rSAP installation to work, but unless you�re a geek like me and using a �cooked ROM� (ie, non-standard Operating System that you yourself have installed), chances are you won�t know if you have .Net installed until you try to install the rSAP program and it either works or fails. I would suggest anyone using this guide downloads the .Net framework file from the Microsoft website, and if it�s not needed so much the better. If it is, at least you have it, and can install it. .Net can be obtained here

Download details: .NET Compact Framework 3.5 Redistributable

Part 2 : Copying rSAP to the phone

As with all mobile device CAB files, once it is installed, it deletes itself, so don�t worry about using up initial storage space on your phone.

1) If you have Activesync and intend to use that method, first find the file you downloaded from Part 1, then open the Activesync program, and do the following

Open the Tools menu

Select �Explore Device�

Find the �My Documents� folder on your phone.

Copy the BT_sap.cab file over to the My Documents folder.

Note : If you have a storage card in your phone, you can also copy the file to that as well. As I said, the cab file will be deleted once installed, so as long as you can find it, it doesn�t really matter where you put it.

If you don�t have MS Activesync, or a connection cable, then you can alternatively copy the file to a removable storage card, and then insert that into the phone instead.

2) If you used Activesync, now disconnect the cable from your phone. If not, then you should have already inserted the storage card into the phone.

Part 3 : Installing rSAP

1) Firstly, we want a �clean� phone memory to do this, so I suggest you power off your phone, and restart it. This is the easiest way to clear the phone of any running applications (bubble breaker, Activesync, outlook, internet explorer etc). Whilst none of these should have any effect on the installation, it�s always wise to do this when installing any new application

2) Now run �File Explorer� on your mobile device. Depending on whether you�ve got a PDA or Phone, or are running WM6.1 Pro or Standard this program could be in a number of places. However, it WILL be on the phone somewhere, so if you don�t know where it is, just go through the various menus until you find it.

3) Once FE is open, use it to browse for the BT_sap.cab file you downloaded in Part 1. If your phone has a search facility, and you can�t find the file with File Explorer, you can use that instead.

4) Select BT_sap.cab and run it. You will now be asked where to install �jasjamming BT SAP� (History Note : The HTC i-mate JasJam was one of the first phones to have rSAP capability, and this file has been copied from that device). If you have a storage card, you could install it there, BUT I�ve not tested a storage install, and as the file is so small I would advise always installing it to your device.

Select �Device�, and click �Install�

You should now get the message �BT_SAP was successfully installed on your device� Click �Done� to continue.

If you do NOT get the above message, or you get an error instead, then you need to install the .Net Framework which you downloaded earlier. You follow the same procedures you did to copy and install the BT_sap file, but if you are in any doubt, then the MS Website has comprehensive installation instructions on how to do this. Once you have installed .Net, repeat parts 2, 3 & 4 above to find and install the BT_sap program..

Part 4 : Configuring rSAP

If Part 3 went successfully, you will now have a new program installed to your phone. As with File Explorer, it could have been installed in a number of places, so you may have to hunt around for it. However, somewhere on the phone, there will now be a new icon labelled �SAP Settings�.

1) Open the �SAP settings� program. If Bluetooth is turned off, then you will get a message informing you of this. Select �Yes� to continue, and wait until Bluetooth is turned on (look for the Bluetooth icon in your status menu).

2) You should now be presented with a page with a checkbox labelled �Remote SIM Access�. Click the checkbox, and select �Done�

3) Now find your Bluetooth configuration settings on your phone. Usually it is available within the �Comm Manager�. You need to configure 2 things within the Bluetooth section.

The first is make your phone �Visible� (this is so the Columbus unit can see the phone when it searches for new devices). This is frequently a checkbox.

The second is to disable the �OBEX authentication� requirement (this is to allow the Columbus unit to connect to the phone - The Columbus unit already has passkey requirements and enabling OBEX simply causes the unit to fail to connect). Again, this is usually a checkbox.

If in ay doubt, your phone user manual should have instructions on where to find these two settings, and how to configure them.

Part 5 : Connecting your phone to your Columbus unit.

Right, final part (the easy bit )

The instructions in the handbook are reasonably comprehensive and most people should be able to connect the phone using those. However a quick recap follows.

1) Ensure Bluetooth is turned on, you have the SIM Access protocol on, OBEX is disabled, and the phone is Visible to other devices

2) Start the car, and select �phone� on the display. Now select �Search for devices�

3) After 30 seconds or so, your phone name should be listed on the display (if you�re doing this in a crowded multi storey, you may see other devices as well. Just make sure you find yours). Click �connect�.

4) The phone will now indicate that the Skoda_rSAP wishes to connect to your phone. The display will give you a 16 digit PIN to enter (4 key presses of 4 consecutive numbers). Type this PIN into your phone. If you�ve done it correctly, the phone will now report it has successfully connected to the Skoda_rSAP.

5) If you have a PIN on your SIM card, the Columbus display will now prompt you for a PIN. Use the scroll keys to select the correct digits, and at the end, select SAVE (if you just do OK, then every time you try to connect the phone to the car, it will prompt you for the PIN).

6) If you�ve done all the above correctly, the phone and car will now be connected to each other, and the Columbus will ask to download all you contacts from the Phone (the phone will prompt you do you wish to allow the Skoda to download the contacts). As the aim of this guide is to give the car access to your phone, I suggest you say Yes . Depending on how many friends you have this could take between 2 and 15 minutes. (a 400 contact database took about 4 minutes, whilst a 3,500 took about 20)

That�s it - You now have an rSAP capable phone connected to your car.

Final Comments.

There are shortcuts to some of the above procedures, and anyone who knows a lot about PC�s / Mobiles can use them. However, these instructions have been written to enable as many people as possible, with minimal experience, to install the rSAP feature. I apologise to anyone who feels �babied� by either my tone of writing or length of the instructions, but I didn�t write them for you (if you�re that smart, you�ll have worked this procedure out anyway )

Side Effect & Solution : There is one potential side effect to this procedure, which I have seen on some phones and not others. I don�t know whether it is as a result of shoe-horning a solution into the phones or just a quirk of the Columbus system. When you connect the phone to the Columbus system, in order to use rSAP, the phone is switched off (the Columbus unit has a GSM transmitter in it, so doesn�t need the GSM part of the phone), putting the phone into a form of �flight mode�.

The side effect is that when you leave the car, and disconnect the phone from the Columbus unit, the GSM phone aerial won�t switch back on again (as I said, it�s not all phones, and I don�t know why it does it). The solution is before turning off the engine, open the �SAP settings� on the phone and turn the SIM Access off. This will disconnect the phone from the unit. Now, switch the phone itself off (ie, power down). When you power the phone back on again, SAP is off, and the phone works perfectly. To reconnect the phone to the unit, simply re-enable SAP, and it will connect automatically.

At the end of the day, whilst annoying, personally I can live with it, and consider this a better solution than changing phones

Hope this helps, and if anyone has any questions, comments or problems, please post and I�ll try to answer as best as I can.

[J6PTP]

Just set this up on my o2 XDA Orbit and Columbus in my new Octavia Elegance estate .... works fine auto connects and disconnects ok when the ignition key is removed ( stays active on the phone until the ignition key is removed ) .... so I'm well chuffed with the bluetooth and new motor.

Thanks everyone

[ianbk]

I am very dissappointed my BB pearl does not work with my Skoda Superb II :'( this rSAP thing is a real bummer....

I have tried several ways (and the suggestions on here) and the car see it as a BB 8110 then tells me it is not compatible.

Edited 7 July, 2010 by ianbk

[neilrz]

Hi, Thanks for this thread - very useful - got my new Superb to work with my blackberry 9700 Bold without any problems.

Cheers

Can you tell me what settings you used on the Bold 9700? Mine connects then immediately disconnects.

[Alien8d]

Just a quick update on my original post (blimey, was it really 18 months ago I did that !). I've noticed (as have some other posters here) that with some HTC model phones, if you try to download the contacts (ie, using rSAP), then phone will connect / disconnect on a regular basis, and is effectively unusable.

A workaround I found was to use a spare Nokia phone I had lying around. Procedure was

Insert SIM card into Nokia, and (in my case) using Outlook, update the Nokia phone with my phone list.

Create a connection to the Columbus with the Nokia phone

Download your contacts list to the Columbus when requested

Turn off the engine, and swap SIM card to the HTC phone

Now, create a new pairing with your HTC phone, keeping the same connection name (which should be fine, as it's the same SIM card).

When the HTC connects, it should now be able to view the contacts you downloaded with the Nokia, despite having swapped phones.

Voila, you now have a correct contacts list, using your HTC phone instead. Yes, it's a pain, but as anyone who's used the GSM III setup knows, it's basically designed to work best with Nokia phones, and other systems are invariably a botch job.

Edited 14 July, 2010 by Alien8d

[BATTY]

Has anyone fitted/tried the RSAP Upgrade kit from Fiscon?

I have a Skoda Superb 2 (1 year old). I got my BBerry bold working okay last night, today it just did not want to work, flattened the battery trying all day. V V V V very frustrating.

the kit is here : http://www.fiscon.co.uk/fiscon-bluetooth-kits/vw-skoda-rsap-upgrade-kit-new.html

I would like to know if it works okay (they say it does) before splashing hundreds, it's a work phone so can scam them for some of it.

[vincefra]

just to let everybody know.

On the current models (2011) all Bluetooth car kits (BT I, II & III) include HFP protocol, enabling the function to nearly all BT enabled phones.

The rSAP car kit (BT III) has currently also HFP protocol next to the rSAP. In the case of usage of an HFP compatible phone, the car kit will not provide the same functionality (e.g. external antenna function, sms messaging, ... ) but will function comparable to any other non rSAP car kit.

[Jono76]

Just a quick one!!

Has anyone managed to connect a HTC Desire to a Columbus in a Superb II???????