There was a problem with the first set of android apps due to a problem with how the FFTW library measures time. Any work you got for an android SETI@home v8 before today can be aborted.

I've fixed the bugs and released version 8.01 which should run much better.

---

Running Task 21631352, and tried pausing at about 17:34 (forget exactly hou many seconds, but at least 17m) and 1.2%, then Force-Stopping it out of memory and restarting BOINC. It resumed at 1.2%, 16m47s. Now to see how long to completion.

---

Seems my phone grabbed a couple while I was at work, so far they're progressing and check pointing normally. Thanks Eric :)

---

Mists of dreams drip along the nascent echo, and love no more.

End of line.

Bad news travels faster than the speed of light, good news never leaves the room.

Downloaded on G-Tab both under stock BOINC and under NativeBOINC.
All good so far, passed best functions choice, processing.

Hosts:
http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=65966
http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=64312

---

News about SETI opt app releases: https://twitter.com/Raistmer

My first three armv7-neon tasks have completed and validated on my Samsung S5 mini:

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

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

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

Still get the warning about text relocations

WARNING: linker: ../../projects/setiweb.ssl.berkeley.edu_beta/setiathome_8.01_arm-android-linux-gnu__armv7-neon has text relocations. This is wasting memory and is a security risk. Please fix.
setiathome_v8 8.00 Revision: 3300 arm-linux-androideabi-g++ (GCC) 4.8
libboinc: BOINC 7.7.0

Claggy

Still get the warning about text relocations

WARNING: linker: ../../projects/setiweb.ssl.berkeley.edu_beta/setiathome_8.01_arm-android-linux-gnu__armv7-neon has text relocations. This is wasting memory and is a security risk. Please fix.
setiathome_v8 8.00 Revision: 3300 arm-linux-androideabi-g++ (GCC) 4.8
libboinc: BOINC 7.7.0

Claggy

My Samsung Note 4 has finished one arm6 and one arm7. Both validated. Both still have that warning too.

---

David
signature sent back to alpha testing

There doesn't seem to be much consensus as to how to get rid of that message. Recompiling all the libraries with the PIE flags didn't help. The only relocatable symbols I see are the ones for libc.so. It might just go away if I used a later android SDK, but that tends to break compatibility with older devices, so I've avoided it.

---

From what I've noticed, it tends to show up whenever BOINC/Seti pauses and has to restart/reload into memory. (Example: when I have BOINC running, run some games, go back to BOINC, and it has to 'reload' the Current Task screen.)

---

It might just go away if I used a later android SDK, but that tends to break compatibility with older devices, so I've avoided it.

As in ARM-6 devices, or OS version? (I'm running a KitKat 4.4.2 cellphone, f.y.i.)

---

21631352 finished in 18h39m28s CPU time, 20h01m45s wall-clock time.

---

I'm more worried about pre-Gingerbread devices. I'm pretty sure armv6 is still supported.

The other difference is I would have to build in a virtual machine because they dropped linux EL6 cross compile support starting with ndk-10.

---

How many "Pre-Gingerbread" (2.3.x per Wikipedia) users are there on Beta/Main?

How many "Pre-Gingerbread" (2.3.x per Wikipedia) users are there on Beta/Main?

Need to get my HTC Desire fired up again, seems it's not crunching atm.

Host 65985

All it's v7 work was failing because of:

<core_client_version>7.0.36</core_client_version>
<![CDATA[
<message>
process exited with code 255 (0xff, -1)
</message>
<stderr_txt>
link_image[1995]: failed to link ../../projects/setiweb.ssl.berkeley.edu_beta/setiathome_7.28_arm-android-linux-gnu__armv6-vfp
CANNOT LINK EXECUTABLE

</stderr_txt>
]]>

I understand you can't link files on pre-2.3.x (Having NativeBoinc installed on a SDCard also doesn't work because of this reason)

Claggy

How many "Pre-Gingerbread" (2.3.x per Wikipedia) users are there on Beta/Main?

At least me :) With fleet of 3 G-Tabs and 1 Samsung Galaxy mini :)
oops, they are 2.3, not pre-2.3 ones...

---

News about SETI opt app releases: https://twitter.com/Raistmer

Just turned in an Arm7-Neon-NoPIE (21632535) without the "Text Relocation" message.

(Edit: spell check.)

---

PIE and noPIE - what does it mean?

---

Forget where I found this- while trying to find out if my phone's ARMv7 CPU was 32 or 64 bit- bit I saw somewhere that PIE means "Position Independent Executable". As to what that means....

PIE and noPIE - what does it mean?

New format of executable binary Google made mandatory in new Android and that incompatible with plain Linux on that Android lives.

---

News about SETI opt app releases: https://twitter.com/Raistmer

PIE and noPIE - what does it mean?

New format of executable binary Google made mandatory in new Android and that incompatible with plain Linux on that Android lives.

So why are my phones getting both PIE and noPIE tasks?

---

David
signature sent back to alpha testing

PIE and noPIE - what does it mean?

New format of executable binary Google made mandatory in new Android and that incompatible with plain Linux on that Android lives.

So why are my phones getting both PIE and noPIE tasks?

Maybe your Android version supports both of them? That is, version prior mandatory PIE introduction.

EDIT: this your host should recive only PIE: https://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=74788
while 2 others - both types.
http://stackoverflow.com/questions/30498776/position-independent-executables-and-android-lollipop

One thing to watch out for on Android: building with PIE prior to 4.1 will cause a segmentation fault in /system/bin/linker. PIE was added at Android 4.1, and it crashes lesser versions.

Error: only position independent executables (PIE) are supported
Yes, that's a Lollipop feature. See Security Enhancements in Android 5.0.

In other words:
less than Android 4.1 - only noPIE
Android 4.1 - 5.0 both noPIE and PIE
Android 5+ - only PIE

---

News about SETI opt app releases: https://twitter.com/Raistmer