Because Android 5 requires PIE support, the android app has been split into two plan classes, one for Android 4.1 and later (a new app), and another for earlier versions (the existing app). Please let me know if you run into any issues.

It will probably be tomorrow before my machine requests additional WUs -- it's in an "exceeded quota" state right now due to the failed WUs -- but I'll provide an update as soon as new WUs are processed.

I just returned 4 WUs on Android 4.4.2, but I'm not receiving any new tasks. Can't see why not - I've got Wifi, server's got WUs, there's enough room on the tablet, ...The log doesn't say anything useful. At least, for me to understand. I could send it over...

Which BOINC client app are you using on your Android device? I'm pretty sure you need to on 7.4.41 in order for it to work on Android 5. HTC's app should also work (on HTC devices anyway) but I don't know that it's been released yet.

My Android 4.4.2 device is running 7.4.41 and is getting the PIE app and completing the WUs OK.

Never mind. I see you are already on 7.4.41. The errors you are getting is because your device is not being identified as an Android 4.1 or later device. That could mean that there's a bug in the BOINC client or server when parsing the OS Version number.

PIE support only exists in Android 4.1 or later. Chances are that devices pre-4.1 can't run a mini_collatz WU in a reasonable amount of time, right? Therefore, disabling non-PIE support for mini_collatz should force all devices that are getting mini_collatz WUs to get the Android app with PIE support. I'll leave the micro_collatz set to run both PIE and non-PIE for now but if I can't find any Android 4.0 or earlier devices running Collatz, I may drop the non-PIE apps altogether.

I don't have access to my device right now but looking at the "All tasks for computer 140965" page I see that four (4) tasks were issued at 02:08:44 UTC today and all reported "Error while computing" failures at 02:23:38 UTC.

Collatz Conjecture 09-02-2015 13:27 Sending scheduler request: To fetch work.
Collatz Conjecture 09-02-2015 13:27 Requesting new tasks for CPU
Collatz Conjecture 09-02-2015 13:27 Scheduler request completed: got 0 new tasks
Collatz Conjecture 09-02-2015 13:27 No tasks sent
Collatz Conjecture 09-02-2015 13:27 No tasks are available for Mini Collatz Conjecture
Collatz Conjecture 09-02-2015 13:27 Tasks for NVIDIA GPU are available, but your preferences are set to not accept them
Collatz Conjecture 09-02-2015 13:27 Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
Collatz Conjecture 09-02-2015 13:27 Tasks for Intel GPU are available, but your preferences are set to not accept them

There is another strange behavior. Einstein@Home is running too in parallel without any problems. But when Collatz Conjecture starts, then Einstein@Home stops and complains "Waiting for shared memory". What the hell..???

BTW: I'm using Native-Boinc-App/Android since years without any problems (Collatz Conjecture, Einstein@Home and SETI@Home).

I changed the plan_class logic on the server. Some people are NOT using the latest BOINC version and that's a big problem. The plan_class logic assumes that the OS version (normally the kernel version) also reports the Android version. When it isn't reported, it can't determine whether to send the PIE or non-PIE app so it sends neither. At least, that's the way it used to work. I have now semi-randomly decided that if it is running kernel 3.4 or later (as my phone reports kernel 3.4 while running Android 4.4.2), it will get the PIE version. Anything less gets the non-PIE version.

Secondly, I recompiled the app just to make sure that the PIE compiler flags were present and re-deployed it as micro and mini collatz version 6.01.

So, if you could all give it a try, I'd appreciate it.I'm hoping that a) you will now get work and b) it will be the android_arm_pie plan class.

I changed the plan_class logic on the server. Some people are NOT using the latest BOINC version and that's a big problem. The plan_class logic assumes that the OS version (normally the kernel version) also reports the Android version. When it isn't reported, it can't determine whether to send the PIE or non-PIE app so it sends neither. At least, that's the way it used to work. I have now semi-randomly decided that if it is running kernel 3.4 or later (as my phone reports kernel 3.4 while running Android 4.4.2), it will get the PIE version. Anything less gets the non-PIE version.

Secondly, I recompiled the app just to make sure that the PIE compiler flags were present and re-deployed it as micro and mini collatz version 6.01.

So, if you could all give it a try, I'd appreciate it.I'm hoping that a) you will now get work and b) it will be the android_arm_pie plan class.

I changed the plan_class logic on the server. Some people are NOT using the latest BOINC version and that's a big problem. The plan_class logic assumes that the OS version (normally the kernel version) also reports the Android version. When it isn't reported, it can't determine whether to send the PIE or non-PIE app so it sends neither. At least, that's the way it used to work. I have now semi-randomly decided that if it is running kernel 3.4 or later (as my phone reports kernel 3.4 while running Android 4.4.2), it will get the PIE version. Anything less gets the non-PIE version.

Secondly, I recompiled the app just to make sure that the PIE compiler flags were present and re-deployed it as micro and mini collatz version 6.01.

So, if you could all give it a try, I'd appreciate it.I'm hoping that a) you will now get work and b) it will be the android_arm_pie plan class.

I changed the plan_class logic on the server. Some people are NOT using the latest BOINC version and that's a big problem. The plan_class logic assumes that the OS version (normally the kernel version) also reports the Android version. When it isn't reported, it can't determine whether to send the PIE or non-PIE app so it sends neither. At least, that's the way it used to work. I have now semi-randomly decided that if it is running kernel 3.4 or later (as my phone reports kernel 3.4 while running Android 4.4.2), it will get the PIE version. Anything less gets the non-PIE version.

Secondly, I recompiled the app just to make sure that the PIE compiler flags were present and re-deployed it as micro and mini collatz version 6.01.

So, if you could all give it a try, I'd appreciate it.I'm hoping that a) you will now get work and b) it will be the android_arm_pie plan class.

I changed the plan_class logic on the server. Some people are NOT using the latest BOINC version and that's a big problem. The plan_class logic assumes that the OS version (normally the kernel version) also reports the Android version. When it isn't reported, it can't determine whether to send the PIE or non-PIE app so it sends neither. At least, that's the way it used to work. I have now semi-randomly decided that if it is running kernel 3.4 or later (as my phone reports kernel 3.4 while running Android 4.4.2), it will get the PIE version. Anything less gets the non-PIE version.

Secondly, I recompiled the app just to make sure that the PIE compiler flags were present and re-deployed it as micro and mini collatz version 6.01.

So, if you could all give it a try, I'd appreciate it.I'm hoping that a) you will now get work and b) it will be the android_arm_pie plan class.