a possible bug in com.google.android.maps.GeoPoint

by zero » Thu, 25 Feb 2010 20:48:23 GMT

Sponsored Links

i see strange behaviour in my logs:
take the following code, assuming location is a valid filled object:
                Location newLoc=(Location)message.obj;
                Log.d("DEBUGLOCAL","passed loc ob="+newLoc.toString());
                int intlat=(int)(newLoc.getLatitude() * 1E6);
                int intlon=(int)(newLoc.getLongitude() * 1E6);
                Log.d("DEBUGLOCAL","passed loc converted INT values\n
lat="+intlat+"\n lon="+intlon);
              GeoPoint newPos=new GeoPoint(
              Log.d("DEBUGLOCAL","passed loc create GEOPOINT values\n
                         "\n lon="+newPos.getLongitudeE6());
i get the following output
  229              DEBUGLOCAL  D  passed loc converted INT values
  229              DEBUGLOCAL  D   lat=123002050
  229              DEBUGLOCAL  D   lon=123002050
  229              DEBUGLOCAL  D  passed loc create GEOPOINT values
  229              DEBUGLOCAL  D   lat=80000000  <----WTF??
  229              DEBUGLOCAL  D   lon=123002050

that surely isn't right ?
stable across 1.6 to 2.1 gmaps emulators.
as google api page doesn't have a bug tracker, does this belong into
the android bugtracker ?

ideas for solutions welcome.



Other Threads

1. When to close database in ContentProvider

I am trying to write a ContentProvider which itself is based on a
SqlLite database. I am puzzled when I need to close the database
because ContentProvider has onCreate( ) function but not onDestroy( )

I downloaded the android source code tree, and found

It appears this class called "openDatabase" but never "close" on it:

    public boolean onCreate() {
        final Context con = getContext();
            mDb = mDbHelper.openDatabase(getContext(), DATABASE_NAME,
null, DB_V

mDb.close( ) is never called

If there is no onDestroy() from ContentProvider and we don't call close
( ) on databases, doesn't this lead to some kind of memory/resource


2. OpenCORE capability

Hi Ravi (or any other from PacketVideo),
I have a straight forward question here about OpenCORE. In my understanding
and based on many feedbacks here at least, though OpenCORE is an awesome OMX
solution, OpenCORE's capability of supporting various media formats is to
some extent limited :) campared with other MMF like GStreamer. It is not
only a problem of the codec but also some missing features in parser
components. I just want to know whether it is on your roadmap to extend
support for more media formats in the near future. I'd appreciate if there
is some heads up in detail. Thank you.


3. CheckBoxPreference onClick Problems (Really Easy)

4. How to view the list of network connection mobile APNs or WiFi configured on the emulator.

5. How to test the openCORE on Android Emulator

6. How to enable debug logging in android source

7. OpenGL Acceleration for 2D Graphics