| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 17
|
|
| Author |
|
|
TheOldH2OMaker
Cruncher Joined: May 19, 2012 Post Count: 2 Status: Offline Project Badges:
|
I am having, I believe, the same problem(s) with one of my Android devices but not the other one (locking up, checkpointing, hanging up a 100%, etc.). The problem child is a Azpen A742 quad core tablet and the one that runs OET without a hiccup is a Motorola Moto G 2nd gen. Only difference between them is the Azpen is running Kitkat and the Moto G is running Marshmallow. Any thoughts.....?
|
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Let tell this *again*: There's no hanging at 100%, all my observations have been. The state can last up to 9-10 hours [it does on my Nexus 7 2013]. It's computing for sure. If the task is restarted it resumes on 99.9%, very quickly goes to 100% and then spends all the overtime there. Why some do, most don't? Ask the technicians who must have read this without a doubt. Given the project will last probably till 2018 at this pace, through batch 5463 we now know, that's with inaction several years of biting tongue.
----------------------------------------[Edit 1 times, last edit by SekeRob* at Jan 16, 2016 6:29:18 PM] |
||
|
|
TheOldH2OMaker
Cruncher Joined: May 19, 2012 Post Count: 2 Status: Offline Project Badges:
|
WELL, I guess I'm just going to dump WTG off my Aspen and only let my Moto do the crunching...I don't have the time to waste on waking up up the "baby" for feeding every time it needs it...Pitty, it WORKED really great on first installation on it, but a short while back it started doing what is currently doing... Thanks, SekeRob
|
||
|
|
Chris311
Cruncher Germany Joined: Jan 3, 2016 Post Count: 20 Status: Offline Project Badges:
|
I have not received any new OET taskes for the last two days... Anyone else having that problem?
----------------------------------------And that 12.5/25%... problem is the same with my Samsung S5mini... Cheers, Chris ![]() |
||
|
|
Skivelitis2
Advanced Cruncher USA Joined: Mar 21, 2015 Post Count: 113 Status: Offline Project Badges:
|
I am having, I believe, the same problem(s) with one of my Android devices but not the other one (locking up, checkpointing, hanging up a 100%, etc.). The problem child is a Azpen A742 quad core tablet and the one that runs OET without a hiccup is a Motorola Moto G 2nd gen. Only difference between them is the Azpen is running Kitkat and the Moto G is running Marshmallow. Any thoughts.....? I have the same Azpen tablet. The problem, I believe, is that it only has 512Mb of Ram. Certain batches of OET1 workunits seem to use slightly more than others and this causes the tablet to become memory-bound and the work units fail. I had to eventually stop running it. Don't believe the problem is with KitKat at all. But for $20 USD what can you do? It works well for Universe, Citizens Science Grid (Subset Sum), YoYo (Cruncher), Asteroids, and Enigma. Exhibits the same problem with Einstein, SkyNet pogs, and SETI, even when used as a dedicated cruncher. Just seems to struggle with four work units (well, 5 with WUProp), the OS overhead, and all the other crap that is so difficult to remove/disable. ![]() |
||
|
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3315 Status: Offline Project Badges:
|
Skivelitis2,
----------------------------------------Is BOINC set to use 100% of RAM in that tablet? I ask because I have a single core smartphone running Einstein@home and it 512 MB of RAM and it wouldn't run if BOINC isn't set to use 100% of RAM. It actually has way less available, more like 480 MB. ![]() - AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W - AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W - AMD Ryzen 7 7730U 8C/16T 3.0 GHz |
||
|
|
Skivelitis2
Advanced Cruncher USA Joined: Mar 21, 2015 Post Count: 113 Status: Offline Project Badges:
|
Falconet,
----------------------------------------Yes it is set to use 100% RAM. Thing is, when I first got it there was no problem at all returning valid work. When things started to go south, I noticed that RAM usage went from about 20-22 Mb per work unit to about 30 or so for a bit. Later they came back down to near 20 and everything was fine for a while. When they again went up in RAM slightly work units began to fail again. It seems like such a small difference but really seems to matter on this particular model. Unfortunately, my young nephew broke the screen and it is stuck on Universe at this time and can't switch back to do any further testing. It should be noted that all RAM figures were derived from the results page at WUProp. ![]() |
||
|
|
|