Estimating remaining time
There is no API for estimating how long it will take to finish the transfer. Because there is no way to compute that value with any usable level of certainity. We all know the jokes about Windows or other program not being able to decide how long the data transfer will take and floctulating wildly between few seconds and few millenia. It's a good joke you'll stop laughing to once you try to implement this functionality yourself.
Because there is no way to do it correctly. Even in stable conditions, when there is no change in speed of actual data transmission, the amount of time will vary wildly based on number of files. Every new file requires certain amount of operations to be performed. If there is small number of large files, time taken by these operations can be ignored, because it will be negligible in comparison to actual data transfer time. But if there is very large number of very small files, these operations can actually take significant amount of time. In combination of large and small files it's almost incredible to predict, even under otherwise ideal conditions.
And the conditions are never close to ideal when performing network operations. Because the network transfer speed can vary wildly, based on network utilization and other factors, such as link quality and interference, especially in wireless networks.
In theory, we can compute the remaining time easily: we know current transfer speed in bytes per second and we know how many bytes remain to be transferred... In practice, for reasons outlined above, I wholeheartedly recommend not to implement this feature -- unless you want to be a butt of many jokes.