Thanks for providing the extra information - we understand what it is that you are trying to do. As you have identified, the Android charts API currently does not function in quite the same way as its iOS counterpart.
Firstly, we apologise for this - we do strive to achieve feature parity between our Android and iOS products and we do base our development on customer demand. As such I have added an item to our backlog to include this feature. I cannot of course provide dates of when such a feature will become available at present.
In the meantime, there may be a work around albeit rather convoluted. Also, we have not tried this solution ourselves so it may not provide the functionality which you need, but it may be worth some consideration. The basic steps would be:
-Using the methods (previously mentioned) on the Axis, obtain a pixel value for your known data value (in your example, this is 10/01/2016, for the x axis).
-Choose a suitable pixel value for the other axis (in this example, the y axis) - you could again use the conversion methods on the Axis to covert from the maximum data value of the visible range, to a pixel value.
-Ensure the crosshair and tool tip are not shown when a user long presses the chart - to achieve this you could use the api methods on the crosshair itself and the OnTrackingInfoChangedForCrosshair (and Tooltip) lister methods
-Using the standard Android framework methods, programmatically perform a long press on your chart, using the pixel values already calculated
-Implement the OnTrackingInfoChangedForCrosshairListener
-Using the values given to you when the onTrackingInfoChanged method is called on the listener, you should be able to obtain the mapped y value which you need.
I hope that this helps,