Got some of them now.
2 errored out with SIGSEGV: segmentation violation
one finished ok
2 more in progress.

I know this error from earlier pogs wu's; if you have troubles finding the source of the problem the dev's there may have a good hint.

http://www.gpugrid.net/results.php?hostid=169540

Alexander

Segmentation violation is one of the most default error messages in programming :) It just means that the application messed badly with the memory, like accessing unallocated memory. So I doubt they can help us. But thanks for reporting it.

Segmentation violation is one of the most default error messages in programming :) It just means that the application messed badly with the memory, like accessing unallocated memory. So I doubt they can help us. But thanks for reporting it.

Ah, this is the android equivalent to the windows blue screen!

But another thing I want to point to: @ Einstein the NEON-version of the app reduced the crunching speed from 12 to 8 hrs; might be worth to take a look onto that. Most modern arm devices have NEON support.

NB: only the first 2 wu's failed, all others finished correct until now.

Alexander

Apps still fail:
Parse error on line 1 in file "protein.pdbqt": ATOM syntax incorrect: "9.00 -17.40" is not a valid AutoDock type. Note that AutoDock atom types are case-sensitive.
16:14:07 (30476): called boinc_finish

Alexander

Apps still fail:
Parse error on line 1 in file "protein.pdbqt": ATOM syntax incorrect: "9.00 -17.40" is not a valid AutoDock type. Note that AutoDock atom types are case-sensitive.
04:37:01 (18675): called boinc_finish

Pls take a look to this device:
http://www.gpugrid.net/results.php?hostid=169540