My essential phone runs Android 10.
some projects seem like they are running, but when I come back to it, they all have computation errors.
Is this due to Android, or the phone entering sleep mode?

I have other, older phones that I would want to add to run boinc on, but am not sure which ones wouldn't give the computation errors (eg: an older LG phone running Android 6, a chinese phone running android 4, etc...)

I think this is an issue with how BOINC is compiled against Android 10. When I upgraded my old phone to Android 10 I now get 100% computation errors. Old Android still works - they need to re-compile the BOINC client for Android.

they need to re-compile the BOINC client for Android.

He.
Singular.
When he has time.

Well, as I see it, BOINC itself runs fine on Android 10. It's just that the science applications from the projects no longer work correctly. They're what doing the calculations and thus the calculation errors. Compiling BOINC for Android versions higher than say 8 shouldn't matter in this. That only needs to matter if BOINC itself crashes upon starting on Android 10, and it doesn't. It runs fine.

---

Well, as I see it, BOINC itself runs fine on Android 10. It's just that the science applications from the projects no longer work correctly. They're what doing the calculations and thus the calculation errors. Compiling BOINC for Android versions higher than say 8 shouldn't matter in this. That only needs to matter if BOINC itself crashes upon starting on Android 10, and it doesn't. It runs fine.

Yes, but all projects?

Ask them. BOINC has no control over the projects or what they do with their applications.

When project tasks err constantly report that to the projects as they'll have to find out what changed and fix their apps.

And yes all projects because none have released apps for Android 10.

---

I wonder if it's not something as simple as port forwarding, or something as simple as a changed memory address space..
Something Boinc could possibly correct for each project, to maintain compatibility.. (that is, if it's the same issue on each project).

On the other hand, some projects start, but error before the first percent comes in.
Others just crash right away.
So I don't think it's the same for each project.

I wonder if it's not something as simple as port forwarding, or something as simple as a changed memory address space..
Something Boinc could possibly correct for each project, to maintain compatibility.. (that is, if it's the same issue on each project).

BOINC is just a managing agent, it doesn't do anything else with regards to the science applications. It just downloads them from the project and starts them when found there is work for the application in queue. BOINC doesn't manipulate firewalls, port numbers, memory addresses, black magic or anything else.

Before Android 10, both BOINC and the science applications worked - albeit on most projects since Android 7 only with 32bit CPUs on a 32bit Android OS and 64bit CPUs on a 64bit Android OS, not with a 64bit CPU and 32bit Android OS.
Since Android 10 BOINC still works - it doesn't immediately crash and exit - but the science applications err on all tasks. Meaning that something in the way the science applications address memory, work space or anything else, fundamentally changed between Android versions. That's either for the projects to solve with new applications, or perhaps that Google has to fix it as there may be a bug in Android 10. Anyone taken it up with Google already?

---

https://einsteinathome.org/it-it/host/12789879 shows a host at Einstein running Android 10, doing Arecibo tasks and finishing them without errors (https://einsteinathome.org/host/12789879/tasks/0/0).

---

https://einsteinathome.org/it-it/host/12789879 shows a host at Einstein running Android 10, doing Arecibo tasks and finishing them without errors (https://einsteinathome.org/host/12789879/tasks/0/0).

Unfortunately, the owner of that machine has posted

I just upgraded on of my Android devices to Android 10 and it doesn't receive other WUs.

I think the completed tasks must have been finished - or at least issued - before the Android version upgrade. The Einstein server is now rejecting requests for new work, with

Couldn't match OS version '4.14.116 (Android 10)' with required regexp 'Android [987N65]|Android 4\.[1-9]|3\.4\.[0-9]'

The server is rejecting it, after many tasks returned back with computation errors.