Something similar is happening to me with the issue of Bluetooth interruptions:jfheath wrote: ↑Mon Nov 11, 2024 8:24 pmAh - I do. Goodness me. But I don't just go to them with a problem - I go to them with a set of well documented evidence. That cuts out all of the try this, try that, try the other. So for example - I am sitting here at my desk with my crash helmet on, Zumo XT2 powered by a spare XT1 cradle on my desk. Video camera point at it. Trying to work out exactly when the BT connection is broken.turbo19 wrote: ↑Mon Nov 11, 2024 8:21 am Please @jfheath , it would be very helpful if you reported this error to Garmin technical service, they tell me that "there is no user with the same problem." I don't believe it.
Please, it is very important that all users who have the same problem send it to technical service so that engineering can do something. Thank you so much.
So that I can tell them when it breaks and how to get it to return (you wont believe the answer to that last one !!). Then they are going to make out that it is the fault of the phone. So I need to prove to them that isn't the case - because with the same gear with the XT1 it works perfectly OK, and witht he same gear with the 595 it works perfectly OK.
Then I will find out what happens it I disable the Tread App with the XT2.
See what I mean ? Give them no way out. But it does mean that lots of people have to report it. But I'm not the one that you need to push to do that. I do it anyway. If you want to help, get onto some of the other forums - simpel - point out the fault, say you have reported it and ask other to report it too if they have the issue.
I was on at them for 2 whole years with the XT RUT issue. The weird routing behaviour after a route has been recalculated and you deviate from the plotted line. It never calculates a new route to the next route point. Instead it calculates to the last point that it calculated - which is usually behind you. They never fixed it for the XT1. They seem to have addressed the symptoms for the XT2 (it seems to limit the number of successive U turn requests, but still allows 'turn around loops').
Still it is good to see that they can introduce new hardware that makes them more money, and they can at last get rid of the end of ride adverts.
I queried progress with the routes from GPX files being altered by the Tread app. It's on-going.
I don't know whether I believe that or not....................
Right - lets try all of those test again with 4.80 installed. Thanks for the info on that.
Garmin technical service has always made me believe that the disconnection failure must be in my Xiaomi or my headphones, but it was not like that. It took me a while to realize. Now that I have changed the phone, it is clear to me.
"Last test I performed:
I connect XT2/Samsung A55/Cardo Packtalk, all from 0. Having forgotten everything and installing the XT2/phone I do it without linking Tread App. In this case:
- Calls are not interrupted
- The music doesn't stop
So, in conclusion, there is something about the Tread App's Bluetooth syncing and management that causes the interruptions."
We will see what he says now regarding this, because it is indisputable.