Hey Eric,
I haven't confirmed this personally, although I have a device so I'll go test
now. But I the nativeboinc works just fine on android 5.0. When I set up POGS
with a plan class for min and max android version, I was still getting heaps of
PIE errors.
Additionally I believe has long as you have an android plan class that doesn’t
include the android version tag and instead uses the os_version and os_regex
tags then older android hosts are still getting work units.
Cheers
Alex
My plan class:
<plan_classes>
<plan_class>
<name>android_arm_pie</name>
<min_android_version>40100</min_android_version>
</plan_class>
<plan_class>
<name>android_arm_non_pie</name>
<max_android_version>40099</max_android_version>
</plan_class>
<plan_class>
<name>android_arm_pie_old_client</name>
<min_os_version>30400</min_os_version>
<os_regex>^[^\(]+$</os_regex>
</plan_class>
<plan_class>
<name>android_arm_non_pie_old_client</name>
<max_os_version>30399</max_os_version>
<os_regex>^[^\(]+$</os_regex>
</plan_class>
</plan_classes>
-----Original Message-----
From: Eric J Korpela [mailto:[email protected]]
Sent: Wednesday, 13 May 2015 12:25 AM
To: [email protected]; [email protected]; Boinc_projects
List
Subject: [boinc_dev] Proposed server change to android version code.
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.
