S-Voice no network connection error after phone non-use

[davidrusher]

I get a "no network connection" error when using Samsung Svoice after my Samsung S5 phone has been sleeping. This problem is not associated with the screensaver kicking in. It takes longer before the wakeup failure bug kicks in.

It appears that S-voice tries to access the 4G network while the phone is still sleeping (or some part of the phone is still in a power-saving mode). If I do the same Svoice request again, it always works the second time. So this is definitely an issue of some power saving function not being turned off before S Voice attempts to use 4G.

I cleared Svoice cache in Settings::Apps and also Android cache. Bluetooth is on and my earbud works fine.

I hate to turn off WiFi -- that send Dropbox over 4G. Is wifi the problem? If I keep wifi on during sleep would that fix it?

I do not have any extra power saving software. My phone is not rooted and I cannot root it. There is definitely and OS issue here. Is there an app I can install that will keep 4g alive enough to handle an outbound request from S-Voice? What can we do about this?

 

[davidrusher]

I think keeping wifi on during sleep might fix this problem. I am trying it now --( Settings::Wifi::Advanced).

I suspect that S-Voice does not have a retry and fails if WiFi is sleeping. Mine fails the first time -- but works if I repeat the command -- which tells me that the first command causes Wifi to wake up but the command fails because S-Voice does not wait for Wifi to wake up before sending the command.

They could cache the command until Wifi wakes up. Or put a retry into the code so S-Voice tries twice -- the first time wakes up wifi. Or they could put a put a setting in the OS to select "Always use 4G for S-Voice" (which would work better on busy WLANS).