Hi Everyone,

Hope someone can help out as I'd like to use my phone too for processing WUs. It's a Nexus 5 running Kitkat Android. It's not rooted.

Installed the Boinc client last night and set it to run all night. All the WUs it processed failed. Here is an example:


Name 25ap08ab.23323.2526.438086664204.12.76_1
Workunit 1584787052
Created 4 Sep 2014, 6:05:05 UTC
Sent 4 Sep 2014, 9:48:50 UTC
Report deadline 30 Oct 2014, 5:46:18 UTC
Received 4 Sep 2014, 10:20:33 UTC
Server state Over
Outcome Computation error
Client state Compute error
Exit status 11 (0xb) Unknown error number
Computer ID 7376512
Run time 1 min 11 sec
CPU time 1 min 10 sec
Validate state Invalid
Credit 0.00
Device peak FLOPS 1.53 GFLOPS
Application version SETI@home v7 v7.21 (armv7-vfpv3d16)
Peak working set size 67.46 MB
Peak swap size 70.76 MB
Peak disk usage 0.01 MB

Is this an issue with the application, with my hardware, or with the application configuration?

We're not the Seti forums. Any calculations done by a project's science application and the outcome thereof is something best asked at the project.

That said, the actual error on the taskID is:

<core_client_version>7.4.14</core_client_version>
<![CDATA[
<message>
process got signal 11
</message>
<stderr_txt>
setiathome_v7 7.21 Revision: 2006 arm-linux-androideabi-g++ (GCC) 4.6 20120106 (prerelease)
libboinc: BOINC 7.2.4

Work Unit Info:
...............
WU true angle range is :  0.378721
Optimal function choices:
--------------------------------------------------------
                            name   timing   error
--------------------------------------------------------
                v_BaseLineSmooth (no other)
           neon_GetPowerSpectrum 0.000171 0.00000 
                  neon_ChirpData 0.014007 0.00000 
                    v_Transpose4 0.006511 0.00000 
                opt NEON folding 0.001251 0.00000 
SIGSEGV: segmentation violation

</stderr_txt>
]]>

Signal 11 in Unix terms usually means problems with the memory. If it were on a PC, you could test that with memtest88+.

You may want to look for a memory tester in the Google App store. I see that Stability Test (https://play.google.com/store/apps/details?id=com.into.stability&hl=en) might be able to help you out here.

---

Is this an issue with the application, with my hardware, or with the application configuration?

Problem with the application on specific hardware, you could attach to the Seti Beta project and see if the 7.28 applications are any better, it's been an ongoing problem, some devices run the apps fine, others don't.

Claggy