Greetings!


I have two android devices - an older Kindle HD and a Samsung S-6 phone.

Way too many WU are downloaded to both.

I wanted to download just a few that can run at night.
Some days, I leave my phone powered off.
Same for the Kindle. I don't want it to overheat.
And I don't like keeping partial or unstarted WU on me devices during the 'off' times.


Its a pain to abort all of the extra WU.

Yes, I set the available kernels to a count on one.
But I still get 3 or 4 times the number of available kernels.

Is there a way to control this?

Not all projects are the same - with respect to getting work.

Thanks in advance, Jay

PS
Will remove projects if WU keep failing.
Is there a way to easily check for success on the BOINC App - rather than having to goto the project website and weed through the devices??

Thanks again,
Jay

If our jobs are consistently failing on your devices, I would suspend all work or detach. Some devices have issues running Rosetta.

Greetings!
... I still get 3 or 4 times the number of available kernels.

Is there a way to control this?

hi Jay

I assume you have discovered, as I seem to have, that web prefs don't propagate to the Android client in the same way as they do on the regular Linux client. I'm still working on that and will post again if I work out how to make that happen.

In the meantime, here is a fudge that world's for me on two different Androids where I have tried it. I've only tried it once on each, like your Android both off mine are munching their very first WUs as I write this. Right now my two core Galaxy Note 1 has only downloaded one WU, despite being enabled for both cores in prefs.

It's a kludge, and will need adjusting when the project upgrades their software. It will also give erratic results if you mix projects. It works by starving BOINC of disk space.

By luck, I have only just discovered the same issue myself and this is my workaround. It's been tried exactly twice so far and worked both times.


Set the parameter for max disk space allowed to Boinc to 0.01 GB or anything less: with the current Rosetta WU nothing will ever be downloaded. If you get work, divide the space you allowed by the number of units you got, and then divide by two to make sure.

Once you have ahem "successfully failed" to get work, check the log file. In the Android client this is currently the last of the options in the main menu, and you access the main menu by tapping the three lines top left.

Look for entries around the time you got the no work message.

There will be one that tells you how much space id's needed for one WU.

Set your limit to (N plus 0.5) times that value and you should get around N units.

It's not perfect: sometimes the project might send out WU with mixed sizes, duo you may get some variation. If at some later time you are getting consistently the wrong number the repeat the slice calibration again.

And out is not likely to work across projects which will each have their own disk space needs. Also Einstein for example sometimes used the same huge data file for several WU, so that the first downloaded WU puff a particular kind would demand more space than follow up work on the same data.

At present, Feb 2016, a setting of 1GB per WU seems to be working for Rosetta on my Androids. The figure I got from from the logs was just over 950MB

Hope that's useful - it's not elegant but it works for me - at least for me

River~~

apologies, I did not explain this bit very well, as I described an earlier plan when I said

66
Set the parameter for max disk space allowed to Boinc to 0.01 GB or anything less: with the current Rosetta WU nothing will ever be downloaded. If you get work, divide the space you allowed by the number of units you got, and then divide by two to make sure.
99

In fact after some experimentation I found what you have to set is the reverse figure to that - you have to play around with the amount of space you want BOINC to leave free for your other apps. So to get more WU you make the number smaller, to get fewer WU you make the number bigger.

again, hope this helps - and if you or anyone else knows a better way to do this, do let us know as I am still experimenting myself.