My phone (Nexus 4, so Snapdragon S4 Pro which is 4x Armv7) hasn't completed any tasks. I suspect something to do with memory access due to the exit codes including:

Exit status 193 (0xc1)
Exit status 11 (0xb)

D

---

Let's see if this version behaves good running on Android , The last time Rosetta was ported to ARM/Android was a disaster

First task finished succesfully using my ZTE L2 (MTK6582) . Althought, I noticed hundreds of warnings when reading the log...

warning: set times/attribs failed for ./minirosetta_database/chemical/atom_type_sets/coarse_rna/
warning: cannot set permissions for ./minirosetta_database/chemical/atom_type_sets/centroid_rot/
Operation not permitted
warning: set times/attribs failed for ./minirosetta_database/chemical/atom_type_sets/centroid_rot/
warning: cannot set permissions for ./minirosetta_database/chemical/atom_type_sets/centroid_min/
Operation not permitted
warning: set times/attribs failed for ./minirosetta_database/chemical/atom_type_sets/centroid_min/
warning: cannot set permissions for ./minirosetta_database/chemical/atom_type_sets/centroid/
Operation not permitted
warning: set times/attribs failed for ./minirosetta_database/chemical/atom_type_sets/centroid/
warning: cannot set permissions for ./minirosetta_database/chemical/atom_type_sets/
Operation not permitted
warning: set times/attribs failed for ./minirosetta_database/chemical/atom_type_sets/
warning: cannot set permissions for ./minirosetta_database/chemical/amoeba/
Operation not permitted
warning: set times/attribs failed for ./minirosetta_database/chemical/amoeba/
warning: cannot set permissions for ./minirosetta_database/chemical/
Operation not permitted
warning: set times/attribs failed for ./minirosetta_database/chemical/
warning: cannot set permissions for ./minirosetta_database/
Operation not permitted
warning: set times/attribs failed for ./minirosetta_database/
Setting database description ...
Setting up checkpointing ...
Setting up folding (abrelax) ...
Beginning folding (abrelax) ...
BOINC:: Worker startup.
Starting work on structure: _00001
======================================================
DONE :: 1 starting structures 7399.9 cpu seconds
This process generated 1 decoys from 1 attempts
======================================================
BOINC :: WS_max 0
BOINC :: BOINC support services shutting down cleanly ...
15:42:23 (6817): called boinc_finish(0)

---

Life is too short to live concerned about its mysteries.

"Chilean" wrote:

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

wow, pretty impressive considering the 'small' mobile cpu compared with today's desktop / server rocket engines lol :)

Only my Nexus 7 2013 has some problems with Rosetta. All of my devices seem to work perfectly. However, I've added an ASUS ZenFone Zoom (ASUS_Z00XS Intel Atom Z3580 2.3GHz 64bit, but the project says 1.33GHz) and I'd like to know if there are plans about a version for x86 Android devices.

---

ASUS X570 E-Gaming
AMD Ryzen 9 3950X, 16 core / 32 thread 4.4 GHz
AMD Radeon Sapphire RX 480 4GB Nitro+
Nvidia GTX 1080 Ti Gaming X Trio
4x16 GB Corsair Vengeance RGB 3466 MHz

i'm thinking that boinc/r@h on android is perhaps a little 'bleeding edge' :)
havn't tried this out, but if for any reason that 1 can run linux on those Intel Android phones/devices, i'd guess it might be possible to run the 'real' r@h for linux :o lol

1 may like to try out some virtualization apps and run linux in a virtual shell :)

...
here u go:
https://play.google.com/store/apps/details?id=ru.meefik.linuxdeploy
certainly no less bleeding edge :o lol

https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=2473600

Intel Atom Z3580 quad-core 2.3GHz, 4GB RAM, 54GB of free memory, high power in single core. I'd really like to run Rosetta@Home on my smartphone.

---

ASUS X570 E-Gaming
AMD Ryzen 9 3950X, 16 core / 32 thread 4.4 GHz
AMD Radeon Sapphire RX 480 4GB Nitro+
Nvidia GTX 1080 Ti Gaming X Trio
4x16 GB Corsair Vengeance RGB 3466 MHz

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

Still getting this error. No solution for it?

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:
db_designs5_t6c.1295.7_0001_android_SAVE_ALL_OUT_327271_4214_1_0
-161 (not found)


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

Still getting this error. No solution for it?

This is likely due to the filtering stringency set by Vikram (the scientist who is running these jobs). If you increase the run time setting, you may get less of these errors since it will give the job a chance to pass the filters and thus produce models. Vikram tried to set the filtering so that at least one model would be generated but there is no guarantee the way the protocol has been written. I'll talk to Vikram and see if he can fix this issue for the next app update.

[quote]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.

Soon, people will complain that Rosetta WUs fail on their Android-powered toasters due to lack of RAM.

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

Still getting this error. No solution for it?

This is likely due to the filtering stringency set by Vikram (the scientist who is running these jobs). If you increase the run time setting, you may get less of these errors since it will give the job a chance to pass the filters and thus produce models. Vikram tried to set the filtering so that at least one model would be generated but there is no guarantee the way the protocol has been written. I'll talk to Vikram and see if he can fix this issue for the next app update.

But all these units generate structures and seem to finish calculations OK, it is after at uploading when occurs the error, isn't it?

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

Still getting this error. No solution for it?

This is likely due to the filtering stringency set by Vikram (the scientist who is running these jobs). If you increase the run time setting, you may get less of these errors since it will give the job a chance to pass the filters and thus produce models. Vikram tried to set the filtering so that at least one model would be generated but there is no guarantee the way the protocol has been written. I'll talk to Vikram and see if he can fix this issue for the next app update.

I upped the wu crunching time to 4 hours and errors seem to have dissappeared :)