Suddenly 2 days ago BOINC Android thinks my battery is too low and will not let anything BOINC run. It had downloaded 4 tasks from RALPH@home but they never started.

Battery was charged to 85% when I turned on the screen and BOINC is set to pause at 80% battery (see screen shot link below).

I suspect there might of been some kind of update to one or more parts of the Android OS overnight because I noticed the phone had "hard rebooted". When I turned on the screen about 5 hours after the last of the 4 tasks had downloaded.

BOINC will not let me suspend or kill the 4 tasks or suspend any active projects.

QUESTION: Should I attempt to UNINSTALL and REINSTALL BOINC to see if I can get it working again?

Here is a link to the phone from RALPH: https://ralph.bakerlab.org/show_host_detail.php?hostid=42055

OS: Android: 3.10.49-g01e0dc6 (Android V 7.0 / Kernel Version 3.10.49 / Build Number nrd90u)
HARDWARE / PHONE: LGL 158VL
CPU: (ARM V7) LGE LGL158VL - SDK:24 ABI: armeabi-v7a
BOINC client version: 7.4.53 for arm-android-linux-gnu

Below is the start up messages

Thu Sep 26 08:32:26 CDT 2019|WUProp@Home|Scheduler request completed
Thu Sep 26 08:32:24 CDT 2019|WUProp@Home|Not requesting tasks
Thu Sep 26 08:32:24 CDT 2019|WUProp@Home|Sending scheduler request: Requested by project.
Thu Sep 26 08:32:24 CDT 2019||Resuming network activity
Thu Sep 26 08:32:22 CDT 2019||Suspending network activity - not connected to WiFi network
Thu Sep 26 08:32:22 CDT 2019||(battery charge level 0.0% < threshold 80.0%
Thu Sep 26 08:32:22 CDT 2019||Suspending computation - battery low
Thu Sep 26 08:32:21 CDT 2019||Not using a proxy
Thu Sep 26 08:32:21 CDT 2019||(to change preferences, visit a project web site or select Preferences in the Manager)
Thu Sep 26 08:32:21 CDT 2019||suspend work if non-BOINC CPU load exceeds 90%
Thu Sep 26 08:32:21 CDT 2019||don't use GPU while active
Thu Sep 26 08:32:21 CDT 2019||don't compute while active
Thu Sep 26 08:32:21 CDT 2019||max disk usage: 7.61GB
Thu Sep 26 08:32:21 CDT 2019||max memory usage when idle: 1532.92MB
Thu Sep 26 08:32:21 CDT 2019||max memory usage when active: 958.07MB
Thu Sep 26 08:32:21 CDT 2019||Preferences:
Thu Sep 26 08:32:21 CDT 2019||Reading preferences override file
Thu Sep 26 08:32:21 CDT 2019|SETI@home Beta Test|URL http://setiweb.ssl.berkeley.edu/beta/
; Computer ID 86298; resource share 100
Thu Sep 26 08:32:21 CDT 2019|ralph@home|URL http://ralph.bakerlab.org/
; Computer ID 42055; resource share 500
Thu Sep 26 08:32:21 CDT 2019|WUProp@Home|URL https://wuprop.boinc-af.org/
; Computer ID 146366; resource share 1
Thu Sep 26 08:32:21 CDT 2019|Moo! Wrapper|URL http://moowrap.net/
; Computer ID 1056729; resource share 200
Thu Sep 26 08:32:21 CDT 2019|yoyo@home|URL http://www.rechenkraft.net/yoyo/
; Computer ID 442810; resource share 300
Thu Sep 26 08:32:21 CDT 2019|World Community Grid|URL http://www.worldcommunitygrid.org/
; Computer ID 4960078; resource share 1000
Thu Sep 26 08:32:21 CDT 2019|LHC@home|URL https://lhcathome.cern.ch/lhcathome/
; Computer ID 10603784; resource share 300
Thu Sep 26 08:32:21 CDT 2019|SETI@home|URL http://setiathome.berkeley.edu/
; Computer ID 8599620; resource share 200
Thu Sep 26 08:32:21 CDT 2019|Einstein@Home|URL http://einstein.phys.uwm.edu/
; Computer ID 12721973; resource share 100
Thu Sep 26 08:32:21 CDT 2019|Universe@Home|URL https://universeathome.pl/universe/
; Computer ID 506968; resource share 100
Thu Sep 26 08:32:21 CDT 2019|Asteroids@home|URL http://asteroidsathome.net/boinc/
; Computer ID 572098; resource share 300
Thu Sep 26 08:32:21 CDT 2019|Rosetta@home|URL http://boinc.bakerlab.org/rosetta/
; Computer ID 3483115; resource share 300
Thu Sep 26 08:32:21 CDT 2019||Config: report completed tasks immediately
Thu Sep 26 08:32:21 CDT 2019||Local time is UTC -5 hours
Thu Sep 26 08:32:21 CDT 2019||Disk: 10.33 GB total, 6.01 GB free
Thu Sep 26 08:32:21 CDT 2019||Memory: 1.87 GB physical, 477.04 MB virtual
Thu Sep 26 08:32:21 CDT 2019||OS: Android: 3.10.49-g01e0dc6
Thu Sep 26 08:32:21 CDT 2019||Processor features: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 evtstrm
Thu Sep 26 08:32:21 CDT 2019||Using 2 CPUs
Thu Sep 26 08:32:21 CDT 2019||Processor: 4 ARM ARMv7 Processor rev 5 (v7l)
Thu Sep 26 08:32:21 CDT 2019||Host name: android_dbb96c87
Thu Sep 26 08:32:21 CDT 2019||No usable GPUs found
Thu Sep 26 08:32:21 CDT 2019||Data directory: /data/data/edu.berkeley.boinc/client
Thu Sep 26 08:32:21 CDT 2019||Running as a daemon
Thu Sep 26 08:32:21 CDT 2019||Libraries: libcurl/7.48.0 OpenSSL/1.0.2g zlib/1.2.8.f-linuxfoundation-mods-v1
Thu Sep 26 08:32:21 CDT 2019||log flags: file_xfer, sched_ops, task
Thu Sep 26 08:32:21 CDT 2019||Starting BOINC client version 7.4.53 for arm-android-linux-gnu

Link to phone's screen shot showing the 4 tasks and the battery status message.

Thu Sep 26 08:32:22 CDT 2019||(battery charge level 0.0% < threshold 80.0%

There's your problem and if that's due to an OS update changing things around there's nothing you can do about it. Other than figure out how it was changed and recode & recompile a BOINC version using that new code.

Uninstalling & reinstalling BOINC won't help as it's a change in the OS. It won't magically teach BOINC where to look for the battery charge value now that's changed.

It's like on my phone where before under Android 8 I was able to read the full temperature range of all sensors and since Android 9 was installed that's no longer available to me.

---

UPDATE - Good news:
Uninstalled BOINC yesterday afternoon because it was causing issues with other apps on the phone from running ...
Apparently something updated again on Android OS and some apps also overnight but no hard reboot of phone...
Reinstalled BOINC BETA version this time and the battery issue is "fixed".for now.... apps are running after attaching to my favorite projects.

Update #2:
This morning when I unlocked my phone's screen BOINC was suspended - back to thinking my battery was less than 70% charged but was in fact fully charged. There have been no Android OS or other Android program updates since I reinstalled BOINC several days ago. At least what that is the Android program lists claims....

Boinc screen was unresponsive for nearly 5 minutes to any input/touch and prevented my screen from going blank. Suddenly BOINC started back up processing tasks allowing it to recognize I was trying to pause BOINC.

Once I paused BOINC I saw that 4 tasks from the RALPH project had downloaded overnight again and all 4 were trying to run at the same time. That is exactly what happened when I first started this topic.

The 4 concurrent RALPH tasks had pushed the RAM usage & storage limits to over the limit I had set of 90% for each. When I checked my RAM & storage settings from the Android OS settings screens both had less than 5% available.

I suspended 3 of the RALPH TASKS and resumed BOINC task processing with no problems the last few hours. Available RAM and free storage space were once again below the 90%.used marks after suspending 3 of the 4 RALPH tasks.

This leads me to suspect the latest RALPH program is ignoring the BOINC RAM & storage settings.
Looking at my task list on the RALPH web site I see the one task that downloaded after reinstalling BOINC got the dreaded "finish file present too long" message.

*** I will post a message on the RALPH BOARDS with link back to this topic but I highly doubt I will get any reply on their forums as they rarely do seem to read and/or reply to anything even on the ROSETTA forums. ***

>>> EDIT: I have posted a message over at the RALPH FORUMS Message 6615