I've had 2 more, both on my Android 9.0 phone. Both completed in 33 hours and are awaiting validation.

Pete

Got some on one of my Banana PI M3 devices.
However, the CPU efficieny isn't very good. The worst WU had these stats:

BETA_ MCM1_ 9800033_ 0070_ 1-- android_3b03982
4 Valid 2/6/20 02:32:51 2/6/20 12:41:12 0.27 / 10.10 129.1 / 104.0

So, CPU time only 0.28h and elapsed time over 10 hours. Is this perhaps a RAM size issue? Perhaps I'm running 6/8 cores with a total of 2GB of ram and it makes it have to write to disk? Will have to try lower the amount of simultaneous WUs.

UPDATE: Wingman needed 7.14h so I am actually suspecting that CPU time of 0.27h is a miscalculation by BOINC? How can the difference be so large otherwise?

One WU errored out: BETA_ MCM1_ 9800033_ 0073_ 0--
Here's the log:

Result Name: BETA_ MCM1_ 9800033_ 0073_ 0--


<core_client_version>7.4.53</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
WARNING: linker: ../../projects/www.worldcommunitygrid.org/wcgrid_beta17_map_7.53_arm-android-linux-gnu: unused DT entry: type 0x6ffffffe arg 0x1e50
WARNING: linker: ../../projects/www.worldcommunitygrid.org/wcgrid_beta17_map_7.53_arm-android-linux-gnu: unused DT entry: type 0x6fffffff arg 0x2
Commandline = ../../projects/www.worldcommunitygrid.org/wcgrid_beta17_map_7.53_arm-android-linux-gnu -SettingsFile MCM1_9800033_0073.txt -DatabaseFile dataset-sarc-draft1.txt
Settings File
DateOfDesign = 20191101
Designer = Krembil/cubes
WorkOrderID = MCM1_9800033_0073
DatasetID = sarc-draft1
RSeed = 5554

NumberOfGenesInStartingSignature = 20
NumberOfGenesInSignatureMin = 20
NumberOfGenesInSignatureMax = 20
StartingGeneSignatureAlgorithm = randomFixedLengthSearch
SearchAlgorithmNumberToCreate = 1782
//SearchAlgorithmSequentialStartPosition = 304
RunPermutationAlgorithm = 0
//PermutationGroups = C
//PermutationGroupsForReplacement = F
//PermutationAlgorithm = insertEnumerateFromGroup
//PermutationsNumIterations = 5
//OptimizationAlgorithmFrequency = 0 0 1

// Do we need these?
FBeta = 1.5
SimAnnealIMax = 20000
SimAnnealAlpha = 0.9996
//Pseudocounts = 0.2

FitnessFn = 0
MinFitness = 0.4

NReps = 100
VMethod = CV
TrainFrac = 0.7
// Alternatively
////NReps = 10
////TrainFrac = 0.7
////NFolds = 10
//VMethod = LOO

// Apparently the default
//ModelType = SVM
SvmArgs = "-v 0 -t 3 -c 0.01 -d 2 -r 0 -s 1"
SvmLearnLimit = 250000



[03:34:05] Initializing
terminating with uncaught exception of type Exception
/buildbot/src/android/ndk-release-r18/external/libcxx/../../external/libcxxabi/src/abort_message.cpp:73: abort_message: assertion "terminating with uncaught exception of type Exception" failed
SIGABRT: abort called

Exiting...

</stderr_txt>
]]>

How are your stats on CPU time vs Elapsed time looking? From my post above you can see I am having very strange figures, so it would be interesting to know.

Easy, but at your own peril, default 75% 'because' they can run warm at full load. Some folks have set up their crunching tablets/phones in an array with a USB fan on it. Upright or leaning is better than lying down for sure for more air circulation aka cooling.

I see, thanks, that would explain some of the results I returned w.r.t. CPU/elapsed time. But not all, since I had some with like 0.27h CPU time having Elapsed time of 10.1 hours.