BOINC 7.16.5 for Android is still available from some APK sites including APKpure.

I don't want to use not official apk.
I want to use Play Store.

---

BOINC 7.16.5 for Android is still available from some APK sites including APKpure.

I don't want to use not official apk.
I want to use Play Store.

It doesn't fix it anyway.

Besides, LHC and Rosetta have both sorted the problem at their end, your old client should be fine.

---

BOINC 7.16.5 for Android is still available from some APK sites including APKpure.

I don't want to use not official apk.
I want to use Play Store.

Good choice. I only found 7.16.3 and while it has some extra settings to use, it seems to fall out of memory a lot and even when it's running it seems to suspend itself when it's not the foreground task.
Not recommended at all. Having adjusted my Android settings, I'm thinking of downgrading again

---

Good choice. I only found 7.16.3 and while it has some extra settings to use, it seems to fall out of memory a lot and even when it's running it seems to suspend itself when it's not the foreground task.
Not recommended at all. Having adjusted my Android settings, I'm thinking of downgrading again

It's working perfectly on my phone. Only one tiny problem - if you expand a task for details, you cannot unexpand it. But so what, I can just select "tasks" view again and it collapses them.

I'd much rather use the very latest version (Beta or not) of every program.

But you would probably be fine downgrading to the official version now, since LHC and Rosetta (and presumably Numberfields) have fixed it at their end.

---

Good choice. I only found 7.16.3 and while it has some extra settings to use, it seems to fall out of memory a lot and even when it's running it seems to suspend itself when it's not the foreground task.
Not recommended at all. Having adjusted my Android settings, I'm thinking of downgrading again

It's working perfectly on my phone. Only one tiny problem - if you expand a task for details, you cannot unexpand it. But so what, I can just select "tasks" view again and it collapses them.

I'd much rather use the very latest version (Beta or not) of every program.

But you would probably be fine downgrading to the official version now, since LHC and Rosetta (and presumably Numberfields) have fixed it at their end.

The current non Beta version of BOINC for Android in Google Play is 32bit. 7.4.53, released in July 2016
The Beta version available for Google play Beta testers is 64bit compatible, 7.16.3, last updated in October 2019
There is a later Beta version which I am currently using, 7.16.5 that is no longer available from the BOINC website, OR Google Play.
I got the latest Beta from ApkPure. It fixes the bug of collapsing the Tasks list, but it has other bugs, including the inability to remove the app from the Notification bar, even if Suspended.

If you are running a 64bit version of Android on 64bit hardware, then you may be better off using 7.16.3

The current non Beta version of BOINC for Android in Google Play is 32bit. 7.4.53, released in July 2016
The Beta version available for Google play Beta testers is 64bit compatible, 7.16.3, last updated in October 2019
There is a later Beta version which I am currently using, 7.16.5 that is no longer available from the BOINC website, OR Google Play.
I got the latest Beta from ApkPure. It fixes the bug of collapsing the Tasks list, but it has other bugs, including the inability to remove the app from the Notification bar, even if Suspended.

If you are running a 64bit version of Android on 64bit hardware, then you may be better off using 7.16.3

I was also using 7.16.5, I can't remember where I got it from. It prevented me from installing 7.16.3, claiming the apk installer file was corrupt, when what it should have said was "why the hell are you downgrading?" I had to uninstall the "older" version (why did they get the numbers wrong?) to allow the 7.16.3 to go on.

7.16.3 was supposed to fix the SSL problem, but it had no effect for me, I had to wait until Rosetta and LHC fixed it from their end.

I get around the collapsing tasks problem by opening the menu and selecting "tasks" again. They're now all collapsed.

I've no idea what you mean by a "notification bar" - is this a new invention? I'm on Android 7.0.

---

Good choice. I only found 7.16.3 and while it has some extra settings to use, it seems to fall out of memory a lot and even when it's running it seems to suspend itself when it's not the foreground task.
Not recommended at all. Having adjusted my Android settings, I'm thinking of downgrading again

It's working perfectly on my phone. Only one tiny problem - if you expand a task for details, you cannot unexpand it. But so what, I can just select "tasks" view again and it collapses them.

I'd much rather use the very latest version (Beta or not) of every program.

But you would probably be fine downgrading to the official version now, since LHC and Rosetta (and presumably Numberfields) have fixed it at their end.

I don't know if being on Android 9 here makes a difference.
I'll downgrade eventually once I find the time and inclination.
While I was having problems with Rosetta wrt the security cert I switched over to WCG and grabbed a whole load of tasks which I'm now trying to work through, but the constant falling out of memory is taking an age. It's taking 18hrs of wall clock time to get 12hrs of CPU time for WCG tasks that should only be taking 3 or 4hrs to complete.
It's just a mess for everything here

---

Good choice. I only found 7.16.3 and while it has some extra settings to use, it seems to fall out of memory a lot and even when it's running it seems to suspend itself when it's not the foreground task.
Not recommended at all. Having adjusted my Android settings, I'm thinking of downgrading again

It's working perfectly on my phone. Only one tiny problem - if you expand a task for details, you cannot unexpand it. But so what, I can just select "tasks" view again and it collapses them.

I'd much rather use the very latest version (Beta or not) of every program.

But you would probably be fine downgrading to the official version now, since LHC and Rosetta (and presumably Numberfields) have fixed it at their end.

I don't know if being on Android 9 here makes a difference.
I'll downgrade eventually once I find the time and inclination.
While I was having problems with Rosetta wrt the security cert I switched over to WCG and grabbed a whole load of tasks which I'm now trying to work through, but the constant falling out of memory is taking an age. It's taking 18hrs of wall clock time to get 12hrs of CPU time for WCG tasks that should only be taking 3 or 4hrs to complete.
It's just a mess for everything here

feel free to post in the WCG forums to help figure out what's going on. Some projects on the grid vary in WU size.

---

The notification bar or area is part of Android, not part of BOINC
It's the bit at the top of the screen where Battery level, Clock, WiFi indicator, Signal strength, etc. are shown.
BOINC appears there when it is running, but on 7.16.3 you can get rid of the notification when Suspended; On 7.16.5 you can't get rid of the notification without Force Stopping the app.

This is totally off topic, but it might be useful.

There are at least 4 different types of WCG tasks, some are more memory, CPU and storage intensive than others.

It's probably best to only use about 50% of your available Cores, depending on what else you are doing, I would certainly leave at least 1 or 2 unused on an 8 core device for best performance.

The notification bar or area is part of Android, not part of BOINC
It's the bit at the top of the screen where Battery level, Clock, WiFi indicator, Signal strength, etc. are shown.
BOINC appears there when it is running, but on 7.16.3 you can get rid of the notification when Suspended; On 7.16.5 you can't get rid of the notification without Force Stopping the app.

The reason I asked was I didn't know what you were referring to. I only have a phone to make phonecalls, and it happens to also run Boinc. I'm not familiar with the terminology.

Neither of those versions displays it there on mine. I turned off notifications entirely within the Boinc options, as I didn't want it displaying a paragraph thanking me for computing every time I woke up the screen.

---

This is totally off topic, but it might be useful.

There are at least 4 different types of WCG tasks, some are more memory, CPU and storage intensive than others.

It's probably best to only use about 50% of your available Cores, depending on what else you are doing, I would certainly leave at least 1 or 2 unused on an 8 core device for best performance.

I would say the opposite. Even on my PCs with GPUs, I use all available CPU cores. No point in not running the CPU flat out. The GPU tasks seem to manage to squeeze in enough to keep the GPU fully used, if I do two tasks per GPU at once.

I'm interested to know what advantage you think you gain from leaving some unused cores.

---

I'm interested to know what advantage you think you gain from leaving some unused cores.

Depending on the application, some GPU applications require considerable amounts of CPU support.
By using all CPU cores to process CPU work, as well as support a GPU application, the Runtimes for CPU Tasks end up much longer than the CPU time, and the output from the GPU is also significantly reduced. So the amount of work you do per hour is much, much less than it otherwise would be.

Personally i find it better to reserve a CPU core for each GPU application that is running. That way, the CPU tasks Runtime & CPU time are pretty much equal (no wasted time due to CPU resource contention) and the output of the GPUs are maximised. If i run out of GPU work, then the CPU cores that were supporting the GPU applications then start doing CPU work again. More GPU work comes along, the CPU thread goes back to supporting the GPU.
Much better than leaving available cores/threads sitting there idle IMHO.

---

Grant
Darwin NT

Good choice. I only found 7.16.3 and while it has some extra settings to use, it seems to fall out of memory a lot and even when it's running it seems to suspend itself when it's not the foreground task.
Not recommended at all. Having adjusted my Android settings, I'm thinking of downgrading again

It's working perfectly on my phone. Only one tiny problem - if you expand a task for details, you cannot unexpand it. But so what, I can just select "tasks" view again and it collapses them.

I'd much rather use the very latest version (Beta or not) of every program.

But you would probably be fine downgrading to the official version now, since LHC and Rosetta (and presumably Numberfields) have fixed it at their end.

I don't know if being on Android 9 here makes a difference.
I'll downgrade eventually once I find the time and inclination.
While I was having problems with Rosetta wrt the security cert I switched over to WCG and grabbed a whole load of tasks which I'm now trying to work through, but the constant falling out of memory is taking an age. It's taking 18hrs of wall clock time to get 12hrs of CPU time for WCG tasks that should only be taking 3 or 4hrs to complete.
It's just a mess for everything here

Feel free to post in the WCG forums to help figure out what's going on. Some projects on the grid vary in WU size.

I've had issues with wall clockCPU time since I got this Samsung Galaxy S8 a few years ago, where it didn't happen at all with the S6 - both using 7.14.53
With 7.16.3 I have the additional issues described in the 1st line of the 1st quote above.
I'd always run with just 4 of 8 cores, but since Rosetta got so large I reduced that to 3, and now just 2 out of 8 because of the CPU demands (my phone got very sluggish - still does tbh)
The last time I asked (while using 7.14.53) I was told that there were so few settings available in 7.14.53, if there was anything that could be changed to run better, the settings weren't there to change them, so I gave up.
With the best will in the world, I'm not going to join a whole other forum only to be told much the same thing.
I maximise my available RAM and disk space and reduce the CPU demands as much as I can - if it doesn't run I can't do any more than that.
I'm now aborting unstarted and badly running tasks as a more likely way of getting any progress at all

---

I'm interested to know what advantage you think you gain from leaving some unused cores.

Depending on the application, some GPU applications require considerable amounts of CPU support.
By using all CPU cores to process CPU work, as well as support a GPU application, the Runtimes for CPU Tasks end up much longer than the CPU time, and the output from the GPU is also significantly reduced. So the amount of work you do per hour is much, much less than it otherwise would be.

Personally i find it better to reserve a CPU core for each GPU application that is running. That way, the CPU tasks Runtime & CPU time are pretty much equal (no wasted time due to CPU resource contention) and the output of the GPUs are maximised. If i run out of GPU work, then the CPU cores that were supporting the GPU applications then start doing CPU work again. More GPU work comes along, the CPU thread goes back to supporting the GPU.
Much better than leaving available cores/threads sitting there idle IMHO.

I run two GPU tasks per card. Then I look at the GPU usage. If it's dropping below 90%, there's not enough CPU available, so I free one core up. Haven't had to on any of these machines, might be different if I was running Einstein Gravity tasks, which need a lot of CPU, but my machines aren't powerful enough for that because:

1) My GPUs don't have enough RAM.
2) My CPUs are not powerful enough to keep up with the GPUs, even when doing nothing else.

As long as GPU usage >90%, then I'm happy. Might aswell make the CPU be 100% used.

---

I've had issues with wall clockCPU time since I got this Samsung Galaxy S8 a few years ago, where it didn't happen at all with the S6 - both using 7.14.53
With 7.16.3 I have the additional issues described in the 1st line of the 1st quote above.
I'd always run with just 4 of 8 cores, but since Rosetta got so large I reduced that to 3, and now just 2 out of 8 because of the CPU demands (my phone got very sluggish - still does tbh)
The last time I asked (while using 7.14.53) I was told that there were so few settings available in 7.14.53, if there was anything that could be changed to run better, the settings weren't there to change them, so I gave up.
With the best will in the world, I'm not going to join a whole other forum only to be told much the same thing.
I maximise my available RAM and disk space and reduce the CPU demands as much as I can - if it doesn't run I can't do any more than that.
I'm now aborting unstarted and badly running tasks as a more likely way of getting any progress at all

Strange, as I have a budget 4 core VKWorld phone (which seems to have as much RAM and "disk" space as more powerful phones - I get the feeling Samsung are economising....). Running 4 Rosettas at once, I can use the phone for phoning, texting, browsing, watching Youtube, without any slowdown.

You could always tell it to pause Boinc when the phone is in use, or if CPU usage exceeds x%. Plenty ways to make it back off a bit to get out of your way.

---

You could always tell it to pause Boinc when the phone is in use, or if CPU usage exceeds x%. Plenty ways to make it back off a bit to get out of your way.

That's how I've ended up running just 2 cores. Anything more and eg a youtube video will stutter throughout. It's truly dreadful. Messed around with RAM too

---

You could always tell it to pause Boinc when the phone is in use, or if CPU usage exceeds x%. Plenty ways to make it back off a bit to get out of your way.

That's how I've ended up running just 2 cores. Anything more and eg a youtube video will stutter throughout. It's truly dreadful. Messed around with RAM too

Strange your phone does that when my cheaper one does not. Can't you set it to run all cores, but pause when you use the phone? Then most of the time it will do Boinc flat out, but it can't disturb you at all.

---

You could always tell it to pause Boinc when the phone is in use, or if CPU usage exceeds x%. Plenty ways to make it back off a bit to get out of your way.

That's how I've ended up running just 2 cores. Anything more and eg a youtube video will stutter throughout. It's truly dreadful. Messed around with RAM too

Strange your phone does that when my cheaper one does not. Can't you set it to run all cores, but pause when you use the phone? Then most of the time it will do Boinc flat out, but it can't disturb you at all.

With the S6 I was running up to 6 cores and no hold-ups for RAM or anything.
With the S8 I had to drop to 4 cores. With the bigger tasks, 3 or 2.
I also make it the foreground task under this beta version. I've even had to extend the screen timeout to a maximum 10mins
I'm sure I'm repeating myself now. I've done everything. I've even done the next 3 things you're going to ask me about. Everything.

---

You could always tell it to pause Boinc when the phone is in use, or if CPU usage exceeds x%. Plenty ways to make it back off a bit to get out of your way.

That's how I've ended up running just 2 cores. Anything more and eg a youtube video will stutter throughout. It's truly dreadful. Messed around with RAM too

Strange your phone does that when my cheaper one does not. Can't you set it to run all cores, but pause when you use the phone? Then most of the time it will do Boinc flat out, but it can't disturb you at all.

With the S6 I was running up to 6 cores and no hold-ups for RAM or anything.
With the S8 I had to drop to 4 cores. With the bigger tasks, 3 or 2.
I also make it the foreground task under this beta version. I've even had to extend the screen timeout to a maximum 10mins
I'm sure I'm repeating myself now. I've done everything. I've even done the next 3 things you're going to ask me about. Everything.

I guess you didn't consider taking the phone back to the shop (too late now after 3 years). If I buy a newer better version of something and it has trouble doing what my old one managed fine, it's not fit for purpose. I was about to say thanks for warning me, I'll avoid Samsung, but since they're overpriced I would have done anyway :-)

---