I tried, but "notifications" seems to be all one thing. Couldn't find a way to edit sounds for individual notifications. If you can find, I would be SO grateful!
Sprint and any other carrier with this problem should be putting pressure on Samsung or whomever is responsible for the change to make wifi available again the way it worked previous to having to ping the LTE signal. It appears to only be affecting those networks with weak LTE coverage. Seems like Verizon doesn't have weak LTE coverage so doesn't have the problem. Xfinity mobile should be OK too. But then with good Lte coverage who needs wifi calling! Just us on sprint with no Lte coverage.
Alrihty BREERRUSS. I was only able to find out how to set custom text tones on Textra SMS. It appears all app notifications are the same.
Since I'm the OP ("Original Poster" - I started this thread), I feel I should give everyone an update on my situation. Sadly, I have finally left Sprint AND Samsung after many, many years together (I'm a retired Sprint employee). This problem with the Location Timeout and the inability to utilize WiFi Calling in a dead zone just became too much to overcome, and my Sprint loyalty finally died.
I have gone to Xfinity Mobile and I have a Moto G7 Power, which is VERY similar to my Samsung S8. I haven't lost ANY features but gained Verizon's network AND WiFi Calling works flawlessly! Since I now have four bars at home, I really don't even need WiFi Calling, but it's nice knowing it's available.
Good luck, everyone!
You are assuming that this is a Samsung issue - T-mobile doesn't have this problem...
Sprint should be contacting Samsung as a resaler and having them fix this problem for their customers.
Are you still experiencing the same issues mentioned earlier?
Yes, I am on Note 8. Get the location error notice when not in LTE area. Calls drop when using wifi calling. It's unreliable. Wifi calling is needed in poor sprint reception areas not when LTE is available. Sprint has this wrong!
I get that frustration. We haven't had any updates on this yet.
The only change I've seen is that I get a notification about location timeout briefly; it then goes away automatically. Still having the error, still get the notification, but at least it disappears quickly. Almost as good as turning this notification off, since no fix for the problem so it's useless to keep telling me.