This version should have slightly lower memory usage. Several versions have been released with different compile options to see if I can figure out what works best. If you get versions that fail, please continue to request work. Eventually the failing versions stop being sent to you.

---

I've already deprecated one app_version because the server feature that was supposed to limit its distribution to only hosts that could run no other version failed. If I get time to find the problem and fix it, I may re-enable that app version.

---

I have created a beta account. How do I register to download the Android beta version of seti@home?

Just download Boinc or better nativeboinc on your android device.
Add the project by typing the project url http://setiweb.ssl.berkeley.edu/beta.

---

With each crime and every kindness we birth our future.

Thanks. Found Boinc.

Thanks. Found Boinc.

Hopefully you did it via the Google Play app store, that means it'll be the current release, and that it'll be updated as new versions come out.

Claggy

This version should have slightly lower memory usage. Several versions have been released with different compile options to see if I can figure out what works best. If you get versions that fail, please continue to request work. Eventually the failing versions stop being sent to you.

Done that, all the versions on my HTC One S fail now at Zero seconds with SIGILL: illegal instruction (as opposed to just the armv6 ones before, while the the armv7 got SIGSEGV: segmentation violation before)

What SDK version are you building the apps with? My HTC One S has SDK:16 ABI: armeabi-v7a, while the Nexus 7 has SDK:18 ABI: armeabi-v7a, could there be an instruction that isn't supported in the SDK:16 ABI?

Edit: Do you have access to the Model column for all our devices?

Claggy

@Claggy
Where did you find this info? For example "About phone" on my Galaxy mini says:
Android version: 2.3.5
Firmware version: S5570XXKS1
Kernel version: 2.6.35.7-perf-CL561921
se.infra@SEI-30 #1
Build number: GINGERBREAD.XXKS1

How to extract info about SDK supported ?

How to extract info about SDK supported ?

It's shown on the all hosts page (Your computers page), as long as you're logged on, and are looking at your own hosts:

Your computers

It's also shown third line down on the host details page. (But I expect you're got to be running Boinc 7.2.x)

Claggy

How to extract info about SDK supported ?

It's shown on the all hosts page (Your computers page), as long as you're logged on, and are looking at your own hosts:

Your computers

It's also shown third line down on the host details page. (But I expect you're got to be running Boinc 7.2.x)

Claggy

On all hosts page:

ARM
ARMv7 Processor rev 0 (v7l) @1400MHz
(2 процессоров)

Android
2.6.32.48-cyanogenmod

and for Galaxy mini:

ARM
ARMv6-compatible processor rev 5 (v6l) @600MHz
(1 процессоров)

Android
2.6.35.7-perf-CL561921

I'm afraid, just the same info as in "About phone" fields in OS settings...


EDIT: BTW, 1400MHz for G-tab is definitely lie. 1000MHz max and at least for one it set as low as 912MHz. So, 1400MHz is taken from the air.

(But I expect you're got to be running Boinc 7.2.x)

Claggy

If it's possible to install stock BONC side by side with NativeBOINC I'll give it a try.

(But I expect you're got to be running Boinc 7.2.x)

Claggy

If it's possible to install stock BONC side by side with NativeBOINC I'll give it a try.

It should be, my Nexus 7 still has Native Boinc installed, but set not to start automatically.

Claggy

Is there a main thread to look for Q&A on issues with the Android version of SETI @ Home?

I've been having a problem getting a new task this morning: I keep getting "computation error" when it attempts to download or run the new task.

If there are server issues, maybe "STATUS" can be modified to show the status on the other end as well?

Thanks much!

Yes, it's doable.
I shutted down NativeBOINC's client and continued with stock BOINc from Google Play.
Here is new host with stock BOINC:
http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=65966

First of all, new field in "all hosts" table was created and filled with info:

Model: malata GTablet - SDK:10 ABI: armeabi-v7a

This info missed from NativeBOINC output.
Also, this info available from hosts's details: Product name malata GTablet - SDK:10 ABI: armeabi-v7a

It's good indeed.

And now bad side:
1) Host name: localhost. It's untrue, this host has own name and NativeBOINC displays very that name correctly. For this particular host it's smb_a1002, not "localhost". I think this inability of stock BOINC to pickup right host name leads to issues with similar devices sharing same IP. NativeBOINC has no problems with that.

2) Found "Suspend" but can't find "suspend network". How so ? Again, NativeBOINC (just as BOINc for Windows) has full set of corresponding controls, it allows to suspend network communications leaving device's WiFi enabled for other needs.

3) Stock BOINC shows only generic app name, in our case SETI@home v7. Not plan class or app version. Very inconvenient! We have different app versions, different plan classes... Now all this info missed on device, need to refer web pages after task reported. For example, 2 tasks were downloaded, 1 already crashed and I have no idea what app was used for crashed task! It's very big minus for stock BOINC.

4) there is option for battery temp; there is option for "android debug output". And where battery temp reading in Android debug output ? Devs consider this feature fully tested already? Hardly so...
(found battery readings in log)
But another 4): few lines in log every second. Is it really required for android-related debugging? Must switch off this debug flag now, it pollutes whole log.


So, I'm not very pleased with stock BOINC. Will complete few tasks on it for beta testing sake, but surely will return to NativeBOINC for everyday crunching.

Now back on SETI beta topic:

On Gtab SETI@home v7 v7.10 (armv6-vfp) started to crunch OK, and SETI@home v7 v7.10 (armv7-vfpv3) crashed immediately (3 times already).

<core_client_version>7.2.9</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
SIGILL: illegal instruction

Exiting...

</stderr_txt>
]]>

No other flavours so far. Will install stock BOINC on Samsung mini now (if free space allows).

Back to stock BOINC and it's "android debug" info:

excessively verbose... but completely screwed!
I disabled WiFi: "on WiFi" - yes (and was "yes" before too)
I plugged device: "On AC" - no (and was "no" before too)
Well...

Yes, it's doable.
I shutted down NativeBOINC's client and continued with stock BOINc from Google Play.
Here is new host with stock BOINC:
http://setiweb.ssl.berkeley.edu/beta/show_host_detail.php?hostid=65966

First of all, new field in "all hosts" table was created and filled with info:

Model: malata GTablet - SDK:10 ABI: armeabi-v7a

This info missed from NativeBOINC output.
Also, this info available from hosts's details: Product name malata GTablet - SDK:10 ABI: armeabi-v7a

It's good indeed.

Yep, looking through the changesets shows the minimum SDK for the Official Boinc is SDK 10, not sure if that has any bearing on apps though.

And now bad side:
1) Host name: localhost. It's untrue, this host has own name and NativeBOINC displays very that name correctly. For this particular host it's smb_a1002, not "localhost". I think this inability of stock BOINC to pickup right host name leads to issues with similar devices sharing same IP. NativeBOINC has no problems with that.

That is fixed on later Boinc's, i'm on Boinc 7.2.15, that shows android_55e13fad or android_fd990a4e

2) Found "Suspend" but can't find "suspend network". How so ? Again, NativeBOINC (just as BOINc for Windows) has full set of corresponding controls, it allows to suspend network communications leaving device's WiFi enabled for other needs.

There isn't one sadly.

3) Stock BOINC shows only generic app name, in our case SETI@home v7. Not plan class or app version. Very inconvenient! We have different app versions, different plan classes... Now all this info missed on device, need to refer web pages after task reported. For example, 2 tasks were downloaded, 1 already crashed and I have no idea what app was used for crashed task! It's very big minus for stock BOINC.

Yep, that's annoying.

4) there is option for battery temp; there is option for "android debug output". And where battery temp reading in Android debug output ? Devs consider this feature fully tested already? Hardly so...

I have a feeling that it was in during early testing and has been removed, playing with the value shows my Battery temp is ~38°C at the moment (It suspends on 38°C, runs on 39°C),
It's running two Asteroids Peroid Search tasks at the moment.

So, I'm not very pleased with stock BOINC. Will complete few tasks on it for beta testing sake, but surely will return to NativeBOINC for everyday crunching.

You could join the Google 'BOINC Android Testing' Group and then you'll get the latest client, then provide feedback about what isn't right about it.

Claggy

Well, I'm afraid I just swarm that group - too many bugs for now ;)
One of them - list of enabled debug flags not populated so it's impossible to disable that "android debug" output. Nice, I have no usable log at all now on that device...

Well, I'm afraid I just swarm that group - too many bugs for now ;)
One of them - list of enabled debug flags not populated so it's impossible to disable that "android debug" output. Nice, I have no usable log at all now on that device...

I would join it, it's a bit quiet at the moment. ;)

Claggy

@Claggy
Where did you find this info? For example "About phone" on my Galaxy mini says:
Android version: 2.3.5
Firmware version: S5570XXKS1
Kernel version: 2.6.35.7-perf-CL561921
se.infra@SEI-30 #1
Build number: GINGERBREAD.XXKS1

How to extract info about SDK supported ?

For Info, my HTC One S says:
Android version: 4.1.1
HTC Sense version: 4+
Software version: 3.16.771.6
HTC SDK API level: 4.63
HTC Extension version: HTCExtension_sense45_2
Kernel version: 3.4.10-g8d7cd09
root@abm029 #1
SMP PREEMPT
Baseband version: 1.11.50.05.28_10.27.50.08L
Build number: 3.16.771.6 CL128550 release-keys
Browser version: Webkit/534.30

Claggy