if the client downloaded those tasks then our server deems your phone as compatible *and* such a download includes the actual science app, not just the data. I can confirm that for your phone based on our logs.
I can't tell why BOINC itself doesn't schedule that task, however. You may enable detailed logging in its advanced settings, though. That should give you more details about what's going on.
Please note: BOINC for Android (version 7.4.53) is severely outdated unfortunately and there are a number of known issues. We've really hoped to see an earlier update but the BOINC community went for a (more or less) full rewrite which still seems to be quite a bit away from a Play Store release. That said, I think there's a beta app available you could try. YMMV, as always.
I enabled Homogeneous Redundancy for BRP4. There should be no cross-validation between Android and Intel-GPU anymore, which may lead to longer validation times e.g. for ARM-CPUs.
Update: had to disable "Homogeneous redundancy" again. Setting this up properly takes more time than I have currently available. Will follow up, though.
I'm unsure if it's the correct topic but it seems to be appropriate to me.
I recently rejoined Einstein on my Samsung S20 Ultra running Android 11 and all the tasks it got errored : https://einsteinathome.org/fr/task/1051830408 for example.
Is it a known issue? I recall it was also crashing like that with Android 10.
I don't think that's a known issue, but it is now. Thanks, we're going to look into it. Please don't hold your breath, though, reproducing and fixing these kind of errors may take time as they often depend on device-specifics and we only have so many device at our disposal.
Regarding Android 10/11: we do not target specific Android versions with our app, we target hardware architectures. That said, as long as we don't see version-specific needs, we don't really distinguish between Android versions. I can confirm that we have about 2,500 Android 10/11 devices attached to our project and they do return valid results (not all of them of course), so there shouldn't be a general issue. BUT, I do see a lot of failures on Android 11, so that might indeed have broken things to some degree. Again, we do see valid results on Android 11 but the errors far outweigh those. Unfortunately we do not have an Android 11 device for testing, so it's going to be a challenge to tackle that problem, I'm afraid.
Even if I'm a dev I don't think I could help on that side as I'm not a knowledgeable person Android-wise nor BOINC wise for this kind of stuff, but if I can help to test apps or whatever on my device I'll gladly help!
So, we had a closer look and the reported (fdsan) error currently affects Android 11 only. We decided to disable Android 11 until the error is fixed. The good news is that we now know what causes the error, so a fix is hopefully in reach.
We're still analyzing that but my working hypothesis is that it's caused by incorrect file descriptor management that Android 11 doesn't allow anymore (Android 10 just issued a warning). Hopefully we have a new version available by the end of the week.
Hi Martin, if the client
)
Hi Martin,
if the client downloaded those tasks then our server deems your phone as compatible *and* such a download includes the actual science app, not just the data. I can confirm that for your phone based on our logs.
I can't tell why BOINC itself doesn't schedule that task, however. You may enable detailed logging in its advanced settings, though. That should give you more details about what's going on.
Please note: BOINC for Android (version 7.4.53) is severely outdated unfortunately and there are a number of known issues. We've really hoped to see an earlier update but the BOINC community went for a (more or less) full rewrite which still seems to be quite a bit away from a Play Store release. That said, I think there's a beta app available you could try. YMMV, as always.
Oliver
Einstein@Home Project
I enabled Homogeneous
)
I enabled Homogeneous Redundancy for BRP4. There should be no cross-validation between Android and Intel-GPU anymore, which may lead to longer validation times e.g. for ARM-CPUs.
BM
Update: had to disable
)
Update: had to disable "Homogeneous redundancy" again. Setting this up properly takes more time than I have currently available. Will follow up, though.
BM
Hi, I'm unsure if it's
)
Hi,
I'm unsure if it's the correct topic but it seems to be appropriate to me.
I recently rejoined Einstein on my Samsung S20 Ultra running Android 11 and all the tasks it got errored : https://einsteinathome.org/fr/task/1051830408 for example.
Is it a known issue? I recall it was also crashing like that with Android 10.
My Android 9 phone is able to crunch correctly.
Are any updates planned to support Android 10/11?
Hi!I don't think that's a
)
Hi!
I don't think that's a known issue, but it is now. Thanks, we're going to look into it. Please don't hold your breath, though, reproducing and fixing these kind of errors may take time as they often depend on device-specifics and we only have so many device at our disposal.
Regarding Android 10/11: we do not target specific Android versions with our app, we target hardware architectures. That said, as long as we don't see version-specific needs, we don't really distinguish between Android versions. I can confirm that we have about 2,500 Android 10/11 devices attached to our project and they do return valid results (not all of them of course), so there shouldn't be a general issue. BUT, I do see a lot of failures on Android 11, so that might indeed have broken things to some degree. Again, we do see valid results on Android 11 but the errors far outweigh those. Unfortunately we do not have an Android 11 device for testing, so it's going to be a challenge to tackle that problem, I'm afraid.
Cheers,
Oliver
Einstein@Home Project
Hi, thanks for you
)
Hi, thanks for you answer!
If I can help in any way, let me know!
Even if I'm a dev I don't think I could help on that side as I'm not a knowledgeable person Android-wise nor BOINC wise for this kind of stuff, but if I can help to test apps or whatever on my device I'll gladly help!
Thanks for the offer! We'll
)
Thanks for the offer! We'll get back to you as soon as that can be helpful.
Oliver
Einstein@Home Project
So, we had a closer look and
)
So, we had a closer look and the reported (fdsan) error currently affects Android 11 only. We decided to disable Android 11 until the error is fixed. The good news is that we now know what causes the error, so a fix is hopefully in reach.
Cheers,
Oliver
Einstein@Home Project
Oh that's good news! May I
)
Oh that's good news!
May I ask what is causing the error?
We're still analyzing that
)
We're still analyzing that but my working hypothesis is that it's caused by incorrect file descriptor management that Android 11 doesn't allow anymore (Android 10 just issued a warning). Hopefully we have a new version available by the end of the week.
Oliver
Einstein@Home Project