After the May 2018 firmware update

Comments

15 comments

  • Official comment
    Beeline Team

    Hi Toby, thanks for flagging this. We're looking into it. Peter makes a good point, which we're also working on. Keep us posted on how your next few rides pan out, and Happy Beelining! 

    Sam

    Comment actions Permalink
  • Peter S

    I've installed the May 2018 firmware update too, and then did a 40 km / 25 mile cycle ride afterwards. The overall distance, time and average speed appears to have been measured correctly (i.e. they're in line with my previous journeys on this route), but the times, speeds and distances for the segments of the trip in Strava seem completely off. Sometimes it claims I covered long stretches with an average speed of just 3 km/h (just over half the speed of my usual walking pace!) which is clearly false. But it also claims I hit a maximum speed of 78.5 km/h which again I highly doubt because I was careful to control my descents with regular braking (I also can't find that supposed maximum in any of the segments). My working assumption is that the GPS signal wasn't great (despite cloudless, blue skies), which led to delays in the times and distances being picked up which in turn led to the very odd measurements. It's possible that something similar has happened to you - maybe (I'm just speculating here) it lost you for a mile or two, and then decided you had taken a longer route than you did? It's certainly pushed me closer to installing my speedometer to get some rather more real and reliable measurements.

    0
    Comment actions Permalink
  • Toby S

    Interesting - thanks, Peter. I don't think it can be that it lost me, though, as the route it mapped for me looks to be exactly where I went (and is within a few feet here or there the same as the route I usually take). I'm not 'pro' enough to be looking at segments on Strava, I'm afraid - but I'd still be keen to have fairly accurate info from Beeline. My instinct is that the shorter distance that it used to claim my route was is closer to the truth than the new, longer, one, but the truth is I don't really know!

    I hope you have better luck/less peculiar results in future, anyway. 

    0
    Comment actions Permalink
  • Toby S

    FWIW, my morning commute today - very much the same route as ever - came out as 6.5 miles. That's slightly longer than the old usual but much less than on Friday...

    0
    Comment actions Permalink
  • Toby S

    And today's same-as-ever morning commute came out as 7 miles. I seem to have lost consistency of measuring (and don't really know what the true distance is).

    0
    Comment actions Permalink
  • Beeline Team

    Toby, I've passed this on to our developers. A bit of variation might be expected from the GPS pinging around a bit, which is something we're looking to significantly reduce. Thanks for letting us know, and for your patience!

    Cheers,

    Sam

    0
    Comment actions Permalink
  • Beeline Team

    Toby, could you pass us the email you use for Beeline login? We're investigating!

    0
    Comment actions Permalink
  • Toby S

    Today's came out at 6.3 miles - the previous 'normal' distance. Maybe things have settled?

    1
    Comment actions Permalink
  • Beeline Team

    Hi Toby, thanks for keeping us updated on this - let's hope so, but any sign of significant deviation from the norm, do shoot that email across and we can look into the specifics :)

    Happy Beelining!

    0
    Comment actions Permalink
  • James Gunn

    I had a similar issue today using my beeline to commute home. I stopped off near the end of my ride and went round a couple of shops - at the moment there is no function to pause a ride so it was annoying to see my average speed decimated by the 20mins or so i spent walking between groceries isles. However i like to upload my rides to Strava anyway which does recognise stops during journeys so no huge issue.

    However my uploaded journey on Strava shows all manner of strange jumps which i did not make. These don't show on the beeline journey. There is definitely an issue with synching the gps data between the two apps which needs resolved. As it stands I am now a record holder for a segment on Strava which i didn't even do today. It's not great!

    0
    Comment actions Permalink
  • Beeline Team

    Hey James - that is really not ideal! Can I ask for your email, and we'll look at the GPS data ASAP! The team are putting a good deal of work into ensuring the experience isn't tarnished by issues like this - we're determined to get it right.

    Thanks for getting in touch!
    Sam

    0
    Comment actions Permalink
  • James Gunn

    Hello my email is Banditjames@hotmail.co.uk thanks for the prompt response

    0
    Comment actions Permalink
  • Beeline Team

    We've sent you an email James :)

    0
    Comment actions Permalink
  • Toby S

    Yesterday’s morning ride was claimed to be 6.8 miles - ie a bit more than the 6.2 Beeline used to claim - but today’s was said to be a massive 8 miles! It definitely isn’t that long from home to work - and it’s showing the same on the map. Very puzzling!

    0
    Comment actions Permalink
  • Toby S

    Today’s morning ride was said to be 7.3 miles - different again...

    0
    Comment actions Permalink

Please sign in to leave a comment.