But since you're had that message, you have got Binary Radio Pulsar Search (Arecibo) selected, and you know the reason why you're not got work, see Bikeman's post earlier:
Quote:
Maybe we can lower this somewhat. The actual RAM Consumption should be somewhat lower.
I really like the support for Android, but on my Galaxy S2 it seems that it needs to be charged 12h/day so the WU can finish before the deadline :(
If this stays this way, I probably won't be using it to crunch.
Is there a way to choose smaller WUs or are they already downsized for this?
edit: OK according to my latest calculations it would be even more if the calculation rate stays as it is. Hm.
I really like the support for Android, but on my Galaxy S2 it seems that it needs to be charged 12h/day so the WU can finish before the deadline :(
If this stays this way, I probably won't be using it to crunch.
Is there a way to choose smaller WUs or are they already downsized for this?
edit: OK according to my latest calculations it would be even more if the calculation rate stays as it is. Hm.
That is a bit weird, in beta tests we found the Galaxy S2 to be quite a good cruncher. It should take around 9h CPU time, let's say 10 hours. The deadline is 14 days, so theoretically, 1 hr crunching time per day should be more than enough.
Reasons for slower throughput can include:
a) when crunching on more than one core and/or if the ambient temperatures are high, BOINC's overheating protection kicks in (at a configurable battery temperature, we do NOT recommend to change this threshold temperature). Crunching on just 1 core might help in this situation
b) if you device is attached to more than one project, BOINC has to divide the computation time between the projects, according to your resource share. BOINC needs good estimations about the run times of the different apps and usually it takes a few completed tasks for BOINC to improve the estimates with measurements of actual app crunching performance.
c) Insufficient chargers: When crunching, your phone will consume more power than in pure stand-by. Most phones reload via a cable plugged into a USB socket, but it does make a difference whether that cable is connected to a dedicated phone charger, or just the USB port of (say) a PC. USB ports are usually limited to provide 500 milli Ampere of current, while chargers will usually provide 1000mA or even 2000mA. So when you connect the phone to a USB port for charging, it's possible that running BOINC will still actually drain the battery, and BOINC will stop crunching when the configured minimum battery charge level is reached.
thanks for the suggestions, I cheked it and that's what I found out:
a) BOINC is running one task and so far nothing else at the moment, so I guess it's crunching on one core (?) I couldn't find an option to check this. The ambient room temperature is currently (I guess) about 25-28°C, but the phone or the battery itself is not warm at all, compared to the tempperature during actual charging.
b) Currently this system is only connected to Einstein@home
c) I'm using an official Samsung charger that is not connected over USB but the wall socket directly. However, it says that it's using 150mA (0.15A)... Could this be the cause? However the battery is not drained during the crunching.
edit: OK maybe I should mentioned the whole stuff, I'm not really an EE expert...
Input: 100V-240V~
50-60Hz 0.15A
Output: 5.0V - 0.7A
etc.
700mA still seems a bit low according to your definitions.
Good, you're not sending work unnecessarily to devices that don't have enough memory. Like mine: [WU#171173698 p2030.20121022.G194.79-01.99.C.b2s0g0.00000_814] needs 247.96MB RAM; [HOST#8219005] has 278.31MB, 139.15MB usable
[HOST#8219005] [WU#171173698 p2030.20121022.G194.79-01.99.C.b2s0g0.00000_814] WU is infeasible: Not enough memory
Now then, questions though:
In the same log it shows: no app version available: APP#23 (einsteinbinary_BRP5) PLATFORM#12 (arm-android-linux-gnu) min_version 0
What does that mean then?
And also --although this is possibly a BOINC question-- checking the actual hostID, it says for me IP address 127.0.0.1
Why doesn't it show the correct internal IP address 192.168.1.7 as my router and the device itself show it has?
Apropos, for those wondering, this is a Samsung Gio GT--S5660, with a whopping 278MB of memory and never enough free. If only it could use the 32GB memory card. ;-)
Also getting no work to be
)
Also getting no work to be done on an htc wildfire
RE: Also getting no work to
)
Check the project preferences for the location the htc wildfire is on.
Claggy
hmm I dont know what you
)
hmm I dont know what you mean, im in prefrences on the htc app what now ?
EDIT:
Getting binary radio pulsar search (arecibo) needs 247.96mb of ram and only 209.15mb are aviable
RE: hmm I dont know what
)
I ment the Einstein project preferences, check that you are allowing Binary Radio Pulsar Search (Arecibo) work,
But since you're had that message, you have got Binary Radio Pulsar Search (Arecibo) selected, and you know the reason why you're not got work, see Bikeman's post earlier:
Claggy
I really like the support for
)
I really like the support for Android, but on my Galaxy S2 it seems that it needs to be charged 12h/day so the WU can finish before the deadline :(
If this stays this way, I probably won't be using it to crunch.
Is there a way to choose smaller WUs or are they already downsized for this?
edit: OK according to my latest calculations it would be even more if the calculation rate stays as it is. Hm.
RE: I really like the
)
That is a bit weird, in beta tests we found the Galaxy S2 to be quite a good cruncher. It should take around 9h CPU time, let's say 10 hours. The deadline is 14 days, so theoretically, 1 hr crunching time per day should be more than enough.
Reasons for slower throughput can include:
a) when crunching on more than one core and/or if the ambient temperatures are high, BOINC's overheating protection kicks in (at a configurable battery temperature, we do NOT recommend to change this threshold temperature). Crunching on just 1 core might help in this situation
b) if you device is attached to more than one project, BOINC has to divide the computation time between the projects, according to your resource share. BOINC needs good estimations about the run times of the different apps and usually it takes a few completed tasks for BOINC to improve the estimates with measurements of actual app crunching performance.
c) Insufficient chargers: When crunching, your phone will consume more power than in pure stand-by. Most phones reload via a cable plugged into a USB socket, but it does make a difference whether that cable is connected to a dedicated phone charger, or just the USB port of (say) a PC. USB ports are usually limited to provide 500 milli Ampere of current, while chargers will usually provide 1000mA or even 2000mA. So when you connect the phone to a USB port for charging, it's possible that running BOINC will still actually drain the battery, and BOINC will stop crunching when the configured minimum battery charge level is reached.
Cheers
HBE
Installed to HTC Vivid,
)
Installed to HTC Vivid, working just fine. Already crunching data!
Suggestion for future update; a widget!
Hi HBE, thanks for the
)
Hi HBE,
thanks for the suggestions, I cheked it and that's what I found out:
a) BOINC is running one task and so far nothing else at the moment, so I guess it's crunching on one core (?) I couldn't find an option to check this. The ambient room temperature is currently (I guess) about 25-28°C, but the phone or the battery itself is not warm at all, compared to the tempperature during actual charging.
b) Currently this system is only connected to Einstein@home
c) I'm using an official Samsung charger that is not connected over USB but the wall socket directly. However, it says that it's using 150mA (0.15A)... Could this be the cause? However the battery is not drained during the crunching.
edit: OK maybe I should mentioned the whole stuff, I'm not really an EE expert...
Input: 100V-240V~
50-60Hz 0.15A
Output: 5.0V - 0.7A
etc.
700mA still seems a bit low according to your definitions.
I should get a new charger I guess?
Good, you're not sending work
)
Good, you're not sending work unnecessarily to devices that don't have enough memory. Like mine:
[WU#171173698 p2030.20121022.G194.79-01.99.C.b2s0g0.00000_814] needs 247.96MB RAM; [HOST#8219005] has 278.31MB, 139.15MB usable
[HOST#8219005] [WU#171173698 p2030.20121022.G194.79-01.99.C.b2s0g0.00000_814] WU is infeasible: Not enough memory
Now then, questions though:
In the same log it shows:
no app version available: APP#23 (einsteinbinary_BRP5) PLATFORM#12 (arm-android-linux-gnu) min_version 0
What does that mean then?
And also --although this is possibly a BOINC question-- checking the actual hostID, it says for me IP address 127.0.0.1
Why doesn't it show the correct internal IP address 192.168.1.7 as my router and the device itself show it has?
Apropos, for those wondering, this is a Samsung Gio GT--S5660, with a whopping 278MB of memory and never enough free. If only it could use the 32GB memory card. ;-)
Running fine on Nexus 7
)
Running fine on Nexus 7