Deprecated: Function get_magic_quotes_gpc() is deprecated in /disks/centurion/b/carolyn/b/home/boincadm/projects/beta/html/inc/util.inc on line 663
SETI@home v7 7.23 released for ARM Android

SETI@home v7 7.23 released for ARM Android

Message boards : News : SETI@home v7 7.23 released for ARM Android
Message board moderation

To post messages, you must log in.

Previous · 1 · 2 · 3 · 4 · 5

AuthorMessage
Grumpy Swede
Volunteer tester
Avatar

Send message
Joined: 10 Mar 12
Posts: 1700
Credit: 13,216,373
RAC: 0
Sweden
Message 48972 - Posted: 26 Jan 2014, 10:41:45 UTC
Last modified: 26 Jan 2014, 10:45:58 UTC

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.
ID: 48972 · Report as offensive
BetelgeuseFive
Volunteer tester

Send message
Joined: 3 Jun 12
Posts: 64
Credit: 2,532,468
RAC: 0
Netherlands
Message 48973 - Posted: 26 Jan 2014, 13:33:20 UTC - in response to Message 48972.  

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.
ID: 48973 · Report as offensive
Grumpy Swede
Volunteer tester
Avatar

Send message
Joined: 10 Mar 12
Posts: 1700
Credit: 13,216,373
RAC: 0
Sweden
Message 48974 - Posted: 26 Jan 2014, 16:48:05 UTC - in response to Message 48973.  

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.
ID: 48974 · Report as offensive
Profile Jackyman38
Volunteer tester
Avatar

Send message
Joined: 26 Nov 13
Posts: 32
Credit: 140,363
RAC: 0
United Kingdom
Message 48988 - Posted: 28 Jan 2014, 7:05:44 UTC - in response to Message 48974.  

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.
ID: 48988 · Report as offensive
Grumpy Swede
Volunteer tester
Avatar

Send message
Joined: 10 Mar 12
Posts: 1700
Credit: 13,216,373
RAC: 0
Sweden
Message 49005 - Posted: 28 Jan 2014, 16:51:38 UTC - in response to Message 48988.  

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.
ID: 49005 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 29 May 06
Posts: 1037
Credit: 8,440,339
RAC: 0
United Kingdom
Message 49006 - Posted: 28 Jan 2014, 20:58:48 UTC - in response to Message 48988.  

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
ID: 49006 · Report as offensive
Profile David S
Volunteer tester
Avatar

Send message
Joined: 10 Sep 13
Posts: 1187
Credit: 2,791,507
RAC: 0
United States
Message 49026 - Posted: 29 Jan 2014, 15:31:58 UTC - in response to Message 48972.  

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
ID: 49026 · Report as offensive
EdwardPF
Volunteer tester

Send message
Joined: 8 Sep 05
Posts: 82
Credit: 545,522
RAC: 0
United States
Message 49067 - Posted: 31 Jan 2014, 1:48:40 UTC - in response to Message 49026.  

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
ID: 49067 · Report as offensive
Profile David S
Volunteer tester
Avatar

Send message
Joined: 10 Sep 13
Posts: 1187
Credit: 2,791,507
RAC: 0
United States
Message 49079 - Posted: 31 Jan 2014, 14:20:31 UTC - in response to Message 49067.  

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
ID: 49079 · Report as offensive
EdwardPF
Volunteer tester

Send message
Joined: 8 Sep 05
Posts: 82
Credit: 545,522
RAC: 0
United States
Message 49084 - Posted: 31 Jan 2014, 16:39:35 UTC - in response to Message 49079.  
Last modified: 31 Jan 2014, 16:41:03 UTC

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

Ed F
ID: 49084 · Report as offensive
Grumpy Swede
Volunteer tester
Avatar

Send message
Joined: 10 Mar 12
Posts: 1700
Credit: 13,216,373
RAC: 0
Sweden
Message 49095 - Posted: 1 Feb 2014, 12:03:40 UTC

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.
ID: 49095 · Report as offensive
BetelgeuseFive
Volunteer tester

Send message
Joined: 3 Jun 12
Posts: 64
Credit: 2,532,468
RAC: 0
Netherlands
Message 49096 - Posted: 1 Feb 2014, 14:43:19 UTC

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
ID: 49096 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 29 May 06
Posts: 1037
Credit: 8,440,339
RAC: 0
United Kingdom
Message 49097 - Posted: 1 Feb 2014, 15:15:49 UTC - in response to Message 49096.  

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
ID: 49097 · Report as offensive
Josef W. Segur
Volunteer tester

Send message
Joined: 14 Oct 05
Posts: 1137
Credit: 1,848,733
RAC: 0
United States
Message 49100 - Posted: 2 Feb 2014, 7:21:11 UTC - in response to Message 49096.  

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
ID: 49100 · Report as offensive
BetelgeuseFive
Volunteer tester

Send message
Joined: 3 Jun 12
Posts: 64
Credit: 2,532,468
RAC: 0
Netherlands
Message 49101 - Posted: 2 Feb 2014, 11:20:15 UTC - in response to Message 49095.  

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.
ID: 49101 · Report as offensive
Profile Raistmer
Volunteer tester
Avatar

Send message
Joined: 18 Aug 05
Posts: 2423
Credit: 15,878,738
RAC: 0
Russia
Message 49103 - Posted: 2 Feb 2014, 20:14:31 UTC

any chance to get fresh rebuild with Android 2.3 support I tested offline some time ago?
ID: 49103 · Report as offensive
Profile TomTom
Volunteer tester
Avatar

Send message
Joined: 4 Dec 13
Posts: 98
Credit: 10,262,771
RAC: 0
France
Message 49105 - Posted: 3 Feb 2014, 10:14:43 UTC

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
ID: 49105 · Report as offensive
Profile David S
Volunteer tester
Avatar

Send message
Joined: 10 Sep 13
Posts: 1187
Credit: 2,791,507
RAC: 0
United States
Message 49109 - Posted: 3 Feb 2014, 14:21:00 UTC

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
ID: 49109 · Report as offensive
Profile Eric J Korpela
Volunteer moderator
Project administrator
Project developer
Project scientist
Avatar

Send message
Joined: 15 Mar 05
Posts: 1547
Credit: 27,183,456
RAC: 0
United States
Message 49179 - Posted: 6 Feb 2014, 17:23:00 UTC - in response to Message 49109.  

Other than Android annoying you with messages about upgrading, probably not.
ID: 49179 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 29 May 06
Posts: 1037
Credit: 8,440,339
RAC: 0
United Kingdom
Message 49181 - Posted: 6 Feb 2014, 17:46:50 UTC - in response to Message 49109.  

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
ID: 49181 · Report as offensive
Previous · 1 · 2 · 3 · 4 · 5

Message boards : News : SETI@home v7 7.23 released for ARM Android


 
©2023 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.