Since this conversation has spread out over "several" different threads I want to start a thread here where I may eventually understand what I can try to do about these things.

I am up to 3 Android products. 2 I bought specifically because they were "Android 6" according to the listings.

This is my "newest" Android Tablet. The listing claimed it has an "Android 6".
https://setiathome.berkeley.edu/show_host_detail.php?hostid=8725776
This is my "oldest" (at least from an Android point of view).
https://setiathome.berkeley.edu/show_host_detail.php?hostid=8724359 I recently switched from the "HTC help" client back to the standard Google Play BOINC client now that it is available on Google Play again.
This is my daily operator phone. It runs Android 7+
https://setiathome.berkeley.edu/show_host_detail.php?hostid=8724628

After you take a look at my tasks, could you offer any advice (even advice you previously offered on another thread) about how to "make it work better" for Seti?

As it is, I am running WCG on the Android 7 phone because of the "error out" issues with Seti. I would prefer to run Seti. Even Seti Beta if it will get it into production a little sooner.

Tom

---

A proud member of the OFA (Old Farts Association).

For the "quick" stuff, that I've gathered:

* Your "oldest" will work almost guaranteed (and does seem to be doing it, from what I've seen).
* The "6"... I don't recognize the model, but most of mine have worked; they're LG, though, a little more mainstream I think.
* For 7.0+... It seems to depend on the exact build, but mostly it's a "no". They seem to mostly use 64-bit ARM CPU's with poor support for the 32-bit ARM apps currently in use on SETI. (Other projects are different, of course.)

---

* For 7.0+... It seems to depend on the exact build, but mostly it's a "no". They seem to mostly use 64-bit ARM CPU's with poor support for the 32-bit ARM apps currently in use on SETI. (Other projects are different, of course.) - JLDun

Additionally, some Android 7+ OS, when they accept to execute 32 bit code, do it poorly (low efficiency).

As it is, I am running WCG on the Android 7 phone because of the "error out" issues with Seti. - Tom

Exactly the same situation for one of my devices which has been crunching WCG data after initial attempts to process S@h data failed .

I cannot recommend enough that users contribute (for statistical purposes) to the low impact WUProp@home project, which compiles compatibility & performance stats :

http://wuprop.boinc-af.org/
WUProp@home - Active projects
http://wuprop.boinc-af.org/active_projects.py
WUProp@home - Results
http://wuprop.boinc-af.org/results/delai.py
http://wuprop.boinc-af.org/results/arm.py
http://wuprop.boinc-af.org/results/arm.py?projet=SETI%40home
http://wuprop.boinc-af.org/results/arm.py?projet=SETI%40home&application=SETI%40home+v8
http://wuprop.boinc-af.org/results/arm.py?projet=SETI%40home+Beta+Test&application=SETI%40home+v8

---

Apr 3, 1999 - May 3, 2020