Hello all! I hope you're doing fine.

So, I had this issue some days back when 2 WUs on my android phone were stuck on Running at 100% for a really long time. I thought there must be some transient glitch with my phone or something, so I aborted them. Hours and hours of work, put to no use.

But then it again happened today with a WU on another phone. Same thing - kept on running at 100%. Paused the computation from the BOINC app, waited for it to suspend, and when resumed it, all was gone. It reset to 0%, started running from there on, but the time continued from the previous time. Some 40+ hours. Had to abort again.

https://drive.google.com/file/d/1hLIbzlEIcbZLIYAZsmuxjcOwC-r2haPG/view?usp=drivesdk

Is something wrong with my phones (there are other WUs which get successfully completed and validated from these same phones)? Or, some other issue?

Any help will be appreciated.

I have been seeing something similar. I'll find that the task is at 100% and Boinc has stopped running it. If I force the issue by suspending the other tasks, the task will restart from zero. I have been aborting these when I find them, because recently I had a task time-out on Android. I don't know if it had been resetting back to zero endlessly, but it's a possibility. I have no problems with other projects on this host, or problems completing Universe@Home tasks on time (when they behave themselves). I think there may be a problem with what happens when Universe@Home tasks on Android get to 100%.

It just gets stuck on Running 100%, the clock keeps on running. And when you stop it or stop the whole Network/Computation, it resets to 0 and then starts from there. Atleast that's what the percentage status tells.

Had 2 more tasks today that faced the same fate. Both on different phones :(

Hello!
I had the same failure- stopping at 100% - as described on my Samsung tablet at July 4th for 4 tasks each with about 55h crunching time. It seems, that at the end of the task there is an infinite loop. It´s very angry to waste so much time and energy.
The other failure - touching the ||-bottom accidentally resulting in permanent halt - I had yesterday on two tasks too. This is also angry, specially when near end of crunching time.
So it´s fine that I´m not allone with this and
I hope, the administrators will take soon care of this !!!
The fist failure seems to me to be from the application software, the 2 failure my be from BOINC.

Kind regards and happy crunching
Martin

---

I've seen this issue more of late, especially on my RCA (Alco) tablet with 4 processors. I have 4 Android devices working on Universe@Home, as these don't have enough RAM to work on medical projects fighting COVID. The process times can vary greatly, between 130K seconds to over 606K seconds. If I aborted every task that seemed to get "stuck" at 100% I wouldn't get much done.

I note that even though the task shows at 100% that the clock is still advancing, so I assume it's still crunching. Occassionally on my RCA tablet I'll suspend the task, which starts another new task. I'll then unsuspend the 100% task and most times it will start back at 0%. The task is NOT lost, as the clock will continue where it left off. When jobs (Universe BHspin) complete on computers, in the BOINC manager I note there are a number of sections to each task. I've concluded from this that the same process is going on with the Android jobs and that when it "starts over" it is actually starting another section of the task. Krzysztof would need to verify that for us, however.

In other words, I'd suggest to NOT abort these jobs, but try to coax it to continue on as described above or by other means. My longest job so far has taken 7 days (606K seconds), so don't panic.

---