HI Joachim That's great. Confirmed working.
In case anyone else wants to use, here's a quick and dirty script for getting project files into the client/projects directory for anonymous platform without having to root your phone: https://www.dropbox.com/s/gln2l0nvi0m6zxa/push.txt One thing I did notice. When attaching a different project using the login interface (e.g. POGS), there's an error in the message file: "invalid or missing account key". If I attach via remote RPC command I have no problems. I believe I've pin-pointed the issue. logcat output (I've masked password with question marks): D/BOINC Client Monitor Service(29022): attachProjectAsync D/ProjectAttachAsync-doInBackground(29022): attachProjectAsync started with: http://ec2-23-23-126-96.compute-1.amazonaws.com/pogs/--dcarrio...@gmail.com-???? ?? D/RpcClient(29022): Sending request: D/RpcClient(29022): <lookup_account> *D/RpcClient(29022): <url>http://isaac.ssl.berkeley.edu/test/</url>* D/RpcClient(29022): <email_addr>dcarrio...@gmail.com</email_addr> D/RpcClient(29022): <passwd_hash>?????</passwd_hash> See *android/BOINC/src/edu/berkeley/boinc/client/Monitor.java*<http://boinc.berkeley.edu/gitweb/?p=boinc.git;a=blob;f=android/BOINC/src/edu/berkeley/boinc/client/Monitor.java;h=4637e3d5e5a7d1dc99f5c9a59a8eb06a9cf52747;hb=deab056001a771d458bec5c7e3445ba18a83390d> at line *278*: 272<http://boinc.berkeley.edu/gitweb/?p=boinc.git;a=blob;f=android/BOINC/src/edu/berkeley/boinc/client/Monitor.java;h=4637e3d5e5a7d1dc99f5c9a59a8eb06a9cf52747;hb=deab056001a771d458bec5c7e3445ba18a83390d#l272> public AccountOut lookupCredentials(String url, String id, String pwd) { 273<http://boinc.berkeley.edu/gitweb/?p=boinc.git;a=blob;f=android/BOINC/src/edu/berkeley/boinc/client/Monitor.java;h=4637e3d5e5a7d1dc99f5c9a59a8eb06a9cf52747;hb=deab056001a771d458bec5c7e3445ba18a83390d#l273>Integer retval = -1; 274<http://boinc.berkeley.edu/gitweb/?p=boinc.git;a=blob;f=android/BOINC/src/edu/berkeley/boinc/client/Monitor.java;h=4637e3d5e5a7d1dc99f5c9a59a8eb06a9cf52747;hb=deab056001a771d458bec5c7e3445ba18a83390d#l274>AccountOut auth = null; 275<http://boinc.berkeley.edu/gitweb/?p=boinc.git;a=blob;f=android/BOINC/src/edu/berkeley/boinc/client/Monitor.java;h=4637e3d5e5a7d1dc99f5c9a59a8eb06a9cf52747;hb=deab056001a771d458bec5c7e3445ba18a83390d#l275>AccountIn credentials = new AccountIn(); 276<http://boinc.berkeley.edu/gitweb/?p=boinc.git;a=blob;f=android/BOINC/src/edu/berkeley/boinc/client/Monitor.java;h=4637e3d5e5a7d1dc99f5c9a59a8eb06a9cf52747;hb=deab056001a771d458bec5c7e3445ba18a83390d#l276>credentials .email_addr = id; 277<http://boinc.berkeley.edu/gitweb/?p=boinc.git;a=blob;f=android/BOINC/src/edu/berkeley/boinc/client/Monitor.java;h=4637e3d5e5a7d1dc99f5c9a59a8eb06a9cf52747;hb=deab056001a771d458bec5c7e3445ba18a83390d#l277>credentials .passwd = pwd; 278<http://boinc.berkeley.edu/gitweb/?p=boinc.git;a=blob;f=android/BOINC/src/edu/berkeley/boinc/client/Monitor.java;h=4637e3d5e5a7d1dc99f5c9a59a8eb06a9cf52747;hb=deab056001a771d458bec5c7e3445ba18a83390d#l278>credentials .url = getString(R.string.project_url); I believe that should just be "url" instead of getting the project_url string which defaults to isaac or am I reading this wrong? A few other little things: - Possible masking of passwords from LOG.d output in java code? - If you uninstall BOINC apk the boinc command hangs around running and won't die until the user restarts their phone. Regards Daniel On Sun, Jan 20, 2013 at 11:45 PM, Joachim Fritzsch < joachim.fritz...@gmail.com> wrote: > I have uploaded a new test build of the current master branch to: > http://fridgelike.com/boinc/BOINC.apk > > Daniel: This package is unsigned, debuggable should therefore be set to > true. > > If Roms build is installed on the device, remove it and restart device > first before installing this one. (package conflict) > > Cheers, > > Joachim > > > On Sat, Jan 19, 2013 at 11:10 AM, Joachim Fritzsch < > joachim.fritz...@gmail.com> wrote: > >> >> >> On Fri, Jan 18, 2013 at 12:49 PM, Daniel Carrion <dcarrio...@gmail.com>wrote: >> >>> Managed to get this working with POGS using anonymous platform, as the >>> project currently doesn't support ARM natively. Few things I had to do: >>> >>> - Gain root access using modded boot - this is just something I do when >>> working in restricted locations. I revert back later. >>> - Add /data/data/edu.berkeley.boinc/client/remote_hosts.cfg so I can send >>> project attach commands using remote UI. >>> - Dump POGS project files into >>> >>> /data/data/edu.berkeley.boinc/client/projects/ec2-23-23-126-96.compute-1.amazonaws.com_pogs >>> - Send attach command remotely for project (no built in option at >>> present). >>> - Modified computing preferences to always allow network activity and run >>> whilst on batteries etc... Some reason this didn't set for newly attach >>> project. >>> >>> Some things that I noticed: >>> >>> - When the screen dims it sets all tasks to "waiting" except one that >>> runs >>> in high priority. >>> >> >> Interesting. We might need to use a CPU mode lock as provided by >> android.os.PowerManager class. I will investigate this... >> >> >>> - When force closing the app, the BOINC client hangs around in the >>> background. This I noticed from running a ps inside my SSH shell to my >>> phone. >>> >> >> That is true. Force closing kills the VM process. BOINC client is not >> inside the VM. If Android closes an app, it calls its onDestroy() method >> and one could close the Client in code, this does not happen if you force >> kill it. Anyway, re-opening the BOINC application, it connects to the >> previously started Client. So the process does not get abandoned or >> uncontrollable. >> >> >>> >>> Overall seems very promising. Great work! I'm guessing we'll be seeing >>> project command features and further computing/network tweaking >>> capabilities in the future? Is there any chance of modifying the default >>> manifest to include android:debuggable="true" so we can use adb shell >>> run-as edu.berkeley.boinc? I don't use this feature, but there might be >>> some out there that don't want to compile their own apk and want to debug >>> this way using your version. >>> >> >> I will include the debugable flag in the next commit. >> >> >>> Here are a couple screenshots of POGS crunching on your test version: >>> >>> https://www.dropbox.com/s/zfzi2uydh30sc59/pogs_berkeley_android1.png >>> https://www.dropbox.com/s/lz019q27f7orjj0/pogs_berkeley_android2.png >>> >>> If you need a hand doing further testing or whatever let me know. I'm >>> very >>> keen on ARM related projects. >>> >>> Cheers >>> >>> Daniel >>> >>> >>> On Fri, Jan 18, 2013 at 8:25 PM, Daniel Carrion <dcarrio...@gmail.com >>> >wrote: >>> >>> > Thanks for the response. Sounds great. >>> > >>> > I've loaded it up on my Samsung Galaxy S3 and managed to run some work >>> > units from the test site just fine - >>> > http://isaac.ssl.berkeley.edu/test/results.php?hostid=674 >>> > >>> > I'm going to see if I can get some theSkyNet POGS WUs running under >>> this >>> > version. I'll post back. >>> > >>> > I'd also like to take a look at the VM used for development when it >>> gets >>> > posted up, as I'm currently running a mix of different SDK/NDKs - >>> mainly >>> > because of the gfortran toolchain requirement for POGS main app. >>> > >>> > Cheers >>> > >>> > Daniel >>> > >>> > >>> > On Fri, Jan 18, 2013 at 3:35 AM, David Anderson < >>> da...@ssl.berkeley.edu>wrote: >>> > >>> >> Daniel: >>> >> >>> >> The software described in Rom's email (which I'll call "BOINC on >>> Android") >>> >> is a version of BOINC for Android developed and supported by >>> >> the BOINC project. This means that: >>> >> >>> >> - It's part of the BOINC software distribution. >>> >> - It's released under the same license as the rest of BOINC. >>> >> - It will be maintained by the BOINC project (as long as we exist). >>> >> >>> >> BOINC on Android has the same architecture as on other platforms: >>> >> a client and a GUI that communicate over TCP. >>> >> The client is standard; it's built from the same source as other >>> >> platforms. >>> >> As we extend and debug the BOINC client, >>> >> these changes will automatically appear in the Android version. >>> >> The GUI is new, and uses the Android GUI toolkit. >>> >> It's a work in progress, and may change a lot in the future. >>> >> >>> >> BOINC on Android was developed by Joachim Fritzsch as a Google >>> >> Summer of Code project in 2012. >>> >> He's continuing to work on it (supported by Einstein@home) >>> >> and Rom will also be working on it. >>> >> We hope to get other contributors as well. >>> >> >>> >> Functionally, BOINC on Android is similar to Mateusz Szpakowski's >>> >> NativeBOINC. >>> >> Mateusz chose to work independently of us, >>> >> and he made some architectural decisions different from ours. >>> >> >>> >> From a project point of view, there should be no difference between >>> >> NativeBOINC and BOINC on Android; >>> >> if a project provides applications for platform >>> "arm-android-linux-gnu", >>> >> they should work with either client. >>> >> >>> >> --------- >>> >> >>> >> App stores: yes, we hope to get BOINC on Android in Google Play >>> >> and other Android app stores. >>> >> >>> >> -- David >>> >> >>> >> On 17-Jan-2013 8:25 AM, Daniel Carrion wrote: >>> >> > ... >>> >> > I'm very curious about this new version and if it ties in at all >>> with >>> >> what >>> >> > NativeBOINC has been doing. Would be a bit of a pain having two >>> >> different >>> >> > clients that essentially do the same thing with their own separate >>> bugs, >>> >> > quirks and features. >>> >> > >>> >> > Very curious if there's intentions to get this released to the >>> Google's >>> >> > Play store and if so how it's going to be approved with project >>> binaries >>> >> > running a muck. :) >>> >> > >>> >> > Cheers >>> >> > >>> >> > Daniel >>> >> _______________________________________________ >>> >> boinc_dev mailing list >>> >> boinc_dev@ssl.berkeley.edu >>> >> 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 >>> boinc_dev@ssl.berkeley.edu >>> 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 boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
