Message boards :
Number crunching :
Error while computing on Android
Message board moderation
Author | Message |
---|---|
![]() Send message Joined: 17 May 99 Posts: 2 Credit: 1,825,715 RAC: 32 ![]() ![]() |
I have two android devices: Android samsung SM-T378V - SDK:27 ABI: armeabi-v7a 3.18.14-14676478 (Android 8.1.0) Android motorola Moto E (4) Plus - SDK:25 ABI: armeabi-v7a 3.18.31-perf-g0692b31-00140-g09b2f28 (Android 7.1.1) The Samsung device was working fine until it updated to 8.1.0 since, it gets the Error while computing on nearly every task. (It can get up to 4 "normal" tasks completed within each day. I have reinstalled and still get the same results. The moto device was an older phone, I factory wiped and updated then installed only the boinc app. and it has 0 completed tasks in 6 days every single task gets the error. Is this a Boinc issue?is this a S@H issue? Is it and Android issue? Does anyone really know what time it is? Thank you for your time. |
![]() Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 ![]() |
Read https://setiathome.berkeley.edu/forum_thread.php?id=82842 on that. To answer your question, it's a Seti@Home problem in combination with your 32bit CPUs AND Android 8. Until new science applications are released, this won't be fixable by you. Your only option is to either replace the devices with newer versions, to go back to an older Android version (force a downgrade) or to cease using these devices. |
![]() Send message Joined: 17 May 99 Posts: 2 Credit: 1,825,715 RAC: 32 ![]() ![]() |
Thank you for the reply, I looked, I really did. but searching for android in the forus I just kept getting stuff about android vs Win10 ... Sorry to ask a question that was already answered, but again thank you. |
![]() Send message Joined: 25 Jul 99 Posts: 155 Credit: 16,507,264 RAC: 19 ![]() ![]() |
For a while I ran two old android handsets which crunch slowly when plugeed in for charging, but since they are old and the charging sockets are loose, they didn't work much of the time. Eventually it was more trouble than it was worth, so now only use my partner's handset, but that is very slow even with 8 cores. |
![]() Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 ![]() |
It's slow because Android doesn't use all 8 cores the same way as a PC does. You will find it speeds up things if you set it to use 4 cores only, because now it will run 2 tasks per core on those 4 cores only. Most new devices have two sets of cores, the so-called BIG and LITTLE cores. The BIG cores are only used by Android, the LITTLE cores are what is used by all the rest, BOINC included. Perhaps that a future version of BOINC can make use of the faster BIG cores, but not at this time. So it's better to set BOINC to use half the amount of cores the device has available and then it'll speed up enormously. See my computers for an indication. I only have Android devices running, with both 8 core phones running on 4 cores only. My old Huawei P9 Lite has a RAC of 590.60 all on its own. |
©2025 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.