Message boards :
Number crunching :
Errors on android, all tasks
Message board moderation
Author | Message |
---|---|
Penguin Send message Joined: 5 Sep 14 Posts: 13 Credit: 16,544,489 RAC: 360 |
Every task I've gotten on my Android device has gotten a computation error. Working fine for World Community Grid and Asteroids and Universe but not for SETI. Any ideas? http://setiathome.berkeley.edu/results.php?hostid=8583782 |
tullio Send message Joined: 9 Apr 04 Posts: 8797 Credit: 2,930,782 RAC: 1 |
It works on 801 tasks on my Ulefone with Android 7.1.1 SETI@home v8 8.01 aarch-android-linux-gnu Tullio |
Penguin Send message Joined: 5 Sep 14 Posts: 13 Credit: 16,544,489 RAC: 360 |
It works on 801 tasks on my Ulefone with Android 7.1.1 Yes, I see that in your computer list... I dunno why SETI won't run when other projects will on my Android phone... I am fairly sure I have all the updates but I will double check those now. I only have 4 ARM processors not AArch64 Processor rev 4 (aarch64) (8 processors) as you have on your device... my OS is currently as listed in the computer details - Android 3.18.31-perf-g0200b58 (Android 7.0) http://setiathome.berkeley.edu/show_host_detail.php?hostid=8583782 SETI works on like nearly anything I throw at it even an old 32bit netbook |
tullio Send message Joined: 9 Apr 04 Posts: 8797 Credit: 2,930,782 RAC: 1 |
My Android is 4.4.22+ The funny thing is that the SETI server sees also an on board GPU OpenCL GPU Mali-671 (4096 MB) driver 1.02 which is not used by SETI. The Einstein@home server does not see it. Tullio |
Mr. Kevvy Send message Joined: 15 May 99 Posts: 3776 Credit: 1,114,826,392 RAC: 3,319 |
This thread may be useful... SETI@Home may not work with some Android 7 or higher devices. For some, letting tasks error out may eventually lead to tasks that work (slowly) but not always. |
Penguin Send message Joined: 5 Sep 14 Posts: 13 Credit: 16,544,489 RAC: 360 |
This thread may be useful... SETI@Home may not work with some Android 7 or higher devices. For some, letting tasks error out may eventually lead to tasks that work (slowly) but not always. Yes good thread. Good info there. So I will now let it keep getting SETI@home tasks and see if it decides to use a different version like 8.01 instead. I didn't want to error out on a zillion tasks but it seems this is necessary so it knows it can't use that app version. Will know in a few days. |
tullio Send message Joined: 9 Apr 04 Posts: 8797 Credit: 2,930,782 RAC: 1 |
My 8 cores ARM64 has also an on board GPU. I wish somebody could write a SETI@home app that uses it. Tullio |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
I wish somebody could write a SETI@home app that uses it.Writing isn't necessary. Just have someone port the OpenCL application to be able to use the Mali GPUs. They're already detected. And as far as I know, the base program for the Intel, Nvidia and AMD OpenCL apps are one and the same (although these are probably optimized for specific brand GPUs). So it just needs porting to Android. Where you then probably have to problem that the API doesn't allow for using of the GPU, just as it now doesn't allow for using all foreground and background CPUs at the same time, without especially disabling the code that sets that. |
tullio Send message Joined: 9 Apr 04 Posts: 8797 Credit: 2,930,782 RAC: 1 |
There is a recent "|Nature" article which says that scientists are discovering the use of GPU boards to speed scientific computing. It cites the example of the Summit supercomputer, number 1 on the top500 list with its 27000 GPU boards by nVidia. I think we at BOINC have been a kind of pioneers of this trend. I am using GPU boards in Einstein, SETI and GPUGRID. Tullio |
Tom M Send message Joined: 28 Nov 02 Posts: 5124 Credit: 276,046,078 RAC: 462 |
This thread may be useful... SETI@Home may not work with some Android 7 or higher devices. For some, letting tasks error out may eventually lead to tasks that work (slowly) but not always. I ended up buying an older phone to process Seti. (It doesn't have a phone #). Tom A proud member of the OFA (Old Farts Association). |
Penguin Send message Joined: 5 Sep 14 Posts: 13 Credit: 16,544,489 RAC: 360 |
This thread may be useful... SETI@Home may not work with some Android 7 or higher devices. For some, letting tasks error out may eventually lead to tasks that work (slowly) but not always. now that's a cool idea. works through the Wi-Fi is my guess. Great idea. But I would still like to get it working on my newer device. |
Penguin Send message Joined: 5 Sep 14 Posts: 13 Credit: 16,544,489 RAC: 360 |
Up to 112 errors as of this post. Still no new app being used like 8.01. |
tullio Send message Joined: 9 Apr 04 Posts: 8797 Credit: 2,930,782 RAC: 1 |
I am getting no more SETI@home tasks on my Android 7.1.1, only Einstein@home. Tullio |
Raistmer Send message Joined: 16 Jun 01 Posts: 6325 Credit: 106,370,077 RAC: 121 |
just as it now doesn't allow for using all foreground and background CPUs at the same time, without especially disabling the code that sets that. So, finally, number of CPUs in device became same advertizing hype as number of megapixels on shit-optics cameras or number of gigabytes of device memoty already filled with preinstalled crap. Free market, nothing honest, only money. Modern Android versions seems to actively resist to computaional load. On both my Digma phones (Android 6) I experience silent BOINC shut downs. They happen w/o any other phone activity. Device just cools down so I understand that computations stopped again. Sometime it can continue for hours or even days, sometimes it stops very shortly after relaunching. On relaunch BOINC says that "another instance detected" and refuses to start. Second attempt usually results in operational (for some time) BOINC client with working scientific (SETI) apps. SETI apps news We're not gonna fight them. We're gonna transcend them. |
tullio Send message Joined: 9 Apr 04 Posts: 8797 Credit: 2,930,782 RAC: 1 |
I am getting again SETI@home tasks on my Ulephone. They all complete and validate. Tullio |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Up to 112 errors as of this post. Still no new app being used like 8.01. v8.01 is a 64-bit application. Your ARMv7 CPU isn't 64-bit, it's a 32-bit CPU. So your CPU ought to be able to run the armv6_* and armv7_* applications, but there's not guarantee it can. Some Android devices just cannot run these tasks. I am running solely Android devices. My oldest phone, a Huawei G700 is coming up on its one year anniversary on the 17th and it still hasn't figured out which of the 12 applications is the fastest it can run with. It's got a 32bit CPU, Android 4.2.1, it runs the same applications your device is erring on, 24/7 all year round @ 2 KWh electricity a year. So you probably want to find a project you can run on that device, I saw it did manage to run Universe@Home. |
Penguin Send message Joined: 5 Sep 14 Posts: 13 Credit: 16,544,489 RAC: 360 |
Up to 112 errors as of this post. Still no new app being used like 8.01. Yeah I'm figuring SETI@home isn't an option for it. I've had it running Universe@home, World Community Grid, and Asteroids@home so I will stick with those for now. Was working on getting up to 2 million credits as my next goal, so I was running SETI@home on all my devices, losing one won't be devastating. |
©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.