It wasn't really a 'computation error' - the actual processing ran to completion with no sign of errors.

It was more of a 'housekeeping error', involving memory, disk, and the operating system. The sequence should be:

1. The SETI app writes a data file to disk for upload
2. The SETI app writes a 'finished' file to disk
3. The SETI app shuts down and removes itself from memory
[at which point, another SETI app will probably start up and load itself from disk to memory]
4. The BOINC client checks that both 2 and 3 have happened within 10 seconds

If it takes more than 10 seconds for that to happen, then the OS is thrashing. It might be memory paging as David suggests in his comment (in which case, more RAM might help). Or it might be the OS being too busy starting the next task (in which case, fewer concurrent operations requiring disk access might help). Or perhaps an SSD data disk.

Are the security certificates updated in your boinc client?

Or does your install of boinc use the system certificates?...

Or is the https being blocked by a firewall?

<master_url>http://setiathome.berkeley.edu/</master_url>

<scheduler_url>http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi</scheduler_url>

29/11/2018 09:59:42	SETI@home	Reporting 4 completed tasks, not requesting new tasks
29/11/2018 09:59:42			[http_debug] HTTP_OP::init_post(): http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
29/11/2018 09:59:42			[http_debug] HTTP_OP::libcurl_exec(): ca-bundle set
29/11/2018 09:59:42			[http_debug] HTTP_OP::init_get(): http://boinc.berkeley.edu/download.php?xml=1
29/11/2018 09:59:42			[http_debug] HTTP_OP::libcurl_exec(): ca-bundle set
29/11/2018 09:59:42			[http_debug] [ID#0] info: timeout on name lookup is not supported
29/11/2018 09:59:42			[http_debug] [ID#0] info: About to connect() to setiboinc.ssl.berkeley.edu port 80 (#1)
29/11/2018 09:59:42			[http_debug] [ID#0] info:   Trying 208.68.240.126... 
29/11/2018 09:59:42			[http_debug] [ID#1] info: timeout on name lookup is not supported
29/11/2018 09:59:42			[http_debug] [ID#1] info: About to connect() to boinc.berkeley.edu port 80 (#2)
29/11/2018 09:59:42			[http_debug] [ID#1] info:   Trying 208.68.240.115... 
29/11/2018 09:59:42			[http_debug] [ID#0] info: Connected to setiboinc.ssl.berkeley.edu (208.68.240.126) port 80 (#1)
29/11/2018 09:59:42			[http_debug] [ID#0] Sent header to server: POST /sah_cgi/cgi HTTP/1.1
					User-Agent: BOINC client (windows_x86_64 6.10.18)
					Host: setiboinc.ssl.berkeley.edu
					Accept: */*
					Accept-Encoding: deflate, gzip
					Content-Type: application/x-www-form-urlencoded
					Content-Length: 26878
					Expect: 100-continue
29/11/2018 09:59:42			[http_debug] [ID#0] info: Expire cleared
29/11/2018 09:59:42			[http_debug] [ID#1] info: Connected to boinc.berkeley.edu (208.68.240.115) port 80 (#2)
29/11/2018 09:59:42			[http_debug] [ID#1] Sent header to server: GET /download.php?xml=1 HTTP/1.1
					User-Agent: BOINC client (windows_x86_64 6.10.18)
					Host: boinc.berkeley.edu
					Accept: */*
					Accept-Encoding: deflate, gzip
					Content-Type: application/x-www-form-urlencoded
29/11/2018 09:59:43			[http_debug] [ID#0] Received header from server: HTTP/1.1 100 Continue
29/11/2018 09:59:43			[http_debug] [ID#1] Received header from server: HTTP/1.1 301 Moved Permanently
29/11/2018 09:59:43			[http_debug] [ID#1] Received header from server: Date: Thu, 29 Nov 2018 08:59:42 GMT
29/11/2018 09:59:43			[http_debug] [ID#1] Received header from server: Server: Apache/2.2.15 (Scientific Linux)
29/11/2018 09:59:43			[http_debug] [ID#1] Received header from server: Location: https://boinc.berkeley.edu/download.php?xml=1
29/11/2018 09:59:43			[http_debug] [ID#1] Received header from server: Content-Length: 347
29/11/2018 09:59:43			[http_debug] [ID#1] Received header from server: Connection: close
29/11/2018 09:59:43			[http_debug] [ID#1] Received header from server: Content-Type: text/html; charset=iso-8859-1
29/11/2018 09:59:43			[http_debug] [ID#1] Received header from server: 
29/11/2018 09:59:43			[http_debug] [ID#1] info: Expire cleared
29/11/2018 09:59:43			[http_debug] [ID#1] info: Closing connection #2
29/11/2018 09:59:43			[http_debug] [ID#1] info: Issue another request to this URL: 'https://boinc.berkeley.edu/download.php?xml=1'
29/11/2018 09:59:43			[http_debug] [ID#1] info: timeout on name lookup is not supported
29/11/2018 09:59:43			[http_debug] [ID#1] info: About to connect() to boinc.berkeley.edu port 443 (#2)
29/11/2018 09:59:43			[http_debug] [ID#1] info:   Trying 208.68.240.115... 
29/11/2018 09:59:43			[http_debug] [ID#1] info: Connected to boinc.berkeley.edu (208.68.240.115) port 443 (#2)
29/11/2018 09:59:43			[http_debug] [ID#1] info: successfully set certificate verify locations:
29/11/2018 09:59:43			[http_debug] [ID#1] info:   CAfile: C:\Program Files\BOINC\ca-bundle.crt  CApath: none
29/11/2018 09:59:43			[http_debug] [ID#1] info: SSLv3, TLS handshake, Client hello (1):
29/11/2018 09:59:43			[http_debug] [ID#0] Received header from server: HTTP/1.1 200 OK
29/11/2018 09:59:43			[http_debug] [ID#0] Received header from server: Date: Thu, 29 Nov 2018 08:59:42 GMT
29/11/2018 09:59:43			[http_debug] [ID#0] Received header from server: Server: Apache/2.2.15 (Scientific Linux)
29/11/2018 09:59:43			[http_debug] [ID#0] Received header from server: Connection: close
29/11/2018 09:59:43			[http_debug] [ID#0] Received header from server: Transfer-Encoding: chunked
29/11/2018 09:59:43			[http_debug] [ID#0] Received header from server: Content-Type: text/xml
29/11/2018 09:59:43			[http_debug] [ID#0] Received header from server: 
29/11/2018 09:59:43			[http_debug] [ID#0] info: Expire cleared
29/11/2018 09:59:43			[http_debug] [ID#0] info: Closing connection #1
29/11/2018 09:59:43			[http_debug] [ID#1] info: SSLv3, TLS handshake, Server hello (2):
29/11/2018 09:59:43			[http_debug] [ID#1] info: SSLv3, TLS handshake, CERT (11):
29/11/2018 09:59:43			[http_debug] [ID#1] info: SSLv3, TLS alert, Server hello (2):
29/11/2018 09:59:43			[http_debug] [ID#1] info: error:0D0C50A1:asn1 encoding routines:ASN1_item_verify:unknown message digest algorithm
29/11/2018 09:59:43			[http_debug] [ID#1] info: Expire cleared
29/11/2018 09:59:43			[http_debug] [ID#1] info: Closing connection #2
29/11/2018 09:59:43			[http_debug] HTTP error: SSL connect error
29/11/2018 09:59:44			Project communication failed: attempting access to reference site
29/11/2018 09:59:44			[http_debug] HTTP_OP::init_get(): http://www.google.com/
29/11/2018 09:59:44			[http_debug] HTTP_OP::libcurl_exec(): ca-bundle set
29/11/2018 09:59:44			[http_debug] [ID#2] info: Connection #0 seems to be dead!
29/11/2018 09:59:44			[http_debug] [ID#2] info: Closing connection #0
29/11/2018 09:59:44			[http_debug] [ID#2] info: timeout on name lookup is not supported
29/11/2018 09:59:44			[http_debug] [ID#2] info: About to connect() to www.google.com port 80 (#0)
29/11/2018 09:59:44			[http_debug] [ID#2] info:   Trying 216.58.207.228... 
29/11/2018 09:59:44			[http_debug] [ID#2] info: Connected to www.google.com (216.58.207.228) port 80 (#0)
29/11/2018 09:59:44			[http_debug] [ID#2] Sent header to server: GET / HTTP/1.1
					User-Agent: BOINC client (windows_x86_64 6.10.18)
					Host: www.google.com
					Accept: */*
					Accept-Encoding: deflate, gzip
					Content-Type: application/x-www-form-urlencoded
29/11/2018 09:59:44			[http_debug] [ID#2] Received header from server: HTTP/1.1 200 OK
29/11/2018 09:59:44			[http_debug] [ID#2] Received header from server: Date: Thu, 29 Nov 2018 08:59:43 GMT
29/11/2018 09:59:44			[http_debug] [ID#2] Received header from server: Expires: -1
29/11/2018 09:59:44			[http_debug] [ID#2] Received header from server: Cache-Control: private, max-age=0
29/11/2018 09:59:44			[http_debug] [ID#2] Received header from server: Content-Type: text/html; charset=ISO-8859-1
29/11/2018 09:59:44			[http_debug] [ID#2] Received header from server: P3P: CP="This is not a P3P policy! See g.co/p3phelp for more info."
29/11/2018 09:59:44			[http_debug] [ID#2] Received header from server: Content-Encoding: gzip
29/11/2018 09:59:44			[http_debug] [ID#2] Received header from server: Server: gws
29/11/2018 09:59:44			[http_debug] [ID#2] Received header from server: Content-Length: 5254
29/11/2018 09:59:44			[http_debug] [ID#2] Received header from server: X-XSS-Protection: 1; mode=block
29/11/2018 09:59:44			[http_debug] [ID#2] Received header from server: X-Frame-Options: SAMEORIGIN
29/11/2018 09:59:44			[http_debug] [ID#2] Received header from server: Set-Cookie: 1P_JAR=2018-11-29-08; expires=Sat, 29-Dec-2018 08:59:43 GMT; path=/; domain=.google.com
29/11/2018 09:59:44			[http_debug] [ID#2] Received header from server: Set-Cookie: NID=148=KbgYurj5D3yWqZxGYBRCgLwafDv6VrfDcrWx2Zt6MKVXphNgNo3BEFk5LfALm-tXd3st5IC8tmOIEDKjE3asItE_Jmp9BC1G0bnauhk8i0SPeXdwh50TGOLp3S1oG9AvYPzdsOPTszkEiXDSZ6wFZqV02SBOkxlQcKM2n4cQjhM; expires=Fri, 
29/11/2018 09:59:44			[http_debug] [ID#2] Received header from server: 
29/11/2018 09:59:44			[http_debug] [ID#2] info: Expire cleared
29/11/2018 09:59:44			[http_debug] [ID#2] info: Connection #0 to host www.google.com left intact
29/11/2018 09:59:45			Internet access OK - project servers may be temporarily down.
29/11/2018 09:59:47	SETI@home	Scheduler request completed

I don't see why someone would want to do only 1/3 or 1/4 of what he can actually do for the project.

I estimate we have from hundreds to thousands of times greater of a chance finding ETI in a GBT work unit than an Arecibo one, because it is targeted to stars that are nearby, known to have exoplanets, and known (or thought) to have them in favourable positions for life (as we know it, Jim.)

It comes down to quality over quantity. And it's rather sadly ironic that the people who have contributed to this project the most over the years in terms of work done and time/money/effort invested in doing so are now mostly excluded from its most anticipated and promising venture.

Efficient is to send a task to a processing unit, which can process it fastest compared to other type of work on the same PU. Sending a VLAR to a GPU, which could crunch 3-4 mid-AR tasks (according to message 1779961) in the same time is waisting of ressources, since a CPU does the VLAR in nearly same time as a mid-AR WU.

Again, this is only correct for CUDA. The VLAR issue does not affect OpenCL so GUPPI work units would complete in about the same time. Most people are going to have both platforms available, as far as I know. All we ask for is to be able to make the decision to run them ourselves.

Since the core is going to get used anyway, why not use it the most efficient way to crunch those VLARS?

Posting those articles, even though it's a good thing about marketing, is a great misrepresentation of the "efficient donation of computational power"! Not to mention that it doesn't propagate some kind of program that regulates BOINC in accordance to temperature of the CPU & GPU (like Tthrottle for example)...

My HP laptop is crunching vLHC@home, Einstein@home searching for gravitational waves and SETI@home on Green Bank data. No smoke coming out of it.
Tullio

because of the app_info

You said it yourself.
Move it or delete it. Restart boinc.

if it's not rooted, delete SETI@home project and attach again, but this time entering URL manually as it would be unknown project.
This way you get stock binary.

Honestly I did not download NativeBOINC from Play, I downloaded it from Mateusz web site. And that version defaults to his app and anonymous platform in auto mode. That is, no user action required to get anonymous platform configured and best optimized app for Android to work. Device shouldn't be rooted for that. Is Play version different?

08ja11af.25606.9883.3.12.54.vlar_0 has completed and validated. 52,287 secs runtime and 21,318 cpu time.