What owners are actually seeing
The complaints kick off in an r/PixelWatch thread, where one owner says their Pixel Watch 4 LTE refuses to stay connected once it is away from the phone. The only way they get data flowing again is to fully power the watch off and back on, every single time. Texting is hit or miss too, sometimes it sends with the phone miles away, other times it throws a “disconnected from phone” error and sends nothing.
That owner is not alone. Other commenters in the same thread describe the same disconnects, with a second workaround making the rounds: toggle airplane mode off and on to force a reconnect. Neither one is something you want to do five times a day.
A Pixel Watch 4 owner lays out the LTE dropouts and texting trouble on Reddit. | Image by SquirrelFar9890 via Reddit
Why this one hurts more than a normal bug
Plenty of smartwatch bugs are just annoyances, however, this one hits the wallet. As expected, an LTE smartwatch usually costs more than the Wi-Fi model, so the whole pitch is going phone-free. A cellular connection that collapses the moment you go phone-free guts that pitch.It should be noted that this lands on top of a rough stretch for the Pixel Watch in particular. We covered a software update that broke Find My Phone two weeks ago, and that came after sleep-data and ECG glitches earlier in the cycle. Four wonky things in a few weeks starts to look like a quality-control problem on Google’s wearable team.
What the community is figuring out on its own
One detail worth flagging, because it might save you a service request: a follow-up comment in that same thread points out that the watch still needs the paired phone powered on and connected to the network, even while you are roaming around on LTE. The watch leans on that pairing to find the phone and vice versa. This person says T-Mobile reps did not understand this either, and once they left their phone on the charger at home instead of fully off, everything worked.
A follow-up comment points out the watch still needs the phone powered on and connected. | Image by Automatic_Ad1887 via Reddit
So some of these reports may be setup confusion rather than a true bug. The trouble is telling the two apart, and as that same commenter put it, lately nothing on these Pixel watches is guaranteed.
Does this happen on a Galaxy Watch or Apple Watch too
Short answer: yes, and that is the part Pixel critics tend to skip. Standalone LTE has been shaky across every brand.
If you own a Galaxy Watch 8 or an Apple Watch Series 11 and you lean on cellular, this Pixel news does not really touch you, your platform has its own version of this headache. Nobody has fully nailed standalone watch LTE, so this is less a reason to jump ship and more a reason to keep expectations in check no matter whose watch is on your wrist.
Where I land on it
I daily-drive a Pixel Watch on an LTE plan and I have not run into the dropouts, but I am also the wrong test case. I almost always text from my phone and barely touch the watch’s own connection, so a flaky LTE link rarely gets a chance to bother me. Plenty of people are not in that boat, though.Picture someone whose workplace bans phones on the floor, where the watch is the only thing that can surface an emergency call or text. For them an LTE connection that comes and goes is not a minor gripe, it is the difference between catching an urgent message and missing it. That is who Google needs to be building for here, and that is why a fix needs to come fast.
