Skip to content
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

Open
Cyberman-tM opened this issue May 6, 2013 · 5 comments
Open

Turning off WiFi disconnects local client #11

Cyberman-tM opened this issue May 6, 2013 · 5 comments

Comments

@Cyberman-tM
Copy link

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.

@matszpk
Copy link
Owner

matszpk commented May 6, 2013

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.
PS: Check your WIFI configuration, may be some wrong in WiFi setup or you installed some WiFi utility.

@Cyberman-tM
Copy link
Author

Native Client, yes.
I have no WiFi utilities installed as far as I know - it's stock LG Android 4.0, few apps installed.

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:
Error - Client disconnected
Client error - Error happens during BOINC operation

Is there a log I can copy that may contain more info? Apparently bugcatcher mode cannot be enabled - because it's stock android?

@matszpk
Copy link
Owner

matszpk commented May 6, 2013

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.
Edit: if possible you can get android logs for nativeboinc (by using adb, android sdk for eclipse sdk). For me, will be interesting only logs with WARN,ERROR,FATAL priority. Ofcourse this is only my proposal (you needn't get android logs for me) and I will revise my code again.

@Cyberman-tM
Copy link
Author

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.
In the meantime, I've installed this "aLogcat" app, would that be of use to you? I tried to read the logs, but for me it's too much Android-inside - all I could gather was that there are no Fatal priority logs, but plenty of the rest.

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.

@Cyberman-tM
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants