I found that to run both SETI@home and Einstein@home on my Ulefone smart phone with an ARM64 CPU I have to connect the phone to a power outlet, so it is not likely that smart phone users will contribute much to BOINC.
Tullio

There are settings that allow you run on your battery down to XX% as well as run only when you are connected to a charger.

Tom

---

A proud member of the OFA (Old Farts Association).

Do know though that the v8.01 application (aarch64-android-linux-gnu) works fine on Android 7 (and maybe 8). It is just the v8.00 arm64-vfpv4 and v8.00 arm64-neon that don't work. If you allow for these to run errors, eventually they will be on the 1 task per day limit for these applications and you should get mostly tasks for the v8.01 app which will finish fine. Like so:

<core_client_version>7.4.53</core_client_version>
<![CDATA[
<stderr_txt>
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
setiathome_v8 8.00 Revision: 3553 aarch64-linux-android-g++ (GCC) 4.9 20140827 (prerelease)
libboinc: BOINC 7.7.0

Work Unit Info:
...............
WU true angle range is :  2.179504
Triplet: peak=7.971074, time=32.25, period=0.7381, d_freq=1420280761.72, chirp=0, fft_len=16 
Spike: peak=24.17157, time=90.6, d_freq=1420285295.82, chirp=-11.657, fft_len=64k
Spike: peak=24.38553, time=90.6, d_freq=1420285295.82, chirp=-11.672, fft_len=64k
Autocorr: peak=19.17839, time=33.55, delay=2.2229, d_freq=1420283599.19, chirp=11.804, fft_len=128k
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
Restarted at 38.55 percent.
Triplet: peak=8.216975, time=77.97, period=0.6095, d_freq=1420284035.8, chirp=-20.632, fft_len=64 
Triplet: peak=9.033834, time=105.1, period=0.1442, d_freq=1420281559.56, chirp=-25.79, fft_len=256 
Triplet: peak=8.289671, time=105.1, period=0.1442, d_freq=1420281560.43, chirp=-49.001, fft_len=256 
Triplet: peak=8.519686, time=23.36, period=0.9011, d_freq=1420279556.98, chirp=-51.579, fft_len=64 
Triplet: peak=8.200883, time=105.1, period=0.1442, d_freq=1420281557.19, chirp=-74.79, fft_len=256 
Triplet: peak=8.559072, time=105.1, period=0.1442, d_freq=1420281558.06, chirp=-98.001, fft_len=256 

Best spike: peak=24.38553, time=90.6, d_freq=1420285295.82, chirp=-11.672, fft_len=64k
Best autocorr: peak=19.17839, time=33.56, delay=2.2229, d_freq=1420283599.19, chirp=11.804, fft_len=128k
Best gaussian: peak=0, mean=0, ChiSq=0, time=-2.124e+11, d_freq=0,
	score=-12, null_hyp=0, chirp=0, fft_len=0 
Best pulse: peak=0.5680848, time=84.9, period=0.01807, d_freq=1420284106.26, score=0.9061, chirp=82.527, fft_len=16 
Best triplet: peak=9.033834, time=105.1, period=0.1442, d_freq=1420281559.56, chirp=-25.79, fft_len=256 

Flopcounter: 16219663652779.679688

Spike count:    2
Autocorr count: 1
Pulse count:    0
Triplet count:  7
Gaussian count: 0
03:07:14 (15539): called boinc_finish(0)

</stderr_txt>
]]>

This v8.01 application works on my windows 8. Glad I found this in here. Thanks man!

Even then it's a limited list. I'll see in the coming weeks if I'll add WuProp to my devices. Add some to the list.

That's a pretty limited list. I have other ARM devices like my RPi or my Nano working.

True but we are talking Android OS here rather than Linux/Raspberian so it is consistent with the OS under discussion.

Tom

---

A proud member of the OFA (Old Farts Association).

That's a pretty limited list. I have other ARM devices like my RPi or my Nano working.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Seems like someone posted a list of "known" working phones and/or tablets.

http://wuprop.boinc-af.org/results/arm.py?projet=SETI%40home&application=SETI%40home+v8
--edit---

Without knowing how (often) the list updates, I do know it leaves out my LG Stylo 5, which I've attached in the past couple of weeks.

---

Android 9 host with full errored tasks ...

https://setiathome.berkeley.edu/show_host_detail.php?hostid=8858057

---

Seems like someone posted a list of "known" working phones and/or tablets.

I can't find it and it looks like the only working Android phone I had crunching has died.... or the battery went Kaput.

---edit--- Found it -----
http://wuprop.boinc-af.org/results/arm.py?projet=SETI%40home&application=SETI%40home+v8
--edit---

Tell me about a cheap, best performing, older model phone that will crunch Seti@Home?

Tom

---

A proud member of the OFA (Old Farts Association).

Hi!
I'm trying to run Seti from the Android 9 client, but all I get is computation errors, both on Rockchip and AMLogic ARM quad core chipsets (Amlogic 905W, 905x, and Rockchip 3139 if I'm not mistaken, that's the 1,5Ghz quadcore version).

Any idea when the SETI@Home Android client will start working for Android 9?

It'll work if both your CPU and Android OS are matched in bitness, so 32bit/32bit and 64bit/64bit, but not if you're mismatched with a 64bit CPU and 32bit Android.

You can check with AnTuTu Benchmark (https://play.google.com/store/apps/details?id=com.antutu.ABenchMark&hl=en) -> My Device -> Android (version (bitness) and CPU Type what they are.

---

Do NOT try Beta just now - it is down for an indeterminate time as they have suffered a hardware failure.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

You can try with SETI@Home Beta. I'm receiving some WUs on my devices.

---

ASUS X570 E-Gaming
AMD Ryzen 9 3950X, 16 core / 32 thread 4.4 GHz
AMD Radeon Sapphire RX 480 4GB Nitro+
Nvidia GTX 1080 Ti Gaming X Trio
4x16 GB Corsair Vengeance RGB 3466 MHz

They need to find someone with the time and ability at a price that the project can afford.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Any idea when the SETI@Home Android client will start working for Android 9?

---

None of the projects have applications at the time of writing that are Android 10 compliant, thus pointing out other projects won't help in this case, all will err. That won't be fixed until the projects release new applications that are built for Android 10 specifically.

---

Why the newer Android versions are incompatible with SETI@home

Until the code is updated, your smartphone can contribute in other worthwhile projects (look for projects with the Android logo).

I just upgraded one of my Android devices to Android 10 and it doesn't receive other WUs.

https://einsteinathome.org/it-it/host/12789879

Can you fix this problem?

https://setiathome.berkeley.edu/show_host_detail.php?hostid=8856048

---

Apr 3, 1999 - May 3, 2020

I just upgraded one of my Android devices to Android 10 and it doesn't receive other WUs.

https://einsteinathome.org/it-it/host/12789879

Can you fix this problem?

https://setiathome.berkeley.edu/show_host_detail.php?hostid=8856048

---

ASUS X570 E-Gaming
AMD Ryzen 9 3950X, 16 core / 32 thread 4.4 GHz
AMD Radeon Sapphire RX 480 4GB Nitro+
Nvidia GTX 1080 Ti Gaming X Trio
4x16 GB Corsair Vengeance RGB 3466 MHz

I just upgraded one of my Android devices to Android 10 and it doesn't receive other WUs.

https://einsteinathome.org/it-it/host/12789879

Can you fix this problem?

---

ASUS X570 E-Gaming
AMD Ryzen 9 3950X, 16 core / 32 thread 4.4 GHz
AMD Radeon Sapphire RX 480 4GB Nitro+
Nvidia GTX 1080 Ti Gaming X Trio
4x16 GB Corsair Vengeance RGB 3466 MHz

You have an ARMv7 Processor rev 4 processor, which is 32bit. You're getting tasks sent for ARMv6 and ARMv7 type processors, all err with "process got signal 6". This won't fix itself with a different science application, you can stop trying.

Process aborted with signal 6 means that the process itself has found that some essential prerequisite for correct function is not available and voluntarily killing itself, rather than the process being killed by the kernel because it ran over resource limits or looked at memory addresses funny or something.

You're probably missing a driver or library that the science apps were built with or expect to be there. While it's possible to figure this out on Linux, it's neigh on impossible to do so on Android without rooting the phone, and even then it's not so easy.

---

Thanks, I will try that. Interesting that I didn't find this thread when I searched the first time. Evidently, the search function is case sensitive.
Cheers
Charles

---