Posts by JLDun
|
1)
(Message 8853)
Posted 14 Mar 2025 by 
JLDun
Post: I was looking through my task list, and saw several marked invalid, which (while rare) I accept can happen (and not just to me). There's just one that makes me wonder a little bit, though: while the other two were sent out a total of three (and only three), to different setups within each grouping, one was sent out five times in total, to four different types of setups, and the two that validated were matching setup types (Win 10, incidentally), which leads me to the suspicion of something maybe being a little "off" with the task. 250248363 |
|
2)
(Message 8776)
Posted 7 Feb 2025 by
JLDun
Post: 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... |
|
3)
(Message 8591)
Posted 8 Oct 2024 by
JLDun
Post: And again. (Just checked at about 7:05 UTC) |
|
4)
(Message 8587)
Posted 29 Sep 2024 by
JLDun
Post: Just snagged a couple, myself. This is through the Android app release May 8 2024 (and Boinc 8.0.4, though that doesn't really apply, I think). Downloaded some more WUs about two minutes later, and the next set started crunching; maybe a differently generated batch? |
|
5)
(Message 8387)
Posted 15 May 2024 by
JLDun
Post: 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.) |
|
6)
(Message 8365)
Posted 11 May 2024 by
JLDun
Post: 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) |
|
7)
(Message 8364)
Posted 11 May 2024 by
JLDun
Post: <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.) |
|
8)
Posted 23 Apr 2024 by
JLDun
Post: In the stderr, do you see a line mentioning "Error: number of lc points is greater than POINTS_MAX = 1000"? |
|
9)
(Message 8351)
Posted 21 Apr 2024 by
JLDun
Post: I agree. My current oldest listed (valid) tasks are from January 20. That makes three months of tasks.... |
|
10)
(Message 8321)
Posted 27 Mar 2024 by
JLDun
Post: Short answer: It's an older version of the Android app, which for some reason will return the error "Error: Number of lc points is greater than POINTS_MAX = 1000" for certain batches of tasks. (The Mac app did this too; from what I understand it was updated recently.) I've seen talk that a new version of the Android app is being worked on, but I forget where I've seen the post. EDIT: Found a different post mentioning the issue, and a mention of the Android app being updated. |
|
11)
(Message 8260)
Posted 7 Feb 2024 by
JLDun
Post: There was a few hours when I couldn't get any on one of my phones, but I managed to snag a few later. |
|
12)
(Message 8137)
Posted 16 Nov 2023 by
JLDun
Post: Occasionally, for "Period Search Application v102.12 (arm_android_pie) arm-android-linux-gnu", the task will error out in under 3 seconds, and the stderr will report: <core_client_version>7.24.1</core_client_version> <![CDATA[ <message> process exited with code 2 (0x2, -254)</message> <stderr_txt> stackdumps unavailable Error: Number of lc points is greater than POINTS_MAX = 1000 </stderr_txt> ]]> |
|
13)
(Message 8136)
Posted 15 Nov 2023 by
JLDun
Post: Now I'm seeing "0 tasks available". |
|
14)
(Message 7189)
Posted 15 Apr 2021 by
JLDun
Post: I'm doing Einstein at the moment. Rosetta has intermittent work; several days/weeks with, then several without. Yoyo and MooWrapper might, but I know they wouldn't work with Android 9, which is what I'm running... |
|
15)
(Message 6313)
Posted 18 Jun 2019 by
JLDun
Post: I'm not sure how Einstein codes their apps but from something I picked up on the S@H boards: the app(s) may be written in 32-bit mode, and newer Android versions tend to be 64 (to run on newer 64-bit CPUs), and may have 'poor' support for 32-bit apps. (As an aside, there's an announcement somewhere that Google wants most developers - on the Facebook-BOINC-Clash of Clans app level, at least- to automatically have 64-bit apps, due to the availability of those newer CPUs, by August.) |
|
16)
(Message 6273)
Posted 7 May 2019 by
JLDun
Post: First thought(s): 1.) Are you sure there isn't a locally set BOINC setting on that computer, for "Don't use more than XX MB"/"XX %" that's been set kinda strange? 2.) BOINC (or the server) is mis-applying a setting even if it's correct... 3.) Gremlins |
|
17)
(Message 5994)
Posted 24 Oct 2018 by
JLDun
Post: Out of disk space Oct 24, 2018 6:42:07 PM|Asteroids@home|Backing off 00:27:19 on upload of ps_181020_input_156450_1_3_0 Oct 24, 2018 6:42:07 PM|Asteroids@home|Temporarily failed upload of ps_181020_input_156450_1_3_0: transient upload error Oct 24, 2018 6:42:07 PM|Asteroids@home|[error] Error reported by file upload server: Server is out of disk space Oct 24, 2018 6:25:47 PM||Local time is UTC -5 hours |
|
18)
(Message 4633)
Posted 13 Sep 2015 by
JLDun
Post: Mine seems to do between 47 and 54 hours. Results |