I did so. Moreover, I've uninstalled the app and installed it directly in the internal memory, but I see the same - 20-30 sec of crunching and restarting then. Should I give it up, or there is may be any other ideas?

---

I did so. Moreover, I've uninstalled the app and installed it directly in the internal memory, but I see the same - 20-30 sec of crunching and restarting then. Should I give it up, or there is may be any other ideas?

I am out of ideas. Might be time to try here.
http://nativeboinc.org/site/uncat/notifybug

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

got inconclusive vs CUDA stock:
http://setiathome.berkeley.edu/workunit.php?wuid=1209102694

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

My phone has completed 6 units all of which have been validated, even though it did pop a couple of 'error occurred during computation' messages. Is this app optimized in any way?
______________

I just installed this Native Boinc client on an Asus TF101 eeepad transformer.
Does anyone know how to get this to be manageable under BoincTasks.

I have added the host IPs, the access password and enabled remote access.
I've added it into Boinc Tasks as a computer but no connect.
The TF101 is pingable and is showing up in my computers on setiathome.

Any ideas ?

Reg
[Edit} Belay the above, it started working. Took a few minutes, but it's working. Reporting 23 hours for 1st task and 60 hours for the 2nd task !

---

got inconclusive vs CUDA stock:
http://setiathome.berkeley.edu/workunit.php?wuid=1209102694

Looks like small precision issue - all 3 qualified as valid in the end

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

got inconclusive vs CUDA stock:
http://setiathome.berkeley.edu/workunit.php?wuid=1209102694

Looks like small precision issue - all 3 qualified as valid in the end

I've got an inconclusive against Stock Cuda too, it'll likely be because of Stock Cuda's poor chirp.

Claggy

I use SETI MB for Android on 2 almost identical devices. Both are Viewsonic G-Tab. Both were rooted with Cyanogen mod.
But one of them shows elapsed time ~2x of CPU time.
Another one shows elapsed ~== CPU time.
On first one there were issues (lockups) before, when it crunched MW tasks. So I played with options and set 50% or so CPU usage.
But since then I reverted to 100% usage of both CPU cores. Just checked this once more in local prefs - use 100% of CPUs 100% of time.
Maybe NativeBOINC missed that instruction? Can anyone confirm this observation - how (if yes) NativeBOINC obeys fractional CPU usage setting?

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

I use SETI MB for Android on 2 almost identical devices. Both are Viewsonic G-Tab. Both were rooted with Cyanogen mod.
But one of them shows elapsed time ~2x of CPU time.
Another one shows elapsed ~== CPU time.
On first one there were issues (lockups) before, when it crunched MW tasks. So I played with options and set 50% or so CPU usage.
But since then I reverted to 100% usage of both CPU cores. Just checked this once more in local prefs - use 100% of CPUs 100% of time.
Maybe NativeBOINC missed that instruction? Can anyone confirm this observation - how (if yes) NativeBOINC obeys fractional CPU usage setting?

I'm running my Nexus 7 at 75% of processors, and only 3 Seti tasks (or PrimeGrid tasks beforehand) run at once, increasing usage to 100% locks the Nexus 7 up and often causes it to reboot, this i think increased with newer NativeBoincs,
when i first ran NativeBoinc it would run 4 instances with little problem. (It's currently on 0.4.4.1b)

Claggy

To Raistmer: Maybe one of your G-Tabs have disabled core. If you have root, you can force to enable second core.
echo 1 > /sys/devices/system/cpu/cpu1/online
On my HTC Sensation that trick works.

To Raistmer: Maybe one of your G-Tabs have disabled core. If you have root, you can force to enable second core.
echo 1 > /sys/devices/system/cpu/cpu1/online
On my HTC Sensation that trick works.

But why NativeBOINC sees 2 CPUs then and launches 2 tasks at once?...

EDIT: entered that string in terminal emulator - premission denied (as should be :) ). Re-entered after su command - no error in return. Checked that file - it contains 1 now (just as cpu0/online does).
Will see if it will change anything. Will report back when new SETI task finished.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Anonymous platform (CPU)
2993321760 1243493560 12 May 2013, 14:40:13 UTC 16 May 2013, 5:45:23 UTC Completed and validated 96,581.59 94,933.89 109.70 SETI@home Enhanced
Anonymous platform (CPU)

So, now elapsed very close to CPU times, as should be.
Looks like the trick works indeed, thanks.
How it became disabled though... but it's another question :)

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Regard to disabling cores:
echo 0 > /sys/devices/system/cpu/cpu1/online
Just file 'online' controls a core enabling (1 - enable, 0 - disable).
Regard to boinc client core detection: a boinc client cant handle dynamic core allocation (enabling) and this is reason why I decided to detect all cores even if disabled.
Ofcourse this is not good behaviour (likely, will be fixed in next versions of a boinc client).

Hi all, I'm running SETI on two android devices. Asus Infinity TF700 in performance mode and the HTC One X.

Both have exactly the same ARM V7 processor HTC has quad core at 1500MHz and the TF700 at 1700MHZ.

Both crunching fine with no issues I can see but HTC appears to crunch faster than TF700 even though it's a slower processor...

I am keeping them running as much as I can to see how much RAC can be achieved.

HTC runs very hot if not careful and will discharge faster than it can charge if the screen is left on.

i compiled version from repository. This is 'sah_v6'@1793 branch.
I didnt use sah_v7, because it didnt provided by server (workunit was available for sah6).

Any progress in getting the v7 app compiled? Setiathome v7 is supposed to go live here tomorrow.

Claggy

i compiled version from repository. This is 'sah_v6'@1793 branch.
I didnt use sah_v7, because it didnt provided by server (workunit was available for sah6).

Any progress in getting the v7 app compiled? Setiathome v7 is supposed to go live here tomorrow.

Claggy

I really hope that v7 deployment will be addition, not substitution. I.e., at least for some time both v6 and v7 work will be generated.
Otherwise we will lose instantly not only Android devices but all anonymous platform ones that will not update promptly.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

About the 'to use smartphones or not to use smartphones' discussion: I think this is for people who already have smartphones and are just wanting to make use of their spare processing power. Of course it doesn't make sense for someone who doesn't have/want/need a smartphone (like myself) to get one solely or predominantly for the purpose of contributing to BOINC projects.

I see it as similar to the situation with the MB OpenCL application for ATI GPUs. It doesn't matter that processing performance isn't as great as MB CUDA between ATI and NV GPUs of roughly equal graphical performance. The point is that at least the ATI GPUs have the opportunity to contribute, should the owner wish it. At least, I recall that was the reasoning given by Raistmer at the time of the initial release.

So even though I don't have a smartphone and have no intention of getting one for the foreseeable future, I'm in favour of this development for if I ever do decide to join the ranks of Android users. Keep up the good work! (:

---

Soli Deo Gloria

Likely, new setiboinc v7 will be available in this weekend (2013-06-01,02) or next week (much likely). I compiled new version v7, and I applied my changes to it, and now I am testing it on my hardware :). Ofcourse, version v6 going to be still available :)

Likely, new setiboinc v7 will be available in this weekend (2013-06-01,02) or next week (much likely). I compiled new version v7, and I applied my changes to it, and now I am testing it on my hardware :). Ofcourse, version v6 going to be still available :)

Great news!

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Eagerly awaiting the v7 for android now. My small phone recently crossed 1000 credits, better put it to some work than let it lie idle.