I've been trying to activate LTE on my Galaxy Watch 8 Classic on Visible using my Galaxy S21 Ultra and kept getting "Visible doesn't offer any mobile plans for watches." Since they advertise watch support, I used ADB to capture the full logcat during the activation attempt to see what's actually going on.
Note: This is specific to my setup — results may vary on other devices.
What I found:
The phone successfully contacts Visible's eSIM server and gets back this top-level response — the watch is on their approved hardware list:
Result: SUCCESS
ResultCode: 1000
EsSupport: true
OnlineSupport: true
QrSupport: true
SmdpAddress: [Verizon SMDP+ server]
OperatorName: Visible
But buried inside that same response is a GmFeature config block that immediately contradicts it:
"esim_method_override": {
"method": "subscription",
"source": "qr",
"source_value": "true",
"overide_value": "false"
},
"custom_not_support_qr": "true"
So the server says QrSupport: true at the top, then custom_not_support_qr: true lower down, and the override block explicitly flips QR from true → false. The Galaxy Wearable app reads the GmFeature block and gets told "no QR, no NumberShare" — silently gives up with no error message, just the generic "no plans" screen.
What Visible would need to change:
Option 1 — QR activation: Set custom_not_support_qr to false and remove the override block. Done.
Option 2 — Server-push (no QR): Keep QR disabled but flip "overide_value" in the override block from "false" to "true". The watch would then send its EID to Visible's backend and receive the eSIM profile directly over the network, no QR needed.
Option 3 — Both: These two paths don't conflict at all. Enabling both would be the most robust setup — the Wearable app would have two valid activation paths and use whichever applies. All of this is a config change on their end — the watch hardware is already whitelisted on their server.
Either way it's a config change on their end — the watch hardware is already whitelisted on their server.
Watches currently whitelisted in Visible's server config (not sure if all affected):
- Galaxy Watch 4 — SM-R865U (40mm), SM-R875U (44mm)
- Galaxy Watch 4 Classic — SM-R885U (42mm), SM-R895U (46mm)
- Galaxy Watch 4 LTE US — SM-R866U
- Galaxy Watch 5 — SM-R905U (40mm), SM-R915U (44mm)
- Galaxy Watch 5 Pro — SM-R925U (45mm)
- Galaxy Watch 6 — SM-R935U (40mm), SM-R945U (44mm)
- Galaxy Watch 6 Classic — SM-R955U (43mm), SM-R965U (47mm)
- Galaxy Watch 7 — SM-L305U (40mm), SM-L315U (44mm)
- Galaxy Watch FE — SM-L325U
- Galaxy Watch 8 — SM-L345U (40mm), SM-L355U (44mm)
- Galaxy Watch 8 Classic — SM-L505U ← my device
- Galaxy Watch Ultra — SM-L705U
- Galaxy Watch Ultra 2 — SM-L715U
Hopefully this helps anyone else hitting this, and hopefully the engineers at Visible see this and can get it sorted since they do advertise support for these watches.
EDIT: Visible rep said engineers are working on a backend fix. Should take around 24-48 hours according to the notes from them.