So we have some common ground and agree with some things.

But consumers aren't interested in what you are, and neither is WCG.
So until then.... dream on. We wont get our dream platform unless it's in Walmart, I want WCG with SunOS 5.10 on an UltraSparc III, which Aisle is that in?

Okey Dokey,
but sometimes I guess members just hope peer pressure can get members to change...

Sorry Aunty ErikaT

Im having the same problem - Sony Netbook running the Asus laptop build of 4.0.4. BOINC will run WCG tasks refuse to recognise the build - but forgive me if I am wrong - wouldnt gimmicking the ID of the x86 Android build to a recognised one solve this problem? Unless I'm missing something fairly fundamental this looks like a recognition issue, in as much as the system is perfectly capable of processing the data sets, but the provider/server doesnt recognise it - add the recognition data and the server should spit the relevant downloads out without issue...

It should also be noted that systems running X86 are very much more likely to be running on desktop grade processors which are in turn more likely to be more valuable in processing terms per core or processor than something you would find in a phone - and therefore proportionally more valuable to what we are trying to achieve here on a per unit basis. Given that this is the case it might be an idea to work on x86 compatibility with high priority...?

Coleslaw: If I may translate your post, and please correct me if I don't have the gist of it:

This is characteristic of the circular reasoning WCG always uses to avoid doing absolutely anything more than they have to. We can't develop a new app because there is no demand, but until we have such an app, there is no way to gauge demand.

Sound familiar?

I have had managers of exactly the same bent... wont let you stock hardware that *will* fail, yet whine like a Morris gearbox when it takes days to order one in specially - and blame everyone else.
The problem is there are a lot of machines that are being produced with android built in - including ARM based netbook style machines - It wouldnt take much for this approach to be progressed to desktop/X86 based hardware as a OEM device. Some of these are actually starting to hit the market belatedly.
There are currently several Android netbooks being offered on Dx.com for example - and at a good price.. albeit they use Cortex Axx processors.
The CLB (Circularly Lazy Bugger) argument is a common one unfortunately - and the people who *do* have the ability to come up with something new are normally the sort of people who cannot cope with this sort of individual approach (such as Steve Jobs).
Imagine - a batch of say 20 BIG.little processor boards built into a SMP system, its more than possible - but needs development time. Hence it never happens.
I still wonder however where the recognition string that is causing the issue is located and whether it would be possible to trick the WCG server to drop data by changing it - after all this is a common trick used with Play Store - there are apps specifically to do it to get round the 'not compatible with this device' issue.

Just tried the Market Helper app to see if that'd make a difference - apparently not :-(