My Android device is receiving two versions of tasks. The 507 version runs correctly but the Data collect version 5 v5.03 (android_arm_non_pie) tasks always fail. I am trying to understand why the older version tasks are being generated and distributed unless it is for different versions of Android OS.

If it is for different versions of OS then why are incorrect versions of the tasks being distributed to my device ?

Can someone help me out a little here ?

Thanks
Bill F

---

In October 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

My Android device is receiving two versions of tasks. The 507 version runs correctly but the Data collect version 5 v5.03 (android_arm_non_pie) tasks always fail. I am trying to understand why the older version tasks are being generated and distributed unless it is for different versions of Android OS.

If it is for different versions of OS then why are incorrect versions of the tasks being distributed to my device ?

Can someone help me out a little here ?

Thanks
Bill F

Which Project is this?

Uhh this one.

I've seen that too in the past. Some androids would seem to randomly get either one.

Yes, seen this many times. Usually sorts itself out after 3 attempts to get the correct task.

Pete

---

Pretty close ... it did 3 cycles wrong then right swapping back and forth then did 6 correct versions back to wrong version and now another 6 with the correct version.

Bill F

---

In October 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

Uhh this one.

LOL!!!

I had my Android devices deactivated during the summer. Now where the temperatures are cooler again I am putting them back online. After the upgrade to the newest BOINC version all WUprop units turn out to be invalid. So far my devices produced close to 40 of them all of them being of the number 5 version, not a single one is valid! Does anybody else have that problem? My devices run World Community Grid.

---

I had my Android devices deactivated during the summer. Now where the temperatures are cooler again I am putting them back online. After the upgrade to the newest BOINC version all WUprop units turn out to be invalid. So far my devices produced close to 40 of them all of them being of the number 5 version, not a single one is valid! Does anybody else have that problem? My devices run World Community Grid.

I have that problem as well. The new Android BOINC release (which is great because it has RPC enabled) fails with WUProp tasks.

You can try the Android BOINC client from efmer. This is the same efmer that created BOINCTasks. That should also support RPC and supposedly doesn't die on WUProp tasks. I haven't personally been able to use it because I have been unable to load it on my Fire tablets. But others have reported good results with it.

Or you could drop back to the previous official BOINC client.

---

Want to find one of the largest known primes? Try PrimeGrid. Or help cure disease at WCG.

I had my Android devices deactivated during the summer. Now where the temperatures are cooler again I am putting them back online. After the upgrade to the newest BOINC version all WUprop units turn out to be invalid. So far my devices produced close to 40 of them all of them being of the number 5 version, not a single one is valid! Does anybody else have that problem? My devices run World Community Grid.

I have that problem as well. The new Android BOINC release (which is great because it has RPC enabled) fails with WUProp tasks.

You can try the Android BOINC client from efmer. This is the same efmer that created BOINCTasks. That should also support RPC and supposedly doesn't die on WUProp tasks. I haven't personally been able to use it because I have been unable to load it on my Fire tablets. But others have reported good results with it.

Or you could drop back to the previous official BOINC client.

Has anyone been able to figure out the changes that are blocking wuprop so it can get fixed?

I run Boinc version 7.18.1 and Wuprop version 5 on Android without problem.

But I do not use de Remote access setting for the client.

I think I remember from a remark on a other project that use of that setting could cause problems.

Has anyone been able to figure out the changes that are blocking wuprop so it can get fixed?

The relevant stderr output lines for a couple of failure cycles in a failed Android task are:

<core_client_version>7.18.1</core_client_version>
01:20:17 (15127): Mise en veille (derniere requete date de moins de 30 secondes
01:20:17 (15127): can't connect to Unix domain socket
01:20:17 (15127): Erreur reception active_result
01:20:46 (15127): Erreur reception build.prop
01:21:17 (15127): Mise en veille (derniere requete date de moins de 30 secondes
01:21:17 (15127): can't connect to Unix domain socket
01:21:17 (15127): Erreur reception active_result
01:21:46 (15127): Erreur reception build.prop

The specific problem is the "can't connect to Unix domain socket" line. Domain sockets allow data exchange between processes running on the same system, and my guess is WUProp uses a domain socket to collect information about the other tasks from the Boinc client.

Core client versions 7.16.* don't have that problem, so it must be related to the changes in Android Release 7.18.1. The change most likely to have caused this is the one allowing remote monitoring of Android clients (Android remote monitoring #1699), in particular #4233: Remote monitoring: Enable remote monitoring in client and Manager and the related #4231: Remote monitoring: Add checkbox 'Enable Remote Monitoring'.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

Has anyone been able to figure out the changes that are blocking wuprop so it can get fixed?

The relevant stderr output lines for a couple of failure cycles in a failed Android task are:

<core_client_version>7.18.1</core_client_version>
01:20:17 (15127): Mise en veille (derniere requete date de moins de 30 secondes
01:20:17 (15127): can't connect to Unix domain socket
01:20:17 (15127): Erreur reception active_result
01:20:46 (15127): Erreur reception build.prop
01:21:17 (15127): Mise en veille (derniere requete date de moins de 30 secondes
01:21:17 (15127): can't connect to Unix domain socket
01:21:17 (15127): Erreur reception active_result
01:21:46 (15127): Erreur reception build.prop

The specific problem is the "can't connect to Unix domain socket" line. Domain sockets allow data exchange between processes running on the same system, and my guess is WUProp uses a domain socket to collect information about the other tasks from the Boinc client.

Core client versions 7.16.* don't have that problem, so it must be related to the changes in Android Release 7.18.1. The change most likely to have caused this is the one allowing remote monitoring of Android clients (Android remote monitoring #1699), in particular #4233: Remote monitoring: Enable remote monitoring in client and Manager and the related #4231: Remote monitoring: Add checkbox 'Enable Remote Monitoring'.

I agree I am using 17.18.1 on two Samsung phones. One fairly old and one a little newer with different versions of Android OS and both are working fine with RPC disabled.

Bill F

---

In October 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

I run Boinc version 7.18.1 and Wuprop version 5 on Android without problem.

But I do not use de Remote access setting for the client.

I think I remember from a remark on a other project that use of that setting could cause problems.

That's correct, if you don't use RPC, then it works. Of course, if you don't use RPC, then what's the point of using the newer BOINC client? You might as well be using the old client.

---

Want to find one of the largest known primes? Try PrimeGrid. Or help cure disease at WCG.

I run Boinc version 7.18.1 and Wuprop version 5 on Android without problem.

But I do not use de Remote access setting for the client.

I think I remember from a remark on a other project that use of that setting could cause problems.

That's correct, if you don't use RPC, then it works. Of course, if you don't use RPC, then what's the point of using the newer BOINC client? You might as well be using the old client.

The point for using the newer version without RPC is to take advantage of additions that were added for the newer hardware in newer phones and for better support of the newer Android OS versions.

Bill F