The Scottish Boinc Team

scole250 wrote:The guys are still working on an updated NativeBoinc install. They have a little bit of learning curve on this. All the android app development they've done up to now has been in Java. NativeBoinc is C so it's taking a little bit of time to work it out.

C is quite another cup of coffee, compared to Java...

Our app developer has a question...

I'm looking for a better understanding of some things.
If I am seeing things correctly the NativeBoinc(https://play.google.com/store/apps/deta ... oinc&hl=en) that you use combines the AndroBoinc(https://play.google.com/store/apps/deta ... androboinc) manager for remote clients and an internal client compiled for android devices. There is also the Boinc from Berkeley(https://play.google.com/store/apps/deta ... eley.boinc) that seems to also do this.

I believe you mentioned that the Berkeley version wasn't liked as well as the NativeBoinc. If this is correct then I would like to know why. The context of my question comes from the fact that I will be using the NativeBoinc app merely as inspiration for my own app. I need to understand the differences that made NativeBoinc better.

The Berkeley Boinc client for Android won't cooperate with BOINCTasks, meaning that remote control is not possible.
With NativeBoinc that's no problem.

Dirk Broer wrote:The Berkeley Boinc client for Android won't cooperate with BOINCTasks, meaning that remote control is not possible.
With NativeBoinc that's no problem.

He ran into some issues using the NativeBoinc source and I think he's wanting to mod the Berkeley version to make it do what we want it to do. I've told him not being able to connect to it from a Manager running on a different computer. Any other deficiencies in the Berkeley version?

I don't know exactly about NativeBoinc, but Berkeley's Boinc for Android only supports ARM.
I recall Alex running Android for x86 and only being able to crunch Seti, so NativeBoinc supports more architectures (MIPS also runs Android and has a BOINC manager).

The x86 issue is due to the lack of projects that support. The biggest problem is lack of external managment support ie remote access and that nativeBoinc is useless beyond android 4 as it does not support pie/ non pie apps.

Alez wrote:nativeBoinc is useless beyond android 4 as it does not support pie/ non pie apps.

Isn't that reversing cause and effect? NativeBOINC doesn't run on Android 5 or higher, so by definition can't handle pie/non pie.
Once NativeBOINC is Android 5 compatible it will automatically be able to run pie/non pie apps.

I presume so.

Any news on this?

I gave up on my minions but I'll check with them again.

Various Android clients.

[https://boinc.berkeley.edu/dl/boinc_7.4.43.apk
[https://boinc.berkeley.edu/dl/boinc_7.4.44.apk
[https://boinc.berkeley.edu/dl/boinc_7.4.45.apk
[https://boinc.berkeley.edu/dl/boinc_7.4.46.apk
[https://boinc.berkeley.edu/dl/boinc_7.4.47.apk
[https://boinc.berkeley.edu/dl/boinc_7.4.48.apk
[https://boinc.berkeley.edu/dl/boinc_7.4.49.apk
[https://boinc.berkeley.edu/dl/boinc_7.4.50.apk
[https://boinc.berkeley.edu/dl/boinc_7.4.51.apk
[https://boinc.berkeley.edu/dl/boinc_7.4.52.apk
[https://boinc.berkeley.edu/dl/boinc_7.4.53.apk

Am am about to inherit a sony cell phone/mobile/handy/whatever with Android 4.3 on it and a dual-core CPU, no earth-shakings specs you'd say.
This is because the former owner -my wife- got a new phone. Now I'm not much of a mobile phone user (I still used an old Nokia running Symbian up till now), but the specks of her new phone let me drop my jaw. Her Huawei P Smart is supposed to be a 'light' mobile phone, but it features an octo-core HiSilicon Kirin 659 CPU with an ARM Mali-T830 MP2 GPU and runs Android 8.0

This puts many an Android TV to shame. My son appears to have a mobile phone with even better specs. We seem to be doing something wrong, crunching as we do, or I've missed something more while hiding under a rock. I think we shouldn't be trying to let Native Boinc run under Android 5.1 (or higher), we should aim at a New Native Boinc, integrated with a BOINC Tasks-like interface to run our crunching farms from our Android Smartphones.

I've got a Huawei P9 Smart to, nice bit of kit, as good as my Google Nexus 5X was before it blew itself up .... probably due to BOINC.

Dirk Broer wrote: ↑Sun Jun 17, 2018 12:56 amI think we shouldn't be trying to let Native Boinc run under Android 5.1 (or higher), we should aim at a New Native Boinc, integrated with a BOINC Tasks-like interface to run our crunching farms from our Android Smartphones.

BOINCTasks seems to have been thinking along similair lines:

BoincTasksCloud: Control BOINC from anywhere.
New, the connection now fully secured using ssl (https).
Allows you to control BOINC on your pad of phone all over the world.
Check out BoincTasks Cloud