I've made a change to the SETI@home beta server code regarding android version selection. The change is if min_android_version is 0 or not set in a plan_class, that plan_class can be valid for hosts that do not report an android version.
The current stock server code will refuse to send an android app to a client that doesn't report its numeric android version (which is not the same its kernel version). As far as I can tell there are two cases where this occurs... 1) The client is running an old version of the BOINC client which does not include support for PIE code or run on PIE only versions of android. 2) The client is running Native BOINC, which does not include support for PIE code or run on PIE only versions of android. If that's true, absence of an android version number indicates that non-PIE code is supported, and PIE may or may not be supported, so non-PIE executables can be safely sent. This shouldn't affect projects that only support PIE executables, as they already need to specify a min_android_version. What it would affect is any project that currently limits a plan class to less than a specific android version, but does not want BOINC clients that do not report android version number to get work for that plan_class. They would need to specify a non-zero min_android_version, like 1. That's a lot of words for a 1 line code change. To push or not to push? That is your question. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
