I've just sent out v7.08 for Android-armv6

Great! It seems to be working now :)
It checkpoints OK, and it finds no problem so far... but it's gonna take loooong time to finish it (0,5% done @ 2 hours running)
Task 14523568
Thanks!

---

Descarga gratuitamente y comparte mi primer eBook: Amaneceres

I've just sent out v7.08 for Android-armv6. I've rebuilt every library, so hopefully it is fully v6 compatible now. In addition, I've made it friendlier to small memory devices. On devices with less than 512MB, it will use the CPU capabilities to decide which functions to use rather than timing them. (Timing was memory intensive).

An added enhancement... the chosen functions on all platforms will be stored in the state file, so on restart it won't have to benchmark the functions again.

First run of the 7.08 app on my probablamatic HTC One S ended after 0 seconds and a SIGILL: illegal instruction, normally it runs for a little while before erroring.

All tasks for computer 64283

Claggy

No rush, my Droid 1 will still be working on its first result at that point.

Downloaded 7.08 on Samsing Galaxy mini (armv6). Now working. first % done increase passed OK. Will see if it can run till end now.
On G-tab v7.07 downloaded. Should this device recive 7.08 too or those plan classes mutually exclusive?

ARMv7 processors should get both versions for now. It seems likely that there will be little difference in speed, so we will probably just distribute the ARMv6 version on the main project.

---

First run of the 7.08 app on my probablamatic HTC One S ended after 0 seconds and a SIGILL: illegal instruction, normally it runs for a little while before erroring.

I'm not sure what's going on with 64283. It doesn't appear to be significantly different than other hosts that are running successfully. Is it able to run E@H OK? Is there anything unusual about the setup? Did you install to an SD card rather than to internal storage?

---

Did you install to an SD card rather than to internal storage?

for the record, on my Galaxy mini NativeBOINC configured to run from SD card. And app works OK.

Hm... only 0.893% after 4h14min...
For comparison, third party app suspended on 0.299% after 10 mins.
It would be hard to collect enough statistics with such speed. More chances to get comparison on G-tab.

Did you install to an SD card rather than to internal storage?

for the record, on my Galaxy mini NativeBOINC configured to run from SD card. And app works OK.

Some BOINC devices mount their SD card with the "noexec" mount option, which could be a problem. Its not entirely clear to me whether that moves the run directory (/data/data/edu.berkeley.boinc/) to the SD card as well.

---

On my Toshiba Excite Pro (Tergra4) Host ID: 64580 all WU with v7.08 end with:
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
SIGILL: illegal instruction

On my Odroid U2 Host ID: 64579 the WUs run since 4h without problem.
3 x WU with v7.07 (11-14% after 4h)
1 x WU with v7.08 ( 4,8% aufter 4h)

cu JagDoc

That's a full ARMv7 processor, so it shouldn't be finding any illegal instructions, unless they've done something weird with their ARM implementation. I'll look at the RPCs tomorrow to see if anything looks strange.

---

My first task 7.08 (ARMv6) crunched OK :)

Task 14598571

---

Descarga gratuitamente y comparte mi primer eBook: Amaneceres

Now my Toshiba Excite Pro (Tergra4) Host ID: 64580 got some WUs with v7.07 run without problem.

Same with the Nvidia Shield Host ID: 64582 , v7.07 no problem, v7.08 error.

cu JagDoc

Finally found ARM illegal instruction encoding.

My HTC One S is still throwing 'process exited with code 193 (0xc1, -63) SIGILL: illegal instruction' with the v7.09 (armv6) app (released yesterday),

With the 7.07 (armv7a) app it still manages to complete a variable amount of time on the Wu before getting a 'SIGSEGV: segmentation violation', normally this is within a few % of start, but it does sometimes manage to get to ~70% before failing,

The Nexus 7 has no problem with any of the apps so far (It's not run the v7.09 (armv6) app yet)

Claggy

I'm going to see if I can figure out how to get a stack dump for SIGILL.

---

@Eric
Look prev messages from Mateusz. He provided some logs from crashing app. Maybe needed info can be extracted from there?
No crashes on my phone (I'm running under NativeBOINC so "bug-catcher" should be available).

But I'm afraid 7.08 too slow vs custom app. >100 hours and only 20,1% done. And it's even not VLAR...

And another (cosmetic) issue with stock android app:

<stderr_txt>
setiathome_v7 7.00 Revision: 1941 g++ (GCC) 4.4.6 20110731 (Red Hat 4.4.6-3)
libboinc: BOINC 7.2.0

Work Unit Info:
...............
WU true angle range is : 0.447883
Optimal function choices:
--------------------------------------------------------
name timing error
--------------------------------------------------------
v_BaseLineSmooth (no other)
vfp_GetPowerSpectrum 0.002403 0.00000
vfp_ChirpData 0.126063 0.00000
v_Transpose4 0.050126 0.00000
opt VFP folding 0.021716 0.00000

Flopcounter: 36584464432882.351562

Spike count: 0
Autocorr count: 0
Pulse count: 0
Triplet count: 0
Gaussian count: 1
12:14:17 (26557): called boinc_finish

</stderr_txt>

I'm not sure that bolded line is true. Especially "Red Hat".

Yes, that is undoubtedly wrong.

---

@Eric
Look prev messages from Mateusz. He provided some logs from crashing app. Maybe needed info can be extracted from there?
No crashes on my phone (I'm running under NativeBOINC so "bug-catcher" should be available).

Previous messages where?

But I'm afraid 7.08 too slow vs custom app. >100 hours and only 20,1% done. And it's even not VLAR...

I've downloaded Mateusz's source code, and the only significant difference with the stock app is which FFT he is using (FFTS vs FFTW). Unless he's not using the android NDK compiler.

Which host have you been using his app on?

---

Also, looks like 7.08 MUCH slower than 7.07 on armv7 device capable to run both versions. My tablet running >70h already and only near 20%. Usually it takes much less time...

@Eric
Look prev messages from Mateusz. He provided some logs from crashing app. Maybe needed info can be extracted from there?
No crashes on my phone (I'm running under NativeBOINC so "bug-catcher" should be available).

Previous messages where?

Hm... Can't find them. I thought I saw them in very this thread...

Which host have you been using his app on?

On SETI main:

http://setiathome.berkeley.edu/show_host_detail.php?hostid=6958030
http://setiathome.berkeley.edu/show_host_detail.php?hostid=6952254
http://setiathome.berkeley.edu/show_host_detail.php?hostid=6952249

Same hosts on beta (still running stock only):
http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=64312
http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=64311
http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=64393

G-tabs have 7.07 results already, Samsung mini can't complete its first 7.08 task still. But 7.08 takes much longer on G-tabs too and still no single complete result for 7.08.

EDIT: for first link on beta 7.06 took ~52h per task. Now that host running >70h and near 20 % only...

Both tablets just lie plugged and crunch, even WiFi disabled most of time...