The BOINC GUI/client RPCs on Android use local (Unix-domain) connections instead of network (TCP/IP).
Using network connections requires that the client maintain a listening TCP socket. Google considers this a security vulnerability, and doesn't allow apps that do this to be included in Android (which we are doing via our partnership with HTC). That's why we switched to local connections on Android. The code is still there to use TCP/IP, and if someone wants to enable it and make a "remote Android" version that would be possible; but we (me and Rom) don't have time to do this right now. -- David On 15-Jan-2015 2:41 AM, John F. Kerr wrote:
Is there future plans to include mobile boinc into boinctasks? Since there is the requirement that it be connected to a local WiFi which is usually a home routed WiFi. It would be nice to see what the status is, what task are executing etc. presently you must turn on the mobile phone and this stops the boinc client. I understand that the mobile client is somewhat limited, but in my home the mobile phone is on the charger most of the day. At least the status of projects that are presently executing, waiting to execute and ready to start would be nice. _______________________________________________ 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.
_______________________________________________ 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.
