Thank you for your answer. Unfortunately, I don't have root on my phone and won't do it, but I'll try to get it running on my PC. 😊

---

Thank you for your answer. Unfortunately, I don't have root on my phone and won't do it, but I'll try to get it running on my PC. 😊

Indeed. I have two phones and rooted the old one which I only use for Boinc. I would never risk rooting the phone I use every day. All kinds of shit could go wrong. It's absurd this is required for so many things. Whoever wrote the Android OS is an idiot.

I may have spoken too soon. The tasks were running for exceptionally long times (18-26 hours) - although unlike the normal "not doing anything" vbox tasks, they were showing significant CPU time utilised (rather than the tasks that "run" for 18 hours but have only consumed 10-20 seconds of CPU). I shut down BOINC, rolled VBox back to version 6.1.12 (BOINC recommended version, not 6.1.32 which I had been running), restarted, and all the vbox tasks came up with computation errors.

Oh well, will see what happens with the next tasks to run.

I'm on VB version 5 (or Cosmology breaks completely) and it seems to run Rosetta Python just as well as 6. LHC is also happy with it. Kryptos at Home also hates 6. Seems like VB screwed up when they made the new one.

Downgraded to VBox 5, everything was happy. Tried upgrading back to VBox 6.1.12, and everything continued to be happy, including an in-progress task resuming and completing normally. So maybe there was something up with 6.1.34 - and in-progress tasks can cope with VBox upgrades but not downgrades.

So looks like I'll stick with VBox 6.1.12 for the time being. I'm only using it for R@H (or other enrolled BOINC projects if they can make use of it) so not being up-to-date won't affect anything else.

I am using 6.1.34 on rosetta python, Atlas@home and QuChem. All go well, but QuChem has many invalid results, not errors.
Tullio

---

I am using 6.1.34 on rosetta python, Atlas@home and QuChem. All go well, but QuChem has many invalid results, not errors.
Tullio

My QuChem works perfectly on VB5. The good VB before they messed it up.

Why do you differentiate between "invalid" and "error"?

I think error means task crashed and result wasn't uploaded to server.
Invalid means task ran to completion but result wasn't accepted by the project..

Thank you for your answer. Unfortunately, I don't have root on my phone and won't do it, but I'll try to get it running on my PC. 😊

Then you phone might as well do some other non virtual box work from another project.
This project has gone to 99% virtual box.

Look on the BOINC list of projects and see what there is for ARM projects, but then watch out for the virtual box symbol because the project may be only virtualbox work.

I am using 6.1.34 on rosetta python, Atlas@home and QuChem. All go well, but QuChem has many invalid results, not errors.
Tullio

My QuChem works perfectly on VB5. The good VB before they messed it up.

Why do you differentiate between "invalid" and "error"?

Maybe you should check with the project for us and see if they know that VB 6 flavors DO NOT work on their project. Because I had the 6.1.32 and QuChem kept going unstable. So I gave up.

Thank you for your answer. Unfortunately, I don't have root on my phone and won't do it, but I'll try to get it running on my PC. 😊

Then you phone might as well do some other non virtual box work from another project.
This project has gone to 99% virtual box.

Look on the BOINC list of projects and see what there is for ARM projects, but then watch out for the virtual box symbol because the project may be only virtualbox work.

Einstein (Radio waves) works on all phones that aren't really old. My V4.5 Android can't do more than one at a time for no apparent reason.

Universe runs on any phone.

WCG when it's back will run cancer on any but the oldest phones, and covid on any phone.

Sidock is considering an Android app.

Yoyo runs on any phone.

Moo wrapper runs on any phone.

I am using 6.1.34 on rosetta python, Atlas@home and QuChem. All go well, but QuChem has many invalid results, not errors.
Tullio

My QuChem works perfectly on VB5. The good VB before they messed it up.

Why do you differentiate between "invalid" and "error"?

Maybe you should check with the project for us and see if they know that VB 6 flavors DO NOT work on their project. Because I had the 6.1.32 and QuChem kept going unstable. So I gave up.

There's already a thread on it but no admins, just like here:
https://quchempedia.univ-angers.fr/athome/forum_thread.php?id=162

I'd love to work in a university called "angers"!

yoyo and moowrap crash on redmi 9 nfc

yoyo and moowrap crash on redmi 9

Weird, I assume that's Android 10? I can run both of those on Android 7 and 4.5.

nfc

No idea what that means.

So how's it going in Russia, you didn't answer last time.

https://en.wikipedia.org/wiki/Near-field_communication

Can you charge with that? Otherwise I guess it's a faster closer bluetooth?

And why are you shy about Russia?

I am using 6.1.34 on rosetta python, Atlas@home and QuChem. All go well, but QuChem has many invalid results, not errors.
Tullio

My QuChem works perfectly on VB5. The good VB before they messed it up.

Why do you differentiate between "invalid" and "error"?

It is the project that makes the difference. I follow their naming.
Tullio
I have 56 invalids and 2 errors. I am number 59 in the RAC list.

---

I am using 6.1.34 on rosetta python, Atlas@home and QuChem. All go well, but QuChem has many invalid results, not errors.
Tullio

My QuChem works perfectly on VB5. The good VB before they messed it up.

Why do you differentiate between "invalid" and "error"?

It is the project that makes the difference. I follow their naming.
Tullio
I have 56 invalids and 2 errors. I am number 59 in the RAC list.

Your computer one generated an error. Not your fault. That was a plagued task. No one had it validate successfully.

Computer 2 - invalid validate error. not your fault. again...everyone else had the same problem.
Then you have Completed, validation inconclusive. Again, not your fault.

It seems to be a bug in their system. The error messages are consistent and the people before and after you get the same result.

The two error types are Completed, can't validate and Completed, validation inconclusive.
Neither one has anything to do with your machines. It's the tasks and their validation process that have issues.

I have three Windows PC , one old Linux laptop and one Linux Virtual Machine on a Windows 10 host. The Linux computers all validate their tasks. The rosetta python tasks all validate, as the ATLAS@home tasks at LHC@home CERN tasks.
Tullio

---

I have three Windows PC , one old Linux laptop and one Linux Virtual Machine on a Windows 10 host. The Linux computers all validate their tasks. The rosetta python tasks all validate, as the ATLAS@home tasks at LHC@home CERN tasks.
Tullio

Almost every one of my Python and 4.2 tasks validate, on 7 Windows PCs for 4.2, and 2 Windows PCs for Python (since only those two are new enough to run them). Not sure why anyone is grumbling about anything apart from:

1) Python only runs on very new machines, having AVX instructions.
2) 4.2 tasks are very rare so there's nothing to do on older machines, or for people who don't want that shitty virtualbox slowing their machine down.

I have three Windows PC , one old Linux laptop and one Linux Virtual Machine on a Windows 10 host. The Linux computers all validate their tasks. The rosetta python tasks all validate, as the ATLAS@home tasks at LHC@home CERN tasks.
Tullio

Almost every one of my Python and 4.2 tasks validate, on 7 Windows PCs for 4.2, and 2 Windows PCs for Python (since only those two are new enough to run them). Not sure why anyone is grumbling about anything apart from:

1) Python only runs on very new machines, having AVX instructions.
2) 4.2 tasks are very rare so there's nothing to do on older machines, or for people who don't want that shitty virtualbox slowing their machine down.

Hardly, avx came out at the start of 2011 - very new in terms of computers would be at least the start of 2021.

I have three Windows PC , one old Linux laptop and one Linux Virtual Machine on a Windows 10 host. The Linux computers all validate their tasks. The rosetta python tasks all validate, as the ATLAS@home tasks at LHC@home CERN tasks.
Tullio

I just grabbed you top two machines and saw the errors.
Each machine is different.
I can run Python with no problems most of the time.
LHC ATLAS runs background no problem.
I grind Einstein and Prime Grid no problem either.
So not sure whats up with your two machines other than just bugged tasks because others also errored out on the same task. it was a 100% failed task start to finish.

LHC runs a bit more professionally and their data is all the same. Not the new and weird stuff they try here.