WiFi calling button is stalking me

[Grabber5.0]

Can't figure out who to blame here. I have no interest in using WiFi calling, and have never enabled it, but the stupid toggle button insists on staying in the top row of quick settings. I've moved it out numerous times, and it always comes back and pushes out the 6th button I have set up. Doesn't matter if I just move it past the 6th position or remove it from the full quick settings panel completely, it always comes back to the top row after a few days. Is this an Google bug, a OnePlus bug, or is Sprint causing this?

 

[Rukbat]

Strange, weird, but something that someone would have to have the phone in hand to troubleshoot, unless OnePlus can tell you how to get around that.

It's not a "Google bug" - I've never had a phone that did that. If I put an icon on the 3rd row, it stays off the default row(s). (It's not Google - stock Android has no WiFi shortcut button.)

 

[Grabber5.0]

Yeah I need to post this on the OnePlus community forum. But dumb dumb me deleted the screenshots. Guess I can save them from here.

 

[mustang7757]

Let me see if @Javier P heard anything

 

[Javier P]

Yeah I need to post this on the OnePlus community forum. But dumb dumb me deleted the screenshots. Guess I can save them from here.

Is that the Sprint model? It looks like another "peculiarity" of their specific ROM. Maybe you can switch WiFi calling off in one of the Sprint apps. Sorry, US carrier models are a mystery for me, they are full of surprises.

 

[Grabber5.0]

Is that the Sprint model? It looks like another "peculiarity" of their specific ROM. Maybe you can switch WiFi calling off in one of the Sprint apps. Sorry, US carrier models are a mystery for me, they are full of surprises.

WiFi calling is turned off, that's why it's so maddening. I've never enabled it. It is a "Sprint" model, which is just the T-Mobile model with a Sprint sim card.

 

[Grabber5.0]

It's baaaack LOL

 

[frederickdawg]

I don't even have the quick toggle for wifi calling even when wifi calling is enabled. Device is in2025 type.

 

[Grabber5.0]

Not that I expected it to, but the latest update didn't stop this behavior.