Hi HBE, I'm having a similar issue getting old clients to receive the correct application version on theSkyNet POGS any chance you could email me a copy of your plan_class_spec.xml file. As that would greatly help me.
Regards Alex -----Original Message----- From: Heinz-Bernd Eggenstein [mailto:[email protected]] Sent: Tuesday, 7 April 2015 10:06 PM To: Stephen Maclagan Cc: [email protected] Subject: Re: [boinc_dev] Android 4.3 hosts not receiving Seti work. Hi! Sorry for the late reply to this one, but I suspect a related problem might still exist for some projects. > It's running an Android older than 5.00, because the client works!!!!!!, >If it was running Android 5, then old Boincs wouldn't work, >and Probably NativeBoinc wouldn't work, This was my initial guess as well, but actually we had quite a lot of computing error results at E@H where the Android version wasn't reported properly (old client), therefore we sent a non-PIE app by default, which failed because the client was running on Android 5 (!!). I suspect that NativeBOINC actually can run on Android 5. In order not to waste resources on the affected devices I'm now using the following workaround: If the OS version string contains the string 3.4.0, the client will get the PIE app version. Rationale: there never was or will be an Android version 3.4.0, so this must be the Kernel version reported by older (native)BOINC clients. AFAIK, the versions of Android that are based on kernel 3.4.0 all support (or even require) PIE, so it's safe to send a PIE app version. This rule might not be perfect (you can always have custom made Android images with whatever kernel version) but this hopefully will catch the vast majority of cases at E@H where some (Native?)BOINC users will be downloading workunit after workunit only to have them fail. Cheers HBE ----------------------------------------------------------------- Heinz-Bernd Eggenstein Max Planck Institute for Gravitational Physics Callinstrasse 38 D-30167 Hannover, Germany Tel.: +49-511-762-19466 (Room 037) From: Stephen Maclagan <[email protected]> To: Eric J Korpela <[email protected]>, Cc: "[email protected]" <[email protected]> Date: 08/03/2015 18:15 Subject: Re: [boinc_dev] Android 4.3 hosts not receiving Seti work. Sent by: "boinc_dev" <[email protected]> Wild6-NJ's host is still reporting it's Android version as 4.3 on the website, the website hasn't been updated to show it as 4.3.0, and is still failing to get work: http://setiathome.berkeley.edu/show_host_detail.php?hostid=7495128 You really don't need to know the Android version in all cases, If a host is running an old Boinc that doesn't report the Android version contacts a project, you automatically know that: It's running an Android older than 5.00, because the client works!!!!!!, If it was running Android 5, then old Boincs wouldn't work, and Probably NativeBoinc wouldn't work, and neither would be able to contact the project, you don't know if it is pre or post Android 4.1, But what you do know is that non-PIE apps will work, So send it non-PIE work. Users are also reporting they now can't upgrade Boinc to the latest version because their Android is too old: http://boinc.berkeley.edu/dev/forum_thread.php?id=10084 http://setiathome.berkeley.edu/forum_thread.php?id=76729&postid=1650642 Seems Android 4.1 is now the minimum, Shouldn't the Play Store also have a non-PIE Boinc for pre-Android 4.1 hosts? Claggy From: [email protected] Date: Sun, 22 Feb 2015 09:13:05 -0800 Subject: Re: [boinc_dev] Android 4.3 hosts not receiving Seti work. To: [email protected] CC: [email protected]; [email protected] The problem with NativeBoinc is that it hasn't been update to report the Android version. What's being reported as "2.6.32.15-gf5a401c" is not the Android version but the linux kernel version. That can't be used to determine the Android version. As far as BOINC goes, someone needs to compile more recent BOINC code to work on older Android versions and release it in the App store to fix that one. On Sun, Feb 22, 2015 at 6:01 AM, Stephen Maclagan <[email protected]> wrote: Neither of those two hosts have received work since the change, if it's been applied that is, One of the hosts now doesn't exist either. Other complications are that hosts run Native Boinc don't receive Stock work either: http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=69846 But do receive work if they run the NativeBoinc supplied Seti app via anonymous platform: http://setiathome.berkeley.edu/show_host_detail.php?hostid=7207503 I would hope that NativeBoinc's running old kernels like my Android 2.2.2 equipped host, (that's below the Official Boinc's minimum OS version) Android 2.6.32.15-gf5a401c would still receive Stock work because of that reason: http://setiathome.berkeley.edu/show_host_detail.php?hostid=6975058 (It's off doing work at Albert, so hasn't needed to ask for work from Seti) It won't help Dr Who Fan while running Native Boinc, But he does have a Boinc upgrade option, My HTC Desire S doesn't have that option. Claggy > Date: Mon, 16 Feb 2015 14:51:22 -0800 > From: [email protected] > To: [email protected]; [email protected] > Subject: Re: [boinc_dev] Android 4.3 hosts not receiving Seti work. > > I changed the schedule code so that it parses either "4.3.0" or "4.3". > Eric, feel free to deploy this on S@h. > -- D > > On 16-Feb-2015 1:02 PM, Stephen Maclagan wrote: > > There's a pair of Android 4.3 hosts that seem to have been caught by Eric's > > limiting Seti work to pre-Android 5 hosts, They are both reporting themselves as > > Android 4.3, as opposed to Android 4.3.0 which seems strange: > > > > http://setiathome.berkeley.edu/forum_thread.php?id=76729 > > > > http://setiathome.berkeley.edu/show_host_detail.php?hostid=7501642 > > > > http://setiathome.berkeley.edu/show_host_detail.php?hostid=7495128 > > > > Do their scheduler logs show anything? > > > > Claggy _______________________________________________ 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. > > > _______________________________________________ > 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. _______________________________________________ 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. _______________________________________________ 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. _______________________________________________ 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.
