Ride Control App - Freezes

Oscar56

Active Member
Until today I have only used my iOS Ride Control app to check battery levels. Today I attached my iPhone to the handle bars and went for a spin.n I am riding a 2020 Phantom E+ Pro.

For the first 2 minutes the app seemed to record distance and cadence properly. If I stopped pedalling then within 2 seconds cadence showed zero, when I started pedalling again then cadence rate showed values within 2 seconds.

But after two minutes the cadence value and speed froze, although the distance seemed to continue to compute. I stopped for 10 minutes and put the app on pause. After I restarted the app it showed data correctly for about 2 minutes then froze again.

When I got home, after a 35 minute ride, I ended my ride on the app then it crashed. When I opened it up again I had to re-enter my email and password. Today's ride and one of my previous rides are gone.

I never really intended to use the app for more than battery checks, system health and cadence (my LBS informed me that a cadence of ~80rpm reduces the strain on the motor). I will be using my Polar watch for ride details.

Will deleting and downloading the app again solve these problems or is it just a buggy app?
 
Sounds like it lost it's BT connection.
I've had absolutely no bugs with three of them on two phones.
 
Tried again today, while running concurrently with Cyclemeter which I have used since 2011. RideControl crashed again. I think I will set the app aside and limit it’s use to check the battery level at the end of my rides.
 
Tried again today, while running concurrently with Cyclemeter which I have used since 2011. RideControl crashed again. I think I will set the app aside and limit it’s use to check the battery level at the end of my rides.

What is 'cyclemeter' and why do they need to run concurrently?
Does the app run properly by itself?
 
Cyclemeter is an iOS app that has been around for many years. Records the usual data, time, distance, speed etc. I have previous rides stored on my phone since 2011.

I ran it concurrently with RideControl to ensure that at least one app would work properly. My previous rides with RideControl were less than satisfactory.
 
Back