Hi I recently bought a 2014 Superb Elegance 2.0 tdi. The Bluetooth module that is installed is the 3C8 035 730 D, which I am aware is capable of both rSAP and HFP. An important point of my problem is that I am with the 3 network on my phone contract.

 

My problem is that in my previous vehicle, a 2012 Octavia L & K, which had the B revision of the same BT module, all was well in the world and it connected to the module in rSAP without issue. Now in the new car, it will connect to rSAP upon initial pairing of the phone but then afterwards steadfastly refuses to connect via rSAP. It HAS to be something to do with the 3 network, as my daughter in law is with T mobile and her identical Galaxy S4 connects straight away and is a good stable connection. If I put my 3 network sim into her previously stable phone then it will not connect, If I then put her T mobile sim into my phone then I get the same stable connection. We have 4 Galaxy S4 phones within our family, and we have mixed and matched all the phones to test. All the phone show the same behaviour with the 3 network sim in them and also are stable with the none 3 sim.

 

It is not a faulty sim card as I have persuaded 3 to give me a new sim and the problem remains, also my son and my wife are with 3 and the car is showing the same issue.

 

My son has just retrofitted the C revision of the same module into his car and all is well.

 

After some researching of the issue my son found this info:

 

According to Ross Tech’s Bluetooth Module info (http://wiki.ross-tech.com/wiki/index.php/Telephone_Retrofitting) the ‘D’ rev is the same as the ‘B’ and ‘C’ with the addition of Wi-Fi – all 3G modules so no issue relating to the Three network not having 2G transmission as there is with the Original revision, (3C8 035 730), which I know is only 2G and won’t work with Three. The only other difference it does show is that the ‘D’ rev is HT-5 whereas the ‘B’/’C’ are HT-4. Does anyone know what effect this difference will have and whether that is the cause of my issues?

 

PLEASE does anyone have any helpful info on this issue, surely I am not the first to experience this. I could try to get a B revision module again but would rather keep the D with the additional Wi-Fi  capability.

 

Awaiting your wisdom with everything crossed ;-)

 

Ray

Not a solution but as a data point, my HTC One M7 on three happily connects to my 3C8 035 730D using rsap without issue.

 

I'm really not sure what would cause this kind of issue as I'd only expect the phone to impact to rsap compatibly, not the sim card :/

Hmm thanks Langers for that info, that only serves to confuse me even more,

 

In light of langers information would there be a friendly member on here close to Jct 31 of the M1 who is on the 3 network but does NOT use the Samsung Galaxy S4?

 

You may just have started me down the road to resolution Langers. As the phone connects using the T mobile sim I didn't even consider that it could be the combination of the S4 and the 3 network. I am willing to try any sensible solution, :-)

 

Thank you again

 

ray

If it helps......

I have used the following phones all on Three with no problems using RSAP.

Nokia 6700

Nokia N8-00

LG G2 mini on Jelly Bean android 4.2.2

LG G3 on lollipop android 5.0

Skoda module "B" type

Thanks DCC I had no problem on the B revision, only now I have the D revision

Ray

Just a thought here as it sounds like the combination of the Three network and the phone is the issue. The phone itself definitely does support rSap but in Three mode the rSap seems to be getting switched off after initial pairing. I reckon that is happening in the settings for the Bluetooth pairing itself - you can check these when the phone is disconnected from the car by going into Settings on the phone then selecting the Bluetooth option (not the yes no thing but select Bluetooth itself) and looking at the settings for each pairing there. Make sure the tick boxes are ticked for phone and media connections if not already.

Adam

Thanks Adam. I will try that.

Sent from my GT-I9505 using Tapatalk

My other half has a Note 3 on Three.

 

It connects fine but roams onto Orange as my Bluetooth is 2G only.

 

Phil

I have a note 3 on three and have the same problem when it's connected to premium on my 2014 superb it says 999 call only

If I change it to hands free it works faultlessly

• Took delivery of Superb in December.
• Blackberry on 3 would not connect.
• Eventually by 'unticking' rSAP box on phone everything worked. 

Shanco

Hopefully i would like to find a resolution and be able to use the 3 network and on rSAP

Sent from my GT-N8010 using Tapatalk

Hopefully i would like to find a resolution and be able to use the 3 network and on rSAP

Sent from my GT-N8010 using Tapatalk

 

Do you have another phone you can try your Sim card in to rule out the phone?

 

As I said before my other half's phone works with rSAP but he gets text messages saying he's on a feel at home network and the Columbus displays Orange as the network.

 

Phil

Did anyone get any further with this? I have been running a "B" module with my Note 4 in RSAP just fine with no problems, I then recently bought a E module (latest) as it supports Wi-Fi as I really miss the data connection but love RSAP as it uses the roof antenna.

After connecting as soon as you select Wi-Fi it just hangs and the only way to get it going again is to reset everything!

 

I think 3 have sort of block on a phone Sim being used in anything other than a phone, it probably doesn't recognise the car as a phone, especially with a unlimited data plan they think it would be put into a mifi device which I suppose RSAP is a bit like

Edited 25 May, 201511 yr by silverdales

Not convinced this is a network issue.

 

My HTC One M7 GPE with a three SIM works flawlessly with both D and E rev modules for rSAP and WiFi. Although I did need to root and install rSAP from the market.

 

Some people have reported success by ordering a replacement SIM's, mine is from Nov '14 if it helps. Then again as you've had it running happily running in rSAP mode previously then I doubt it's that.

I'm now also on Three.

 

I currently use a rooted Nexus 4 with rSAP. It works and uses the Orange network (my Bluetooth module is 2G only).

 

Three block tethering if your plan doesn't include it. But the car should be able to connect and turn the wifi on just that when you try to browse to a site you will be presented with a Three web page.

 

I get 4GB per month of tethering allowance. I hope to upgrade my Bluetooth module soon (as the other half has just ordered an iPhone) and will give wifi hotspot a go.

 

Phil

I am still struggling on with this, I tried another phone a S3 with 3 sim, really I need to try another service provider.. I will buy a O2 sim PAYG and try that. I found it strange it works for some and not others.

Someone mentioned there are only 2 manufactures of SIM cards and maybe 1 was different from the other.... How can a card be identified? To be able to recognise testing of each type? ..any ideas

By the way my sim is from Sept 14 and the S3 was from Feb 15 ...but both sims could be same manufacturer I guess as were supplied direct from 3

Hi,

 

I am having the exact same issues with a Galaxy S4 on the three network., It connects via rsap but shows no network on the columbus system. I have also tried my sons S4 on EE and it connects no problem at all. This is using an older module 5KO 035 730B. I have rooted the phone and installed rsap app etc etc but still have the same issue with three. Wife has the same phone on three with a later sim and she also gets the No Network problem. I have a new module on order 3c8 035 730E which i still doubt will solve the issue. I am beginning to think I may change network when contract is up for renewal. GOOD LUCK with yours too. I will let you know what happens with the new nodule when it arrives.

Hi Wens66 my S4 on 3 works perfectly on rsap on the B revision module and also on my sons C revision. I cannot connect via rsap on anything later than the C module.

Sent from my GT-I9505 using Tapatalk

Hi Blackray

 

That sounds about right !!!  Guess the latest module I have ordered wont solve my issues either. Its all a bit of hit and miss it seems on the modules etc with the phones on three.

I am still no further forward and will let you all know what happens.............

I had been experiencing the odd issue with mine on the Nexus 4.

 

It would connect to Bluetooth and the phone signal would drop etc but then on the stereo/maxidot it would just never get a signal.

 

I had to reboot the Nexus 4 and connect again to solve this so I'm not convinced it was a network issue as such.

 

I think with mine it's to do with the fact that my module only works with 2g networks. Do any of you have one that supports 3g networks?

 

Phil

If anyone is local I'm more than happy to have a quick play as my set up is working. Assuming you also have a microsim we can swap bits over to find the problem.

You're very lucky Simbo! It's all very strange as everyone have different problems..it hangs on my wife's S3 but I will try my daughters Vodafone S4 later

.that may through some clues!

I wouldn't mind meeting and up swapping but I'm in the south ..do you have access to the VCDS coding? Any plans to go to the national meeting in a couple of weeks?

My phone is not rooted...how to do this unlocking shop?

No you do it yourself.

 

It voids any warranty you may have in the phone and does require a certain technical knowledge/ability usually.

 

Here are the instructions for the S3. Just be warned that if you do something wrong there is the possibility of bricking the phone (meaning cannot be recovered) but most of the time if you go wrong you can recover the phone but you need to know what you're doing.

 

I usually like to have a rooted phone as it has other benefits like ad blocking apps, ability to remove bloatware apps etc.

 

Phil