OnePlus 13 as Bluetooth bridge

Bugs and Support
1

Hi

I’ve recently bought OnePlus 13 and I’m using it as Bluetooth bridge. I’ve noticed that my power measurement quite often stalls at one value for couple of seconds (more or less 3).

My whole setup hasn’t changed. I’ve just replaced my old OnePlus Nord 2 5G with this new phone and now I see this issue.

Maybe someone has similar issue? Maybe someone has a solution for it?

2

Hi @Slawomir_St, welcome to the Forums! I’m Francisco from Zwift Support.

Since you’ve just switched to the OnePlus 13 and are now seeing power readings stall for a few seconds, here are a couple of things worth checking:

  • Make sure the device running Zwift and the phone running the Companion app are on the same Wi‑Fi network, including the same band (2.4 GHz vs 5 GHz).

  • Close the Companion app completely before starting Zwift. Then try one of these steps on your phone:

  • Turn off mobile data.

  • Switch on Airplane Mode, then connect to your Wi‑Fi.

  • After that, launch the Companion app, and then launch Zwift on your separate device.

These steps often clear up the kind of stalling you’re describing. For a full walkthrough, I’d recommend checking out our official guide here: Issues with Zwift Companion App.

Thanks for posting! If you need any further assistance, feel free to reach out to us at support@zwift.com.

Ride On.

3

Thanks for this…it did not solve the issue. The issue is with the phone…I think, since for another example iPhone X works just fine.

4

Other possible solutions would depend on knowing which trainer you have, what you are running the game on, and the things you are pairing to the game. Sometimes other options exist (not always).

5

Tacx Neo 2T, Linux :slight_smile:, Garmin Dual HR monitor. I’ve been using this setup for years. The issue is visible after switching the phone.

6

I also noticed one thing: when using OP 13, I see yellow colour of the icon next to given device/function when pairing the trainer or hr monitor (this is this funny icon you see next to device name). With iPhone it is green. With my old phone it was also green…maybe my phone case is causing that…I will check.

7

Without the case, OP13 is still seeing the trainer with yellow colour. See attached picture.

The green item on the picture (with less digits in the name…why?) is from iPhone.

Any idea if this is the issue: yellow colour for range (is that a range indicator anyway?)?

8435
84351920×2560 805 KB

8

I’ve been also checking the ping times to my OP13…looks super wrong to my taste (318ms avg!!!):

ping 192.168.1.91 -c 20
PING 192.168.1.91 (192.168.1.91) 56(84) bytes of data.
64 bytes from 192.168.1.91: icmp_seq=1 ttl=64 time=64.3 ms
64 bytes from 192.168.1.91: icmp_seq=2 ttl=64 time=17.8 ms
64 bytes from 192.168.1.91: icmp_seq=3 ttl=64 time=209 ms
64 bytes from 192.168.1.91: icmp_seq=4 ttl=64 time=435 ms
64 bytes from 192.168.1.91: icmp_seq=5 ttl=64 time=50.1 ms
64 bytes from 192.168.1.91: icmp_seq=6 ttl=64 time=271 ms
64 bytes from 192.168.1.91: icmp_seq=7 ttl=64 time=509 ms
64 bytes from 192.168.1.91: icmp_seq=8 ttl=64 time=122 ms
64 bytes from 192.168.1.91: icmp_seq=9 ttl=64 time=352 ms
64 bytes from 192.168.1.91: icmp_seq=10 ttl=64 time=1194 ms
64 bytes from 192.168.1.91: icmp_seq=11 ttl=64 time=183 ms
64 bytes from 192.168.1.91: icmp_seq=12 ttl=64 time=412 ms
64 bytes from 192.168.1.91: icmp_seq=13 ttl=64 time=437 ms
64 bytes from 192.168.1.91: icmp_seq=14 ttl=64 time=51.3 ms
64 bytes from 192.168.1.91: icmp_seq=15 ttl=64 time=284 ms
64 bytes from 192.168.1.91: icmp_seq=16 ttl=64 time=520 ms
64 bytes from 192.168.1.91: icmp_seq=17 ttl=64 time=124 ms
64 bytes from 192.168.1.91: icmp_seq=18 ttl=64 time=355 ms
64 bytes from 192.168.1.91: icmp_seq=19 ttl=64 time=573 ms
64 bytes from 192.168.1.91: icmp_seq=20 ttl=64 time=199 ms

— 192.168.1.91 ping statistics —
20 packets transmitted, 20 received, 0% packet loss, time 19010ms
rtt min/avg/max/mdev = 17.780/318.191/1194.488/261.801 ms, pipe 2

Other phones in my network are way better (avg below 100ms).
I think some long times here might be causing the issue I see.

9

Yes that is horrible. Even 100ms is very poor.

10

I think this is a false alarm. When the Companion app is running, time is below 10ms always. But the range indicator is yellow…

11

Tested on Windows 11. The same issue when using OP13 and the Companion app. With Bluetooth from PC - no issue. But I can’t use Bluetooth from PC on Linux, so I want Companion app working :slight_smile: