I fixed the AUTHORS file on main. The same problem probably exists on beta. I will investigate between meetings today.

---

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

I see no mention of ARM64 in https://setiweb.ssl.berkeley.edu/beta/plan_class_spec.xml

Is this file the same as that is actually in use?

Claggy

Just as a Note, I've reported the ARM64 api24 app doesn't work:

http://setiweb.ssl.berkeley.edu/beta/forum_thread.php?id=2266&postid=60860

All you get is Boinc reporting pseudo progress, that restarts from zero when the device is restarted, and stderr.txt showing repeated start ups as far this:

setiathome_v8 8.00 Revision: 3642 aarch64-linux-android-g++ (GCC) 4.9.x 20150123 (prerelease)
libboinc: BOINC 7.7.0

Work Unit Info:
...............
WU true angle range is : 0.011386
Getting CPU Capabilities from /proc/cpuinfo
features: fp asimd evtstrm aes pmull sha1 sha2 crc32

Unable to resolve function unwind_backtrace_signal_arch
Unable to resolve function acquire_my_map_info_list
Unable to resolve function release_my_map_info_list
Unable to resolve function get_backtrace_symbols
Unable to resolve function free_backtrace_symbols
Unable to resolve function format_backtrace_line
Unable to resolve function load_symbol_table
Unable to resolve function free_symbol_table
Unable to resolve function find_symbol
one or more symbols not found. stackdumps unavailable

Claggy