| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: Android Support Forum
Thread: Older versions of Android |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 15
|
|
| Author |
|
|
Coleslaw
Veteran Cruncher USA Joined: Mar 29, 2007 Post Count: 1343 Status: Offline Project Badges: 
|
I don't recall, but does WCG block server side older Android clients from downloading work? I ask because I had one of my really old devices recently power up and it downloaded some OET work (which obviously failed for not being PIE cabpable). Notice this is Android v. 2.3.6
----------------------------------------I can remove the device once I figure out which one in my pile of 30'ish phones it is, but just wanted to know if it fell through the WCG cracks or if it is still up to the users to monitor. Device name: android_f7c4f557 OET1_ 0003799_ x4O6HchD_ rig_ 63318_ 0-- 2.6.35.7-1209670 (Android 2.3.6) <core_client_version>7.4.37</core_client_version> <![CDATA[ <message> process got signal 11 </message> <stderr_txt> </stderr_txt> ]]>     |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
OS it could test if minimal compliant, clients it does not, so your report indicates. It's good, for how would WCG test if a self-build from the open source code complies or not and to what? It's the science app that does the execution, not the agent.
----------------------------------------Now testing the OS is a resource problem too. If you visit BOINCStats http://boincstats.com/en/stats/15/host/breakdown/os/0/0/1000, WCG by OS, you see there are like 10,000+ versions of Android in circulation. 2 cent thoughts. [Edit 1 times, last edit by SekeRob* at May 19, 2016 3:41:41 PM] |
||
|
|
Coleslaw
Veteran Cruncher USA Joined: Mar 29, 2007 Post Count: 1343 Status: Offline Project Badges:
|
Yeah, but isn't there a way to filter server side an OS version requirement? So, for example, if it doesn't have at least Android 4.1 it gets no work or just blocked altogether? I personally don't know, but figured there would be a way as I did see someone else failed that same task because they had Android 4.0.3
----------------------------------------I just figured if they could block it, then there would be a lot less data transfers, failed work units, etc... as the majority of these users are not compiling anything themselves. And IIRC, you need Android 4.1+ to be PIE capable. [Edit 4 times, last edit by Coleslaw at May 19, 2016 4:01:32 PM] |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Falls in the knreed department, and yes, it would reduce the error rate. The thought I expressed was, if you have to test 10,000 OS versions on yes/no, what is more costly... just let it fail on the host [in the first few seconds], or the scheduler load increase? Maybe maybe, such a test could be applied at point of project attaching I suppose, but how to convey that message in the client? At any rate, the System Requirement page does tell, so the system is relying on member self discovery for the moment https://www.worldcommunitygrid.org/help/viewTopic.do?shortName=minimumreq
|
||
|
|
Coleslaw
Veteran Cruncher USA Joined: Mar 29, 2007 Post Count: 1343 Status: Offline Project Badges:
|
You shouldn't really have to test 10,000 OS versions as we already know that anything lower than 4.1 should indeed fail (unless a very unique build) because they don't have the PIE requirement. So, sure during first attach it may detect. Yes detecting when calling for work could be extra load, but projects already reference hardware/software requirements when asking for work. Otherwise, I would not get notices saying no available work for your device type (or whatever the actual lingo is) when there is only work for competing OS's... So it should be doable.
----------------------------------------[Edit 1 times, last edit by Coleslaw at May 19, 2016 4:17:12 PM] |
||
|
|
SiKTheGreatOne
Cruncher Joined: Aug 4, 2009 Post Count: 24 Status: Offline Project Badges: 
|
My OUYA console with version 3.1.10 is still chugging along just fine. Would anything change in the future for it not to be supported? I side-loaded an early version of BOINC for Android on it almost two years ago and haven't updated it since.
----------------------------------------Edit: Version 3.1.10 as reported by BOINC may not correlate to the actual Android version. For instance, my Motorola Xoom says Android 2.6.39.4-g4e32b94 (Android 4.1.2) according to WUProp.  [Edit 1 times, last edit by SiKTheGreatOne at Jun 5, 2016 6:36:22 AM] |
||
|
|
Coleslaw
Veteran Cruncher USA Joined: Mar 29, 2007 Post Count: 1343 Status: Offline Project Badges:
|
3.4.0 was actually Android 4.3.0 or 4.4.0 depending on device
----------------------------------------3.4.67 was 4.4.2 3.0.8 was 4.0.4 3.10.49 was 5.1 3.4.42 was 4.4.4 2.6.35.7 was 2.3.6 And those are just some I've checked from all the devices on my list that report both numbers. Edit: So odds are, your Ouya is using Android 4.1 or newer which supports PIE. [Edit 2 times, last edit by Coleslaw at Jun 5, 2016 11:30:50 PM] |
||
|
|
TruboXL
Cruncher Malaysia Joined: Nov 22, 2015 Post Count: 29 Status: Offline Project Badges: 
|
I personally think that Google Play itself already blocks majority Androids below 4.1...
Any method to obtain BOINC throuugh 3rd party sites is the one that leaks through the block... Also don't forget there's NativeBOINC which allows Androids as low as 2.3 to install without warring project units need 4.1+ PIE support... NativeBOINC should really up their requirements now if all projects moved to PIE already... |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Problem is, NB has gone unmaintained since long as I can remember, itself needing recompiling to comply to PIE [it wont install as of Android 5.0], a reason why some members linger on something between a droid 4.1 and 4.4
|
||
|
|
Coleslaw
Veteran Cruncher USA Joined: Mar 29, 2007 Post Count: 1343 Status: Offline Project Badges:
|
I personally think that Google Play itself already blocks majority Androids below 4.1... Any method to obtain BOINC throuugh 3rd party sites is the one that leaks through the block... Also don't forget there's NativeBOINC which allows Androids as low as 2.3 to install without warring project units need 4.1+ PIE support... NativeBOINC should really up their requirements now if all projects moved to PIE already... This might be true if: 1. devices didn't have BOINC installed on them before the requirements changed. Thus not bi-passing or using 3rd party sites or side loading. 2. Not all projects have re-compiled for PIE. Thus there are still projects supporting non-PIE or not supporting PIE at all. Besides, projects can determine whether the OS meets the requirements. Not sure why WCG can't do the same. An example is POGS. They send work according to whether the device is PIE or non-PIE appropriately... |
||
|
|
|