2013 pre-facelift Yeti Elegance. Connected ok to older Nokia 115 but reads out "not possible to connect" or some such message on MaxiDot when attempting to pair the Nokia 220. Any ideas? 

My recollection is that sometimes perseverance pays off.

I guess others phones have been deleted.....?

Could be the age of phone related to car. My 2010 Yeti was fine with my phone when bought, but would not work when phone was upgraded, and no solution found at the time. Changed the car in 2014 and the phone then just worked perfectly

13 hours ago, awfabia said:

2013 pre-facelift Yeti Elegance. Connected ok to older Nokia 115 but reads out "not possible to connect" or some such message on MaxiDot when attempting to pair the Nokia 220. Any ideas? 

 

Morning :-)

I think you will find it is the software on the Nokia phone that is incompatible with the car.

 

I recently bought two Nokia 216 phones to use in our Yeti and now our new Karoq. Whilst the Bluetooth version on the phones is (I think!) the latest one available. The software that drives the phone is peculiar to Nokia. In my case , its "Windows Series 30+". This results in only certain facilities of the phone being able to be used. The most annoying of which is that the Phone Book (contacts) only displays phone numbers! No Name and no picture!

 

I tried putting your vehicle / phone combination into the Skoda Compatibility checker [LINK = https://compatibilitylist.skoda-auto.com/ ] and it unfortunately shows no compatibility whatsoever for the 220. Perhaps you might like to try it?

 

It appears that this software has issues with a number of different manufacturers and that you and I have fallen foul of this irritating problem. 

 

Sorry to be the bearer of bad news. Chin-up, not the end of the world but annoying nonetheless.........Tony

 

Edited 1 September, 20187 yr by Great Yeti

At a guess, the Nokia 115 supported rSAP but the Nokia 220 doesn't.

 

Annoying, for a while Skoda/VW fitted bluetooth modules that only worked with rSAP enabled phones which could be causing your issue...