Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Yes they are, but at the moment only one has a cellular plan until EE gets their act together. I’m getting error 007 (ineligible for another line) when trying to add the second. I emailed the credit department over the weekend but I’m not chasing it other than that.
So each Watch needs it’s own plan. That seems unreasonable since you literally can’t use them both at the same time!

I guess it’s an artefact of how lines work in general, but even so...
 
So each Watch needs it’s own plan. That seems unreasonable since you literally can’t use them both at the same time!

I guess it’s an artefact of how lines work in general, but even so...
Yes, but honestly I think the price is very reasonable, and with six months free, we have the best price in the world (though we pay for it through setup issues! :D). If you can afford two Apple Watches you shouldn't be complaining at an extra fiver a month.

Anyway, EE emailed me back, and after a quick call to 150 I have my second Watch up and running with data. I had the same errors (007, 008, and 012) as previously which is why I had to call - so that hasn't been fixed yet. But the response to it has and they know what they're doing now.

I'll be going out in a moment to check if it is working.
 
Well finally got it working and it seems to have a stable connection. To begin with they reset the something on their backend and was told to add the plan which worked but it still wouldn't connect, so I was told to re-pair the watch again and remove the plan. This caused the error 019 again and they reset it again on their system and it finally connected!

Don' t give up if you have issues just keep calling EE and they should be able to get it sorted.
 
  • Like
Reactions: Brookzy
Actually I think you are both right. Now that I'm getting a cellular connection at home on the watch I tried doing this. I put the iPhone in airplane mode, confirmed the watch was on WiFi, and made a note of the IP address allocated to it. I then made a call and used tcpdump to monitor the network traffic from the watch. I saw lots of IPSec traffic to an IP address owned by EE - WiFi calling uses an IPSec tunnel.

I then disabled LTE on the watch and tried again. The call failed immediately every time. So it looks like it needs LTE to help set up the call but then uses WiFi calling after that.
IMG_0090.PNG

'Ello, 'ello... :eek:

Interestingly, I have Wi-Fi calling turned off on my phone too.
 
Sorry if this was addressed already somewhere else, but if I register my watch now with EE, will be process of moving to a new iPhone a hassle (ie I have to get in touch with EE directly for them to change things at their end)? I have a 6+ now, but will move to the X or 8+ in November. I would think it should be a straightforward process, but given that the watch is new, I am not sure...
 
Sorry if this was addressed already somewhere else, but if I register my watch now with EE, will be process of moving to a new iPhone a hassle (ie I have to get in touch with EE directly for them to change things at their end)? I have a 6+ now, but will move to the X or 8+ in November. I would think it should be a straightforward process, but given that the watch is new, I am not sure...
Worst case scenario you'll have to call EE and get them to do it on their end again.

The good news is that process seems to be far quicker now, at least based on my experience today vs. last week.

However I can imagine there being a surge of requests once the X is out so probably best to get in there first.

It is still a while away though so hopefully EE will get their systems working properly by then, though I'm not holding my breath.
 
  • Like
Reactions: cvdb1969
I suspect it might depend on whether you go with a new SIM or not? If you just move your existing SIM to a new phone than the eSIM will still be working against the same physical SIM?
[doublepost=1507057503][/doublepost]
View attachment 723193

'Ello, 'ello... :eek:

Interestingly, I have Wi-Fi calling turned off on my phone too.
My Watch says Network Not Available, even though I have 2-bars of 4G at home. Should I be concerned?
 
I suspect it might depend on whether you go with a new SIM or not? If you just move your existing SIM to a new phone than the eSIM will still be working against the same physical SIM?
I heard that a major factor in error 012 was that the IMEI of the phone wasn't updating (and in some cases hadn't updated for more than a year) so I guess getting an iPhone X will present an issue if that isn't fixed. I hope not though.
[doublepost=1507057598][/doublepost]
My Watch says Network Not Available, even though I have 2-bars of 4G at home. Should I be concerned?
Is your phone switched on? If it is then there is no issue. It will only say anything if the Watch is actively using cellular (or in the case of my screenshot, making a Wi-Fi call).
 
Is your phone switched on? If it is then there is no issue. It will only say anything if the Watch is actively using cellular (or in the case of my screenshot, making a Wi-Fi call).
Tried turning the phone off. At that point, calls instantly fail on the watch (phoning a landline, if that makes a difference). I’m at home so the watch is connected to my WiFi.

With the phone on, the watch will make a call but seems to just be bridging via my actual phone. Is the best test to walk down the road sans iPhone and try to make a call once I am outside of WiFi range?
 
Tried turning the phone off. At that point, calls instantly fail on the watch (phoning a landline, if that makes a difference). I’m at home so the watch is connected to my WiFi.

With the phone on, the watch will make a call but seems to just be bridging via my actual phone. Is the best test to walk down the road sans iPhone and try to make a call once I am outside of WiFi range?
The handoff is buggy at best and I'm sure will get better with an update. Right now if you turn your phone off and try to make a call on the Watch while it is connected to Wi-Fi it will frantically try to start up cellular, to arrange a connection to EE and then get the call going over Wi-Fi, and then power down the cellular again.

This results in some failed calls if the cellular takes too long to power up.

It is a weird implementation that can only be to try to use as little power as possible and is probably a unique problem because we don't have iCloud device calling like they do in the States.

So if you give it more time it should work. If you go for a walk it will definitely work because it will give up this Wi-Fi trickery and just go pure cellular.
 
  • Like
Reactions: danmart
The handoff is buggy at best and I'm sure will get better with an update. Right now if you turn your phone off and try to make a call on the Watch while it is connected to Wi-Fi it will frantically try to start up cellular, to arrange a connection to EE and then get the call going over Wi-Fi, and then power down the cellular again.

This results in some failed calls if the cellular takes too long to power up.
Just given that another try with the phone off and it worked this time :)
I’ll do the walk-test, too.
 
  • Like
Reactions: Brookzy
Got my plan set up yesterday on the phone. But had real difficulties with the watch. Several calls to EE and a couple to Apple. Resolved by tier 2 EE tech late in the afternoon.
 
I received an email from Technical Support Lever 2, stating that they don't have the training to deal with the issue. They have been fooling me around for several days. Each time, when I try to call them, they just say they will call me later and, in fact, they never did.
 
Picked up my watch at lunchtime today activated it with EE and worked instantly. Had no problems so far all very smooth!
 
Setting things up on the phone was seamless, but when out without my phone for the first time tonight, it took about 20 minutes to register on cellular. Is that normal?

Will try again tomorrow.

Was a bit strange not having my phone, but was quite nice actually.
 
Setting things up on the phone was seamless, but when out without my phone for the first time tonight, it took about 20 minutes to register on cellular. Is that normal?

Will try again tomorrow.

Was a bit strange not having my phone, but was quite nice actually.

Glad you managed to get your setup, I am one of many who have moved to EE and EE does not know how to fix this new number issues with Apple watches. Some people have been waiting for two weeks for help. Staff have been good, but then do not know when there will be a fix :-(

https://community.ee.co.uk/t5/Apple...oesn-t-work/m-p/616048/highlight/false#M62880
 
I received my Nike+ series 3 LTE today. I've been an EE customer for a good few years with an EE max plan, but encountered Error 007 (my account wasn't eligible for an additional line). I tried the online chat who couldn't help, but recommended I called 150. I called EE and within 2 minutes of speaking to the representative, I was able to follow the process on the watch and within 15 minutes the line was active.
 
  • Like
Reactions: Brookzy
How quickly should the watch pick up an LTE connection (assuming there's a decent signal) from the time your phone goes off or you walk away from it?
 
So setting up then plan with EE went straight through without any errors. 1hr30mins later still waiting for a connection to the network. How long did it take for those who have had success?
 
Setting things up on the phone was seamless, but when out without my phone for the first time tonight, it took about 20 minutes to register on cellular. Is that normal?

Will try again tomorrow.

Was a bit strange not having my phone, but was quite nice actually.
The battery on my phone ran dead and 30 seconds later, LTE activated on my watch with maximum bars so it works well
 
  • Like
Reactions: ascender
Mine been saying "Activating" for more than two hours now. How long before it moves from "Activating" or before it displays an error?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.