I have completed more than 1000 bike rides with Strava in the last few years.  I record them with my Samsung A13 phone.  This has always had reliable GPS that accurately records my rides.  I also record the rides on my watch, which doesn’t have as good GPS accuracy as the phone (it “wobbles” a few metres occasionally), but it has the benefit of recording heartrate.  If I go somewhere new and want to create a couple of new Segments I do it using the Activity as recorded on the phone, as the GPS data is better.  To avoid duplicating the recordings, I usually delete the phone version after a day or so (unless I forgot to tighten my watch-strap which causes the heart-rate to under-read and be meaningless !).  This methodology has worked well for several years.

However, for the last 3 rides I notice that all the recordings on my phone show small spikes about every 15 seconds or so (for the whole ride) that make them unsuitable for using as a basis for new Segments.  The watch data is unaffected and it now means the phone overstates distance by about 5%, compared to the watch.  Here’s a pic of a section of a ride from a couple of weeks ago (recorded by phone)…

...and here’s a recent ride on the same route with the “spikes”…

Has anyone else experienced anything similar ?  More importantly, are there any suggestions for getting the phone GPS quality back to where it used to be ?

I’m not aware of any other phone changes.