That might be worth a try but we're cross-compiling our apps using the NDK in our own custom build pipeline. We'll see. For know we focus on getting a working app to you guys since the underlying issue hasn't been a functional or scientific problem up to now. The new app isn't any more worse than the old one, it just doesn't enforce things that Android 11 otherwise would.
Is it possible that my issue has something to do with the recent experiments described here?
Link wrote:
Untill few days ago my Sony Xperia Ray cruched BRP tasks using the NEON version of the app, now it suddenly is only getting tasks for the VFP version, which is slower by factor 2.5: NEON needed about 46,000 seconds per task, VFP needs 115,000 seconds.
No idea what triggered the change and no idea how to fix it, this phone was just crunching here since SETI shut down. I tried resetting the project, but got again the VFP app.
Probably No, that was an unrelated change but your device reports the Android version in an unusual way (looks like a kernel version but lacks the Android release). What Android version are you running? Would you mind upgrading your BOINC client? That should hopefully fix the missing version detail.
This is NativeBOINC, I use it because the original BOINC client can't run on SD card (besides that it lacks few other basic features) and the internal memory of this phone is very small, it's not possible to get more than about 200MB free and Google Play Services use up most of it (up to just few MB left) resulting in BOINC not getting any tasks.
It worked without issues untill few days ago, you can still see some of the NEON tasks in the list, first VFP task is from the 19th January, the same day as Keith Myers reported his issue.
How much disc space do BRP tasks require, i.e. how much free space is necessary to get them? I could try running the original client, but from my experience in the past it's not going to work very long without any issues and without remote access it's also more complicated to check frequently if it's actually working.
This shouldn't be due to free disk space. We "fixed" the Android version parsing, using the official BOINC standard as of BOINC 7.8 (presumably). Your NativeBOINC client just isn't compatible with that anymore, judging from its version number. Can it be updated to match at least BOINC 7.8?
Additionally we'll look into how to restore support such "broken" or old clients.
Now it's not, but if I use the official client it might be as on the internal storage I have usually less than 100MB free, sometimes even less than 20MB depending on what Google Play is doing. Right now for example 53MB free. The official client can't be moved to SD card.
Oliver Behnke wrote:
We "fixed" the Android version parsing, using the official BOINC standard as of BOINC 7.8 (presumably). Your NativeBOINC client just isn't compatible with that anymore, judging from its version number. Can it be updated to match at least BOINC 7.8?
It didn't seem to be broken from here. ;-)
NativeBOINC development stopped few years ago, this is the last version of it. If I need to update, than to the official BOINC, but than I have to find a way to permanently disable all that Google stuff first, as it isn't doing anything useful anyway. I just don't know yet how.
Oliver Behnke wrote:
Additionally we'll look into how to restore support such "broken" or old clients.
This would be great if possible. I see on Google Play Store that version 7.4.53 requires at least Android 4.1, this phone is on 4.0.4 and no updates are available. And that's still not BOINC version 7.8.
EDIT: I can't even find BOINC on that device because of that, on my newer phone I can find it, but that's not in use for BOINC yet. So no update possible. :-(
Yeah I can definitely imagine
)
Yeah I can definitely imagine how it's not sustainable.
Using Android Studio emulators can't help you? Leading to something too different from reality with such scientific apps?
That might be worth a try but
)
That might be worth a try but we're cross-compiling our apps using the NDK in our own custom build pipeline. We'll see. For know we focus on getting a working app to you guys since the underlying issue hasn't been a functional or scientific problem up to now. The new app isn't any more worse than the old one, it just doesn't enforce things that Android 11 otherwise would.
Oliver
Einstein@Home Project
Is it possible that my issue
)
Is it possible that my issue has something to do with the recent experiments described here?
.
Probably, but your device
)
ProbablyNo, that was an unrelated change but your device reports the Android version in an unusual way (looks like a kernel version but lacks the Android release). What Android version are you running? Would you mind upgrading your BOINC client? That should hopefully fix the missing version detail.Oliver
Einstein@Home Project
This is NativeBOINC, I use it
)
This is NativeBOINC, I use it because the original BOINC client can't run on SD card (besides that it lacks few other basic features) and the internal memory of this phone is very small, it's not possible to get more than about 200MB free and Google Play Services use up most of it (up to just few MB left) resulting in BOINC not getting any tasks.
It worked without issues untill few days ago, you can still see some of the NEON tasks in the list, first VFP task is from the 19th January, the same day as Keith Myers reported his issue.
How much disc space do BRP tasks require, i.e. how much free space is necessary to get them? I could try running the original client, but from my experience in the past it's not going to work very long without any issues and without remote access it's also more complicated to check frequently if it's actually working.
.
This shouldn't be due to free
)
This shouldn't be due to free disk space. We "fixed" the Android version parsing, using the official BOINC standard as of BOINC 7.8 (presumably). Your NativeBOINC client just isn't compatible with that anymore, judging from its version number. Can it be updated to match at least BOINC 7.8?
Additionally we'll look into how to restore support such "broken" or old clients.
Oliver
Einstein@Home Project
Oliver Behnke wrote:This
)
Now it's not, but if I use the official client it might be as on the internal storage I have usually less than 100MB free, sometimes even less than 20MB depending on what Google Play is doing. Right now for example 53MB free. The official client can't be moved to SD card.
It didn't seem to be broken from here. ;-)
NativeBOINC development stopped few years ago, this is the last version of it. If I need to update, than to the official BOINC, but than I have to find a way to permanently disable all that Google stuff first, as it isn't doing anything useful anyway. I just don't know yet how.
This would be great if possible. I see on Google Play Store that version 7.4.53 requires at least Android 4.1, this phone is on 4.0.4 and no updates are available. And that's still not BOINC version 7.8.
EDIT: I can't even find BOINC on that device because of that, on my newer phone I can find it, but that's not in use for BOINC yet. So no update possible. :-(
.
Oliver Behnke
)
Ok, should be fixed. Please give it a try :)
Oliver
Einstein@Home Project
Yes, got NEON task
)
Yes, got NEON task now.
Thanks a lot, that was really fast. :)
.
Hi Oliver, So it looks
)
Hi Oliver,
So it looks like they errored at the end...
https://einsteinathome.org/fr/task/1063790841
One is still running because it started later. I'll let it run to see but I'm guessing it will crash too in the end.