I'm running Asteroids on a Galaxy Tab, two WUs at a time (one per core)

Yesterday I let the battery run down and both WUs failed.

When I got home I recharged the battery and started another pair of WUs. The tablet, no doubt aided by a
curious kitten, slid behind a cushion and got very warm. The Android app shuts down when the temperature exceeds a threshold and both WUs failed.

All four WUs had the same stderr:

<core_client_version>7.2.9</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
ERROR - signal handler called in timer thread

</stderr_txt>
]]>

Normally tasks run without any issue whatsoever. So i wanted to bring your attention to these two cases in case you can fix them for other users who may be running on batteries way more than me, or have a larger clowder than I do :)

Cheers!

S.

I was getting loads of errored out WU's that ran to completion on Android. Sent the admin a PM, waiting to hear back.

They are just coming back online after being offline for several days for a Server upgrade. That could automatically fix the problems you were having, or it may not.

Android errors were happening way before the shutdown. I had several and pulled my Android off of computing because of it.

I was getting loads of errored out WU's that ran to completion on Android. Sent the admin a PM, waiting to hear back.

I can see, that there is kernel 3.4.10. What version of Android do you have?

I was getting loads of errored out WU's that ran to completion on Android. Sent the admin a PM, waiting to hear back.

I can see, that there is kernel 3.4.10. What version of Android do you have?

I have:
ARMv7 Processor rev 2 (v7l) @1188MHz
Android 3.0.16-gf59f9ce, Android version 4.03
using NativeBoinc 0.4.4.2.3 with BOINC API 7.0.36
Here are the errored units:
http://asteroidsathome.net/boinc/result.php?resultid=27978764
http://asteroidsathome.net/boinc/result.php?resultid=27978762
http://asteroidsathome.net/boinc/result.php?resultid=27919767
http://asteroidsathome.net/boinc/result.php?resultid=27661666

---

Have you tried official BOINC manager for Android? I compiled it using official BOINC API, for NativeBOINC, there is adjusted BOINC API. It was working with earlier version of NativeBOINC but I haven't tried it yet on the new version and this version of Android. Isn't it overclocked, according to the processor frequency?
I can test it later on Android 4.2.2.

Mine was not overclocked. I did not try it on the official BOINC version. Alas that unit is now gone (it didn't die, I just decommissioned it), but I shall be getting a newer unit that I will put the official version on.

I can say these stopped working between 31-DEC and 1-JAN. Any units I downloaded before 1-JAM worked fine.

And was there any update of the NativeBOINC in that time?

No update to NativeBOINC. It has not been updated since the official BOINC version was released.

Unless how you present the date itself is an issue? Other project ran fine.

After reading this thread, I installed nativeboinc on my android (Galaxy 3 S) from the play store and connected to asteroidsathome. There seems to be some real problems with nativeboinc. An asteroid task downloaded and started executing and was checkpointing about every 60 seconds but there was no indication on the status screen of anything going on other than
"suspended until battery is over %90: currently %100"
and "waiting project initialization" on the project page even though the task had been running for many hours.
I tried suspending the project to see if the dialog button would change to "resume" but it didn't and boinc is currently stuck "reading projects" and a full reset failed to fix the problem. The event log shows null pointers when accessing the status page and I will be uninstalling the app as it seems too many problems too soon for my android which has 2 cores and 2gb memory (the sprint version of the IIIs)

follow-up on my post of problems earlier: I uninstalled boinc from Berkeley and put in the "native boinc" and that seems to be working and I have 2 asteroids tasks running. Will see how they turn out. Unfortunately, the boinc I downloaded earlier was the "official" one which seems to be buggy.

Completed my first pair of Android tasks under nativeboinc, both valid. I first tried the original boinc but the manager was too buggy and I had to uninstall.

Shown below is a screen grab of my Galaxy IIIs and a, somewhat, comparable EeePC with an n570 cpu. That win7x32 system is significantly slower. It should finish in about 8 more hours and I will try disabling hyperthread for the next asteroids run which should speed it up. As it is, my Galaxy IIIs Sprint phone is superior to an intel n570 dual core in an Asus netbook.

Instead of disabling Hyper-Threading you may just try to run 2 tasks at a time

To not affect your other computers it's easier to set it locally
Local preferences

On multiprocessor systems, use at most 50 % of the processors

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)