I found an annoying bug, in native Boinc, this bug cause computation error for World community grid project running on a phone that lack of ram.

When the RAM is Full, android stop World community grid application and nativeboinc looks for the file containing the results of the calculation, but it don't find this results file and cause computation error.

Please fix this bug.

2 solution:

Increase the process priority of World community grid apps.
Or suspend computation when RAM is full.

This bug affect Native Boinc and official Boinc client !

Thanx for your future replie :)

Sorry for my english, I do not speak much English...
____________[Administrateur de la BDC] en charge de l'Informatique

I found an annoying bug, in native Boinc, this bug cause computation error for World community grid project running on a phone that lack of ram.

When the RAM is Full, android stop World community grid application and nativeboinc looks for the file containing the results of the calculation, but it don't find this results file and cause computation error.

Please fix this bug.

This is the Setiathome forum, it is neither the World community grid, Boinc or Native Boinc Forum, your best cause of action is to report the problem at each of those and supply some corroborating info.

The HTC ONE has returned 10 tasks in a few minutes, all with "Computation error" :-(

That's one of the reasons we need beta testers, so I can figure out things like this. Hope to have new versions out early next week that, even if they don't fix the problem will at least give me more info on why it's happening.
____________

When the RAM is Full, android stop World community grid application and nativeboinc looks for the file containing the results of the calculation, but it don't find this results file and cause computation error.

There's something projected dependent about this. When SETI@home gets stopped for the same reason, it just restarts. (Sometimes over and over and over again without doing much of anything). So there's something about the way that the WCG app quits that BOINC recognizes as an error. Maybe it is lack of the output file, which is the first thing SETI@home creates.

I'll bring it to the attention of the BOINC developers. You should mention it to the WCG developers.

Congratulations to this idea, unfortunately, appears after the start of the app only STARTING on the screen and over and over again
my smartphone is a motorola razr i ; with intel inside ;-)
Android is 4.1.2

Hmmm. Did you install from one of the app stores, if so, which one? They're supposed to limit it to ARM processors at this point unless your phone/pad has an ARM emulator. (The Intel version hasn't been released yet).
____________

I followed the instructions, created a new account and Seti@Home is running just fine on my Kindle. I am very excited, I was disappointed when I couldn't contribute to the project from my Kindle. This is great!
____________

We're still working on why this is happening. It seems restricted to specific phones that don't like the armv6 version. I'll be releasing new versions this week that may be able to correct the problem. Till then you should do fine with the armv7 version.
____________

I've been running this Beta program for just over 1 week on my Galaxy_N8010, I'm finding on my Samsung Exynos 4412 4 x 1.4Ghz cpus it takes about 70 hours to grind through a work unit. This seems really long to me. Anyone else have benchmarks? Is this normal? Curious.
____________

That's not unusual for portable devices. The FPUs on phones and tablets typically process at 1/10th the speed of a desktop computer of the same clock rate. That's how they get away with using so little power. Imagine trying to run your desktop on your phone's battery. :)
____________

That's not unusual for portable devices. The FPUs on phones and tablets typically process at 1/10th the speed of a desktop computer of the same clock rate.

When seeing the Android beta message, this was the very first thing that popped up in my head - considering the low-power -> low crunch rate of mobile phones, why make an ARM version to begin with? Is crunching on your mobile really going to contribute to the grand scale of SETI and other BOINC projects, or is it just going to drain your battery faster without making much of a difference at all?
Especially considering a single desktop GPU will probably be equivalent to 100 phones or so, if not more :P

Added the project on my Photon Q which has been running Einstein@Home successfully for some time. I previously participated in testing for POGS, which had a huge number of segmentation errors, and which I think was released, but on this phone it errors out frequently, so I've stuck with Einstein.