hi dose anyone know why my 3 phone cant be used on my superb II it connects but with no signal . been through settings found "3" "O2" and others but says 3 not allowed . why?

My Virgin phone won't work in my 2010 Superb II either. Suspect it's the unit beneath the driver's seat that needs updating.

 

Dave

depends on phone model also i believe 3 as the network rsap won't work

I had rSAP on 3 working perfectly. If anything, once I moved to O2 it's slightly worse as it falls back to 2G then drops the internet connection more often.

From what I can tell, it depends on phone, sim and Bluetooth module. Any one of the three can cause you issues but I expect the most common is the phone.

it finds 3 but says not allowed . i have a new samsung 5

Will be the same answer I gave on that other thread with someone else having problems.

 

I bet your module doesn't support 3G and as Three is purely 3G/4G then a 2G only module will not work.

 

I've found it far easier with a module that support hands free then it works with any phone and network.

Thats the main reason why when i retro fitted my bluetooth kit i bought the newest & best module so it won't need changing for many years to come & it should be fine if i change phone & network in the future, I'm just a bit miffed that iPhones won't work on rsap.

3 works fine on my 2013 Superb II.

Sent from my iPhone using Tapatalk

Iv always found Samsung phones to be the problem when connecting to Bluetooth. Some connect but some don't. I had an iPhone on the 3 network and it connected no bother

Sent from my iPhone using Tapatalk

I have had "ongoing" issues with rSap connection... I have now confirmed, or seems to confirm it is all down to SIM card/network... 

 

With my Samsung Galaxy Note 4 using my contract Vodafone it will always connect to Premium rSap ok, but will disconnect for no reason then connect either to normal handsfree or rSap or maybe I have to connect manually... I have found now, if I reboot the phone before I use it in the car and clear all the cache for the apps it is more reliable... 

 

There is no set time, it can go for days, on the other hand can do it twice in a trip.... 

 

The dealer replaced that module which made it better but not perfect..

 

I then tested my old Galaxy S3 with a PAYG "VIRGIN" SIM... Not one single issue, worked perfect for 4 months!

 

So I suspect that it is either SIM cars from different providers or just networks in general... 

 

It drove me mad, but now I seem to know why I may look at changing to "VIRGIN" when my contract expires later this year... 

Edited 11 April, 201610 yr by stuarttunstall

As said above, 3 doesn't work with the older '2G' modules, but also has issues with the later 'wifi' modules. Myself, my dad and mum all use 3 network with Samsung phones and have no issues connecting via rSAP - the best modules for conmsistant stable connections seem to be the 3C8 035 730 B/C (i have a 'C' and both my parents are running the 'B'). I think the issue with the wifi enalbled modules is that 3 see it as a Wifi dongle, therefore prevents connection via rSAP, and reverts to HFP (my dad tried the 'D' and 'E' revisions with the same result).

As said above, 3 doesn't work with the older '2G' modules, but also has issues with the later 'wifi' modules. Myself, my dad and mum all use 3 network with Samsung phones and have no issues connecting via rSAP - the best modules for conmsistant stable connections seem to be the 3C8 035 730 B/C (i have a 'C' and both my parents are running the 'B'). I think the issue with the wifi enalbled modules is that 3 see it as a Wifi dongle, therefore prevents connection via rSAP, and reverts to HFP (my dad tried the 'D' and 'E' revisions with the same result).

 

It's much more convoluted than it just being D/E revs are incompatible with 3, I say this having used both of these modules (rSAP and WiFi enabled) with a HTC One M7 on 3.

 

Personally, I think it's more likely to be down to phone and it's software version. There are also numerous reports that replacement SIM cards from the same operator have helped.

It's much more convoluted than it just being D/E revs are incompatible with 3, I say this having used both of these modules (rSAP and WiFi enabled) with a HTC One M7 on 3.

 

Personally, I think it's more likely to be down to phone and it's software version. There are also numerous reports that replacement SIM cards from the same operator have helped.

 

When the dealer replaced my module under warranty to try to fix the issue, my old Galaxy S3 using a "Virgin" SIM works perfect with the "E" module... (I did say a "3" SIM" above, now changed), My Vodafone Note 4 is a bit of a pain at times.... 

As stated by MarkTB if the 3C8-035-730-B or 3C8-035-730-C module is used then rsap connects everytime without issue, any later D or E with wifi it will no connect. if anyone doubts this solution I am happy for anyone to come to my place and try your 3 network phone on my Bluetooth. 100% certain it will connect to rsap without issue

 

 

Ray

 any later D or E with wifi it will no connect. 

 

Both those modules worked perfectly for me on 3 including the WiFi hotspot functionally

Both those modules worked perfectly for me on 3 including the WiFi hotspot functionally

I tried both the D and the E version and i just could not connect at all

Sent from my GT-N8010 using Tapatalk