Thx Claggy, the update trick worked for me!

Unfortunatly there's already a new problem here: I had 2 tasks running for more then 3 days, they finished today but the validation is inconclusive.
Before I got this tasks I copied the 7.28 neon application from Seti Beta to the Seti folder on my phone and renamed it to 7.21. Could this be a problem?

Some of the 7.21 apps have a known Bug where they find an extra triplet, just stand by and you'll get a fixed app in due course.

Swapping an app from Seti Beta won't work, they'll have different file_signatures, Boinc should just download the correct file again.

Claggy

Damn, and I thought I can run the 7.28 on regular SETI. I wonder why it hasn't been released yet......

---

Ok, one of those 2 tasks has been validated now. This task has been running for more then 3 days and I got 83 credits?!? I got more for shorter tasks on the same device. That's strange and I'm not sure if running Seti on android is really worth it :-(

---

That's strange and I'm not sure if running Seti on android is really worth it :-(

I think it's a miscalculation, or maybe just a "free publicity" thing.

If we caught all of the rain that fell over the oceans and harnessed the power from all of that falling water, we'd solve all of the energy problems we have.

If we get millions of pads and tablets and phones running SETI while they are being charged, then you've got some serious crunching power.

Twenty years from now, when your phone has more power than your desktop does now, maybe it'll be worthwhile, but not for a while.

Twenty years from now, when your phone has more power than your desktop does now, maybe it'll be worthwhile, but not for a while.

See my recent post in the Milestones thread...

---

Ok, one of those 2 tasks has been validated now. This task has been running for more then 3 days and I got 83 credits?!? I got more for shorter tasks on the same device. That's strange and I'm not sure if running Seti on android is really worth it :-(

My current phone, Galaxy S4, is much more powerful than several old desktops I still run. So by getting it working now the ever increasing power can be leveraged. I think someone mentioned that getting the mobile GPU to run is being looked at now. However only some of them support OpenCL. So it may take a generation or two to get that all worked out & the CPU in the phone isll probably be and 8 core 3GHz+ monster by then.

---

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

IMO there is one big problem with modern smartphones and BOINC. Let me explain:

As I said earlier in this thread, I own 2 android phones atm. My old phone, a Samsung Galaxy Ace 2, with 2 cores running at 1 GHz each, and my new phone, a Google (LG) Nexus 5, with a Snapdragon 800 SOC, that's 4 cores running at 2260 MHz.

Running Seti on the Samsung is no problem. It doesn't get hot, even on warm days the battery temperature stays below 35 degrees. You can run Seti 24/7 without problems.

The Nexus 5 is a complety different story. It's a quiet powerful phone but in my opinion it is just not made to run at full load for a longer time. When you run Seti on this phone it just takes a few minutes until it gets really hot. So no way to run Seti 24/7 on this phone unless you use some kind of active cooling. But ofc, nobody does this with a smartphone.

@HAL9000: Have you ever tried running Seti on your S4? I guess it's the same there.

---

The Nexus 5 is a complety different story. It's a quiet powerful phone but in my opinion it is just not made to run at full load for a longer time. When you run Seti on this phone it just takes a few minutes until it gets really hot. So no way to run Seti 24/7 on this phone unless you use some kind of active cooling. But ofc, nobody does this with a smartphone.

Put it on something metal, like a computer case, that conducts a lot of the heat away.

Claggy

That may help a bit but not enough to let it run for a longer time. And to be honest: This phone costed me €450 and it is my daily driver, so I won't take any risk there. It just doesn't feel safe to run Seti on this phone.

---

IMO there is one big problem with modern smartphones and BOINC. Let me explain:

As I said earlier in this thread, I own 2 android phones atm. My old phone, a Samsung Galaxy Ace 2, with 2 cores running at 1 GHz each, and my new phone, a Google (LG) Nexus 5, with a Snapdragon 800 SOC, that's 4 cores running at 2260 MHz.

Running Seti on the Samsung is no problem. It doesn't get hot, even on warm days the battery temperature stays below 35 degrees. You can run Seti 24/7 without problems.

The Nexus 5 is a complety different story. It's a quiet powerful phone but in my opinion it is just not made to run at full load for a longer time. When you run Seti on this phone it just takes a few minutes until it gets really hot. So no way to run Seti 24/7 on this phone unless you use some kind of active cooling. But ofc, nobody does this with a smartphone.

@HAL9000: Have you ever tried running Seti on your S4? I guess it's the same there.

I have used my S4. It is the 1.9GHz quad version instead of the 1.6/1.2 4+4 version. I thought I might have cooling issues with the hard rubbery case I have for it, but that didn't seem to be an issue. Using CPUz I did find that when running the core speeds were all over the place. So it looks like Samsung is doing something, probably in the interest of saving power, to throttle down the CPU most of the time.

The only real issue I had was power. When using all 4 cores a standard 500mA USB connection was not enough to keep the battery from discharging while running. I don't have a good solution for using a high powered wall charger at work. In our cubicals the outlets are inside the cube walls. Which makes plugging and unplugging a charger a PITA.

After a few weeks off running tasks on my phone I stopped until I can figure out some kind of power solution. I could rung 2 tasks & not have the problem, but what fun is that!

---

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

Nice, looks like not all newer phones have trouble with overheating then. So we may have indeed a future for Seti on android :-)

---

IMO there is one big problem with modern smartphones and BOINC. Let me explain:

As I said earlier in this thread, I own 2 android phones atm. My old phone, a Samsung Galaxy Ace 2, with 2 cores running at 1 GHz each, and my new phone, a Google (LG) Nexus 5, with a Snapdragon 800 SOC, that's 4 cores running at 2260 MHz.

Running Seti on the Samsung is no problem. It doesn't get hot, even on warm days the battery temperature stays below 35 degrees. You can run Seti 24/7 without problems.

The Nexus 5 is a complety different story. It's a quiet powerful phone but in my opinion it is just not made to run at full load for a longer time. When you run Seti on this phone it just takes a few minutes until it gets really hot. So no way to run Seti 24/7 on this phone unless you use some kind of active cooling. But ofc, nobody does this with a smartphone.

@HAL9000: Have you ever tried running Seti on your S4? I guess it's the same there.

I have used my S4. It is the 1.9GHz quad version instead of the 1.6/1.2 4+4 version. I thought I might have cooling issues with the hard rubbery case I have for it, but that didn't seem to be an issue. Using CPUz I did find that when running the core speeds were all over the place. So it looks like Samsung is doing something, probably in the interest of saving power, to throttle down the CPU most of the time.

The only real issue I had was power. When using all 4 cores a standard 500mA USB connection was not enough to keep the battery from discharging while running. I don't have a good solution for using a high powered wall charger at work. In our cubicals the outlets are inside the cube walls. Which makes plugging and unplugging a charger a PITA.

After a few weeks off running tasks on my phone I stopped until I can figure out some kind of power solution. I could rung 2 tasks & not have the problem, but what fun is that!

Why not plug in a surge strip into the Cube Wall and plug/unplug from the surge strip... Perhaps less of a PITA???...??? YMMV

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

running on LG G2, stock firmware and default settings on boinc, except for using 4 cores... I usually keep it connected to the charger during the night. Slightly warm when I disconnect it in the morning.

Still, I am not sure it's worth having seti running on a smartphone. They're just not made for crunching.

---

Why not plug in a surge strip into the Cube Wall and plug/unplug from the surge strip... Perhaps less of a PITA???...??? YMMV

That is the obvious solution. However we are not allowed to use them in the cubes. Probably some electrical safety thing I would guess

running on LG G2, stock firmware and default settings on boinc, except for using 4 cores... I usually keep it connected to the charger during the night. Slightly warm when I disconnect it in the morning.

Still, I am not sure it's worth having seti running on a smartphone. They're just not made for crunching.

It can also be said there are a number of desktop machines that are not sufficiently engineered for crunching 24/7. However, That does not prevent us from giving it a go.
Once I get around to repairing my old MyTouch 3G Slide. I plan to play around with running stuff on it again. I may be able to leave it connected 24/7 without the battery in it & have it run still.

---

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

I just can't resist those $ 55 Wal-Mart Ematic EGQ307s ... so I got another one.
That's 3 tabs and 4 desktops ... OCD at work. Maybe I need a shrink.

Folks, I could still need some help here.

Even with Claggys update-trick I can not get more then 4 WUs on my phone. And it's just 4 if they are shorties, Usually I can just get a max of 3.

The problem is that I need the charger at work for my other phone and I don't have Wifi at work. So with just 3 tasks I have to carry the phone from work to home every 2 days or so.
So I need more tasks on the phone, enough for 1 week. I would take the phone to work on monday, let it run there the whole week and take it back home on friday to upload & report the tasks done and fetch new work.

I have root access on this phone so I thought I just have to edit some files, but it looks like I can't find the correct file to get it done.

First I went to data/data/edu.berkely.boinc/client There is a file called global_prefs.xml that includes a line "<work_buf_min_days>". I changed the value there from 0 to 7 but nothing happens.
Then I found a file called sched_request_setiathome.berkeley.edu.xml which includes the same line. Again I switched the value to 7 but again no luck.


So can maybe anybody tell me which line in which file I have to edit to get more work on my phone?

---

Folks, I could still need some help here.

Even with Claggys update-trick I can not get more then 4 WUs on my phone. And it's just 4 if they are shorties, Usually I can just get a max of 3.

The problem is that I need the charger at work for my other phone and I don't have Wifi at work. So with just 3 tasks I have to carry the phone from work to home every 2 days or so.
So I need more tasks on the phone, enough for 1 week. I would take the phone to work on monday, let it run there the whole week and take it back home on friday to upload & report the tasks done and fetch new work.

I have root access on this phone so I thought I just have to edit some files, but it looks like I can't find the correct file to get it done.

First I went to data/data/edu.berkely.boinc/client There is a file called global_prefs.xml that includes a line "<work_buf_min_days>". I changed the value there from 0 to 7 but nothing happens.
Then I found a file called sched_request_setiathome.berkeley.edu.xml which includes the same line. Again I switched the value to 7 but again no luck.


So can maybe anybody tell me which line in which file I have to edit to get more work on my phone?

I am pretty sure global_prefs.xml is populated from server data. So changing it may not have any effect.
In your BOINC settings you would want to set Maintain enough tasks to keep busy for at least n days to your desired value for the venue where this device is set.

---

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

I've been having problems with my second EGQ307 tablet. I keep getting out of memory errors. I cleaned out everything I could today and managed to get 4 cores up and running but the memory error is still there. Sorry, that's all I can suggest ... look for 'out of memory errors'.

Any ideas what can cause this:

<core_client_version>7.3.12</core_client_version>
<![CDATA[
<stderr_txt>
ted at 68.07 percent.
stackdumps unavailable
Restarted at 68.07 percent.
stackdumps unavailable
Restarted at 68.07 percent.

(skipping lots of this)

stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
Restarted at 68.10 percent.
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
stackdumps unavailable
Restarted at 68.10 percent.

Flopcounter: 36638428715310.914062

Spike count:    0
Autocorr count: 0
Pulse count:    0
Triplet count:  0
Gaussian count: 1
11:57:00 (5390): called boinc_finish

</stderr_txt>
]]>

The WU finished OK and was valid, but I guess this should not look like that.

---

Folks, I could still need some help here.

Even with Claggys update-trick I can not get more then 4 WUs on my phone. And it's just 4 if they are shorties, Usually I can just get a max of 3.

The problem is that I need the charger at work for my other phone and I don't have Wifi at work. So with just 3 tasks I have to carry the phone from work to home every 2 days or so.
So I need more tasks on the phone, enough for 1 week. I would take the phone to work on monday, let it run there the whole week and take it back home on friday to upload & report the tasks done and fetch new work.

I have root access on this phone so I thought I just have to edit some files, but it looks like I can't find the correct file to get it done.

First I went to data/data/edu.berkely.boinc/client There is a file called global_prefs.xml that includes a line "<work_buf_min_days>". I changed the value there from 0 to 7 but nothing happens.
Then I found a file called sched_request_setiathome.berkeley.edu.xml which includes the same line. Again I switched the value to 7 but again no luck.


So can maybe anybody tell me which line in which file I have to edit to get more work on my phone?

I am pretty sure global_prefs.xml is populated from server data. So changing it may not have any effect.
In your BOINC settings you would want to set Maintain enough tasks to keep busy for at least n days to your desired value for the venue where this device is set.

Thx Hal, but:

These preferences do not apply to Android devices.

---