-
Notifications
You must be signed in to change notification settings - Fork 417
FR : Properly killed syncthing binary #96
Comments
This error shouldn't usually occur, and restarts/exits work fine for me. What device and Android version do you have? Logcat would also be helpful. |
I will get back to you about this. I have this issue with multiple devices, it has been there since I started testing ST for android for couple months. thanks |
I've noticed this when trying to restart the GUI too quickly. If I wait 15-20 seconds before restarting it seems to be fine. Scott |
I've experienced the same problem. At times the app has hung (with very high CPU usage) while displaying the "Waiting for API" message. Despite waiting a few minutes nothing happens. Then I:
At the end, I have no choice but to restart the phone. |
I'Ve experienced the "Waiting for API" hanging quote often but didn't go as far as yourself to track it down so I cannot contribute any insights. |
This should not happen any more with 0.5.x, because any leftover syncthing instance is killed on start. Only if there's another app or another syncthing instance (with different API key) running, this could still happen. But then a device restart should fix it. But it will only be properly fixed by #46. @ovizii Could you post a logcat please? |
Sure but keep in mind it's working fine right now. http://pastebin.com/acjW5QpX |
Hi
One of the main issue I have with this tool is that it never kills its own process when exiting or restarting it. Restarting it via the gui is almost useless because it never restarts properly and at times I have to just restart my tablet which is an inconvenience. Not a life threatening issue for sure but it would be nice if restarting is done properly so we could test things out much easier.
Sometimes I kill the process using android`s running apps but then it is not a solution because recurrent restarts of this app ends up in crash at start with some message
"
Syncthing Binary Crashed
The syncthing binary has exited with error code 2.
If this error persists, try reinstalling the app and restarting your devic
It seems like when a health ST restart is needed, the best way is to restart the tablet.
I hope that the dev could address this issue so that we could test out versions with a nicer setup
thanks
The text was updated successfully, but these errors were encountered: