FAHMM on iOS? Anyone got it working?

[Tuna_Ertemalp]

Thanks for your interesst in that app. Haven’t touched it for a while. First: the discovery was a kind of experiment and proof of concept but never made it into consideration of the official FAH stack. No direct scientific benefit. UX is not a high enough priority. I might should remove or hide that to avoid confusion. if one is really geeky it could be setup manually but defeat somehow the purpose.

static IPs for the folding hosts works best.

Was myself inactive for the last two years F@H and recently reinstalled a CPU system, but didn’t got any work. Even after a day idle. Basically I can’t test right now. No GPU Right now at hand. Will try again soon.

@ChristianVirtual,

I just saw that you (or, was it someone else?) made an update to the iOS app and my daily AppStore update brought it in. Thanks!

Fresh feedback:

1) The donor stats now work. However: I briefly contributed to a different team than my main team, like for a day. So, I end up having two boxes in there, one for my main team, and another for that transient team. It would be great if there was an additional summary box that showed the combined score & WUs & ranking, like https://stats.foldingathome.org/donor/Tuna_Ertemalp does.

2) The log viewer for each slot (third icon from top left), when brought up first is on the Workunit tab and is empty. When I click on the CLIENT tab, then it shows the log. Afterwards, clicking on SLOT or WORKUNIT tabs do show the relevant log.

3) Emailing from the log viewer brings up the email app with the proper subject line, and I can enter the destination email address. However there is no log in the email, either as body text or as an attachment.

4) The Camera icon now works without a crash! But there is no visual indication that something happened, so I found myself clicking on it many times, at first, until I saw something like 23 photos in my photo roll. LOL.

5) One problem with the camera snapshot: I don't see the host name, even though the slot name is visible. So, if you have 23 snapshots, you have no idea what hosts they are from. One solution might be to include the host name in the slot info in the card all the time, subject to some truncation.

6) There might be value in making the camera click a long tap which could bring up three choices: Snapshot this slot, snapshot all slots on this host, snapshot all hosts & slots. And choosing one of the last two might ask whether the user wants a combined photo, or one photo per host, or one photo per slot. Just a thought...

Thanks for the work!
Tuna

[ChristianVirtual]

Thanks for your interesst in that app. Haven’t touched it for a while. First: the discovery was a kind of experiment and proof of concept but never made it into consideration of the official FAH stack. No direct scientific benefit. UX is not a high enough priority. I might should remove or hide that to avoid confusion. if one is really geeky it could be setup manually but defeat somehow the purpose.

static IPs for the folding hosts works best.

Was myself inactive for the last two years F@H and recently reinstalled a CPU system, but didn’t got any work. Even after a day idle. Basically I can’t test right now. No GPU Right now at hand. Will try again soon.

@ChristianVirtual,

I just saw that you (or, was it someone else?) made an update to the iOS app and my daily AppStore update brought it in. Thanks!

Fresh feedback:

<snip>
Tuna

Thanks Tuna for the great feedback. Will try to incorporate them.

Some, like the double stats box I have too. Was struggle a bit to decide what way I wanted. But was until time pressure to get it through app review due to changes on requirements by Apple. I keep working on it.

[Tuna_Ertemalp]

I keep working on it.

Awesome! All we can ask for!

Tuna

[AnClar]

I keep working on it.

Awesome! All we can ask for!

Tuna

+1 Thank you @ChristianVirtual for your work on the app! Greatly appreciated.

[AnClar]

Since the update, the app seems more stable, however, unless I'm doing something wrong, the protein viewer is broken, both on my iPhone and iPad. It stays stuck at "loading" and never brings up the protein.

[ChristianVirtual]

Since the update, the app seems more stable, however, unless I'm doing something wrong, the protein viewer is broken, both on my iPhone and iPad. It stays stuck at "loading" and never brings up the protein.

Yes, I have the same issue with FAHClient 7.6.13. It still works well with 7.5.1. I can easy reproduce via telnet connection.
In case of 7.6.13 the connection to telnet get closed; on 7.5.1 I get the desired information

What client version are you running ?

Raised an issue on GitHub https://github.com/FoldingAtHome/fah-issues/issues/1536

[AnClar]

Since the update, the app seems more stable, however, unless I'm doing something wrong, the protein viewer is broken, both on my iPhone and iPad. It stays stuck at "loading" and never brings up the protein.

Yes, I have the same issue with FAHClient 7.6.13. What client version are you running ?

Raised an issue on GitHub https://github.com/FoldingAtHome/fah-issues/issues/1536

I’m running 7.6.13 ON iOS 13.5.1 And thanks again for maintaining the app.

[ChristianVirtual]

Since the update, the app seems more stable, however, unless I'm doing something wrong, the protein viewer is broken, both on my iPhone and iPad. It stays stuck at "loading" and never brings up the protein.

Yes, I have the same issue with FAHClient 7.6.13. What client version are you running ?

Raised an issue on GitHub https://github.com/FoldingAtHome/fah-issues/issues/1536

I’m running 7.6.13 ON iOS 13.5.1 And thanks again for maintaining the app.

Thanks; same FAHClient version ... here we need to wait for an update version of the FAH software as this is out of my control and no workaround possible.

[Tuna_Ertemalp]

I have the same issue with FAHClient 7.6.13. It still works well with 7.5.1. I can easy reproduce via telnet connection.
In case of 7.6.13 the connection to telnet get closed; on 7.5.1 I get the desired information

Interesting. I remember in 7.5.1 the viewer didn't work on Windows. In 7.6.13, it does. So, seems the effort to fix it on Windows broke the telnet side... Hah!

Tuna