Improved stop detection and distance calculation with a speed sensor

Marcel K shared this idea 8 months ago
Collecting votes


First of all, Locus is amazing, keep up the great work!

I use Locus to record rides with my road bike and noticed two things:

First, it seems like the total distance of a ride is computed with the recorded gps location points, is that right? If so, I would love to see that the distance is computed from the speed sensor data (with the comulative wheel revolutions parameter and the wheel circumference). This has obvious advantages: The distance will be much more accurate, and the update frequency of the gps points could be reduced without sacrificing accuracy, while saving battery life.

Secondly, I noticed that the stop detection seems to depend on the gps location, correct? If that is the case, one might get an unreliable stop detection if the gps is inaccurate, and a lot of false positives. In my option, it would be a much better solution to use the speed sensor for the stop detection. If the wheel stops spinning, the bike is standing and the activity should be paused. Again this has advantages: It is way more precise than using gps location updates, and thus delivers a more accurate moving average speed.

Again, I really love Locus, but these two improvements would make it the perfect cycling computer for road cyclists, making the accuracy of the track recording competitive with high end dedicated cycling computers!

Comments (7)


For the second idea: How is the accelerometer sensor is measuring speed? is it based on wind exposure? Also, there is an option in the setting to record only when moving .


Sure I know that option, but it uses the accelerometer, so it is relatively prone to false positives, I noticed that on my rides. The accelerometer might work okay, but I think if you already own a wheel speed sensor, it is the best possible way to detect movement.


Oh by the way, if I say speed sensor, I mean something like the wahoo wheel rpm speed sensor (, it's a device that you put on your front wheel axle to measure how often it turns. If you know your wheel circumference, you can use it to accurately measure your total cycled distance, and with that your accurate average speed. When only using the gps location points, the total distance tends to be too low and the average speed too high as a result.



I did a comperhensive review of bike sensors and their support and features in majority of bike/sport tracking apps. My findings:

Technically, Locus is than any of these, of course to beat Strava in their "social" features is a challenge. But there are 2 problems , exactly the 2 what what Marcel says:

1. Sensor speed over GPS speed prio:

Also using Wahoo speed sensor, it has ANT+ and BluetoothLE

Once the sensor is connected, the speed measured by the bike sensor should have the priority over GPS speed and should be used to compute ridden distance. (If you use Bike speed sensor, you are obviously on the bike, so you care about how much you have ridden on the bike....). I know you can display both GPS speed and sensor speed, but ATM the distance is computed from GPS speed? Or trackpoint distance? . Sowieso it is not acurate.

2. Autopause. Here I understand there is "track time" and "Track time (movement)" which could do the the trick. However only in case the (movement) is computed exclusively from speed sensor. Otherwise it does show inaccurate information if you use train or something in the middle of the trip... I did not have opportunity to test this yet...

Both of the features (1. speed sensor prio, 2. Autopause based on speed senosor) are implemented correctly in major competitive apps (RideWith GPS, MapMyRide). However for all of these Locus has advantatge: you have profiles. Therefore you are able to set different biking profile for your Mountain bike and different for City bike... So fix the two above and you are the King ;)


Ok let me describe the desired bike use case (I am frequent biker, using Mountain bike, 2 city bikes and the scooter (kolobezka)). ATM none of the tracking apps can do the scenario completely (shame on you Strava etc..) , but Locus is closest:

1.I put the phone in the rubber holder on my handlebar (with NFC tag), the app detects that this is my Mountain bike, turn on "Mountain bike profile" and start tracking. The profile MTB has specific settings:

a) Autoconnect "Speed sensor MTB" device

b) Autopause (track only movement) - speed sensor based: (tracking is paused/"Track time (movement)" not being measured when the speed sensor does not report any speed > 0)

c) Use "Speed sensor MTB" to compute distance. (Maybe there "Track distance" and "Biking distance" measured separately? )

2. I start biking and ride some distance (eg. 10km)

3. I stop biking and get on the train / bus / mountain lift (eg. 5km) Bike wheel stops turning, sensor reports 0 speed , Movement Time stops being measured. Distance measurement stops (or just new data field "Biking distance" ?), however the track still is still being recorded, to see where I have ridden with the bike/bus/lift.

4. I get off the transport, start biking again, the measurement start again.

5. At the end of the trip I see how much(time, distance) I have ridden on the bike, how much was my ride in total(time, distance).

6. I can use my trips to compute aggregated data such as : how much I have ridden on MTB, City bike, etc...



+1 , same story like Marcel nad Jan . I was using Wahoo , now using Garmin speed sensor. I would love to see a profile where you can measure "biking distance" which is computed only from speed from speed sensor X time.. I do mountain biking , using ski lifts and downhill, if you forget to pause Locus one, the recording of the entire day is useless.. I know many people that use MapMyRide (full of adds) only because of this feature... Please fix it


Wahoo Bike speed sensor, same problem, please add disstance computed from sensor speed, that matters