On my Nexus 4, job cache is around 24 tasks, but only 12 tasks on (more powerful) Nexus 7. The log says "Not requesting tasks: don't need (job cache is full)". Despite having "download work for 10 days" in project preferences, my Nexus 7 tablet has work for just one day (no internet connection - no work to do).
How do I fix that?

Also, I noticed that Nexus 7 has smaller Gflops rating (application details->average processing rate) compared to Nexus 4 computer, which is ridiculous, and maybe that is the reason behind job cache size difference. How do I update that number? There isn't even a button to remove/delete a computer from my account!

There isn't even a button to remove/delete a computer from my account!

Lots of questions...I will tackle this one...go into your account on the website, then view computers on this account, then select the computer you want to delete and click details, as long as ALL tasks are returned, credited and the database says it's okay the delete this computer option will be highlighted at the bottom of the page. BUT if you have any workunits that have not cleared yet that option will not be available yet.

I apologise for a convoluted explanation :-) I guess my question is, how do I increase job cache size, so that my Nexus 7 is not idling without work to do?

I apologise for a convoluted explanation :-) I guess my question is, how do I increase job cache size, so that my Nexus 7 is not idling without work to do?

I don't know, I thought it was under your account, computing preferences, but it says for all devices EXCEPT and it lists Android Devices. So maybe they are adjusted on the device itself?

On my Nexus 4, job cache is around 24 tasks, but only 12 tasks on (more powerful) Nexus 7. The log says "Not requesting tasks: don't need (job cache is full)".

I tried to find the setting myself too and failed. I guess BOINC devs think it's too advanced for Android users or something. :(

It's true that the normal computing prefs are not used by Android devices, they only listen to locally configured settings and they are quite limited (one can't even setup remote management). NativeBOINC does have more normal configuration options but it's BOINC Client version is getting old.

It's the BOINC Client that says "job cache is full" and it's purely a client decision to fetch or not fetch work. BOINC Server or stats stored on serve side doesn't have much (or maybe anything) to do with the decision.

Also, I noticed that Nexus 7 has smaller Gflops rating (application details->average processing rate) compared to Nexus 4 computer, which is ridiculous, and maybe that is the reason behind job cache size difference. How do I update that number?

These are calculated based on the results received from the device. I don't think BOINC Client gets to even see these values as they are used by the BOINC Server to send work and to calculate granted credits. (Except we don't use that crediting option since it's unreliable but grant fixed amount instead.)

The only way to change these is to.. complete more work units successfully and the stats will change. Slowly but surely, if the new measurements are different. However, the measured GFLOPS might be affected by our apps CPU usage calculation bug where only CPU usage from last run is returned. This affects especially your Nexus 4 device as it pauses and restarts a lot. However, that shouldn't affect the average return time which is also quite different.

Do you still have this problem or did you find a way to fix it?

-w

I still have this problem: my Nexus 7 only downloads at most 11 tasks, and it's barely enough for 12 hours of work. After that, the table is idling, because it doesn't have a permanent internet connection to fetch more work.

I found a workaround that kind of works for my particular scenario.
I'm running dnetc client directly on Nexus 7, without a wrapper. Typically that would be a problem, because the client itself doesn't know current battery temperature and state of charge, and on my non-rooted Nexus 7 it doesn't detect if it's running on battery or is plugged in.
The tablet is a bit overheated, but because it's always plugged in, overall it works much better for me than the moowrap: I'm in control of dnetc.ini file and I'm manually setting work fetch threshold.