Forum Replies Created
-
Posts
-
hmm. the crash message you gave is useful. might be one of the underlayer package we use updated when recompile. have digger deeper.when we have more effort on this.
-
and the service was running alone. before you reopen netCut. so it might be lost 1 second control , if when reopen and UI was dead.
-
so the service is working alone when UI is completely gone. this inline with the design and expected.
when you change the ip, the service can still catch that. but the service will valid the old IP and remove that IP in 57 seconds. the new IP however should be pick up just as if any new device appear in your network.
again, this has nothing todo with the update. remmber: no code change in service. only price change.
Re error message? App crashed when not at front ? we can’t do anything with that, as background app might been blocked or ignored or killed randomly by OS. not user, or app. plus, it should not bother your usage, since as soon as your reopen netcut, it will start a new service and pick up the saved JALED devices and , start working on it.
take easy .
-
when netCut UI (APP) been destoryed , the service might still running. however, if your start the APP (re-born). the app will kill previous running netCut service by start a new one. this is ensure netCut don’t run over old data. it is by design and not something new.
can you try this?
next time you found the CUT off is not working, instead of reopn netCut. try to do a
1. adb shell
2. su
3. ps | grep netcutsee if netcut service has gone.
because if you open netCut app. for sure it will kill netCut service and restart a new one if the APP is fresh start one (instead of bring from background).
-
hello BetaV1,
can you help do test as
1. instead of quit but keep service running. use one of system tool to kill the app. see if the service still running.
let me know.
I will check further too on this.
