| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Android Support Forum
Thread: BOINC reboots, not resumes, after battery charges up |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 10
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
"Suspending computation - battery low
----------------------------------------(battery charge level 0.0% < threshold 90.0%" These are the last two messages when my Android 4.4.4 device has fully recharged its battery and I check it to see how BOINC 7.4.41 is doing and find BOINC has rebooted itself the moment I checked the device. android_dbed95d0 I also surmize BOINC has not resumed itself when the battery charge rises above the set threshold for resuming. This has been going on for months, at least. If this problem is in the generic part of the code, it won't go away when switching from FA@H to Ebola soon. I have already started a thread in the Ebola forum similar to this, but have been running mostly FA@H. I have read BOINC or WCG was looking to hire an Android programmer, and no new work will be done for the FA@H client, but what about having robust/reliable BOINC/client/project code for _all_ projects? [Edit, 2220 THU 21 MAY 2015 CT: added device name] [Edit 1 times, last edit by Former Member at May 22, 2015 2:20:18 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I set this device to only use three of four cores.
Now it stays charged and all is well, except it used to stay charged with all four cores running, and an identical device still stays charged while running on all four cores. Yes, I swapped the stock A/C chargers, no difference. Rebooting the device, also no difference. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I set this device to only use three of four cores. Make that two/four.Its identical other runs 4/4 cores just fine. Within a year or two I plan to replace all my dedicated rigs with 16 core devices running straight Linux, or maybe Firefox OS. That should fix 'em! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Eventually figured the battery was aging too much. Maybe not,
but removed this particular device from WCG anyway. Its "twin" is still crunching along just fine on WCG. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Batteries are said to not like the constant pass-thru charging, though must say, after 2.5 years the Lith-Ion in my I7-2670QM laptop is still managing to keep machine running for about 6 hours [albeit it's then at 900Mhz or so with dimmed display]. Some recommend to remove the battery when on mains for long.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Batteries are said to not like the constant pass-thru charging, ... My eight other tablets don't seem to mind,seven of similar age, so probably not the problem. Anyway, decided to reinstall BOINC from the Play place, but left Power Source, Battery: Disabled. So far, so good (> 20 minutes). Stock charger as usual. I was just thinking, as WiFi occasionally needs reconnecting, perhaps BOINC/tablet occasionally get confused about power. First time for me with nine tablets the last 1.5 years. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Supposedly Android M is going to extend battery use time considerably, which Lollipop 5.1 was supposed to do too [small pieces are being backported into Lollipop].
Have no complaints. Tablet goes on GPS direct & record [Navigator] when on cycle tour, plus MapMyRide to record effort [speed, elevation change, climb rate what not], plus regular stops to cam/photo-shoot and after the day's over, still 30-40 percent left. That's trips of 8-10 hours. Do swipe[kill] before that all juice sucking apps who somehow constantly try updating the GUI even when the screen is off [time out 2 minutes]. Do explicitly suspend BOINC when going out as when in the house, do walk/sit around then not minding it using the bat until down to 30% and paused when non-BOINC CPU use >50%. OET is stable enough to do that, which FAHV wasn't [on my Nexus 7 table!][End of OT even if whole or part were not ;] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
... Anyway, decided to reinstall BOINC from the Play place, Neither this, nor anything else I tried, helped.but left Power Source, Battery: Disabled. ... The device's BOINC productivity and reliability is so poor I am going to uninstall BOINC when the WU cache is empty and repurpose this device. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There can be lots of battery draining apps besides BOINC, various tools available to identify them such as CleanMaster and Battery Doctor [Can be set to give an alert if level reaches desired level, e.g. when at 100%, which I use to manually resume BOINC, which is set to stop at 30%]
|
||
|
|
NixChix
Veteran Cruncher United States Joined: Apr 29, 2007 Post Count: 1187 Status: Offline Project Badges: 
|
"Suspending computation - battery low (battery charge level 0.0% < threshold 90.0%" These are the last two messages when my Android 4.4.4 device has fully recharged its battery and I check it to see how BOINC 7.4.41 is doing and find BOINC has rebooted itself the moment I checked the device. ... I also surmize BOINC has not resumed itself when the battery charge rises above the set threshold for resuming. This has been going on for months, at least. If this problem is in the generic part of the code, it won't go away when switching from FA@H to Ebola soon. I have already started a thread in the Ebola forum similar to this, but have been running mostly FA@H. I am seeing this too, even on an old, unused device that just sits plugged into the charger 100% of the time. All other apps have been de-installed. When I pick up the phone and check the log, I find that it has just restarted, with the same battery message as quoted above. It hasn't reported to the server for the past week. I have no idea what it has been doing during that time. Added to that is impossible to meet deadlines (returned one 50 hours later and it was dubbed "too late") and you end up with a system that doesn't work. I am pulling the plug and removing BONIC from my Android devices since it is a failed experiment. Cheers   |
||
|
|
|