Thank you

Dared fetching 4 which came with the new logo. All _0 or _1 originals, new 7.16.

Two went with signal 11 well into the job, some time apart, but some heavy things were going on at the time. The third went valid and fourth is waiting on wingman. No 195s so far on 7.16. The agent is set to suspend when load is greater than 50%. Lowered it to 40% and will see how the next 4 fare. Rather have the agent pause more often than jobs going out with any of these signal codes. Downside, see some very long checkpoint intervals and thus when stop and resume, see large drop backs in the progress percent. No setting to retain in memory available.

Unrelated, did notice that with arrival of the new compile, the slideshow set had 4 old logo images removed, never understood why there were 4 duplicates, and substituted with one new logo on pitch black background.

Exactly David. This is the same as 7.06

Simaping back

This was a production batch, but 100 of them were sliced small. Which I think masked the problem.


Yes the results were valid in beta.


We are working towards having multiple sized work units in the future. This would mean that slower devices like Android will have less jobs per work unit decreasing the chances of the problem from happening. We are still investigating why it's happening, but out of the machines we have for testing only one of them encounters the problem and it's very infrequent when it does.

Thanks,
-Uplinger

Now displayed in it's new colour scheme... but could someone explain what is the point of continuing to provide the android client for the World Community Grid if my experience is typical?