We are glad to announce a new version of the MLDS application has been deployed to the server. New features include:

• Added support for datasets in INT8 format as well as Float32 (helps memory usage)
  
• ARM64/ARM32 support
  
• Update to libTorch v1.6
  
• Capture libtorch and arch information
  
• Support for Dataset 3 WUs
  
• Lots on internal improvements, including CI support
  

This release prepares us for Dataset 3 WUs, which will start trickling out over the next few days as we enter the next phase of the project. The way the clients were built has changed, so please report any issues with the new clients to the forum.

As always check the News section of the website for weekly "This Week in MLC@Home" updates, and/or follow us on Twitter at @MLCHome2.

I am very interested to hear if there are issues with the new windows app. Specifically signature errors. I ran into an unexpected issue registering the new 9.50 of the app that contains updated dlls with the same name of the original 9.20 app, and the server doesn't like two different files with the same name. Hopefully I fixed it, but please report any issues in the forums. I don't have a current windows system to test.

Definitely an issue with windows support. Disabling v9.50 for windows for now, and trying to restore v9.20 for windows only.

Also a minor regression on some amd64 hosts due to using OpenBLAS for BLAS, and it mis-detecting some CPU features, causing the client to error with "Error 4". Will spin a version 9.51 release for windows and amd64 which should fix both issues by the end of day today.

Project MLC for ARM isn't viewable on Boinc Android 10 yet.

Android is not supported. Only Linux/ARM.

This is due to linking against linux pytorch shared libraries. Compiling/supporting android is feasible, but not high on the priority list at the moment.

Note: some other projects, which can statically linked, can run the statically linked linux binaries on android. We're not statically linked (pytorch limitation).

I know this is an old post, but I have been thinking about Android support lately and am curious if an Android client is currently feasible. I have ran BOINC projects on multiple Android devices over the years and personally highly support the idea. Unfortunately, there are large barriers that would prevent many users from participating, aside from development issues and statically linking pytorch. This is the fact that the BOINC app for Android is so outdated that it does not allow users to add newer projects or account managers using URL.

I am fully aware there are work-arounds, such as using one of the 3 already included account managers, using an edited version of the APK, or using a third party BOINC client. Unfortunately, even the edited version of the APK is so old it will not run on certain devices and using an account manager is not optimal for many peoples set-up. I also reached out to the BOINC android developer last year who said they are aware of the issues and were awaiting help from someone with Android development. That was about a year ago, so I am not sure if there are any updates on that project.

This is just my 2 cents, thank you for reading!

Now that pytorch allows static linking, an android client is a possibility again... admittedly lower on the priority list at the moment, but its at least possible now.