Prepping for Android 5
log in

Advanced search

Message boards : News : Prepping for Android 5

1 · 2 · Next
Author Message
Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 20214 - Posted: 2 Feb 2015, 21:00:17 UTC

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.

Jon Fox
Send message
Joined: 6 Sep 09
Posts: 36
Credit: 351,380,599
RAC: 260,574
Message 20229 - Posted: 6 Feb 2015, 1:37:30 UTC

Early feedback:


Here's a link to one of the errors I'm seeing on my 2013 nexus 7 running Android 5.0.2 and the 7.4.41 client: http://boinc.thesonntags.com/collatz/result.php?resultid=14157549

--
Jon

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 20232 - Posted: 6 Feb 2015, 14:14:45 UTC - in response to Message 20229.

Thanks. It looks like your Android device is running the mini WUs and I had only deployed the new PIE enabled app for micro WUs. I'll go ahead and add it to the mini's as well.

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 20233 - Posted: 6 Feb 2015, 15:08:42 UTC - in response to Message 20229.
Last modified: 6 Feb 2015, 15:09:52 UTC

I've added mini_collatz apps for Android with PIE support (Android 4.1 or later) and without PIE (pre-Android 4.1) and deprecated the Android apps that use no plan class.

Jon Fox
Send message
Joined: 6 Sep 09
Posts: 36
Credit: 351,380,599
RAC: 260,574
Message 20234 - Posted: 6 Feb 2015, 17:16:24 UTC

Thanks, Slicker.

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.

Thanks again.

--
Jon

JagDoc
Send message
Joined: 4 Oct 09
Posts: 1
Credit: 70,108,895
RAC: 0
Message 20236 - Posted: 7 Feb 2015, 9:47:11 UTC

On my Nvidia Shield Tab with Android 5.0.1 all WUs have error:
http://boinc.thesonntags.com/collatz/results.php?hostid=157747

Sensory++
Send message
Joined: 9 Dec 14
Posts: 1
Credit: 388,262
RAC: 0
Message 20240 - Posted: 8 Feb 2015, 10:48:16 UTC

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...

Jon Fox
Send message
Joined: 6 Sep 09
Posts: 36
Credit: 351,380,599
RAC: 260,574
Message 20243 - Posted: 9 Feb 2015, 12:47:29 UTC

Just a quick update. No WUs offered yet.

--
Jon

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 20245 - Posted: 9 Feb 2015, 18:46:20 UTC - in response to Message 20243.

Just a quick update. No WUs offered yet.

--
Jon


I'm not seeing anything in the server logs from your device so I wonder if it is having connect issues which were listed at https://boinc.berkeley.edu/dev/forum_thread.php?id=9734&sort_style=&start=0

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.

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 20247 - Posted: 9 Feb 2015, 19:14:50 UTC

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.

Jon Fox
Send message
Joined: 6 Sep 09
Posts: 36
Credit: 351,380,599
RAC: 260,574
Message 20248 - Posted: 9 Feb 2015, 19:19:45 UTC - in response to Message 20245.

I'm running the 7.4.41 client under Android 5.0.2.

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.

In each case, the error code was 0x1 and the stderr_txt reads:

error: only position independent executables (PIE) are supported


Here are the links to the four (4) tasks:
http://boinc.thesonntags.com/collatz/result.php?resultid=14248865
http://boinc.thesonntags.com/collatz/result.php?resultid=14248800
http://boinc.thesonntags.com/collatz/result.php?resultid=14248799
http://boinc.thesonntags.com/collatz/result.php?resultid=14248797

Here's a link to the "details" page for the Nexus 7:
http://boinc.thesonntags.com/collatz/show_host_detail.php?hostid=140965

Please let me know if there's anything else I can provide or do to help.

--
Jon

Dr Who Fan
Avatar
Send message
Joined: 27 May 14
Posts: 21
Credit: 4,562,054
RAC: 0
Message 20249 - Posted: 9 Feb 2015, 19:57:41 UTC - in response to Message 20232.

Thanks. It looks like your Android device is running the mini WUs and I had only deployed the new PIE enabled app for micro WUs. I'll go ahead and add it to the mini's as well.

How soon will the Mini app be restored for the "android_arm_non_pie"?
The old Andriod ARM Mini app is no longer listed as available in the Applications List... I only see:
    Android running on ARM 6.00 (android_arm_pie)
    Android running on x86 6.00


Recent Work Fetch log from my Nexus7

    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


____________

Jon Fox
Send message
Joined: 6 Sep 09
Posts: 36
Credit: 351,380,599
RAC: 260,574
Message 20256 - Posted: 10 Feb 2015, 3:31:22 UTC

Slicker,

I see my most recent response was created just as you were describing the root cause of the "no WUs offered" scenario--sorry for the overlap.

I'll drop back into wait-and-monitor mode and provide updates as changes occur.

Thanks again.

--
Jon

Profile Coronium
Avatar
Send message
Joined: 3 May 13
Posts: 6
Credit: 79,900,693
RAC: 176
Message 20258 - Posted: 11 Feb 2015, 10:34:42 UTC - in response to Message 20256.
Last modified: 11 Feb 2015, 10:37:29 UTC

Problem with Shared Memory

I got no new tasks since 7 days. Resetting project doesn't help. "Not tasks available ..."

Therefore I create an app_info.xml which seems to work.

<app_info>
<app>
<name>micro_collatz</name>
<user_friendly_name>micro_collatz</user_friendly_name>
</app>
<file_info>
<name>micro_collatz_6.00_arm-android-linux-gnu__android_arm_pie</name>
<executable/>
</file_info>
<app_version>
<app_name>micro_collatz</app_name>
<version_num>600</version_num>
<file_ref>
<file_name>micro_collatz_6.00_arm-android-linux-gnu__android_arm_pie</file_name>
<main_program/>
</file_ref>
<platform>arm-android-linux-gnu</platform>
<plan_class>android_arm_pie</plan_class>
<avg_ncpus>1.000000</avg_ncpus>
<max_ncpus>1.000000</max_ncpus>
</app_version>
</app_info>


New WUs arrive. But there is a strange issue with shared memory. WUs don't start because they are waiting for shared memory. State: "Waiting for shared memory"

Raw task info from remote Boinctui / Linux:
┌─────────────────────────────────── Task Info Raw View ──────────────────────────────────┐ │ │ │ PROJECT NAME Collatz Conjecture │ │ APP NAME micro_collatz │ │ │ │ name micro_collatz_2393173198289669727347_6442450944_1 │ │ wu_name micro_collatz_2393173198289669727347_6442450944 │ │ version_num 600 │ │ plan_class android_arm_pie │ │ project_url http://boinc.thesonntags.com/collatz/ │ │ final_cpu_time 0.000000 (0s) │ │ final_elapsed_time 0.000000 (0s) │ │ exit_status 0 │ │ state 2 (downloaded) │ │ report_deadline 1424852678.000000 (Wed Feb 25 09:24:38 2015) │ │ received_time 1423643078.192069 (Wed Feb 11 09:24:38 2015) │ │ estimated_cpu_time_remaining 43412.926186 (12h 3m 32s) │ │ │ │ active_task_state 0 (uninitialized) │ │ app_version_num 600 │ │ slot 2 │ │ pid 0 │ │ scheduler_state 1 (preempted) │ │ checkpoint_cpu_time 0.000000 (0s) │ │ fraction_done 0.000000 (0 %) │ │ current_cpu_time 0.000000 (0s) │ │ elapsed_time 0.000000 (0s) │ │ swap_size 0.000000 │ │ working_set_size 0.000000 │ │ working_set_size_smoothed 0.000000 │ │ page_fault_rate 0.000000 │ │ needs_shmem │ │ │ │ │ └─────────────────────────────────────────────────────────────────────────────────────────┘


My OS is Android 4.4.4 (quad core cpu, 1GB RAM) with Native-Boinc-App. PIE and none-PIE are supported both.

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).

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 20259 - Posted: 12 Feb 2015, 0:45:41 UTC

Try closing apps that aren't actually running and see if the memory issue goes away. It seems that the BOINC apps don't swap out very well.

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 20264 - Posted: 12 Feb 2015, 21:19:21 UTC

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.

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 20265 - Posted: 12 Feb 2015, 21:19:44 UTC

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.

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 20266 - Posted: 12 Feb 2015, 21:19:45 UTC

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.

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 20267 - Posted: 12 Feb 2015, 21:19:45 UTC

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.

Profile Slicker
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Avatar
Send message
Joined: 11 Jun 09
Posts: 2525
Credit: 740,580,099
RAC: 1
Message 20268 - Posted: 12 Feb 2015, 21:19:46 UTC

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.

1 · 2 · Next
Post to thread

Message boards : News : Prepping for Android 5


Main page · Your account · Message boards


Copyright © 2018 Jon Sonntag; All rights reserved.