getY() behaviour is incorrect?
<p>I have doubts that coordinates from <code>Event</code>s are right.</p>

<p>My application have single <code>Activity</code> instance with root <code>FrameLayout</code> element in its layout. I'm working on Galaxy Nexus, Android 4.0.2, but am writing application for Android 1.6 API. </p>

<p>Now to the production of this:</p>

<p>Let's override <code>onTouch()</code> callback on <code>FrameLayout</code> instance and add this logger (<code>e</code> stands for <code>event</code>):</p>

<pre><code>Log.i("a",String.valueOf(e.getY()-e.getRawY())
        +" "+String.valueOf(e.getY())
        +" "+String.valueOf(e.getRawY()));
     );
</code></pre>

<p>Then we check what the output is:</p>

<pre><code>06-03 16:31:50.560: I/a(15480): 0.0 676.4715 676.4715
06-03 16:31:51.326: I/a(15480): 0.0 675.4723 675.4723
06-03 16:31:51.380: I/a(15480): 0.0 680.4684 684.4653
06-03 16:31:51.388: I/a(15480): -100.0 584.4653 684.4653
06-03 16:31:51.412: I/a(15480): 0.0 686.4637 686.4637
06-03 16:31:51.412: I/a(15480): 0.0 686.4637 686.4637
</code></pre>

<p>See strange fluctuation in fourth stroke? Interesting that "100.0" is exactly the height of upper Android OS menu graphical elements (in my case). These "100.0" can be obtained from the app in this way:</p>

<pre><code>float padding = act.instance.getWindowManager().getDefaultDisplay().getHeight()
                -fl.getBottom();
</code></pre>

<p>, where <code>act</code> is <code>Activity</code>'s instance and <code>fl</code> is <code>FrameLayout</code>'s one.</p>

<p>I can add that if we draw something on layout with second value (<code>e.getY()</code>) from fourth stroke, it'll be right under finger. With third value it will be pretty lower than finger. So I conclude that system supplies me with wrong values of touch y-coordinate most of the time, and sometimes suddenly tells me right one.</p>

<p>My current workaround for this is only listen to <code>e.getRaw()</code> and subtract Android upper-screen elements height computed above.</p>

<p>So the questions are:</p>

<ol>
<li>Have anyone encountered this? Maybe run this logger and check what it prints on your configuration?</li>
<li>If your configuration is affected, do you know what causes it? Maybe you can tell more elegant workaround?</li>
</ol>

<p>Thank you for your attention!</p>
