There are better solutions, driven by forum member timschuerewegen. The technical problem is described in a 77-page thread here. The reason for the iPhone behavior is described here:
timschuerewegen is working on a better solution, described here:
an update is on its way, read here.
Reading the complete thread from page 23 takes time but gives deep inside knowledge about why and how