<core_client_version>8.0.0</core_client_version>
<![CDATA[
<stderr_txt>
BOINC client version 8.0.0
Application: ../../projects/asteroidsathome.net_boinc/period_search_10220_aarch64-android-linux-gnu
Version: 102.20.1.1
Hardware	: MT6761V/CAB
CPU implementer	: 0x41
CPU architecture: 8
BogoMIPS	: 26.00
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4
Number of processors: 4
CPU current frequency: 2001 MHz
Available memory: 2.8 GB
Using ASIMD (NEON) SIMD optimizations.
Hardware	: MT6761V/CAB
CPU implementer	: 0x41
CPU architecture: 8
BogoMIPS	: 26.00
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4
Number of processors: 4
CPU current frequency: 2001 MHz
Available memory: 2.8 GB
Using ASIMD (NEON) SIMD optimizations.
2024-05-10 23:44:55 (14730): called boinc_finish(0)

(This is on a LG phone, Android 9.)

---

And for a Moto G Power 2022 Android 12 (a primary difference between them is how they handle CPU frequency):

<core_client_version>8.0.0</core_client_version>
<![CDATA[
<stderr_txt>
BOINC client version 8.0.0
Application: ../../projects/asteroidsathome.net_boinc/period_search_10220_aarch64-android-linux-gnu
Version: 102.20.1.1
Hardware	: MT6765H
CPU implementer	: 0x41
CPU architecture: 8
BogoMIPS	: 26.00
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4
Number of processors: 8
CPU current frequency: 2301 MHz
Available memory: 3.7 GB
Using ASIMD (NEON) SIMD optimizations.
Hardware	: MT6765H
CPU implementer	: 0x41
CPU architecture: 8
BogoMIPS	: 26.00
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4
Number of processors: 8
CPU current frequency: 2139 MHz
Available memory: 3.7 GB
Using ASIMD (NEON) SIMD optimizations.
Hardware	: MT6765H
CPU implementer	: 0x41
CPU architecture: 8
BogoMIPS	: 26.00
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4
Number of processors: 8
CPU current frequency: 1351 MHz
Available memory: 3.7 GB
Using ASIMD (NEON) SIMD optimizations.
Hardware	: MT6765H
CPU implementer	: 0x41
CPU architecture: 8
BogoMIPS	: 26.00
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4
Number of processors: 8
CPU current frequency: 2301 MHz
Available memory: 3.7 GB
Using ASIMD (NEON) SIMD optimizations.
Hardware	: MT6765H
CPU implementer	: 0x41
CPU architecture: 8
BogoMIPS	: 26.00
CPU variant	: 0x0
CPU part	: 0xd03
CPU revision	: 4
Number of processors: 8
CPU current frequency: 1218 MHz
Available memory: 3.7 GB
Using ASIMD (NEON) SIMD optimizations.
2024-05-10 23:14:02 (21358): called boinc_finish(0)

---

Samsung A15
Is this bug known?
"process got signal 35"

<core_client_version>8.0.0</core_client_version>
<![CDATA[
<message>
process got signal 35</message>
<stderr_txt>
BOINC client version 8.0.0
Application: ../../projects/asteroidsathome.net_boinc/period_search_10220_aarch64-android-linux-gnu
Version: 102.20.1.1
CPU implementer	: 0x41
CPU architecture: 8
BogoMIPS	: 26.00
CPU variant	: 0x4
CPU part	: 0xd0b
CPU revision	: 0
Number of processors: 8
CPU current frequency: 2000 MHz
Available memory: 3.6 GB
Using ASIMD (NEON) SIMD optimizations.

---

> Is this bug known?

no, it's not. "Signal 35" indicates the app has been killed by the OS for some reason. Perhaps, out of memory killer?

RAM optimizer, I added an exception for BOINC, I reduced the number of tasks in progress, we'll see if it helps.

---

Under "you may already know, but I'm suggesting anyway...":
I looked at your devices connected, and attached to Asteroids. The Androids each report 8 CPUs/cores. BOINC works better (on Android) using 50% or less (regardless of project), so at most 4 CPUs/cores. (It has to do with switching tasks in and out of the 4 cores it's actually allowed to use by the OS.)

---

Does the new app not like older phones? My old Samsung isn't getting any tasks. It was getting them ok a week or two ago.

the current requirements are 64-bit and arm64-v8 cpu. Most phones from the 2014+ era with Android 5+ should work.

if there's enough interest, we can probably build an app for older architectures, but they can't use new optimizations and their performance is weak. Also, I don't have such an old phone to test the app.

I have a Samsung Galaxy A10 with Android 11. It stopped getting tasks a week or two ago, I'm just told "got 0 new tasks" as though there are none in the queue. My newer phone works fine.

Boinc reports:

ARMv8 Processor rev 4 (v8l) [Impl 0x41 Arch 8 Variant 0x0 Part 0xd03 Rev 4] (8 processors)

I can't find 64 or 32 bit mentioned anywhere.

Unfortunately I'm now down to running two Einstein tasks on it, as it's not got enough RAM for more, and the other projects it can run are all out of work or down.

ok, arm-v8l is a 64bit CPU running in 32bit mode. So we need a 32bit app.

<platform>
  <name>arm-android-linux-gnu</name>
  <user_friendly_name>Android running on ARM armeabi-v7a</user_friendly_name>
</platform>

this may work...

I'll see if I can build it and discuss with Georgi if it's worth the effort...

.
Can I make it run in 64 bit mode? All the apps I use on that phone also run on the newer phone which I assume is 64bit since Asteroids runs ok on it.

Where do I put the platform command? I can't see it in the Boinc manual at https://boinc.berkeley.edu/wiki/Client_configuration

the phone manufacturer has decided to use a 32bit Android, even if the CPU does support 64bit, most likely due to "memory savings".
to run 64bit apps, you need a 64bit OS and I have no idea if it's even possible...

Under "you may already know, but I'm suggesting anyway...":
I looked at your devices connected, and attached to Asteroids. The Androids each report 8 CPUs/cores. BOINC works better (on Android) using 50% or less (regardless of project), so at most 4 CPUs/cores. (It has to do with switching tasks in and out of the 4 cores it's actually allowed to use by the OS.)

Samsung A55 status update,
After a short break, there are updates now,
looks ok, I currently count 4 tasks.
The fan also blows air around the phones

---