I'm hoping someone can help me understand the following.

I have a 2009 Ford Galaxy Ghia and the clock in the instrument Binacle will display the same time for hours or even days and then randomly catch up to current time which will then stick on the same time until the next update. 

Any clues ?

1 hour ago, Gaffer411 said:

will display the same time for hours or even days and then randomly catch up to current time which will then stick on the same time until the next update.

Do you listen to the local radio station ?

Sorry for delay in replying, the car is currently in Spain and it has an aftermarket android head unit. We tend to use the internet radio via Android Auto. I didn't realise that's where the clock got its time from so I'll try listening to FM radio and see if that fixes it. 

Thanks as always for your help.

 

 

So finally got to try the FM theory but to no avail. I'm guessing something needs pairing radio/canbus etc. but not sure how to proceed.

UPDATE.

So when I installed the android head unit it wouldn't switch on until I connected a 12v+ trigger using the cigar lighter socket which meant the unit came on every time I opened the door and stayed on for 10 minutes or so after the car was locked. Not ideal but at least it was working. I now realise the reason it wasn't switching on without the trigger was because the canbus wasn't communicating properly. I went down many rabbit holes looking for the solution and eventually removed the instrument cluster and re-soldered the main connector. A revelation!!! The radio and cluster display now display the same time and I've removed the trigger wire and the unit turns on and off as it should via the canbus.

Sincere thanks to everyone who has helped me resolve this problem.

Unfortunately I now have a new puzzle involving battery drain.

Codes U0300 U0306 U0416 U0126 and P060D are my new enemies, I removed the fault codes but some or all them came back and drain continues. I'm struggling to see the wood for the trees! All the codes seem to be low voltage related but can't work out which module or device is harbouring the actual fault

As always any ideas would be welcome.

Any thoughts