S6 Classic LTE Remote Connection Help

[PJC67]

My Devices & Service Carrier.

S23+ USA Factory unlocked.

S6 Classic LTE Factory unlocked.

Tmobile.

Last couple days I've had issues getting LTE cloud handshake with S23+.

Making & receiving call on watch works as should but unable to receive text & email.

My trouble shoot:

On S23 , ive uninstall/reinstall Wearable app couple times remote connection setting enabled within app.

Cleared Google Play Services Cache couple times.

Reset watch couple times with new sign in to Samsung account.

None of this has resolved issue which brings me to today. 

Wearable app is installed remote connection enabled BT synced with Watch & watch signed into Samsung account everything good there.

I disable watch BT , watch connects LTE with no cloud handshake watch signed into account.

From there i looked closer into phone settings - "Connected Device" finding Watch not listed in " Call & Text on Othet device" as seen below 

Is "No other Devices" showing normal?

I would think watch should be listed.

Any help resolving this issue would be much appreciated.

Thanks

[LongHiker]

You don't use "Call and text on other devices with a watch". The connection is just magic through the Wearable app.

[PJC67]

Thanks for info.

I just finished finished wearable uninstall reinstall followed path in opening post & reset still getting same result.
I'm just about over this watch Samsung support provides zero help getting issue resolved.

[realaud]

Samsung is zero help getting connection issues resolved, because anything LTE related is a carrier issue. T-Mobile tech support, however, is stellar in getting these types of issues resolved.  Dial 611 on your phone and ask for tech support, not the general customer service agents.

[PJC67]

First off , thanks to all for feedback.

Issue resolved 😊.
Installed "Google Play Services" update on S23 & that did the trick , LTE watch now functions as should.

Why Samsung Customer support failed to provide such simple fix is puzzling.
Their watchs basically have no support.

Anyway, it was working perfectly for 5 months no issue till couple days ago.
Maybe Samsung or Play Store pushed app update that caused issue.