-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Turning off WiFi disconnects local client #11
Comments
Are you connecting with native boinc client (inside device)? Native client have addres 127.0.0.1, and shouldn't be disconected when WiFi will be disabled. |
Native Client, yes. Apparently I can't save the log file - or at least can't find it. The last line says: "Suspending network activity - wifi network was disabled". When I disable WiFi I get two pop-up messages: Is there a log I can copy that may contain more info? Apparently bugcatcher mode cannot be enabled - because it's stock android? |
Thank you. If boinc client is working after disconnecting (you can simply reconnect without restarting), this mean that is problem with nativeboinc (RPC communication with client) and in this case bugcatcher is not necessary. |
Sorry, I don't have Eclipse installed right now - sooner or later I'll install it again, then I could install the SDK and send you the logs. Interestingly, the client seems to reconnect by itself after a few seconds - I didn't notice before because I immediately manually reconnected it. [edit]BTW, it doesn't matter if the phone is connected to the charger, PC (mode MTP), or not at all. |
Quick update: I think now that the client isn't really disconnected - because when I leave the manager and immediately enter again, all tasks are working again, without me restarting the client. That is what I thought was the client reconnecting itself, apparently. |
LG Optimus 4X HD (P880), running Albert@Home on 2 CPUs.
I only turn on WiFi to upload finished results, it seems that every time I disable WiFi, there is an error in NativeBoinc and the client disconnects. The app itself remains stable, as it catches the problem. I can immediately reconnect the client and everything is fine.
The text was updated successfully, but these errors were encountered: