As the topic says, the NR Android client dies if idling in the background too long due to Android's memory management automatically killing apps to keep memory free. This wouldn't be an issue if not for the fact that NR is basically ALWAYS in the background because it's a VPN client - i.e. you launch it, connect, forward a port, and then forget it and don't access it again unless you need to change your forward. The usage pattern for this app, basically, all but guarantees that it will be killed prematurely by the OS.
The CORRECT solution to this, or ANY android app that runs in the background 90% of the time, is to run it as an Android SERVICE rather than a normal foreground app. Why NR doesn't work this way is beyond me.
In an effort to fix this, I'm now trying my third different memory manager to attempt to keep all my memory free all the time with NR set with a -17 (never kill) process priority and/or in the memory manager's ignore list. For whatever reason, the process priority doesn't stick, and whilst the other memory manager won't kill apps in its ignore list, the OS itself does so anyway.
These solutions seem to extend the time before NR is killed from 15 minutes to around 45 minutes, but I want NR running, in the background, without my intervention, 24/7, as I suspect many users do. These efforts are, even if they worked, stop gap solutions for a problem that desperately needs to be fixed within NR itself.
I have emailed with NR support previously about this. I was provided with an alternate build to try that STILL doesn't run NR, even partially, as an android service. It does seem to list the client as a "permanent" host in the Network Config tool on windows, meaning I can rename it so I don't have 2 android devices both named "localhost" so it DOES help, but it does NOT fix the issue I actually have with the constant closing in the background. Can someone please, PLEASE create a build of the NR client that ACTUALLY runs the NR client as a SERVICE, not anything else, just RUNS IT AS A SERVICE, to fix this once and for all?
|