While everything done can be perfectly done in a dev board, it will probably save headaches doing it on a x86 computer.
The first thing we will need for this is an android system suitable for our system. this will work just right :
We download it and extract it.
Now we need to uncompress the android system image. Fortunately, we have a tool for that, unfortunately, it is not on the repositories of many distributions. Ubuntu and Debian have one, Archlinux has it on the AUR, and for the rest of them you have this git repository : https://github.com/anestisb/android-simg2img
Once we have it ready we can apply it to our rootsystem.img, running it as : simg2img rootsystem.img rootsystem.ext4 . And now we can access it's data, as it's just a regular loop device.
So we create a directory : mkdir androidimg
And we mount it : mount -t ext4 -o loop rootsystem.ext4 androidimg
We do now need to copy these files to our dev board, so just plug any pen drive, sd and copy those files from the folder to it.
Assuming you have already copied that folder to your dev board and are now operating from it .
What it's now needed it's to create a chroot script.
So we create a file called setup-chroot.sh and we add these lines :
cd androidimg/
mount -o /etc/resolv.conf etc/resolv.conf
mount -t proc /proc proc/
mount --rbind /sys sys/
mount --rbind /dev dev/
and we move it to /usr/local/bin
Now we move on installing the android version of boinc. You could cross compile it yourself, but the easiest way its to download it from this link : https://boinc.berkeley.edu/dl/boinc_7.4.53.apk
And we extract it with unzip boinc_7.4.53.apk . And we pick the executables from arm64-v8a and we move them to androidimg/boinc .
We could now run it without problem, but it would be a lot more comfortable to automate it on boot.
So we go to /usr/lib/systemd/system/
and we create the file chroot-boinc.service
[Unit]
Description=chroot boinc service
[Service]
RootDirectory=/androidimg
ExecStartPre=/usr/local/bin/setup-chroot.sh
ExecStart=/boinc/boinc
RootDirectoryStartOnly=yes
So it will chroot into it every time it boots, and starts the boinc client.
To control the boinc client we will need to use boinccmd in the directory. So we do
chroot /androidimg
cd boinc
and now we can run boinccmd to pass the commands that we wish.
What most people will want is to synchronize with grcpool.
boinccmd --join_acct_mgr grcpool.com username password
(add the projects in grcpool.com)
boinccmd --quit_acct_mgr
boinccmd --join_acct_mgr grcpool.com username password
for not having to wait for it to synchronize.
Ask me any question you have.