Message boards :
Number crunching :
Nexus 5X: Android tasks fail immediately
Message board moderation
Author | Message |
---|---|
Rob Send message Joined: 7 Apr 12 Posts: 9 Credit: 951,019 RAC: 0 |
Hello, I've been on SETI@Home on and off for quite some time, but recently I thought I'd let my Google Nexus 5X help a bit and noticed the workunits it received immediately failed. Example task <core_client_version>7.4.43</core_client_version> I thought perhaps it was an issue with Android 7.0 or the hardware, but I couldn't find any specific informatin, so I thought I'd post it in case that's unintended. Perhaps something is wrong on my end...? |
JLDun Send message Joined: 21 Apr 06 Posts: 573 Credit: 196,101 RAC: 0 |
First thing I can think of is the CPU type: "ARM AArch64". The apps were built for "ARM" or "x86"; yours may be different enough.... |
Rob Send message Joined: 7 Apr 12 Posts: 9 Credit: 951,019 RAC: 0 |
Thank you - I hadn't really considered that before. I would've suspected not to receive any workounits if the hardware was incompatible, but perhaps that's not accurate. |
Juha Send message Joined: 7 Mar 04 Posts: 388 Credit: 1,857,738 RAC: 0 |
I don't think it's the CPU that's the problem. ARM's 64-bit processors should be able to run 32-bit code just fine. It's more likely there's something wrong in the science app. There are some Android 6 devices that can run the app but then there's others that can't. |
HAL9000 Send message Joined: 11 Sep 99 Posts: 6534 Credit: 196,805,888 RAC: 57 |
I seem to recall that error would occur when BOINC was run from an SD Card, but I don't believe that any version of BOINC supports being installed that way. SETI@home classic workunits: 93,865 CPU time: 863,447 hours Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[ |
JLDun Send message Joined: 21 Apr 06 Posts: 573 Credit: 196,101 RAC: 0 |
NativeBOINC? |
Juha Send message Joined: 7 Mar 04 Posts: 388 Credit: 1,857,738 RAC: 0 |
Since Android 6, it only runs code compiled as Position Independent Code (or Position Independent Executable=pie). This is a security measure, PIEs can be loaded to randomised memory addresses which makes it harder to exploit any bugs. I seem to recall that error would occur when BOINC was run from an SD Card, but I don't believe that any version of BOINC supports being installed that way. The message about text relocations means that the code was not compiled as PIC (text=code). It's starting to look like Eric has mixed plain (pie) and nopie app versions. |
Rob Send message Joined: 7 Apr 12 Posts: 9 Credit: 951,019 RAC: 0 |
First, I'd like to thank for the replies. I really appreciate it. :) @JLDun: No, I'm using the "BOINC" titled app, which seems to be the official one...? Should I try NativeBoinc instead? @HAL9000: The Nexus 5X doesn't have an SD slot where I could connect an additional SD card, so I don't think this could be the problem (in this case). @Juha: The SETI app list names a "normal" and a "-nopie" version for every Android app. It seems like my phone receives the default(?) / with-pie apps, though, at least judging from the app names connected with the returned, and failed, tasks.
Could the issue be that I have an older version of BOINC installed? I originally installed the 7.4.53 version but I could not get any work (neither Einstein, nor SETI) before manually reverting to 7.4.43. Einstein worked fine, though. When I use the most recent version(s), I seem to run into the same issue as the people in this thread. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Worth to bring Eric's attention to issue. SETI apps news We're not gonna fight them. We're gonna transcend them. |
JLDun Send message Joined: 21 Apr 06 Posts: 573 Credit: 196,101 RAC: 0 |
NativeBOINC won't work in this case. (I've gathered development stopped before PIE became a big thing, which means pre-KitKat.) As to .43 vs .53, might influence it. I have several (non-64) ARM that can use .53, and an Android x86_64 that's currently 'stuck' with .43. |
Wales_Family Send message Joined: 5 Sep 11 Posts: 9 Credit: 3,181,278 RAC: 8 |
I've migrated to a Nexus 5x running Android 7 this weekend, and have a similar issue. With a new installation of BOINC, I could see the first tasks downloading - but they never showed up in the list of tasks. |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
Eric aware of issue. He said rebuild with latest Anbdroid SDK required. Also he is looking for providing x64 Android build. So sign up for beta if don't already - new builds appear there first. SETI apps news We're not gonna fight them. We're gonna transcend them. |
Wales_Family Send message Joined: 5 Sep 11 Posts: 9 Credit: 3,181,278 RAC: 8 |
Update: My Nexus 5x started correctly processing just before New Year's eve (circa 29-12-2016). |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
NativeBOINC? Wasn't able to run NativeBOINc on Android 4 Samsung Galaxy J1 mini. It can't connect to daemon. Both available versions (5.x.x and 4.x.x) Had to install stock BOINC instead :/ SETI apps news We're not gonna fight them. We're gonna transcend them. |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.