I have aborted my last 2 ones on android tab, one of this:

http://wuprop.boinc-af.org/result.php?resultid=38660168

They never ending. I dont know if the latest boinc client 7.3.0 update caused this issue while the other ones before were successfully. I have reseted my project now and see if this still happening.

I have reinstalled boinc 7.2.41 and now all is fine. The v7.3.0 must have a bug somewhere.

Is that an app for Android?

I'm also seeing this issue with 7.3.0 on Android; I've a task at 99.9% which has run for 20h.

same probleme here with Android version 7.3.0 ... 30h30 running.

I don't see a reason to complain here about first (x.x.0) alpha (x.3.x - 3 is odd number) version of BOINC
Next 'good' version of BOINC will be in the range 7.4.x (or maybe some hotfix in the range 7.2.x)

i.e. if you are not a BOINC beta-tested do not go now over 7.2.41 'Recommended Version' on Android
http://boinc.berkeley.edu/download_all.php

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

When I went to Google apps, Boinc for Android version 7.3.0 was presented to me and had a good review. If it's a Beta version then why was it there and why didn't it say Beta version for testers only?

Yesterday 7.3.5 was uploaded, and is the only version now listed. Again, no indication that this is a Beta.

Anyway, I'm at 94% in a fairly long Asteroids WU (42h), so I will wait until that finishes before messing around installing a replacement app.

The WUProp task eventually progressed from 99.9% to 100%, but its still running!

---

=sticky tape=

I finally gave up on the never ending WU and aborted it. I tried to install the Boinc Andriod version at Berkeley but it wouldn't take so I installed 7.3.5 (yesterdays update). I'm running another WUProp task... http://wuprop.boinc-af.org/results.php?hostid=66264

The Stderr output of the WU I had to abort basically keeps saying 'can't connect to local host'.

Task 38934580

Name wu_v4_1389300887_1019596_0
Workunit 38361733
Created 22 Feb 2014 7:39:12 UTC
Sent 22 Feb 2014 18:22:38 UTC
Received 24 Feb 2014 20:35:38 UTC
Server state Over
Outcome Computation error
Client state Aborted by user
Exit status 203 (0xcb)
Computer ID 66264
Report deadline 4 Mar 2014 18:22:38 UTC
Run time 154,678.11
CPU time 207.52
Validate state Invalid
Credit 0.00
Application version Data collect version 4 v4.05 (nci)
Stderr output

<core_client_version>7.3.5</core_client_version>
<![CDATA[
<message>
aborted by user
</message>
<stderr_txt>
13080): can't connect to localhost12:43:42 (13080): Erreur reception cc_status
12:44:13 (13080): Mise en veille (derniere requete date de moins de 30 secondes
12:44:13 (13080): can't connect to localhost12:44:13 (13080): Erreur reception active_result
12:44:44 (13080): Mise en veille (derniere requete date de moins de 30 secondes
12:44:44 (13080): can't connect to localhost12:44:44 (13080): Erreur reception cc_status
12:45:15 (13080): Mise en veille (derniere requete date de moins de 30 secondes
12:45:15 (13080): can't connect to localhost12:45:15 (13080): Erreur reception active_result
12:45:46 (13080): Mise en veille (derniere requete date de moins de 30 secondes
12:45:46 (13080): can't connect to localhost12:45:46 (13080): Erreur reception cc_status
12:46:17 (13080): Mise en veille (derniere requete date de moins de 30 secondes
12:46:17 (13080): can't connect to localhost12:46:17 (13080): Erreur reception active_result
12:46:48 (13080): Mise en veille (derniere requete date de moins de 30 secondes
12:46:48 (13080): can't connect to localhost12:46:48 (13080): Erreur reception cc_status
12:47:19 (13080): Mise en veille (derniere requete date de moins de 30 secondes
12:47:19 (13080): can't connect to localhost12:47:19 (13080): Erreur reception active_result
12:47:50 (13080): Mise en veille (derniere requete date de moins de 30 secondes
12:47:50 (13080): can't connect to localhost12:47:50 (13080): Erreur reception cc_status
12:49:45 (3478): initialisation
12:49:46 (3478): can't connect to localhost12:49:46 (3478): Erreur reception cc_status
12:49:46 (3478): can't connect to localhost12:49:46 (3478): can't connect to localhost12:49:46 (3478): can't connect to localhost12:49:46 (3478): Erreur reception active_result
12:50:46 (3478): can't connect to localhost12:50:46 (3478): Erreur reception cc_status
12:51:17 (3478): Mise en veille (derniere requete date de moins de 30 secondes
...
14:10:51 (3478): can't connect to localhost14:10:51 (3478): Erreur reception active_result
14:11:19 (5606): initialisation
14:11:19 (5606): can't connect to localhost14:11:19 (5606): Erreur reception cc_status
14:11:20 (5606): can't connect to localhost14:11:20 (5606): can't connect to localhost14:11:20 (5606): can't connect to localhost14:11:20 (5606): Erreur reception active_result
14:12:34 (5729): initialisation
14:12:34 (5729): can't connect to localhost14:12:34 (5729): Erreur reception cc_status
14:12:34 (5729): can't connect to localhost14:12:34 (5729): can't connect to localhost14:12:34 (5729): can't connect to localhost14:12:34 (5729): Erreur reception active_result
14:13:25 (5782): initialisation
14:13:25 (5782): can't connect to localhost14:13:25 (5782): Erreur reception cc_status
14:13:37 (5782): can't connect to localhost14:13:37 (5782): can't connect to localhost14:13:37 (5782): can't connect to localhost14:13:37 (5782): Erreur reception active_result
...
16:32:02 (7232): Mise en veille (derniere requete date de moins de 30 secondes
16:32:02 (7232): can't connect to localhost16:32:02 (7232): Erreur reception active_result
16:32:33 (7232): Mise en veille (derniere requete date de moins de 30 secondes
16:32:33 (7232): can't connect to localhost16:32:33 (7232): Erreur reception cc_status
...
16:50:38 (7232): Mise en veille (derniere requete date de moins de 30 secondes
16:50:38 (7232): can't connect to localhost16:50:38 (7232): Erreur reception active_result
20:29:34 (11958): initialisation
20:29:35 (11958): can't connect to localhost20:29:35 (11958): Erreur reception cc_status
20:29:35 (11958): can't connect to localhost20:29:35 (11958): can't connect to localhost20:29:35 (11958): can't connect to localhost20:29:35 (11958): Erreur reception active_result
20:30:45 (11980): initialisation
20:30:46 (11980): can't connect to localhost20:30:46 (11980): Erreur reception cc_status
20:30:46 (11980): can't connect to localhost20:30:46 (11980): can't connect to localhost20:30:46 (11980): can't connect to localhost20:30:46 (11980): Erreur reception active_result
20:31:10 (11987): initialisation
20:31:10 (11987): can't connect to localhost20:31:10 (11987): Erreur reception cc_status
20:31:46 (11987): can't connect to localhost20:31:46 (11987): can't connect to localhost20:31:46 (11987): can't connect to localhost20:31:46 (11987): Erreur reception active_result

</stderr_txt>
]]>

http://wuprop.boinc-af.org/result.php?resultid=38934580

I continue to use NativeBOINC, as the Berkeley one is still in Beta (they really have not had an official release). I tried the Berkeley one for a couple of days and found it lacking a lot of usability. I can control NativeBOINC just like any of my desktops, where the Berkeley one had limited ability to remote into it and seemed to crash the Android OS every 8 or so hours, making my device reboot.

---

My movie https://vimeo.com/manage/videos/502242

I don't see a reason to complain here about first (x.x.0) alpha (x.3.x - 3 is odd number) version of BOINC
Next 'good' version of BOINC will be in the range 7.4.x (or maybe some hotfix in the range 7.2.x

I don't think that they're using the standard numbering convention for BOINC Android just yet, as they are pushing out more releases due to the number of bugs they're working out.

---

Click here to see My Detailed BOINC Stats

7.3.5 is the same; WUProp tasks go to 99.9% and sit there.
While I'm happy with the performance of Compute Intensive tasks on 7.3.5 I would like something that works with WUProp, so I might try NativeBOINC, if I can...

12:16:39 (4044): Mise en veille (derniere requete date de moins de 30 secondes
12:16:39 (4044): can't connect to localhost12:16:39 (4044): Erreur reception cc_status

When I went to Google apps, Boinc for Android version 7.3.0 was presented to me and had a good review

I think this is the link:
https://play.google.com/store/apps/details?id=edu.berkeley.boinc&hl=en

When I try to [Write a Review] I get:
"You must install this app before submitting a review."

Since I don't have such a device can you (and anyone that have the problem) post some info there?

I did try to post this (Title & text) (you may use it if you like):

BOINC 7.3.x have problems with WUProp@Home

7.3.x have problems with WUProp@Home on Android
7.2.41 work OK
http://wuprop.boinc-af.org/forum_thread.php?id=252
(app "can't connect to localhost" on 7.3.x and is stuck at 99.9%)

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

Here is the Google Group where they discuss the Alpha client and bugs

https://groups.google.com/forum/#!topic/boinc-android-testing/S_SLOEWoh2Y

---

I don't see a reason to complain here about first (x.x.0) alpha (x.3.x - 3 is odd number) version of BOINC
Next 'good' version of BOINC will be in the range 7.4.x (or maybe some hotfix in the range 7.2.x)

i.e. if you are not a BOINC beta-tested do not go now over 7.2.41 'Recommended Version' on Android
http://boinc.berkeley.edu/download_all.php

I think this is the link:
https://play.google.com/store/apps/details?id=edu.berkeley.boinc&hl=en

When I try to [Write a Review] I get:
"You must install this app before submitting a review."

Since I don't have such a device can you (and anyone that have the problem) post some info there?

I did try to post this (Title & text) (you may use it if you like):

BOINC 7.3.x have problems with WUProp@Home

7.3.x have problems with WUProp@Home on Android
7.2.41 work OK
http://wuprop.boinc-af.org/forum_thread.php?id=252
(app "can't connect to localhost" on 7.3.x and is stuck at 99.9%)

https://play.google.com/store/apps/details?id=edu.berkeley.boinc&hl=en
Yes, that's the one.

There is still no mention that this is an Alpha app. It just says,

BOINC
Space Sciences Laboratory, U.C. Berkeley
Education

I posted here because my problem was running WUProp tasks - other tasks ran normally.

"7.2.41 work OK" How do you know that if you 'don't have such a device'?
I can't find any version on play.google.com other than the latest.

There are now over 1400 'reviews' - mostly drivel. It appears that the reviews are not version specific! So many are from several months ago.

Reading through some of the boinc-android-testing thread it's very much a work in progress,
https://groups.google.com/forum/#!topic/boinc-android-testing/S_SLOEWoh2Y
Lots of changes, bugs and development ongoing.

I'm now trying NativeBOINC (which has also seen plenty of development). I like the interface, but it will be 6h before I will know if the WUProp task completes and uploads. At present a Pogs WU and a WUProp WU are progressing...

skgiven, if it matters for any reason, nativeBOINC is based on 7.0.36 as well. I know some projects require certain versions. I just wanted to give the heads up.

As far as getting older version of the Android App, the usually download location for BOINC is also still available. https://boinc.berkeley.edu/download_all.php As you can see, it isn't updated as often as the Play store and you can still modify the link like the others to pull the older versions. However, if you have your device setup to auto update apps, it will still try to pull the latest from the Play store. So make that change first when testing.

---

Thanks for the tips.

WUProp data_collect_v4 version 405 managed to complete and report under NativeBoinc (7.0.36), so I will stick with that version for a while. It's different from using the mainstream Boinc version and has pros and cons but at least it works for here.

I was hoping to find a few new apps to run, but so far I've only added to the same apps I can with a CPU (POGS, BoincSIMAP). After adding Asteroids@home, it looked like its the same as the CPU version (Period Search Application), so I started to use Bam, and got several different apps. I've already reached Blue for 3 of these projects, and pink for another, so I wanted to find others. Unfortunately it looks like they are all the same as what I can get on a CPU, but I might need to go to each project and select the Android only apps if they exist?

It's a fairly basic phone model anyway (1 cpu @1GHz) so even if there were 20 Android only apps available (and I knew what they were and wanted to crunch them) it would take close to 3months to get 20apps over 100h and a lot of micro-management. If I don't find any Android only apps I will at least be able to inch forward a few Green and Red apps...

Thanks for the tips.

WUProp data_collect_v4 version 405 managed to complete and report under NativeBoinc (7.0.36), so I will stick with that version for a while. It's different from using the mainstream Boinc version and has pros and cons but at least it works for here.

I was hoping to find a few new apps to run, but so far I've only added to the same apps I can with a CPU (POGS, BoincSIMAP). After adding Asteroids@home, it looked like its the same as the CPU version (Period Search Application), so I started to use Bam, and got several different apps. I've already reached Blue for 3 of these projects, and pink for another, so I wanted to find others. Unfortunately it looks like they are all the same as what I can get on a CPU, but I might need to go to each project and select the Android only apps if they exist?

It's a fairly basic phone model anyway (1 cpu @1GHz) so even if there were 20 Android only apps available (and I knew what they were and wanted to crunch them) it would take close to 3months to get 20apps over 100h and a lot of micro-management. If I don't find any Android only apps I will at least be able to inch forward a few Green and Red apps...

Let me know if you find any. From what I have seen, they all get tallied the same as x86/x64 apps. I'm assuming PPC apps do the same, but I don't have one to test with.

---

"7.2.41 work OK" How do you know that if you 'don't have such a device'?

See the second post in this thread:
"I have reinstalled boinc 7.2.41 and now all is fine. The v7.3.0 must have a bug somewhere"

And I think everybody of you (posting about the problem in this thread) started noticing it after 'update' of BOINC to 7.3.0

Date of the file boinc_7.3.0.apk is 04-Feb-2014 (probably takes some time for that to reach play.google.com and be pushed to users)
First post here is from 11 Feb 2014 (How long did it take for you to see there is a problem between BOINC 7.3.0 and WUProp@Home?)


There are two changes that say 'Communication' which may be the reason for the WUProp@Home problem (app say "can't connect to localhost")

New to v7.3.5:
- Communication between GUI and BOINC client now uses local pipes
instead of TCP, increasing security.
- Communication that contains email address uses HTTPS if possible,
to avoid sending email address in cleartext.


Even Eric Korpela (SETI@home admin) complains there is a problem (crashes) for BOINC 7.3.5 on his device:
https://groups.google.com/forum/#!msg/boinc-android-testing/S_SLOEWoh2Y/q6b3KfCCqAkJ

I can't find any version on play.google.com other than the latest.

I'm not familiar with play.google.com but All BOINC Versions are here:
http://boinc.berkeley.edu/dl/?C=M;O=A

Ctrl+F for .apk to find them (for Android), e.g.:
boinc_7.2.39.apk
boinc_7.2.41.apk (the last of 7.2.x series)
boinc_7.3.0.apk
boinc_7.3.3.apk
boinc_7.3.4.apk
boinc_7.3.5.apk

Direct links look like this:
http://boinc.berkeley.edu/dl/boinc_7.2.41.apk
http://boinc.berkeley.edu/dl/boinc_7.3.5.apk


And I have no idea how to get and install such files on a phone ...

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)

And I have no idea how to get and install such files on a phone ...

You just navigate to the website in a browser like you linked above and click on the appropriate version to download or type in the direct download to the linked file. When the download completes you run the apk file by opening it like any other download. It then installs like pretty much every other app. Phones and tablets are virtually the same procedure.

Otherwise, you use the Play store method...

---

I published a new test application for android.
I don't have any android device, so I can't test this app.
The WU should run for five minutes.

---

I don't have any android device, so I can't test this app.

You may try this (I still didn't use/test it):

BlueStacks - Your favorite mobile apps on PC, MAC
http://www.bluestacks.com/

(seems it is Android Emulator or VM with Android)

From this post BOINC runs on it. If your app will run you have to say.
http://setiathome.berkeley.edu/forum_thread.php?id=74193&postid=1481714#1481714

---

- ALF - "Find out what you don't do well ..... then don't do it!" :)