Galaxy Watch 7 / Ultra (LTE)

[Jason_K]

Hi all, is anyone successfully using a Watch 7 or Ultra on LTE successfully, and able to make calls from the watch?
(or anyone else having issues?)

I have a Galaxy Watch Ultra, have activated a paired £7/Month eSim for the watch but it does not work properly. 

Plan shows as active, Watch shows as connected, and when disconnected from the phone, watch data works - I can browse the internet, update apps, use WhatsApp etc. What doesn't work is Calling - neither incoming or outgoing. If I try to make an outgoing call, it attempts it, then ends the call within 2 seconds before it rings. Incoming calls aren't routed to the watch.

I've called EE, and they have re-applied the eSim and also got me to remove the plan from my watch and put a new one on - nothing has worked, and I think they are a bit stuck!

On the Samsung community there are several other people with the same issue - all on EE, and all with a Watch 7 or Ultra. One person reported dealing with EE 3rd line, and overnight it started working - the kicker being when they spoke to their handler the following day they didn't know what had fixed it!

[TheNokiaN95]

@carlkenyonc have you asked EE to put this on a family plan as EE CS says it will have a separate number so wondering if paring with the same number is the issue with calls? who knowns? - i did try a samsung galaxy s9 that i dusted off but it seems that the plugin isn't compatible with android 10, Looking around i can see that the minimum is android 11 what come around 2010 also VoLTE/4G Calling works funny enough!

So now waiting on a friend to bring hes samsung s20 that he no longer uses to see if that works, Will let you know how i get on later on with data/cells wise with the family plain but as i said before, Tried it with a Moto Razr 50 Ultra and a Pixel 7A what both gives me a complete error even though samsung says you can do this on a non samsung phone... Ehh!

So looks like to me that Samsung is going down the Apple route, Google will follow soon! 😲

[carlkenyonc]

The numbers should be associated by account and even if they were separate numbers you should still be able to make and receive calls so I doubt changing to a family plan would make a difference but I'm open to he corrected on that 

[Cyborgtf3]

To get the txt to work when disconnected from your phone make sure  Remote connection is enabled in the galaxy wearable app on your phone, go to the app then Advanced Features and enable remote connection, the txt will work but I still have no joy with calls 

 

[Kyjuan]

I really think this is getting ludicrous now. For the best part of two months, it's been pin drop silence from EE, no indication of a fix, no comms of any sort from them and the worst part? They continue to take money!!!! I've purposely left the direct debit as is to see if they'd do "the right thing" by initiating contact and proposing something in the interim (e.g. Stop payment + compensation for lack of service etc) but they are acting like nothing is wrong! Lol.

I think I'm just gonna call them and stop the service. I can get by without the watch being on LTE - it's just a nice to have for me. Nothing more. 

[Cyborgtf3]

I totally agree that this is taking way to long for a fix, I bought the watch ultra for the lte bennifit and at 600 quid it is a big purchase for me, paired it up with a s24ultra and ee are unable to provide a working esim, customer service have been as good as they can but a call back from tech 3 would be nice or even if they posted a update in the community, they have reduced my bill for the next 3mth and assured me it's been worked on, I've been waiting since the beginning of August for a fix and it all this time not a single call with an update which means it's me having to do all the chasing, I've been with ee since before it was ee and I've never missed or been late on a bill payment but do I feel a valued customer......no. 

I'm thinking now of ending my contract early as they can not hold me to a contract that is not fit for purpose and moving to another provider as the esim issue only seems to be with ee

[Kyjuan]

I'm in somewhat similar boat as you. I've been with EE for as long as I can
remember. Never given it a thought of even moving and I have about 5 mobile
lines with them. For the first time ever, its crossed my mind to move.
For me it's either I keep the non-watch lines (no issues there) and ditch
the watch service or move everything. Decisions, decisions, decisions.

[Jason_K]

Yep, me too. Been with EE since they were T-Mobile, with a few lines. Given they appear to be the only network that has a consistent issue it is really disappointing that it has not been solved yet. It might be difficult, but communication is everything - give us a clue. What are you doing? Have you engaged Samsung? Have you got a few users you are actively engaged with trying to understand the problem? The fact it is only EE suggests it is a 'feature' of their network or how they are applying E-Sims that isn't playing nicely with the Samsung implementation. If it's something that cannot, or will not, be fixed due to a fundamental mis-match then own up and we can decide what to do. I find it incredible they appear to have no clue after 3 months+

[Kyjuan]

You couldn't have said it better. It's the communication part that's really
**bleep**ing me off the most.

I just might give them a call in the coming days to hear what they have to
say - That might be the decider.

Although, with the constant merging of telco operators these days, I can't
say there's a huge amount of options to even switch to.

[danielwhitt28]

The simple fact is, if they offer it for sale with a data plan, it should work, end of story. If they can't make it work, because of network compatibility, sell it without a data plan. It's not rocket science. They seem hell bent on taking people's money and then wonder why people complain when it doesn't work. 

I originally bought the watch when it first came out and had the same issues. Sent the original watch back after two months of waiting and listening to EE and the excuses. Waited for a few months, and got another one thinking the same issue would have been fixed by now, and low and behold, it's still going on. I know I should have checked this thread first, but decide to bite the bullet as I hadn't heard anything for a while. 

Guess it will be some phone calls to EE, to raise the issue again, and see what they have to say. It's annoying because if we want the watch to ever work with our phone number, currently it will not be with EE which means switching networks. They should either be discounting the watch to the price of a Bluetooth version and cancelling the paired watch esim off the account or offering major discounts until all of this is sorted out one way or another. Just expecting people to carry on paying for a service they can use, and possibly won't ever be able to use, seems crazy to me. 

I had this happen on a previous Samsung watch, but it was sorted out within a week, so I'm not sure what the issue could be, or what has changed so much for this to be such a big problem ? 

[danielwhitt28]

I've just spoken to EE, she read me out the statement that ee are giving the operators to say, which now includes not even putting it through to level 2 tech, because there is nothing they can do, there is no current work around or fix, and don't know when or if it will get fixed. The lady I spoke to has just literally given me the 7.25p a month off indefinitely and said that's about all they can do, so all I'm doing is just paying for the watch. If it's starts working I still get the discount and it's applied til the end of the contract. 

I know it's not perfect but at least that is something, and if it starts working eventually, then it's an extra bonus I guess. Still think it's rubbish ee are selling a watch that can't be used. 

The only other thing they said, was it doesn't effect all users, which I guess would explain why it's still for sale as a watch plan, but doesn't stand to reason why it will work for some, but not for all ? Surely it either works or it doesn't and effects everyone ?