Hi, I am getting  three or four messages on the maxidot each day which reads "unknown number, call ended". The Yeti has a Bolero radio and is the SE L model 110BHP diesel. I have the mobile phone (Samsung galaxy a70) connected by Bluetooth and by 12v socket for charging.

The phone shows no missed calls, and when the message appears on the maxidot, no message or indication shows on the phone. I have tried moving the charging lead to the USB socket but the message still occurs.

Any ideas to help please? Not a major issue, but it is getting a bit annoying!

thanks,

Iain

Try fully disconnecting the phone from the car, not just physically, but unpair the Bluetooth connection, delete the phone from the Bluetooth list in the infotainment system and the car from the phone's available Bluetooth connections list, and start again from the beginning.

 

Turn the phone off and on again.

 

Finally, pull the fuse for the radio to reset the Bolero...

 

 

Essentially a full system reset.

 

Edited 16 January, 20206 yr by silver1011

Thanks for that silver1011, I will pull the fuses tomorrow morning when it it is light, no. 13 under the bonnet and no. 8 in the dashboard.

Iain

TBH, it feels more like a phone issue.

 

I expect an app is making sounds or notification sounds but the phone BT stack isn't dealing with them well and it's presenting as calls to get the audio out.

 

Might be worth putting the phone in aeroplane mode and enabling only bluetooth to see if it's still happening.

I was thinking similar.  Some apps, like Google Maps, send their notifications as phone calls rather than BT audio, so that the receiver will interrupt whatever it is playing to play the notification.

Thanks to everyone for your replies, I did what silver 1011 suggested, and the problem recurred.

Following on from langers2K and from weasley, I have been experimenting  and have found that the problem does not arise if mobile data is not selected on the phone.

I am now attempting to identify which program is causing the problem by trial and error, but my money is on either Sygic  or Google maps.

A factor that also has not helped is that at the same time, I am getting used to my new phone (Samsung galaxy A70) as the old one died last week!

Update - it was the Sygic app that was causing the problem. App removed and all is now working properly. Once again, thank you for all of your suggestions and help.

Iain