Client keeps on waking the server sporadically
spown andy 00
my android(5.0.1) UR client (3.5.2 full) wakes my PC (sleeping or hibernating doesn't matter) sporadically. Sometimes when another app issues a notification. Sometimes with no apparent reason. Always when I exit the UR app (close it, but keep services running). If force complete stop via settings/apps or kill only the UR services the server remains sleeping no matter what I do with android device. I can close UR app without WoL as long as no UR services are active.
when I used the free UR version I didn't have that problem.
Sounds similar to my problem:
Some service is running in the background it tries to reconnect, even after exit.
What operating system are you using on the PC?
spown andy 00
its win10 but why does it matter? pc is virtually turned off when the problem occures. the client sends the WOL signal to my router, not to the OS, not even to the pc as a hardware...
I'm also facing this problem on two separate Windows 10 machines. I reported this issue back in May but it was basically shrugged off and never fixed so I had to resort to disabling WOL altogether since there is no way to disable UR from sending out a WOL upon reinitialization of the app either in the background or foreground.
I don't know why UR continues to restart its services in the background even after fully exiting the app which therefore sends out a WOL but I should mention that I have an android wear watch and notice there is a UR "WearHandheldService" that always starts along with the "BackendService". Could it be that the wear device initiates UR on the phone every so often to maintain a connection with the UR wear app? If that's the case then there should be the ability to disable wear integration altogether. Does anyone else affected also have an android wear watch?
A good option that I think UR should provide is to let users decide whether or not they want the app to send out a WOL upon starting the app. As of now there is no way to disable WOL even after removing the MAC address from the server settings in app.
Really hoping this issue gets fixed now that others are starting to take notice. I'm sure many other users are also having their computers randomly wake up all the time and that they just haven't been able to pinpoint it to UR yet.
Well turns out the problem was with improper configuration of my network adapters. The default settings of Intel / Windows has WOL set to wake on any packet with a "Pattern Match" which will wake the system up when any network device is pinging it. That needs to be disabled and only wake on a "Magic Packet" should be enabled.
Take a look here for more information on Windows WOL:
I apologize for my mistake in thinking the problem was with UR.