Hello,

is it possible to build the boinc-client with enabled gui_rpc for remote control and replace the official one? I'm asking because gui_rpc is not allowed on the official client an, as far as i know, there is no way get it working.

I have several arm-devices (development boards) which are running linux and android. I'll get some more of them in the future an i'm planning to get them all running with android because there are more projects which support android on arm then linux on arm.

It will be hard to handle 10+ devices without a way for remote control.

Best regards,
Nuke

For devices with an Android below 5.0 you can use the alternate NativeBOINC (Not maintained since longer). It got many features the desktop client has to include naming the device and the possibility to put the data on an SD, but, some things were achieved with hacks, and that you wont see Berkeley supporting. This client can also be used to remote control BOINC on desktops. (Actually I use free and secure TeamViewer for this.)

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

I checked with X-plore File Manager while being super user (SuperSU) in root/data/data/edu.berkeley.boinc/client/ and see that gui_rpc_auth.cfg is there, all 32 bytes with its random 32 character password.

What you probably need though and isn't there, is the remote_hosts.cfg file. But I don't see why it cannot be added, as long as you have write capability to that directory. As far as I know, the actual client isn't that different from the one on Windows or Linux, so it should work fine with the remote_hosts.cfg file.
http://boinc.berkeley.edu/wiki/Controlling_BOINC_remotely

---

To answer the original question, yes, you can build BOINC for Android yourself. See Building BOINC. I can search what you need to change once you have a working build system.

The stock client for Android can't be controlled remotely. It's hard-coded to use Unix local sockets for GUI RPCs. I believe (but don't take my word for it) this is so that the client is less likely to introduce a remotely exploitable security hole and thus be more likely that Google accepts bundling it with Android.

I will set up the bulid system next week. Thank you!

For devices with an Android below 5.0 you can use the alternate NativeBOINC (Not maintained since longer).

NativeBOINC is already running on my Android 4.4 devices, but, as you said, there is no support for newer versions.