| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Outsmart Ebola Together
Thread: OET Andoid WU issue |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 12
|
|
| Author |
|
|
vlado101
Senior Cruncher Joined: Jul 23, 2013 Post Count: 226 Status: Offline Project Badges: 
|
Hello all,
----------------------------------------I have noticed that on one of my android devices I had OET work units that went up to 0.4% and then reset themselves. I have an HTC M8 with android version 5.0.1. I had no issues with any of FightAIDs work units. Has anyone else experienced this? Below are the WU that I had to abort. However other android devices seem to have no issues. OET1_ 0000477_ xMBGP-FA_ rig_ 11183_ 2-- OET1_ 0000337_ xZAGP-OM_ rig_ 6363_ 4-- OET1_ 0000337_ xZAGP-OM_ rig_ 6331_ 4-- Is this just an error with my android version? Thanks  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Maybe an aggressive application removal/memory cleaning app, which I had to whip into behaving too, or your device not being as stable as we all want them to be.
----------------------------------------There the general higher 'uncontrollable' fail rate that comes with Android. Most common fails are signal 11 and the 193 [visit result logs]. I'm running only half of cores, do not allow to compute when in use, nor allow computing when not on charger and battery is not at 50% charged level. This gives me about 85-90% success rate. I dare say that OET1 seems to be a little bit more stable than FAHV, on Android. @Admin, please move to the Android Support forum. FYI, the last 15 on my droid..., 2 outright errors, no invalid. OET1_ 0000464_ xZAGP-S_ rig_ 74747_ 0-- android_2654196 a Valid 2/16/15 05:20:06 2/16/15 18:18:31 3.75 / 3.99 51.2 / 38.3 OET1_ 0000462_ xZAGP-S_ rig_ 43769_ 1-- android_2654196 a Valid 2/16/15 04:26:27 2/16/15 14:19:21 2.80 / 2.97 36.4 / 32.2 OET1_ 0000463_ xZAGP-S_ rig_ 82642_ 3-- android_2654196 a Pending Validation 2/16/15 01:09:21 2/16/15 11:20:52 3.22 / 3.48 43.4 / 0.0 OET1_ 0000460_ xZAGP-FW_ rig_ 16228_ 0-- android_2654196 a Pending Verification 2/15/15 03:59:48 2/16/15 06:05:33 0.74 / 0.76 7.5 / 0.0 OET1_ 0000460_ xZAGP-FW_ rig_ 11280_ 0-- android_2654196 a Valid 2/15/15 03:56:52 2/16/15 05:20:06 0.87 / 0.89 8.9 / 11.0 OET1_ 0000460_ xZAGP-FW_ rig_ 11313_ 0-- android_2654196 a Pending Validation 2/15/15 03:56:52 2/16/15 04:26:27 0.80 / 0.82 8.2 / 0.0 OET1_ 0000460_ xZAGP-FW_ rig_ 11311_ 0-- android_2654196 a Error 2/15/15 03:56:52 2/16/15 03:39:15 0.69 / 0.71 7.0 / 0.0 OET1_ 0000460_ xZAGP-FW_ rig_ 11310_ 0-- android_2654196 a Valid 2/15/15 03:56:52 2/16/15 02:55:05 0.77 / 0.80 7.9 / 7.6 OET1_ 0000460_ xZAGP-FW_ rig_ 59308_ 0-- android_2654196 a Valid 2/15/15 03:31:03 2/16/15 02:07:16 0.96 / 0.99 9.9 / 9.4 OET1_ 0000331_ xEBGP-OM_ rig_ 7001_ 2-- android_2654196 a Error 2/15/15 02:46:09 2/16/15 01:09:21 8.21 / 8.68 86.6 / 0.0 OET1_ 0000460_ xZAGP-FW_ rig_ 79442_ 1-- android_2654196 a Valid 2/15/15 01:52:42 2/15/15 03:56:51 0.72 / 0.74 7.3 / 7.9 OET1_ 0000460_ xZAGP-FW_ rig_ 7787_ 1-- android_2654196 a Pending Validation 2/15/15 00:54:11 2/15/15 03:31:03 0.73 / 0.75 7.5 / 0.0 OET1_ 0000457_ xSDGP-S_ rig_ 29537_ 3-- android_2654196 a Valid 2/14/15 05:33:28 2/15/15 00:54:10 4.05 / 4.27 42.6 / 40.8 OET1_ 0000459_ xZAGP-FW_ rig_ 81397_ 1-- android_2654196 a Valid 2/14/15 21:42:44 2/15/15 00:46:39 0.59 / 0.63 6.3 / 6.7 OET1_ 0000458_ xZAGP-FW_ rig_ 24157_ 0-- android_2654196 a Pending Validation 2/14/15 14:28:16 2/15/15 00:08:52 0.51 / 0.55 5.5 / 0.0 Maybe the technicians can pitch in with some 'close to the chest' held statistics how the first week with PIE compares to pre-PIE. [Edit 1 times, last edit by Former Member at Feb 16, 2015 6:41:52 PM] |
||
|
|
ThreadRipper
Veteran Cruncher Sweden Joined: Apr 26, 2007 Post Count: 1324 Status: Offline Project Badges: 
|
I have a problem on Android where OET1 WUs reset themselves when I disconnect the charger (WU suspends) and when I reconnect to charger it will reset to 0% or last checkpoint (at around 25% first one as it seems).
----------------------------------------I thought that LAIM was turned on because I cannot find such a setting elsewhere in the app...  Join The International Team: https://www.worldcommunitygrid.org/team/viewTeamInfo.do?teamId=CK9RP1BKX1 AMD TR2990WX @ PBO, 64GB Quad 3200MHz 14-17-17-17-1T, RX6900XT @ Stock AMD 3800X @ PBO AMD 2700X @ 4GHz |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Default LAIM is on BOINC for Android. Ask the developers... maybe they dropped the ball on this with the 5.0 release.
----------------------------------------If at all, absent many settings on the client compared to the PC version, BfA is supposed to listen/was listening in parts to the 'default' profile, no matter what location profile the Android is associated with to select the projects to compute. Not sure at all if that may have been ripped out or not. Again, a question for the client developers, it being clear as mud to me. [Edit 1 times, last edit by Former Member at Feb 16, 2015 7:33:25 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It's one reason I'm going to switch to NativeBOINC [when finding time], it having all these controls of the PC version, -AND- the ability to modify the cc_config.xml, to set the checkpoint debug flag for instance.
|
||
|
|
Eric_Kaiser
Veteran Cruncher Germany (Hessen) Joined: May 7, 2013 Post Count: 1047 Status: Offline Project Badges: 
|
I've got nativeboinc running on five Androids. Neither invalids nor errors on wus.
---------------------------------------- |
||
|
|
ThreadRipper
Veteran Cruncher Sweden Joined: Apr 26, 2007 Post Count: 1324 Status: Offline Project Badges:
|
Yes, perhaps I should look into NativeBOINC as well.
----------------------------------------The behaviour is strange - if a WU is allowed to pass 20 or 25% before suspending it, then it will use that as a checkpoint when reconnecting to a charger. Otherwise it will start from 0% again. To me, that is the expected behaviour of LAIN Off given that it is true that first checkpoint occurs no earlier than at 20/25% into a WU. To me it seems as a strange decision to turn LAIM off per default while at the same time not letting me control that from the Preferences menu. Weird. Join The International Team: https://www.worldcommunitygrid.org/team/viewTeamInfo.do?teamId=CK9RP1BKX1 AMD TR2990WX @ PBO, 64GB Quad 3200MHz 14-17-17-17-1T, RX6900XT @ Stock AMD 3800X @ PBO AMD 2700X @ 4GHz |
||
|
|
sdodson
Cruncher Joined: Dec 31, 2004 Post Count: 1 Status: Offline Project Badges: 
|
What about hitting 100% and staying there for several hours?
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Yes, discussed in other threads too... had one 9 hours sitting there and computing. Before that 3 hours, and on restart went back to 99.99%. No idea what's it doing, but it sat there after reporting as 'Pending Validation'. Not seen how the wingman did as it's now off the RS pages... pity.
|
||
|
|
ravenigma
Cruncher USA Joined: Oct 3, 2012 Post Count: 47 Status: Offline Project Badges: 
|
What about hitting 100% and staying there for several hours? I am seeing this issue as well. I currently have a task which has been at 100% for over two hours.  |
||
|
|
|