I haven't had a single error since I started testing ARM android (apart from the buggy 7.22 APP) Now though, I got one (SIGBUS: bus error). It came about after a restart of the app (Charger plugged in again. I do not run on batteries, only when connected to a charger, that's why you'll see all those "Restarted at XX percent" )

I've recently started running on both cores, so maybe that's the reason for the error. The second WU continued to crunch after I connected the charger though. Going back to running on only one core now.

http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=15861186

Stderr output
<core_client_version>7.2.15</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
setiathome_v7 7.24 Revision: 2072 arm-linux-androideabi-g++ (GCC) 4.6 20120106 (prerelease)
libboinc: BOINC 7.3.0

Work Unit Info:
...............
WU true angle range is : 0.444808
Optimal function choices:
--------------------------------------------------------
name timing error
--------------------------------------------------------
v_BaseLineSmooth (no other)
neon_GetPowerSpectrum (CPU Caps)
neon_ChirpData (CPU Caps)
v_Transpose4 (default)
neonFoldMain (CPU Caps)
Restarted at 5.59 percent.
Restarted at 5.59 percent.
Restarted at 9.77 percent.
Restarted at 22.95 percent.
Restarted at 37.94 percent.
SIGBUS: bus error
#00 pc 000cfb08 /data/data/edu.berkeley.boinc/client/projects/setiweb.ssl.berkeley.edu_beta/setiathome_7 (getchr_str+0x8) [0xe5d20000]
#01 pc 000d261c /data/data/edu.berkeley.boinc/client/projects/setiweb.ssl.berkeley.edu_beta/setiathome_7 (vscan+0x19c) [0xe12fff33]

Exiting...

</stderr_txt>
]]>

---

WARNING!! "THIS IS A SIGNATURE", of the "IT MAY CHANGE AT ANY MOMENT" type. It may, or may not be considered insulting, all depending upon HOW SENSITIVE THE VIEWER IS, to certain inputs to/from the nervous system.

In your list of computers I see only one Android device and it reports 473.18 MB of memory. Is this sufficient to run two tasks (in combination with whatever else is running) ? My tablet has 1 Gb of memory (and reports 994.39 MB) but Primegrid crashes (even when running only a single task at a time) when too many other apps are open. I have not yet seen crashes like this on multibeam, but it does not seem to require the same amount of memory as Primegrid.

Tom

I haven't had a single error since I started testing ARM android (apart from the buggy 7.22 APP) Now though, I got one (SIGBUS: bus error). It came about after a restart of the app (Charger plugged in again. I do not run on batteries, only when connected to a charger, that's why you'll see all those "Restarted at XX percent" )

I've recently started running on both cores, so maybe that's the reason for the error. The second WU continued to crunch after I connected the charger though. Going back to running on only one core now.

In your list of computers I see only one Android device and it reports 473.18 MB of memory. Is this sufficient to run two tasks (in combination with whatever else is running) ? My tablet has 1 Gb of memory (and reports 994.39 MB) but Primegrid crashes (even when running only a single task at a time) when too many other apps are open. I have not yet seen crashes like this on multibeam, but it does not seem to require the same amount of memory as Primegrid.

Tom

Well, I have been running a few on both cores, as well a using the browser and other stuff without it crashing, so obviously it is enough with the memory it has. However, it may be on the limit, so as I said, I'm back at one task, one core now.

---

WARNING!! "THIS IS A SIGNATURE", of the "IT MAY CHANGE AT ANY MOMENT" type. It may, or may not be considered insulting, all depending upon HOW SENSITIVE THE VIEWER IS, to certain inputs to/from the nervous system.

Sten-Arne it seems you are running BOIC 7.2.15, the BOINC beta version is 7.2.37 now (added supported for AC powered ARM devices), I am not sure if there are major change to make a difference but at least its worth a try.

In term of speed we will always be limited by the ARM CPU itself of how much it can processes, but in terms of reliability, it is running good on both my Rockchip RK3188 TV stick and MediaTek MT6589T devices.

I ask the question as a matter of curiousity because I love to see Seti@Home officially support Android devices as other projects has already done so.

Sten-Arne it seems you are running BOIC 7.2.15, the BOINC beta version is 7.2.37 now (added supported for AC powered ARM devices), I am not sure if there are major change to make a difference but at least its worth a try.

In term of speed we will always be limited by the ARM CPU itself of how much it can processes, but in terms of reliability, it is running good on both my Rockchip RK3188 TV stick and MediaTek MT6589T devices.

I ask the question as a matter of curiousity because I love to see Seti@Home officially support Android devices as other projects has already done so.

v7.2.15, is the latest available on Gooogle Play. I never install anything from any other sites than Google Play. So v7.2.15 it is, until the Boinc version on Play changes.

Thanks for pointing out though that there is a later Beta version available from other places.

---

WARNING!! "THIS IS A SIGNATURE", of the "IT MAY CHANGE AT ANY MOMENT" type. It may, or may not be considered insulting, all depending upon HOW SENSITIVE THE VIEWER IS, to certain inputs to/from the nervous system.

Sten-Arne it seems you are running BOIC 7.2.15, the BOINC beta version is 7.2.37 now (added supported for AC powered ARM devices), I am not sure if there are major change to make a difference but at least its worth a try.

You only get a version later than 7.2.15 if you're subscribed to the Google BOINC Android Testing Group, or you download it manually.

Claggy

I haven't had a single error since I started testing ARM android (apart from the buggy 7.22 APP) Now though, I got one (SIGBUS: bus error). It came about after a restart of the app (Charger plugged in again. I do not run on batteries, only when connected to a charger, that's why you'll see all those "Restarted at XX percent" )

I've recently started running on both cores, so maybe that's the reason for the error. The second WU continued to crunch after I connected the charger though. Going back to running on only one core now.

I've had a few SIGBUS errors. After I whined about them enough times, Eric said he thought he'd fixed the problem... but he hasn't released a new version since then.

I also run only on power, with 2 of my phone's 4 cores.

(BTW, I hate the Android update from a couple of weeks ago.)

---

David
signature sent back to alpha testing

I don't know if anyone is looking BUT:

my samsung SAMSUNG-SGH-I337 - SDK:18 ABI: armeabi-v7a is failing everything
(running 4 cpu's and running as a normal use phone)

my HTC Desire HD - SDK:10 ABI: armeabi-v7a is successful all the time.
(running as a BOINC only device)

Ed F

---

I don't know if anyone is looking BUT:

my samsung SAMSUNG-SGH-I337 - SDK:18 ABI: armeabi-v7a is failing everything
(running 4 cpu's and running as a normal use phone)

my HTC Desire HD - SDK:10 ABI: armeabi-v7a is successful all the time.
(running as a BOINC only device)

Ed F

Have you tried cutting back the cores you use on the Samsung?

---

David
signature sent back to alpha testing

if it will help the project ..... done! down from 4 to 2.

Ed F

---

BOINC version 7.2.39, is now available at Google Play, without being subscribed to the Google BOINC Android Testing Group.

I just got an update notice on my phone, and updated my BOINC 7.2.15 to version 7.2.39. I do not have my phone set to automatic updates of course. It's my phone, not the property of Google, so I decide what apps I want to update.

---

WARNING!! "THIS IS A SIGNATURE", of the "IT MAY CHANGE AT ANY MOMENT" type. It may, or may not be considered insulting, all depending upon HOW SENSITIVE THE VIEWER IS, to certain inputs to/from the nervous system.

Can someone explain why I keep receiving armv7-vfpv4 tasks instead of armv6-vfp ? The last 10 tasks were all armv7-vfpv4 while armv6-vfp has a higher average processing rate.

Tom


armv6-vfp:

Number of tasks completed 6
Consecutive valid tasks 7
Average processing rate 1.40 GFLOPS

armv7-vfpv4:

Number of tasks completed 14
Consecutive valid tasks 15
Average processing rate 1.26 GFLOPS

Can someone explain why I keep receiving armv7-vfpv4 tasks instead of armv6-vfp ? The last 10 tasks were all armv7-vfpv4 while armv6-vfp has a higher average processing rate.

Not sure if the scheduler takes any notice of the fastest app_version for CPU tasks,
The scheduler sends both x32 and x64 work to my Linux host, the x64 app is fastest, but it still sends x32 work.

Claggy

Can someone explain why I keep receiving armv7-vfpv4 tasks instead of armv6-vfp ? The last 10 tasks were all armv7-vfpv4 while armv6-vfp has a higher average processing rate.

Tom


armv6-vfp:

Number of tasks completed 6
Consecutive valid tasks 7
Average processing rate 1.40 GFLOPS

armv7-vfpv4:

Number of tasks completed 14
Consecutive valid tasks 15
Average processing rate 1.26 GFLOPS

First, the servers ignore average processing rate until there are more than 10 "Number of tasks completed". So for armv6-vfp the speed estimate is being based on the computer's "Measured floating point speed" scaled by an average of how that compares to actual speed across all hosts which have completed tasks with armv6-vfp.

Second, there's a random factor applied to each of the speeds before comparing them. While there are relatively few "Number of tasks completed" that adjustment is fairly large, IOW the intent is to make the host do enough tasks with each feasible application so comparison can eventually be realistic.

                                                                  Joe

I also upgraded to BOINC 7.2.39 and it worked fine until I restarted my tablet. Now the only thing that happens is a message 'BOINC stopped'. Starting BOINC manually results in the same message. Restarting the tablet again does not help. Does anyone else have problems with this new BOINC version ? Any clues as to what I can do to fix this ?

Tom

BOINC version 7.2.39, is now available at Google Play, without being subscribed to the Google BOINC Android Testing Group.

I just got an update notice on my phone, and updated my BOINC 7.2.15 to version 7.2.39. I do not have my phone set to automatic updates of course. It's my phone, not the property of Google, so I decide what apps I want to update.

any chance to get fresh rebuild with Android 2.3 support I tested offline some time ago?

Each time I update the BOINC version, it generates a new name for my Android device. How can I merge results for this device, since the automatic way is based on the device name?
Could it be possible to merge manually with check boxes and choose info of each columns. Not only for Android devices.

---

WU's on first

I'm looking at the Play Store page for the Boinc update. It says

New to v7.2.39: Added support for Ouya and other AC powered devices

(this doesn't affect me)

Added support for x86 and MIPS powered devices

(this doesn't affect me)

Updated translations

(I take it this means GUI languages. Doesn't affect me, since my native language is English.)

So is there any reason for me to update?

---

David
signature sent back to alpha testing

Other than Android annoying you with messages about upgrading, probably not.

---

I'm looking at the Play Store page for the Boinc update. It says

New to v7.2.39: Added support for Ouya and other AC powered devices

(this doesn't affect me)

Added support for x86 and MIPS powered devices

(this doesn't affect me)

Updated translations

(I take it this means GUI languages. Doesn't affect me, since my native language is English.)

So is there any reason for me to update?

There are loads of changes and fixes, the most vital for me was a retry transfers selection as my Nexus 7 doesn't have 24/7 wifi,
haven't seen a thread with the list of changes to give you.

Claggy