I recently updated my old Nexus 7 to Android 5.0. After the update the BOINC client hangs at the 'BOINC' splash screen.

Relevant Info:
Tablet Model: ME370T
Android Version: 5.0
BOINC Client Version: 7.4.14

Obviously this is a pretty bleeding edge problem that doesn't affect many yet. I just wanted to make sure it was a known issue.

Thanks!

Same story on my Nexus 4.

I'm still on 4.3, but been having a lot of problems as well... Starting BOINC, the splash screen will sit seemingly forever--I never actually see it go away, but if I come back to the phone after a while it will be running with a "Nothing to do" message, and no tasks/projects, even though the Even Log lists the projects and account manager. However, if I click on the "GUI Messages" tab, I get multiple entries of the following:

11-17 20:49:21.964 E/BOINC_GUI(17556): readClientStatus(): connection problem, null: state,

If I force-quit the app and relaunch, I get the same thing. If I clear the cache, same. Clear all data, same. Uninstall and reinstall, same.

To be honest, I can't really say when this behavior started... Here's a summary of recent WUs from WUprop, which should always have an active task: http://wuprop.boinc-af.org/results.php?hostid=73794

---

My Detailed BOINC Stats

Nexus 7: same model ... same Problem.
Addition: Build-Number LRX21P

My Nexus 10 is having the same issue since upgrading to Lolipop. Boinc worked fine before the new Droid 5.0 upgrade. I have two other devices that I plan on holding off upgrading until we are able to resolve this. The Nexus 10 just happened to be the first machine to get the OTA update.

Has anyone OTA updated their droid to 5.0 and still had BOINC functional afterwards? I'm wondering if it didnt change a setting behind the scenes. I am going to try uninstalling & reinstalling BOINC and see if I can notice anything amiss tonight.

I have a 2012 Nexus 7 and a Nexus 5 that havent been updated yet and both run BOINC fine.

Hello Folks.
I am thinking it is perhaps a rights issue at this point. I was able to capture a log from Boinc on the Nexus 10 and have attached a small part of it:

11-18 20:48:24.995 E/BOINC_GUI( 2233): connection failed!
11-18 20:48:24.995 W/BOINC_GUI( 2233): at java.util.Timer$TimerImpl.run(Timer.java:284)
11-18 20:48:24.995 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor$StatusUpdateTimerTask.run(Monitor.java:319)
11-18 20:48:24.995 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.access$5(Monitor.java:328)
11-18 20:48:24.995 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.updateStatus(Monitor.java:331)
11-18 20:48:24.995 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.clientSetup(Monitor.java:518)
11-18 20:48:24.995 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.connectClient(Monitor.java:585)
11-18 20:48:24.995 W/BOINC_GUI( 2233): at edu.berkeley.boinc.rpc.RpcClient.open(RpcClient.java:173)
11-18 20:48:24.995 W/BOINC_GUI( 2233): at android.net.LocalSocket.connect(LocalSocket.java:130)
11-18 20:48:24.995 W/BOINC_GUI( 2233): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:290)
11-18 20:48:24.995 W/BOINC_GUI( 2233): at android.net.LocalSocketImpl.connectLocal(Native Method)
11-18 20:48:24.995 W/BOINC_GUI( 2233): java.io.IOException: Connection refused
11-18 20:48:24.995 W/BOINC_GUI( 2233): connect failure
11-18 20:48:23.992 E/BOINC_GUI( 2233): connection failed!
11-18 20:48:23.992 W/BOINC_GUI( 2233): at java.util.Timer$TimerImpl.run(Timer.java:284)
11-18 20:48:23.992 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor$StatusUpdateTimerTask.run(Monitor.java:319)
11-18 20:48:23.992 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.access$5(Monitor.java:328)
11-18 20:48:23.992 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.updateStatus(Monitor.java:331)
11-18 20:48:23.992 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.clientSetup(Monitor.java:518)
11-18 20:48:23.992 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.connectClient(Monitor.java:585)
11-18 20:48:23.992 W/BOINC_GUI( 2233): at edu.berkeley.boinc.rpc.RpcClient.open(RpcClient.java:173)
11-18 20:48:23.992 W/BOINC_GUI( 2233): at android.net.LocalSocket.connect(LocalSocket.java:130)
11-18 20:48:23.992 W/BOINC_GUI( 2233): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:290)
11-18 20:48:23.992 W/BOINC_GUI( 2233): at android.net.LocalSocketImpl.connectLocal(Native Method)
11-18 20:48:23.992 W/BOINC_GUI( 2233): java.io.IOException: Connection refused
11-18 20:48:23.992 W/BOINC_GUI( 2233): connect failure
11-18 20:48:22.991 E/BOINC_GUI( 2233): connection failed!
11-18 20:48:22.991 W/BOINC_GUI( 2233): at java.util.Timer$TimerImpl.run(Timer.java:284)
11-18 20:48:22.991 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor$StatusUpdateTimerTask.run(Monitor.java:319)
11-18 20:48:22.991 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.access$5(Monitor.java:328)
11-18 20:48:22.991 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.updateStatus(Monitor.java:331)
11-18 20:48:22.991 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.clientSetup(Monitor.java:518)
11-18 20:48:22.991 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.connectClient(Monitor.java:585)
11-18 20:48:22.991 W/BOINC_GUI( 2233): at edu.berkeley.boinc.rpc.RpcClient.open(RpcClient.java:173)
11-18 20:48:22.991 W/BOINC_GUI( 2233): at android.net.LocalSocket.connect(LocalSocket.java:130)
11-18 20:48:22.991 W/BOINC_GUI( 2233): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:290)
11-18 20:48:22.991 W/BOINC_GUI( 2233): at android.net.LocalSocketImpl.connectLocal(Native Method)
11-18 20:48:22.991 W/BOINC_GUI( 2233): java.io.IOException: Connection refused
11-18 20:48:22.991 W/BOINC_GUI( 2233): connect failure
11-18 20:48:21.990 E/BOINC_GUI( 2233): connection failed!
11-18 20:48:21.990 W/BOINC_GUI( 2233): at java.util.Timer$TimerImpl.run(Timer.java:284)
11-18 20:48:21.990 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor$StatusUpdateTimerTask.run(Monitor.java:319)
11-18 20:48:21.990 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.access$5(Monitor.java:328)
11-18 20:48:21.990 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.updateStatus(Monitor.java:331)
11-18 20:48:21.990 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.clientSetup(Monitor.java:518)
11-18 20:48:21.990 W/BOINC_GUI( 2233): at edu.berkeley.boinc.client.Monitor.connectClient(Monitor.java:585)
11-18 20:48:21.990 W/BOINC_GUI( 2233): at edu.berkeley.boinc.rpc.RpcClient.open(RpcClient.java:173)
11-18 20:48:21.990 W/BOINC_GUI( 2233): at android.net.LocalSocket.connect(LocalSocket.java:130)
11-18 20:48:21.990 W/BOINC_GUI( 2233): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:290)
11-18 20:48:21.990 W/BOINC_GUI( 2233): at android.net.LocalSocketImpl.connectLocal(Native Method)
11-18 20:48:21.990 W/BOINC_GUI( 2233): java.io.IOException: Connection refused

I would like to add my Nexus 5 to the list of not working after upgrading to Android 5. Also stuck at the flash screen.

App will not go beyond the splash screen for me either after upgrading to Android 5/Lollipop.

BOINC 7.4.14
Nexus 7 (model ME370T, build number LRX21P)

Additional details were posted by lavaflow in this thread https://secure.worldcommunitygrid.org/forums/wcg/viewthread_thread,37432

Something is happening as of last night, indicating that both boinc and the science app for fahv have to be recompiled.

On Wednesday, November 19, 2014 7:04:57 PM UTC-5, davea wrote:

We've identified the problem: starting with 5.0,
Android will run only position-independent executables (PIE),
and the current BOINC client (and all existing science apps)
are not position-independent.

Support for PIE was added in Android 4.1.
So if all the native-mode stuff (BOINC client and apps) are recompiled as PIE,
everything will work on 4.1 and later devices, but will fail on pre-4.1.
Currently around 10% of the active Android devices (2500 out of 27000) are pre-4.1.

What we'll do is:

- make a PIE version of the BOINC client
- encourage projects to build PIE versions of their apps
- tell projects how to ensure that their PIE apps get sent
only to 4.1+ clients,
and (if they want to maintain their non-PIE apps) that these
get sent only to pre-5.0 clients.

All this will take a week or two, maybe more.

-- David

First code check-ins to make the next boinc for android lollipop ready

android: Set the minSdkVersion to 16 (Android 4.1) and add the position-independent...
commit | commitdiff | tree
Rom Walton [Thu, 20 Nov 2014 00:34:54 +0000]
android: Set the minSdkVersion to 16 (Android 4.1) and add the position-independent-executable flags for native code build scripts.

21 hours agoandroid: Properly report the android version to the core client so it can bubble...
commit | commitdiff | tree
Rom Walton [Thu, 20 Nov 2014 00:05:41 +0000]
android: Properly report the android version to the core client so it can bubble it up to the server

@technicians, are you planning to make a move on this for the fahv app?

---

boinc worked on my Nexus 4 after the Lollipop upgrade, but on my new Nexus 6 it just spins it's wheels trying to connect to the server, and there is no way to link it to grid Republic

It is known to the developers.
They're presently testing a version that works with Android 5.0 in the Google test group. Patience please, when it's found to be sturdy enough it'll find its way to an Android device near you (Android 4.1 and better only).

---

Any update? BOINC not working on my Nexus 5 since updating to Android Lollipop. Thanks.

At some point, Google introduced the notion of "position-independent executable" (PIE) native-mode programs: http://stackoverflow.com/questions/24818902/

Support for PIE programs was added in Android 4.1.
Starting with Android 5.0 (which is now shipping on some devices) native-mode applications *must* be PIE. This means that all current Android apps will fail on Android 5.0.

BOINC 7.4.37 available from the Google Play Store does not contain the PIE fixes since projects are still getting ready for that. Only until the projects have added science applications that can actually run under the new BOINC will that version be promoted to the public.

---

Me too. Nexus 6

I take it things will remain this way for the future? Google has 5.0.2 available for the Nexus 7 but if I can't run Boinc there is no reason to update. In fact I am considering reflashing my Nexus 5 with KitKat to get Boinc running again. Lollipop seems to have memory issues that pop up from time to time for me.

Bump, any update?

Bump, any update?

Boinc 7.4.41 was tagged almost two weeks ago.

Claggy

Me too. Samsung Galaxy S5

The 7.4.41.apk was built on 22 January, but I'm not familiar with Android distribution channels.

The 7.4.41.apk was built on 22 January, but I'm not familiar with Android distribution channels.

It should be in the Google Play app store, and other apps stores.

It shows up here as:

What's New

New to 7.4.41:

* Add support for Android 5.0.

But I'm attached to the 'BOINC Android Testing' Google Group, so I get the most recent build, regular users get whatever Rom has released to them.

Looks as if they get 7.4.39, But only if they are running an Android lower than 5.0:

What's New

New to 7.4.39:

* Prevents the PlayStore from advertising BOINC on Android 5.0.

7.4.40+ should be Android 5.0 compatible.

The other alternative is to just monitor the download directory:

http://boinc.berkeley.edu/dl/

But you'll need to know what the changes are to a particular version, so you get the right version.

Claggy