Great to know for the day I decide to upgrade my old tablet. Don't forget to run http://wuprop.boinc-af.org/index.php on it so that your device can finally appear here ^.^ (for the record I know you already are a participant to this project otherwise I'd have remained silent)

I just bought a new Samsung Galaxy Tab A 10.5, which has a 64bit CPU and a 64bit kernel, but the user space is made 32bit by Samsung, so the EABI is recognized as ARMv7a, thus Seti sends the 32bit apps that the CPU cannot process.

---

Apr 3, 1999 - May 3, 2020

I just bought a new Samsung Galaxy Tab A 10.5, which has a 64bit CPU and a 64bit kernel, but the user space is made 32bit by Samsung, so the EABI is recognized as ARMv7a, thus Seti sends the 32bit apps that the CPU cannot process.

Hello i was using android 7.0 on samsung p580 tablet with boinc witout problems and updated to oreo 8.1 now seti@home wus always gives computation error.

---

BOINC still works on a by-debt basis, so if Seti has done a lot of work eventually Einstein will take over until it has run equally or a little more work and then it'll switch back to Seti again. All normal under BOINC 7.

---

I get no more SETI@home tasks on my Android 7.1.1 device. Only Einstein@home tasks.
Tullio

---

Thank you for clarifying that up for me.

I am running 801 tasks on my Ulefone with Android 7.1.1 and I did nothing to choose them.
Tullo

---

No, there is no way to specify that you want to run only v8.01 bar rooting your phone and installing an anonymous platform file specifying the application, then manually uploading that application as well. Too much trouble on a handheld device.

---

My Galaxy S7 edge seems to be one of the devices having issues. I've read the thread, but honestly I'm having trouble following along so I apologize in advance if this was already answered and I missed it.

I'm wondering if there is a way to request only v801 tasks on affected devices? It seems a waste to spend all the computing power running v800 take that are going to fail.

My ARM64 CPU has also an onboard GPU Mali-G71, which is not used by SETI. Einstein@home BOINC server does not recognize it.
Tullio

---

That still doesn't solve why none of the ARM7 clients seem to like this phone -- perhaps that has more to do with it running on Oreo (Android 8) than anything else.

Pointing back to Mr.Kevvy's fipo:
The technical reason behind this is that the SETI@Home Android client is 32-bit and has never been ported to Android's 64-bit CLANG C++ suite. Some devices have a 32-bit subsystem to run these older 32-bit apps. (much like desktop OSes do so you can still use your older programs in Windows 10 64-bit, for example) but some do not and the client will not launch. Even if the 32-client does work, tasks may complete slowly compared to a native 64-bit client. (Thanks to Dr. Korpela for confirming this.)

I surmise that with 'the client' Mr.Kevvy means the science application(s) here, not the BOINC client (for which it shouldn't matter, although I think it's 32-bit only, so to allow it to run on any Android version).

---

there is also a DSP processor inside ^^

https://developer.qualcomm.com/software/hexagon-dsp-sdk/dsp-processor

not used for Seti ...

---

It still reports your CPU as being:

ARM
ARMv7 Processor rev 4 (v7l) [Impl 0x41 Arch 7 Variant 0x0 Part 0xd03 Rev 4]

Can you post what it says for the Model from your account, you computers, details?

And if you haven't yet, can you post what brand and model Android device this is? I know you said the Snapdragon version, but that doesn't always meam it's true.

For instance, the Archos device I have should have a 32-bit CPU, but in reality it has a 64-bit CPU. I suspect that it lives in the wrong outer casing....

My details are the same as you've given above.
According to a CPU identifier program on my phone, the chipset is an MSM8920. According to Qualcomm's web site that's a Snapdragon 427 4 core A53 @ up to 1.4 GHz (64 bit). The program reports the following -
Chipset: MSM8920
Processor: Rev 4 (v7l)
Design: Cortex A53
Architecture: ARMV7L
CPU Cores: 4x1401 MHz
Freq. range:960-1401 MHz
...
CPU ABI: ARMEABI-V7A
CPU ABI2: ARMEABI
Revision: r0p4
Implementation: 0x41
------------------
According to the similar CPU-Z:
Cores: 4
Architechture: ARMv7 Processor rev 4 (v7l)
Board Name: msm8937
Chipset: MSM8920
Speed: 960 - 1401 MHz
---------------------
And according to AIDA64:
SoC: Qualcomm Snapdragon 427 (MSM8920)
Architecture: 4x ARM Cortex-A53 @ 1401 MHz
Instruction set: 64 bit ARMv8-A (32 bit mode) <---- Ah ha! Here seems to be the key to where all the confusion is. The 427 can run as a 32 bit processor apparently.
Supported ABIs: armeabi-v7a, armeabi
--------------------------------------------------------------------
So it seems that all the confusion (at least on my part) is not knowing that my phone HAS a 64 bit processor (ARMv8 capable), but it is only running as a 32 bit (so only ARM v7) chip.
That still doesn't solve why none of the ARM7 clients seem to like this phone -- perhaps that has more to do with it running on Oreo (Android 8) than anything else.

---

7.4.53

---

I am running 801 tasks on my ARM64 CPU in a Ulefone smart phone. Both SETI@home and Einstein@home tasks run well. Android is 7.1.1.
Tullio

What BOINC app are you using?

Tom

---

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

It still reports your CPU as being:

ARM
ARMv7 Processor rev 4 (v7l) [Impl 0x41 Arch 7 Variant 0x0 Part 0xd03 Rev 4]

Can you post what it says for the Model from your account, you computers, details?

And if you haven't yet, can you post what brand and model Android device this is? I know you said the Snapdragon version, but that doesn't always meam it's true.

For instance, the Archos device I have should have a 32-bit CPU, but in reality it has a 64-bit CPU. I suspect that it lives in the wrong outer casing....

If you set that you want to test beta software on the Boinc site on Google Play, you will get 7.14.2 which has a new routine for detecting CPUs. It might detect the CPU correctly.

Trying that for a couple of days. BONC Beta on Android is version 7.14.1 according to the "about" screen. So far everything is still erroring out, but we'll see if we can't get a working client in a day or two. Fingers crossed.

---

If you set that you want to test beta software on the Boinc site on Google Play, you will get 7.14.2 which has a new routine for detecting CPUs. It might detect the CPU correctly.

---

The ARMv7 is a 32-bit CPU. You won't get the v8.01 app on that device.

Not all Android devices manage to run all the Seti applications correctly. If you see continuous errors, your device is one that cannot be used here, no need to continue trying.

You can still try it with any other project out there.

Ah, and therein is the problem. The phone actually has a Snapdragon 425 which is a 64 bit 4x Cortex-A53 1.4 GHz -- technically an ARMv8. Since BOINC is saying it's an ARMv7, I'll never get the correct 64 bit client (8.01). I'll just have to carry on with the devices I currently have. (Or save my pennies for an RTX 2080ti or similar.)

8-)

---

I am running 801 tasks on my ARM64 CPU in a Ulefone smart phone. Both SETI@home and Einstein@home tasks run well. Android is 7.1.1.
Tullio

---