Set allowance to compute while using. No troubles here doing calls over VOIP on tablet. It's only when suspension is longer, the apps get pushed out of memory... not the app, but BOINC is the dictator on that. It's as if LAIM has become time-limited on Android... and if short of memory, the OS rules. It is what it is [And OET1 is so much more stable as 2nd generation VINA app on Android compared to 1st.Gen. FAHV]

Between the flaws in the Android app and the long periods between checkpoints on this project, I can't get OET jobs to complete. I just had one running all night, this morning it finally was at 100% when I awoke (which it always sits at for a long time). After I had breakfast I checked to see if it completed and uploaded, but instead it was back at 75% minus several hours of work. This job has been running for days and is now a "no reply". The phone was on the charger the entire time.

The checkpoints are farther apart than the interruptions!

If WCG is not going to be serious about making Android work why does it bother supporting Android? If no one is going to address and fix I'm going to uninstall since I am just wasting my time and resources.

(no cheers this time - I'm too upset)

My Samsung S3 has the same problem.
WUs stay at 100% for ages, then go back to 90 odd %. Usually then are reported late as they take over 36 hrs real time, though report as just over 24 hrs, and get awarded 12 hrs.
I have to keep aborting the WUs in cache before they start, as I know they wont complete anywhere near the deadline time.
Currently have 2 that the ddeadline is in 30mins, 1 is at 100% the other has just gone back to 96%.

Any chance of increasing the deadline time on these WUs for android devices?

Update: Gave up and have uninstalled from my phone. I need to use my phone and at the moment I can't if WUs are to process in current time constraints.

Patrick

Does everyone that has an issue crunching on android use the BOINC app available on marketplace? Does any one that uses NativeBOINC or HTC power to Give or the Samsung version received the same issues?

I did not notice any problem with FAAH WUs not being able to complete. It also appears that LAIM is not working, which results in any interruption causing the client to restart at the last checkpoint, which is usually several hours. The bug with the status displays make it impossible to tell which device is struggling using the website.
I've often posted that not having the date in the timestamp in the results log is a real problem in diagnosing long-running jobs. The client reports its just been running a few hours when it really has been running several days and constantly resetting. That really needs to be addressed.
I too had aborted jobs because I could see that they were not going to ever complete. One time I had a job that was overdue, but it was at 100% so I thought it would complete on time. When I checked on it about 30 minutes later it had reset back to 75% and lost many hours. I pulled the plug on that job since it was never going to finish.
What really annoying is that I need to have a pad of paper to keep track of whats going on with the work, monitor progress, keep track of what device is what and that is what the client and website should be doing for us. The problems that I have noticed are ones that are really bad. I can't really tell if there are more problems because the tools are so non-functional.

Cheers