Thank you Pieter for the code snippet.
I can also confirm that this workaround is needed for Samsung Spica,
phone model GT-I5700
with android 1.5.
Johan
On Fri, Nov 13, 2009 at 10:12 AM, Pieter pie...@gamesquare.nl wrote:
Allright, I have taken up the gauntlet and wrote a subclass for
working
Since this was brought back up ... this worked for me as well for the Cliq
(original issue).
Also, FYI, I found that an easier way to get the distance for the circle
radius is to simply use Projection.metersToEquatorPixels(float), which
converts a distance in meters to pixel units.
I also added
Allright, I have taken up the gauntlet and wrote a subclass for
working around this bug.
It draws the my location disc and an accuracy circle. You can test
it on a device that is
not bugged by initializing the bugged variable to true.
It is a quick and dirty hack but it seems to work correctly
It appears to be on the Cliq only..
I actually reported the bug first when it was seen in Cyanogen.
http://code.google.com/p/cyanogenmod/issues/detail?can=2q=344colspec=ID%20Type%20Status%20Priority%20Version%20Owner%20Summary%20Stars%20Modifiedid=344
They fixed it. Looks like they had same
Actually we got around it by drawing our own dot on the screen.. Here
is a code snippit.. Inside our
@Override
public void drawMyLocation(Canvas canvas, MapView mapView,
Location
lastFix, GeoPoint myLocation, long when)
.
.
.
try {
Thanks for the info and code snippet. At least I know where to go from
here. Of course without an actual Cliq device I have no way of truly testing
and verifying this, so this should be fun.
It's sad that it's up to developers to add special-case code to compensate
for a device's bugged version
I already implemented that code into our live version of a2b, and we
got
feedback that it is working now. So that should fix it up for you.
Chris.
On Nov 12, 12:29 pm, TreKing treking...@gmail.com wrote:
Thanks for the info and code snippet. At least I know where to go from
here. Of course
The only drawback is that the accuracy indicator (the blue circle
indicating GPS accuracy) does not work in this case. With a little bit
of work this could probably also be implemented, but it is a little
more complex than just drawing an image.
On Nov 12, 6:37 pm, chrispix chris...@gmail.com
You are correct. Until it is fixed, I figure this was a workaround
that would work :). You can pull accuracy from the GPS, although I am
not sure of the exact calculation to determine the pixel circle size
on screen based on the zoom view.
Chris.
On Nov 12, 2:36 pm, Pieter pie...@gamesquare.nl
Yeah, it's better than a force-close, that's for sure.
Though getting the pixel radius for the circle shouldn't be too hard. With
the GPS accuracy value you can get a latitude / longitude value that's an
offset from the current estimated location, map those two points to screen
space with the
I have seen exactly the same problem, but only reproducible in some
phones with non standar builds. Anyway, they are 1.5 flavour.
The same piece of code works perfectly in a 1.6 G1 Dev Phone.
If you extend MyLocationOverview and overwrite the draw method it does
not crash... anyway this is not
Well, I suppose you do have a point. I just thought that 1.6's
proper release was a bit more imminent.
I'll check back once Donut's fully ready for prime time, then.
Thanks!
On Sep 26, 8:48 am, MrChaz mrchazmob...@googlemail.com wrote:
Well if they will install a non-released version of the
Well if they will install a non-released version of the OS then that's
to be expected.
On Sep 25, 10:04 pm, CaptainSpam captains...@gmail.com wrote:
Recently, two independent users with 1.6 (Donut) on their phones have
informed me that my app crashes after it enters a MapView, just as
soon as
13 matches
Mail list logo
