Marker strangely lying above the sky when first start

[GoogleCodeExporter]

Start demo activity

Expect to see markers but nothing shows up. Instead, when rotate the phone 
toward the mid of the sky, you would see many markers lying there.

What version of the product are you using? On what operating system?
r104

Seems like the initializing process of coordinate transform matrix go wrong.

Original issue reported on code.google.com by wanpee...@gmail.com on 8 Mar 2012 at 4:05

[GoogleCodeExporter]

same issue i have faced , i guess it take a wrong value of altitude . 

Original comment by android....@gmail.com on 31 May 2012 at 10:13

[GoogleCodeExporter]

I'd check the altitude of your device versus the altitude of the Markers. When 
the markers altitude gets very high/low it could make something like that 
happen. Sometimes it's better to just zero out the altitude unless you are 
interested in things like mountain peaks, etc.

Original comment by phishman3579@gmail.com on 16 Aug 2012 at 2:01

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Similar issue here: The markers are only displayed from the horizon upwards, 
even though all heights are zeroed. 
Also, when "zooming in" (selecting a smaller radius), the markers are dragged 
to the left of the view until they disappear. With a radius <1km, the markers 
just bounce around.

Original comment by b...@creativeworkline.com on 3 Sep 2012 at 3:26

[GoogleCodeExporter]

If it's of any help, I think the issue is within the Marker.updateRadar() 
method, which asserts the marker not to be on the radar even though it is. I 
guess it has something to do with the vector calculation behind it.

This part seems to fail:
if ((locationArray[2] <= -1f) && (x*x+y*y)<(Radar.RADIUS*Radar.RADIUS)) {
            isOnRadar = true;
}

Original comment by b...@creativeworkline.com on 4 Sep 2012 at 9:52

[GoogleCodeExporter]

Original comment by phishman3579@gmail.com on 8 Jan 2013 at 7:27

• Changed state: Started

[GoogleCodeExporter]

I've made a commit today trying to fix this, let me know if it helps. revision 
143

Original comment by phishman3579@gmail.com on 15 Mar 2013 at 12:17

[GoogleCodeExporter]

Original comment by phishman3579@gmail.com on 17 Mar 2013 at 1:39