The issue is VINA, *not* per-se SCC1's build. The SIGSEGV 11 appears on all the Android sciences, worse for SCC1, least for OET1, FAHV as SCC1. [Someone wrote checkpoints for SCC1 are much more frequent, every 5% than for OET which I think is every 12.5%, another potential moment things could go belly up]. Most typical it occurs when 'using' my tablet. Whilst some claim the errors increased on Android 5 and up which enforced PIE memory/execution handling, in my case it was less than before PIE.

Detail discussion on the forums, detail spreadsheet analysis performed while trying to pin the situations this occurs. Typically, 2 cores of 4 [50%], and *not* allowing the battery charge to alternate [not keeping up], which causes a continues stop start stop cycling is the moment where the most fails occur, so leave it alone, suspend BOINC when not on juice except for brief moments to change location, is when fails are minimal. Oh and the battery temp setting is set to 35C, which I think is lower than the default.

Sek,

We have stopped sending out new work on Android for SCC1 because we are seeing a significant number of invalids, this is unrelated to the sigsegv errors. We are still early in the investigation but it will likely require a new binary. We will try and get a new version out in beta with a fix for the invalids and it will also include more debug data for the sigsegv errors.

Thanks,
armstrdj