FYI: Nexus 7 (2013 model) just updated to Android 4.4 KitKat, and appears to be still working with 7.23 as before.

FYI: Nexus 7 (2013 model) just updated to Android 4.4 KitKat, and appears to be still working with 7.23 as before.

Same here with the 2012 model Nexus 7.

Claggy

FYI: Nexus 7 (2013 model) just updated to Android 4.4 KitKat, and appears to be still working with 7.23 as before.

Same here with the 2012 model Nexus 7.

Claggy

Oops, may have spoken too soon.

http://setiweb.ssl.berkeley.edu/beta/result.php?resultid=15381462

process exited with code 151 (0x97, -105)

We'll see. Hopefully was just the task that had been in progress before the update :/

My HTC One_V just keeps plugging along, it looks like the 7.23 app is faster than 7.21 as well.
http://setiweb.ssl.berkeley.edu/beta/results.php?hostid=66536

Ugh, looks like my error wasn't one off. A few more happened while I was out. So setting the Nexus 7 to NNT until needed for a new test.

I'll be releasing a new app tonight, I hope, which should restore some of the debugging info, and (again) reduce memory use at the (possible) cost of performance on low memory machines.

---

I'll be releasing a new app tonight, I hope, which should restore some of the debugging info, and (again) reduce memory use at the (possible) cost of performance on low memory machines.

Is there a reason why I only get one app type, SETI@home v7 v7.23 (armv6-vfp), on my Cat Phone? No change after resetting either.

Perhaps my Processor can't handle other app types, or that you haven't released any other types than (armv6-vfp).

http://setiweb.ssl.berkeley.edu/beta/host_app_versions.php?hostid=68232

---

WARNING!! "THIS IS A SIGNATURE", of the "IT MAY CHANGE AT ANY MOMENT" type. It may, or may not be considered insulting, all depending upon HOW SENSITIVE THE VIEWER IS, to certain inputs to/from the nervous system.

In past runs the armv6-vfp was as fast as any of the other apps except for armv7-vfpv4, so to make my life simple, I've only been releasing those two apps. Most phones don't have vfpv4, so that's why most people are only getting armv6-vfp.

---

In past runs the armv6-vfp was as fast as any of the other apps except for armv7-vfpv4, so to make my life simple, I've only been releasing those two apps. Most phones don't have vfpv4, so that's why most people are only getting armv6-vfp.

OK, I take it then, that my phone does not support vfpv4, whatever that is :-)

(must google vfpv4)

Edit: Did google it. Got confused. Now playing on my lips with my fingers. LOL

---

WARNING!! "THIS IS A SIGNATURE", of the "IT MAY CHANGE AT ANY MOMENT" type. It may, or may not be considered insulting, all depending upon HOW SENSITIVE THE VIEWER IS, to certain inputs to/from the nervous system.

In past runs the armv6-vfp was as fast as any of the other apps except for armv7-vfpv4, so to make my life simple, I've only been releasing those two apps. Most phones don't have vfpv4, so that's why most people are only getting armv6-vfp.

OK, I take it then, that my phone does not support vfpv4, whatever that is :-)

(must google vfpv4)

Edit: Did google it. Got confused. Now playing on my lips with my fingers. LOL

I did too. I didn't quite have the same reaction, but I am no more enlightened than I was before regarding my phone's ability or lack of it to run vfpv4. I just know it hasn't done so so far.

---

David
signature sent back to alpha testing

The phone is Zopo C2 - MTK MT6589T 1.5Ghz Quad Core Processor i.e. Armv7 Cortex-A7 (NEON and vfpv4)
Android 4.2.1


armv6-vfp 2 tasks Completed and validated
http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=5903355
http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=5903359

armv7-vfpv4 2 tasks Completed and validated
http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=5911119
http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=5911181

Hey, I'm new on this beta platform - I joined because there's this Android app available. I've already finished one workunit and found a small bug which I think no one reported. (found on Samsung Galaxy Young)

After disconnecting a charger and connecting again elapsed time on the task goes back to zero. I checked the results page and I noticed that it also totally "forgot" about counting CPU time.
The real run time was certainly way over 24 hours.


Here's the link to that WU. http://setiweb.ssl.berkeley.edu/beta/workunit.php?wuid=5918025

BTW, I checked in the BOINC event log, one time after reconnecting the charger it says:
[task] task_state=EXECUTING for <WU name here> from start
and another
[task] task_state=EXECUTING for <WU name here> from suspend
It's for the same WU and it still was processing from the point it was stopped despite this "from start" statement.

Of course I'm not saying that it's a vital bug but it would be nice if it could be fixed.

You might want to upgrade to a newer BOINC. They've been slow at updating the BOINC download page. I think the Google store is offering 7.2.35 as opposed to 7.2.15 from the BOINC page. You can also get 7.2.25 from the BOINC download page.

---

You might want to upgrade to a newer BOINC. They've been slow at updating the BOINC download page. I think the Google store is offering 7.2.35 as opposed to 7.2.15 from the BOINC page. You can also get 7.2.25 from the BOINC download page.

Google Play says latest version is still 7.2.15. It is from Dec. 6, though, which is certainly newer than the 7.2.15 Boinc I installed back in September. Perhaps the software is new but the version number wasn't updated?

You might want to upgrade to a newer BOINC. They've been slow at updating the BOINC download page. I think the Google store is offering 7.2.35 as opposed to 7.2.15 from the BOINC page. You can also get 7.2.25 from the BOINC download page.

Google Play says latest version is still 7.2.15. It is from Dec. 6, though, which is certainly newer than the 7.2.15 Boinc I installed back in September. Perhaps the software is new but the version number wasn't updated?

Yes, I noticed that too. And since the version number on Google Play is the same as the one I already have, no notices about upgrading will happen, and if I want to install the one now on Google Play, I have to uninstall the one on my phone first.

I haven't tried that though, so I do not know if they just forgot to update the version number on the one now on Google Play.

---

WARNING!! "THIS IS A SIGNATURE", of the "IT MAY CHANGE AT ANY MOMENT" type. It may, or may not be considered insulting, all depending upon HOW SENSITIVE THE VIEWER IS, to certain inputs to/from the nervous system.

You might want to upgrade to a newer BOINC. They've been slow at updating the BOINC download page. I think the Google store is offering 7.2.35 as opposed to 7.2.15 from the BOINC page.

Eric, you only get 7.2.35 from the Google Play Store if you're subscribed to the BOINC Android Testing Google Group, everyone else will get whatever is the latest Public Release is.

Claggy

I can confirm that's at least the third time I've seen the date change while the version number (7.2.15) stays the same.

If you uninstall do it locally on your device, don't use the Play store uninstall option/button.

Hey guys 1 problem I am having ,trying to run BOINC on a RK3188 TV stick under Android, is that there are no battery in these devices, even when I set the battery level to 0% it still don't work. Is it possible to have a tick box to ignore battery settings?

I know it is part of the BOINC client side thing but I am just wondering.

I'll have to ask ask David about that.

---

The changesets are already in for those, I think we're probably waiting for Rom to be in a position to built a new version:

Changeset 4eb156e in boinc-v2

android: support for stationary devices

•detect whether battery is present,
•if not, skip checks for battery heat, battery level and charger status
•by sending positive dummy data to the client
•remove category Power from preferences
•code to detect wired internet connection, treat as wifi
•refactor DeviceStatus? class, to have detection code in edu.berkeley.boinc.client rather than .rpc

Changeset d770bc3 in boinc-v2

android: added charger type preference.

•fix layout size of leglevel dialog
•refector preference code, more readable
•add charger type preference (ac vs usb vs wireless vs battery)

Claggy