Have a problem with stall of computation on Samsung gs2. After little babysitting ;-) seems like battery overheats and client switch to suspended status. Then after while computing resumes but running tasks percentage stays still. And with suspending and resuming task restarts and new cycle begins...
Tue Jul 23 23:07:19 EEST 2013|Einstein@Home|[task] task_state=EXECUTING for p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 from unsuspend
Tue Jul 23 23:07:19 EEST 2013||Resuming computation
Tue Jul 23 23:06:39 EEST 2013|Einstein@Home|[task] task_state=SUSPENDED for p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 from suspend
Tue Jul 23 23:06:39 EEST 2013||(battery temperature 41.0 > limit 40.0 Celsius)
Tue Jul 23 23:06:39 EEST 2013||Suspending computation - battery thermal protection
Tue Jul 23 23:06:28 EEST 2013|Einstein@Home|[task] result p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 checkpointed
Tue Jul 23 23:05:25 EEST 2013|Einstein@Home|[task] result p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 checkpointed
Tue Jul 23 23:04:21 EEST 2013|Einstein@Home|[task] result p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 checkpointed
Tue Jul 23 23:03:19 EEST 2013|Einstein@Home|[task] result p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 checkpointed
Tue Jul 23 23:02:17 EEST 2013|Einstein@Home|[task] result p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 checkpointed
Tue Jul 23 23:01:12 EEST 2013|Einstein@Home|[task] result p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 checkpointed
Tue Jul 23 23:00:12 EEST 2013|Einstein@Home|[task] result p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 checkpointed
Tue Jul 23 22:59:09 EEST 2013|Einstein@Home|[task] result p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 checkpointed
Tue Jul 23 22:58:04 EEST 2013|Einstein@Home|Restarting task p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 using einsteinbinary_BRP4 version 106 (NEON) in slot 0
Tue Jul 23 22:58:04 EEST 2013|Einstein@Home|[task] task_state=EXECUTING for p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 from start
Tue Jul 23 22:58:04 EEST 2013|Einstein@Home|[task] ACTIVE_TASK::start(): forked process: pid 10552
Tue Jul 23 22:58:04 EEST 2013|Einstein@Home|[task] task_state=UNINITIALIZED for p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 from handle_exited_app
Tue Jul 23 22:58:04 EEST 2013|Einstein@Home|[task] Process for p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 exited, status 9, task state 8
Tue Jul 23 22:58:03 EEST 2013|Einstein@Home|[task] quit request timed out, killing task p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1
Tue Jul 23 22:58:00 EEST 2013|Einstein@Home|task p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 resumed by user
Tue Jul 23 22:57:47 EEST 2013|Einstein@Home|[task] task_state=QUIT_PENDING for p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 from request_exit()
Tue Jul 23 22:57:47 EEST 2013|Einstein@Home|task p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 suspended by user
Tue Jul 23 22:39:14 EEST 2013|Einstein@Home|[task] task_state=EXECUTING for p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 from unsuspend
Tue Jul 23 22:39:14 EEST 2013||Resuming computation
Tue Jul 23 22:38:33 EEST 2013|Einstein@Home|[task] task_state=SUSPENDED for p2030.20121022.G194.54-02.45.S.b4s0g0.00000_2236_1 from suspend
Tue Jul 23 22:38:33 EEST 2013||(battery temperature 41.0 > limit 40.0 Celsius)
Tue Jul 23 22:38:33 EEST 2013||Suspending computation - battery thermal protection
I think I have the same issue with the S2, seems that it just doesn't actually continue after the battery cooled down. Did you try this with a different project or could this be BOINC related?
I think I have the same issue with the S2, seems that it just doesn't actually continue after the battery cooled down. Did you try this with a different project or could this be BOINC related?
Only tried Einstein, can't say is it BOINC client or science application related.
Also installed battery monitoring app and discovered, that during casual use (without BOINC) temperature can reach to 48°C (when charging+browsing).
Don't now, where is temp sensor actually located, but it is for sure also related to CPU activity. When BOINC works (phone plugged) battery is not active and stays cool to touch, warm area is upper part of screen, where CPU is, and sensor reading reach to limit in minutes even if phone is under massive old CPU cooler radiator. Raised 40°C limit and will try to finish current task tonight. Maybe not right hardware for crunch?
After a couple of days running this on my Android tablet I have a few things to share.
For the novice user(like me) it should be noted that when the project talks about the required version of Android needed to run this project they are talking about the Kernel your device uses, not the version of Android commonly known as 4 or 3 or whatever is on the box and how it is sold. For example my tablet's OS is Android 4.0.3 and the Kernel is 2.6.39.4 which is the one they are concerned about on this project. You have to go to setup and detailed facts on your device to discover this.
I am sure many different devices come with different sizes of RAM. Mine has 721MB of ram and with one cpu running Einstein it has 226MB free and with both 2 cpu running the project I still have 115MB of free RAM.
My only temperature sensor is on the battery and it stays between 32 and 34 degrees (C). The battery reports that .8mV is being used which is low. The CPU also shows a very low usage rate. With my ASUS tablet I don't have any problems running on just the battery. I changed the value from 90% to 70% and that allows me to be mobile for some period of time. The device has a ARMv7 processor an run at 1Ghz on this project.
I did find I needed to change the default RAM level from .100GB to a lower level to keep the second CPU running. This indicated that it needed extra memory from time to time while processing. I set mine to .05GB of RAM.
My 2 cents worth.
I recently downloaded the client from the Amazon store for my Kindle Fire HD, and I connected to Einstein@home but it just says that it's waiting for tasks, I have a 24/7 Wifi connection, I am not sure what I am doing wrong.
Unfortunately I am not going to run the official version until support is better, I will however continue to run nativeBOINC, seems to be stable enough to get computations across however the official version seems to crash the WU after a minute. I hasn't been sent yet but it will show that the WU was aborted, this is done by me when I get the accursed "computation error" in the manager.
Is anyone having this issue?
going into task manager on my GALAXY player 4.2 (YP-GI1) shows 4 to 6% CPU usage in BOINC.
is this normal?
Hi!
I would think that this is the CPU load caused by BOINC itself (GUI and potentially also the background BOINC "core client"), but does not include the load from the science app(s). There are tools that will show you the combined load on the CPUs from whatever process (so 100% if a core is fully loaded), that might be better suited to check utilization with and without BOINC running.
That's great stuff! I just installed BOINC on my Google Nexus 4 with Android 4.3 and currently I'm running my first workunit. Einstein, of course. :)
Works just fine so far.
RE: Have a problem with
)
I think I have the same issue with the S2, seems that it just doesn't actually continue after the battery cooled down. Did you try this with a different project or could this be BOINC related?
going into task manager on my
)
going into task manager on my GALAXY player 4.2 (YP-GI1) shows 4 to 6% CPU usage in BOINC.
is this normal?
RE: I think I have the same
)
Only tried Einstein, can't say is it BOINC client or science application related.
Also installed battery monitoring app and discovered, that during casual use (without BOINC) temperature can reach to 48°C (when charging+browsing).
Don't now, where is temp sensor actually located, but it is for sure also related to CPU activity. When BOINC works (phone plugged) battery is not active and stays cool to touch, warm area is upper part of screen, where CPU is, and sensor reading reach to limit in minutes even if phone is under massive old CPU cooler radiator. Raised 40°C limit and will try to finish current task tonight. Maybe not right hardware for crunch?
After a couple of days
)
After a couple of days running this on my Android tablet I have a few things to share.
For the novice user(like me) it should be noted that when the project talks about the required version of Android needed to run this project they are talking about the Kernel your device uses, not the version of Android commonly known as 4 or 3 or whatever is on the box and how it is sold. For example my tablet's OS is Android 4.0.3 and the Kernel is 2.6.39.4 which is the one they are concerned about on this project. You have to go to setup and detailed facts on your device to discover this.
I am sure many different devices come with different sizes of RAM. Mine has 721MB of ram and with one cpu running Einstein it has 226MB free and with both 2 cpu running the project I still have 115MB of free RAM.
My only temperature sensor is on the battery and it stays between 32 and 34 degrees (C). The battery reports that .8mV is being used which is low. The CPU also shows a very low usage rate. With my ASUS tablet I don't have any problems running on just the battery. I changed the value from 90% to 70% and that allows me to be mobile for some period of time. The device has a ARMv7 processor an run at 1Ghz on this project.
I did find I needed to change the default RAM level from .100GB to a lower level to keep the second CPU running. This indicated that it needed extra memory from time to time while processing. I set mine to .05GB of RAM.
My 2 cents worth.
I recently downloaded the
)
I recently downloaded the client from the Amazon store for my Kindle Fire HD, and I connected to Einstein@home but it just says that it's waiting for tasks, I have a 24/7 Wifi connection, I am not sure what I am doing wrong.
James
jswirfs-[at]-gmail.com
I figured it out, everything
)
I figured it out, everything is gold. Downloading tasks and crunching away! Woo hoo!
RE: Samsung Galaxy Ace -
)
Ah. If it works on an Ace then a Samsung Galaxy Note II will do fine.
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
Unfortunately I am not going
)
Unfortunately I am not going to run the official version until support is better, I will however continue to run nativeBOINC, seems to be stable enough to get computations across however the official version seems to crash the WU after a minute. I hasn't been sent yet but it will show that the WU was aborted, this is done by me when I get the accursed "computation error" in the manager.
Is anyone having this issue?
RE: going into task manager
)
Hi!
I would think that this is the CPU load caused by BOINC itself (GUI and potentially also the background BOINC "core client"), but does not include the load from the science app(s). There are tools that will show you the combined load on the CPUs from whatever process (so 100% if a core is fully loaded), that might be better suited to check utilization with and without BOINC running.
Cheers
HB
That's great stuff! I just
)
That's great stuff! I just installed BOINC on my Google Nexus 4 with Android 4.3 and currently I'm running my first workunit. Einstein, of course. :)
Works just fine so far.