Android app release: feedback thread

Drago75
Drago75
Joined: 19 Sep 20
Posts: 5
Credit: 1,862,375
RAC: 421

The phone is connected to the

The phone is connected to the charger and BOINC settings should be fine since the phone runs Universe or WCG without problems.

Oliver Behnke
Oliver Behnke
Moderator
Administrator
Joined: 4 Sep 07
Posts: 889
Credit: 25,165,240
RAC: 0

Hi! Drago75 wrote: Hi

Hi!

Drago75 wrote:

Hi everyone. I am trying to set up a Galaxy S9 with Android 10 to run Einstein but it doesn't receive any work. In my personal settings I have accepted all projects except the ones that offer GPU support. Did I miss a key setting somewhere or are there just no WU's available?

Your Android 10 device just contacted our server once and it didn't request any work/tasks. Apart from that our backend server reported incorrect preferences for that request.

When you say "accepted all projects", do you really mean "projects", or rather "applications"? Please check your preferences to verify you didn't exclude any relevant applications (here: Binary Radio Pulsar Search (Arecibo)).

Hope this helps,
Oliver

 

Einstein@Home Project

Oliver Behnke
Oliver Behnke
Moderator
Administrator
Joined: 4 Sep 07
Posts: 889
Credit: 25,165,240
RAC: 0

Hm, looks like your

Hm, looks like your application selection is just fine. However, I recommend to disable the different GPU types at the top of the page if you want to opt out of using them. Disabling GPU use via apps isn't a good approach since it prevents new apps to run on your devices (won't be added automatically), unless "Allow non-preferred apps" is also enabled.

Anyway, it looks like your preferences got mangled at some point which also triggers the backend warning I referred to above. I suggest the following:

  1. Remove any local preference in the BOINC manager/app you use (they override web preferences)
  2. Remove (clear) all unused "venues" (and/or here) from the web preferences

If none of that works I can remove your preferences from your account so that you can start from scratch.

Oliver

 

Einstein@Home Project

Drago75
Drago75
Joined: 19 Sep 20
Posts: 5
Credit: 1,862,375
RAC: 421

Hi Oliver. I did as you

Hi Oliver. I did as you suggested. Maybe I was too restrivtive with the cached worked as I had it set at 0.1 days + 0.1 days. Maybe the WU's didn't fit into that time span. My S9 got 4 WU's now and will start processing them soon. Thanks for the help!

Oliver Behnke
Oliver Behnke
Moderator
Administrator
Joined: 4 Sep 07
Posts: 889
Credit: 25,165,240
RAC: 0

Glad it works now. Your

Glad it works now. Your preferences now also look fine :)

Thanks for supporting us!

 

Einstein@Home Project

Richie
Richie
Joined: 7 Mar 14
Posts: 639
Credit: 1,701,200,995
RAC: 62,703

Just a casual

Just a casual observation...

I've let a Nokia 8.1 (Android 11) crunch BRP4 tasks for a few days now.

https://einsteinathome.org/host/12898181

'Binary Radio Pulsar Search (Arecibo) v1.51 (ASIMDPIE_1X)' app variant was given for this machine.

Tasks run without problem but after 100+ tasks it seems that only about one fourth of the completed tasks will be successfully valid.

Not too good of a rate, sadly. Disconnecting that chip for now... but ready to test again in future.

Oliver Behnke
Oliver Behnke
Moderator
Administrator
Joined: 4 Sep 07
Posts: 889
Credit: 25,165,240
RAC: 0

Hi Richie,Richie

Hi Richie,

Richie wrote:

Tasks run without problem but after 100+ tasks it seems that only about one fourth of the completed tasks will be successfully valid.

Thanks for sharing this. You're right, the current figures aren't looking too well but they could be statistically biased because there're not that many hosts total running that particular app version. Tracking this down is non-trivial, unfortunately, since our set of test devices can't possibly cover the whole landscape out there.

We'll keep an eye on it.

Oliver

 

 

Einstein@Home Project

Link
Link
Joined: 15 Mar 20
Posts: 24
Credit: 167,609
RAC: 118

Link wrote:Noticed several

Link wrote:

Noticed several times now, that sometimes the Android results can't validate against Intel GPU.

Examples: WU 478781022, WU 480355887.

Seen also cases, where an Intel GPU "lost" against two Androids, so it's probably not an issue with my device. I also never seen an invalid result if the wingman was an Android device.

Oliver Behnke wrote:

Thanks for the notice. Validation might need some tuning. We'll look into it (will take some time, low prio).

Oliver

How is the progress there? As far as I can tell, the issue still persists.

Two Intel GPUs win against Android: WU 568973044

Two Androids win against Intel GPU: WU 569383484

And if you want, we can make some bets on who will win on those: WU 567612159WU 569824008 and WU 567105606

Sucks a bit to loose at least 1-2 WUs per week (over a day of CPU time in my case) every week. AFAIK BOINC has a feature to send tasks from the same WU only to the same type of device, maybe that would be a simple workaround.

.

Richard Haselgrove
Richard Haselgrove
Joined: 10 Dec 05
Posts: 2,041
Credit: 745,865,427
RAC: 1,192,648

I've been concerned about the

I've been concerned about the validation accuracy of the Intel iGPU apps for some time now (some years, even), and I've posted about some very specific issues concerning compiler opimisation settings.

Bernd Machenschalk picked up on those concerns earlier this week, and my latest position update was a PM from Bernd on Tuesday:

"The BRP search had pretty low priority for us for a while, but we finally have someone activly working on it now, so we're getting back to it. I'll take a look at this issue."

Link
Link
Joined: 15 Mar 20
Posts: 24
Credit: 167,609
RAC: 118

OK, thanks, than they will

OK, thanks, than they will maybe fix it soon.

.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.