Well, I did some test on G-Tablet.
All this based on assumption that PrimeGrid task progress is linear (don't know if it's true or not).

First 3 h tablet worked with dimmed display, next ~2h it worked with switched off display (power button was short-pressed)

For "display on": both cores give 0.01%/min progress.

With switched off display both cores give 0.011%/min and 0.0115%/min

So, looks like no slowdown and maybe even speedup.

But this should be repeated few times on different WU stages to be more or less sure.

Will leave GT-S5570 in dimmed screen state for night and see how linear progress is. For now it looks like some acceleration present in %/min ratio.

Are there Primegrid benchmark tasks? That would help evaluate without taking 80 hours.

---

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

If I found a tablet with a good enough CPU cheap I might consider getting one.

Maybe Viewsonic G-Tablet too? Quite cheap, 2-core 1,4GHz ARMv7 CPU, Tegra GPU... and crap display ;D.

One of pluses - it's completelly configurable. Few firmwares in the net, can be easely rooted and so on...

Are there Primegrid benchmark tasks? That would help evaluate without taking 80 hours.

No idea :)

But leaving display switched off on phone (via power button short-press) looks promising. Another ~8h and same progress (~2,3%) as with just dimmed display.
So, at least no big underclocking occured.

Summary: Viewsonic G-tablet and Samsumg Galaxy mini can crunch with switched off displays at full speed.

Anyone succeeded in moving BOINC from inner storage to SD card?
I tried it on HTC Desire but it can't download tasks cause too little space in inner storage remains on that phone...

It asks for Host nickname, Address, port (31416) and password. Nowhere (and I have pressed all the buttons it has) is there a place for me to log into something. I even used the address that shows up on the bottom of my client's advanced view, no workie.

I'd try the following:

1. Attach to Milkyway or PrimeGrid with one of your PCs (with very low cache, if you don't want to crunch that on your PC) to create an account.

2. As host nickname you can probably choose whatever you want (of course nothing "complicated", single word only), adress I *think* is the e-mail adress you use for BOINC and password is your BOINC password.


@all: is there BOINC for (jailbreaked) iOS? I couldn't find anything useful so far...

Nothing worked so I ended up deleting it from my phone :(

If I found a tablet with a good enough CPU cheap I might consider getting one.

Maybe Viewsonic G-Tablet too? Quite cheap, 2-core 1,4GHz ARMv7 CPU, Tegra GPU... and crap display ;D.

One of pluses - it's completelly configurable. Few firmwares in the net, can be easely rooted and so on...

Those are $250-300 here. I was thinking more <$100 range. The price range I would be looking at may not have the CPU like I would want right now, but next year, or in 6 months, they might.

Also I wasn't able to get NativeBOINC to live on the SDCard. With my phone only having 140mb usable storage for apps I had to delete some stuff to be able to download tasks.

---

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

Hal, that is a HUGE drawback on Android....

Some apps allow you to install to SD, and some don't. Furthermore some apps that don't allow installation to SD, can often be moved to SD on rooted phones and sometimes even non-rooted phones.

It all has to do with the dalvik machine on which apps run. If they make some changes to that app, it can totally allow install to SD, but it's up to the Boinc ppl to do it, or (on rooted phones) you can try an app called "app to SD"(or others) or something like that to see if Boinc as-is would allow transferring it to SD.

---

#resist

Hal, that is a HUGE drawback on Android....

Some apps allow you to install to SD, and some don't. Furthermore some apps that don't allow installation to SD, can often be moved to SD on rooted phones and sometimes even non-rooted phones.

It all has to do with the dalvik machine on which apps run. If they make some changes to that app, it can totally allow install to SD, but it's up to the Boinc ppl to do it, or (on rooted phones) you can try an app called "app to SD"(or others) or something like that to see if Boinc as-is would allow transferring it to SD.

I can see reasons for not allowing apps on the SD Card. It is removable storage after all. Internal storage being limited is crazy on some devices. I was looking at phones. One with 8GB built in only allowed 1GB for user storage. So making sure you have enough storage space is another issue when using mobile devices it would seem.

---

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

Yes, wasn't able to install on HTC Desire because of inner space free amount limitation

Yes, wasn't able to install on HTC Desire because of inner space free amount limitation

I've also got very little internal space left on my HTC Desire, once i hear that it can be installed on SD card then i'll try it,

Claggy

There's a nifty workaround in case of unsufficient internal space - worked for me on a Galaxy with factory-set internal 256 MB.

http://en.androidwiki.com/wiki/ADB_Shell_Command_Reference
The setInstallLocation command changes the default install location
0 [auto]: Let system decide the best location
1 [internal]: Install on internal device storage
2 [external]: Install on external media

Therefor, ADB is needed.
http://developer.android.com/guide/developing/tools/adb.html

I was able to get heaps of free space then, but still I'm unable to tell which directories used for WU's.

---

SETI@home user since: Sat Apr 3 1999 20:42:33 1999 UTC
SETI@home classic workunits 3,773
SETI@home classic CPU time 24,750 hours

Well, I did some test on G-Tablet.
All this based on assumption that PrimeGrid task progress is linear (don't know if it's true or not).

First 3 h tablet worked with dimmed display, next ~2h it worked with switched off display (power button was short-pressed)

For "display on": both cores give 0.01%/min progress.

With switched off display both cores give 0.011%/min and 0.0115%/min

So, looks like no slowdown and maybe even speedup.

But this should be repeated few times on different WU stages to be more or less sure.

Will leave GT-S5570 in dimmed screen state for night and see how linear progress is. For now it looks like some acceleration present in %/min ratio.

Was not able to reproduce working while switched display off on G-Tablet.
Moreover, very often power short-press leads to complete power-off after some time (power short-press doesn't wake device, long-press switches it off and then boot sequence follows).

Bif flaw of current NativeBOINC - it's doesn't start automatically when device booted.

I was not able to complete a Primegrid task in time with it. Milkyway it was able to do reasonably well. It actually ran faster than the PIII 850MHz machine I ran to compare.

How did you manage to run MW ? Each time I attach to project first tasks end with computation error and NativeBOINC refuses to ask more tasks from MW project after this...
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=450933

I was not able to complete a Primegrid task in time with it. Milkyway it was able to do reasonably well. It actually ran faster than the PIII 850MHz machine I ran to compare.

How did you manage to run MW ? Each time I attach to project first tasks end with computation error and NativeBOINC refuses to ask more tasks from MW project after this...
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=450933

I do not know. It ran fine without my help.

I had the opposite problem with NativeBOINC always running. Even when I did not want it to. Such as closing it. Only to find it running later. I think that might be something T-Mobile did to the OS. As I find a lot of things spontaneously are restarted.

I might want to get a Nexus device to play with at some point. As products using that name are sot meant to have customized things done to them & just be a "pure" android device.

---

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

I was not able to complete a Primegrid task in time with it. Milkyway it was able to do reasonably well. It actually ran faster than the PIII 850MHz machine I ran to compare.

How did you manage to run MW ? Each time I attach to project first tasks end with computation error and NativeBOINC refuses to ask more tasks from MW project after this...
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=450933

I do not know. It ran fine without my help.

I had the opposite problem with NativeBOINC always running. Even when I did not want it to. Such as closing it. Only to find it running later. I think that might be something T-Mobile did to the OS. As I find a lot of things spontaneously are restarted.

I might want to get a Nexus device to play with at some point. As products using that name are sot meant to have customized things done to them & just be a "pure" android device.

And your device and Android version ?

PrimeGrid on G-Tablet missed deadline too though managed to get credits when finally reported tasks. Galaxy mini failed to finish before task completely disappears from site so I aborted task.
The single project that functioning OK is WUprops@home.
MW ends with computation error then doesn't ask for work, PrimeGrid has too long tasks, Enigma@home has no work. And RadioActive@home requires special hardware as I understand their comments on site.

I was not able to complete a Primegrid task in time with it. Milkyway it was able to do reasonably well. It actually ran faster than the PIII 850MHz machine I ran to compare.

How did you manage to run MW ? Each time I attach to project first tasks end with computation error and NativeBOINC refuses to ask more tasks from MW project after this...
http://milkyway.cs.rpi.edu/milkyway/results.php?hostid=450933

I do not know. It ran fine without my help.

I had the opposite problem with NativeBOINC always running. Even when I did not want it to. Such as closing it. Only to find it running later. I think that might be something T-Mobile did to the OS. As I find a lot of things spontaneously are restarted.

I might want to get a Nexus device to play with at some point. As products using that name are sot meant to have customized things done to them & just be a "pure" android device.

And your device and Android version ?

http://en.wikipedia.org/wiki/MyTouch_3G_Slide with FroYo
http://milkyway.cs.rpi.edu/milkyway/show_host_detail.php?hostid=448127

---

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

All devices I tried so far work under Gingerbread. Maybe it's the key difference?
Will try to reflash my GTablet with Froyo based image...