Hello, friends.
I am participating in the Astreroids@home project on 2 devices - a laptop and a mobile phone with OS Android 14. When checking the sent calculations, I found that while all the calculations are correct and valid on the laptop, there are many calculations that are incorrect on the Android device (error at counting). I don't know if the problem is with my device, the app or the Android OS. Have you also encountered such a problem? If so, I'd be happy to discuss it together.

Check if you have any RAM optimizers or antivirus programs running. These tools often dislike long-running background tasks and may terminate them to improve battery life and reduce RAM usage.

Hello friends. Even after uninstalling the Bitdefender antivirus program and other programs that are at least somewhat related to RAM, the problem was not solved. The strange thing is that some tasks are completed in order and credit is given, for some, and there are quite a few, but I have a note that there is an error in the calculation and credit is not given. The problem must be somewhere else.

signal 35 indicates the app has been killed which caused a failure. Some mobile optimizers can be quite aggressive in terminating background processes.
what about other projects like Einstein?
try reducing the number of WUs you run simultaneously

if you're familiar with Termux, you could try running the app in offline mode to determine whether it consistently fails on specific WUs or if the failures are random.

Ok, I have determined the cause of the error.

When the system is under load, it first responds by throttling the CPU speed. However, if the load becomes too intense and the device cannot cool itself effectively, the Android system aggressively terminates applications to prevent permanent damage.

The new app is more optimized for ARM CPUs, increasing the strain on the device. While mobile devices can handle short bursts of high load, their passive cooling systems are not designed for prolonged heavy workloads.

The only solution is to reduce the number of active CPUs in BOINC preferences. Modern mobile CPUs are quite powerful and capable of reaching speeds up to 3GHz, but only for short durations. While utilizing all available cores (typically 8) might seem ideal for maximum performance, it is not a good idea. Temperature is the primary limiting factor.

While utilizing all available cores (typically 8) might seem ideal for maximum performance, it is not a good idea.

From what I understand, most Android devices are 'designed' so that half of the cores are largely reserved for system/high-intensity tasks, so that BOINC (as with most apps a user would install) would have effective access to 50% of the cores at most (the non-system ones), even if set to 100%, and will swap tasks to give each one an equal chance at the 'useable' cores...

This would, of course, influence how busy the system gets, and then temps...

---

my Snapdragon 8 Gen 3 has 3 types of cores:
1 x 3.3 GHz ARM Cortex-X4 = the BIG one, fast
3 x 3.2 GHz ARM Cortex-A720 = cores for enhancing MT performance
2 x 2.3 GHz ARM Cortex-A520 = efficiency cores (useless for computing)

Scaling is never perfect, note that all cores share the L3 cache and memory bandwidth. As a result, even without thermal constraints, utilizing all cores could potentially degrade performance.
The same principle applies to Intel's P/E cores. Disabling E-cores is often beneficial, especially for multithreaded applications that share data.