Need help: Bluetooth problems XT2

[turbo19]

All my joy has disappeared as soon as I have tried a little of everything. With a new Samsung A55.

The first hour everything worked fine, calls, WhatsApp, music and collection synchronization. Everything working and without problem.
On the second connection between XT2/Samsung/Cardo everything started to fail. The bluetooth connection would break, with a "reconnect to Tread" message in the Explore sync menu on the XT2, calls dropping within a minute, etc.


I thought that with the Samsung it would work better, but I see that the problem persists. Does anyone have any idea what it could be?
Tomorrow I will call Garmin customer service because my patience has run out.

Thanks to all

[turbo19]

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.

[Oop North John]

So, in conclusion, there is something about the Tread App's Bluetooth syncing and management that causes the interruptions.

What a surprise, Tread messing something else up

[turbo19]

It is very important to send these problems to Garmin technical service, so that they can see that they are not isolated cases.

product.Support@garmin.com

Otherwise they will never fix it, and in this case Bluetooth is essential for the Tread App to perform all its functions.

Thank you all.

[jfheath]

As I said - I always do.

Here is the latest regarding my phone / BT issue. It is different from your descriptions - but I think it may be the same cause.

Zumo XT2
Hardware V9 Pv3 DT R512D WB
Unit Id 346123456
Software v 4.80
BT Firmware 1067.1127

App name: Tread
App version: 2.08.37
OS version: Android 12
Phone: samsung SM-A415F
Device(s) connected: zūmo XT2(SW:4.80).

Zumo XT2 and Phone calls.

The XT2 has an issue with ending phone calls – which makes it impossible for subsequent phone calls to be received and for other BT devices to function properly.
Exact behaviour from test to test tends to be slightly different – but basically, when a call has finished, the XT2 does not truncate the call at its end. Which prevents other BT devices from working again.
Eg Music will not play, Nav instructions cannot be heard. Subsequent phone calls cannot be made. It is hard to pin down exactly what is happening when on the bike, but clearly something was wrong as I had to stop and restart the XT2 in order to return to a phone call where the caller clearly could not hear me.

So I experimented at home with a few simple steps.

1. Check BT / Music / Nav Instructions work OK.
2. Call smartphone from house phone.
3. Answer call by pressing the button on the XT2 screen
4. Phone call works OK.
5. End call by pressing button on screen. Call ends – according to the XT2, and according to the landline phone.
6. BT does not return for nav instructions.
7. In fact, the smartphone has not hung up, although I have found no way of being able to see that the call is in progress – not on the XT2 screen, not on the phone itself. So I call it again, and I get a message. John Is on the phone, please leave a message.
8. The only way I have found of getting out of this is to soft restart the XT2. Short press the power button to turn the XT2 off, and then again to turn it on. BT is then disconnected and reconnected.
Although I noticed a couple of times if I leave it for a few minutes, BT is disabled according to the XT2 and it reconnects again.

This does not a appear to be a problem with my phone, my Cardo headset or with the XT2 . I say this because when I removed the Tread App from my phone – ie I uninstalled it completely - and then I carried out the same simple tests with the same equipment, the phones disconnected from each other immediately and another call could be placed immediately. Headset and Music returned to normal immediately the call was disconnected. BT did not disconnect a few minutes later.

So it would appear that the Tread App is also responsible for making it impossible to make and receive reliable phone calls – as well as being responsible for destroying carefully planned routes (I have reported that it moves the route and shaping points onto different roads. These are things that have always been possible with the 550, the 660, the 590, the 595 and the XT1. If I want reliability for these things on the XT2, then I have to turn tread off – but that means discarding the Traffic, roadworks and weather information.

I made a couple of videos of these tests. So when this get escalated to the team that eventually deal with it, I have something ready.

John Heath.

[turbo19]

Anyone else having bluetooth dropouts issues?

I imagine a lot of people will have the Tread App disabled.