Android FAH client is now open source

[foldy]

https://developer.sonymobile.com/2017/1 ... en-source/

So if you have issues with the APP I guess you can post it here
https://github.com/sonyxperiadev/Folding-home/issues

And if someone has programming skills I guess you could help improve the APP.

[ChristianVirtual]

nice move ... some learning ahead ...

[joekienzle]

Is the project still active? Last commit was 5 months ago? Is there a new repo now? Are you looking for supporters?

[JimboPalmer]

Is the project still active? Last commit was 5 months ago? Is there a new repo now? Are you looking for supporters?

These are all good questions of Sony, who supports the Android client.

[foldy]

I asked the questions there, lets see if there will be an answer.
https://github.com/sonyxperiadev/Folding-home/issues/1

[bruce]

As far as FAH is concerned, the project is still running.

Are any of you smart enough to update the client so that it works on, say my Samsung Android phone rather than only working on Sony hardware?

[JimboPalmer]

Are any of you smart enough to update the client so that it works on, say my Samsung Android phone rather than only working on Sony hardware?

I understand the problem, not at all sure there will be an answer

ARM has introduced three strategies all called big.LITTLE for recent devices.

https://en.wikipedia.org/wiki/ARM_big.LITTLE

Each uses the idea that minor processing needs a low power CPU and major processing needs a high power CPU.

1) swaps all the tasks from weak, low power CPUs to strong, power hungry CPUs all at once. only all the weak or all the strong CPUs are active

2) swaps a task from a weak, low power CPU to a strong, power hungry CPU on a task by task basis. One of each pair of weak and stong CPUs is active

3) has all weak and strong CPUs active at once, migrates tasks as needed.

As you might imagine, all will have FAH swapping CPUs unexpectedly to a CPU that does not match the specs of when it started. Option 3 would have different CPUS taking different times to complete folding. These are 'hard' problems. Sony may not use any form of big.little, but if it does I bet it only uses one of them. The other two strategies may never be supported.

If Sony could figure out a way to force FAH into powerful CPUs before it gets the configuration of the processor, that would help in 1) and 2). For 3) you would have to either ignore the weak CPUs or assign them to a separate slot.

[bruce]

The classic client, is divided into two or three components which make sense in those terms. (I have not looked at the Sony code.) The FAHCore does Strong/Heavy processing -- the primary science code. The FAHClient does light/weak processing which can be further divided into two pieces: Display processing (which may or may not have intermediate processing needs) and then Internet I/O and file management (neither of which needs a high power CPU). The FAHCore processing would certainly need the battery management routines that can be found in the Sony code.

[foldy]

@joekienzle: I asked your questions at sonyxperiadev/Folding-home and got answer from Sony developer:

Hi.
Sorry for a delay in response, but we're regrouping after the project went open here in GitHub. Please, by all means submit bug reports, pull requests, fork, in other words consider project alive. We'll figure out the best way/place to continue and let you know in good time.
Cheers
https://github.com/sonyxperiadev/Foldin ... -345202627