Posts by [WHGT]Cyberman

1) Message boards : Android : How do I know if my device is too old? Is there a specific message? (Message 113822)
Posted 25 Mar 2024 by [WHGT]Cyberman
Post:
That did it - Einstein is now getting work!

Thanks!
2) Message boards : Android : How do I know if my device is too old? Is there a specific message? (Message 113810)
Posted 24 Mar 2024 by [WHGT]Cyberman
Post:
Or is the only clue that I don't get any work?

I've installed the 8.0.0 client on my old Cubot Quest Lite (Android 9) and signed up for Einstein, ralph and Rosetta. None get any work.
Maybe those projects don't have Android work right now? Or the device is too old/weak, in which case I was hoping there's a message, or log.
3) Message boards : BOINC client : Boinc on ARM devices? (Not Android, generic linux) (Message 52903)
Posted 1 Mar 2014 by [WHGT]Cyberman
Post:
The problem you face is that you not only need to get BOINC running on that eReader, but after you managed that, that Simap then also has a science application for it.

Hm.
I continually assume that the science applications are merely processor dependent, ignoring the operating system.
Damn. Too bad.
Thanks for the answer.
4) Message boards : BOINC client : Boinc on ARM devices? (Not Android, generic linux) (Message 52896)
Posted 1 Mar 2014 by [WHGT]Cyberman
Post:
Is there an easy way to get Boinc on an ARM device? "Easy" as in "download, install/unpack and run", as compared to "install using apt-get/whatever, build from source".

The reason is that I recently learned of the SIMAP project and noticed it doesn't use much resources - so while it's a waste to run SIMAP on my cell phone (better to do WCG WUs, IMO), it would be interesting to see if it'll run on my old Kobo Wifi eReader (running Linux). It does run on my ImcoV6L eReader (Android) after all...

However, all I found was attempts to get Boinc on Raspi and a few generic Debian attempts - mostly the sources, or the instruction to use apt-get to install it. :-(
5) Message boards : BOINC client : Is there (a plan for) an official version for ARM Linux (not Android) ? (Message 51966)
Posted 10 Jan 2014 by [WHGT]Cyberman
Post:
What would need to be different is the science application. I'm not sure how much would have to be done to convert 'ARM for Android' to 'ARM for Linux' - hopefully just a new cross-compilation with different compiler switches, but each project would have to do at least that much for each of their applications.

I see.
Hm. I hoped the actual calculation would be somewhat system independent.
Still, a recompile is far easier than the port to a different architecture.
Of course, the question is if it would be actually worth the trouble for them. Any device capable of crunching likely runs android already...
6) Message boards : BOINC client : Is there (a plan for) an official version for ARM Linux (not Android) ? (Message 51964)
Posted 10 Jan 2014 by [WHGT]Cyberman
Post:
I'm asking mostly out of curiosity.

There's now several projects that support ARM processors - but so far the only official Boinc client for non-x86 processors is for Android. Unless I'm wrong?

If there were a client for generic ARM linux, would it be able to make use of the ARM WUs that are currently crunched on Android?

Running Android must consume processing power too - so if this could be removed, it should make more power available to Boinc - effectively creating a dedicated Boinc device that wouldn't need much power or supervision. And should be cheap - I'm thinking single board computers, or old cell phones with the OS switched.

So, either I didn't succeed in searching the web, or my reasoning is inherently flawed, I guess?
7) Message boards : Questions and problems : Is there a portable version 7 for windows? (Message 51691)
Posted 10 Dec 2013 by [WHGT]Cyberman
Post:
I'd like to know too.
Maybe it would be possible to create a virtual machine (I read that Boinc now includes a VM?) to be used as a portable BOINC?

I'd like to use a portable Boinc with my work computer (still trying to find an opportunity to ask the admin, though :-), so it shouldn't use the internet, only the processor (or GPU if possible).



Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.