-----
Samsung Galaxy A52s 5G
Snapdragon 778G
One UI 5.1 (Android 13)
Boinc 7.22.2
-----

Hello!

I'm having an issue with the Boinc app on Android. There seems to be a bug or problem that is preventing the app from executing tasks properly.

I had been using version 7.18 of Boinc for several months and the bug was already present. I decided to update to the newest version, hoping that the issue would be resolved, but now it's even worse than before.

Here's what happens: I start or resume computation and everything goes well for a few minutes. Then, the bug triggers the minimum battery level and I receive an error message that says:


`battery charge level 0.0% < threshold 31.0%`

`Suspending computation - battery low`


Clearly, something is wrong here since my phone's battery is never at 0.0%. I always get the same error, regardless of the actual battery level.

Any help would be greatly appreciated because, at the moment, I am unable to execute any tasks.

Thank you.

Here are the logs from the client and the GUI:




CLIENT LOG

5 jul 2023 9:35:13||(battery charge level 0.0% < threshold 31.0%

5 jul 2023 9:35:13||Suspending computation - battery low

5 jul 2023 9:35:13||Checking presence of 57 project files

5 jul 2023 9:35:13||Setting up GUI RPC socket

5 jul 2023 9:35:13|World Community Grid|URL http://www.worldcommunitygrid.org/; Computer ID 8714668; resource share 0

5 jul 2023 9:35:13|Rosetta@home|URL https://boinc.bakerlab.org/rosetta/; Computer ID 6257239; resource share 100

5 jul 2023 9:35:13|BOINC Central|URL https://boinc.berkeley.edu/central/; Computer ID 6283; resource share 100

5 jul 2023 9:35:13||Checking active tasks

5 jul 2023 9:35:13||Setting up project and slot directories

5 jul 2023 9:35:13||- (to change preferences, visit a project web site or select Preferences in the Manager)

5 jul 2023 9:35:13||- max disk usage: 62.66 GB

5 jul 2023 9:35:13||- Store up to an additional 0.50 days of work

5 jul 2023 9:35:13||- Store at least 0.10 days of work

5 jul 2023 9:35:13||- Suspend if no input in last 60.000000 minutes

5 jul 2023 9:35:13||- max memory usage: 5.24 GB

5 jul 2023 9:35:13||- suspend if non-BOINC CPU load exceeds 100%

5 jul 2023 9:35:13||- Use at most 100% of the CPU time

5 jul 2023 9:35:13||- max CPUs used: 2

5 jul 2023 9:35:13||- When computer is not in use

5 jul 2023 9:35:13||- max memory usage: 5.24 GB

5 jul 2023 9:35:13||- suspend if non-BOINC CPU load exceeds 100%

5 jul 2023 9:35:13||- Use at most 100% of the CPU time

5 jul 2023 9:35:13||- max CPUs used: 2

5 jul 2023 9:35:13||- don't use GPU

5 jul 2023 9:35:13||- don't compute

5 jul 2023 9:35:13||- 'In use' means mouse/keyboard input in last 3.0 minutes

5 jul 2023 9:35:13||- When computer is in use

5 jul 2023 9:35:13||Preferences:

5 jul 2023 9:35:13||Reading preferences override file

5 jul 2023 9:35:13||Config: report completed tasks immediately

5 jul 2023 9:35:13||Local time is UTC +2 hours

5 jul 2023 9:35:13||Disk: 106.31 GB total, 62.64 GB free

5 jul 2023 9:35:13||Memory: 5.24 GB physical, 6.00 GB virtual

5 jul 2023 9:35:13||OS: Android: 5.4.210-qgki-25904254-abA528BXXU4EWE4

5 jul 2023 9:35:13||Processor features: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp

5 jul 2023 9:35:13||Processor: 8 ARM [Impl 0x41 Arch 8 Variant 0x2 Part 0xd05 Rev 0]

5 jul 2023 9:35:13||Host name: Snapdragon 778G - Samsung Galaxy A52s 5G

5 jul 2023 9:35:12||No usable GPUs found

5 jul 2023 9:35:11||Data directory: /data/user/0/edu.berkeley.boinc/client

5 jul 2023 9:35:11||Running as a daemon

5 jul 2023 9:35:11||Libraries: libcurl/8.0.1-DEV OpenSSL/3.1.0 zlib/1.2.13

5 jul 2023 9:35:11||log flags: file_xfer, sched_ops, task

5 jul 2023 9:35:11||Starting BOINC client version 7.22.2 for aarch64-android-linux-gnu


----


GUI LOG


Mensajes de la GUI

07-05 09:35:34.874 V/BOINC_GUI(10261): [CLIENT] ClientNotification: notification needs update? false false false false false
07-05 09:35:34.873 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): computation enabled: true
07-05 09:35:34.873 V/BOINC_GUI(10261): [CLIENT] setClientStatus: #results: 2 #projects: 3 #transfers: 0 // computing: computingParseError: false computingStatus: 3 computingSuspendReason: 0 - network: networkParseError: false networkStatus: 2 networkSuspendReason: 0
07-05 09:35:34.869 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): screen on, get complete status
07-05 09:35:34.868 V/BOINC_GUI(10261): [MONITOR] reportDeviceStatus()
07-05 09:35:33.903 V/BOINC_GUI(10261): [CLIENT] ClientNotification: notification needs update? false false false false false
07-05 09:35:33.903 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): computation enabled: true
07-05 09:35:33.902 V/BOINC_GUI(10261): [CLIENT] setClientStatus: #results: 2 #projects: 3 #transfers: 0 // computing: computingParseError: false computingStatus: 3 computingSuspendReason: 0 - network: networkParseError: false networkStatus: 2 networkSuspendReason: 0
07-05 09:35:33.872 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): screen on, get complete status
07-05 09:35:33.868 V/BOINC_GUI(10261): [MONITOR] reportDeviceStatus()
07-05 09:35:32.875 V/BOINC_GUI(10261): [CLIENT] ClientNotification: notification needs update? false false false false false
07-05 09:35:32.875 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): computation enabled: true
07-05 09:35:32.874 V/BOINC_GUI(10261): [CLIENT] setClientStatus: #results: 2 #projects: 3 #transfers: 0 // computing: computingParseError: false computingStatus: 3 computingSuspendReason: 0 - network: networkParseError: false networkStatus: 2 networkSuspendReason: 0
07-05 09:35:32.868 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): screen on, get complete status
07-05 09:35:32.867 V/BOINC_GUI(10261): [MONITOR] reportDeviceStatus()
07-05 09:35:31.873 V/BOINC_GUI(10261): [CLIENT] ClientNotification: notification needs update? false false false false false
07-05 09:35:31.873 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): computation enabled: true
07-05 09:35:31.873 V/BOINC_GUI(10261): [CLIENT] setClientStatus: #results: 2 #projects: 3 #transfers: 0 // computing: computingParseError: false computingStatus: 3 computingSuspendReason: 0 - network: networkParseError: false networkStatus: 2 networkSuspendReason: 0
07-05 09:35:31.868 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): screen on, get complete status
07-05 09:35:31.867 V/BOINC_GUI(10261): [MONITOR] reportDeviceStatus()
07-05 09:35:30.872 V/BOINC_GUI(10261): [CLIENT] ClientNotification: notification needs update? false false false false false
07-05 09:35:30.872 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): computation enabled: true
07-05 09:35:30.872 V/BOINC_GUI(10261): [CLIENT] setClientStatus: #results: 2 #projects: 3 #transfers: 0 // computing: computingParseError: false computingStatus: 3 computingSuspendReason: 0 - network: networkParseError: false networkStatus: 2 networkSuspendReason: 0
07-05 09:35:30.868 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): screen on, get complete status
07-05 09:35:30.866 V/BOINC_GUI(10261): [MONITOR] reportDeviceStatus()
07-05 09:35:29.871 V/BOINC_GUI(10261): [CLIENT] ClientNotification: notification needs update? false false false false false
07-05 09:35:29.871 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): computation enabled: true
07-05 09:35:29.871 V/BOINC_GUI(10261): [CLIENT] setClientStatus: #results: 2 #projects: 3 #transfers: 0 // computing: computingParseError: false computingStatus: 3 computingSuspendReason: 0 - network: networkParseError: false networkStatus: 2 networkSuspendReason: 0
07-05 09:35:29.867 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): screen on, get complete status
07-05 09:35:29.865 V/BOINC_GUI(10261): [MONITOR] reportDeviceStatus()
07-05 09:35:28.870 V/BOINC_GUI(10261): [CLIENT] ClientNotification: notification needs update? false false false false false
07-05 09:35:28.870 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): computation enabled: true
07-05 09:35:28.870 V/BOINC_GUI(10261): [CLIENT] setClientStatus: #results: 2 #projects: 3 #transfers: 0 // computing: computingParseError: false computingStatus: 3 computingSuspendReason: 0 - network: networkParseError: false networkStatus: 2 networkSuspendReason: 0
07-05 09:35:28.866 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): screen on, get complete status
07-05 09:35:28.865 V/BOINC_GUI(10261): [MONITOR] reportDeviceStatus()
07-05 09:35:27.872 V/BOINC_GUI(10261): [CLIENT] ClientNotification: notification needs update? false false false false false
07-05 09:35:27.872 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): computation enabled: true
07-05 09:35:27.871 V/BOINC_GUI(10261): [CLIENT] setClientStatus: #results: 2 #projects: 3 #transfers: 0 // computing: computingParseError: false computingStatus: 3 computingSuspendReason: 0 - network: networkParseError: false networkStatus: 2 networkSuspendReason: 0
07-05 09:35:27.868 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): screen on, get complete status
07-05 09:35:27.865 V/BOINC_GUI(10261): [MONITOR] reportDeviceStatus()
07-05 09:35:26.878 V/BOINC_GUI(10261): [CLIENT] ClientNotification: notification needs update? false false false false false
07-05 09:35:26.878 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): computation enabled: true
07-05 09:35:26.873 V/BOINC_GUI(10261): [CLIENT] setClientStatus: #results: 2 #projects: 3 #transfers: 0 // computing: computingParseError: false computingStatus: 3 computingSuspendReason: 0 - network: networkParseError: false networkStatus: 2 networkSuspendReason: 0
07-05 09:35:26.864 V/BOINC_GUI(10261): [MONITOR] readClientStatus(): screen on, get complete status
07-05 09:35:26.863 V/BOINC_GUI(10261): [MONITOR] reportDeviceStatus()

---

José Ángel

I think it's best you post a bug report issue at https://github.com/BOINC/boinc/issues, especially as it differs from #4873, doesn't it?

Hello Jord!

You are right. I will post a bug report at Github.

Thank you.

---

José Ángel

Newest version won't work as you get the dreaded battery level message. You have to go back to 7.1.1 version which is no longer on the Boinc site and I had to toot around to ffind it.

That should read 7.18.1

Known bug, see #5305 for progress on its development.

I'm glad I found this topic in fact!

I encountered this bug on Android version 11, and running BOINC version 7.24.1.

First time I noticed it a few days ago due to my lack of checking the charge being run down, it was so intrusive that powering the phone off just wouldn't reinitialize the suspended tasks!

I had to do a Reset on the project after the phone was fully charged and restarted, and then it would begin getting new tasks again and they would work.

Well, after playing in those Android battery settings, I might have found a way to 'undo' the suspend lock. I toggled the following two settings, and tasks all started from where they were! Here are the options I changed:

First thing I did was:

System Settings -> Battery and device care -> tap on Battery (the option above Storage): it opens up the Battery menu. -> Background usage limits -> Never sleeping apps -> Add+ BOINC app to this list.

Second thing I did was:

In the same Battery menu above, scroll down below the "Usage since last full charge" section graph/data: you will see More battery settings. -> Adaptive battery -> Off

Don't know which one of those worked, maybe someone can test this and see if they reach the same conclusion as I did.

Best wishes,
Dave.

This is a KNOWN BUG in the more recent Android operating system versions and the BOINC developers are aware of it.
Battery charge level 0.0% < threshold 31.0% #5305
In the meanwhile, please check that:

1) BOINC is in the exceptions of Android Battery Saving list.
2) BOINC is always on the foreground (especially when the screen is off).

Not to sound argumentative, but in fact my previous post just seemed to inactivate my methods I got working before.

I can't even find one of those two settings you mentioned. I would question why Android chose to obfuscate things.

Still not to worry.

Just for the sheer confusion and waste of time/WUs around this affair, I have uninstalled.

I'll just keep my PC running it instead from now on. Thanks for trying to advise though.