Someone here may know the answer to my problem. I have a bunch of old tablets from when I used to replace broken touch screens on them that I had working on Seti@Home and they were churning along fine, finishing a loading new tasks. Now some of them are exhibiting an error and not loading new work units. This all started around the time of the doubling of the work unit size.

The Samsung Galaxy Tab 2 unitsunits still working are the "samsung SAMSUNG-SGH-I497 - SDK:16 ABI: armeabi-v7a" units and the "samsung GT-P5113 - SDK:17 ABI: armeabi-v7a" units which all have 10.1" screens. Again these are still functioning fine. These are 16Gb units.

In contrast the Galaxy Tab 2 units "samsung SCH-i705 - SDK:16 ABI armeabl-v7 a" as well as the "samsung GT-P3113 - SDK:17 ABI: armeabi-v7a" units all, to a unit, began reporting an error. These are all 7 inch tablets. I can see the error message under the projects option in BOINC for Seti, which states "SETI@home v8 needs 32.00MB more disk space, you currently have 0.00 MB available and it needs 32.00 MB." These are all 8Gb units.

My computers are set to be viewable.

I Checked and adjusted the disk space and ram settings to no avail, and the units themselves, most of which were factory reset and then had BOINC installed, still show 3 or more gigabytes of disk space free and a multiple of 32Mb in ram memory free as well. All have older versions of Android, but it does not seem to matter exactly which 4.x.x is on them and similar versions run on the 10.1 inch variants.

Adjusting the computing preferences does not seem to have any impact on this problem, although, uninstalling BOINC and reinstalling it will cause it to download and execute one or two work units before the error recurs.

I don't know if I am missing something simple or if there was a fundamental change that will prevent these units from participating in the project. I don't know where to go from here. These units are surplus and also not super productive, maybe 60RAC apiece when left crunching continuous, but they do not consume much power and I have a bunch of them. I had planned to keep these and another box of them I have churning out data as a better source of electric heat over the winter than just a space heater.

Another unrelated thing I am curious about is what type system gives the best ratio of calculations per Joule of energy consumed, but that's probably best left to a separate thread.

-Rich

---

Boinc for Android has no one really working on it at the moment, so if it runs it runs, if it doesn't it will be a long time. Eric has not had to time update the Seti app either.

---

... and still I fear, and still I dare not laugh at the Mad Man!

Queen - The Prophet's Song

If it is related to file size doubling it could be file downloads timing out (5 minutes I think)
I don't know if you even have a cc_config ... could try to slow things down a bit ...
<max_file_xfers>1</max_file_xfers>
<max_file_xfers_per_project>1</max_file_xfers_per_project>

Also try cache size 0.01 + 0.01 days to keep minimal tasks on board (that should load a fresh one just before finish current one.

Set Project Preference to 0, so that it only loads a new task after current one is complete.

The applications involved in processing didn't change for us non-Andoidie's - not sure if yours did or need to (pre codeded limits?) Don't think this would have changed your folded size with new apps, but could check the dates on them to see.

A few random ideas to ponder ....

When I get back home I will try and find the file to mod and fiddle with the computing preferences some more. They had been working right for a while and then stopped, so I am thinking something changed, but I don't really understand what is going on with it at this point so I have a bit of learning to do.

---

I can't see how to get to a 'cc config' file to edit it. I ended up reinstalling BOINC on them all and tinkered with the space allocations in the preferences again. I do not expect it to work. One other change that could have effected this is that I did go into the preferences a while back and adjusted them to use 2 processors instead of the default 1 processor. When they stop taking new jobs again I think I will set a couple of them back to using one processor and see if that has any impact on the problem.

---

Given the performance of a Galaxy tablet I would expect 0.1 + 0.1 cache setting to be somewhat limiting - you want to set the first figure to about double the expected run time of a single task - e.g. if you think a task will take 6 hours then set the first figure to 0.5 (half a day). Setting it below the expected run time may prevent any tasks being sent. In this example I would set cache to 0.5 days, plus an additional 0.1 days.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

0.01 + 0.01 days works fine on PCs. I do this if I want to run my cache down if I need to empty it for changes. It loads a new task 14 minutes before completing the current, so keeps chugging right along.

As far as I know, the only way to get to the Boinc subdirectory to create or modify a config.xml is to root the device. Of course, this tends to void any warranty the device may have.

---

... and still I fear, and still I dare not laugh at the Mad Man!

Queen - The Prophet's Song