How about making it easier to Crunch on Cellphones

Message boards : Promotion : How about making it easier to Crunch on Cellphones
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Tom Miller
Avatar

Send message
Joined: 6 Jul 14
Posts: 21
United States
Message 90429 - Posted: 3 Mar 2019, 0:31:40 UTC

There are BOINC apps that don't crunch on modern Android OS phones. It would be easier to "get the phone out" if we could get a positive result on all the projects we are fond of.

Example: Seti doesn't run well on modern Android OS's.
"You are entitled to your own opinion but not to your own facts." Senator and Professor Patrick Moynihan
ID: 90429 · Report as offensive     Reply Quote
Profile Gary Charpentier
Avatar

Send message
Joined: 23 Feb 08
Posts: 1887
United States
Message 90466 - Posted: 3 Mar 2019, 7:53:38 UTC - in response to Message 90429.  

There are BOINC apps that don't crunch on modern Android OS phones. It would be easier to "get the phone out" if we could get a positive result on all the projects we are fond of.

Example: Seti doesn't run well on modern Android OS's.

I hate to be so blunt but, the project is open source. Write it so it works as you envision it.
ID: 90466 · Report as offensive     Reply Quote
Profile Ageless
Volunteer moderator
Project administrator
Avatar

Send message
Joined: 29 Aug 05
Posts: 13124
Netherlands
Message 90470 - Posted: 3 Mar 2019, 8:55:36 UTC - in response to Message 90429.  

Of course it doesn't help if these modern Android versions are 32bit running on a 64bit CPU. Because then you automatically get 32bit apps sent to you, which don't run well on 64bit hardware. It would be nice if the Android device manufacturers were consequent and honest and just send 64bit OS along with all 64bit hardware. Now you won't find out about it until well after you bought the thing and then you have to run some third party software to find out about the bitness of your OS as the OS itself doesn't tell you!

I know, I've been bit by it with the Samsung Galaxy Tab A 10.5" (2018) version with Android 8.1 - 32bit, and with BOINC checking the EABI version, it gets sent the old 32bit applications which go bust because the correct 32bit drivers aren't loaded for the CPU.
But nowhere in the wide world will you find that when you buy a Samsung Galaxy Tab A 10.5 inch (2018) with Android 8.1 that that Android 8.1 is only 32bit, apparently no one knows about it or everyone assumes it's 64bit. That combined with Samsung formatting the user space in FAT32, so you can at max send one 4GB file over, or at max a bunch of files at 4GB... just crazy.

I'm waiting for XDA-Developers to come up with a good ROM and then I'll switch over immediately. Now the tablet is almost unusable anyway, as copying stuff to it, be it text files, music or video is a chore: plug cable in, press allow access, select files, copy files over, now anywhere between after 10 seconds and a minute the transfer may hang, so unplug USB cable, replug, allow access, copy stuff. I resort to moving the SD card from the tablet to my phone, copy everything I need, then put the card back in the tablet. This of course only works for stuff on the SD Card, not for stuff on the internal 64GB.
ID: 90470 · Report as offensive     Reply Quote

Message boards : Promotion : How about making it easier to Crunch on Cellphones

Copyright © 2019 University of California. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.