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.

1 · 2 · 3 · 4 . . . 5 · Next

AuthorMessage
Profile Eric J Korpela
Volunteer moderator
Project administrator
Project developer
Project scientist
Avatar

Send message
Joined: 15 Mar 05
Posts: 1546
Credit: 26,819,612
RAC: 27
United States
Message 48047 - Posted: 14 Nov 2013, 23:24:29 UTC

Two versions have been released thus far. armv6-vfp and armv7-vfpv4

If these work OK, I may add more combinations (although I don't anticipate they will be significantly better than these). I'll also start working on the MIPS and x86 android versions.

Anyone with an x86 android device out there want to let me know if the stock x86 linux version of SETI@home works?
ID: 48047 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 29 May 06
Posts: 1037
Credit: 8,439,427
RAC: 0
United Kingdom
Message 48048 - Posted: 15 Nov 2013, 0:01:31 UTC - in response to Message 48047.  
Last modified: 15 Nov 2013, 0:02:52 UTC

I'll also start working on the MIPS and x86 android versions.

Anyone with an x86 android device out there want to let me know if the stock x86 linux version of SETI@home works?

I think we'll need new clients for MIPS and x86 androids, there were a set of changes for cross compiling for Mips and x86 on the 22nd October, but no new clients have been released for alpha testing since then.

http://boinc.berkeley.edu/gitweb/?p=boinc-v2.git;a=shortlog;pg=3

Claggy
ID: 48048 · Report as offensive
Profile Eric J Korpela
Volunteer moderator
Project administrator
Project developer
Project scientist
Avatar

Send message
Joined: 15 Mar 05
Posts: 1546
Credit: 26,819,612
RAC: 27
United States
Message 48049 - Posted: 15 Nov 2013, 0:04:07 UTC - in response to Message 48048.  

Ah... That would slow things down...
ID: 48049 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 29 May 06
Posts: 1037
Credit: 8,439,427
RAC: 0
United Kingdom
Message 48050 - Posted: 15 Nov 2013, 0:30:24 UTC - in response to Message 48049.  

Ah... That would slow things down...

I've pinged a message to the BOINC Android Testing Google Group asking if they have a time scale for the revised client.

Claggy
ID: 48050 · Report as offensive
Profile Raistmer
Volunteer tester
Avatar

Send message
Joined: 18 Aug 05
Posts: 2423
Credit: 15,878,738
RAC: 0
Russia
Message 48051 - Posted: 15 Nov 2013, 3:07:26 UTC
Last modified: 15 Nov 2013, 3:08:06 UTC

Sorry, but no luck with G-tab again:

<core_client_version>7.0.36</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
stackdumps unavailable
setiathome_v7 7.23 Revision: 2072 arm-linux-androideabi-g++ (GCC) 4.6 20120106 (prerelease)
libboinc: BOINC 7.2.4

Work Unit Info:
...............
WU true angle range is : 0.414600
Optimal function choices:
--------------------------------------------------------
name timing error
--------------------------------------------------------
v_BaseLineSmooth (no other)
neon_GetPowerSpectrum (CPU Caps)
neon_ChirpData (CPU Caps)
v_Transpose4 (default)
neonFoldMain (CPU Caps)
SIGILL: illegal instruction

Exiting...

</stderr_txt>
]]>

And initial Mateuzs' app continues to work just ok....
ID: 48051 · Report as offensive
Profile Eric J Korpela
Volunteer moderator
Project administrator
Project developer
Project scientist
Avatar

Send message
Joined: 15 Mar 05
Posts: 1546
Credit: 26,819,612
RAC: 27
United States
Message 48052 - Posted: 15 Nov 2013, 3:31:35 UTC - in response to Message 48051.  
Last modified: 15 Nov 2013, 3:36:39 UTC

Damn, and no stack trace.

It think that means its likely to be faulting in FFTW, because I've gone to using his setup, VFP and NEON code.

Maybe it's time to add code for autocorrelation with ooura.
ID: 48052 · Report as offensive
Profile Raistmer
Volunteer tester
Avatar

Send message
Joined: 18 Aug 05
Posts: 2423
Credit: 15,878,738
RAC: 0
Russia
Message 48055 - Posted: 15 Nov 2013, 11:43:47 UTC - in response to Message 48052.  
Last modified: 15 Nov 2013, 11:44:46 UTC

add smth like increase verbosity levels as I did in GPU builds.
-v N where app more and more verbose with N increase.
We need that it put string (and flush stderr) each time before (and right after) calling FFTW.
That way we could check your guess.

FFT that Mateuzs used is not an option completely?
ID: 48055 · Report as offensive
Linux? You're kidding me!!
Volunteer tester
Avatar

Send message
Joined: 10 Mar 12
Posts: 1626
Credit: 11,797,955
RAC: 391
Sweden
Message 48060 - Posted: 15 Nov 2013, 17:02:09 UTC
Last modified: 15 Nov 2013, 17:02:29 UTC

v7 v7.23 (armv6-vfp) seems to be running just fine on my Catphone.
10.6 % at 2 Hours 40 Minutes.
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: 48060 · Report as offensive
Profile Raistmer
Volunteer tester
Avatar

Send message
Joined: 18 Aug 05
Posts: 2423
Credit: 15,878,738
RAC: 0
Russia
Message 48062 - Posted: 15 Nov 2013, 18:48:52 UTC - in response to Message 48051.  

And Samsung Galaxy mini failed in same way as G-tab:

<core_client_version>6.12.38</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
stackdumps unavailable
setiathome_v7 7.23 Revision: 2072 arm-linux-androideabi-g++ (GCC) 4.6 20120106 (prerelease)
libboinc: BOINC 7.2.4

Work Unit Info:
...............
WU true angle range is : 0.414637
Optimal function choices:
--------------------------------------------------------
name timing error
--------------------------------------------------------
v_BaseLineSmooth (no other)
neon_GetPowerSpectrum (CPU Caps)
neon_ChirpData (CPU Caps)
v_Transpose4 (default)
neonFoldMain (CPU Caps)
SIGILL: illegal instruction

Exiting...

</stderr_txt>
]]>
ID: 48062 · Report as offensive
Linux? You're kidding me!!
Volunteer tester
Avatar

Send message
Joined: 10 Mar 12
Posts: 1626
Credit: 11,797,955
RAC: 391
Sweden
Message 48071 - Posted: 16 Nov 2013, 17:55:38 UTC
Last modified: 16 Nov 2013, 18:04:53 UTC

First v7 v7.23 (armv6-vfp)finished for me. Validated OK. A number of restarts, but that's me doing other things with the phone, which needed full attention of the CPU.
(Yeah I know, stupid me, using the phone for its original purpose also) LOL

Stderr output
<core_client_version>7.2.15</core_client_version>
<![CDATA[
<stderr_txt>
setiathome_v7 7.23 Revision: 2072 arm-linux-androideabi-g++ (GCC) 4.6 20120106 (prerelease)
libboinc: BOINC 7.2.4

Work Unit Info:
...............
WU true angle range is : 1.105970
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 22.12 percent.
Restarted at 97.92 percent.
Restarted at 98.43 percent.
Restarted at 98.82 percent.
Restarted at 99.41 percent.

Flopcounter: 23139283260826.710938

Spike count: 0
Autocorr count: 0
Pulse count: 0
Triplet count: 0
Gaussian count: 0
17:15:43 (16103): called boinc_finish

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

Send message
Joined: 10 Sep 13
Posts: 1187
Credit: 2,508,034
RAC: 51
United States
Message 48086 - Posted: 18 Nov 2013, 14:05:00 UTC

So far, so good. I've reported three 7.23s and they all validated. I didn't check them for extra anything vs. their wingmates.

David
signature sent back to alpha testing
ID: 48086 · Report as offensive
BetelgeuseFive
Volunteer tester

Send message
Joined: 3 Jun 12
Posts: 64
Credit: 2,430,358
RAC: 15
Netherlands
Message 48089 - Posted: 18 Nov 2013, 17:26:09 UTC - in response to Message 48086.  


No problems here either using 7.23 armv6-vfp on my Asus Memo Pad 7 HD. First task reported and validated. But I had no problems with 7.21 armv6-vfp either.

Tom
ID: 48089 · Report as offensive
Profile David S
Volunteer tester
Avatar

Send message
Joined: 10 Sep 13
Posts: 1187
Credit: 2,508,034
RAC: 51
United States
Message 48108 - Posted: 20 Nov 2013, 14:21:55 UTC - in response to Message 48086.  

So far, so good. I've reported three 7.23s and they all validated. I didn't check them for extra anything vs. their wingmates.

I've now done five v7.23s. Three of them matched all counts against both wingies. One wingy was cancelled by the server and one is still in progress, but in each case I matched the other wingy.

It looks like you may have a winner here, Eric.

David
signature sent back to alpha testing
ID: 48108 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 29 May 06
Posts: 1037
Credit: 8,439,427
RAC: 0
United Kingdom
Message 48114 - Posted: 20 Nov 2013, 21:15:19 UTC - in response to Message 48052.  
Last modified: 20 Nov 2013, 21:15:28 UTC

My HTC One S has only produced inconclusive and invalid results with v7.23, with frequent stalls, suspending and resuming the app gets it going for a bit longer, but it happens again,
Once you look at the stderr.txt you have frequent SIGSEGV: segmentation violation's, I think we still have an api Bug (as well as a app Bug), if we get an SIGSEGV: segmentation violation the Wu should be erroring, and isn't aways:

All tasks for computer 64283

Claggy
ID: 48114 · Report as offensive
Linux? You're kidding me!!
Volunteer tester
Avatar

Send message
Joined: 10 Mar 12
Posts: 1626
Credit: 11,797,955
RAC: 391
Sweden
Message 48115 - Posted: 20 Nov 2013, 21:36:32 UTC
Last modified: 20 Nov 2013, 21:38:50 UTC

I've crunched four, v7 v7.23 (armv6-vfp) so far on my Catphone. The fifth will be finished in a few hours. All of them did run perfectly, validated OK, and no extra triplets.

All tasks for computer 68232
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: 48115 · Report as offensive
Profile Eric J Korpela
Volunteer moderator
Project administrator
Project developer
Project scientist
Avatar

Send message
Joined: 15 Mar 05
Posts: 1546
Credit: 26,819,612
RAC: 27
United States
Message 48116 - Posted: 20 Nov 2013, 23:11:56 UTC - in response to Message 48114.  

I still don't quite understand Android garbage collection...

I think what is happening is that BOINC has either died or already been removed from memory when the SEGV happens. I believe that it's during a read/write from the shared memory segment which no longer exists (probably because it was cleaned up with the BOINC process). In any case, since the shared memory segment doesn't exist, the error condition doesn't reach the BOINC client, which happily restarts SETI@home when BOINC restarts, until some other SEGV happens that the BOINC client does catch.

The more concerning problem is that when your HTC One S does generate a result on the armv6-vfp version, it's a triplet and spike overflow that doesn't validate. You did get some (very few) valid results with it before. Is it getting really warm when SETI@home runs?

I'm going to get a new version out that doesn't use so much memory at start up on low memory machines in hopes that id does somewhat better.

My HTC One S has only produced inconclusive and invalid results with v7.23, with frequent stalls, suspending and resuming the app gets it going for a bit longer, but it happens again,
Once you look at the stderr.txt you have frequent SIGSEGV: segmentation violation's, I think we still have an api Bug (as well as a app Bug), if we get an SIGSEGV: segmentation violation the Wu should be erroring, and isn't aways:

All tasks for computer 64283

Claggy


ID: 48116 · Report as offensive
Profile Eric J Korpela
Volunteer moderator
Project administrator
Project developer
Project scientist
Avatar

Send message
Joined: 15 Mar 05
Posts: 1546
Credit: 26,819,612
RAC: 27
United States
Message 48117 - Posted: 20 Nov 2013, 23:14:22 UTC - in response to Message 48062.  


SIGILL: illegal instruction


I tried and I tried and I tried to get libcorkscrew statically compiled into SETI@home or in a .so that would work on Cyanogen, but I failed. :(

ID: 48117 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 29 May 06
Posts: 1037
Credit: 8,439,427
RAC: 0
United Kingdom
Message 48118 - Posted: 20 Nov 2013, 23:33:14 UTC - in response to Message 48116.  

The more concerning problem is that when your HTC One S does generate a result on the armv6-vfp version, it's a triplet and spike overflow that doesn't validate. You did get some (very few) valid results with it before.

Is it getting really warm when SETI@home runs?

Warm with Setiathome? It hardly even gets Warm, Asteroids is another matter, there it does get Warm, and produces results that validate, it does still get SIGSEGV: segmentation violation's, but no-where as frequent:

All tasks for computer 32848 at Asteroids

Claggy
ID: 48118 · Report as offensive
Profile Eric J Korpela
Volunteer moderator
Project administrator
Project developer
Project scientist
Avatar

Send message
Joined: 15 Mar 05
Posts: 1546
Credit: 26,819,612
RAC: 27
United States
Message 48119 - Posted: 21 Nov 2013, 0:37:38 UTC - in response to Message 48118.  

Do you know what the memory use for asteroids is like?

And I see that asteroids is still being very generous with the credit.
ID: 48119 · Report as offensive
Claggy
Volunteer tester

Send message
Joined: 29 May 06
Posts: 1037
Credit: 8,439,427
RAC: 0
United Kingdom
Message 48120 - Posted: 21 Nov 2013, 1:32:42 UTC - in response to Message 48119.  

Do you know what the memory use for asteroids is like?

And I see that asteroids is still being very generous with the credit.

I have no idea how to get the memory usage for an Asteroids task, Boinc doesn't say, neither are there logging flags that I can see that would tell me,
I do know that Boinc is using 154Mb, up from around 15Mb after start, I understand that is just what the manager uses, if I shut down the client, it still uses the same, killing the Manager process frees that memory.

The other view is that New Credit is very stingy with Credit, see Jason G's posts after his New Credit code walking sessions (I expect he's already emailed you, so you know all about it):

http://setiathome.berkeley.edu/forum_thread.php?id=73306&postid=1444197

Claggy
ID: 48120 · Report as offensive
1 · 2 · 3 · 4 . . . 5 · Next

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


 
©2019 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.