Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 303
|
![]() |
Author |
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It's google who wont allow apps on their play store that don't comply with certain insecure memory handling.
Google is going to impose new rules that forbid loading of one application by another and will kick present BOINC off if no solution is found. Developers at Berkeley are already working on a complex solution. Essentially they have to include all the project science apps in the build i.e. it will require frequent updating. Suspect though that side loading would still be possible outwith the store, but not sure if that's an avenue ever entertained. |
||
|
sstrzelec
Cruncher Germany Joined: Dec 19, 2006 Post Count: 3 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
That would be one more reason not to outdate old devices, where those restrictions don't (and mostly won't) apply.
----------------------------------------Well but I can understand their point, actually an app downloading other binaries 'after install' normally is at best ... untrustworthy :D I'm not even talking about the store though, since old devices will continue to exist and old versions of the app running on them, too... so why not have workunits for them. just consider on the next projet ;) [Edit 1 times, last edit by sstrzelec at May 14, 2020 9:42:35 PM] |
||
|
Brummig
Cruncher Joined: Sep 19, 2016 Post Count: 22 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Snail number 5 came in last night with a valid result, ending the race, and giving the following CPU times:
Snail 1: 6.74 h Snail 2: Retired lame (timeout followed by abort) Snail 3: 81.25 h Snail 4: Left the course (detached) Snail 5: 39.81 h That's quite a spread. I'm guessing Snail 1 (aka "Speedy") is a Pi 4. Snail 3 (ie mine) snagged two more tasks last night, and their ETAs imply a lot less than 81 hours of crunching. Indeed one of the tasks is already half complete. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
That would be one more reason not to outdate old devices, where those restrictions don't (and mostly won't) apply. Well but I can understand their point, actually an app downloading other binaries 'after install' normally is at best ... untrustworthy :D I'm not even talking about the store though, since old devices will continue to exist and old versions of the app running on them, too... so why not have workunits for them. just consider on the next projet ;) I have no particular view other than Google wants their Android ecosystem to be as secure as can be. It so happens that Apple iOs does not allow BOINC either for the same reason so the BOINC developers have a particular interest in a solution that would permit for BOINC to also become available on the iPhone, 2 birds with 1 stone. The security certification is going to be interesting... Dr Anderson wont allow any science app to be packaged in the kit and the kit will be big. They'll have to make sure that it can be moved to 'external storage'. The current BOINC for Android cannot be moved, albeit saw a 'developer' option "Force allow apps on external' that permits pushing this. /OT edit: spell [Edit 1 times, last edit by Former Member at May 15, 2020 10:40:49 AM] |
||
|
yoerik
Senior Cruncher Canada Joined: Mar 24, 2020 Post Count: 413 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
That would be one more reason not to outdate old devices, where those restrictions don't (and mostly won't) apply. Well but I can understand their point, actually an app downloading other binaries 'after install' normally is at best ... untrustworthy :D I'm not even talking about the store though, since old devices will continue to exist and old versions of the app running on them, too... so why not have workunits for them. just consider on the next projet ;) I have no particular view other than Google wants their Android ecosystem to be as secure as can be. It so happens that Apple iOs does not allow BOINC either for the same reason so the BOINC developers have a particular interest in a solution that would permit for BOINC to also become available on the iPhone, 2 birds with 1 stone. The security certification is going to be interesting... Dr Anderson wont allow any science app to be packaged in the kit and the kit will be big. They'll have to make sure that it can be moved to 'external storage'. The current BOINC for Android cannot be moved, albeit saw a 'developer' option "Force allow apps on external' that allows pushing this. /OT that's one thing that would be helpful. Allowing it to move to external storage like MicroUSB, would mean BOINC would be less obstructive to the end user, and has more available storage to use for projects. ![]() |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Since my Android offers this (was some activation of the developer mode), I'm going to try it soon to see if it continues to stably crunch on 3 threads. The SD card is 64Gb (58GB real) when the core memory is only 16GB and 14GB used.
|
||
|
sstrzelec
Cruncher Germany Joined: Dec 19, 2006 Post Count: 3 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
[...] The SD card is 64Gb (58GB real) when the core memory is only 16GB and 14GB used. lol thats better than my best Android device :D I'm talking old devices, the oldest runs on 500MB zram and a 2GB SD (bindmounted into /data), since 2016 straight... But lately it struggles since someone set the min-SDK version to 19 (or at least above 17) for workpackages (Not at all talking about any APKs). |
||
|
yoerik
Senior Cruncher Canada Joined: Mar 24, 2020 Post Count: 413 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Since my Android offers this (was some activation of the developer mode), I'm going to try it soon to see if it continues to stably crunch on 3 threads. The SD card is 64Gb (58GB real) when the core memory is only 16GB and 14GB used. do keep me updated, please! I've got a decently sized SD card that could expand the usefulness of my devices. ![]() |
||
|
DavidH
Cruncher Joined: Apr 1, 2020 Post Count: 10 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
All, It appears that OpenPandemics only support Raspberry Pis running 32 bit OS images. Anyone else seeing this?
the boinc platform code aarch64-unknown-linux-gnu throws an error. Raspberry Pi 4 running Ubuntu 64 OS when I use Ubuntu 32 bit, platform code arm-unknown-linux-gnueabihf works, there is no issue and I am able to get work units. I would imagine the OpenPandemics can be complied for both ARM types since it is working on Android no issue...thoughts? |
||
|
|
![]() |