I love the fact that we can now use the android app to remote into managed devices. It works well when the user is already logged in...
The problem I'm experiencing is when I remote control a Windows device and have to login. I bring up the keyboard no problem and try typing the password to that computer. What I am typing on my keyboard isn't typing in the password box on the PC. In other words, it never seems to respond and type the password letters as I am typing, hence I cannot login (invalid password). I suspect it has something to do with how Android on Samsung deals with autofill. Ironically, I don't have this problem when using the Team Viewer app on the same phone. That fact leads me to believe that it is a problem with the Pulseway Android App.
Using a Samsung Galaxy Note 9 running Android 10.
I've been trying to turn on my computer when I'm away from the house using both mobile data and another WiFi connection. When I'm on the same network the wake up command works but if I'm using mobile data I'll get the message "Wake up command failed" and when I'm on another network it says "wake up command sent" but nothing happens. I have the necessary port forwarded (UDP 9) and through the Pulseway android app port monitor I can see it works. Any help would be greatly appreciated.
I am attempting to install pulseway on my raspberry pi 3b+, and have downloaded and installed the correct file from the pulseway website, and made sure that my openssl libraries are up to date and correctly setup. I followed through with the given installation instructions and repeatedly the pulseway service is unable to be started. When executing the command sudo systemctl start pulseway, the command works and presents no errors. Upon checking the app or the list of all services, however, pulseway is not shown as a service and there is no devices connected to the app. See the attached images for the output of sudo systemctl status pulseway
On new Gallaxy S10 with Android 9 Pulseway app ignores Do Not Disturb schedule. So audible alarms wake up me all night long.
Settings on phone are the same, Do Not Disturb schedule is set to mute everything, except alarms, favourites and repetitive calls. It is the same setting on my old Samsung s2 Note and s7 edge. But only on newest S10 Pulseway rings at night, while older android devices are mute.
I guess Android 9 must somehow diferently clasify alarms, and pulseway tones are then wrongfully clasified as alarms, thus ignoring DoNotDisturb rules.