I have three androids crunching currently. Two are old mobiles, both HTC Ones nos. 8172296 and 7988119 which are my current and previous handsets. Both crunch away slowly but steadily when plugged in. My partner's Vivo handset no. 8221737 which is new and with 8 cores is proving a bit of a dud when processing WUs. I have tried using from 2-8 of the cores but the logged processing time is pathetic. Did a little test just now and the two WUs running show weird behaviour:
at 15.13 hrs: WU 05my10ab etc 14.41.1.142_1 showed 37.0% completed with 10.47.50 elapsed time while for the other WU: 06may10ab etc 14.41.1.176_0 showed 39.9% completed with 11.24.25 elapsed.
But at 15.26 hrs the former had gone backwards to show only 36.3% completed displaying a lower 10.39.18 elapsed
with the latter displaying: 39.2% completed with 11.15.42 elapsed????????
Can someone tell me what is going on here as these are now timed out as well?
I thought this new handset with 8 cores could provide an extra bit of number crunching power but seems to be useless?
TIA
George

---

Update
Seem to have cracked the vivo android issue. It only seems to run for a few minutes while plugged in and charging. But going into the app on the handset to see how the units are being crunched seems to get them going again. The read out showing % done does weird things and sometimes displays three different values in about 15 seconds. Doing this for the last few days when practical (It's my partner's mobile) means that several completed WUs were finally sent in yesterday (some with errors) with average crunch times of around a day. Newer ones look to take about half that. These times are slow compared to my laptops but then with eight cores, that makes up for it.
Having to do this though takes time and is rather like having to keep winding up a clockwork toy.
HTH

---