Message boards :
Number crunching :
Odd re-occuring issue with Android device
Message board moderation
Author | Message |
---|---|
FalconFly Send message Joined: 5 Oct 99 Posts: 394 Credit: 18,053,892 RAC: 0 |
Hmpf, every now and then I run into trouble with crunching on an Android device (Samsung Galaxy S4). After installation (or re-installation) of the official BOINC client, initially everything runs fine. Since I have to limit the device to "use 1 processor" due to overheating issues, I have to enter the preferences at least once. As soon as I do that, the device of course creates its local set of preferences (visible in the event log). However, something else changes as well : It from there on also states "suspended network activity (user request)" which of course I never did and I don't even have that setting. And that's where it's crunching its cache dry, just to never upload a single workunit again and of course not getting new ones. Since I can't access all of its client preferences, it's usually the end of story. Does anybody know how to convince Android BOINC that I never suspended network activity ?! I recently updated to the latest version but that didn't change anything. PS. I changed all available preferences around and allowed it to transmit data by all means - but still nothing worked. Naturally, repeating any upload attempt in the projects page also fails (its not accepted and the attempts don't even show up in the event log). Generally, I sure wish that the local preferences/config files of BOINC were at least be stored in a user-accessible location, so in case of everything going wrong it could be deleted or manually edited. Having full access to the options in the advanced preferences would also help. Overall, I periodically run into some preferences-related woes. Sometimes it fails to recognize WLAN on/off states or simply fails to resume after suspending computation for whatever reasons. Generally - it's not running reliably smooth and really never has for me. I do wonder if that's my device acting up or BOINC. |
Mike Send message Joined: 17 Feb 01 Posts: 34264 Credit: 79,922,639 RAC: 80 |
Why not give native boinc a try ? I never had issues with it. With each crime and every kindness we birth our future. |
FalconFly Send message Joined: 5 Oct 99 Posts: 394 Credit: 18,053,892 RAC: 0 |
Yeah, that was my next step as I'm running out of options with the official BOINC client :/ |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
I have not had any of those issues on my Galaxy S4. I would guess you have the dual 4 core 1.6GHz + 1.2GHz variant? Mine is the single 4 core 1.9GHz LTE variant. The only time I see "suspending network communication" is when I pause BOINC from the main screen using the Pause/Play button in the top right. Those also suspends processing of work. So I guess that isn't not the issue you are having. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
FalconFly Send message Joined: 5 Oct 99 Posts: 394 Credit: 18,053,892 RAC: 0 |
Hm, I checked out that NativeBOINC client - and it demands App rights to access personal Files, Images, Videos and Audio files on the device. That's a NoGo right there, as BOINC needs none of that obviously... I guess I'll just leave it be, that's the easiest solution - and it's not like I'm losing a whole lot of computing power because of that anyway ;) PS. I do suspect that this has to do with Samsung Software Updates. Ever since they introduced the KNOX package into the updates, it appears everytime BOINC is losing control over its preferences and I ran into similar troubles with it... Plus, the device always had overheating issues in a few certain applications, so I'm pretty confident the device has issues (I think it's the 1.6GHz version as it doesn't have LTE). It's gonna be my last Android device anyway. |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
I have as much of the KNOX disabled as I can without rooting my phone. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
It from there on also states "suspended network activity (user request)" which of course I never did and I don't even have that setting. Android Boinc of around 7.3.12 vintage suspended Network activity when Computation was suspended, What was the latest version that you upgraded to? without giving a version number no-one actually knows what version you were running, the latest version can means many different things. Claggy |
FalconFly Send message Joined: 5 Oct 99 Posts: 394 Credit: 18,053,892 RAC: 0 |
I ran the 7.4.14 Version, which didn't change anything after its upgrade from 7.3.12 two days ago... I also observed that the tasks were running normal, so computation was running just fine. It really only seemed to be the network activity that BOINC somehow switched to "suspended at user request" without me doing anything. I also did a complete uninstall/reinstall, but the problem returned within a few hours. Resetting the project also didn't help, after initially running fine it as well ran into the very same problem. Rebooting the whole device multiple times also didn't do anything. (all occured while the device was at the charger for the whole time and temperatures running a single task were well in the green) While I do recall having similar issues in the past, I could always solve them with any of above means. Sometimes changing preference back-and-forth did the trick. Not this time though, that was persistent with "ready to upload" workunits being stuck indefinitely and no new work being downloaded as the server was waiting for the others to be uploaded 1st (running SIMAP at the end). During the last 3 weeks crunching SETI WorkUnits (WoW!2014 event), the only issue sometimes was that computation was stopped and failed to resume (for whatever reason, usually overnight with 0 other device activity). But other than that, it was crunching along nicely. Overall, no big deal but at least on my Device, I noted Android BOINC never really did 100% what it should do once a while (ever since release basically). All of it had to do with it not following my preferences correctly - and lately inaccesible preferences being set somehow, effectively rendering itself useless As said, my device could be faulty so it may not necessarily be a BOINC issue after all ... |
Claggy Send message Joined: 5 Jul 99 Posts: 4654 Credit: 47,537,079 RAC: 4 |
Can you post the log of what is happening please, I only see Network suspension when I suspend computation manually with the pause button (which is expected behaviour), when do you see it? If I deselect Battery Or USB connection in 'Power sources for computation' then only computation is suspended, every other method I've tried only suspends computation, not network. Claggy |
FalconFly Send message Joined: 5 Oct 99 Posts: 394 Credit: 18,053,892 RAC: 0 |
No, BOINC is uninstalled from the device and the log did not reveal anything useful anyway (except giving the reason for the failure : "network activity suspended - user request"). The network suspension always occured some 2 hours after starting computation with no other activity and the device not even being touched. I do believe it is possible that the device temporarily lost WLAN connection (standard power-saving feature) and thus entered into network suspend mode. However, even when allowed to transmit data via any means (UMTS), this condition never changed. IMHO has to do with some form of long-standing issue/bug of Android BOINC handling its preferences and reliably detecting device status changes, since it has been with me for so long. One of the earliest issues of that kind I ever observed was that it i.e. detected temperatures being over the threshold but never detected them sinking back again to resume computation). But all in all that's only my best educated guess. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.