792468934 and others continue to restart.
I've killed

---

The success rate is low for android. Some devices do not like Rosetta and it is likely due to memory issues. I suspect due to heap space limits. If your device has repeated issues with R@h jobs, I would suspend all work.

Hi

What are the memory requirements for android WUs?

thanks

Hi

What are the memory requirements for android WUs?

thanks

1gig. But even if you meet the requirements (https://boinc.bakerlab.org/rah_requirements.php), your device may still have issues with Rosetta and I suspect it may be due to various factors depending on the device which may include but may not be limited to:

1. dynamic memory limits
2. job suspension at the android OS level.

If your device has repeated issues with R@h jobs, I would suspend all work.

1) If you see my post on Ralph's forum, some wus run ok.
2) I have an "old" Galaxy S3, not a top smartphone.

---

Ha! I just checked my hosts and apparently my S5 mini completed a WU during the night while charging.

---

Ha! I just checked my hosts and apparently my S5 mini completed a WU during the night while charging.

It's not a bad phone.
I'm curious about next S7, may be a good crunching machine on Rosetta.
I'm also curious about Rasp Pi2 with Android on Rosy, if it crunchs and how

---

One running on a Samsung S4 as we speak. Hopefully it completes before its deadline, which is again pretty short

---

Things have gone wild. Another two!

With a reasonable completion date of Tuesday too. Things are looking up.

---

I'm crunching android wus in a TV set box, octa core 2 GB RAM, they are going through fairly well in spite the low amount of RAM of the host.

Almost all the erros I have are upload errors for the db_design5 units, around 15-20% of them, no idea why only part of them

upload failure: <file_xfer_error>
<file_name>db_designs5_t6c.1295.7_0001_android_SAVE_ALL_OUT_327271_4214_1_0</file_name>
<error_code>-161 (not found)</error_code>
</file_xfer_error>

The ab_xx_xx__vall units do not have this problem and need less memory

Now i'm crunching regularly on my phone.
It would be interesting to know the total contribution of android to Rosetta.

---

Now i'm crunching regularly on my phone.
It would be interesting to know the total contribution of android to Rosetta.

I would guess you'd need to upgrade the BOINC version on the server. This will never happen tho.

---

I would guess you'd need to upgrade the BOINC version on the server. This will never happen tho.

:-(

---

Actually, it could be done more easily on our end. Although there are a lot of registered devices, the actual contribution so far is quite low relative to the standard platforms. There is around a 10x decrease in throughput when comparing ab initio jobs run on android devices vs standard cpus. And there is about a 50-70% success rate vs 95+%. There have been around 10,000 completed android jobs in the last 24 hours vs 210,000+ as a rough estimate. And the jobs that are currently being sent to android devices are centroid only ab initio and small cyclic peptide jobs which require less memory. So far, android throughput is a very small fraction of our total and limited to protocols that are not as memory intense.

While throughput may be small overall, I'm quite pleased with my own phone's current contribution, however small it is.

---

Yes, I'm a little biased but I think it's quite cool and impressive that Rosetta is modeling proteins and peptides on phones! And it should only get better as processing power and memory improve....

Yes, I'm a little biased but I think it's quite cool and impressive that Rosetta is modeling proteins and peptides on phones! And it should only get better as processing power and memory improve...

My Samsung S4 is a few generations behind now and I share 2 of 4 cores with WCG and only run while battery level is 70%+ and it's contributing 200 to my current RAC on Rosetta alone - mainly because I have the opportunity to keep my phone charging quite a lot through the day. The regular supply of tasks recently is giving me a nice boost. No complaints here.

My S4

---

The Samsung devices seem to be stable running Rosetta compared to some other devices. It would be nice if volunteers running android devices can provide us some input about how Rosetta is or is not running well on their device. For example, device make and specs along with host ID.

The Samsung devices seem to be stable running Rosetta compared to some other devices. It would be nice if volunteers running android devices can provide us some input about how Rosetta is or is not running well on their device. For example, device make and specs along with host ID.

This is me
It's always seemed a bit flakey in the past, but the most recent batch of jobs has seemed to run stably and no errors come up at all. I'm guessing I'm benefitting from the changes you described earlier - lower memory req't etc. I imagine this will improve as people upgrade over time.

---

This phone has been running fine. The only "errors" were the missed deadlines.

---