Skip to content

Intermittant Bluetooth problem

Featured Replies

This is different to the current thread - Mine is a May 2011 170 Elegance, and I use an IPhone 4S. The phone connects OK to the Blue Tooth, and I can make outgoing calls OK, but sometimes the phone rings and it doesn't connect to the BT, or I notice 'Missed Call' on the display (I have the phone on a charging holder down by the heater controls.)

When it does this, after the call has finished it then displays 'Connecting to Iphone' on the Maxi-dot and reconnects itself. Sometimes it says 'no paired phone found' then it may reconnect or I have to turn the ignition off and start again to get it to connect.

I have taken the car into my local dealer, they have 'tested' the system and say there is no fault showing on the computer, BUT they say the operating system on the phone - 5.1 - is not compatable with the BT - they say the BT 'is an earlier version' - I suspect they are refering to the GSM version (GSM II) - the phone is GSM III, but I am assured by the experts at Carphone Wharehouse that the phone is backwards compatable. - Further research tells me that the phone is in fact BT 4 (GSM IV), but still backward compatable.

I also have an HTC Sensation which is BT 3 (GSM III ) that does exactly the same thing, so I don't think it's the phone. I in fact have the BT switched off on the HTC so there is no chance of conflict.

The dealer says there is nothing he can do, until SUK upgrade the GSM version, but he will report the problem to them. The Iphone 4S is incidently on the 'approved' list of compatable phones.

Any suggestions????

Mine does that too sometimes, although I'm running a Fiscon bluetooth module

Make sure the wi-fi on the phone is off. I had the same problem until I learned that the wi-fi should be off when using the BT connection.

Thanks for the tip 175GDY. I have had a similar problem with my old Android on the Dutch KPN. Got a new 4s today and hope not to have the same with it.

I missed a call today, I realised the phone was vibrating in my pocket, but nothing showing on the car.

I stopped and looked at the phone (a brand new iPhone 4S) and it showed connections, but would not change from iPhone to Skoda BT.

Never ever had any BT problems with my old iPhone 4, just other issues and Apple swapped it for the 4S yesterday.

The 4S was fine for the rest of the day.

I never turn BT or WiFi off. Battery lasts about a day. I do use it a lot as it is my work (and personal) phone.

I hope I don't have any problems with this as my Yeti is a November 2010 built car.

PS. Are Skoda ever likely to upgrade the GSM module? I would have thought it was a hardware issue and not software.

Never had a problem with having both Wifi and bluetooth on with my Android phone.

My previous phone, a Samsung feature phone, didn't have Wifi but would drop the bluetooth connection at random intervals for no discernible reason. Samsung tech support offered a number of increasingly implausible and obviously erroneous excuses for this behaviour. It would have been simpler if they'd just come straight out and said: the phone and the car don't like each other but we don't really know why - sorry.

I think bluetooth is one of those things a bit like HDMI: there's a standard, and everyone adheres to it, but some manufacturers manage to adhere to it in a slightly different way to others. The result being that it generally works, but certain equipments can sometimes take a dislike to each other for no readily apparent reason. Even two different models from the same manufacturer can be built with different bluetooth modules, so just because the old model worked is no guarantee that the new model will.

My iPhone 4 works fine with the Bluetooth. I never switch off the wi-fi and the pairing works perfectly every time.

I would suggest that the missed calls may be purely because you were in an area where coverage for your particular network is patchy.

My iPhone 4 works fine with the Bluetooth. I never switch off the wi-fi and the pairing works perfectly every time.

I would suggest that the missed calls may be purely because you were in an area where coverage for your particular network is patchy.

The missed call: wrong description by me.

I could feel the phone vibrating in my pocket, but it wasn't displaying on the maxidot. I pulled it out of pocket once i had stopped, I answered the call but could not hear anything which was when I realised something was not right. it was stuck on iPhone as an audio source and not the Skoda BT source and I could not change it.

The iPhone 4S BT seems to be different to the iPhone 4 BT.

I will keep an eye on things, as I'm in the car loads and people are always ringing me.

I never had a problem with the old iPhone 4.

I have taken the car into my local dealer, they have 'tested' the system and say there is no fault showing on the computer, BUT they say the operating system on the phone - 5.1 - is not compatable with the BT - they say the BT 'is an earlier version' - I suspect they are refering to the GSM version (GSM II) - the phone is GSM III, but I am assured by the experts at Carphone Wharehouse that the phone is backwards compatable. - Further research tells me that the phone is in fact BT 4 (GSM IV), but still backward compatable.

I also have an HTC Sensation which is BT 3 (GSM III ) that does exactly the same thing, so I don't think it's the phone. I in fact have the BT switched off on the HTC so there is no chance of conflict.

I think you're making a mistake in equating the Skoda GSM model number with the Bluetooth version. No phone is "GSM II" or "GSM III" - it's purely a designation used by Skoda for their mobile phone integration modules. Bear in mind that "GSM" is a set of mobile telephony standards and has zip to do with Bluetooth. The Skoda "GSM" modules are phones in their own right; they just use Bluetooth to "borrow" your phone's SIM in order to make and receive calls, and to download its phonebook information.

Different phones can have different Bluetooth versions but all the later versions of Bluetooth are designed to be backwards compatible with the earlier versions. For example. a phone with Bluetooth 4.0 should be able to connect to and communicate with a device running Bluetooth 2.1, although they will only be able to interoperate using the Bluetooth 2.1 feature set. Equally and/or contrariwise, having the "right" Bluetooth version is no guarantee that a given phone will work with the car's GSM module. My Samsung and my Android phone are both Bluetooth 2.1: the Android phone works fine in the car but the Samsung randomly drops the Bluetooth connection.

The main difference between the Bluetooth 2.1 and Bluetooth 4.0 standards is that Bluetooth 4.0 includes the high-speed data transfer capability which was introduced with Bluetooth 3.0+HS (which uses Wifi for the high speed data channel), and adds the Bluetooth Low Energy protocol intended for very low power applications. Neither of those features are relevant to the use of a mobile phone in a car. (Not even for audio streaming: Bluetooth 2.1 phones can stream music perfectly well, so the high-speed data channel isn't needed for that - and the car's audio system doesn't have the necessary Wifi capability anyway).

The iPhone 4S BT seems to be different to the iPhone 4 BT.

The iPhone 4 has Bluetooth 2.1 whereas the iPhone 4S has Bluetooth 4.0 - but Bluetooth 4.0 is designed to be backwards compatible with Bluetooth 2.1 so it should work. If it doesn't then I suspect that you've fallen foul of an implementation glitch by Apple, Skoda or both. It might be the case that a firmware update for the phone could fix it, but I wouldn't be too hopeful (my Samsung has had several firmware updates but they've never fixed the Bluetooth problem).

If Millstone's dealer said that the iPhone's iOS version was the problem then said dealer was talking rubbish. The iOS version does not affect the Bluetooth version that the phone has - that's down to the hardware. Bear in mind that both the iPhone 4 and the the Iphone 4S can run iOS 5.1, but an iPhone 4 running iOS 5.1 still only has Bluetooth 2.1.

Far to much technical information going on in this thread for my confused, simple mind....

I did have a problem the other week where I actually had an incoming call(rare) that came through on the bluetooth, the car 'rang' but when i pressed the answer button it refused to answer the call, just continued ringing out. I just assumed it was a phone issue, as on occasion the bluetooth has caused the phone to turn off. Oh well, the call in question was just a woman calling to moan so no big loss....

I have had several apple devices including an iPhone 4s, when they are first set up new it is worth giving them a few off, on power cycles as they seem to get a bit confused for a few days untill they settle down.

My 4s works well with my 2010 yeti apart from synchronising the call lists which it won't do.

  • 2 weeks later...

I have realised that there is a problem with my IPhone 4S and the GSM11 in my Yeti

When the connection works, I can make external calls through the car, but when I receive a call the call is put through to the internal iPhone speaker and not the car.

There is a lot of chatter on the Internet about this, and it is not just Skoda, but most manufacturers are affected.

But some phones seem to work fine and some others don't.

I'm now running iOS 5.1.1 which I downloaded today. Still no change.

I will find an old phone and connect that and then delete from the car and repair and see it that works after a reset of my iPhone.

I have reset the iPhone several times now & re-paired the phone, but not deleted in the car.

If all else fails, a call to apple will be next.

The MY13 press release states GSM II software update, assume this would apply to all installed modules too?

If so maybe this will help.

The phone connects OK to the Blue Tooth, and I can make outgoing calls OK, but sometimes the phone rings and it doesn't connect to the BT

Just to clarify one point, the phone should be connected to the car by bluetooth all the time. So if an incoming call rings on the phone and not on the car's BT module, that means that the phone had already disconnected before the call came in and you hadn't noticed. Do you have the "bluetooth bong" (the noise it makes when a phone connects or disconnects) turned off? You'd know if you had, since it has to be done using VCDS - you can't do it through the maxidot.

I think it's unlikely that the incoming call caused the phone to disconnect. The BT module in the car effectively "borrows" the SIM card in the phone, so an incoming call would be picked up by the BT module in the car. If the phone disconnected from the BT module at that point then most likely the call would be dropped; I can't envisage a way that the call could be passed from the BT module to the phone, especially with the BT connection down. (On the other hand, I suppose a sequence of events like that might explain why you are getting "missed call" indications without being aware of a call having been received.)

Either way, the simple fact is that your phone and the car's BT module do not get on well together. I've no idea how to fix it I'm afraid. (I gave up and bought a new phone when I had BT connection drop-outs.)

Just to clarify one point, the phone should be connected to the car by bluetooth all the time. So if an incoming call rings on the phone and not on the car's BT module, that means that the phone had already disconnected before the call came in and you hadn't noticed. Do you have the "bluetooth bong" (the noise it makes when a phone connects or disconnects) turned off? You'd know if you had, since it has to be done using VCDS - you can't do it through the maxidot.

I think it's unlikely that the incoming call caused the phone to disconnect. The BT module in the car effectively "borrows" the SIM card in the phone, so an incoming call would be picked up by the BT module in the car. If the phone disconnected from the BT module at that point then most likely the call would be dropped; I can't envisage a way that the call could be passed from the BT module to the phone, especially with the BT connection down. (On the other hand, I suppose a sequence of events like that might explain why you are getting "missed call" indications without being aware of a call having been received.)

Either way, the simple fact is that your phone and the car's BT module do not get on well together. I've no idea how to fix it I'm afraid. (I gave up and bought a new phone when I had BT connection drop-outs.)

Sorry.

I wasn't explicit enough.

The phone connects to the car on start up every time.

I can make a call and speech is output through the car speakers.

I receive a call. The phone rings. I can not answer it through the MFSW.

I stop. Take phone out of pocket, or wherever it may be.

The phone is still ringing. I press Audio selection. iPhone is selected, whereas it should be connected to Skoda_BT.

The Car still says that it is connected even though it is routed through to the iPhone.

This is a problem that many people and cars have, not just me. It is to do with apple's latest implementation of Bluetooth. -

I managed to find another phone today and connect that and delete my phone & profile, so that I could then re-pair my phone with the car from scratch.

Once I had done so I made a call without problems. I then asked somebody to ring me back, and it worked properly. But I had not turned the ignition off and disconnected the phone. I will get my wife to ring me later when we go out and see it it is working.

  • Author

Just to clarify one point, the phone should be connected to the car by bluetooth all the time. So if an incoming call rings on the phone and not on the car's BT module, that means that the phone had already disconnected before the call came in and you hadn't noticed. Do you have the "bluetooth bong" (the noise it makes when a phone connects or disconnects) turned off? You'd know if you had, since it has to be done using VCDS - you can't do it through the maxidot.

Yes I did have it, but like everybody else it frightened the life out of me/Mrs M, so I had it disconnected via VCDS

I think it's unlikely that the incoming call caused the phone to disconnect. The BT module in the car effectively "borrows" the SIM card in the phone, so an incoming call would be picked up by the BT module in the car. If the phone disconnected from the BT module at that point then most likely the call would be dropped; I can't envisage a way that the call could be passed from the BT module to the phone, especially with the BT connection down. (On the other hand, I suppose a sequence of events like that might explain why you are getting "missed call" indications without being aware of a call having been received.)

I understand what you are getting at BUT... I have had the phone ringing, with an indication on the maxidot that it is connected, and still it doesn't ring/connect via the BT!! Though it will then tell me it is connecting !!

Either way, the simple fact is that your phone and the car's BT module do not get on well together. I've no idea how to fix it I'm afraid. (I gave up and bought a new phone when I had BT connection drop-outs.)

Unfortunatly I don't have the option of changing the phone (It's my company one), I may try using my Android (HTC) phone, and diverting all calls to it, problem is then when I want to make an outgoiung call I have to start swapping the BT connections, that and the phone books are different.

Perhaps I'll have a moan at Apple (or O2 who supplied the phone) But I agree with another poster that my dealer is talking rubbish, It's just the effort of going back and trying to explain to their 'techi' who admits he doesn't understand iphones (& his computer says there is nothing wrong with the BT module !!!!)

Sounds we have the same issue millstone.

The car did not ring earlier even though the phone was connected when I tried it this evening. :no:

If you feel it's a software bug at Apples end then you need to report via their bug reporter.

You need to register for a free developer account first.

My tin can on a piece of string works perfectly.

My tin can on a piece of string works perfectly.

wrapped around your neck.......... :rofl:

Now which corner was it you are supposed to inhabit? :giggle:

Well it didn't work yesterday.

So I changed the name of the phone on the iPhone 4S and did a hard reset.

I deleted the profile in the car and on the phone the re-paired from the car.

I then rang the iPhone and it worked. I switched off and removed the key, the switched on again. I rang it again and it worked. Hopefully all is working now correctly.

  • Author

Well it didn't work yesterday.

So I changed the name of the phone on the iPhone 4S and did a hard reset.

I deleted the profile in the car and on the phone the re-paired from the car.

I then rang the iPhone and it worked. I switched off and removed the key, the switched on again. I rang it again and it worked. Hopefully all is working now correctly.

Keep us posted !! I'll try this tomorrow... any suggestions as to what to re-name the phone (just in case it's easily offended and refuses to work again) ???!!!

any suggestions as to what to re-name the phone (just in case it's easily offended and refuses to work again) ???!!!

On the assumption that this isn't a joke: you can call it anything you like - the car doesn't tell the phone what it's called on the Maxidot, so the phone won't know. It's a just a tag that appears in the list on the Maxidot which is easier for the user to understand than the Bluetooth address. So for example, I can tell which phone is connected to my car because one is called Blackberry and the other is called Defy+. Much easier than trying to work out which one is which out of 30:69:4B:EF:C3:9F and E0:D7:BA:A7:3E:45.

Yes call it whatever you like.

It did not work today. I could not persuade it to move off iPhone onto Skoda_BT in the audio selection choices.

I think a call to Apple is in order now. When I have the time.....

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.