Delayed notifications over Wi-Fi - Samsung Galaxy Note 9 Questions & Answers

I am having issues with receiving notifications on time over Wi-Fi after screen was turned off for 10+ minutes. Usual delay is about 5 - 10 minutes. I don't have any problems with same applications and scenarios over mobile connection. These apps are chat and video call apps: WhatsApp, Viber, Duo, Slack. This is especially annoying for calls, because I just get missed call notification (after 5 or so minutes or if I manually launch the app), instead of a call ring. I ticked all of them off in "Optimise battery usage" section. Same behavior on Oreo and now on Pie version. Same behavior on my home network, my parents' house network and at my work place. Browsing, streaming and all other things over internet work, no issues with it, so the connections were good. I have SMN960F model, if that matters.
At first, I thought this issues are caused by Doze when the phone is in "Connected to Wi-Fi" state. I don't even know if Doze could distinguish those two states (Connected to Wi-Fi or Connected to Mobile). But since everything works just fine over mobile, I doubt it is Doze. Now I think it is something related to my Wi-Fi settings, but I can't figure it out.

@Japro
Did you ever figure this out?

Related

WiFi keeps turning off during sleep

Running any Marshmallow rom on this phone always turns the wifi off after about 30 seconds of screen-off time. This is incredibly frustrating because it breaks any app I have running in the background that uses wifi. For example netflix on chromecast always loses it's connection and I cant control my chromecast because the wifi disconnected. It's also needlessly using cellular data while asleep.
I have checked all the wifi options and theyre all set correctly. There is a whole 10 pages of complaints about this on a simple google search with no real solution provided. You guys have any ideas?

wi-fi calling preferences updated

Ever since I updated my Note 9 (Tmobile, stock OS) to Pie, I get the "wi-fi calling preferences updated" message numerous times throughout the day. There is no longer an icon in the status bar when Wifi calling is connected. The network switches even when I am on a call (and the call drops).
Are there others here having this issue? T Mobile staff appear to be surprised at this happening (though on their forum there are several threads about this with no solution). Any help will be much appreciated. Thanks!
I am having exactly the same issue, I really hope there is a solution to this because it's causing me tremendous connection issues when I am on my call.
would that be normal if on the go the location changes? just spitballin
using a system that has been updated versus starting from scratch on that new OS version is bound to cause issues. forum is riddled with users having weird issues post pie upgrade.
do your selves a favour and factory wipe and be done with it.
Your device is supposed to switch during a call to help keep the call going. You'll hear a beep which signifies your wifi signal is getting too weak to maintain the call. If you have a network connection, the device will switch to it, but if you're in a building where the is none, it will drop the call unless you stay within range of the wifi.
I went ahead and just adjusted the notification settings so that it doesn't even bother popping up. I think the wifi calling icon thing might be a Android Pie issue with Google knocking out certain permission allowances. I will have to do some digging into that.
I have, and have had for a long time, this very issue. I have had it over a few phones and Android versions. T-mobile is pushing down a change to 'WiFi Calling Preference' setting changing it to Cellular preferred. T-Mobile denies it but I have screen shots of the notification when they do it.
This is a problem for me since I rely heavily on WiFi calling with marginal cell signal strength. I am about to leave TMobile because of it.

wifi Calling problems.... (help? pls?)

First off, I can make outgoing calls 100% of the time, and never have any problem except a split-second delay (as expected with VOIP)
Receiving calls though......
First, wifi calling randomly turns off, with a note I find later about "wifi calling is not available at this location" ---- yes, I have poor reception, and I know wifi calling requires an always-active GPS signal so rain or clouds can kill it --- but it never turns back on once the storm/cloud/whatever is gone, it stays turned off until I manually turn it back on.
Second, even when it is turned on, I will randomly get no notification - no ring, no vibrate, the screen stays black, and no "miss call" notification, I just get told later that someone tried to call me and it went straight to voicemail.
Third, when it does register an incoming call, I will swipe to answer and the phone app will... kinda half-freeze... it acts like it's trying to answer the call, where the red end button appears, but all the other buttons are greyed out except message. It's in a strange limbo-like state of being answered and not... when this happens usually the other party will connect and can hear me, but whatever they say never reaches me.
Fourth, I answer the call, everything seems fine, I say hello and just hear my own voice echoing, and even though I answered the call, they never connect and end up on voicemail.
I know that WiFi calling is a "new technology" (even if we've been using VOIP for years....) and Sprint hasn't "ironed out the bugs" yet, but is there anything I can do to improve it?
I have tried doing a hard reset on the phone, updating PRL/settings/OS, changing the phone data mode from LTE to CDMA, sprint tech changed out my SIM card for a new one, airplane mode (which doesn't work because it turns off GPS)... none of it works and I still miss a good 60%+ of my calls... any other suggestions?
Ashton_Durkhun said:
First off, I can make outgoing calls 100% of the time, and never have any problem except a split-second delay (as expected with VOIP)
Receiving calls though......
First, wifi calling randomly turns off, with a note I find later about "wifi calling is not available at this location" ---- yes, I have poor reception, and I know wifi calling requires an always-active GPS signal so rain or clouds can kill it --- but it never turns back on once the storm/cloud/whatever is gone, it stays turned off until I manually turn it back on.
Second, even when it is turned on, I will randomly get no notification - no ring, no vibrate, the screen stays black, and no "miss call" notification, I just get told later that someone tried to call me and it went straight to voicemail.
Third, when it does register an incoming call, I will swipe to answer and the phone app will... kinda half-freeze... it acts like it's trying to answer the call, where the red end button appears, but all the other buttons are greyed out except message. It's in a strange limbo-like state of being answered and not... when this happens usually the other party will connect and can hear me, but whatever they say never reaches me.
Fourth, I answer the call, everything seems fine, I say hello and just hear my own voice echoing, and even though I answered the call, they never connect and end up on voicemail.
I know that WiFi calling is a "new technology" (even if we've been using VOIP for years....) and Sprint hasn't "ironed out the bugs" yet, but is there anything I can do to improve it?
I have tried doing a hard reset on the phone, updating PRL/settings/OS, changing the phone data mode from LTE to CDMA, sprint tech changed out my SIM card for a new one, airplane mode (which doesn't work because it turns off GPS)... none of it works and I still miss a good 60%+ of my calls... any other suggestions?
Click to expand...
Click to collapse
do u have a vpn active?
plus i dont think GPS has anything to do with "WIFI" calling.
as long as wifi is connected to a proper wifi network, that should be all you need.( other than if a VPN is activated or wifi network is congested/ to many AP ssids with overlapping channels, then it should work fine.)
I did before the hard reset (one-dot), I dont now. so it didn't seem to matter...
Ashton_Durkhun said:
First off, I can make outgoing calls 100% of the time, and never have any problem except a split-second delay (as expected with VOIP)
Receiving calls though......
First, wifi calling randomly turns off, with a note I find later about "wifi calling is not available at this location" ---- yes, I have poor reception, and I know wifi calling requires an always-active GPS signal so rain or clouds can kill it --- but it never turns back on once the storm/cloud/whatever is gone, it stays turned off until I manually turn it back on.
Second, even when it is turned on, I will randomly get no notification - no ring, no vibrate, the screen stays black, and no "miss call" notification, I just get told later that someone tried to call me and it went straight to voicemail.
Third, when it does register an incoming call, I will swipe to answer and the phone app will... kinda half-freeze... it acts like it's trying to answer the call, where the red end button appears, but all the other buttons are greyed out except message. It's in a strange limbo-like state of being answered and not... when this happens usually the other party will connect and can hear me, but whatever they say never reaches me.
Fourth, I answer the call, everything seems fine, I say hello and just hear my own voice echoing, and even though I answered the call, they never connect and end up on voicemail.
I know that WiFi calling is a "new technology" (even if we've been using VOIP for years....) and Sprint hasn't "ironed out the bugs" yet, but is there anything I can do to improve it?
I have tried doing a hard reset on the phone, updating PRL/settings/OS, changing the phone data mode from LTE to CDMA, sprint tech changed out my SIM card for a new one, airplane mode (which doesn't work because it turns off GPS)... none of it works and I still miss a good 60%+ of my calls... any other suggestions?
Click to expand...
Click to collapse
Oh sprint. I always had network connectivity issues with them. I wouldn't be surprised if this is something that is wrong on sprints end
bober10113 said:
plus i dont think GPS has anything to do with "WIFI" calling.
as long as wifi is connected to a proper wifi network, that should be all you need.( other than if a VPN is activated or wifi network is congested/ to many AP ssids with overlapping channels, then it should work fine.)
Click to expand...
Click to collapse
You have to have an active GPS signal for "e911 services" --- yes the app claims you can set your location manually, but doing so does nothing and as soon as my phone loses cell/GPS reception, wifi calling goes off and will NOT come back on till reception is restored (also I've used two of Sprints Femtocells and both of them required an active GPS for e911 so....)
Bober_is_a_troll said:
Oh sprint. I always had network connectivity issues with them. I wouldn't be surprised if this is something that is wrong on sprints end
Click to expand...
Click to collapse
yeah.... since about the start of this year my LTE speeds have gone down (though only in actual use! --- run speedtest and magically I have like 50mbps, even though I can't watch youtube even at 144p without it buffering and asking my phone "Alexa Next Track" returns an error about connectivity) Also my reception in my home has gotten worse in the last couple months --- for the last 17.5 years I've been able to make/receive calls on sprint over normal cellular without issue as long as it wasn't raining (yes, I've been with Sprint for almost long enough to raise a child.... they started out as the best carrier in my area, believe it or not), but now even though my phone reports 2 bars (out of like 8 or 10), I recieve almost no calls, and drop outgoing ones very frequently unless I switch to WiFi Calling.
So... yeah... I figured it was actually bad implementation on either Samsung or Sprint's part, but I was hoping there was something I could do to improve it....
Ashton_Durkhun said:
You have to have an active GPS signal for "e911 services" --- yes the app claims you can set your location manually, but doing so does nothing and as soon as my phone loses cell/GPS reception, wifi calling goes off and will NOT come back on till reception is restored (also I've used two of Sprints Femtocells and both of them required an active GPS for e911 so....)
yeah.... since about the start of this year my LTE speeds have gone down (though only in actual use! --- run speedtest and magically I have like 50mbps, even though I can't watch youtube even at 144p without it buffering and asking my phone "Alexa Next Track" returns an error about connectivity) Also my reception in my home has gotten worse in the last couple months --- for the last 17.5 years I've been able to make/receive calls on sprint over normal cellular without issue as long as it wasn't raining (yes, I've been with Sprint for almost long enough to raise a child.... they started out as the best carrier in my area, believe it or not), but now even though my phone reports 2 bars (out of like 8 or 10), I recieve almost no calls, and drop outgoing ones very frequently unless I switch to WiFi Calling.
So... yeah... I figured it was actually bad implementation on either Samsung or Sprint's part, but I was hoping there was something I could do to improve it....
Click to expand...
Click to collapse
Switch telco's... Sprint dropped the ball. They invested in. Winax , then LTE took off. They've been behind ever since

Wifi Calling Preferred Default w/adb -Verizon

Is anyone able to access the global wfc_ims_mode in the Pixel 4 or any later versions of android than 9? Here is the method I am referring to.
I need to know this because I am currently using an OG pixel and I manually set the Wifi Calling to Wifi Preferred as we know the toggle button verizon offers inside settings is a dud.
Without forcing the global wfc_ims_mode to 2, my phone is essentially a paperweight as all data and more importantly calls and text will always default to cellular which I have 0-0.5 bars of service at my home.
Thanks!
Deeper explanation and rant - cynicism and blame incoming.
A quick summary of Wifi Calling Preferred - There is Wifi Calling, yes I know, that toggle works and is on. Then there is Wifi Preferred, a separate setting that tells the phone it what connection to default to. This is a toggle that was inside of the the Wifi Calling settings that has been confirmed to do absolutely nothing regarding your phones affinity for wifi or celluar. It is not tied to anything on the side of the android ROM, it is just there to create the illusion that it works. It was supposed to allow people to force the phone you have to use the wifi connection over the mobile connection which really help people on the edge of a service area or, in my case, in .5 miles from a Cal State University with a partially obstructed view of a cell tower.
"But I see "Wifi calling" in the top of my phone sometimes and I have never had problems."
1. Yes, Verizon does allow calls to sometimes initiate through wifi and even stay on wifi for several minutes. However, Verizon has set conditions on what a "good connection" means in order to keep wifi routing of calls AND data to an absolute minimum regardless of how this effects the end users call and data quality. Simply put, if we rate our wifi and cell connections from 1-20 with 20 being spectacular and 1 being awful; Verizon has effectively written boundary rules that say a cellular signal rating of 1 is ALWAYS preferred over wifi signal 20. You could be standing next to a brand new gigabit router with google fiber and full signal, but if Verizon thinks it has .005 % of a bar, then guess what? No call! However, Verizon knows that it must initiate the call with good quality so they use the "wifi calling" (comes up on the top of the screen) to start the call, but as soon as the call has begun, and the phone has detected a signal of 1 on the cellular it will perform a hand-off to the cellular network. Icing on the cake?This is a mono-directional hand-off, meaning wifi MUST handover to the cellular but going from cell to wifi requires the phone disconnecting the call. Outstanding move Verizon!
2. I have 0-1 bars of service where I am so if you have more than that you wont notice the hand-off. I run my business through my phone and I was so tired of missed calls, missed texts, dropped calls, garbled sound, echo. Most people will see the "wifi calling" icon in the top of the phone and assume the entire call took place over wifi. Not the case at all. Just trying to avoid the "I have wifi calling on and everything is fine for me". Yeah, how long do you talk on the phone? How many calls are you getting? How sure are you after reading what I just wrote that the entire call, and every call that takes place in your house just simply because you are home and connected to wifi and one time saw wifi calling on the top is actually using wifi maintaining the call through your ISP??
To get around this, here is a method that I still use on my original pixle XL. I am still running android 9 as the move to 10 seems to have move the wfc_ims_mode select.
This is one of the main reasons I still use this phone. Without Wifi Calling being forced as "Preferred", I know everything will route through Verizons service which is virtually 0 where I am. This results in missed calls, dropped calls, and video qualities jumping around between 144p and 360p.
Would like to know also.
i have tried this method on my Pixel 3 android 10 stock and it didnt work.

WI-FI Sleeping?

This is a problem I've noticed for quite a few months now, before the MIUI 12 update (possibly even saw it on 10).
The best way I can desribe it is the WI-FI connection seems to go to sleep randomly when the phone has been locked.
I won't get any notifications, I won't get any messages through facebook come through etc. The device still says it's connected to my home WI-FI network though. If I try to browse the web or do something else then it will try to do it instead of saying No Internet, it acts like it does have an internet connection (probably because it believes it's connected to a wi-fi network?) but will never succeed.
If I then turn WI-FI off and on again I'll then get bombarded with notifications and messages I've missed.
Is anybody else experiencing this and is there a solution? It's only a 2-second inconvenience to flick the WI-FI off and on, but it's an annoyingly regular occurence and more importantly I'm missing messages and notifications which could be important to me.

Categories

Resources