Is "edu.berkeley.boinc:remote" process really useful?

Message boards : Android : Is "edu.berkeley.boinc:remote" process really useful?
Message board moderation

To post messages, you must log in.

AuthorMessage
siu77

Send message
Joined: 20 Jun 12
Posts: 12
Russia
Message 62386 - Posted: 30 May 2015, 10:58:19 UTC
Last modified: 30 May 2015, 10:59:11 UTC

It eats 1-2% of 1 core even when boinc is not active. And even if a phone is not charging. Why?

Is it possible to turn it off somehow?

Thank you.

boinc 7.4.41. x86. android 4.4.2. asus zenfone 4.
ID: 62386 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 62387 - Posted: 30 May 2015, 15:13:18 UTC - in response to Message 62386.  

It's an Android process that allows one service to run with multiple processes. If this weren't used, a multi-core CPU in an android device would always run one process only.
ID: 62387 · Report as offensive
siu77

Send message
Joined: 20 Jun 12
Posts: 12
Russia
Message 62390 - Posted: 30 May 2015, 16:18:35 UTC - in response to Message 62387.  

Thanks for the answer, Ageless.

I only wanted to ask: why boinc consumes power, instead of sleeping entirely until next recharging?
ID: 62390 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 62391 - Posted: 30 May 2015, 16:29:19 UTC - in response to Message 62390.  

If you changed your preferences to run always, then that's why.
If you didn't, then in the case of this process it's not BOINC, instead it's the Android process called android:process=":remote" that runs. And as far as I know it'll run always.

I looked on the internet if there's a way to stop the process, but there isn't.
The developers can't do without it either, as then BOINC only runs one thread always, instead of however many threads it can run on the CPU (and next GPU).

Here's what I also found on my searches:
In Android, there's an important distinction between a running service and a running process.

A service follows a carefully defined lifecycle; it begins when onStartCommand() is called and ends after onDestroy() is finished. During that lifetime, the service can be performing tasks or sitting idle, but it is still running.

A process can extend beyond the life of a service. As you've seen, the process can keep running for some time after your service has stopped. Don't worry about it. Android will destroy the process and reclaim any resources exactly when it needs to. It's definitely confusing at first, but once your service has stopped, you don't need to care about the process it was in.

Bottom line: if onDestroy has been called, your service has stopped. Don't worry about the leftover process.

ID: 62391 · Report as offensive
siu77

Send message
Joined: 20 Jun 12
Posts: 12
Russia
Message 62401 - Posted: 30 May 2015, 17:44:33 UTC - in response to Message 62391.  
Last modified: 30 May 2015, 17:45:43 UTC

If you changed your preferences to run always, then that's why.
Do you mean "Power sources for computation" option on Android or some global BOINC options which are controlled from the projects? I'm not quite understand which preferences.

Don't worry about it
I'm worry about battery life, that's all.
ID: 62401 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 62402 - Posted: 30 May 2015, 18:35:08 UTC - in response to Message 62401.  
Last modified: 30 May 2015, 18:35:29 UTC

Do you mean "Power sources for computation" option on Android
Yes those.
...or some global BOINC options which are controlled from the projects?
BOINC on Android doesn't use the web-based computing preferences, only the local preferences.
ID: 62402 · Report as offensive

Message boards : Android : Is "edu.berkeley.boinc:remote" process really useful?

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.