One of our colleagues from Boinc@Poland team, matszpk, successfully ported BOINC manager to Android device! There is also milkyway@home app, so we'd like to invite you for testing. Here are links for binaries and related subject on Boinc@Poland forum.:
binaries:
forum thread:
and my Samsung I 9100 stats :-)
/ 
Reply
Quote
Is there a way to manually "update" the project to send completed work? I am not seeing the option and this would be rather handy on a phone that would periodically need to shut down the client.
/ Reply
Quote
Never mind...I found it. Under manage client there is an option for "Do network communication now" that does this.
/ Reply
Quote
if you have some suggestions, bugs found, or any other feedback, please share. And on behalf of matszpk and Boinc@Poland thank you for participating :-)
/ Reply
Quote
Well, i give it a try on my Samsung Galaxy Tab 10.1 and Samsung Galaxy Nexus.
No probems so far on the Tab. On the Nexus with ICS 4.0.4 NativeBOINC 3.9.2.2
can not recognize the Battery. I have to start NativeBOINC by hand.
Neverless...thanks for that cool App. :-)
Helli
____________
/ Reply
Quote
I've been using NativeBOINC for some months now, crunching on an HTC EVO 3D. On average tasks takes 14 hours to crunch. It works excellent.
My stats:
http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=434262
/ Reply
Quote
Is the thread in the polish forum the only support thread? Because most people will very probably have problems to register there...
Anyway, in hope it can be answered here, I copy here a question from the SETI forums:
When i open it, I have to configure it to a new host, and I have no clue as to how to do that. I was wondering if anyone here knows what to do?
It is asking for Host Nickname, Address and password, using port #31416
____________
.
/ Reply
Quote
Is the thread in the polish forum the only support thread? Because most people will very probably have problems to register there...
Anyway, in hope it can be answered here, I copy here a question from the SETI forums:
When i open it, I have to configure it to a new host, and I have no clue as to how to do that. I was wondering if anyone here knows what to do?
It is asking for Host Nickname, Address and password, using port #31416
Having not tried it yet those sound like the normal things a new pc asks for when you first put Boinc on it, except for the nickname but maybe since it is not a pc it needs you to give it a device name.
/ Reply
Quote
Is the thread in the polish forum the only support thread? Because most people will very probably have problems to register there...
Anyway, in hope it can be answered here, I copy here a question from the SETI forums:
When i open it, I have to configure it to a new host, and I have no clue as to how to do that. I was wondering if anyone here knows what to do?
It is asking for Host Nickname, Address and password, using port #31416
That's what BOINC always asks if you want to attach a new host to a new project.
If you chose "Existing Account" instead of "New Account" you just have to give your email and password.
If you use BAM! (or any other account manager), you can attach projects to your android there as well.
I have just finished my first 2 WUs on my Galaxy S2, not that bad for a mobile methinks.
____________
Grüße vom Sänger
/ Reply
Quote
Hi, please make sure that you are using the most recent version.
Native client>Update binaries
and also, WUprop aplication has been released
/ Reply
Quote
Installed NativeBOINC with MW on ViewSonic G-Tablet.
Got:
<core_client_version>6.12.38</core_client_version>
<![CDATA[
<message>
process exited with code 26 (0x1a, -230)
</message>
<stderr_txt>
execv: Text file busy
</stderr_txt>
]]>
And both downloaded tasks failed.
Anyone saw such error and what suggestions would be how to avoid it ?
/ Reply
Quote
This error repeated on another similar device too.Attaching after changing from 2to1 CPU doesn't't help. How to run MW under Android?
/ Reply
Quote
Hello,
I am having problems receiving workunits on Android. So far I have not been able to crunch tasks for this project.
/ Reply
Quote
Yeah! Text file busy syndrome has been fixed. Please update NativeBOINC and BOINC client. currently these error shouldnt appear after updating/installing project app.
/ Reply
Quote
Updated. Now MW working on Galaxy mini. Will see if it can finish before deadlne.
/ Reply
Quote
Working on G-Tablet too now.
But there is big drawback still - no auto start when device switched on and booted. I have manually launch NativeBOINC first then manually launch client for it. Too much manual work not to forget to do it at each device startup.
Any suggestions how to automate it?
/ Reply
Quote
No lack with this project on Android still:
<core_client_version>6.12.38</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
<search_application> milkyway_separation 1.00 Linux ARM double </search_application>
Unrecognized XML in project preferences: nvidia_block_amount
Skipping: 128
Skipping: /nvidia_block_amount
<search_application> milkyway_separation 1.00 Linux ARM double </search_application>
Unrecognized XML in project preferences: nvidia_block_amount
Skipping: 128
Skipping: /nvidia_block_amount
<search_application> milkyway_separation 1.00 Linux ARM double </search_application>
Unrecognized XML in project preferences: nvidia_block_amount
Skipping: 128
Skipping: /nvidia_block_amount
suspend activities
resume activities
Integral 0 time = 132202.246668 s
Failed to calculate integral 0
Failed to calculate likelihood
<background_integral> NaN </background_integral>
<stream_integral> NaN NaN </stream_integral>
<background_likelihood> NaN </background_likelihood>
<stream_only_likelihood> NaN NaN </stream_only_likelihood>
<search_likelihood> NaN </search_likelihood>
17:46:13 (14035): called boinc_finish
</stderr_txt>
]]>
Before erroring computation stopped for days, was restarted many times from ~54%
/ Reply
Quote
From the other side, G-Tablet finally completed its 2 tasks:
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=453024
It took much longer then one can infere from listed elapsed time. App hung many times w/o any progress, was restarted really huge number of times... and finally finished OK in this case.
I noticed regular suspend computations/resume computations based on battery status. But device was always on plug, battery 100% actually.
I think NativeBOINC should refuse to do suspend in case that it doesnt' see gradual battery discharge and prev readings show high battery level.
/ Reply
Quote
Ok. new version available. Autostart has been added. BOINC client prevents discharging when device is plugged by suspending when battery level is low. Sometime frequently suspends/resumes can be observed when battery level is close to low level.
/ Reply
Quote
Ok. new version available. Autostart has been added. BOINC client prevents discharging when device is plugged by suspending when battery level is low. Sometime frequently suspends/resumes can be observed when battery level is close to low level.
I tested autostart - works great, thanks a lot!
About battery - I'm afraid it's not the case. Being unplugged device shows full battery meter, so it's not near full discharge. Will monitor this issue further.
And another issue: NativeBOINC doesn't request new work for MilkyWay@home project
Updated to latest NativeBOINC both manager and client, issue still here:
On first attach to project app was successfully downloaded and 2 tasks were started. They finally finished OK, both uploaded, reported and ultimately validated. So, host has positive RAC and no failures. Nevertheless NativeBOINC never initiates work fetch for MW now. Another attached project, WUprops, connect with its server often and asks for work regularly.
Attempt to manual update MW results in "not reporting or asking work" request. That is, problem with work fetch on client side - MW project never recives work fetch request from client.
host id: http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=453024
/ Reply
Quote