Thanks!terRemote wrote:first of all, the next version will probably contain an "action on error" option for the webview that is called whenever the content could not be loaded. There will also be a "reload" action for the WebView so that what you wanted to achieve should be possible by then.
I have never had that problem, excpet once, but terRemote was not running.terRemote wrote:About the crash of mpg732: This is new to me. A similar behavior was once reported for the HTTP action, though. Do you use that? If it happens again, please try to reproduce the error for better diagnosis. That would be a big help.
Regarding the Web View, I did another test, and I launched the app immediately after a reboot of my tablet, when the system is still busy initialising itself and is usually not well responsive. I got again the 404 error. It seems that the web is available only after some time, even if the wifi icon in the android taskbar shows that the connection is established. I don't remember if my previous test has been made in similar conditions, but it's possible.
BTW, Chris, I've noticed that terRemote starts on boot. I suppose it's to verify if the "Use background service" option is on, and if it's the case, to launch it. Since I don't need the background service, I have disabled terRemote from starting on boot with the Boot Manager Xposed plugin. Can you confirm that disabling it is safe?