Nothing you can do with the Android apps until BOINC sends you every application and maybe in a year will sort out which one is the fastest and most reliable. Just forget about them and don't worry.Seti@Home classic workunits:20,676 CPU time:74,226 hours

Blame the ancient BOINC scheduler code that hasn't been updated in over 5 years. No money - no developers = no progress.

I have 3 Android devices and I have my phone that tries 12 different applications every few days. Most, like you have observed, have never returned a single valid result. Yet the scheduler still sends me those tasks. It is broken, just accept it and not worry about it.Seti@Home classic workunits:20,676 CPU time:74,226 hours

I am a little bit concerned that BOINC doesn't Suspend correctly when I want to use it for normal use !
I have tried various different preferences for the last few days.
I have also allowed all 8 cores to crunch data, and I can still listen to internet radio at the same time, without any glitches.
However, if I try to watch YouTube or Netflix etc, I have to Suspend BOINC Manually first, or everything freezes.
I have tried setting CPU Usage limits as low as 30%, Got slightly better results by setting CPU Time limit to 80 or 90%

If anyone else is thinking of getting a low cost Android TV box from eBay or similar, you could do a lot worse than this box.
Some sellers are still selling Quad Core TV boxes for almost the same price !

I normally never mess with the Project Compute Preferences and leave them default. I have never seen them work the way they are described to work. I find it easier to limit the amount of cpu work that the project attempts by using the <project_max_concurrent> setting in an app_config file or a statement in app_info.

Gives me finer control over system resources and I never have BOINC ever hog the system resources so that it impacts daily driving or YouTube video playback or whatever.Seti@Home classic workunits:20,676 CPU time:74,226 hours

It appears that many of them are happening because of Applications that are not compatible.

If you think you spotted pattern, just manually abort tasks that were assigned to faulty plan class. Then you will dry quota for that particular plan class much faster and will continue with remaining working ones.SETI apps news
We're not gonna fight them. We're gonna transcend them.