First noticed "issue":
Occasionally, when adding a project- at the project login, it will flash white and not move (automatically) to the next step. Most of the time when this happens I would need to exit back to the main client, then try to log in again; it does work the second time. (This also happened with 7.18.0)

This is on two different LG Stylo 5's, Android 9.

---

https://boinc.berkeley.edu/dl/

Hi,
I've been BOINC'ing for years with differing levels of success as different devices and versions come and go.
7.18.1 has my all my usual setting up the creek. I run WCG, Universe@Home, (and sometimes Rosetta but just lately Android isn't happy with that).
The phone is getting really hot and whilst charging the battery is running down not charging up.

What are the ideal settings for an Android 10 running those projects?
Cores=4
CPU limit=? (I've set 100%)
Pause above=? (I've set 50%)
RAM limit=? (I've set 50%)
I would go for the default but uninstall/reinstall retains my custom settings.
Right now, battery is just draining whilst running 4 Universe@H WU.
Thanks

I don't know why but BOINC (the lastest one - 7.18.1) for Android is so buggy: it crashes everytime I change the settings

I had that with the 7.16 and 7.18.0 clients, but no longer with the 7.18.1 client, so this seems to be a case of YMMV.

can't receive any tasks from Einstein@Home but 7.16 can

What's the error you get?

always error while computing on yoyo@home or moo! wrapper

This is because of their app that isn't optimized to run on 64bit Android AND 64bit CPU.

(but Android < 6 can compute)

Yep, that's because this is either a 32bit Android running on a 64bit CPU, or a 32bit Android running on a 32bit CPU. As soon as both cases are 64bit, the 32bit science application can no longer run correctly. This is something you have to report at the project and ask them to make a 64bit compliant science application and have a plan class detect the right CPU/OS to send the right application.

Also I remember the golden day when many many scientific projects are support Android, it gave people the chance to contribute to science with just their Android phone even the cheap one.

AFAIK the current projects in the list have always had the ARM/Android support, and those projects missing have just stopped being a project (like Seti@Home).

The phone is getting really hot and whilst charging the battery is running down not charging up.

Get active cooling on the phone. Just a (small) fan next to it is sufficient.

My 4 device farm has a 140mm fan blowing air over them at 5V (half speed). which is sufficient to cool the batteries down. All 8-core CPUs run at only 4 cores, because when using the present big.LITTLE architecture, data is only done on the smaller more energy efficient cores, not on the larger, faster, more power hungry ones. Those are reserved by Android for the operating system only. Running 8 tasks anyway will just double down on the 4 smaller cores.

Does the Event log say anything (besides "0 tasks")?

---

https://boinc.berkeley.edu/dl/

Caught a fleeting glimpse of the 'will resume when battery is' "issue"; this was right after playing a particular game on my Android phone (Shop Titans). As an incidental, S.T appears to be a memory hog somehow, despise reporting using "273 MB average over past 3 hours"; I'd does still cause BOINC to pause. (The whole thing including cache data takes 750+ MB, and is consistent enough on pausing BOINC (or at least dropping it out of memory)- even when running no tasks, just the client- that I know to do one or the other, but not both.

---

https://boinc.berkeley.edu/dl/