- Jul 21, 2013
- 335
- 94
- 28
Finally received my new Z Flip4 yesterday and got it all set up, transferring data, apps, and settings from my S22Ultra.
One "feature", however, won't load/start -- wifi calling. My house sits in a "low reception/dead zone" between towers so straight cell service is spotty. Previously, I had a microcell device in the house that made connection perfect, but that was discontinued when wifi calling became available.
(My Flip4 is Unlocked on AT&T service)
So, when I go to Settings>Connections I try to toggle Wifi Calling to ON. I get a "notice bubble" at the bottom of the screen that says something like "Loading. Might take a few moments." That sits and sits, then after a couple of minutes it fails to connect and I get notification that Wifi Calling could not be started. Try later.
Went to the AT&T store this morning to get a new SIM card. Same result there. Even tried connecting in SAFE MODE. One of the reps at the store tried on her S22Ultra with same result I had on my Flip4. Only guess they can offer is that it might be a system problem.
Anyone experience similar issue? Is this a backend issue in the AT&T network?
One "feature", however, won't load/start -- wifi calling. My house sits in a "low reception/dead zone" between towers so straight cell service is spotty. Previously, I had a microcell device in the house that made connection perfect, but that was discontinued when wifi calling became available.
(My Flip4 is Unlocked on AT&T service)
So, when I go to Settings>Connections I try to toggle Wifi Calling to ON. I get a "notice bubble" at the bottom of the screen that says something like "Loading. Might take a few moments." That sits and sits, then after a couple of minutes it fails to connect and I get notification that Wifi Calling could not be started. Try later.
Went to the AT&T store this morning to get a new SIM card. Same result there. Even tried connecting in SAFE MODE. One of the reps at the store tried on her S22Ultra with same result I had on my Flip4. Only guess they can offer is that it might be a system problem.
Anyone experience similar issue? Is this a backend issue in the AT&T network?