RE: [boinc_projects] platform string for Linux on ARM

123 views
Skip to first unread message

Rom Walton

unread,
Jun 25, 2016, 1:49:37 AM6/25/16
to Eric Korpela, Juha Sointusalo, Boinc Projects, boinc-andr...@googlegroups.com

Okay, I’ve pushed out a new build which will have the alt platform defined for all three 64-bit platforms supporting their 32-bit flavors.

 

I found evidence in the standalone toolchain that leads me to believe that both 64-bit and 32-bit executables are supported on 64-bit platforms.  Namely there are both /usr/lib and /usr/lib64 directories in the virtualized sysroots.  Both containing the same libraries.

 

I found some documentation, namely:

https://developer.android.com/ndk/guides/standalone_toolchain.html#abi

 

Describing the preferred parameters to pass to gcc to support armeabi-v7a and an additional piece of information about a bug with the cortex-a8 processor.  Applying the extra parameters seems to have cleared up the execution failures on 5 of the 13 devices Google tests us against in the play store.

 

I believe 7.4.51 will be a good build to get out to the public.

 

It is important to note that the devices Google tests us against are all ARM devices.  So if anybody has an x86/x86_64/mips/mips64 device you are willing to test out the new build on, let me know how it goes.

 

----- Rom

 

 

 

From: Rom Walton
Sent: Friday, June 24, 2016 5:57 PM
To: Eric Korpela; Juha Sointusalo
Cc: Boinc Projects
Subject: Re: [boinc_projects] platform string for Linux on ARM

 

That’s the part I haven’t been able to look into yet.

Up until a couple days ago I was unaware that BOINC was previously working on the Galaxy S6.  So, at least for that device, it is capable of running 32-bit ARM apps.

I need to find out what the rules are for Android before I go monkeying around too much.  We were accepted into a testing program Google offers to run your app through a robo testing process on a bunch of (13) devices.  We are still failing on a class of devices 32-bit devices where the architecture is ‘armv7l’.

Hopefully I’ll be making some more headway on this during the weekend.

----- Rom

From: Eric Korpela<mailto:kor...@ssl.berkeley.edu>
Sent: Friday, June 24, 2016 5:28 PM
To: Juha Sointusalo<mailto:juha.so...@gmail.com>
Cc: Rom Walton<mailto:ro...@romwnet.org>; Boinc Projects<mailto:boinc_p...@ssl.berkeley.edu>
Subject: Re: [boinc_projects] platform string for Linux on ARM

I would think that it should be added, assuming they can run the 32-bit versions, of course.

On Fri, Jun 24, 2016 at 6:07 AM, Juha Sointusalo <juha.so...@gmail.com<mailto:juha.so...@gmail.com>> wrote:
Shouldn't the 64-bit versions announce 32-bit alt platforms? In the forum
thread the poster's phone doesn't receive work from any project any more
because no project has 64-bit Android apps yet.

-Juha

On 23 June 2016 at 18:50, Rom Walton <ro...@romwnet.org<mailto:ro...@romwnet.org>> wrote:

> I’ve committed a fix for the typo:
>
>
> https://github.com/BOINC/boinc/commit/1eb3d0631b48fdf3d361840daf578bab4d87529a
>
>
>
> I’ll push out a new build tonight.
>
>
>
> ----- Rom
>
>
>
>
>
>
>
> From: Nicolás Alvarez<mailto:nicolas...@gmail.com<mailto:nicolas...@gmail.com>>
> Sent: Thursday, June 23, 2016 8:33 AM
> To: Jord van der Elst<mailto:els...@gmail.com<mailto:els...@gmail.com>>
> Cc: Boinc Projects<mailto:boinc_p...@ssl.berkeley.edu<mailto:boinc_p...@ssl.berkeley.edu>>
> Subject: Re: [boinc_projects] platform string for Linux on ARM
>
>
>
> He must have downloaded the Pirates@Home edition ;-)
>
> But seriously speaking: it's a typo in the code.
>
> https://github.com/BOINC/boinc/blob/5d31a75b/android/build_boinc_arm64.sh#L42
>
> --
> Nicolás
>
> 2016-06-23 12:27 GMT-03:00 Jord van der Elst <els...@gmail.com<mailto:els...@gmail.com>>:
> > Someone on the forums reporting his CPU is misread.
> > In https://boinc.berkeley.edu/dev/forum_thread.php?id=11065 a user
> tells he
> > updated to 7.4.49 from the Google Play Store and since that time his
> > Samsung Galaxy S6 phone cannot get any work anymore due to: "This project
> > doesn't support computers of the type aarrch64-android-linux-gnu"
> >
> > So does BOINC detect the CPU type, or is that 'aarrch64' a typo in the
> > code? Normally these CPUs are detected as aarch64, in his case he has a
> > double 'r'.
> >
> >
> > -- Jord van der Elst.
> >
> > On Wed, Jun 22, 2016 at 9:47 PM, Christian Beer <
> christi...@aei.mpg.de<mailto:christi...@aei.mpg.de>>
> > wrote:
> >
> >> Thanks.
> >>
> >> Regards
> >> Christian
> >>
> >> On 22.06.2016 18<tel:22.06.2016%2018>:56, David Anderson wrote:
> >> > I made those changes to the platform list.
> >> > -- David
> >> >
> >> > On 6/20/2016 6:53 AM, Christian Beer wrote:
> >> >> Hi,
> >> >>
> >> >> while experimenting with Linux on ARM64 (Odroid C2) I recognized that
> >> >> the platform string for ARM (arm-linux-gnueabihf) on
> >> >> http://boinc.berkeley.edu/trac/wiki/BoincPlatforms is wrong. It
> should
> >> >> be arm-unknown-linux-gnueabihf and we should add the string
> >> >> aarch64-unknown-linux-gnu to the list and projects should add this to
> >> >> the platform table. Unfortunately I can't edit this page myself.
> >> >>
> >> >> Regards
> >> >> Christian
> _______________________________________________
> boinc_projects mailing list
> boinc_p...@ssl.berkeley.edu<mailto:boinc_p...@ssl.berkeley.edu>
> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.
> _______________________________________________
> boinc_projects mailing list
> boinc_p...@ssl.berkeley.edu<mailto:boinc_p...@ssl.berkeley.edu>
> http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects
> To unsubscribe, visit the above URL and
> (near bottom of page) enter your email address.
>
_______________________________________________
boinc_projects mailing list
boinc_p...@ssl.berkeley.edu<mailto:boinc_p...@ssl.berkeley.edu>
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.



--
Eric Korpela
kor...@ssl.berkeley.edu<mailto:kor...@ssl.berkeley.edu>
AST:7731^29u18e3
_______________________________________________
boinc_projects mailing list
boinc_p...@ssl.berkeley.edu
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_projects
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Jord van der Elst

unread,
Jun 30, 2016, 3:16:03 AM6/30/16
to Rom Walton, Eric Korpela, Juha Sointusalo, Boinc Projects, boinc-andr...@googlegroups.com
There looks to be problems with 7.4.51

1. A host which detected the CPU correctly with 7.4.43 now does not detect any CPU.
https://setiathome.berkeley.edu/show_host_detail.php?hostid=8006871 showed as ARM AArch64 Processor rev 2 (aarch64) with 7.4.43, Number of processors 8.
It got a new hostID, because it now has a new name, plus a new CPU of sorts: https://setiathome.berkeley.edu/show_host_detail.php?hostid=8034503
CPU shows only as "Number of processors 8", no other distinction.

2. I suspect we have one Nexus 5X on the forums (https://boinc.berkeley.edu/dev/forum_thread.php?id=11070) where the projects list is empty, it shows only the option to use an account manager, everything else is not available.



-- Jord van der Elst.

Seke Rob

unread,
Jun 30, 2016, 3:43:52 AM6/30/16
to Jorden van der Elst, Juha Sointusalo, Rom Walton, boinc-andr...@googlegroups.com, Boinc Projects, Eric Korpela

There's several reports over at WCG with empty project pick lists, only getting Account Mngr as option, no menu icons left or right top. Galaxy S6 with marshmallow. One has 7.4.51 so proposed to go back to 7.4.43.

On my Nexus 7 with 6.0.1 and 7.4.51 no issue but those with problems were clean installs on new devices.

--SekeRob

(Sent from Nexus 7-4G - 2013)

--
You received this message because you are subscribed to the Google Groups "BOINC Android Testing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to boinc-android-te...@googlegroups.com.
To post to this group, send email to boinc-andr...@googlegroups.com.
Visit this group at https://groups.google.com/group/boinc-android-testing.
To view this discussion on the web visit https://groups.google.com/d/msgid/boinc-android-testing/CAEXjb0etRB8%3Df%3D3Hp7eLu6difuuOoh4GG%3DArGz02gGiyjne97w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jord van der Elst

unread,
Jul 3, 2016, 10:05:36 AM7/3/16
to Rom Walton, Boinc Projects, boinc-andr...@googlegroups.com
Another ping about this, as this version is still the one showing on the Google Play Store. It may not be a problem for the 32bit CPUs out there, but together with download problems, non-populated project menus and not detecting of the CPU, I feel 7.4.51 needs to be retracted. Everyone with problems went back to 7.4.43 and they have no problems with that one. So why keep version 7.4.51 as recommended? (It's not even an alpha)

Cheers,


-- Jord van der Elst.

Rom Walton

unread,
Jul 3, 2016, 4:50:37 PM7/3/16
to Jord van der Elst, Boinc Projects, boinc-andr...@googlegroups.com

I’ve deployed a new version which should fix this issue.

 

Basically the Android GUI didn’t know anything about the alternate platform mechanism.  The GUI hard coded what platforms it supported instead of querying the client for them.  I added the alternate platform to the list of supported platforms in the project list.

 

----- Rom

Jord van der Elst

unread,
Jul 4, 2016, 6:15:23 AM7/4/16
to Rom Walton, Boinc Projects, boinc-andr...@googlegroups.com
On a Nextbook tablet, Intel Atom x86_64, Android 5.0 BOINC 7.4.51 and 7.4.53 hang immediately upon initializing. They don't get past the title screen.

I've asked what it does when returning to 7.4.43 (although that one won't detect x86_64 CPUs, I think?)

Cheers,


-- Jord van der Elst.

Jord van der Elst

unread,
Jul 4, 2016, 1:15:48 PM7/4/16
to Rom Walton, Boinc Projects, boinc-andr...@googlegroups.com
This same user installed 7.4.53 on two ARM devices and there it runs fine. He just can't get past the BOINC title screen on .53 on his Intel Atom.
He's now installed 7.4.43 on it and that works fine.


-- Jord van der Elst.

Rom Walton

unread,
Jul 4, 2016, 2:10:56 PM7/4/16
to Jord van der Elst, Boinc Projects, boinc-andr...@googlegroups.com

Well that is interesting.

 

We were getting sporadic reports of the title screen lock-up issue with .43, on a mix of all device types.  Which lead us to the need for arm64, x86_64, and mips64 platform types.

 

Google allowed us to use one of their device testing facilities, which unfortunately only had various arm based devices, and I was able to track down and (maybe fix?) the additional issues with running BOINC on arm based devices.

 

I guess I have some more research to do for x86_64.

 

----- Rom

 

boincadm@boinc-build-android:~/boinc/android/BOINC/assets/arm64-v8a$ file boinc

boinc: ELF 64-bit LSB shared object, version 1 (SYSV), dynamically linked (uses shared libs), stripped

boincadm@boinc-build-android:~/boinc/android/BOINC/assets/arm64-v8a$ file boinccmd

boinccmd: ELF 64-bit LSB shared object, version 1 (SYSV), dynamically linked (uses shared libs), stripped

boincadm@boinc-build-android:~/boinc/android/BOINC/assets/x86_64$ file boinc

boinc: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), stripped

boincadm@boinc-build-android:~/boinc/android/BOINC/assets/x86_64$ file boinccmd

boinccmd: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), stripped

boincadm@boinc-build-android:~/boinc/android/BOINC/assets/mips64$ file boinc

boinc: ELF 64-bit LSB shared object, MIPS, version 1 (SYSV), dynamically linked (uses shared libs), with unknown capability 0x756e670000000f41 = 0x104000000070100, stripped

boincadm@boinc-build-android:~/boinc/android/BOINC/assets/mips64$ file boinccmd

boinccmd: ELF 64-bit LSB shared object, MIPS, version 1 (SYSV), dynamically linked (uses shared libs), with unknown capability 0x756e670000000f41 = 0x104000000070100, stripped

 

 

 

From: Jord van der Elst
Sent: Monday, July 4, 2016 10:15 AM
To: Rom Walton
Cc: Boinc Projects; boinc-andr...@googlegroups.com
Subject: Re: [boinc_projects] platform string for Linux on ARM

 

This same user installed 7.4.53 on two ARM devices and there it runs fine. He just can't get past the BOINC title screen on .53 on his Intel Atom.

Jord van der Elst

unread,
Jul 8, 2016, 7:34:15 AM7/8/16
to Rom Walton, Boinc Projects, boinc-andr...@googlegroups.com
Hi Rom,

This fix didn't do it for this device: https://setiathome.berkeley.edu/show_host_detail.php?hostid=8038962
It's still got no CPU detected at all. Just an empty string and that there are 8 cores/CPUs. That is with 7.4.53

Another report at https://boinc.berkeley.edu/dev/forum_thread.php?id=11082 says that now projects show up in the Add Project listing that do not have ARM/x86 for Android applications at all, like CPDN, Milkyway, primaboinca etc. I see the same thing on my Android (ARM v7) device.

My listing which you can compare against http://boinc.berkeley.edu/projects.php to see if they have Android apps, which a lot of them do not, at all:
Radioactive@Home
CAS@home
Yoyo@home
Citizen Science Grid
World Community Grid
Ibercivis
Climateprediction.net
Mindmodeling@Home
Primegrid
NFS@home
Enigma@home
SAT@home
SRBase
Collatz Conjecture
Gerasim@home
SZTAKI Desktop Grid
Numberfields@home
Moo! Wrapper
primaboinca
Constellation
Milkyway@home
Universe@home
LHC@home
Asteroids@Home
ATLAS@Home
Cosmology@Home
Einstein@Home
Leiden Classical
vLHCathome
theSkyNet POGS
DENIS@home
Malariacontrol.net
The Lattice Project
Rosetta@Home
GPUGrid.net
POEM@Home
RNA World
FiND@Home


-- Jord van der Elst

Jord van der Elst

unread,
Sep 7, 2016, 4:42:26 PM9/7/16
to Rom Walton, Boinc Projects, boinc-andr...@googlegroups.com
Pushing this one back into view.
Thread at Seti with plenty of people with non-working BOINC: https://setiathome.berkeley.edu/forum_thread.php?id=79858
Can we get a new version out with fixes, please? Or is development for Android at the moment at total standstill?

Thanks,


-- Jord van der Elst.

David Anderson

unread,
Sep 7, 2016, 5:08:40 PM9/7/16
to boinc-andr...@googlegroups.com
Dev/maintenance for Android is at a total standstill, unfortunately.
Rom, is that true?
Anything we can do to recruit some help?
--
You received this message because you are subscribed to the Google Groups "BOINC Android Testing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to boinc-android-te...@googlegroups.com.
To post to this group, send email to boinc-andr...@googlegroups.com.
Visit this group at https://groups.google.com/group/boinc-android-testing.
Reply all
Reply to author
Forward
0 new messages