Message boards :
Number crunching :
Beta Android app : validation inconclusive
Message board moderation
Author | Message |
---|---|
Send message Joined: 4 May 11 Posts: 27 Credit: 112,091,698 RAC: 0 |
My Android device (Galaxy Nexus) has just completed its firts WU, but it is in validation inconclusive state :( I don't see what's wrong in the stderr output, so if someone whould like to look at it, here's the link to the host : http://moowrap.net/show_host_detail.php?hostid=27376 |
Send message Joined: 20 Apr 11 Posts: 388 Credit: 822,356,221 RAC: 0 |
My Android device (Galaxy Nexus) has just completed its firts WU, but it is in validation inconclusive state :([/url] Thanks for the report. Basically the inconclusive happens because the phone lost two stats units from the input (it should have crunched 9 stats units, but it only managed to return 7). As soon as something else completes the wu fully, this will get partial credit but obviously this is not optimal situation. I've seen this behavior on my own test Nexus and seems to especially get triggered when BOINC Client or the OS needs to suspend/kill/restart our app or BOINC Client during crunching. Everything seems to go more smoothly when I leave the phone to just crunch (and not do anything else with it) for the duration of the wu. That's not how people normally use their phones, though. :) There might be something wrong in our Android wrapper so that it doesn't cope with various oddities that running flakily (by design) on a phone brings. That's why I've left this as a beta app for now as our wrapper or Dnet Client settings might need more tweaks for Android. Also providing even smaller wu for Androids (with only one stat unit instead of the 9 our tiny wus have) might help as this ~5.5h crunch time is a bit long. -w |