| 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: 6
|
|
| Author |
|
|
vlado101
Senior Cruncher Joined: Jul 23, 2013 Post Count: 226 Status: Offline Project Badges:
|
Hello everyone,
----------------------------------------I was hoping that some of the users on these forums that are using their LG G4 give me some tips about setting up my phone to cruch. I have recently upgraded my phone from a samsung and I have set up the BOINC app previously. Currently here are my settings: Daily limit: 600 mb (I have unlimited plan). Power source: wall socket (only when plugged in to charger). max batter temp: 40c Used Cpu cores: 3 cpu limit: 100% Pause at CPU usage: 30% Max used space: 10% Min Space storage: 1gig Access interval 60s Ram limit: 100% The issues that I have been having is that any time I select more than 3 CPUs I only see 3 CPUs running. The max number is 6, but even set at 6 I only see 3 running. Another issue that I have been facing is that even if I leave my phone to run Workunits over night ( I also leave it plugged in when I am at work through a wall socket and not through usb) I see the workunit almost complete and then go to 0. I am aware that currently there are checkpointing issues on OET ( and I had this on my previous phone), but this seems a bit excessive. I checked the log and because I am only using 3 out of 6 Cpus I don't see my phone stopping due to heat. Is anyone else having such an issue with an LG phone? I think I might have to use this phone for another BOINC project since it does not seem to be submitting work units for OET project :( ![]() [Edit 1 times, last edit by vlado101 at May 9, 2016 5:38:29 PM] |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
You have not posted your event log, which tells how many cores BOINC actually sees, aside from the number you allow. Mine says
Processor: 4 ARM ARMv7 Processor rev 0 (v71) Set the log verbosity to level 5 (max), which gives more details on what's going on. Resetting to zero I've only ever seen if no checkpoint is saved, so if hitting at least 12.6% (indication the task is passed the 1st), it would not do that unless the processes crashes out. Other than that, the occasional 'SigSegv / Signal 11' these single job OETs doing doing fine here. |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Note there was some discussion regarding this on some Androids... these systems having 2 different levels of processor.
|
||
|
|
vlado101
Senior Cruncher Joined: Jul 23, 2013 Post Count: 226 Status: Offline Project Badges:
|
Hi SekeRob*,
----------------------------------------I have put the log setting to 5 and after scrolling for a while I see that for processor it says 6 ARM. I did not see a list that tells me which ARM version it is. Would that information be under Client messages or GUI messeges? I believe I have also heard that post on BOINC forums. However I believe the issue is that BOINC app for android does not automatically put the work unit onto the fastest processor in the phone, but randomly. https://boinc.berkeley.edu/dev/forum_thread.php?id=10677 The only thing I can find about the processor from the LG website is that its 64-bit 1.8 GHz hexa-core CPU. ![]() [Edit 1 times, last edit by vlado101 at May 9, 2016 6:09:35 PM] |
||
|
|
enels
Senior Cruncher Joined: Apr 25, 2008 Post Count: 286 Status: Offline Project Badges:
|
Correct SekeRob. It is likely a big.LITTLE design that uses a Quad-core 1.44 GHz Cortex-A53 for the heavy lifting & dual-core 1.82 GHz Cortex-A57 for lighter loads.
I don't know how BOINC handles switching from 3 or 4 cores to 2, or if it ever does. Presumably it would suspend more than 2 running tasks. I'd watch to see if this happens, or you switch to LITTLE mode when unplugging. I'd also try 'Pause at CPU usage above' 100% instead of 30% and see what happens. |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Was half asleep still [a 36 hour drive did not do me well]... ticked under client logging android and client_sched logging. That's where the processor message is logged.
"However I believe the issue is that BOINC app for android does not automatically put the work unit onto the fastest processor in the phone, but randomly." Scary, as this could be a cause why you have tasks dying. |
||
|
|
|