This is a bare bones client without NEON optimized routines for SETI@home, but does have NEON FFTW routines. It'll be a while before I can modify the ARMv6 NEON routines to work when compiled under aarch64.

---

I don't think there is a recent Boinc Android that correctly works with Android Arm64 hosts,

Boinc 7.4.53 was the last Boinc built, development has stalled since then:

https://github.com/BOINC/boinc/commits/client_release/7/7.4

Since then there has been frequent reports of no work received:

https://groups.google.com/forum/?hl=en#!topic/boinc-android-testing/eUfr8NoDHQY

https://setiathome.berkeley.edu/forum_thread.php?id=79858

Claggy

Most of the info required for specific plan classes seems to be missing, but an "all aarch64-android" app seem to get sent to at least some hosts using 7.4.53. Six hosts have gotten work at last count.

7.4.53 is unable to get 32 bit apps on aarch64 platforms. I'm not 100% convinced that the 32 bit apps will work. I should try some on my Nexus6p

---

Seeing one that was one of my wingmen - Host 79316 - that seems to be getting "Signal 11" error codes.

core_client_version>7.4.53</core_client_version>
<![CDATA[
<message>
process got signal 11
</message>
<stderr_txt>

</stderr_txt>
]]>

(Edit:) Could the BOINC version have something to do with it? I know I "can't" yet use 7.4.53 on my x86_64 Android tablet...

---

I am running 8 task at the same time on my Nexus 6P, Lets see how this works out :)

Seems a lot of devices are getting signal 11 (SIGSEGV). I'm going to try some of the 32 bit versions on my 64 bit device to see if they work.

---

So far so good, all tasks between 13 and 23%

Using the boinc app from the play Store and connected seti beta via Bam!.

It is taking quite some time though.

The first few tasks have finished, lowest running time was 370 000 seconds with cpu at about 50 000 seconds.
Some tasks are not at 50% yet.

Host info: http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=80690

Task list: http://setiweb.ssl.berkeley.edu/beta/results.php?hostid=80690

Yes, incredibly slow seems to be the consensus.

---

Most of the info required for specific plan classes seems to be missing, but an "all aarch64-android" app seem to get sent to at least some hosts using 7.4.53. Six hosts have gotten work at last count.

7.4.53 is unable to get 32 bit apps on aarch64 platforms. I'm not 100% convinced that the 32 bit apps will work. I should try some on my Nexus6p

Attached my new Samsung S7 to Asteroids and is crunching work from there OK (Seti was down at the time),
Attached it to Seti Main and got no work,
Attached it to Seti Beta, got aarch64 work, but errored with process got signal 11,
I suspect it'll run 32bit apps O.K, I'll downgrade to Boinc 7.4.43 once the Asteroids work is complete.

Additional:
Seti Beta Reports the GPU: opencl_gpu Mali-T880 (3552MB) driver: 1.02
Seti Main Reports nothing

Claggy

Received the v8.01 (arm64-vfpv4) and (arm64-neon) apps, And been crunching Wu's with them O.K (I assume they are 32bit rebranded apps),

But today I started receiving the nopie apps, they don't don't work on Android 6.0.1 strangely enough, and the scheduler shouldn't have sent them.

Host 80807

All tasks for computer 80807

Claggy

The nopie apps are a test. Some had claimed that the pie/nopie designations are switched. Apparently not, but the pie executables still don't work on some android 6/7. I'll disable them once more hosts have gotten them (and failed on them).

---

My Nexus 6P only runs standard tasks, it fails on neon and nopie. (android 7.0)
Should I just keep it going or wait?

I hope to have a faster replacement for the standard task within a couple weeks, so please keep running (or check the apps page to see when I release an update).

---

My Nexus 6P just got stuck in a boot loop, which is a common problem after last androids software update. So I cant run any new tasks until it gets back from repairs which may take some time. Anyways hope there are enough people testing so you can miss me for some time.

Happy Holidays

My Samsung S7 is now only getting work for the 8.00 aarch64 app (which doesn't work) both here and again Seti Main, no work for the arm64-neon or arm64-vfpv4 apps get sent,
has there been any scheduler changes at eithier project?

Claggy

Same scheduler and plan classes as the beta project. Are you getting work for those plan classes at beta?

---

Same scheduler and plan classes as the beta project. Are you getting work for those plan classes at beta?

No, those two plan classes just stopped getting work.

http://setiweb.ssl.berkeley.edu/beta/results.php?hostid=80807&offset=20&show_names=0&state=0&appid=

And the plan classes that do get work are down to 'Max tasks per day' of One:

http://setiweb.ssl.berkeley.edu/beta/host_app_versions.php?hostid=80807

The scheduler on the other hand says 'This computer has finished a daily quota of 1 tasks', even though eight tasks were sent today:

Sun Jan 01 17:21:26 GMT+00:00 2017|SETI@home Beta Test|This computer has finished a daily quota of 1 tasks
Sun Jan 01 17:21:26 GMT+00:00 2017|SETI@home Beta Test|Tasks for Intel GPU are available, but your preferences are set to not accept them
Sun Jan 01 17:21:26 GMT+00:00 2017|SETI@home Beta Test|Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
Sun Jan 01 17:21:26 GMT+00:00 2017|SETI@home Beta Test|Tasks for NVIDIA GPU are available, but your preferences are set to not accept them
Sun Jan 01 17:21:26 GMT+00:00 2017|SETI@home Beta Test|No tasks are available for SETI@home v8
Sun Jan 01 17:21:26 GMT+00:00 2017|SETI@home Beta Test|No tasks sent
Sun Jan 01 17:21:26 GMT+00:00 2017|SETI@home Beta Test|Scheduler request completed: got 0 new tasks
Sun Jan 01 17:21:17 GMT+00:00 2017|SETI@home Beta Test|Requesting new tasks for CPU and Mali-T880
Sun Jan 01 17:21:17 GMT+00:00 2017|SETI@home Beta Test|Sending scheduler request: Requested by user.
Sun Jan 01 17:21:15 GMT+00:00 2017|SETI@home Beta Test|update requested by user
Sun Jan 01 17:21:12 GMT+00:00 2017|SETI@home|This computer has finished a daily quota of 1 tasks
Sun Jan 01 17:21:12 GMT+00:00 2017|SETI@home|No tasks are available for SETI@home v8
Sun Jan 01 17:21:12 GMT+00:00 2017|SETI@home|No tasks sent
Sun Jan 01 17:21:12 GMT+00:00 2017|SETI@home|Scheduler request completed: got 0 new tasks
Sun Jan 01 17:21:10 GMT+00:00 2017|SETI@home|Requesting new tasks for CPU and Mali-T880
Sun Jan 01 17:21:10 GMT+00:00 2017|SETI@home|Sending scheduler request: Requested by user.
Sun Jan 01 17:21:05 GMT+00:00 2017|SETI@home|update requested by user

Claggy

Eric, please look this thread.
https://setiathome.berkeley.edu/forum_thread.php?id=80781
Seems smth wrong with autors file on main.
At least for one of plan classes. Most probably - difference between this file for different plan classes cause all have same version.
On beta work fetched OK by the same device,

---

News about SETI opt app releases: https://twitter.com/Raistmer

Same scheduler and plan classes as the beta project. Are you getting work for those plan classes at beta?

The last time I got work from those two plan classes at Seti Beta was on the 22nd Dec.

Claggy