-------- Original Message --------
Subject: Re: [boinc_dev] Report on use of Berkeley Android for BOINC.
Date: Wed, 13 Mar 2013 08:58:41 +0100
From: Filip Rydlo <[email protected]>
To: David Anderson <[email protected]>
Yeah, just write a "virtual storage" like Microsoft for very-old or even DOSbox
games / apps that are trying to write savegames into their program files
directory! :)
Detect executables, just virtually store them in the slot on SD card... But
in fact they are physically on internal.
Tell them their data are there: ext.mem.card in the slot :)
Hehe :)
A.H.O.Y.
Filip
Dne 12.3.2013 21:46 "David Anderson" <[email protected]
<mailto:[email protected]>> napsal(a):
In BOINC for Android, one of the goals is to dynamically
download and run client applications, as on other platforms.
Android external storage, by default, can't be used for executable files.
So the boinc/projects/ directory must be on internal storage.
Notes:
- in principle we could split the project directories:
one part for executables, another for data files.
Data files could go on external storage.
However, this would be a large rewrite.
- slot directories could go on external storage,
but there's no advantage because they just contain
links to the project directory.
On 12-Mar-2013 12:25 PM, Rom Walton wrote:
IIRC, the default mode of operation for NativeBOINC is to run all
applications as anonymous platform applications. From an eco-system
perspective it kind of limits NativeBOINC to running applications that
are
OSS software.
Now this is probably the result of a chicken/egg problem where projects
were not quite as ready to jump on the Android bandwagon. Anonymous
platform
was the only route left open.
Several projects use software that is not OSS software in nature.
Anyways, we'll be flipping the bit that allows for external memory
installs
And see what happens.
According to this (section: android:installLocation)
http://developer.android.com/__guide/topics/manifest/__manifest-element.html
<http://developer.android.com/guide/topics/manifest/manifest-element.html>
even if the apk file is stored on the SD card, the data directory which
allows
for native applications to have the execute bit set, is still setup in
internal memory. So it may well be that NativeBOINC and the BOINC
package we
are putting together have the same limitations as far as phones with
smaller
memory sizes goes.
Or they may both be operating under a different set of constraints due
to how
project applications are installed with the anonymous platform
mechanism.
We just need to try and see what happens.
----- Rom
-----Original Message-----
From: boinc_dev [mailto:boinc_dev-bounces@ssl.__berkeley.edu
<mailto:[email protected]>] On Behalf Of Raistmer the
Sorcerer
Sent: Tuesday, March 12, 2013 6:51 AM
To: Jorden van der Elst
Cc: BOINC Dev Mailing List
Subject: Re: [boinc_dev] Report on use of Berkeley Android for BOINC.
Does "official" BOINC supports installation on SD card instead of
inner phone memory?
NativeBOINC does. And w/o this feature such BOINC just useless for vast
majority of smartphones (no direct access to inner memory, too low
amount of inner memory and so on and so forth).
Actually current NativeBOINC state is close to perfection from features
point of view. User can "just crunch" with it, not to fight with some
missings and bugs. The main issue now is lack of scientific
applications ports.
Вторник, 12 марта 2013, 11:37 +01:00 от Jorden van der Elst
<[email protected] <mailto:[email protected]>>:
Hi all,
In http://boinc.berkeley.edu/dev/__forum_thread.php?id=8246
<http://boinc.berkeley.edu/dev/forum_thread.php?id=8246> the user
NullCoding writes:
"Cutting to the chase:
I was unable to find any information about how to run BOINC on
Android
- specifically, using the official Berkeley installer (.apk) on not
a
tablet, but a smartphone.
Granted, my particular phone is often referred to as a "fablet" (or
"phablet?") i.e. "phone-tablet," as it's rather large in size. The
screen itself is larger than an iPhone 4S. I have an HTC Droid DNA,
which is comparable to the perhaps more commonly-seen Samsung Galaxy
SIII. They are like a Nikon DSLR and a Canon DSLR. When it comes to
brass tacks, hard to pick a clear winner.
In any case I happen to know my phone has a "quad-core CPU."
Granted,
I'm not entirely sure there are even any apps for Android in
existence
which can actually address all four...but I thought that if anything
could, it'd be BOINC (hopefully).
I also happen to know that many, many people run / have run /
continue
to run BOINC on their smartphones - often models older than mine!
However, I installed the BOINC package from Berkeley (which I do
recognize is a development release) and attached to a few projects
that
I knew to support Android.
All I'm getting is "This project does not support computers of type
arm-android-linux-gnu."
hmm?
That and there's no way to edit computing preferences (I will NOT
"root" my device - afraid I can't go into the exact reasons here
though) that I can see, so for all I know it IS recognizing "four
cores" but only using one, which I believe is the default setup (use
"0%" of multi-core systems, i.e one core) Here is my "host" at
SubSetSum, which was specifically recommended to me for Android.
Here is another "host" at the same project with what appears to be
an
older (albeit apparently faster) CPU as well as an older OS, and
it's
gotten more credit than my quad-core i5-2350M 2,3GHz has in less
calendar time! O_o
What on earth am I doing wrong here?
I assume I need to use an anonymous platform, but without direct
access
to the /data/ directory, I see no way so to do.
I also assume I need to change my computing preferences, but I
cannot
find a way to do that either.
I know there are other versions of BOINC for Android out there, but
it's late and I'm just gonna leave this here for now and experiment
with other apps tomorrow.
If I'm missing something obvious, please be nice about it...I tend
to
blow things out of proportion until I end up blaming things like
overheated DIMMs and unstable overclocking and other irrelevant
things.
tl;dr they told me this is a super-powerful phone; they are
correct; it
won't crunch; I would like it to; halp"
And:
" Oh felt I should mention that in the meantime I am simply using
NativeBOINC, which appears to be working properly thus far.
If it's simply a matter of the official Berkeley version missing
some
kind of feature set specifically for my kind of phone, okay.
So it looks like this on a project. Cool.
All that said, I'm definitely interested in the porting of BOINC to
Android in some kind of native form. I will definitely keep up with
the
progress and all!"
Someone may want to swing by on him and tell about the state of the
client and its support.
I've given the Wiki links with (some of) the documentation.
--
-- Jord van der Elst.
_________________________________________________
boinc_dev mailing list
[email protected] <mailto:[email protected]>
http://lists.ssl.berkeley.edu/__mailman/listinfo/boinc_dev
<http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev>
To unsubscribe, visit the above URL and (near bottom of page) enter
your email address.
_________________________________________________
boinc_dev mailing list
[email protected] <mailto:[email protected]>
http://lists.ssl.berkeley.edu/__mailman/listinfo/boinc_dev
<http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev>
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_________________________________________________
boinc_dev mailing list
[email protected] <mailto:[email protected]>
http://lists.ssl.berkeley.edu/__mailman/listinfo/boinc_dev
<http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev>
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_________________________________________________
boinc_dev mailing list
[email protected] <mailto:[email protected]>
http://lists.ssl.berkeley.edu/__mailman/listinfo/boinc_dev
<http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev>
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
