Android app release: feedback thread

Forums › Problems and Bug Reports

Oliver Behnke
Oliver Behnke
Moderator
Administrator
Joined: 4 Sep 07
Posts: 982
Credit: 25170813
RAC: 0

Hi! You're running a number

4 Oct 2024 9:55:00 UTC
Message 228723
(moderation:
    )

    Hi! You're running a number of Android devices. Which one is the affected S24? 13108550? That's the only one I find with errors, but that one gets identified as a SM-G996U, which is a Galaxy S21+ (ARMv8). OTOH, the CPU type hints at a Cortex-A520 (ARMv9.2-A) which matches the one used in the S24+ in North America...

    If the latter is correct, then despite ARMv9 having optional 32 bit userspace support, the Cortex-A520 only supports 64 bit. Our apps are currently all still 32 bit, so that would explain it. We can try to build and deploy a beta app for 64, but we don't currently have suitable hardware to actually test things properly. YMMV.

    Also, it's rather curious that BOINC requests work for your device at all as we don't advertise aarch64-android-linux-gnu as a supported platform. I presume that BOINC just falls back to arm-android-linux-gnu and/or can't distinguish between aarch64-only (>= ARMv9) and aarch64/aarch32-combined (< ARMv9). I opened a bug report with BOINC to look into that as well.

    Thanks

    Einstein@Home Project

    ahorek's team
    ahorek's team
    Joined: 16 Dec 05
    Posts: 18
    Credit: 249159803
    RAC: 6736

    Hey, I encountered the same

    11 Oct 2024 14:40:17 UTC
    Message 228961 in response to message 228723
    (moderation:
      )

      Hey,
      I encountered the same issue with the Asteroids app on my S24, and rebuilding it for the aarch64-android-linux-gnu platform using the Android NDK (https://dl.google.com/android/repository/android-ndk-r26c-linux.zip) resolved the problem. I can try building and testing the BRP app next week if you'd like.

      Oliver Behnke
      Oliver Behnke
      Moderator
      Administrator
      Joined: 4 Sep 07
      Posts: 982
      Credit: 25170813
      RAC: 0

      I think there's already

      11 Oct 2024 15:12:44 UTC
      Message 228963
      (moderation:
        )

        I think there's already evidence for this and eventually it's up to us to provide an aarch64 version anyway. So thanks for the offer, but it might be a waste of your time at this point. We're going to provide a build, briefly tested locally (on different hardware), which we then publish as an official beta, as usual. I can't say when this is going to be since we're still understaffed right now, but I hope we'll manage next week.

        Thanks,
        Oliver

        Einstein@Home Project

        ahorek's team
        ahorek's team
        Joined: 16 Dec 05
        Posts: 18
        Credit: 249159803
        RAC: 6736

        thanks to Oliver Behnke &

        30 Oct 2024 15:46:25 UTC
        Message 229396
        (moderation:
          )

          thanks to Oliver Behnke & Bernd Machenschalk the new aarch64-android app (CPU, beta) has been released.
          https://einsteinathome.org/cs/task/1675224529
          we would appreciate feedback from other users, please give it a try.

           

          Oliver, when you're back, could you review the GPU app?
          Using OpenCL device "QUALCOMM Adreno(TM) 750" by: QUALCOMM
          https://einsteinathome.org/cs/task/1674449034

          the app itself works fine on an anonymous platform, but it's currently not recognized on the user's profile https://einsteinathome.org/cs/host/13173580
          while other projects can correctly recognize it Coprocessors: OpenCL GPU QUALCOMM Adreno(TM) 750 (5545MB) driver: 3.00

          also, a new option, something like "Use Mobile GPU: yes/no" could be useful to allow/disallow GPU work.

          Wedge009
          Wedge009
          Joined: 5 Mar 05
          Posts: 120
          Credit: 17261622626
          RAC: 7269194

          ahorek's team wrote:we would

          30 Oct 2024 22:05:07 UTC
          Message 229406 in response to message 229396
          (moderation:
            )

            ahorek's team wrote:
            we would appreciate feedback from other users, please give it a try.

            On this host, it consistently produced instantaneous errors. I had to disable beta applications to revert to v1.51.

            Example: https://einsteinathome.org/task/1675236772 (won't be available after the work-unit is dropped from the database)

            <core_client_version>8.0.4</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
CANNOT LINK EXECUTABLE "../../projects/einstein.phys.uwm.edu/einsteinbinary_BRP4_1.72_aarch64-android-linux-gnu__armv8a": cannot locate symbol "_Unwind_Resume" referenced by "/data/data/edu.berkeley.boinc/client/projects/einstein.phys.uwm.edu/einsteinbinary_BRP4_1.72_aarch64-android-linux-gnu__armv8a"...

            </stderr_txt>
            ]]>


            Soli Deo Gloria

            ahorek's team
            ahorek's team
            Joined: 16 Dec 05
            Posts: 18
            Credit: 249159803
            RAC: 6736

            thanks for your feedback, we

            31 Oct 2024 14:42:34 UTC
            Message 229433
            (moderation:
              )

              thanks for your feedback, we will try to lower the NDK_PLATFORM=29 version for older Android versions to see if it helps (likely next week).

              Wedge009
              Wedge009
              Joined: 5 Mar 05
              Posts: 120
              Credit: 17261622626
              RAC: 7269194

              I just started processing on

              1 Nov 2024 5:38:53 UTC
              Message 229450
              (moderation:
                )

                I just started processing on an Android 12 system a few days ago. I let it pick up a couple of the beta tasks and so far they seem to be running okay.

                I'm still leaving beta applications off until the issue with older Android is resolved.

                Soli Deo Gloria

                Link
                Link
                Joined: 15 Mar 20
                Posts: 121
                Credit: 9167872
                RAC: 47170

                Wedge009 wrote:I'm still

                2 Nov 2024 13:57:31 UTC
                Message 229495 in response to message 229450
                (moderation:
                  )

                  Wedge009 wrote:
                  I'm still leaving beta applications off until the issue with older Android is resolved.

                  If you move the two Androids to different venues, you can crunch with the beta application just on one of them.

                  .

                  Wedge009
                  Wedge009
                  Joined: 5 Mar 05
                  Posts: 120
                  Credit: 17261622626
                  RAC: 7269194

                  I'm well aware of that,

                  2 Nov 2024 20:57:38 UTC
                  Message 229505
                  (moderation:
                    )

                    I'm well aware of that, thanks.

                    Soli Deo Gloria

                    Bernd Machenschalk
                    Bernd Machenschalk
                    Moderator
                    Administrator
                    Joined: 15 Oct 04
                    Posts: 4308
                    Credit: 249840072
                    RAC: 32485

                    I built and published a new

                    7 Nov 2024 12:03:35 UTC
                    Message 229637
                    (moderation:
                      )

                      I built and published a new app version (1.73) with an older NDK_PLATFORM (29 as suggested). Beta test. Please give it a try.

                      BM

                      Comment viewing options

                      Select your preferred way to display the comments and click "Save settings" to activate your changes.

                      Forums › Problems and Bug Reports