09-17-2018 12:51 PM - last edited on 09-17-2018 06:34 PM by RogersMaude
OK so the system is now live. You should get a pop up asking if you'd like to update the carrier settings. Click Yes
Then you go back to your watch app and 'setup cellular' is active. I was able to get all the way to the 911 address screen but for some reason the 'continue' button is greyed out even when I enter my full address. So not sure what's going on with that. But I was able to get like 2 steps from the finish lol
***Added Labels***
09-23-2018 12:17 PM
09-23-2018 12:22 PM
09-23-2018 12:25 PM
nice to see I'm not the only one with WS516 error....... so aggravating.....
09-23-2018 12:44 PM
09-23-2018 01:51 PM
Someone helped work through a solution. Rebooted that Apple watch and then went through the process again, filling out the 911 form with the address exactly how it appears on my bill... voila!
Good luck
09-23-2018 01:54 PM - edited 09-23-2018 01:55 PM
09-23-2018 03:10 PM
Rogers needs to repair their system. It sounds like watch activation problems are widespread. I have called several times now, spoken with tech support, and nothing works. Their systems is simply broken and they need to repair it.
09-23-2018 05:57 PM
09-23-2018 06:02 PM - last edited on 09-23-2018 06:22 PM by RogersMaude
Apple Watch Cellular Activation Problem (Error WS516)
I know everyone is having major issues with activating their cellular plans on the Rogers network and there's lot's of different error codes out there so I thought I would make my own thread for my error code but everyone can feel free to share their issues as well.
09-23-2018 06:07 PM
Succes. Entering the 911 address properly was the trick.
So here's an example address from my bill
John Smith
1003-80 Bay St
Ottawa On, k1p1k9
On the 911 Page enter info as follows.
Line 1. 80
Line 2. Bay St.
Line 3. 1003
Hope this helps.
09-23-2018 06:13 PM
09-23-2018 06:18 PM - last edited on 09-23-2018 06:21 PM by RogersMaude
I really don’t think Rogers care about anybody’s problems.
I have been dealing with trying to get my wife’s Apple Watch 3 connected for 5 days now.
I have spoken with about 20 different operators, spent hours and hours now the phone, on the online chat, have been lied to, magically disconnected several times, spoken with retention’s who have promised the problem was fixed, drove over an hour to a Rogers store
, was told I needed to do another credit check, was told I can’t set this up over the phone and that I had to go back to the Rogers store.
This is every single time I add a new product or service to my plan...EVERYTIME.
There is no such thing as ‘quick’ with Rogers. The amount of times you get put on hold, transferred, then having to explain the whole situation again to another ‘manager’ which I am sure is whoever is sitting next to the operator you were talking to, is mind numbing.
We have had errors WS201, and WS300. Seems like a pretty common problem on this thread, yet Rogers acts like this is an anomaly and expects to have an answer in 7days...are you kidding me.
With the 5 days spent on the phone, and the predicted 7 day wait, I’m looking 12 days for something that was supposed to be done on the spot.
Seems like the longer you’ve been with Rogers, the worse you are treated.
What a sham.
09-23-2018 07:03 PM
I also had early last week a WS201 error. This was replaced with a WS504 error yesterday. After seeing some had success, tried again today and voila it is working! Good luck.
09-23-2018 07:10 PM
09-23-2018 07:27 PM
Soooo useless.
09-23-2018 08:17 PM
09-23-2018 08:32 PM
@nasa25, I've been busy so just catching up now , I'm having the same problem as you , my watch was working on LTE on Thursday , last night however, I tried my watch on LTE again and it didn't work, and add to that I can't call make calls(rx or tx) on my phone even though data works!!
This is getting to be a fiasco worthy of it's own opera.
09-23-2018 08:44 PM - edited 09-23-2018 08:49 PM
09-23-2018 08:49 PM
@nasa25 not quite the same when I tap the celluar plan on the watch app it comes up with a dialogue box saying unable to connect try turning on Bluetooth... blah blah etc.
09-23-2018 09:06 PM
09-23-2018 09:46 PM
Is it weird that I'm excited to see my error message change from WS516 to WS300?!?! I feel like I've made a step in the right direction and now have a more common error message lol