Tread Changes Exisiting Routes - Shaping Point Issues

[Oop North John]

So, this is the latest from Garmin Customer Support today:

Is the same issue happening if you simply create the point as a shaping point to start with? If so, then that would be the workaround for now - we've received hardly any user reports of this outside of yours, so this is unlikely to get fixed any time soon (if at all) unless we get more users reporting the same behaviour.

So sorry for any inconvenience here, and let me know if there's anything else I can do to help as I'll happily assist any way that I can!

Has anyone else reported it, if so can you let me know the case number?

When I've calmed down I'll reply to them

[Oop North John]

Tried making a route using shaping points, but the route failed to go the way I wanted it to so tried adding a shaping point. But it adds it after the final stop. Can't move shaping points in Tread so converted them into stops to adjust the order. Back to shaping points and the route ignores two of them.

Shaping points on the A66 and M1 are now missed.

Feedback sent to Garmin.

[smfollen]

@Oop North John My case number is (PSC-560689) << Ref: 28420131K1 >> <Q#:1000351> and my case includes a reference to John's.
What is your case number? I can add that to my case too. (PM if you don't want to share publicly.)

Garmin support told me that no one else in the world had reported the issue via any of their reporting channels!
You might also refer them to this thread, as I have, and point out that it now has over 17,000 views so we are apparently not alone in our concerns.
... and that there are a number of reviews of the Tread App on the Google Play store complaining about the same issue.

[Oop North John]

@Oop North John My case number is (PSC-560689) << Ref: 28420131K1 >> <Q#:1000351> and my case includes a reference to John's.
What is your case number? I can add that to my case too. (PM if you don't want to share publicly.)

Garmin support told me that no one else in the world had reported the issue via any of their reporting channels!
You might also refer them to this thread, as I have, and point out that it now has over 17,000 views so we are apparently not alone in our concerns.
... and that there are a number of reviews of the Tread App on the Google Play store complaining about the same issue.

My case details are: "Garmin Tread and XT2 - routes and shaping points related issues << Ref: 28705111K1".

[Oop North John]

More Tread stupidity.

Depending on whether the point on the A66 is a shaping point / stop / or not there (as the route goes through it anyway) gives me a time difference of 24 minutes and 4 miles, all with the same avoidances etc.

Shaping point gives the quickest / shortest route. No point gives the longest time. Stop gives the longest distance but a shorter time than nothing.

Feedback sent, and soon they'll hopefully fix some of the routing issues as it'll be in their interest as they won't be getting feedback from me

[Oop North John]

Garmin's Tech Support want me to now provide a video of what's happening.

Is this a "it's too difficult for us to work out / we can't be bothered" type of request so that it puts the focus on me, and if I don't they'll just close it on the basis that the customer failed to supply the data required?

Or am I becoming too cynical?

[jfheath]

I think that they put off the moment when the front desk people have to write a detailed report for the programming team. I have just been asked - by another person using the same reference - for a copy of the Tread log file - after previously being asked to test with a different phone - which meant removing tread from my first phone - so the log files no longer exist.

I pointed out that they already had this data and a video on (quoted date), but never mind, I'll send the same video again.

The later test using a different phone failed to produce the same problem. So they blamed the first phone. They said that confirms the issue is with the first phone.

I pointed out that the first phone does not produce the fault unless tread is installed, so that strongly suggests that tread is peventing the phone from working as it should.

They said that they would submit a report but it might take time and they wouldn't promise anything.

Which I took as a euphamism for I'm not going to do anything now.


My fault is slightly different. Whan a call is made to the phone on the bike, call is answered and all is ok. If the caller hangs up first, the XT2 doesn't know about it, and cannot clear the phone call - so no sound from music, phone or satnav.