lavaflow,

I figured this question would be raised about versions. There are a few things that have come into thought here on our decision.

1. I have done a check on how many devices are running using Android 4.0.x and older. It came out to be less than 250 devices, if I remember correctly.
2. Since Berkeley is going to only be releasing an application that supports 4.1+ devices, the number of those devices will decrease quickly as they get phased out.

So, to keep the feeder/scheduler happy for a majority of the users, we are going to be changing the minimum requirements for Android to be 4.1+.

As for the signal 11 / error 193 errors, I can not confirm this will help, we will need to see what happens with this Beta test.

Thanks,
-Uplinger

I have 1 running, and 1 waiting to start. I'll keep an eye on them, see what they did tomorrow morning.

On a grand total of 500 WU's, and having just 1 machine for Android, I feel mighty lucky.

Well, got 7.4.41 for pie running off the playstore on 4.4.4 with the dev note 'add support for android 5.0' under 'what's new'. You don't really need a pie agent as the science apps are 'independent'ly executing from the agent i.e. even if you have a none-pie boinc on 4.1+, it will still process the pie versions correctly.

Trawled 4 beta last night and as noted forced them to run concurrent. 2 valid, 2 pending validation. Another 4 fetched just half an hour ago and running simultain. There's a very low participation it seems to be able to catch more so many hours after beta launch.

The charger is not able to keep up with 4 running, one other reason I'm normally running 2 at most. The battery setting which otherwise is set at 90 percent, reduced to 50 so the run will continue while using the device, the sure test to find out if signal 11/193 will come out of it's layer again. Crossing fingers, then hoping oet1 will follow soon in trail of the pr.

Eventually two failed with an unusual code, signal 11