Home > Pixel Series

Cannot Activate LTE on Galaxy Watch 6: How to Fix

In this guide, we will show you a nifty workaround that might help you fix the issue of being unable to activate LTE on Galaxy Watch 6. Many noteworthy players are setting their feet in this domain however, still, it’s the offerings from the South Korean giant that is the go-to choice for the masses. In this regard, it has recently launched its sixth iteration which has already grabbed the attention of the masses.

Unfortunately though, not for all the right reasons. Numerous users have voiced their concern that they are unable to active LTE on their Galaxy Watch 6. The ICCID is not populating even though the IMEI is registered with their carrier. So if you are also getting bugged by this issue then this guide will make you aware of a nifty workaround that might help you resolve this bug. Follow along.

Fix Cannot Activate LTE on Galaxy Watch 6

Cannot Activate LTE on Galaxy Watch 6

In order to rectify this issue, you’ll have to reset the carrier APN on the watch. So on your Watch, go to Settings > Connections > Mobile > APN > Reset it to default. Then restart your watch and the APN will be repopulated. You’ll now have LTE data and this should fix the issue of being unable to activate LTE on Galaxy Watch 6. If you have any queries concerning the aforementioned steps, do let us know in the comments. We will get back to you with a solution at the earliest.

Update: Fix Galaxy Watch 6 LTE not working with Pixel 7/Pro

A similar issue has once again come to light this time involving the Pixel 7/Pro users as they are also unable to activate LTE on their Galaxy Watch 6. And this time around, the latest August patch might prove to be the culprit. This is because the Galaxy Watch 6 LTE is able to easily connect with non-Pixel devices and even with Pixel devices running on July or older security patch.

As far as the fix is concerned, you could try out the aforementioned Reset APN tweak, update your device to the September patch [when it is released], or downgrade it to the July security patch [which would require an unlocked bootloader]. As far as the official stance on this matter is concerned, the developers are yet to acknowledge this issue, let alone give out any ETA for the rollout of a fix. As and when any of these two things happen, we will update this guide accordingly.


Share: