Hi! You're running a number of Android devices. Which one is the affected S24? 13108550? That's the only one I find with errors, but that one gets identified as a SM-G996U, which is a Galaxy S21+ (ARMv8). OTOH, the CPU type hints at a Cortex-A520 (ARMv9.2-A) which matches the one used in the S24+ in North America...
If the latter is correct, then despite ARMv9 having optional 32 bit userspace support, the Cortex-A520 only supports 64 bit. Our apps are currently all still 32 bit, so that would explain it. We can try to build and deploy a beta app for 64, but we don't currently have suitable hardware to actually test things properly. YMMV.
Also, it's rather curious that BOINC requests work for your device at all as we don't advertise aarch64-android-linux-gnu as a supported platform. I presume that BOINC just falls back to arm-android-linux-gnu and/or can't distinguish between aarch64-only (>= ARMv9) and aarch64/aarch32-combined (< ARMv9). I opened a bug report with BOINC to look into that as well.
Hey,
I encountered the same issue with the Asteroids app on my S24, and rebuilding it for the aarch64-android-linux-gnu platform using the Android NDK (https://dl.google.com/android/repository/android-ndk-r26c-linux.zip) resolved the problem. I can try building and testing the BRP app next week if you'd like.
I think there's already evidence for this and eventually it's up to us to provide an aarch64 version anyway. So thanks for the offer, but it might be a waste of your time at this point. We're going to provide a build, briefly tested locally (on different hardware), which we then publish as an official beta, as usual. I can't say when this is going to be since we're still understaffed right now, but I hope we'll manage next week.
thanks to Oliver Behnke & Bernd Machenschalk the new aarch64-android app (CPU, beta) has been released. https://einsteinathome.org/cs/task/1675224529
we would appreciate feedback from other users, please give it a try.
the app itself works fine on an anonymous platform, but it's currently not recognized on the user's profile https://einsteinathome.org/cs/host/13173580
while other projects can correctly recognize it Coprocessors: OpenCL GPU QUALCOMM Adreno(TM) 750 (5545MB) driver: 3.00
also, a new option, something like "Use Mobile GPU: yes/no" could be useful to allow/disallow GPU work.
<core_client_version>8.0.4</core_client_version>
<
Hi! You're running a number
)
Hi! You're running a number of Android devices. Which one is the affected S24? 13108550? That's the only one I find with errors, but that one gets identified as a SM-G996U, which is a Galaxy S21+ (ARMv8). OTOH, the CPU type hints at a Cortex-A520 (ARMv9.2-A) which matches the one used in the S24+ in North America...
If the latter is correct, then despite ARMv9 having optional 32 bit userspace support, the Cortex-A520 only supports 64 bit. Our apps are currently all still 32 bit, so that would explain it. We can try to build and deploy a beta app for 64, but we don't currently have suitable hardware to actually test things properly. YMMV.
Also, it's rather curious that BOINC requests work for your device at all as we don't advertise aarch64-android-linux-gnu as a supported platform. I presume that BOINC just falls back to arm-android-linux-gnu and/or can't distinguish between aarch64-only (>= ARMv9) and aarch64/aarch32-combined (< ARMv9). I opened a bug report with BOINC to look into that as well.
Thanks
Einstein@Home Project
Hey, I encountered the same
)
Hey,
I encountered the same issue with the Asteroids app on my S24, and rebuilding it for the aarch64-android-linux-gnu platform using the Android NDK (https://dl.google.com/android/repository/android-ndk-r26c-linux.zip) resolved the problem. I can try building and testing the BRP app next week if you'd like.
I think there's already
)
I think there's already evidence for this and eventually it's up to us to provide an aarch64 version anyway. So thanks for the offer, but it might be a waste of your time at this point. We're going to provide a build, briefly tested locally (on different hardware), which we then publish as an official beta, as usual. I can't say when this is going to be since we're still understaffed right now, but I hope we'll manage next week.
Thanks,
Oliver
Einstein@Home Project
thanks to Oliver Behnke &
)
thanks to Oliver Behnke & Bernd Machenschalk the new aarch64-android app (CPU, beta) has been released.
https://einsteinathome.org/cs/task/1675224529
we would appreciate feedback from other users, please give it a try.
Oliver, when you're back, could you review the GPU app?
Using OpenCL device "QUALCOMM Adreno(TM) 750" by: QUALCOMM
https://einsteinathome.org/cs/task/1674449034
the app itself works fine on an anonymous platform, but it's currently not recognized on the user's profile https://einsteinathome.org/cs/host/13173580
while other projects can correctly recognize it Coprocessors: OpenCL GPU QUALCOMM Adreno(TM) 750 (5545MB) driver: 3.00
also, a new option, something like "Use Mobile GPU: yes/no" could be useful to allow/disallow GPU work.
ahorek's team wrote:we would
)
On this host, it consistently produced instantaneous errors. I had to disable beta applications to revert to v1.51.
Example: https://einsteinathome.org/task/1675236772 (won't be available after the work-unit is dropped from the database)
</stderr_txt>
]]>
Soli Deo Gloria
thanks for your feedback, we
)
thanks for your feedback, we will try to lower the NDK_PLATFORM=29 version for older Android versions to see if it helps (likely next week).
I just started processing on
)
I just started processing on an Android 12 system a few days ago. I let it pick up a couple of the beta tasks and so far they seem to be running okay.
I'm still leaving beta applications off until the issue with older Android is resolved.
Soli Deo Gloria
Wedge009 wrote:I'm still
)
If you move the two Androids to different venues, you can crunch with the beta application just on one of them.
.
I'm well aware of that,
)
I'm well aware of that, thanks.
Soli Deo Gloria
I built and published a new
)
I built and published a new app version (1.73) with an older NDK_PLATFORM (29 as suggested). Beta test. Please give it a try.
BM