One more tasks on WuProp running successful WITH REMOTE MONITORING DISABLED.

S,o, it does appear to be related to the Alpha release of Android client.

When REMOTE MONITORING ENABLED I don't get any tracking / credit for those hours in WuProp.

Let me know If it's needed, I can run a few hours of the 6 hours WuProp task with REMOTE MONITORING ENABLED to make Case for problem ticket submission.

My Data collect version 5 v5.07 (android_arm_pie) tasks are completing successfully as well. Using the new 7.18.0

Bill F

---

In October 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

Rosetta told me I needed another 2.9GB of disk space.

Rosetta needs 6675.72 MB RAM: is the restriction really needed?

I'm assuming it was one of those WU's that was coded to ask for a large amount of disk space; general consensus is they don't actually need more than 1.5 GB (and sometimes as low as ~400 MB), but they're set to expect needing ~8.5 GB.

It's a Rosetta thing.

---

https://boinc.berkeley.edu/dl/

For my devices, the one that got the Data collect version 5 v5.03 (android_arm_non_pie) tasks, they all crashed.
All later received Data collect version 5 v5.07 (android_arm_pie) run fine across the board. On everything Android 7, 8.1, 9 and 10.

I suspect you already figured it out, but the "_pie" is Android KitKat and above; "_no_pie" is KitKat and below (With KK being an in-between system that can do both, designed that way).

(I wondered when I saw it on Seti, and Wikipedia-ed it once....)

---

https://boinc.berkeley.edu/dl/

When suspending a task with tasks 'Ready to start' in queue, a new task starts to run (ok).
When resuming the suspended task the status 'suspended' keeps on the Android's device display,
but infact the status is 'Waiting to run' (I can see remotely in BoincTasks).
Only by opening the task's details on the Android device, you can notice that there's no longer a resume button and
have to guess that this means status is 'Waiting to run'. There is only the abort button, but also no pause button.
Thus locally on the android device a 'waiting to run' task can't be suspended again.

Confirmed, with screenshots. I'll call it in.

Done: #4463

CONGIRMED BUG!
New Android phone installed the 7.18.0 release. Added my projects and Wu>prop. Configure Android app for remote monitoring, After about 18 minutes added the new phone to remote monitoring on Efmers Boinctasks... let Android run to complete 1 Wu>prop task.

Wu>prop only counted the 18 minutes not remote monitoring.
See Wu>prop task 108208340

08:11:23 (16127): Erreur reception active_result
08:11:52 (16127): Erreur reception build.prop
08:12:23 (16127): Mise en veille (derniere requete date de moins de 30 secondes
08:12:23 (16127): can't connect to Unix domain socket
... >>> snip <<> ...
09:20:48 (16417): initialisation
stackdumps unavailable

Computer 208886
Operating System Android
4.9.186-21441264 (Android 10)

7.18.0 running on Android10. Phone is a Fairphone3+

Currently states waiting for battery to charge and says battery is 65% whereas going to the phones own monitoring it is 69%. I have seen a similar lag with other figures when I have checked.

Edit: Haven't seen it the other way around reporting battery more charged than it is but that doesn't mean it isn't happening.

You do know that the current version for Android is 7.18.1? Released on August 5,; 20 Days ago.

# Android client version 7.18.1 released.

You do know that the current version for Android is 7.18.1? Released on August 5,; 20 Days ago.

# Android client version 7.18.1 released.

I lied. it is 7.18.1 I am running.

Tried the latest version on 3 Androids. I get a message something like will resume when battery reaches 50% currently at 100% on 2 of the machines,and I can't get any further so will go back to 7.54.3. Both tablets are 8.01 Go Version.

Pete

So finally tried something today (because I finally figured out a particular setting today):

Two Android devices, one with data internet, the other can tether to it through hotspot/WiFi.

I figures out today how to tether the internet connection through Bluetooth (it's slower, but it's workable for things like Opera/Chrome and some YouTube). But... Boinc 7.18 can reserve new tasks, or connect to projects, but won't actually download the task files, through hotspot/Bluetooth.

---

https://boinc.berkeley.edu/dl/

What message(s) does it give when it doesn't download?

...but won't actually download the task files, through hotspot/Bluetooth.

As far as I know, only WIFI is used for the connection.

I kinda wondered, since it can add projects both ways...

---

https://boinc.berkeley.edu/dl/

After fiddling (and this is on something without mobile data):
It can download tasks, but if I uncheck the 'wifi only' option; then it'll (also) do it through the Bluetooth tethering.

(And I'm using the tethering to give a bit more control over who's specifically connected at any one time without having to change Hotspot passwords every so often to force disconnect anyone I don't want on at that particular point.)

---

https://boinc.berkeley.edu/dl/

OK, i installed 7.18.1 Boinc on all of my Androids, over 50 in number. These vary from Android 4.4 to Android 11. Now then they all work well with one exception, Android 8.01 the go edition. I have 3 of these Androids and I've tried everything to get them running but no matter what I try I get the message that it will resume computing when the battery reaches 90% currently at 100%. It would also look like the slider to adjust the battery level in preferences doesn't have any effect you still get the 90%, 100% error no matter what you adjust the battery level to. I did find that deleting the Boinc Data and Boinc cache then setting the preferences again and reinstalling the projects fixed it but this only works for a few hours sadly.

Pete

Best report this directly to BOINC Github, as then the developers can look in. I suspect it's something to do with the specific Android version, perhaps that they know a workaround.

Have you set to exclude BOINC from any memory and CPU optimizations in your Android main controls?

BOINC should not be allowed to be "put to sleep" or "optimize RAM / CPU usage" in Android.

I have been running BOINC projects on PC for awhile and wanted to make use of all the ARMv7/8 stuff I have (several SBCs, mobiles and a tablet). Those are using Android 4.4.2 to 11, all with BOINC 7.18.1. Most of them are running fine, but a couple are some pain. All of the devices are 100% dedicated to BOINC, with unnecessary stuff disabled/removed (mobiles+tablet). BOINC is excluded from optimization in all mobiles, but not in the tablet (not available) and SBCs (no need). All devices are air cooled.

Case #1
- Xiaomi Redmi Note 9 Pro (Android 11)
* Works fine when display is active, but slows down when display is inactive. May be an Android issue. Optimization settings does not seems to matter. All the other mobiles I have, do not have this issue. (None of the SBCs either.)

Case #2
- Huawei MediaPad M3 Lite 10 (Android 7)
* The same as Redmi Note 9 Pro.
* When reactivating the display on the MediaPad, the app occasionally crash. At next startup, all the running tasks have restarted from the beginning.

Case #3
- MBX MXQ (Android 4.4.2)
* BOINC installs fine and receives WUs, but refuses to do anything. Claims that battery needs to be charged above 10% (minimum setting). The MXQ have no battery and is DC supplied only. When disabling battery use in the settings, BOINC demands DC power to be connected first. At this point, BOINC is hogging the system, regardless of settings and has to be removed/uninstalled completely, before regaining the normal performance. Have also tried BOINC 7.16.5, but the same. It has been working with an earlier version, but can not recall which. Have tried BOINC 7.4.41/43 and 7.4.51/53, but all of them have other issues, like not connecting to projects. Not even with URLs. Have not checked 7.0.x, 7.1.x and 7.2.x versions.

---

[ E5-2680v4 + i9-10900K + Q9550S + A72 + A57 + A55 + A53 + A15 + A7 + A5 + Kryo 465 | 629.5GB | RTX A2000 + Quadro M6000 + Tesla M40 + GTX 1650 + UHD Graphics 630 + Tegra X1 | Lubuntu 22.04/21.04/18.04 + Debian GNU/Linux 11 + Android 4-11 ]